OID 11g Server Does Not Start As it Can Not Connect to the Oracle Database. Oidmon Log Errors: ORA-12514 ORA-12541 ORA-12560 ORA-511 ORA-61 ns=12541, ns2=12560; nt=511, nt=61, nt=0;
(Doc ID 1494043.1)
Last updated on MAY 02, 2018
Applies to:Oracle Internet Directory - Version 11.1.1 to 22.214.171.124.0 [Release 11g]
Information in this document applies to any platform.
Two OIDs servers in clustered (High Availability) set up on box 1 are not starting. All working fine before being re-cycled. In the process of re-cycling, the servers were shut down but now do not start.
First OID 11g server1 cannot connect to Oracle RAC database 11g repository.
Second OID 11g server2 is up and running and it is able to connect to same Oracle database.
As OID 11g acts as sqlnet client to communicate with Oracle database, testing sqlplus to validate connectivity does not work.
Sqlplus connection from second OID 11g works fine. Main issue only with OID 11g server1.
Follow messages reported in the oidmon-0000.log file:
will retry again after 10 sec
[2012-09-14T15:41:08-04:00] [OID] [NOTIFICATION:16]  [OIDMON] [host: oidserver] [pid: 7624] [tid: 0] Guardian: Connecting to database, connect string is oiddb
[2012-09-14T15:41:08-04:00] [OID] [NOTIFICATION:16]  [OIDMON] [host: oidserver] [pid: 7624] [tid: 0] Guardian: [gsdsiConnect] ORA-12514, ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
7. Enabling sqlnet trace client from OID to Oracle database follow messages are reported:
2012-09-17 14:36:53.637655 : ntt2err:soc 804 error - operation=1, ntresnt=511, ntresnt=61, ntresnt=0
2012-09-17 14:36:53.637678 : ntt2err:exit
2012-09-17 14:36:53.736998 : nttcni:exit
2012-09-17 14:36:53.737045 : nttcon:exit
2012-09-17 14:36:53.737074 : nserror:entry
2012-09-17 14:36:53.737105 : nserror:nsres: id=0, op=65, ns=12541, ns2=12560; nt=511, nt=61, nt=0; ora=0, ora=0, ora=0
Another potential scenario:
OID was configured to use the SCAN host in its $ORACLE_INSTANCE/config/tnsnames.ora and it had been working fine.
After migrating the OID Database to a different host, OID fails to connect with the same errors above.
SCAN hostname for Oracle database, MYDATABASE.US.ORACLE.COM being referenced by an 11gR1 Client, on this case OID 11g as 11gR1.
This was setting as SCAN naming convention for 3-SCAN Listeners. As shown from an “lsnrctl status” command output”, for example:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!