High Availability Data Guard, Sharding and Global Data Services (MOSC)

MOSC Banner

Physical Standby using ASM & OMF

I have done several physical standby implementations.  However, this is my first physical standby using ASM.  The primary and standby database are both configured to use ASM and OMF (Oracle 10gR2).  There are three disk groups which houses different types of files FLASH for the flash recovery area and multiplexed redo logs and control files, DATA for datafiles for non-system tablespaces and SYSTEM for SYSAUX, SYSTEM, UNDO and TEMP tablespaces.  Both the primary and standby have the same exact structure.  STANDBY_FILE_MANAGEMENT parameter is also set to AUTO.

The problem I'm having is that if I create a datafile  on the primary by explicitly specifying the disk group and the name of the disk group is different from the db_create_file_dest parameter, then the file created on the standby is in another disk group (specified by the db_create_file_dest parameter) on the standby.  The parameter values are the same on both.  Is there a way to overcome this behaviour?  The only solution I see to this is by disabling OMF on the standby or on both the primary and standby.  Setting the DB_FILE_NAME_CONVERT parameter will not work because if I happen to want

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