This view shows the state of the reference database replica on the node.

This view is also available as an LMV (local view per node) view.

Column Name



The node ID for the node that originated this replication management row.


Internal ID for replication management. Useful for cross-referencing with tracelogs.


The ID of this distributed database, in the sharded database table of cluster database metadata.


The ID of the node that hosts this reference database replica. Will be the same value as NODE_ID.


The role of this instance in cluster metadata. Possible values: Master, Async Replica, Unrecoverable, Paused Replica.


The role of this instance locally on the node where it exists. Possible values: Master, Replica, Transitioning, Dropping or Reprovisioning, Unrecoverable, Recovering, Missing (disconnected).


Whether the database is a DR replica or not, and if so whether it is paused or not. Possible values: Not DR, Active DR, Paused DR.


Term uniquely identifies a period during which an instance of a database is a master. This holds the term of the master in metadata - it will always match LOCAL_TERM if this instance’s METADATA_ROLE is Master.


Term uniquely identifies a period during which an instance of a database is a master.


The last iteration counter on which this state was updated. Used to cross-check with the other replication management tables.


Name of the database.


Records whether the runtime state for this reference database was successfully updated or not (this includes partition boundaries, for example). This is not used to take an action, but is only used to determine whether an iteration of the replication management thread succeeded or not.

Last modified: September 14, 2022

Was this article helpful?