Oracle RMAN Problems

Can you post your log from module (placed in applogs on client) and rman script please? I assume library linking was done as per manual instructions?

You posted in this forum a while back the following :

luxz


Posts: 4
Registered: 1/17/07
Re: NMO 4.2 windows x86 on Windows Server 2003 R2 EMT64

Posted: May 10, 2007 3:12 AM in response to: Hrvoje Crvelin Reply


Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\oracle>rman nocatalog

Recovery Manager: Release 10.2.0.3.0 - Production on Thu May 10 08:47:25
2007

Copyright (c) 1982, 2005, Oracle. All rights reserved.

RMAN> connect target /

connected to target database: THINFO (DBID=2072533893)
using target database control file instead of recovery catalog

RMAN> run {
2> allocate channel t1 type 'SBT_TAPE' parms
'ENV=(NSR_SERVER=192.168.0.100)';
3> release channel t1;
4> }

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of allocate command on t1 channel at 05/10/2007 08:48:17
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library

RMAN>





Hrvoje Crvelin


Posts: 4,332
From: Orchestra Service Gmbh
Registered: 11/21/05
Re: NMO 4.2 windows x86 on Windows Server 2003 R2 EMT64

Posted: May 10, 2007 3:57 AM in response to: luxz Reply


I know support has guide for this, but I can't check it out exactly what it was. See with support for workaround (as solution for fact is NMO5 which will be out in couple of months).



Do you have the support guide for this ? I am running into the same issue.

I also believe NMO was installed on the box before Oracle not sure troubleshooting the install.

Depending on OS, check if library has been relinked correctly first. If this is 64bit NW make sure you have patched NMO and correct version installed. I believe also that forthcominf version of NMO (4.5 in couple of weeks) will also addressed fully 64 bit Windows systems. Version you install depends on CPU type you have on the box.

The operating system is Windows 2003 Server 32 bit. So do i need to ununstall NMO and reinstall it to relink the libraries?

Btw, I just checked your RMAN script... Few things:
- have parms line in new line (you may wish to use send approach instead too as Oracle suggests that too)
- for server use hostname and make sure you can resolve (either DNS or hosts) IP of server (192.168.0.100)
- you are missing backup action which goes before releasing channel

You can find few RMAN script examples on this forum in case you are wondering what to do (or on Metalink).

Oh that was not my rman script just an example from the last thread, here is the one I am using:

connect Target /
run {
allocate channel chanel1 type 'sbt_tape'
parms 'ENV=(NSR_SERVER=servername.com, NSR_GROUP=backupgroup)'
format 'b_%u_%p_%c';
backup full
(database include current control file);
backup
(archive all delete input);
release channel channel1;
}

Yes... the version you need is x86 of module. After that go to cmd on client and execute rman script as Oracle user via rman cmdfile

Again NMO 4.2 was installed x86 version before Oracle was installed, so I need to uninstall it then reinstall it and then run RMAN again?

OK... here is more example in case you need it more and send version to.

Using parms:

connect target user/pass@SID;
 
run {
allocate channel t1 type 'SBT_TAPE'
parms 'ENV=(NSR_SERVER=, NSR_DATA_VOLUME_POOL=)';
backup full filesperset 4 database include current controlfile format 'ORCL:/FULL_DB_%d_%u/';
sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
change archivelog all validate;
backup full filesperset 5 archivelog all delete input skip inaccessible format 'ORCL:/FULL_ARC_%d_%u/';
release channel t1;
}

Using send

connect target user/pass@SID;
 
run {
allocate channel t1 type 'SBT_TAPE';
send channel t1 'NSR_ENV=(NSR_SERVER=, NSR_DATA_VOLUME_POOL=)';
backup full filesperset 4 database include current controlfile format 'ORCL:/FULL_DB_%d_%u/';
sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
backup full filesperset 5 archivelog all skip inaccessible format 'ORCL:/FULL_ARC_%d_%u/';
release channel t1;
}

I never used / for connect string as I remember having issues with that in the past even I do not think that could be your issue here. Nevertheless, you may wish to check it out too.

As usual you are always helpful much appreciated.