AW: rman problems
Date: Mon, 7 Dec 2009 11:38:31 +0100
Do you have a replica of one database running against the same catlog as the origin? I've seen the same behaviour once.
Might be that you have 2 DB's with the same id. Check if you have two databases with the same dbid: select DBID,name from v$database; unregister both and change the dbid for one with nid.
Von: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] Im Auftrag von Luka Grah Gesendet: Montag, 7. Dezember 2009 11:28 An: Oracle-L Freelists
Betreff: rman problems
I am having a problem with one of my database when doing backup.
We are using 2 jobs for backup
- one for ArchiveLogs
-one for database backup.
We are also using RMAN catalog on DB 22.214.171.124. The target database is 10.2.0.3. The database backup is done with split mirror copy and mounted on mount host. After that the controlfile is changed from current to backup and rman backup job is run.
The problem is that after the db backup job is done the archive job
RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of allocate command at 12/01/2009 09:38:26RMAN-03014: implicit resync of recovery catalog failed RMAN-03009: failure of partial resync command on default channel at 12/01/2009 09:38:26
RMAN-20033: control file sequence# too low
After a few resync catalog in rman the archive job start again. I tried registrer/unregister a few times but it doesn't help.
Do you have any ideas...????
http://www.freelists.org/webpage/oracle-l Received on Mon Dec 07 2009 - 04:38:31 CST