We have an oracle RMAN LV0 backup policy configured for a database called TESTDB on SERVER1. The same SERVER1has lot of other DB's running which also has RMAN backup's configured.
Policy name: SERVER1-ORA-TESTDB-LV0-rmn3pen1
The issue is, when we manually trigger TESTDB LV0 backup or when it runs as per the schedule following things are noted:
1. Parent LV0 backup job of TESTDB takes the policy name as configured which is SERVER1-ORA-TESTDB-LV0-rmn3pen1.
2. When Default-Application starts to run, the policy name is taken as ARCHLOG policy name of some other database in the same server which is SERVER1-ORA-TESTDB2-ARCH-rmn3pen1.
3. Job runs successfully with correct RMAN piece name of LV0 backup for TESTDB and the bpimagelist for SERVER1 show something like this:
01/28/2010 07:06 02/28/2010 1 119426336 N User Backup SERVER1-ORA-TESTDB2-ARCH-rmn3pen1
01/28/2010 07:05 02/28/2010 0 0 N Full Backup SERVER1-ORA-TESTDB-LV0-rmn3pen1
4. In the other scenario when we kill the parent LV0 job of TESTDB the child job completes successfully. The LV0 piece is backed up in the child job.
5. In another scenario when the child job fails the parent job is completed successfully. Here no LV0 piece is backed up.
The LV0 policy is configured to run a RMAN script from policy backup selection. The RMAN script is a generic one for all the DB's present in SERVER1 i.e. it reads the netbackup policy name fields, greps the DB name and type , and then calls corresponding scripts for that DB name and type.
We had a discussion with our Oracle team and they say there is no problem with the RMAN script and don't know why it is picking some other policy name when TESTDB Default-Application is triggered.
Hence sharing this in forum to find why it is picking some other policy name when TESTDB Default-Application is triggered.
We have not yet tested restoring this LV0 backup.