10/30/13

Document 357759.1

Known RMAN - Dataguard Problems (Doc ID 357759.1)

Modified: Sep 20, 2012

Type: BULLETIN

In this Document
Purpose
Scope
Details
References
This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

APPLIES TO:
Oracle Server - Enterprise Edition - Version 9.2.0.1 to 11.2.0.3 [Release 9.2 to 11.2]
Information in this document applies to any platform.

PURPOSE
Give an overview of known problems with RMAN Backups and Restores
in an Dataguard Environment

SCOPE
This document is intended for DBA's who are facing issues during the backup or restore
via RMAN in a database environement which uses Dataguard..
Its intention is to give an overview of the known issues with RMAN and Dataguard
and not to give any diagnosis. The diagnosis and investigation is handled more in
depth in other documents as referenced at the bottom of this document.

DETAILS
Bug:12357315

RMAN DELETE OBSOLETE WITH ORACLE STREAMS

Version affected :

Oracle11g

Version fixed :

Oracle12C, 11.2.0.4

Diagnosis :

Archives get deleted on the primary even when DELETION POLICY TO APPLIED ON STANDBY.

Workaround :

None

Bug:6216036

RMAN+DG ARCHIVELOG DELETION POLICY APPLIED ON STANDBY NOT RESPECTED

Version affected
:

Oracle10g

Version fixed :

Oracle11G

Diagnosis :

Archives get deleted on the primary even when DELETION POLICY TO APPLIED ON STANDBY, as this setting
only applies for the Flash Recovery Area and NOT for RMAN

Workaround :

None

Bug:2802688

DUPLICATE FILE NAMES DELETED WITHOUT CHECKING STANDBY/PRIMARY FLAG

Version affected :

Oracle8.1, Oracle9i

Version fixed :

Oracle10G

Diagnosis :

Mutliple LOG_ARCHIVE_DEST_n (on PRIMARY and / or STANDBY) with the same LOCATION

Workaround :
Bug:2675757

Use different LOG_ARCHIVE_DEST or LOG_ARCHIVE_FORMAT per instance

See the White papers below for initial setup informati

RMAN DID NOT BACKUP ARCHIVELOGS THAT WERE GENERATED DURING SWITCHOVER TO STANDBY http://www.oracle.com/technetwork/database/features/av

Version affected : Oracle 10G Release1

Version fixed :

Oracel 10G Release 2

Diagnosis :

Following a gracefull failover to a standby database and then back

to the original database RMAN cannot identify the archivelogs that
have been generated by the standby database.

Reference :

Alert NOTE:360241.1 RMAN Did Not Backup Archivelogs That Were Generated During
Switchover to Standby

Bug:4755799

RMAN-20070 ERROR ON PRIMARY AFTER DATAGUARD SWITCHOVER

Version affected :

Oracle9i, 10g Release 1, 10g Release 2

Version fixed :

Oracle 11g, with backports to 9208, 10.2.0.3

Diagnosis :

RMAN-20070 occurs on Primary after switchover of Standby to Primary site.

Unable to perform database backups, crosscheck archivelog all fails with the
same error.

Bug:3861505

RMAN DOES NOT RESYNC ARCHIVELOGS PRODUCED BEFORE SWITCHOVER

Version affected :

<= 9.2.0.6, <= 10.1.0.4

Version fixed :

9.2.0.7 10.1.0.5 10.2.0.1

Diagnosis :

RMAN does not resync archivelogs produced before switchover

Workaround :

None

Internal Bug:3633269

Standby Database, Missing Archivelogs When In Catalog Mode

Version affected :

10G Release 1 and Release 2

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=11i0u51b2j_1192&id=357759.1

REFERENCES
BUG:12357315 - RMAN DELETE OBSOLETE WITH
ORACLE STREAMS
BUG:2675757 - RMAN DID NOT BACKUP ARCHIVELOGS
THAT WERE GENERATED DURING SWITCHOVER TO
STANDBY
BUG:2802688 - DUPLICATE FILE NAMES DELETED
WITHOUT CHECKING STANDBY/PRIMARY FLAG
@ BUG:3633269 - STANDBY DATABASE, CROSSCHECK
AND DELETE NOT WORKING AS EXPECTED
BUG:3861505 - RMAN DOES NOT RESYNC
ARCHIVELOGS PRODUCED BEFORE SWITCHOVER
@ BUG:4214635 - BACKUP ARCHIVELOG BACKS LOGS
THAT MATCH ROLE IN CATALOG MODE
BUG:4755799 - S2P1: RMAN-20070 ERROR ON
PRIMARY AFTER DATAGUARD SWITCHOVER
BUG:4755799 - S2P1: RMAN-20070 ERROR ON
PRIMARY AFTER DATAGUARD SWITCHOVER
BUG:4919478 - ARCHIVE DEST FULL
''WARNING:ARCHIVE LOG NOT DELETED, NOT YET
APPLIED''
BUG:4919478 - ARCHIVE DEST FULL
''WARNING:ARCHIVE LOG NOT DELETED, NOT YET
APPLIED''
BUG:6216036 - RMAN+DG ARCHIVELOG DELETION
POLICY APPLIED ON STANDBY NOT RESPECTED
BUG:8468117 - CONSIDER A "DEFERRED" DESTINATION

1/2

10/30/13

Document 357759.1

Version fixed :

Oracle 11g

Diagnosis :

RMAN-20240: archived log not found in the recovery catalog

Workaround :

Run crosscheck and delete expired by using the controlfile rather than the catalog

Reference:

Note:280926.1 RMAN-06059 Error During Backup Archivelog Of Standby (Dataguard) Db

Internal Bug:4214635

BACKUP ARCHIVELOG BACKS LOGS THAT MATCH ROLE IN CATALOG MODE

Version affected :

<= 10.1.0.4

Version fixed :

10.1.0.5 and 10G Release 2

Diagnosis :

RMAN does not backup logs recieved on standby after conversion to primary,
unless these logs are explicitly cataloged.

Workaround:

AS STILL VIABLE
NOTE:280926.1 - RMAN-06059 Error During Backup
Archivelog Of Standby (Dataguard) Db
NOTE:360241.1 - RMAN Did Not Backup Archivelogs
That Were Generated During Switchover to Standby

Explicit catalog the archived redologs

Bug:4919478

Archive Dest Full ''Warning:Archive Log Not Deleted, Not Yet Applied''

Version affected :

<= 9.2.0.7, <= 10.1.0.4

Version fixed :

9.2.0.8, 10.1.0.5.0, 10.2.0.1

Diagnosis :

Some archived logs successfully applied to standby are not removed by RMAN
'backup archivelog all delete input' command.

Workaround :

Change the recover.bsq. Call Oracle Support for the code-fix

Bug:8468117

Consider a "DEFERRED" destination as still viable

Version affected :

10.2.0.0 till 10.2.0.4 and 11.0, 11.1

Version fixed :

11.2

Diagnosis :

The DEFERRED standby dest was considered by RMAN as offline parmanently.

Hence logs required for such standby were deleted.

Workaround :

None

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=11i0u51b2j_1192&id=357759.1

2/2