Database Backup and Recovery (MOSC)

MOSC Banner

RMAN duplicate with block change tracking workaround for Bug 1871441

edited Dec 18, 2014 1:37AM in Database Backup and Recovery (MOSC)

Oracle Database and RMAN 11.2.0.3 and 11.2.0.4 (AIX, and probably generic) exhibit several bugs when you have Block Change Tracking (BCT) enabled. Most manifest as failures of the Duplicate command when in the recovery phase, typically errors opening or trying to open the BCT file using the target database BCT filename rather than the auxiliary database 'new name' (ORA-19755, ORA-19750 and related).

This document is to show a workaround that we currently use that avoids most variations of these.

A pre-requisite is that the patch for Bug 11744544 is installed for your platform. Find this on the Oracle Support site. This patch adds new syntax to rename the BCT file during the duplication:

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center