The database environment has failed.

The local site is now a replication client.

A previously established connection has been broken.

A connection with a remote site has been established.

An attempt to establish a new connection to a known remote site failed.

A duplicate master site has been discovered in the replication group.

The local replication site has just won an election.

The local site's attempt to initiate or participate in a replication master election failed, due to the lack of timely message response from a sufficient number of remote sites.

The internal initialization has been completed.

The local site could not synchronize with the master because an internal initialization was required, but internal initialization has been turned off by RepAutoInit.

The local site has been removed from the group.

The local site is now the master site of its replication group. It is the application's responsibility to begin acting as the master environment.

The connection to the remote master replication site has failed.

The replication group of which this site is a member has just established a new master; the local site is not the new master. The event_info parameter to the EventNotifyDelegate stores an integer containing the environment ID of the new master.

The replication manager did not receive enough acknowledgements (based on the acknowledgement policy configured with RepMgrAckPolicy) to ensure a transaction's durability within the replication group. The transaction will be flushed to the master's local disk storage for durability.

The client has completed startup synchronization and is now processing live log records received from the master.

A new site has joined the group.

An existing remote site has been removed from the group.

A Berkeley DB write to stable storage failed.