bphdb exit status = 6: the backup failed to back up the requested files

Assuming these scripts were built from the netbackup samples then theres should be output files created in C:\Program Files\Veritas\NetBackup\scripts\. One with err and one with out. Check them to see the error faced by RMAN.

Hello Riaan,

no file is Created @ C:\Program Files\Veritas\NetBackup\scripts\.

please suggest..??

Then you would need to look inside the script to see where the log location is. Usually its the same folder as where the script is located. Unless someone specified some other location.

You can also try and run the script from CLI, see what it says.
 

Status 6 is a generic error saying that the rman script has failed.

The first log to check is the output file created by the rman script.

Please check the script on the client:
"C:\Program Files\Veritas\NetBackup\scripts\hot_database_backup_hypp.cmd"
to see where the output file is written. 
Based on the error(s) we see in rman output/log file, we may need NBU logs as well.
Please confirm that all of these log folders exist on the client:
bpcd dbclient bphdb
 

Have you confirmed that NBU Client Service is started as a user with Oracle db rights as well as local Admin rights?
 

Hello Marianne,

sorry for late rply..

actual error is that the Rman Backup is failing with below error..even oracle admin is not able to take Rman Backup.

We are getting below error

==== started on Mon 06/09/2014  05:10 ====

Script name: "C:\Program Files\Veritas\NetBackup\scripts\hot_database_backup_hypdb.cmd"

#                                      

  RMAN  :  c:\oracle\ora92\bin\rman.exe                      

  NLS_LANG  :  american              

  ORACLE_HOME  :  c:\oracle\ora92        

  ORACLE_SID  :  HYPDB          

  NLS_DATE_FORMAT  :  YYYY-MM-DD:hh24:mi:ss

  RMAN_LOG_FILE  :  "C:\Program Files\Veritas\NetBackup\scripts\hot_database_backup_hypdb.out"     

  NB_ORA_SERV  :  wdcbkupmstr                    

  NB_ORA_FULL  :  1                    

  NB_ORA_INCR  :  0                    

  NB_ORA_CINC  :  0                    

Recovery Manager: Release 9.2.0.5.0 - Production

Copyright (c) 1995, 2002, Oracle Corporation.  All rights reserved.

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-00554: initialization of internal recovery manager package failed

RMAN-04005: error from target database:

ORA-01031: insufficient privileges

Hello Marianne,

sorry for late rply actully the Oracle admin is unable to take Rman Backup.. and the script is failing with below error..

We are getting below error

==== started on Mon 06/09/2014  05:10 ====

Script name: "C:\Program Files\Veritas\NetBackup\scripts\hot_database_backup_hypdb.cmd"

#                                      

  RMAN  :  c:\oracle\ora92\bin\rman.exe                      

  NLS_LANG  :  american              

  ORACLE_HOME  :  c:\oracle\ora92        

  ORACLE_SID  :  HYPDB          

  NLS_DATE_FORMAT  :  YYYY-MM-DD:hh24:mi:ss

  RMAN_LOG_FILE  :  "C:\Program Files\Veritas\NetBackup\scripts\hot_database_backup_hypdb.out"     

  NB_ORA_SERV  :  wdcbkupmstr                    

  NB_ORA_FULL  :  1                    

  NB_ORA_INCR  :  0                    

  NB_ORA_CINC  :  0                    

Recovery Manager: Release 9.2.0.5.0 - Production

Copyright (c) 1995, 2002, Oracle Corporation.  All rights reserved.

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-00554: initialization of internal recovery manager package failed

RMAN-04005: error from target database:

ORA-01031: insufficient privileges

This technote agrees with Marianne:

http://www.symantec.com/business/support/index?page=content&id=TECH136157

If the backup shows an ORA-01031: insufficient privileges error message, check the account being used for backups for sysdba rights.