Same "replicationCN" Seen in Output Before DS Stop and After DS Start (Doc ID 2097717.1)

Last updated on JANUARY 26, 2016

Applies to:

Oracle Unified Directory - Version 11.1.2.0.0 to 11.1.2.3.2 [Release 11g]
Information in this document applies to any platform.

Goal

In the following environment the DS1 and DS2 are replication,

- Directory Server1 (DS1)
- Replication Server1 (RS1)
- Directory Server2 (DS2)
- Replication Server2 (RS2)

If DS2 is restarted when the replication data is sending to DS2 from DS1, the same replicationCN is seen in the output in the DS2 once before stop DS and again after the DS is started.

E.X.

<before stop DS2>

[2016-01-01T01:01:01.000+09:00] [OUD] [TRACE] [OUD-xxxxxxxx] [PROTOCOL] [host: xxxxxxx] [nwaddr: xxx.xxx.xxx.xxx]
[tid: xxx] [userId: root] [ecid: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx,0:1] [result: 0] [category: RES] [conn: -1]
[op: xxxx] [etime: 0] [msgID: 8840] [additionalInfo: replicationCN:000001500a11111111110002222c] MODIFY

<after restart DS2>

[2016-01-01T02:30:00.000+09:00] [OUD] [TRACE] [OUD-xxxxxxxx] [PROTOCOL] [host: xxxxxxx] [nwaddr: xxx.xxx.xxx.xxx]
[tid: xxx] [userId: root] [ecid: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx,0:1] [result: 0] [category: RES] [conn: -1]
[op: xxxx] [etime: 1211] [msgID: 625] [additionalInfo: replicationCN:000001500a11111111110002222c] MODIFY

 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms