1,126
edits
Difference between revisions of "Content Manager OnDemand Database Tables"
Jump to navigation
Jump to search
Content Manager OnDemand Database Tables (view source)
Revision as of 14:43, 22 March 2018
, 14:43, 22 March 2018Added IBM CMOD arsseg table
m (Corrected hierarchy of IBM CMOD tables in Table of Contents.) |
(Added IBM CMOD arsseg table) |
||
| Line 414: | Line 414: | ||
|- | |- | ||
|CRYPT_STATUS||SMALLINT||Encryption status | |CRYPT_STATUS||SMALLINT||Encryption status | ||
|} | |||
= arsseg - IBM CMOD Segment Table = | |||
The segment table keeps track of how Application Group tables are segmented -- generally by the 'Maximum Segement Size' parameter in the Application Group configuration, in the advanced pane. Dates in this table are formatted as per the Application Group date format that is selected as the Segment Field (by the checkbox 'Segment' in the Field Information Tab in the Application Group configuration in the IBM CMOD Admin client. This means that old-style date/time formats use the UNIX epoch format (number of seconds since January 1st, 1970, UTC) and the old-style CMOD date format (number of days since January 1st, 1970). In versions of IBM CMOD v9.0 and higher, field names that end in _DT use the internal database timestamp format. | |||
{| class="wikitable" style="text-align:left;" | |||
|+ IBM CMOD Segment Table Structure | |||
!Column Name | |||
!Type | |||
!Description | |||
|- | |||
|AGID||INTEGER||Application Group ID number | |||
|- | |||
|TABLE_NAME||VARCHAR||Table name in AGID_NAME+DBSEG format from ARSAG table | |||
|- | |||
|START_DATE||BIGINT||The minimum value of the segment field (date) in this segment / table. | |||
|- | |||
|STOP_DATE||BIGINT||The maximum value of the segment field (date) in this segment / table. | |||
|- | |||
|POST_DATE||BIGINT||The date the segment/table was created. | |||
|- | |||
|CLOSED_DATE||BIGINT||The date the segment/table was closed, either by becoming full (ARSAG.MAX_ROWS) or being forced closed by the IBM CMOD arstblsp utility. | |||
|- | |||
|REIMPORTED_DATE||BIGINT||The date the table was re-imported back into DB2 if it was migrated out to secondary (TSM) storage. | |||
|- | |||
|LAST_UPDATE||BIGINT||The date of the last update to the database table (insert / delete / update to rows). | |||
|- | |||
|LAST_BACKUP||BIGINT||The date of the last backup in the segment field format. | |||
|- | |||
|LAST_STATS||BIGINT||The last time database statistics were run by the arsdb & arsmaint utilities. | |||
|- | |||
|MASK||INTEGER||A vectored field containing configuration data about the table. | |||
|- | |||
|INS_ROWS||BIGINT||The number of rows inserted into this table. | |||
|- | |||
|UPD_ROWS||BIGINT||The number of rows updated in this table, by the [[arsdoc update]] command. | |||
|- | |||
|DEL_ROWS||BIGINT||The number of rows deleted from this table, either by expiration processing, or the [[arsdoc delete]] format. | |||
|- | |||
|MOD_ROWS||BIGINT||The number of rows modified in this table. | |||
|- | |||
|MAX_ROWS||BIGINT||The maximum number of rows that this table has ever contained, this value is provided by ARSAG.MAX_ROWS at creation time. | |||
|- | |||
|DATABASE_NAME||VARCHAR||On partitioned database systems, the name of the database this table is stored. | |||
|- | |||
|FTI_SERVER||VARCHAR||The Full Text Indexing server that contains the full text index for documents contained in this table. | |||
|- | |||
|START_DT||TIMESTAMP||The minimum (oldest) date of documents stored in this folder, in database-native timestamp format. | |||
|- | |||
|STOP_DT||TIMESTAMP||The maximum (newest) date of documents stored in this folder, in database-native timestamp format. | |||
|- | |||
|POST_DT||TIMESTAMP||The date this table was created, in database-native timestamp format. | |||
|- | |||
|CLOSED_DT||TIMESTAMP||The date this table was closed (by being full, or by the IBM CMOD arstblsp command), in database-native timestamp format. | |||
|- | |||
|REIMPORTED_DT||TIMESTAMP||The date the table was re-imported into the database (after being exported to secondary storage), in database-native timestamp format. | |||
|- | |||
|LAST_UPDATE_DT||TIMESTAMP||The date the table was last updated, in database-native timestamp format. | |||
|- | |||
|LAST_BACKUP_DT||TIMESTAMP||The date the table was last backed up, in database-native timestamp format. | |||
|- | |||
|LAST_STATS_DT||TIMESTAMP||The date the table last had database statistics collected, in database-native timestamp format. | |||
|} | |} | ||