Administering and Monitoring a Secondary Database

The SDS Admin secondary database view enables you to monitor a secondary database. The following image shows an example of the secondary database view in which the Secondary database node and the Journal State and Operational State entity nodes have been expanded.

When attached to a secondary database server, the database view displays a single secondary database entry only.

You cannot start node sampling remotely on a primary server from an SDS secondary server.

For details about using the SDS Administration application, see the following section.

The attribute details for each secondary database, displayed in the Attributes column at the right of the database view when you have expanded a secondary database node and the lower-level nodes, are as follows.

• Secondary database name, specified in the MyName parameter in the [SyncDbService] section of the JADE initialization file

• Operational state

  • Host name

  • Primary database name, specified in the PrimaryServerName parameter in the [SyncDbService] section of the JADE initialization file

  • Database subrole (Native or Relational)

  • State (for example, catching up or disconnected)

  • Tracking status

  • Number of RPS worker threads

  • Last error number

  • Read access enabled (Yes or No)

  • Read access granted (Yes or No)

  • Reorganization status (for example, Not reorging, Seeking Approval, or Offline phase)

  • Reconnection interval (in minutes or in seconds)

  • Connection check interval (in seconds)

  • Synchronization mode, specified by the JournalBlockWrite (default) or JournalSwitch value of the SyncMode parameter in the [SyncDbService] section of the JADE initialization file

  • Recovery required (Yes or No)

    When a secondary server is restarted in an interrupted mode, the recovery required attribute is set. This attribute is reset when the status of the outstanding interrupted transactions have been resolved.

• Journal State

  • Latest ready journal number

  • Last replay journal number

  • Current replay journal number

  • Current replay journal timestamp

  • Next replay journal number

  • Latest ready journal timestamp

  • Last replay journal timestamp

  • Next replay journal timestamp

• Transactions, summarized in the collapsed node as active, interrupted, and total transactions

  • Transaction id

  • User name

  • Transaction start time

  • Status

• Update State (block write synchronization mode only)

  • Transaction id of the maximum stable audit record

  • Transaction id of the maximum replayed audit record

  • Transaction id of the maximum committed audit record

  • Timestamp of the latest stable replayed audit record

  • Timestamp of the latest replayed audit record