My Oracle Support Banner

OID 11g Having Component Name in Mixed / Upper Case Letters Can Cause OID Process Related Issues "Could not delete the Instance" (Doc ID 2773010.1)

Last updated on AUGUST 16, 2022

Applies to:

Oracle Internet Directory - Version and later
Information in this document applies to any platform.


OID 11.1.1.x

In normal scenario, when OID service is stopped, the corresponding running instance entry also will get removed from "cn=osdldapd,cn=subregistrysubentry" container.

But this doesn't happen if the OID component name is in Mixed case or Upper case.

After stopping the OID service, the registry entry still remains there.


  • Default "oid1" component already exists and running
  • Create a new component named "oidLdap1" by executing "opmnctl createComponent" command
  • Start OID services, both oid1 and oidLdap1 start successfully
  • Stop oidLdap1
    • opmnctl stopproc ias-component=oidLdap1
  • Check the entries under "cn=subregistrysubentry"
    • ldapsearch -h <OID_host> -p <OID_port> -D "cn=orcladmin" -w <password> -b "cn=osdldapd,cn=subregistrysubentry" -s sub "objectclass=*" dn                      


                      cn=asinst_1_oidLdap1_1_<hostname>,cn=osdldapd,cn=subregistrysubentry --------------------> not removed


From oidmon log file

[OID] [NOTIFICATION:16] [] [OIDMON] [host: xxxxx] [pid: <PID>] [tid: 0] Guardian: Shutting down

[OID] [NOTIFICATION:16] [] [OIDMON] [host: xxxxx] [pid: <PID>] [tid: 0] OIDMON_STOP: Sent SIGTERM to process id = 21794

[OID] [NOTIFICATION:16] [] [OIDMON] [host: xxxxx] [pid: <PID>] [tid: 0] OIDMON_STOP: gslsggDelete: Deleting entry cn=asinst_1_oidLdap_1_xxxxxxx,cn=osdldapd,cn=subregistrysubentry

[OID] [NOTIFICATION:16] [] [OIDMON] [host: xxxxx] [pid: <PID>] [tid: 0] OIDMON_STOP: Instance cn=asinst_1_oidLdap_1_xxxxx,cn=osdldapd,cn=subregistrysubentry not found.

[OID] [NOTIFICATION:16] [] [OIDMON] [host: xxxxx] [pid: <PID>] [tid: 0] OIDMON_STOP: Could not delete the Instance

[OID] [NOTIFICATION:16] [] [OIDMON] [host: xxxxx] [pid: <PID>] [tid: 0] OIDMON_STOP: OIDLDAPD Instance 1 deletion failed


This problem can sometimes contribute to the OID intermittent crash issue discussed in Doc ID 1607479.1




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

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