Move the library to Oracle home and put put ld_library_path in the backup 
script.  I believe ld_library_path is in the script by default for 5.1  I am 
doing this only on 32bit linux and my database backups are working fine 

-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu [mailto:veritas-bu-admin 
AT mailman.eng.auburn DOT edu] On Behalf Of Mark.Donaldson AT cexp DOT com
Sent: Thursday, September 23, 2004 11:26 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] I hate linux: Oracle 64-bit on RH-ES-3.0 vs the libobk.so 
media m anagement library

They're going to take away my geek card for saying this, but I think I'm
starting to hate Linux.  Just too many variations.

Anyway, we're trying to get Oracle 9.2.0.4 64-bit backing-up using the RMAN
tool through the NB 5.1 database extentions on a Linux RH 3.0
(opteron-based) media server.

Filesystem backups are finally working once we solved the numerous QLogic vs
AMD architecture problems.  The problem persists, though, in that oracle
claims it can't load the media management library,
/usr/openv/netbackup/bin/libobk.so.  We've tried the 32 & 64-bit versions
and both seem the same (you have to spoof the installation script to make
the 64-bit install - there's no provision for a 64-bit Redhat installation).


A "file" of the library, both as root & as oracle, returns valid information
so the file is readable from a Unix POV.  The 64-bit libokk.so returns that
it's an IA-64 (itanium) compile but at this level we're hoping that 64-bit
is 64-bit.

The oracle error looks like this:

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of allocate command on t1 channel at 09/22/2004 11:03:58
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library


Everything we can find on it suggests that the library can't be located.
Our DBA has tried every variant on LD_LIBRARY_PATH, specifying the library
in the RMAN command, etc. that seems possible.  

Anybody solved this one?

-M

=================================================
  The one thing I've learned about freedom of 
  expression is that you really ought to keep
  that sort of thing to yourself - Scott Adams
=================================================
  Mark Donaldson - SA - Corporate Express
=================================================
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

CONFIDENTIALITY NOTICE: 
        This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is privileged, 
confidential and exempt from disclosure under applicable law.  If the reader of 
this message is not the intended recipient or the employee or agent responsible 
for delivering this message to the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited.  If you have received this communication in error, please 
notify us immediately by email reply.