Unsolved
This post is more than 5 years old
20 Posts
0
4355
September 29th, 2006 04:00
Can not backup with RMAN
Dear all,
When I test run RMAN script then it has message error below. Please help me how to solve it?
$
$
$ rman nocatalog cmdfile '/script/nwora' send '"NSR_ENV=(NSR_SERVER=BKPRO-SRV01,
NSR_GROUP=oracle_db)"'
Recovery Manager: Release 9.2.0.6.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
RMAN> connect target sys/change_on_install
2> #connect target /
3>
4> run {
5> set command id to 'xxx';
6> allocate channel t1 type 'SBT_TAPE';
7> allocate channel t2 type 'SBT_TAPE';
8> send 'NSR_ENV=(NSR_DATA_VOLUME_POOL=Defaule)';
9> backup full filesperset 4
10> format '/FULL_%d_%U/'
11> (database);
12> release channel t1;
13> release channel t2;
14> }
15>
connected to target database: SC (DBID=2699706201)
using target database controlfile instead of recovery catalog
executing command: SET COMMAND ID
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of allocate command on t1 channel at 09/29/2006 18:50:22
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library
Additional information: 2
Recovery Manager complete.
$
When I test run RMAN script then it has message error below. Please help me how to solve it?
$
$
$ rman nocatalog cmdfile '/script/nwora' send '"NSR_ENV=(NSR_SERVER=BKPRO-SRV01,
NSR_GROUP=oracle_db)"'
Recovery Manager: Release 9.2.0.6.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
RMAN> connect target sys/change_on_install
2> #connect target /
3>
4> run {
5> set command id to 'xxx';
6> allocate channel t1 type 'SBT_TAPE';
7> allocate channel t2 type 'SBT_TAPE';
8> send 'NSR_ENV=(NSR_DATA_VOLUME_POOL=Defaule)';
9> backup full filesperset 4
10> format '/FULL_%d_%U/'
11> (database);
12> release channel t1;
13> release channel t2;
14> }
15>
connected to target database: SC (DBID=2699706201)
using target database controlfile instead of recovery catalog
executing command: SET COMMAND ID
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of allocate command on t1 channel at 09/29/2006 18:50:22
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library
Additional information: 2
Recovery Manager complete.
$
No Events found!


suwatl
20 Posts
0
September 29th, 2006 05:00
suwatl
20 Posts
0
September 29th, 2006 05:00
suwatl
20 Posts
0
September 29th, 2006 05:00
This environment is:
Oracle Server 9i on Solaris 10, NMO version 4.2
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
September 29th, 2006 05:00
amediratta
2 Intern
•
2K Posts
0
September 29th, 2006 05:00
connect target user/password@{database};
connect rcvcat user/password@{recovery catalog};
run {
set command id to 'abc';
allocate channel t1 type 'SBT_TAPE'
parms 'ENV=(NSR_SERVER={backup server},NSR_DATA_VOLUME_POOL=Default)' ;
allocate channel t2 type 'SBT_TAPE'
parms 'ENV=(NSR_SERVER={backup server},NSR_DATA_VOLUME_POOL=Default)' ;
release channel t1;
release channel t2;
}
The output of this should have reference to NMO. Another way to test is to run the command sbttest which is probably in Oracle bin folder. run- sbttest {filename} - {filename} is a small text file. If there is any backup happening, the link works good.
I assume you have tested the backup of local file system from this machine. Also, you can refere the installation guide for library linking command.
amediratta
2 Intern
•
2K Posts
0
September 29th, 2006 05:00
I still feel you are not linking the library properly. Can you detail the steps you are takin for configuring this module.
amediratta
2 Intern
•
2K Posts
0
September 29th, 2006 05:00
Check the procedure and the library linking. The only difference in the backup script & test script is that the test script does not have the backup syntax and it just check which Media Management layer is working else it may allocate channels, create data but still not backup because of not being able to locate the Media Management Layer.
Therefore we use this script to test the link before spending time on full blown backup scripts.
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
September 29th, 2006 05:00
kkauffmann
2 Posts
0
September 29th, 2006 05:00
Example for AIX:
$ORACLE_HOME/lib/libobk.a
libobk.a -> /usr/lib/libnwora64.a
suwatl
20 Posts
0
September 29th, 2006 05:00
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00552: syntax error in command line arguments
RMAN-01005: syntax error: found "parms": expecting one of: "append, at, auxiliar
y, catalog, cmdfile, clone, debug, log, msglog, mask, msgno, nocatalog, pipe, rc
vcat, slaxdebug, send, target, timeout, trace"
RMAN-01007: at line 2 column 1 file: command line arguments
bash-3.00$
amediratta
2 Intern
•
2K Posts
0
September 29th, 2006 05:00
1. Remove any existing libobk.* or libnwora.* library files. No such library should exist in any of the default directories or in any directory specified in $LD_LIBRARY_PATH, $LIBPATH or $SHLIB_PATH.
2. Log in as root on the Oracle server host.
3. Locate the Oracle module software on the CD ROM.
4. Enter the command ¿
Pkgadd ¿d /dir_pathname LGTOnmo.
5. Install the Oracle module in the same path as Networker Client software. To do this on a non-default location, enter the parameter basedir as ask in /var/sadm/install/admin/default file.
6. Link the Networker module for Oracle library file
a. The library files should be installed in /usr/lib or /usr/shlib folders.
b. Log on as ORACLE_HOME owner.
c. Shut down all Oracle instances that use this ORACLE_HOME(Not required for Oracle 9i & above).
d. Create the symbolic link as per the version in use ¿
1. cd $ORACLE_HOME/lib.
2. ln ¿s /usr/lib/libnwora.so libobk.so.
e. Restart all ORACLE_HOME instances.
7. Configure the nsrnmo script to be used as backup command located in the folder where Legato Networker binaries are located. For multiple databases(using multiple ORACLE_HOME), configure multiple scripts with different name as per the parameters ¿
a. Mandatory ¿
i. ORACLE_HOME ¿ Oracle home for the database to be backed up.
ii. PATH ¿ Location of nsrnmostart script of Legato Networker Module.
8. On the Networker Server, create a client ¿
a. Save Set ¿ path of the script.
b. Backup Command ¿ nsrnmo script.
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
September 29th, 2006 05:00
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
September 29th, 2006 07:00
I don't believe the problem is with script as otherwise you get dofferent kind of error by RMAN - so I still see that library as suspect. Try to relink it again and see what happens. Also, make sure you this opened with both Legato and Oracle (eg. if you are in hurry to address that issue asap).
suwatl
20 Posts
0
September 30th, 2006 20:00
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
September 30th, 2006 23:00