Skip to end of metadata
Go to start of metadata

x_cons <database_name> show state

Displays the operational state of the database.

The SERVERDB state is ONLINE




A database can be in the following operational states.

  • ONLINE: The database is running. Database users with the corresponding authorizations can log on and execute SQL statements. The database system administrator and DBM operators can perform administrative tasks. Database administrators execute the majority of administration tasks in this operational state.
  • STANDBY: For standby databases in hot standby systems only. Note that you cannot connect to a standby database. It is in a constant restart state.
  • ADMIN: The database is only available for administration tasks.
  • OFFLINE: The database is not running.

In addition to the operational states, intermediate status is also displayed here. These are short-term statuses occupied by the database when moving between two operational states such as: STARTING, SHUTDOWN, SHUTDOWNKILL, STOP, KILL, ABORT, UNKNOWN.

  • STARTING: The kernel process is currently starting and not ready to receive commands, it is the phase before the ADMIN state.
  • SHUTDOWN: A normal database shutdown was requested ( e.g. by the database administrator)
  • SHUTDOWNKILL: A database shutdown was requested ( e.g. by the database administrator) but an error occurred during the shutdown phase
  • STOP: A database stop was requested (triggering the kernel stop semaphore) without sending a shutdown command. This state will be shown if the database was previously not in state STANDBY or ONLINE.
  • KILL: A database state stop was requested (triggering the kernel stop semaphore) without sending a shutdown command. This state will be shown if the database was previously in state ONLINE or STANDBY or the database received this request but is already stopping or shutting down normally. Runtime internally stops the kernel in crash situation if the kernel cannot detect the error.
  • ABORT: An abnormal database termination caused by an internal error.
  • UNKNOWN: The current state cannot be determined. This error usually occurs if the database kernel has already removed its IPC resources but the process might be alive.