Hi All,

One of our servers currenty runs two versions of Oracle 8i (8.1.6) and 9i 
(9.2.0).  Yesterday we installed the oracle agent and applied the Maintenance 
Pack 5.  We also brought down all the the oracle instances and did the 
following links.

FOR 8i: $ORACLE_HOME/lib/libobk.sl -> /usr/openv/netbackup/bin/libobk.sl
FOR 8i: $ORACLE_HOME/lib64/libobk.sl -> /usr/openv/netbackup/bin/libobk.sl64
FOR 9i: $ORACLE_HOME/lib/libobk.sl -> /usr/openv/netbackup/bin/libobk.sl64

We then brought up all the instances and did some testing on the oracle 9i.  We 
generated a template for a 9i instance which was then converted to a script and 
added any relevant environment variables.  Even though we have not done any 
restore testing we have been able to backup successfully using this script.

However when testing 8i, we have come across this problem which is driving us 
crazy.  We created a template and generated a script from this template and 
modified the template.  When we executed the template, 
the /usr/openv/netbackup/logs/user_ops/dbext/oracle/progress.log shows the 
following:
.
.
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: ch00
RMAN-08500: channel ch00: sid=14 devtype=SBT_TAPE
RMAN-08526: channel ch00: MMS Version 65.4.10.176
.
.

This clearly shows that RMAN is trying to use some library API , which calls 
some type of media management software and not the Veritas.

After looking at the script we noticed the following lines (SCRIPT 1):

export 
LD_LIBRARY_PATH=$ORACLE_HOME/8.1.6/lib:/lib:/usr/lib:/oracle/product/8.1.6/rdbms
/lib
export SHLIB_PATH=$ORACLE_HOME/lib:$ORACLE_HOME/rdbms/lib

Since we are using 64bit Oracle, we figured these lines should be (SCRIPT 2):

export 
LD_LIBRARY_PATH=$ORACLE_HOME/lib64:/lib:/usr/lib:/oracle/product/8.1.6/rdbms/lib
export SHLIB_PATH=$ORACLE_HOME/lib64:$ORACLE_HOME/rdbms/lib64

However after making these changes and running the script, we got the following:

/usr/lib/dld.sl: Bad magic number for shared 
library: /oracle/product/8.1.6/lib64/libclntsh.sl.8.0
/usr/lib/dld.sl: Exec format error
sh[6]: 29276 Abort(coredump)

After doing research we found out the problem could be that only the 
LD_LIBRARY_PATH should point to ORACLE_HOME:/lib64 but NOT SHLIB_PATH.  So we 
changed the script as follows (SCRIPT 3):

export 
LD_LIBRARY_PATH=$ORACLE_HOME/lib64:/lib:/usr/lib:/oracle/product/8.1.6/rdbms/lib
export SHLIB_PATH=$ORACLE_HOME/lib:$ORACLE_HOME/rdbms/lib

After executing the script now we get the same thing as if LD_LIBRARY_PATH 
pointed to ORACLE_HOME/lib and not ORACLE_HOME/lib64
.
.
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: ch00
RMAN-08500: channel ch00: sid=14 devtype=SBT_TAPE
RMAN-08526: channel ch00: MMS Version 65.4.10.176
.
.

We then doubled checked the links we created and they are as follows:
(32BIT)

lprod>/oracle/product/8.1.6/lib #ll ?d libobk*
lrwxr-xr-x   1 oracle     dba              7 May 24  2000 libobk.a -> libmm.a
lrwxr-xr-x   1 oracle     dba             34 Nov 17 09:06 libobk.sl -
> /usr/openv/netbackup/bin/libobk.sl
lrwxr-xr-x   1 oracle     dba             30 Apr 17  2001 libobk.sl.omni -
> /opt/omni/lib/libob2oracle8.sl
lrwxr-xr-x   1 oracle     dba             36 Nov 30  2000 libobk.sl.orig -
> /opt/omni/lib/libob2oracle8_64bit.sl

(64BIT)
lprod> /oracle/product/8.1.6/lib64 #ll libobk*
lrwxr-xr-x   1 oracle     dba             36 Nov 17 09:09 libobk.sl -
> /usr/openv/netbackup/bin/libobk.sl64
lrwxrwxr-x   1 oracle     dba             13 Jun  7  2000 libobk.sl.orig -> 
libdsbtsh8.sl
lrwxr-xr-x   1 oracle     dba             37 Apr 17  2001 libobk.sl64.omni -
> /opt/omni/lib/libobk2oracle8_64bit.sl

The Netbackup Oracle Admin guide says that if libobk.a exists it should be 
renamed to libobk.a.orig.  It appears that on the 32bit lib directory we failed 
to do this when we did the link.  The *.omni, *.orig, belonged to Omniback 
(which is what we are getting away from).

The questions that we have are the following:
1)      Is the fact that we failed to rename the libobk.a to libobk.a.orig on 
the 32bit lib directory that is causing the problem?
2)      If our failure to move libobk.a to libobk.a.orig is causing our 
problem, why is this library being used by RMAN when we are using 64bit oracle 
and LD_LIBRARY_PATH points to ORACLE_HOME/lib64?
3) Does anyone know if "MMS Version 65.4.10.176" belongs to omniback?

Any help is greatly appreciated.  

Thank you,
-Adam




----------------------------------------------------------------------
This mail sent through Toaster-Horde (http://qmailtoaster.clikka.com/)