<xml></xml>

Collapse All Expand All Code: All Code: Multiple Code: C# Code: Visual Basic Code: Visual C++

Berkeley DB .NET API Documentation
NotificationEvent Enumeration
See Also Send Feedback

Specify a Berkeley DB event

Namespace: BerkeleyDB
Assembly: libdb_dotnet50 (in libdb_dotnet50.dll) Version: 5.0.21.0

# Syntax

C#

    public enum NotificationEvent

Visual Basic (Declaration)

    Public Enumeration NotificationEvent

Visual C++

    public enum class NotificationEvent

# Members

| Member name | Description
--- | --- | ---
| PANIC | The database environment has failed.
| REP_CLIENT | The local site is now a replication client.
| REP_DUPMASTER | A duplicate master site has been discovered in the replication group.
| REP_ELECTED | The local replication site has just won an election.
| REP_ELECTION_FAILED | 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.
| REP_JOIN_FAILURE | The local site could not synchronize with the master because an internal initialization was required, but internal initialization has been turned off by RepAutoInit.
| REP_MASTER | 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.
| REP_MASTER_FAILURE | The connection to the remote master replication site has failed.
| REP_NEWMASTER | 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.
| REP_PERM_FAILED | 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.
| REP_STARTUPDONE | The client has completed startup synchronization and is now processing live log records received from the master.
| WRITE_FAILED | A Berkeley DB write to stable storage failed.

# See Also

BerkeleyDB Namespace