Database Backup and Recovery (MOSC)

MOSC Banner

Problem opening standby DB following RMAN duplicate for standby from active database when using ASM

edited Feb 14, 2012 3:47AM in Database Backup and Recovery (MOSC) 6 comments
When using this method to create the standby, all files are copied to directories in ASM where the path is based upon the DB_UNIQUE_NAME, while aliases to the original path are only created for the non-OMF files. This results in failure when the standby DB is attempted to be opened as any OMF based files are not found.
For example,

Given:

DB_NAME = proddb
DB_UNIQUE_NAME = proddbstndby

Files are created on the standby by the RMAN duplicate for standby... process here:

+dgroup1/proddbstndby/datafile/

ASM aliases to the non-OMF files are created here:

+dgroup1/proddb/datafile/*


Starting the standby errors when an OMF file is attempted to be opened and the file (or an alias to the file) cannot be found in the path +dgroup1/proddb/datafile/

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

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center