OID 11g: 'opmnctl createcomponent -componentType OID' Fails With 'Check -Db_info parameter' (Doc ID 955547.1)

Last updated on AUGUST 08, 2017

Applies to:

Oracle Internet Directory - Version 11.1.1 and later
Information in this document applies to any platform.
Check on Currency 04/02/2015

Symptoms

When trying to Create an Instance-Specific Configuration Entry in OID 11g
'opmnctl createcomponent -componentType OID' fails with the following error while tnsping returns OK and the first OID component is running fine:

INFO: Num of OIDs: 2
Oct 20, 2009 2:53:23 PM oracle.as.config.provisioner.InstallerCmdLine handleRunFailure
SEVERE: Command failed:
oracle.as.config.ProvisionException: Exception in onCreate()
at oracle.iam.management.oid.install.wls.OIDComponent.onCreate(OIDComponent.java:225)
at
oracle.as.config.impl.OracleASComponentBaseImpl.createComponent(OracleASComponentBaseImpl.java:559)
at
oracle.as.config.impl.OracleASComponentBaseImpl.create(OracleASComponentBaseImpl.java:103)
at
oracle.as.config.provisioner.commands.CreateComponentCommand.execute(CreateComponentCommand.java:20)
at oracle.as.config.provisioner.InstallerCmdLine.run(InstallerCmdLine.java:86)
at oracle.as.config.provisioner.InstallerCmdLine.main(InstallerCmdLine.java:44)
Caused by: oracle.as.config.ProvisionException: Additional OID instances within an ASInstance
should be installed against the same DB as the first OID instance . Check -Db_info parameter
(Refer $OI/config/tnsnames.ora)
at oracle.iam.management.oid.install.wls.OIDComponent.onCreate(OIDComponent.java:138)
... 5 more

 

Collect connect string for the first OID component. Here it is OIDDB.

% ps -ef | grep oidmon
oracle    4239 23836  0 15:56 pts/0    00:00:00 grep oidmon
oracle   25556     1  0 14:31 ?        00:00:01 /ora01/app/oracle/product/middleware/Oracle_IDM1/bin/oidmon connect=OIDDB opmnuid=true start

tnsping returns OK:

% tnsping oiddb

TNS Ping Utility for Linux: Version 11.1.0.7.0 - Production on 20-OCT-2009 16:08:50

Copyright (c) 1997, 2008, Oracle.  All rights reserved.

Used parameter files:
/ora01/app/oracle/product/middleware/instances/asinst_1/config/sqlnet.ora


Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION=(ADDRESS=(PROTO   =TCP)(HOST=<DB Host>)(PORT=<DB Listener Port>))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=<DB Service Name>)))
OK (0 msec)

ldapsearch connects to the first OID component and retrieves the entry information successfully:

% ldapsearch -D cn=orcladmin -q -b "cn=oid1,cn=osdldapd,cn=subconfigsubentry" -s base "objectclass=*"
Please enter bind password:

cn=oid1,cn=osdldapd,cn=subconfigsubentry
cn=oid1
orcloidinstancename=asinst_1
orcloidcomponentname=oid1
...

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