RMAN-20033 control file sequence# too low & ORA-00230
DBA2011Aug 17 2010 — edited Aug 17 2010The two RMAN errors shown below occur occasionally I believe the cause is If an archive backup runs during a database backup, the controlfile is backed up by both and may (but not always) result in these errors. The database backup is usually successful and it is just the controlfile backup that complains. I've considered how to avoid this, but it is not easy. Some of the large database backups, especially for a full backup, run for hours so archives still need to be backed up and removed.
This may have started when CONFIGURE CONTROLFILE AUTOBACKUP ON was implemented. I don't know if this can be changed for archive backups without affecting the full/cumu backups. Any ideas are appreciated.
Starting Control File and SPFILE Autobackup at 23-JUL-10
piece handle=c-3756288473-20100723-2e comment=API Version 2.0,MMS Version 5.4.1.0
Finished Control File and SPFILE Autobackup at 23-JUL-10
released channel: T1
released channel: T2
released channel: T3
released channel: T4
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03008: error while performing automatic resync of recovery catalog
RMAN-20033: control file sequence# too low
Starting backup at 06-AUG-10
channel T1: starting full datafile backupset
channel T1: specifying datafile(s) in backupset
released channel: T1
released channel: T2
released channel: T3
released channel: T4
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on T1 channel at 08/06/2010 11:43:52
ORA-00230: operation disallowed: snapshot control file enqueue unavailable