Normally, when I create physical standby database, the configuration has the same directory structures and name values as production with the exception of db_unique_name.
But this time was not the case as shown below.
ANGEL:(SYS@xmenstby):PHYSICAL STANDBY> show parameter name NAME TYPE VALUE ------------------------- ----------- ---------------------------------------- cell_offloadgroup_name string db_file_name_convert string /oradata/xmenprod, /oradata/xmenstby db_name string xmenprod db_unique_name string angel_xmenstby global_names boolean FALSE instance_name string xmenstby lock_name_space string log_file_name_convert string /oradata/xmenprod, /oradata/xmenstby processor_group_name string service_names string xmenstby ANGEL:(SYS@xmenstby):PHYSICAL STANDBY>
I have not been accustomed to adding suffixes such as prod, stby, qa, dev, uat, etc… to database name.
Hopefully, when a connection is made to QA server, it’s for a QA database and not PROD.
Enough of the rant, the requirement is to create physical standby with different directory structures and ORACLE_SID at standby site is xmenstby.
The format I have been using is to prefix db_name with closest airport code to the data center to create db_unique_name.
Alternatively is to prefix with hostname.
Active database duplication is not an option because concern it may take a long time.
It was suggested to perform RMAN backup on primary, transfer backup to standby server using multiple scp, and restore database.
Here I go and if you are interested in how this turned out, then please read more about it here
