08-28-2009 12:14 PM
08-28-2009 12:16 PM
08-28-2009 12:17 PM
08-28-2009 12:22 PM
08-28-2009 12:29 PM
08-28-2009 12:34 PM
08-28-2009 12:48 PM
08-28-2009 01:34 PM
08-28-2009 01:55 PM
08-29-2009 02:11 PM
if the RMAN Script has sufficient persmissions and you have sufficient rights to initiate the RMAN script itself from its original location at the database server, you may try to initiate the script at once which will result in initiating the RMAN hot backup in Netbackup if everything has been set properly that is
NB_ORA_Class = <policy name>
NB_ORA_SERV = <Netbackup Master server hostname>
NB_ORA_Client = <Hostname of the Database server configured with the backup policy (Vrtual hostname if the db is hosted in cluster) >
This will gernerate an output and the recovery manager log file in the '/*****/rman/log/' directory with *.out extention. and point you to the actual reson of failure under the following header...
=======================================
ERROR MESSAGE STACK FOLLOWS
==================================
error code 6 is a general error which just alert us regarding the failure of the RMAN script and not the actuall reson of the failure.
some of the General reasons for the are rman script failure are.
1. NB_ORA_Class Specified wrong at the client end and in the RMAN Script
2. NB_ORA_SERV Specified wrong at the client end and in the RMAN Script
3. NB_ORA_Client Specified wrong at the client end and in the RMAN Script
4. not enough permissions to the RMAN script
5. Script location Specified wrong in the Netbackup policy
6. communication error between the Netbackup Master or Media server and the client host
7. The Netbackup Oracle agent is not installed or not at the same version as the Netbackup server, it should be on the same version / patch level.
8. Not enough channels provided in the RMAN Script, increasing the channel allocation may help reolving the failure.
9. account for the oracle user has locked, password has changed or the script is not attemting to su to oracle user prior.
10. Currupt data encounter during the RMAN database backup and need to take care of it by DBA prior to re-initiate the RMAN backup.
hope this will help.