Re: RMAN
From: Mark D Powell <Mark.Powell2_at_hp.com>
Date: Tue, 24 Jan 2012 10:00:06 -0800 (PST)
Message-ID: <7be6e42f-05e9-4fda-980c-fec2be920bf9_at_f12g2000yqo.googlegroups.com>
On Jan 20, 7:58 pm, joel garry <joel-ga..._at_home.com> wrote:
> On Jan 20, 8:38 am, ExecMan <artme..._at_yahoo.com> wrote:
>
>
>
>
>
> > Hi,
>
> > On Monday we started receiving this error in our backup log:
>
> > RMAN-00571:
> > ===========================================================
> > RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS
> > ===============
> > RMAN-00571:
> > ===========================================================
> > RMAN-03009: failure of delete command on d4 channel at 01/20/2012
> > 02:31:24
> > ORA-19633: control file record 6197 is out of sync with recovery
> > catalog
>
> > We do not use a recovery catalog, we use the control file. Oracle
> > has been less than helpful, telling us that the only way to solve this
> > bug is to use a recovery catalog. I find that funny as we have 20
> > databases, each using their control file, and this is the first time
> > it has ever happened.
>
> > At any rate, I cannot find a solution. Can anyone help? I'm also
> > thinking if I can just delete all the backups, will it clear those
> > records from the control file, and I can start with a fresh level 0
> > backup.
>
> > Thanks!
>
> See MOS Bug 6402384: ORA-19633: CONTROL FILE RECORD 765 IS OUT OF SYNC
> WITH RECOVERY CATALOG
> "Delete and recreate the controlfile which the customer does not want
> to do"
> It appears the controlfile records for backup pieces are reused before
> those of backup sets, allowing duplicate set names.
> I notice this is fixed in 10.2.0.5 and 11.1.0.7 patch sets.
> What a choice: create a catalog, which would let you fix the
> controlfile records through syncronization or re-create the
> controlfile, with incarnation issues. Anything else would be scarier.
>
> jg
> --
> _at_home.com is bogus.http://www.extremetech.com/computing/114803-megauploads-demise-what-h...- Hide quoted text -
>
> - Show quoted text -
Date: Tue, 24 Jan 2012 10:00:06 -0800 (PST)
Message-ID: <7be6e42f-05e9-4fda-980c-fec2be920bf9_at_f12g2000yqo.googlegroups.com>
On Jan 20, 7:58 pm, joel garry <joel-ga..._at_home.com> wrote:
> On Jan 20, 8:38 am, ExecMan <artme..._at_yahoo.com> wrote:
>
>
>
>
>
> > Hi,
>
> > On Monday we started receiving this error in our backup log:
>
> > RMAN-00571:
> > ===========================================================
> > RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS
> > ===============
> > RMAN-00571:
> > ===========================================================
> > RMAN-03009: failure of delete command on d4 channel at 01/20/2012
> > 02:31:24
> > ORA-19633: control file record 6197 is out of sync with recovery
> > catalog
>
> > We do not use a recovery catalog, we use the control file. Oracle
> > has been less than helpful, telling us that the only way to solve this
> > bug is to use a recovery catalog. I find that funny as we have 20
> > databases, each using their control file, and this is the first time
> > it has ever happened.
>
> > At any rate, I cannot find a solution. Can anyone help? I'm also
> > thinking if I can just delete all the backups, will it clear those
> > records from the control file, and I can start with a fresh level 0
> > backup.
>
> > Thanks!
>
> See MOS Bug 6402384: ORA-19633: CONTROL FILE RECORD 765 IS OUT OF SYNC
> WITH RECOVERY CATALOG
> "Delete and recreate the controlfile which the customer does not want
> to do"
> It appears the controlfile records for backup pieces are reused before
> those of backup sets, allowing duplicate set names.
> I notice this is fixed in 10.2.0.5 and 11.1.0.7 patch sets.
> What a choice: create a catalog, which would let you fix the
> controlfile records through syncronization or re-create the
> controlfile, with incarnation issues. Anything else would be scarier.
>
> jg
> --
> _at_home.com is bogus.http://www.extremetech.com/computing/114803-megauploads-demise-what-h...- Hide quoted text -
>
> - Show quoted text -
When I searched Oracle support for the bug number I found 3 patches for this issue. I did not look into the patch details, but a potential fix may be available depending on which specific versions/ platforms the patches were for.
HTH -- Mark D Powell -- Received on Tue Jan 24 2012 - 12:00:06 CST