My Oracle Support Banner

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

Last updated on AUGUST 30, 2023

Applies to:

Oracle Internet Directory - Version 11.1.1 to 11.1.1.9.180709 [Release 11g]
Information in this document applies to any platform.

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=<DB_NAME> status
oidctl : ORACLE_INSTANCE is not set, defaulting to <ORACLE_INSTANCE_DIR>
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 <DB_NAME>
Used parameter files: <DB_ORACLE_HOME_DIR>/network/admin/sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = <DB_HOSTNAME>)(PORT = <DB_PORT>)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = <DB_SERVICE_NAME>)))
OK (10 msec)


* sqlplus to the database using the connect string is successful

SQL> connect system@<DB_NAME>/<PASSWORD>
Connected.

 

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.