the backup failed to back up the requested files

Please list all relevant info:

NBU version on Client and Server
OS on Server and client
Oracle version

Steps performed on server and client before backup was attempted.

Status 6 normally means a failure on the Oracle side.

Create dbclient log folder on the client and post dbclient log as well as RMAN output after next failure.

If Unix client, remember to 'chmod 777 dbclient'.

NBU version 7.1 on Server

NBU version 7.1 on Client

OS is Linux Redhat 5.2 64bit on Server and Client

Oracle version is : Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production

Your DBA needs to review RMAN .out  file for details on the Oracle side

How can i redirect RMAN .out to dbclient log ?

RMAN is Oracle and dbclient is NetBackup.  Best to keep things simple & separate IMO. 

Please haw can do this "post dbclient log as well as RMAN output"

Thanks

Please download this manual: NBU for Oracle Admin Guide for UNIX, Windows, and Linux  http://www.symantec.com/docs/DOC3672

Start by going through the initial linking and configuration steps and see if all the nessary steps were followed in your environment.

The manual also covers the RMAN backup scripts. You Oracle DBA should've created his own script(s)or modified the NBU samples. (The manual will tell you where these sample scripts are located).

The RMAN script will send it's output to a file. This should be hard-coded in the script. We are looking for this file (RMAN output).

From NBU point of view, the dbclient log will be needed. The Troubleshooting section of this manual explains this.

Create the dbclient folder under /usr/openv/netbackup/logs, followed by 'chmod 777 dbclient' so that the oracle user can write to the folder.

Error Message continued

<4> bphdb: INF - EXIT STATUS 6: the backup failed to back up the requested files

<16> bphdb: ERR - Script exited with status = 29

Please note

/usr/openv/nebackup/ext/scripts/ORACLEBACK_SCRIPT_NAME.sh in the exact error message is the default where NetBackup puts the.sh file, this may not be the exact place the script will be located, check with the System Administrator/DBA of the Server.

ORACLEBACK_SCRIPT_NAME.sh is a sample name, the actual script name will be dependent upon Administrator/DBA in charge.


bphdb shows "file not found" message.
Check permissions on the script to ensure they are "owner oracle group dba   rwxr-xr-x"
Note:
This has been seen on Solaris platforms but may apply to other UNIX platforms too.
The Exit status in Job Monitor fails with a Status 6, however, the ACTUAL exit code for the bphdb process is Status 29 which actually provides the pointer to what is wrong (e.g. "Failed trying to exec a command").  Changing the permissions on the script then enables the command to execute, therefore avoids the resulting Status 6: Failed to backup requested files, which is the final exit code that will be seen if the permissions on the script are incorrect.

• INF - Begin progress logging for process: (14892)
• INF - Using policy Oracle_policy to perform a user directed Oracle Stream Based backup.
• INF - Starting Oracle Recovery Manager.
• INF - Using: /oracle/ora10gR2/bin/rman
• INF - Connection info: target 'sys/*****' nocatalog
• INF - Start of Recovery Manager input.
• INF - # -----------------------------------------------------------------
• INF - # RMAN command section
• INF - # -----------------------------------------------------------------
• INF - RUN {
• INF - ALLOCATE CHANNEL ch00
• INF - TYPE 'SBT_TAPE';
• INF - SEND 'NB_ORA_CLIENT=prod.oracle.imist.ma,NB_ORA_SID=unic,NB_ORA_POLICY=Oracle_policy,NB_ORA_SERV=netbackup.imist.ma,NB_ORA_SCHED=Default-Application-Backup';
• INF - BACKUP
• INF - INCREMENTAL LEVEL=0
• INF - FORMAT 'bk_u%u_s%s_p%p_t%t'
• INF - DATABASE;
• INF - RELEASE CHANNEL ch00;
• INF - # Backup Archived Logs
• INF - sql 'alter system archive log current';
• INF - ALLOCATE CHANNEL ch00
• INF - TYPE 'SBT_TAPE';
• INF - SEND 'NB_ORA_CLIENT=prod.oracle.imist.ma,NB_ORA_SID=unic,NB_ORA_POLICY=Oracle_policy,NB_ORA_SERV=netbackup.imist.ma,NB_ORA_SCHED=Default-Application-Backup';
• INF - BACKUP
• INF - FORMAT 'arch_u%u_s%s_p%p_t%t'
• INF - ARCHIVELOG
• INF - ALL
• INF - DELETE INPUT;
• INF - RELEASE CHANNEL ch00;
• INF - # Control file backup
• INF - ALLOCATE CHANNEL ch00
• INF - TYPE 'SBT_TAPE';
• INF - SEND 'NB_ORA_CLIENT=prod.oracle.imist.ma,NB_ORA_SID=unic,NB_ORA_POLICY=Oracle_policy,NB_ORA_SERV=netbackup.imist.ma,NB_ORA_SCHED=Default-Application-Backup';
• INF - BACKUP
• INF - FORMAT 'ctrl_u%u_s%s_p%p_t%t'
• INF - CURRENT CONTROLFILE;
• INF - RELEASE CHANNEL ch00;
• INF - }
• INF - End of Recovery Manager input.
• INF - Start of Recovery Manager output.
• INF - Recovery Manager: Release 10.2.0.3.0 - Production on Mon Oct 31 10:37:37 2011
• INF - connected to target database: UNIC (DBID=3826637397, not open)
• INF - using target database control file instead of recovery catalog
• INF - RMAN-00571: ===========================================================
• INF - RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
• INF - RMAN-00571: ===========================================================
• INF - RMAN-03009: failure of allocate command on ch00 channel at 10/31/2011 10:37:39
• INF - ORA-19554: error allocating device, device type: SBT_TAPE, device name:
• INF - ORA-27211: Failed to load Media Management Library
• INF - Additional information: 9
• INF - Recovery Manager complete.
• INF - End of Recovery Manager output.
• INF - End Oracle Recovery Manager.

• NF - ORA-19554: error allocating device, device type: SBT_TAPE, device name:
• INF - ORA-27211: Failed to load Media Management Library

Did you run oracle_link as per the steps in the manual?