can i switchback from primary to standby after once switchover is complete.

[raja]

Hi Erman

I have successfully completed the switchover and now standby has become primary and primary has become the standby. Successfully started the ebs services and users were redirected to new ebs logon page.

Now i am trying to switchback. It is possible by following the switchover route?

[raja]

when i am trying to switchback , before that my archives from new primary is not getting shipped to standby. i am getting the belo error

ORA-16047: DGID mismatch between destination setting and target database
Error 16047 for archive log file 1 to 'PROD'
Errors in file /u01/database/PROD/12.1.0/admin/PROD_rac2/diag/rdbms/proddr/PROD/trace/PROD_tt00_32478.trc:
ORA-16047: DGID mismatch between destination setting and target database
Errors in file /u01/database/PROD/12.1.0/admin/PROD_rac2/diag/rdbms/proddr/PROD/trace/PROD_tt00_32478.trc:
ORA-16047: DGID mismatch between destination setting and target database
2018-09-04 20:26:16.993000 -04:00


And in the trace file :-

*** SERVICE NAME:() 2018-09-04 20:26:06.996
*** MODULE NAME:() 2018-09-04 20:26:06.996
*** CLIENT DRIVER:() 2018-09-04 20:26:06.996
*** ACTION NAME:() 2018-09-04 20:26:06.996

OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1017 and errmsg is 'ORA-01017: invalid username/password; logon denied
'

*** 2018-09-04 20:26:13.512
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1017 and errmsg is 'ORA-01017: invalid username/password; logon denied
'

*** 2018-09-04 20:26:15.585
krsi_verify_network: Error 16047 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'PROD'
ORA-16047: DGID mismatch between destination setting and target database
*** 2018-09-04 20:26:15.585733 4929 krsh.c
Error 16047 for archive log file 1 to 'PROD'
*** 2018-09-04 20:26:15.585758 6944 krsi.c
krsi_dst_fail_caller: dest:2 err:16047 force:0 blast:1
ORA-16047: DGID mismatch between destination setting and target database

My password file is correct.

[raja]

my primary server

*.db_unique_name='PRODDR'
*.fal_server='PRODDR'
*.log_archive_config='dg_config=(PRODDR,PROD)'
*.log_archive_dest_1='LOCATION=/u01/database/oracledb/data/ VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=PRODDR'
*.log_archive_dest_2='service=PROD ASYNC valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=PROD'
*.log_archive_dest_state_2='ENABLE'



My Stanbdy server

*.db_name='PROD'
*.db_unique_name='PROD
*.fal_server='PRODDR'
*.log_archive_config='dg_config=(PRODDR,PROD)'
*.log_archive_dest_1='LOCATION=/u01/database/PROD/data'
*.log_archive_dest_2='service=PRODDR ASYNC valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=PRODDR'
*.log_archive_dest_state_2='DEFER'

[raja]

some more errors from alert log after primary db bounce
Errors in file /u01/database/PROD/12.1.0/admin/PROD_rac2/diag/rdbms/proddr/PROD/trace/PROD_arc1_7601.trc:
ORA-16047: DGID mismatch between destination setting and target database
PING[ARC1]: Heartbeat failed to connect to standby 'PROD'. Error is 16047.

[ErmanArslansOracleBlog]

The error is 16047.
You have a configuration problem.
Check the relevant files and db parameters.

Here is a similar issue and solution for you ->

PING[ARC2]: Heartbeat Failed To Connect To Standby ORA-16047 (Doc ID 2379045.1)

[Raja]

Thanks Erman. My log archive dest 2 parameter was pointing to wrong service name. Once it is corrected, I was able to perform the switch back.

[Raja]

I successfully created the physical standby for EBS 12.2 and did a successful test of switchover/Switchback test.

Now for the role transitions, i saw your post http://ermanarslan.blogspot.com/2016/05/ebs-dr-dataguard-switchover-tests.html

So just a quick question on- if we do the role transitions using the flashback restore point, wouldn't there be any loss of transactions/archives?

Your post suggest that the standby db tier will be in open mode. But physical standby should be in mount state right?

********
On Standby DB tier:

alter database recover managed standby database cancel;

alter database flashback on;

create restore point OPEN_STANDBY guarantee flashback database;

alter database activate standby database;

alter database open;

sqlplus apps/apps_password
exec fnd_conc_clone.setup_clean;
commit;

******************
How this is possible? Is it certified on EBS?

Thanks

[ErmanArslansOracleBlog]

In that post, I m doing a test.

I mean, I open the standby read write and do my tests..
After the test  are finished, I restore my standby db to the restore point and make it continue to receive and apply redo.

On the hand, I think you are not doing a test..
You are talking about a real switchover..
If so, you shouldn't restore your standby db to a restore point.
you will do the switchover and then you will do a switchback.
As long as your standby-primary database are sync just before the switchover and switchback, you re safe.

I guess that you understand my point.

Please follow -> Business Continuity for Oracle E-Business Suite Release 12.2 Using Oracle 12c (12.1.0.2) Physical Standby Database (Doc ID 1963472.1)

Your EBS system and its configuration should be aligned with the things explained in the document.
Once everything is aligned, You will follow "Section 6: Performing Role Transitions".
As for being aligned, I actually mean the things/configuration that are explained before Section 6.