After failing to install OID with privileged ports (389/636), you may end up with [2013-01-07T14:59:45+01:00] [OID] [NOTIFICATION:16]  [OIDLDAPD] [host: idm02.home.local] [pid: 6800] [tid: 0] Main:: sgslunlListen: IPV4 Bind failed (port=389), OS error=(13) [2013-01-07T14:59:45+01:00] [OID] [NOTIFICATION:16]  [OIDLDAPD] [host: idm02.home.local.nl] [pid: 6800] [tid: 0] Main:: sgslunlListen:
Today, I had to resolve an issue with an APEX LDAP call, that succeeded in the developer database, but failed in test with an ORA-31204: DBMS_LDAP: PL/SQL - Invalid LDAP Session.As this concerned 11G databases, my initial thought was: "Is an ACL defined?" On the other hand, I would have expected an error like "Access denied by ACL".Anyway, check acl's:column host format a30column acl format
Just missed Joels entry, but APEX 4.2 Early Adopter is available. See his post here.
If your application server logging is flooded with errors as below, make sure you have any mod_osso config file defined. it does not matter if it is correct, or not used.[Thu May 24 15:55:42 2012] [warn] [client 127.0.0.1] [ecid: 10.xxx.yyy.zzz:12492:1337867740001,2] \n[OSSO] W14: mod_osso is loaded but OssoConfigFile does not appear to be set.\n
If a Single Sign On enabled Forms server fails to perform SSO, and the client gets a http-500 error, with the stack trace below, then check your variables "oid_formsid" and "formsid_group_dn" in formsweb.cfg ($ORACLE_HOME/forms/server/formsweb.cfg)oracle.forms.net.ConnectionException: oracle.ias.repository.schema.SchemaException: Unable to connect to Oracle Internet Directory Server. Please