Database management

Bug 16053545 RMAN cloning from active database fails when overlapped with database backup job

GOAL : Bug 16053545 RMAN

This note gives a brief overview of bug 16053545. 
The content was last updated on: 14-FEB-2017
Click here for details of each of the sections below.

Affects: Oracle Server (Rdbms)

Product (Component): Oracle Server (Rdbms)

Range of versions believed to be affecte: (Not specified)

Versions confirmed as being affected

  • 11.2.0.4
  • 11.2.0.3

Platforms affected: Generic (all / most platforms affected)

Fixed: 16053545

The fix for 16053545 is first included in

  • 12.2.0.1 (Base Release)
  • 12.1.0.2 (Server Patch Set)


Interim patches may be available for earlier versions - click here to check.

Symptoms:• ORA-19870 / ORA-19505 / ORA-17503

  • Error May Occur
  • ORA-19870 / ORA-19505 / ORA-17503

Related To: RMAN

  • RMAN (Recovery Manager)

Description: RMAN-03002, RMAN-05501, ORA-19870, ORA-19505, ORA-17503

Active duplication tries to incorporate incremental backups and so may

fail with errors of the form:

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

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

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

RMAN-03002: failure of Duplicate Db command at 12/08/2012 20:44:59

RMAN-05501: aborting duplication of target database

RMAN-03015: error occurred in stored script Memory Script

ORA-19870: error while restoring backup piece +RECO_ED01/...

ORA-19505: failed to identify file "+RECO_ED01/...

ORA-17503: ksfdopn:2 Failed to open file

Rediscovery Notes

Duplicate fails when there is a concurrent backup running

Workaround

Run the duplicate at a time when there is no concurrent operation.

Please note: The above is a summary description only. Actual symptoms can vary. Matching to any symptoms here does not confirm that you are encountering this problem. For questions about this bug please consult Oracle Support.