Back up Oracle with Netback reports ora-27206 error handling, netbackora-27206

Back up Oracle with Netback reports ora-27206 error handling, netbackora-27206

Today, my colleague encountered a problem with database backup. The error message is as follows:

channel ch01: starting piece 1 at 2015-01-12:22:06:56RMAN-03009: failure of backup command on ch01 channel at 01/12/2015 22:11:51ORA-19513: failed to identify sequential fileORA-27206: requested file not found in media management catalogcontinuing other job steps, job failed will not be re-runchannel ch01: starting incremental level 0 datafile backup setchannel ch01: specifying datafile(s) in backup setincluding current control file in backup setchannel ch01: starting piece 1 at 2015-01-12:22:11:52RMAN-03009: failure of backup command on ch01 channel at 01/12/2015 22:12:27ORA-19513: failed to identify sequential fileORA-27206: requested file not found in media management catalogcontinuing other job steps, job failed will not be re-runchannel ch01: starting incremental level 0 datafile backup setchannel ch01: specifying datafile(s) in backup setincluding current SPFILE in backup setchannel ch01: starting piece 1 at 2015-01-12:22:12:27RMAN-03009: failure of backup command on ch01 channel at 01/12/2015 22:12:52ORA-19513: failed to identify sequential fileORA-27206: requested file not found in media management catalogcontinuing other job steps, job failed will not be re-runreleased channel: ch00released channel: ch01RMAN-00571: ===========================================================RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============RMAN-00571: ===========================================================RMAN-03009: failure of backup command on ch00 channel at 01/12/2015 23:23:57ORA-19513: failed to identify sequential fileORA-27206: requested file not found in media management catalog

The online query information is as follows:

View mos and find that [ID 558993.1] provides error causes and solutions
Cause of error: RMAN backup to tape using veritas netbackup, The MML parameters like NB_ORA_CLIENT and NB_ORA_SERV were not given in proper case while loading channel in RMAN backup.
Solution: The NB_ORA_CLIENT and NB_ORA_SERV MML parameters are case sensitive. So make sure to give these parameters in same case while allocating or inserting ing RMAN channel as it is configure in Veritas server.

Check the server configuration. The host name is incorrectly configured. First, the case is not properly matched, and second, the number 0 in the host name is written as the letter o. Check the backup result. Everything is normal.

Use the target database control file to replace the channel for restoring directory allocation: c1 channel c1: SID = 601 device type = SBT_TAPE channel c1: Veritas NetBackup for Oracle-Release 7.1 (20110203) start backup at-15 channel c1: starting all data file backup sets channel c1: the data file backup set in the specified backup set contains the current control file channel c1: starting channel c1 from month 1 to month 15: Completed segment 1 to month 15 handle = 1hpskim5_1_1 mark = TAG20150113T155029 comment = API Version 2.0, MMS Version 5.0.0.0 channel c1: the backup set has been completed. After the time: 00: 00: 26, the channel for the backup to be released from month-1 to month-15 is c1.