nsds5replicaLastUpdateStatus

- Replica update status

Description

This attribute is part of replica configuration for nsDS5ReplicationAgreement entries.

This read-only attribute shows the status of the latest update of the replica.

Messages include the following.

-1 Could not bind to replica

Solution: The credentials are wrong for the replication manager bind DN. Fix the replication agreement.

-1 Incremental update has failed and requires a total update

Solution: Reinitialize the replica. See the errors log to determine what led to the problem.

-1 Incremental update has failed and requires administrator action

Solution: Reinitialize the replica. See the errors log to determine what led to the problem.

-1 Internal error: Could not get access to the replica RUV

Solution: Replication stopped and requires a total update. Reinitialize the replica.

-1 Partial replication configuration error

Solution: Replication stopped and requires configuration fix. Fix the configuration.

-1 Partial replication configuration has changed

Solution: Replication stopped and requires a total update. Reinitialize the replica.

-1 Total update required

Solution: Reinitialize the replica. See the errors log to determine what led to the problem.

0 Incremental update session interrupted

Solution: A directory administrator has stopped or disabled replication.

0 Incremental update session started

Solution: Replication is proceeding normally.

0 Incremental update session stopped: nothing to replicate

Solution: Replication is proceeding normally.

0 Incremental update session succeeded

Solution: Replication is proceeding normally.

0 Incremental update started

Solution: Replication is proceeding normally

0 Incremental update stopped : Nothing acquired

Solution: Replication is proceeding normally. Another supplier is replicating to the consumer, and replication from this supplier will resume after that operation finishes.

0 Incremental update succeeded

Solution: Replication is proceeding normally.

0 No replication sessions started since server startup

Solution: No replication operation has been attempted yet and therefore no status is available. This is typically the case when restarting replication.

0 Replica acquired successfully

Solution: Replication is proceeding normally.

0 Replication session successful

Solution: Replication is proceeding normally.

1 Replication error acquiring replica: replica busy

Solution: Another supplier is replicating to the consumer, and replication from this supplier will resume after that operation finishes.

11 Replication error acquiring replica: duplicate replica ID detected

Solution: More than one master is using the same replica ID. Fix the configuration.

12 Replication session aborted

Solution: The consumer is disabled. Error 8194 should also appear in the errors log. Investigate the cause of the problem, fix it, and restart replication.

2 Replication error acquiring replica: excessive clock skew.

Solution: The time difference for clocks on different replicas is too big for replication to handle. Synchronize the system clocks.

202 Incremental update session aborted: Timeout while waiting for change acknowledgement [hostname:port-number]

Solution: Replication is proceeding normally. A timeout temporarily prevented replication from continuing.

3 Replication error acquiring replica: permission denied

Solution: The credentials are wrong for the replication manager bind DN. Fix the replication agreement.

4 Replication error acquiring replica: decoding error

Solution: A protocol error occurred.

401 Incremental update session stopped: Could not parse update vector

Solution: Replication is proceeding normally. A parse error temporarily prevented replication from continuing.

401 Replication session failed, consumer replica needs to be initialized

Solution: The database on the consumer has not been initialized. Either perform a total update on the consumer, or initialize the consumer with the same data as the supplier.

402 Replication session failed, consumer replica has a different data version

Solution: The database on the consumer has been initialized with different data from that of the supplier. Either perform a total update on the consumer, or initialize the consumer with the same data as the supplier.

5 Replication error acquiring replica: unknown update protocol

Solution: The consumer does not support the same replication protocol as the supplier.

6 Replication error acquiring replica: no such replica

Solution: The consumer is not configured for replication for the suffix to be replicated.

7 Replication error acquiring replica: csn below purge point

Solution: The replication change log has been purged and therefore no longer contains the changes necessary to update the consumer.

8 Replication error acquiring replica: internal error

Solution: The consumer failed to replay an replication operation. See the errors log on the consumer to determine what led to the problem.

801 Incremental update session aborted : Unable to adjust the time between replicas

Solution: The time difference for clocks on different replicas is too big for replication to handle. Synchronize the system clocks, perhaps using the network time protocol (NTP).

810 Replication error acquiring replica: Supplier and consumer use the same replica ID

Solution: More than one replica is using the same replica ID. Fix the configuration.

820 Incremental update session stopped: unable to replicate schema

Solution: Replication is proceeding normally, but schema could not be replicated. If this message is observed repeatedly, replicate schema to the consumer manually.

829 Replication error acquiring replica: not able to use partial replication to read-write replica

Solution: Only consumers can be partial replica. Fix the configuration.

9 Replication error acquiring replica: replica released

Solution: Replication is proceeding normally.

Examples

nsds5replicaLastUpdateStatus: 0 replica acquired successfully

Attributes

See attributes(5) for descriptions of the following attributes:

See Also

replication(5dsconf)