Monitoring replication status

Edit online

You can make use of the information provided here to monitor replication status.

In addition, there are many operational attributes that provide replication status information when explicitly requested on a search. One of these attributes is associated with the entry that is the base of the replicated subtree, that is, the entry that the ibm-replicationContext objectclass was added to. If you do a base search of that entry, and request that the ibm-replicationIsQuiesced attribute is returned. This attribute is a boolean that indicates if the subtree has been quiesced.If the subtree is quiesced, no client updates are allowed (only updates from replication suppliers are accepted).There is an extended operation that can be used to quiesce a subtree, see the ldapexop command information in the Command Reference for more information.

The remainder of the status-related operational attributes are all associated with a replication agreement object. These attributes are only returned when explicitly requested on the search. The attributes available are:
  • ibm-replicationLastActivationTime: The time that the last replication session started between this supplier and consumer.
  • ibm-replicationLastFinishTime: The time that the last replication session finished between this supplier and consumer.
  • ibm-replicationLastChangeId: The change ID of the last update sent to this consumer.
  • ibm-replicationState: The current state of replication with this consumer.Possible values are:
    Active
    Actively sending updates to consumer.
    Ready
    In immediate replication mode, ready to send updates as they occur.
    Retrying
    If the server is configured to use a single connection, replication attempts to send the same update after waiting for 60 seconds and keeps trying until replication succeeds or the administrator skips the update.
    Waiting
    Waiting for next scheduled replication time.
    Binding
    In the process of binding to the consumer.
    Connecting
    In the process of connecting to the consumer.
    On Hold
    This replication agreement has been suspended or "held".
    Error Log Full
    For a server configured to use multiple connections, replication is suspended for this agreement. The receiver threads continue polling for status from any updates that have been sent, but no more updates are replicated.
    error xxxx
    An error has occurred where xxxx is the ID of the message that describes the error.
  • ibm-replicationLastResult The results of the last attempted update to this consumer, in the form: 
    <time stamp> <change ID> <result code> <operation> <entry DN>
    Note: This information is available for single threaded replication only.
  • ibm-replicationLastResultAdditional: Any additional error information returned from the consumer for the last update.
    Note: This information is available for single threaded replication only.
  • ibm-replicationPendingChangeCount: The number of updates queued to be replicated to this consumer.
  • ibm-replicationPendingChanges: Each value of this attribute gives information about one of the pending changes in the form: 
    <change ID> <operation> <entry DN>
    Requesting this attribute might return many values.Check the change count before requesting this attribute.
  • ibm-replicationChangeLDIF: Gives the full details of the last failing update in LDIF.
    Note: This information is available for single threaded replication only.
  • ibm-replicationFailedChanges: Similar to ibm-replicationPendingChanges in that it lists the IDs, DNs, update types, result codes, timestamps, numbers of attempts for failures logged for a specified replication agreement.The number of failures displayed are less than or equal to ibm-slapdMaxPendingChangesDisplayed.
  • ibm-replicationFailedChangeCount: Similar to ibmreplicationPendingChangeCount in that it returns a count of the failures logged for a specified replication agreement.
  • ibm-replicationPerformance: Information about multi-threaded replication.
Only the following persons are allowed to view ibm-replicationPendingChanges, ibm-replicationPendingChangesCount, ibm-replicationFailedChanges and ibm-replicationChangeLDIF:
  • The administrator
  • Members of the administrative group
  • Members of the global administrative group
  • Any user explicitly given update access to the replication topology entries through ACLs