Oracle RMAN 'prepare run' ended in error

Question

Hello,

we backup our SAP Oracle DB´s with br*tools usinf rman together with the NMO.

This works generally fine.

Now, I tried to run the brbackup with device_type = rman_prep & saveset_members = 4 to optimize the backup procedure.

All other parameters are the same as for the working backups.

The preparation run aborted:

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on sbt channel at 12/23/2009 09:36:35
ORA-19506: failed to create sequential file, name="becerfog.45", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
lnm_index_cfx_connect retry failed. See privious error messages. (3:3:0)

It seems that the problem is caused by the NMO.

Any ideas, what caused this problem and if this is supported by the NMO generally?

Thanks.

regards

Michael

ble1 · Answer

Do you get anything in sbt log?

sharpeitc · Answer

I didn´t found any sbt.log file. What do you mean? In \applogs
mo.messages.raw I found the following: lnm_index_cfx_connect retry failed.  See privious error messages. 0 But 'previous messages' aren´t registered within the log... regard Michael

h9G1B64TG712206 · Answer

I met the similar problem.I correct the hostname and make it same with the /etc/hosts. And it does work.

sharpeitc · Answer

/etc/hosts isn´t used on this server. What do you mean with 'correct the hostname' and in which configuration exactly?

sharpeitc · Answer

What do you mean with 'UTL file'? Where I can find it? (I´m not a Oracle spcialist...)

mofo · Answer

Is this first RMAN usage that you wanted to test with "device_type = rman_prep" ?

Usually the error message that you got is associated with problems in identification of the NetWorker client on the NetWorker server - hence the questions and comments about the hostname and hosts entries, I guess.

Would this SAP be a cluster system of some sort?

mofo · Answer

Well the only place that should have any impact on the name of the client in this situation is the "client" parameter in the UTL file. You've checked that already, and its properly set?

Have you additionally checked other logs - especially NetWorkers "daemon.raw", and anything that might pop out in the "applogs" folder on the client? Is the client otherwise in the regular backup regime?

sharpeitc · Answer

It´s the first test with device_type = rman_prep.

The backup is already working with device_type = rman_stage without problems.

The SAP & the NW server are not a cluster server (both "normal" Windows Server 2003).

mofo · Answer

actually, you got me a bit puzzled now.If you are using 'pure' NetWorker Module for Oracle, then it shouldn't really be important which backup_dev_type you have configured - execution follows on purely Oracle level and has no importance what is stated in your 'init.SAP' file.If you are using NetWorker Module for SAP on Oracle (either 'proper', or the 'RMAN' version), backup is controlled by BR*TOOLS - and then all of the SAP configuration files (init*.sap, init*.utl und NetWorker's nsrsapsv.cfg) are valid and used for a backup configuration - including options for rman_prep and rman_stage.I assume your client is configured with backint: in the saveset field? If so, then the UTL file which is used for backup purposes is mentioned in the first few lines of the CFG file which is given as argument to the 'Backup Command' field of the 'nsrsapsv' command, in the NetWorker configuration. Sorry for the complicated explanation, but that's where it's at .

mofo · Answer

Have you tried explicitly stating NSR_CLIENT= as a parameter together with the other parameters you are 'sending' to RMAN (at 'rman_send')?

sharpeitc · Answer

Sorry, we are using the 'pure' NW Oracle module, but using br*tools together with rman to create the backups etc.. The NW Module for SAP with backint isn´t used. The needed parameter for the NMO are set within init .sap file with 'rman_sen=...' Perhaps rman_prep isn´t support on this way...

NetWorker

Oracle RMAN "prepare run" ended in error

Was this post helpful?