Last updated on DECEMBER 02, 2016
Applies to:Oracle Internet Directory - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 11g]
Information in this document applies to any platform.
In OID 188.8.131.52.0, 184.108.40.206.0 or 220.127.116.11.0:
1. Deadlock Error is seen as below in one of the oidldapd01sxxxx.log file of the replica/consumer OID .
[2011-03-28T13:36:18+01:00] [OID] [NOTIFICATION:16]  [OIDLDAPD] [host: st-oid06] [pid: 7052]
[tid: 9] [ecid: 004bs_Q8asw9pY14ZvZBEr0001iC0004D9,0] ServerWorker (REG):[[BEGIN ConnID:3 mesgID:2639 OpID:2638 OpName:delete ConnIP:::ffff:10.178.231.46
ConnDN:cn=replication dn,orclreplicaid=st-oid06_p200r1,cn=replication configuration
[gslddd_CreTombStoneEntry]: ORA-60: ORA-00060: deadlock detected while waiting for resource
ORA-06512: at line 1
The problem appears to be a delete and modify of same entry coming in at the same time. We can reproduce the error ORA-60 by deleting entries with NetManager.
2. Its possible to add/modify/delete single level entries and they get replicated successfully, and we can also add/modify nested tnsnames entries (tnsnames entries with children) and they get replicated successfully. However deleting those nested tnsnames entries would not replicate at all.
But we don't see any errors or messages at all in any log, no conflict/hiq, no ora-60 anywhere, even when we turn on high level debug for replication server. The deletes are simply getting ignored altogether.
Although RETRY_CNT shows as completed (-2), the changes are not applied to the replica.
Also No errors or messages in any log, no conflict/hiq, no ora-60's anywhere.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms