-- Backup Issue encountered after DB failover --

By Raja Ankathi

We encountered the backup issue on  db. As per the metalink note 566635.1, there is an bug in 10.2. and it is fixed in 11.2

==================

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.2.0 This problem can occur on any platform.

Symptoms

Resync of the catalog for the Primary database fails with:

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03009: failure of resync command on default channel at 05/06/2008

10:29:09

ORA-00001: unique constraint (RMAN.TF_P) violated Cause You are hitting bug 6653570

The root cause scenario in the bug is:

1) a primary and standby is created

2) on primary customer added a tempfile. This doesn't get created on standby.

    It gets resynced to recovery catalog

3) Then when switchover happens, they add the tempfile on new primary and

    resync it to recovery catalog. This resync marks the tempfile on primary (at

    step 2) as dropped.

4) Then when the switchover happens again, the temp file that was dropped is

    again resynced which is causing the problem.

Solution

Bug 6653570 is fixed in Oracle Database version 11.2

Please check metalink if the patch is available for your platform and version. If not and a one off is required, please contact Oracle support

The workaround for this issue is to recreate the temporary tablespace on the primary database.