ODSEE - The 'insync' Command Reports 0 Delay However DSCC Shows Many 'Missing Changes'
(Doc ID 1440194.1)
Last updated on NOVEMBER 23, 2022
Applies to:
Oracle Directory Server Enterprise Edition - Version 6.0 to 11.1.1.5.0 [Release 6.0 to 11gR1]Information in this document applies to any platform.
The behavior of insync with respect to DSCC's 'Missing Changes' is intuitive therefore expected the displayed values from each to correspond. However the difference between this two is:
Symptoms
When running the insync command, it shows 0 delay -
ReplicaDn Consumer Supplier Delay
<SUFFIX> xxxxxxxx3:xxxx3 xxxxxxxx0:xxxx3 0
<SUFFIX> xxxxxxxx3:xxxx3 xxxxxxxx0:xxxx3 0
<SUFFIX> xxxxxxxx3:xxxx3 xxxxxxxx0:xxxx3 0
<SUFFIX> xxxxxxxx3:xxxx3 xxxxxxxx0:xxxx3 0
<SUFFIX> xxxxxxxx3:xxxx3 xxxxxxxx0:xxxx3 0
<SUFFIX> xxxxxxxx3:xxxx3 xxxxxxxx0:xxxx3 0
DSCC showed missing changes;
Changes
The insync command indicates the synchronization state between a supplier replica and one or more consumer replicas. insync compares the RUVs of replicas and displays the time difference or delay (in seconds) between the servers.
DSCC 'Missing Changes' takes into account of ALL the pending changes from ALL the Primary Servers within the replicated topology for a given consumer. It uses ALL the Primary Servers RUV's, current as well as old(stale), that are found in the replicated topology to determine the "Missing Changes" value.
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 |