Infodb Command Output – Database Information Section
The following is sample output from the database information section. This guide includes the callouts (1) and (2) to aid in explanation:
(1)================11-FEB-2009 14:05:55.02 Database Information============
Database : (demodb,kbref) ID : 0x2D5BF682 Default collation : default
Unicode enabled : Yes
Always logged: No
X100 supported: Yes
Default unicode collation : udefault Unicode normalization : NFC
Extents : 5 Last Table Id : 341
Config File Version Id : 0x00060001 Database Version Id : 8
Mode : DDL ALLOWED, ONLINE CHECKPOINT ENABLED
Status : VALID,JOURNAL,CKP,DUMP,ROLL_FORWARD,CFG_BACKUP,X100_EXIST
(2) The Database has been Checkpointed.
The Database is Journaled.
MVCC is enabled in this database.
Journals are valid from checkpoint sequence : 2
Fields are as follows:
At (1)
Identifies the date and time the infodb operation was run.
Database
Identifies the name (demodb) and owner (kbref) of the database.
ID
Shows the internal identifier of the database.
Default collation
The default collation name.
Unicode enabled
Whether the database can contain Unicode data types.
Always logged
Whether all operations on this database must be logged.
X100 supported
Whether the database allows the use of X100 tables and operations.
Default unicode collation
The default collation for Unicode columns.
Unicode normalization
The normalization form of the database.
Extents
Indicates the number of locations the database is using.
Last Table ID
Indicates the integer identifier assigned to the last created table.
Config File Version ID
Shows the major (upper 2 bytes) and minor (lower 2 bytes) versions of the configuration file.
Database Version ID
The version of DMF that created the database. Note that this is not related to the Ingres version of the database.
Status
Displays status information for the database. Status abbreviations are as follows:
CFG_BACKUP—automatic backup of the configuration file is enabled. A copy of the database configuration file is maintained in the II_DUMP location as a backup.
CKP—indicates that you must perform a rollforwarddb +c (back to checkpoint) before you can do a rollforwarddb -c +j..
DUMP—the database has undergone dump processing (that is, a dump file was created in the dump location) via some online checkpoint
JOURNAL—the database is journaled.
JOURNAL_DISABLED—journaling has been disabled.
NOLOGGING—the database has been opened by a SET NOLOGGING session. Note that if this session encounters an error, the database will be marked inconsistent.
ROLL_FORWARD—indicates that rollforward is available on the database and has not been run to completion since the last checkpoint was taken.
SMINC—indicates the system catalogs are in an inconsistent state.
VALID—the database is consistent and available for use. If this does not appear, the database is marked inconsistent.
X100_EXIST—X100 tables may exist in the database so an X100 engine must be run. This flag can be turned off only by running sysmod, if no X100 tables exist. Dropping X100 tables does not turn the X100_EXIST flag off. Ingres avoids running an X100 engine for a database that does not show X100_EXIST.
X100_DISABLED—X100 operations are disabled (through alterdb -disable_x100).
At (2)
This section displays comments on the status of the database. Important state information is shown.
The Database is Inconsistent. Cause of Inconsistency: <...>
Shown if the database is inconsistent. The cause of inconsistency can be one of the following:
NOLOGGING_ERROR—a transaction failed while the database was in the nologging state.
NOLOGGING_OPENDB—the database was opened for the first time, but was in the nologging state. This means a session exited abnormally.
OPEN_COUNT—the database was opened for the first time, but the database open count in the configuration file was not zero. This means the configuration file could not be read during a recovery attempt.
REC_OPEN_FAILURE—the RCP could not recover a database because the database could not be opened.
RECOVER_ERROR—the RCP failed to recover a database due to an unexpected logging system or recovery protocol problem.
REDO_ERROR—the RCP failed to recover a database due to an error in REDO processing.
RFP_FAIL—the rollforward of the database level checkpoint failed.
UNDO_ERROR—the RCP failed to recover a database due to an error in UNDO processing.
WILL_COMMIT_ERR—the RCP was unable to restore a transaction to the willing commit state.
The Database has been Checkpointed.
Shown if the database has been checkpointed.
The Database is Journaled. or The Database is not Journaled.
Shows the journaling status.
Journaling has been disabled on this database by alterdb. Run 'ckpdb +j' to re-enable journaling.
Shown if journaling has been disabled.
Database is being accessed with Set Nologging, allowing transactions to run while bypassing the logging system.
Shown if a set nologging session is active on the database.
MVCC is {enabled | disabled} in this database.
Shows whether multiversion concurrency control is enabled.
Journals are valid from checkpoint sequence: checkpoint sequence number
Shows the earliest checkpoint from which rollforward is allowed.
Journals are not valid from any checkpoint.
Shown if rollforward is not valid from any checkpoint, or there are no checkpoints.