The folloiwng is a good post from Samir which I kept. It seems to cover your environment well. Hope it helps John
Hi,
In order for RMAN to work with a third party backup product the third party
vendor writes an interface to an Oracle supplied API and supplies this in
the form of a library.
Oracle supplies a default copy of the library as $ORACLE_HOME/lib/libobk.so
which has the RMAN default functionality of writing to disk only.
Installation of an RMAN media management product logically replaces this
library. How this logical replacement is done depends on several Oracle
documents and one netbackup document, most of which contradict each other.
As long as it is clear how the library is logically presented to Oracle it
doesn't matter how it is done.
The library that Oracle currently uses can be established by executing:
ldd $ORACLE_HOME/bin/oracle
This will list the libraries linked to the Oracle executable, specifically
libobk.so.
The Veritas supplied file is called libobk.so.1. Oracle thinks it is called
libobk.so, which it looks for in LD_LIBRARY_PATH. Therefore a soft link is
needed from libobk.so somewhere in LD_LIBRARY_PATH to the Netbackup supplied
libobk.so.1. This can be done with:
LD_LIBRARY_PATH=$ORACLE_HOME/lib:
and then either:
ln -s /opt/openv/netbackup/bin/libobk.so.1 $ORACLE_HOME/lib/libobk.so
or:
cp /opt/openv/netbackup/bin/libobk.so.1 $ORACLE_HOME/lib/libobk.so.1
ln -s $ORACLE_HOME/lib/libobk.so.1 $ORACLE_HOME/lib/libobk.so
Other combinations of these links are obviously possible, but the important
thing is to be consistent. With several ORACLE_HOME's the former is
preferable, the latter becomes more relevant if a version dependency had
been discovered between RMAN and Netbackup such that each ORACLE_HOME needed
a different copy of the library.
Additionally, Oracle 8.0.5 statically links the library into the Oracle
executable, so once the executable is relinked it doesn't matter what
happens to the original library file. At 8.1.6 however the library is
THEORETICALLY dynamically linked and so always depends on finding a copy on
LD_LIBRARY_PATH. A bug in 8.1.6 (1252142) means this dynamic linking does
not work and the library still has to be statically linked to the Oracle
executable. The bug is fixed at 8.1.7.
Hope this helps.
Hi Listers,
I have a question regarding using 8i RMAN with Netbackup 3.4.
I remember on 8i one no longer needs to relink the oracle executable
when intergrate with a 3rd party backup software. All I have to
do it change the symbolic link $ORACLE_HOME/lib/libobk.so to point
to the media management library.
Now from the Netbackup 3.4 for Oracle manual, it says on Solaris
for 8.1.6, you need to relink the oracle executable by doing:
make -f ins_rdbms.mk ioracle LLIBOBK=-lobk
So the question is should I relink or not?
Thanks for your feedback.
Rich
Nice answer Samir. As an additional note... after linking I've used the
sbttest utility from Oracle to verify a working installation. (We're using
Netbackup with Linux and have encountered problems which Veritas is
working on.)
The sbttest program is nice but for complete backup installation testing I
believe in performing test recoveries. I've created small test databases
on production servers and have scripted several recovery scenarios. For our
current situation it turns out that we can get a successful backup but
restores are a problem. Since backups aren't any good if you can't restore
the backup is suspect. We can restore files from tape to disk but finishing
the recovery requires getting out of RMAN and recovering from the SQL
prompt. We can also restore from RMAN as long as we don't have more than 2
commands in the run { commands... } syntax. Of course this could get quite
tedious in a multiple datafile restore scenario so we're insisting that
Veritas fix the communication problems between RMAN, Netbackup and our tape
robot.
So I guess the object lesson from all this is that, regardless of "apparent"
linking success, it pays to be anal and thorough when it comes to validating
your backup implementation and the best way to do this is to perform some
actual recoveries.
Hi Listers,
I have a question regarding using 8i RMAN with Netbackup 3.4.
I remember on 8i one no longer needs to relink the oracle executable
when intergrate with a 3rd party backup software. All I have to
do it change the symbolic link $ORACLE_HOME/lib/libobk.so to point
to the media management library.
Now from the Netbackup 3.4 for Oracle manual, it says on Solaris
for 8.1.6, you need to relink the oracle executable by doing:
make -f ins_rdbms.mk ioracle LLIBOBK=-lobk
So the question is should I relink or not?
Thanks for your feedback.
Rich
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: 22 February 2002 14:38
To: Multiple recipients of list ORACLE-L
Subject: 8i and Veritas NetBackup
Is anyone using this combination? We're having problems getting backups to work with 8i. It works fine with our 8 dbs, but when we try to backup the 8i ones, the control panel says the backup has started, but it doesn't finish and usually has a dead rman process on the db.
We've working with Veritas support, but it's been 2 weeks and no answer.
The dbs are 8.1.7.3 on Solaris 7 and we did patch the oracle executables.
Thank you for any help.
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author:
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
=========================================================
This electronic message contains information from the mmO2 plc Group
which may be privileged or confidential. The information is intended to be
for the use of the individual(s) or entity named above. If you are not the
intended recipient be aware that any disclosure, copying, distribution or
use of the contents of this information is prohibited. If you have received
this electronic message in error, please notify us by telephone or email
(to the numbers or address above) immediately.
=========================================================
