LDAP: error code 53 - Function Not Implemented

Question

Hi All,
While doing search on Oracle internet directory server(oracle ldap server),
we are getting following exception.
Exception
in thread "main" javax.naming.OperationNotSupportedException: [LDAP:
error code 53 - Function Not Implemented]; remaining name
'ou=people,dc=test,dc=com'
     at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3058)
     at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2931)
     at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2737)
     at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1808)
     at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1731)
     at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java:368)
     at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:338)
     at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:321)
     at javax.naming.directory.InitialDirContext.search(InitialDirContext.java:248)
     at DifferentSearches.doFilterSearch(DifferentSearches.java:99)
     at DifferentSearches.main(DifferentSearches.java:23)
Following is the code -
code:
     DirContext ctx= getDirContext();
     SearchControls ctls = new SearchControls();
     ctls. setReturningObjFlag (true);
     ctls.setSearchScope(SearchControls.SUBTREE_SCOPE);
     String filter = "(displayname=chandra)";
     NamingEnumeration answer = ctx.search("ou=people,dc=test,dc=com", filter, ctls);
     formatResults(answer);
     ctx.close();
When we search on the added attributes (like currentsession count) it works
fine. For this we had to enable index in OID on this field. But this is
not possible for the default attributes. OID does not provide a way to
enable indexing on these attributes. Could someone please let us know
how we can search on default attributes ?
Regards
Rahul
Edited by: Rahul_Sonawale on Oct 17, 2008 4:26 AM

Answer 1

Thanks Rajiv for reply.
I had read that thread before posting this. However, this is lightly different.
From other sites I can see that if it's caused by indexing, the error msg would say so and also tell you which attribute it is.
Some one suggested it's OID dropping the database connections intermittantly and should check both CRS ORACLE_HOME and RDBMS ORACLE_HOME have SQLNET.EXPIRE_TIME set and check the TNS and alert logs on the DB side for any other possible connection failure.
From some OID log we do see it has lost database connection:
OID logs in /u01/oid/oid_inst/diagnostics/logs/OID/oid1 :
ConnID:76 mesgID:2 OpID:1 OpName:search ConnIP:10.244.87.239 ConnDN:cn=policyrwuser,cn=users,dc=us,dc=oracle,dc=com
[gsldecfsFetchEntries] ORA error 3135: ORA-03135: connection lost contact
Process ID: 29973
Session ID: 164 Serial number: 3
I should post another thread for oid lost db connection.