Using Netback to back up Oracle Reports ORA-27206 error handling
Using Netback to back up Oracle Reports ORA-27206 error handling
Today, my colleague encountered a problem with Oracle database backup. The error message is as follows:
Channel ch01: starting piece 1 at 2015-01-12: 22: 06: 56
RMAN-03009: failure of backup command on ch01 channel at 01/12/2015 22:11:51
ORA-19513: failed to identify sequential file
ORA-27206: requested file not found in media management catalog
Continuing other job steps, job failed will not be re-run
Channel ch01: starting incremental level 0 datafile backup set
Channel ch01: specifying datafile (s) in backup set
Including current control file in backup set
Channel ch01: starting piece 1 at 2015-01-12: 22: 11: 52
RMAN-03009: failure of backup command on ch01 channel at 01/12/2015 22:12:27
ORA-19513: failed to identify sequential file
ORA-27206: requested file not found in media management catalog
Continuing other job steps, job failed will not be re-run
Channel ch01: starting incremental level 0 datafile backup set
Channel ch01: specifying datafile (s) in backup set
Including current SPFILE in backup set
Channel ch01: starting piece 1 at 2015-01-12: 22: 12: 27
RMAN-03009: failure of backup command on ch01 channel at 01/12/2015 22:12:52
ORA-19513: failed to identify sequential file
ORA-27206: requested file not found in media management catalog
Continuing other job steps, job failed will not be re-run
Released channel: ch00
Released channel: ch01
RMAN-00571: ========================================================== ==============================
RMAN-00569: ==================== error message stack follows ==========================
RMAN-00571: ========================================================== ==============================
RMAN-03009: failure of backup command on ch00 channel at 01/12/2015 23:23:57
ORA-19513: failed to identify sequential file
ORA-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. Change, and observe the backup results. Everything is normal.
Use the target database control file to replace the recovery directory
Allocated channel: c1
Channel c1: SID = 601 device type = SBT_TAPE
Channel c1: Veritas NetBackup for Oracle-Release 7.1 (20110203)
Start backup from month 1 to month 15
Channel c1: starting all data file backup Sets
Channel c1: data files in the specified backup set
The backup set contains the current control file.
Channel c1: Starting from month 1 to month 15
Channel c1: Completed from month 1 to month 15
Segment handle = 1hpskim5_1_1 mark = TAG20150113T155029 comment = API Version 2.0, MMS Version 5.0
. 0.0
Channel c1: Backup set completed. elapsed time: 00: 00: 26
Backup completed from month 1 to month 15
Released channel: c1