GENERAL ERROR: ORA-27206 (RMAN-10035) error when performing backups from a Windows NetBackup Oracle agent to a UNIX master.

Article:TECH23371  |  Created: 2002-01-18  |  Updated: 2013-10-23  |  Article URL http://www.symantec.com/docs/TECH23371
Article Type
Technical Solution

Product(s)

Environment

Issue



GENERAL ERROR: ORA-27206 (RMAN-10035) error when performing backups from a Windows NetBackup Oracle agent to a UNIX master.

Error



RMAN-10035: exception raised in RPC: ORA-27206: requested file not found in media management catalog

Solution



Overview:
ORA-27206 (RMAN-10035) error when performing backups from a Windows NetBackup Oracle agent to a UNIX master.

Troubleshooting:
Enable the bphdb log file on the Oracle server, and review it as well as the Oracle Recover Manager (RMAN) output file.

Log Files:
The bphdb log file shows:
<16> bphdb.CreateProcessForNT: ERR - command failed: the requested operation was partially successful (1)
<4> bphdb Exit: INF - EXIT STATUS 1: the requested operation was partially successful

The Oracle RMAN output file shows:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00579: the following error occurred at 12/12/2002 16:50:48
RMAN-03006: non-retryable error occurred during execution of command: backup
RMAN-12004: unhandled exception during command execution on channel ch00
RMAN-10035: exception raised in RPC: ORA-27206: requested file not found in media management catalog
RMAN-10031: ORA-19583 occurred during call to DBMS_BACKUP_RESTORE.BACKUPPIECECREATE

Resolution:
The dbclient log file on the Oracle server shows that the client and the server exit with status 0 after backing up the data files in the first backup piece. But when the RMAN verification queries for the image using the lower case name no images are found.  Check the policy, backup script, and client configuration for client name case inconsistencies.   If the backup script and client configuration use the client name in lower case, but the class configuration is using upper case,  this causes the backup to be saved under the upper case name (as listed in the policy).  When the master is UNIX, the case of the client name must be consistent throughout.  Either always use upper case or always use lower case.


Legacy ID



252934


Article URL http://www.symantec.com/docs/TECH23371


Terms of use for this information are found in Legal Notices