My Oracle Support Banner

OID 10.1.4.0.1 Replication Does Not Work / Entries Added In the Master Node Does Not Replicate To The Replica Node / On HP, Replication Server Keeps Crashing And Never Fully Starts (Doc ID 553414.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Internet Directory - Version 10.1.4.0.1 and later
Information in this document applies to any platform.

Symptoms

Oracle Internet Directory 10.1.4.0.1.

OID Replication does not work. Entries added in the Master/Supplier node do not replicate to the replica/consumer node.

The $ORACLE_HOME/ldap/log/oidrepld01.log file may show error:   

...<snip>...
2008/01/29:09:43:01 * 1 new changes (for transport) queued from oidsupplierhost_asdb1 to
oidconsumerhost_asdb2.
2008/01/29:09:44:02 * 1 new changes queued from oidsupplierhost_asdb1 to oidconsumerhost_asdb2.
2008/01/29:13:06:21 * 2 new changes (for transport) queued from oidsupplierhost_asdb1 to
oidconsumerhost_asdb2.
2008/01/29:13:07:22 * 2 new changes queued from oidsupplierhost_asdb1 to oidconsumerhost_asdb2.
2008/01/29:13:13:28 * 1 new changes (for transport) queued from oidsupplierhost_asdb1 to
oidconsumerhost_asdb2.
2008/01/29:13:14:29 * 1 new changes queued from oidsupplierhost_asdb1 to oidconsumerhost_asdb2.
2008/01/29:13:19:34 * 1 new changes (for transport) queued from oidsupplierhost_asdb1 to
oidconsumerhost_asdb2.
2008/01/29:13:20:35 * 1 new changes queued from oidsupplierhost_asdb1 to oidconsumerhost_asdb2.
2008/01/29:13:20:35 * sgslufread: Hard error on read, OS error = 32 
2008/01/29:13:20:35 * sgslufread: Hard error on read, OS error = 32 
...<snip>...
  
The $ORACLE_HOME/ldap/log/oidldapd01s<pid#>.log contains error:

BEGIN
2008/01/29:13:20:35 * ServerWorker (REG):3
ConnID:2954 * mesgID:5 * OpID:4 * OpName:modify
ConnIP:198.233.121.75 ConnDN: cn=replication dn,orclreplicaid=oidconsumerhost_asdb2,cn=replication configuration
gslecrireplaceEC: Can not delete null entry in the entry cache
END


 

 

NOTE: The following errors at the beginning of the oidrepld log, corresponding to replication server startup time, are normal and can be ignored if replication is working ok:

2008/01/29:08:51:09 *
oidrepld: Release 10.1.4.0.1 - Production on tue jan 29 08:51:09 2008
Copyright (c) 1982, 2006 Oracle. All rights reserved.
2008/01/29:08:51:09 * Starting OIDREPLD against oidhost.mycompany.com:389...
2008/01/29:08:51:09 * sgslufread: Hard error on read, OS error = 104
2008/01/29:08:51:09 * sgslufread: Hard error on read, OS error = 32
2008/01/29:08:51:09 * sgslufread: Hard error on read, OS error = 32
2008/01/29:08:51:10 * sgslufread: Hard error on read, OS error = 104
2008/01/29:08:51:10 * sgslufread: Hard error on read, OS error = 32
2008/01/29:08:51:10 * sgslufread: Hard error on read, OS error = 32
2008/01/29:08:51:10 * sgslufread: Hard error on read, OS error = 104

 

NOTE: On HP platform, in addition to the symptoms above, replication server may never start, and instead keep crashing and getting restarted by oidmon, with stack trace files generated (oidrepldstack01s<pid#>.log) with the following:

----- Call Stack Trace -----

calling              call     entry                argument values in hex     
location             type     point                (? means dubious value)    --
----------------   -------- -------------------- ----------------------------
sgslusz()+132        ?        gslupsDumpProcStack  40000000000D0713 ? 0 ? 0 ?
                             ()                   800003FFBFB5F930 ?
sgslus4()+24         ?        sgslusz()            10000400000000 ? 3FFE00000 ?
                                                  1 ? 0 ?
_sigreturn()+0       ?        sgslus4()            1 ? 0 ? 517A0010 ?
                                                  800003FFBFB637B0 ?
mallinfo()+9148      ?        _sigreturn()         C00000000005F777 ?
                                                  800003FFBFFE4F40 ? 0 ?
                                                  C00000000039ECE0 ?
_ltostr()+3060       ?        mallinfo()           40000000000CFFCB ?
                                                  800003FFBFE851B8 ?
                                                  8000000101440018 ? 2 ?
realloc()+468        ?        _ltostr()            C0000000003991E7 ?
                                                  8000000101440018 ?
                                                  8000000100011CA0 ? 0 ?
gslumrRealloc()+128  ?        realloc()            8000000101440018 ?
                                                  8000000100011CA0 ? 0 ? 2E ?
gsleioEBerRealloc()  ?        gslumrRealloc()      8000000100EE3FE8 ? 45ED3 ?
+480                                               800003FFBFE8A710 ? 15 ?
gsleioDBerWrite()+7  ?        gsleioEBerRealloc()  8000000100011CA0 ?
6                                                  800000010004B528 ?
                                                  370000000039EB4B ?
                                                  800003FFBFB62D90 ?
gsleenDBerPutLen()+  ?        gsleioDBerWrite()    800000010004B528 ?
64                                                 4000000000123B37 ? 0 ?
                                                  4000000000124537 ?

...<etc, etc>....

Changes

 

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
Changes
Cause
Solution
References


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.