Error 12154 received logging on to the standby

FAL[client, USER]: Error 12154

If you see this error message in alert log file of primary database. Check following points.

• Check if your standby database is up and running and is registered with the Listener?
• Check the value of parameter “FAL_SERVER” initialization parameter in standby database, and use “tnsping <FAL_SERVER>” on standby host to confirm if primary database is accessible through FAL_SERVER TNS entry form standby database.
• Make sure that password file is present on standby and it is exact copy of primary database. In case of RAC, make sure that all primary RAC nodes have exact copy of password file and also same password file is copied on all standby RAC nodes.
• Check whether environment variable TNS_ADMIN is set to a correct value and TNSNAMES.ORA file exists at the location set for this variable. To confirm that TNS_ADMIN was set correctly when database was started, execute following steps.

if Above mentioned steps are ok. Follow below step for last chance

SOLUTION

=========

SQL>  alter system set log_archive_dest_state_2='defer';

SQL> alter system set log_archive_dest_2 = '.....';

SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_2='SERVICE=stby NOAFFIRM ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STBY';

– Switch logfiles on the Primary

SQL> alter system switch logfile;


3) On the Standby Database:

– Cancel Managed Recovery

SQL> alter database recover managed standby database cancel;

– Shutdown the Standby Database

SQL> shutdown immediate

SQL> startup mount;

SQL> alter database recover managed standby database using current logfile disconnect;

6) Re-enable Log Transport Services on the Primary:

SQL> alter system set log_archive_dest_state_2='enable';