In OID 11G 'OIDCTL Status' Command Returns 'Could Not Connect to the Database' (Doc ID 1066474.1)

Last updated on JULY 01, 2016

Applies to:

Oracle Internet Directory - Version 11.1.1.1.0 and later
Information in this document applies to any platform.
***Checked for relevance on 06-SEP-2012***

Symptoms

When using a valid database connect string as per the tnsnames.ora in the Metadata Repository database ORACLE_HOME,  oidctl status fails with 'Could not Connect to the Database':

Example:

export TNS_ADMIN=MR_ORACLE_HOME/network/admin

oidctl connect=testdb1 status
oidctl : ORACLE_INSTANCE is not set, defaulting to /apps/opt/oracle/fmw/mid/IDM/ldap/
oidctl : INSTANCE_NAME is not set, defaulting to inst1
oidctl : COMPONENT_NAME is not set, defaulting to oid1
Could not connect to the Database.

 

 

Changes

This is a new install of OID 11g

* opmnctl status shows that oid1 is Alive.

* tnsping to connect string is successful:

eg.
tnsping testdb1
Used parameter files: /apps/opt/oracle/db/product/11.1.0/network/admin/sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = mydbhost01)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = testdb1.oracle.com)))
OK (10 msec)


* sqlplus to the database using the connect string is successful

SQL> connect system@testdb1/mypassword
Connected.

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms