We have implemented a second standby in test environment but getting below issue while switchover.
When we switchover from primary to standby. standby becomes the primary successfully but issue is primary doesn’t become standby automatically and it’s does not come up. After starting it manually, everything becomes normal.
Below is the output of dgmgrl .
DGMGRL> switchover to msdp
Performing switchover NOW, please wait...
New primary database "msdp" is opening...
Operation requires startup of instance "msdpha" on database "msdpha"
Starting instance "msdpha"...
Unable to connect to database
ORA-12154: TNS:could not resolve the connect identifier specified
Failed.
Warning: You are no longer connected to ORACLE.
Please complete the following steps to finish switchover:
start up instance "msdpha" of database "msdpha"
DGMGRL>
=============================
DGMGRL>
DGMGRL> show configuration
Configuration - msdpdg
Protection Mode: MaxPerformance
Databases:
msdpha - Primary database
Error: ORA-16778: redo transport error for one or more databases
msdp - Physical standby database
msdpdr - Physical standby database
Error: ORA-01034: ORACLE not available
Fast-Start Failover: DISABLED
Configuration Status:
ERROR
=============================================
dataguard log
09/04/2017 11:47:44
SWITCHOVER TO msdp
Notifying Oracle Clusterware to teardown primary database for SWITCHOVER
09/04/2017 11:47:54
Command SWITCHOVER TO msdp completed
Shutting down instance after CTL_SWITCH
alert.log
Mon Sep 04 11:47:44 2017
ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY WITH SESSION SHUTDOWN
ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY [Process Id: 7304] (msdpha)
Waiting for all non-current ORLs to be archived...
All non-current ORLs have been archived.
Waiting for all FAL entries to be archived...
All FAL entries have been archived.
Waiting for dest_id 3 to become synchronized...
Active, synchronized Physical Standby switchover target has been identified
Switchover End-Of-Redo Log thread 1 sequence 131 has been fixed
Switchover: Primary highest seen SCN set to 0x0.0xd977e
ARCH: Noswitch archival of thread 1, sequence 131
ARCH: End-Of-Redo Branch archival of thread 1 sequence 131
ARCH: LGWR is actively archiving destination LOG_ARCHIVE_DEST_3
ARCH: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2
ARCH: Standby redo logfile selected for thread 1 sequence 131 for destination LOG_ARCHIVE_DEST_3
ARCH: Standby redo logfile selected for thread 1 sequence 131 for destination LOG_ARCHIVE_DEST_2
Archived Log entry 193 added for thread 1 sequence 131 ID 0x2b11495c dest 1:
ARCH: Archiving is disabled due to current logfile archival
Primary will check for some target standby to have received alls redo
Final check for a synchronized target standby. Check will be made once.
LOG_ARCHIVE_DEST_3 is a potential Physical Standby switchover target
Active, synchronized target has been identified
Target has also received all redo
Backup controlfile written to trace file /opt/drutt/msdpdb/diag/rdbms/msdpha/msdpha/trace/msdpha_rsm0_7304.trc
Clearing standby activation ID 722553180 (0x2b11495c)
The primary database controlfile was created using the
'MAXLOGFILES 16' clause.
There is space for up to 12 standby redo logfiles
Use the following SQL commands on the standby database to create
standby redo logfiles that match the primary database:
ALTER DATABASE ADD STANDBY LOGFILE 'srl1.f' SIZE 209715200;
ALTER DATABASE ADD STANDBY LOGFILE 'srl2.f' SIZE 209715200;
ALTER DATABASE ADD STANDBY LOGFILE 'srl3.f' SIZE 209715200;
ALTER DATABASE ADD STANDBY LOGFILE 'srl4.f' SIZE 209715200;
ALTER DATABASE ADD STANDBY LOGFILE 'srl5.f' SIZE 209715200;
Archivelog for thread 1 sequence 131 required for standby recovery
Switchover: Primary controlfile converted to standby controlfile succesfully.
Switchover: Complete - Database shutdown required
Completed: ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY WITH SESSION SHUTDOWN
Mon Sep 04 11:47:51 2017
Process (ospid 7269) is suspended due to switchover to physical standby operation.
Mon Sep 04 11:47:51 2017
Process (ospid 7267) is suspended due to switchover to physical standby operation.
Mon Sep 04 11:47:55 2017
Shutting down instance after CTL_SWITCH
DMON (ospid: 7256): terminating the instance
Instance terminated by DMON, pid = 7256