So you’ve decided to you dataguard broker to manage your Primary and Standby. Everything was fine and dandy until you enabled the the configuration.
Primary
Standby
the logs are shipping, and applying.
PRIMARY database,
set linesize 150
select inst_id,status,error from gv$archive_dest where dest_id=2;
return the status as “VALID”
Yet, when you run show configuration; (Primary)
You know you got the password files configure/create/land correctly.
STANDBY Database,
show configuration show a little different error
Hmmm ORA-12514, definitely issue with the TNS alias (By the way, my TNS alias name are the same as db_unique_name).
Here is where things starting to get weird. From Standby database, i can tnsping or sqlplus into Primary using the SAME tns alias that dataguard broker is using.
To get around this issue is to simply bounce the Standby database. Archiver process somehow doesn’t recognize the TNS alias.
After bouncing the Standby Database (or in theory you could kill the archiver process and pray that it will automatically start it back up)
In rare occasion, I had run into similar scenario with reverse role where PRIMARY database’s archiver doesn’t recognize the TNS alias for standby. Unfortunately you will have to bounce Primary (might as well bounce Standby, while you are at it).
Oracle Journey 