Mark,

Please review the text below.  It is from a technote in a pending
publish state.

I'll follow this thread to see if the info helps or not and if needed
I'll provide feedback to the author.

Regards,

Doug Braden
VERITAS Impact Team


The ORA-27211 error indicates that the channel allocation is failing
because Oracle is not loading the media management library. If the
channel allocation fails, then Oracle generates a trace file in the
USER_DUMP_DEST location that contains the error that caused the channel
allocation to fail. The trace file should have the complete path name of
the media management library loaded by Oracle as well as any other media
manager errors or operating system errors. For example, the trace file
on UNIX may be called something like
/oracle/rdbms/log/prod1_ora_16226.trc, and may contain information such
as the following:

*** 2001-08-29 17:16:54.385

SKGFQ OSD: Error in function sbtinit on line 2396

SKGFQ OSD: Look for SBT Trace messages in file
/oracle/rdbms/log/sbtio.log

SBT Initialize failed for oracle.static

The last line of this output indicates that Oracle is loading the
default static library instead of the media management library that you
installed.

To test the loading of the media management library, try allocating a
channel by using the PARMS parameter SBT_LIBRARY to force the loading of
the media management library. 

For example, if the library is called
/usr/openv/netbackup/lib/some_mm_lib.so and is pointed to
by$ORACLE_HOME/lib/libobk.so, then run a command such as the following,
making sure to specify whatever PARMS settings are required by  media
manager:

RUN

{

ALLOCATE CHANNEL c1 DEVICE TYPE sbt

PARMS='SBT_LIBRARY=?/lib/libobk.so',

'ENV=(NSR_SERVER=tape_svr,NSR_CLIENT=oracleclnt,NSR_GROUP=oracle_tapes)'
;

}

If the channel allocation fails, then check the trace file again to see
whether you can learn anything new. If the channel allocation with
SBT_LIBRARY succeeds, but an ordinary SBT channel allocation fails, then
Oracle is probably trying to load a library ($ORACLE_HOME/lib/libobk.so
on UNIX, %ORACLE_HOME%/bin/orasbt.dll on NT) other than the one you
installed. You may have more than one library in the operating system
path, and the one that Oracle is loading is the wrong one. 

-----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