Use this command to display the operational state of the database.
You have the DBInfoRead server permission.
db_state [-v]
Option |
Description |
---|---|
-v |
The fill level of the log area and the data area is displayed. |
OK
<operational_state>
Log Full = <value>
Database Full = <value>
Value |
Description |
---|---|
<operational_state> |
Operational state of the database Apart from the regular operational database states described below, transient operational states are possible which are generated by the operating system. ONLINE: The database is ready for operation. ADMIN: The database has been shut down. Only special administrative work can be done. OFFLINE: The database is not ready for operation. STANDBY: The database is in a constant restart state (in hot standby systems only). STOPPED INCORRECTLY: Only with a UNIX operating system: The database stopped after an error. UNKNOWN: The system cannot determine the operational state. |
Log Full = <value> |
Fill level of the log area Possible values are: YES | NO YES: The log area is full. NO: The log area is not full. |
Database Full = <value> |
Fill level of the data area Possible values are: YES | NO YES: The data area is full. NO: The data area is not full. |
Icon |
Operational State |
Description |
---|---|---|
|
ONLINE |
The database is running. Database users can log on and execute SQL statements. The database system administrator and DBM operators can perform administrative tasks. |
- |
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. |