For doing the switchover, planning to do below steps:
Logon to OEM, go to Prdinfo DB home page, select the drinfo standby database and click Switchover.
I am expecting this to complete successfully. My questions is that after the switchover completes, how should we are plan to rename the DRINFO to PRDINFO? Application would still need to know the DB its connecting to as PRDINFO and not DRINFO(after switchover). Can someone please let me know what does this require and the procedure to rename Drinfo to Prdinfo and PRdinfo to Drinfo(after switch) ?
Standby setup DRINFO 10.2.0.4.0
my physical standby is a standalone on nodes DN1
DGMGRL> show database drinfo1
Role: PHYSICAL STANDBY
Intended State: ONLINE
Current status for "drinfo1":
I was checking this link for renaming the db instance using newid utility http://www.dba-oracle.com/t_rename_database_oracle_sid.htm
But I am not sure if i should be following the same for a primary instance after switchover. Wouldnt this break the connection between DR and PRD? All thos settings and the redos and shipping and falserver will need to be changed? Is there a process somewhere that can help me do this without breaking anything ? :)
You cannot rename the DB_NAME of the databases. You are supposed to have different DB_UNIQUE_NAMES/SID for each one. Your application needs to be using SERVICES to connect and you start up the services as required.
"You cannot rename the DB_NAME of the databases. "
I think I can rename the db_name of the DRINFO database to PRDINFO after the switch using that link. At the same time time I will be making the PRDINFO to DRINFO (i.e., switching the names of the databases also). Are you saying its not recommended to do so or its not possible?
Is there a Metalink or Oracle Doc that you can possibly point me to please ?
"You are supposed to have different DB_UNIQUE_NAMES/SID for each one."
Oh yeah! I forgot to update that the DRINFO after a successful switch is required to have two additional instances as PDRINFO1 PDRINFO2 PDRINFO3 on different nodes. So are you suggesting that the DB name be Drinfrp as usual and instance name be PRDINFO1 2 3 ?
It is not supported to do that with a Data Guard configuration. Who knows what kind of havoc you will create. You should be leaving the DB_NAME and DB_UNIQUE_NAME of the Primary and the Standby as they are. Regardless of who is the Primary and who is the Standby.
As I said before, your application should be using services to connect to the database.
You probably could reconfigure the DB_UNIQUE_NAMES to move the SID's around but why? You are defeating the purpose of a Data Guard configuration and putting yourself at risk. Believe me, the more complexity you have for your failover situations the more errors that will occur.
The thing is that the Application will no longer be using the database PRDINFO after it is switched to Drinfo. Their applications will need to be pointing to Drinfo and theres not going to be a switchover back to the original setup. Thats the reason why I need to make Drinfo as Prdinfo after the switch. But anyways I just now noticed that the dbname is already set to prdinfo(sorry didnt notice that before, thought that was also drinfo), so changing the dbname is crossed out. I think I only need to change the instance_name parameter in the database.
so, with the current setup in my DRINFO DB as below:
SQL> sho parameter name
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
db_name string prdinfo
instance_name string drinfo
db_unique_name string drinfo1
service_names string drinfo1
global_names boolean FALSE
I will have to change the instance_name from drinfo to prdinfo 1 2 3 each on a separate node and provide the application teams the tns entry, like you kindly suggested as: