Databases
cancel
Showing results for 
Search instead for 
Did you mean: 

RMAN error after 8.1.6 to 9.2 conversion

Jon Mattatall
Esteemed Contributor

RMAN error after 8.1.6 to 9.2 conversion

Well, I'm stumped. And not a DBA.

We use OB 4.1 for RMAN backups of Oracle 8.1.6 and 9.2 instances. Platform for Cell Manager is HPUX11.00 / L2000 with 8.1.6 and 9.2 catalog instances, instances live on HPUX11.00 / K370 boxes.

After the DBA converted an instance to 9.2 from 8.1.6, I reconfigured the RMAN integration (which tests successful) to use the 9.2 catalog. I now get the following error.

Starting backup at 04/01/2004 [12:55:11]
current log archived
channel dev_0: starting archive log backupset
channel dev_0: specifying archive log(s) in backup set
input archive log thread=1 sequence=6603 recid=6525 stamp=522282524
channel dev_0: starting piece 1 at 04/01/2004 [12:55:16]
channel dev_1: starting archive log backupset
channel dev_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=6604 recid=6526 stamp=522285439
channel dev_1: starting piece 1 at 04/01/2004 [12:55:16]
channel dev_2: starting archive log backupset
channel dev_2: specifying archive log(s) in backup set
input archive log thread=1 sequence=6605 recid=6527 stamp=522288781
channel dev_2: starting piece 1 at 04/01/2004 [12:55:17]
channel dev_3: starting archive log backupset
channel dev_3: specifying archive log(s) in backup set
input archive log thread=1 sequence=6606 recid=6528 stamp=522294330
[Normal] From: OB2BAR@sv999373.nb.prv "xxxx" Time: 2004-04-01 12:55:17 PM
Starting OB2BAR Backup: 05 hostname:hostname_xxxx_HOT<522334516:1>.dbf // Oracle8

hostname:hostname_xxxx_HOT<522334516:1>.dbf // Oracle8

[Normal] From: OB2BAR@hostname "xxxx" Time: 2004-04-01 12:55:18 PM
Starting OB2BAR Backup: 05 hostname:hostname_xxxx_HOT<522334515:1>.dbf // Oracle8

[Normal] From: OB2BAR@sv999373.nb.prv "xxxx" Time: 2004-04-01 12:55:26 PM
Completed OB2BAR Backup: 05 hostname:hostname_xxxx_HOT<522334515:1>.dbf // Oracle8

[Normal] From: OB2BAR@sv999373.nb.prv "xxxx" Time: 2004-04-01 12:55:27 PM
Completed OB2BAR Backup: 05
hostname:hostname_xxxx_HOT<522334516:1>.dbf // Oracle8

[Normal] From: OB2BAR@hostname "xxxx" Time: 2004-04-01 12:55:27 PM
Completed OB2BAR Backup: 05 hostname:hostname_xxxx_HOT<522334516:1>.dbf // Oracle8

released channel: dev_0
released channel: dev_1
released channel: dev_2
released channel: dev_3
released channel: dev_4
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on dev_3 channel at 04/01/2004 12:55:17
ORA-19595: archivelog /u0306/oradata/xxxx/T0001S0000006606.ARC already included in backup conversation

RMAN> **end-of-file**

RMAN>

Recovery Manager complete.


I tried to issue a crosscheck, but.....

archive log filename=/u0306/oradata/xxxx/T0001S0000006604.ARC recid=6526 stamp=522285439
validation succeeded for archived log
archive log filename=/u0306/oradata/xxxx/T0001S0000006605.ARC recid=6527 stamp=522288781
validation succeeded for archived log
archive log filename=/u0306/oradata/xxxx/T0001S0000006606.ARC recid=6528 stamp=522294330
validation succeeded for archived log
archive log filename=/u0306/oradata/xxxx/T0001S0000006606.ARC recid=6528 stamp=522294330
validation succeeded for archived log
archive log filename=/u0306/oradata/xxxx/T0001S0000006607.ARC recid=6529 stamp=522315461
validation succeeded for archived log


As can be seen, the 6606 log shows up twice.
There is only one log by that name in the archivelog directory. I have even gone through with rm -i ./* to see if there was some strangeness there - nothing.

Anyone seen something like this?
A little knowledge is dangerous - none is absolutely terrifying!!!
3 REPLIES
Hoefnix
Honored Contributor

Re: RMAN error after 8.1.6 to 9.2 conversion

Hi,

Did you check if this ARC file allready existed in the RMAN database before the database was migrated from v8 to v9?
I don't know if its possible to edit this RMAN database to cleanup the double entry?

regards,

Peter
Jon Mattatall
Esteemed Contributor

Re: RMAN error after 8.1.6 to 9.2 conversion

No, the timestamp indicates today, and the instance was migrated yesterday.

There are currently logs 6603 to 6619 in the archive directory. First timestamp is ~11pm last night.

I'll check and see if I can get some feedback fom the DBA responsible for the RMAN catalogs.
A little knowledge is dangerous - none is absolutely terrifying!!!
Jon Mattatall
Esteemed Contributor

Re: RMAN error after 8.1.6 to 9.2 conversion

For reference, if nothing else....

Never did resolve the issue. Edited the archive backup script to include
"change archivelog all crosscheck;"
again, moved the offending log out of the directory, and re-ran the backup.

Success. Ran a hot backup when the next archive log was generated. It ran, and backed up/deleted the archive log no problem. I could no longer restore from that hot, but...

I got permission to run a cold backup last night so I'm covered again, but I have no idea why the same log was referenced twice.
A little knowledge is dangerous - none is absolutely terrifying!!!