OID No Longer Starts Since Changing orclmaxcc or orclserverprocs (Doc ID 359990.1)

Last updated on AUGUST 30, 2023

Applies to:

Symptoms

• opmnctl startall fails with:
  

  Failure when starting the user’s session in the settings. Failure to access the API repository.
  Root cause:: Unable to establish connection to the Oracle Internet Directory Server
  ldap://<OID_HOSTNAME>:<PORT>/. Base Exception :
  javax.naming.CommunicationException: <OID_HOSTNAME>:<OID_PORT> [Root exception is java.net.ConnectException: Connection refused]

• stopping the OID processes, clearing the ods_process table, ensuring the OID ports are free still does not allow OID to start
• opmnctl status shows that OID is alive
• ps -ef shows one oidmon process and only one oidldapd process, indicating that OID is not really running
• OID dispatcher log shows, for example for 10g OID: 
  

   

• renaming the 2 wallet files in 10g $ORACLE_HOME/ldap/admin/ ($ORACLE_INSTANCE/OID/admin in 11g OID) and rerunning "oidpasswd connect=<OID_DB> create_wallet=true" does not allow OID to start

Changes

The default configset/instance or component was recently changed to have orclserverprocs and orclmaxcc set to higher values. The current values can be confirmed with the following query for OID 10g:

sqlplus ods/<PASSWORD>@<OID_DB>
SQL> set pagesize 2000
SQL> select * from ods.ds_attrstore where entryid in
(select entryid from ods.ds_attrstore where attrval like '%osdldapd%'
and attrval like '%configset0%');

Cause

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