Unable To Start ODISRV - Shows LDAP Error Code 53 In ODISRV01.LOG (Doc ID 351138.1)

Last updated on JULY 01, 2016

Applies to:

Oracle Internet Directory - Version 10.1.2 to 10.1.4.3 [Release 10gR2 to 10gR3]
Information in this document applies to any platform.
***Checked for relevance on 07-Mar-2013***


Symptoms

1.  Starting odisrv process fails with the error below in the odisrv0X.log file:

MAIN: Error Registering ODI Server Instance : .
java.lang.Exception: [LDAP: error code 53 - Unwilling To Perform]
Error Updating InstanceRegistration Entrywith Group Info..
Error Registering Server Instance ..

 or

 

Mon Sep 19 16:47:06 CDT 2011 : Starting Server to execute Profile Group :999 against LDAP Server (uxcnas08.usg.com:23350)
Mon Sep 19 16:47:06 CDT 2011 : Retrieved Credentials from Local Wallet
Mon Sep 19 16:47:07 CDT 2011 : Connection to LDAP Server Successful
Mon Sep 19 16:47:07 CDT 2011 : SSL Mode :0
Mon Sep 19 16:47:07 CDT 2011 : Connecting to LDAP...
Mon Sep 19 16:47:17 CDT 2011 : DIP Server Instance Entry Exists : 1
Mon Sep 19 16:47:17 CDT 2011 : DIP Server Instance Entry Created By OIDMON
Mon Sep 19 16:47:17 CDT 2011 : ODI Server Instance Registration Failure : java.lang.Exception: [LDAP: error code 4 - Sizelimit Exceeded]
Exception while validating Instance Entry..
Error Registering Server Instance ..
Mon Sep 19 16:47:17 CDT 2011 : Exiting with Status -1: null

 

 or

ODI Server Instance Registration Failure : java.lang.Exception: [LDAP: error code 4 - Sizelimit Exceeded]

Exception while validating Instance Entry..

2.  The following command reveals there are duplicate entries: 

 ldapsearch -h <host> -p <port> -D cn=orcladmin -w <pwd> -b cn=odisrv,cn=subregistrysubentry -s sub objectclass=* dn

cn=instance1,cn=odisrv,cn=subregistrysubentry

cn=instance1,cn=odisrv,cn=subregistrysubentry

cn=instance1,cn=odisrv,cn=subregistrysubentry

(where instance#  represents the instance you are trying to start)


3.  Missing Indexes are shown for the CT_DN table

To check this,  log in to OID DB using sqlplus as ODS user, and ODS db user pwd defaults to same as orcladmin's at install time, and also qualify the table just in case:

SQL> select index_name,index_type,uniqueness from dba_indexes where table_name='ODS.CT_DN';

>INDEX_NAME - INDEX_TYPE - UNIQUENESS
>EP_DN - NORMAL - UNIQUE

 

 (There SHOULD BE THREE indexes as follows:)

 

>INDEX_NAME - INDEX_TYPE - UNIQUENESS
>EP_DN - NORMAL - UNIQUE
>RP_DN - NORMAL - UNIQUE
>PN_DN - BITMAP - NONUNIQUE

 

4.  Oidmon.log shows:

 

 

 2006/01/09:02:00:23 * Database Search Error.

2006/01/09:02:00:23 * Instance cn=instance1,cn=odisrv,cn=subregistrysubentry search failed

or

Thu May 04 17:43:22 EDT 2006 : ODI Server Instance Registration Failure :
java.lang.Exception: Invalid CN in regsitry entry :WARAWUT
Exception while validating config sets/profile Groups..
Error Registering Server Instance ..




Note that "registry" is intentionally misspelled. That's what the error says.



Changes

This seems to happen after a bulkload has been run.

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