Alert Types, Severities, and States for Replication

Learn about the properties that define and control alerts.

An alert’s type determines what causes it to fire.

Type	Description
State	A state alert fires when the metric on which it is based changes to a particular state. The possible states are running, pending, stopped, warning, error, and unknown.
Threshold	A threshold alert fires when the metric on which it is based passes a preset level.

Alert severities control when an alert is issued. You can configure the states or threshold values for each alert.

Severity	Description
Normal	No alert is issued.
Warning	A problem has given cause for concern. An alert is issued; you can subscribe to alerts that fire at the Warning level.
Critical	A serious problem exists. An alert is issued; you can subscribe to alerts that fire at the Critical level.

Alert states are used on the dashboards, heat chart, and topology icon decorators.

Replication Object	Object State	Alert State	Description
Replication Server	Active	Running	The Replication Server is running and actively replicating data.
	Quiesce	Running	The Replication Server is running, but is not currently replicating data.
	Suspect	Warning	At least one of the Replication Server connections, routes, or queues is down.
	Rebuilding		The Replication Server is rebuilding queues. This state is returned by the admin health command.
	Hibernating		The Replication Server is in hibernation mode. This state is returned by the admin health command.
	Recovering		The Replication Server is in standalone mode and is rebuilding queues. This state is returned by the admin health command.
	Standalone		The Replication Server is in standalone mode. This state is returned by the admin health command.
	Down	Stopped	The Replication Server is unable to communicate with the RSSD. The server state is also set to DOWN if the user or password is incorrect.
	Unknown	Unknown	The state of the Replication Server cannot be determined. UNKNOWN can also indicate that the server is not part of the replication environment.
Replication Server Connection	Active	Running	The Replication Server DSI and RepAgent thread are actively replicating.
	Hidden	Running
	Suspended	Stopped	The Replication Server DSI or RepAgent thread is DOWN or SUSPENDED.
	Unknown	Unknown	The RepAgent for a primary connection is not part of the replication environment.
Replication Server Logical Connection	Active	Running	The RepAgent for the active physical connection and the DSI thread for the standby physical connection are both active.
	Suspended	Stopped	The logical connection can be suspended for these reasons: The active or standby physical connection is not defined for the logical connection. The RepAgent thread for the active connection is suspended. The DSI thread for the standby connection is suspended. The logical connection is in the process of switching the active and standby databases.
	Unknown	Unknown	The RepAgent thread for the active connection is unknown, or the DSI thread for the standby connection is unknown.
Replication Server Route	Active	Running	The route is open and data can pass from the origin to the destination Replication Server.
	Suspended	Stopped	The route is unavailable and data cannot pass between the Replication Servers. The description provides the reason for the suspended route; for example: The route encountered an internal error. The route is being created. The route is suspended. The route encountered an error at the destination. The route is being dropped. The route is being dropped with NOWAIT. An indirect route is being changed to a direct route.
	Unknown	Unknown	The destination Replication Server is not part of the replication environment.
Replication Path	Active	Running	All objects along the Replication Path are actively replicating data.
	Suspect	Stopped	One or more objects along the Replication Path are not replicating data.
	Unknown	Unknown	The state of the objects in the Replication Path cannot be determined.
Replication Agent	Replicating	Running	Sucessfully connected to the Replication Agent. The agent is in replicating state. This state is returned by the ra_status command.
	Replicating (Resynchronization)	Running	The Replication Agent has been restarted and is resynchronizing the primary and replicate databases. This state is returned by the ra_status command.
	Admin	Stopped	Sucessfully connected to the Replication Agent. The agent is in administration state and is not currently replicating data. This state is returned by the ra_status command.
	Replication Down	Stopped	Cannot connect to the Replication Agent or the agent state is set to REPLICATION DOWN. This state is returned by the ra_status command.
	Unknown	Unknown	The state of the Replication Agent cannot be determined. Also may indicate that the agent is not part of the replication environment.
Adaptive Server RepAgent Thread	Active	Running	The RepAgent thread is enabled and started.
	Suspended	Stopped	The RepAgent thread is enabled, but stopped.
	Down	Stopped	The RepAgent thread is not enabled.
Replication-Only Adaptive Server	Active	Running	Successfully connected to the Adaptive Server and all RepAgent threads for connections within this environment are enabled and started.
	Down	Stopped	Cannot connect to the Adaptive Server. The server state is also set to DOWN if the user and password are incorrect.
	Unknown	Unknown	The state of the Replication-only Adaptive Server cannot be determined. This also may indicate that the server is not part of the replication environment.