OID 11.1.1.9 Crashes With "Recieved Signal = 11, Shutting Down" While Issuing Search on "cn=jpscontext,cn=jpsroot" with -z 1
(Doc ID 2681069.1)
Last updated on AUGUST 30, 2023
Applies to:
Oracle Internet Directory - Version 11.1.1.9.180709 and laterInformation in this document applies to any platform.
Symptoms
Applied OID 11.1.1.9 bundle Patch 28125308 - "OID BUNDLE PATCH 11.1.1.9.180709"
OPSS using OID as LDAP security store.
OID crashes and reports the following in the oid logs:
oidldapd01s<PID>.log
2020-05-05T13:31:52.285955 * Bind variables: :szCommonName = "cn=jpscontext",
:szBaseDomain = "cn=jpsroot,"
2020-05-05T13:31:52.288036 * gslbndnWithEscChar:
origDN:<cn=JPSContext,cn=jpsroot> NormDn:<cn=jpscontext,cn=jpsroot>
2020-05-05T13:31:52.288126 * Base Search Completed with: 0 nentires=1
2020-05-05T13:31:52.289248 * 2020-05-05T13:31:52.289290 * Recieved signal = 11, shutting down
END
oidldapd_stack00_<PID>.dmp
============================
gslutcTrace() gsldpGetMaxAttrValForOPSS()+890 arg#1: ????
value=0000001D (ptr)
arg#2: ???? value=00625EC0 (ptr)
arg#3: ???? value=00000019 (ptr)
Issue produces with the following ldapsearches:
modifytimestamp createtimestamp
"objectclass=*" modifytimestamp createtimestamp
"objectclass=*" modifytimestamp createtimestamp
"objectclass=*" modifytimestamp createtimestamp
cn=soa-infra,cn=bpm,cn=JPSContext,cn=jpsroot
modifytimestamp= <MODIFYTIMESTAMP_VALUE>
createtimestamp= <CREATTIMESTAMP_VALUE>
cn=SystemPolicy,cn=bpm,cn=JPSContext,cn=jpsroot
modifytimestamp=<MODIFYTIMESTAMP_VALUE>
createtimestamp=<CREATTIMESTAMP_VALUE>
ldap_search: Sizelimit exceeded
Cause
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
Symptoms |
Cause |
Solution |
References |