Symantec Netbackup RMAN-03009 ORA-19513 ORA-27206

channel ch00: starting piece 1 at 29-DEC-11
RMAN-03009: failure of backup command on ch00 channel at 12/29/2011 12:51:07
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 ch01 channel at 12/29/2011 12:51:07
ORA-19513: failed to identify sequential file
ORA-27206: requested file not found in media management catalog

RMAN> RMAN>

Recovery Manager complete.

Script /usr/openv/netbackup/ext/db_ext/oracle/rman/hot_database_backup.sh
==== ended in error on Thu Dec 29 12:51:07 PHT 2011 ====

Backup images are created in Netbackup staging area, and it appears that the DB was backed up. However listing the backup from RMAN console produces no output.

$rman target /
RMAN> list backup summary;

The problem is usally NetBackup cannot write it’s logging files. The most dangerous thing I found from this was that the NetBackup console was showing the backup completed but the RMAN catalog, due the error, dropped all references to the backup. So you could lose sync between your catalog ( or controlfile ) and NetBackup catalog.

Server specs:

NetBackup 7.0
RMAN ( RDBMS). 11.1.0.7
Oracle Ent Linux 5.6

Three things to check:

1. Check the NBU library is linked to the Oracle binary

2. Check the CLIENT_NAME in the bp.conf (client system) is identical to the client name in the NBU Policy

3. You may also need to ensure the logging directories are accessible to the oracle software owner/user:

chown -R oraprod:dba /usr/openv/netbackup/logs/user_ops/dbext
chmod -R 755 /usr/openv/netbackup/logs/user_ops/dbext
mkdir /usr/openv/netbackup/logs/user_ops/dbext/jobs
chown oraprode:dba /usr/openv/netbackup/logs/user_ops/dbext/jobs
chmod 755 /usr/openv/netbackup/logs/user_ops/dbext/jobs

One way to discover the answer is get the NBU admin to put level 5 logging and create the bpcd logging directory in place to get the
runtime logs ( mkdir /usr/openv/netbackup/logs/bpcd ).  Run the job, the bpcd log will show something about unable to write to a
logs or jobs directory as the backup jobs starts. This seems  to throw RMAN off  and causes the jobs to blow out, leaving the RMAN and NBU catalogs out of sync.

refs:
http://www.symantec.com/connect/forums/netbackup-and-oracle-agent

About these ads

About this entry