ORA-12154 and ORA-26808 In Logical Standby Database
(Doc ID 2138289.1)
Last updated on MARCH 22, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.3 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
The following ORA-12154 and ORA-26808 logged in LOGICAL standby alert.log and the Apply Process dies:
Fri May 06 10:36:22 2016
LOGSTDBY Apply process AS02 started with server id=2 pid=54 OS id=4202
LOGSTDBY Apply process AS01 server id=1 pid=53 OS id=4198 stopped
Errors in file/<path>/diag/rdbms/<db_name>/<oracle_sid>/trace/<oracle_sid>_as01_4198.trc:
ORA-12154: TNS:could not resolve the connect identifier specified
Fri May 06 10:36:30 2016
Errors in file /<path>/diag/rdbms/<db_name>/<oracle_sid>/trace/<oracle_sid>_lsp0_2458.trc:
ORA-26808: Apply process AS01 died unexpectedly.
ORA-12154: TNS:could not resolve the connect identifier specified
LOGSTDBY Apply process AS02 started with server id=2 pid=54 OS id=4202
LOGSTDBY Apply process AS01 server id=1 pid=53 OS id=4198 stopped
Errors in file/<path>/diag/rdbms/<db_name>/<oracle_sid>/trace/<oracle_sid>_as01_4198.trc:
ORA-12154: TNS:could not resolve the connect identifier specified
Fri May 06 10:36:30 2016
Errors in file /<path>/diag/rdbms/<db_name>/<oracle_sid>/trace/<oracle_sid>_lsp0_2458.trc:
ORA-26808: Apply process AS01 died unexpectedly.
ORA-12154: TNS:could not resolve the connect identifier specified
Changes
N/A
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |