Content Manager OnDemand Database Tables - Revision history

Jderrick: ibm cmod arsseg - fixed minor typos.

2020-01-07T18:02:32Z

ibm cmod arsseg - fixed minor typos.

← Older revision		Revision as of 18:02, 7 January 2020
Line 443:		Line 443:
	\|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.		\|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.		\|REIMPORTED_DATE\|\|BIGINT\|\|The date the table was re-imported back into DB2 if it was migrated out to secondary (i.e. TSM) storage.
	\|-		\|-
	\|LAST_UPDATE\|\|BIGINT\|\|The date of the last update to the database table (insert / delete / update to rows).		\|LAST_UPDATE\|\|BIGINT\|\|The date of the last update to the database table (insert / delete / update to rows) if this configuration option is enabled.
	\|-		\|-
	\|LAST_BACKUP\|\|BIGINT\|\|The date of the last backup in the segment field format.		\|LAST_BACKUP\|\|BIGINT\|\|The date of the last backup in the segment field format.
Line 457:		Line 457:
	\|UPD_ROWS\|\|BIGINT\|\|The number of rows updated in this table, by the [[arsdoc update]] command.		\|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~~.		\|DEL_ROWS\|\|BIGINT\|\|The number of rows deleted from this table, either by expiration processing, or the [[arsdoc delete]] command.
	\|-		\|-
	\|MOD_ROWS\|\|BIGINT\|\|The number of rows modified in this table.		\|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.		\|MAX_ROWS\|\|BIGINT\|\|The maximum number of rows that this table should contain. 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.		\|DATABASE_NAME\|\|VARCHAR\|\|On partitioned database systems, the name of the database this table is stored in.
	\|-		\|-
	\|FTI_SERVER\|\|VARCHAR\|\|The Full Text Indexing server that contains the full text index for documents contained in this table.		\|FTI_SERVER\|\|VARCHAR\|\|The Full Text Indexing server that contains the full text index for documents contained in this table.

Jderrick: Updated links to application group tables and cmod compression types

2019-08-16T12:58:52Z

Updated links to application group tables and cmod compression types

← Older revision		Revision as of 12:58, 16 August 2019
Line 395:		Line 395:
	\|RID\|\|INTEGER\|\|Unique Resource ID		\|RID\|\|INTEGER\|\|Unique Resource ID
	\|-		\|-
	\|AGID\|\|INTEGER\|\|Numeric Application Group ID that the resource belongs to - See: [[Content_Manager_OnDemand_Database_Tables#arsag_-_Application_Group_Table]]		\|AGID\|\|INTEGER\|\|Numeric Application Group ID that the resource belongs to - See: [[Content_Manager_OnDemand_Database_Tables#arsag_-_Application_Group_Table\|Application Group Table]]
	\|-		\|-
	\|PRI_NID\|\|INTEGER\|\|"Primary" Node ID where the resource is stored		\|PRI_NID\|\|INTEGER\|\|"Primary" Node ID where the resource is stored
Line 401:		Line 401:
	\|SEC_NID\|\|INTEGER\|\|Deprecated		\|SEC_NID\|\|INTEGER\|\|Deprecated
	\|-		\|-
	\|COMP_TYPE\|\|CHARACTER\|\|Compression Type - See: [[Content_Manager_OnDemand_Database_Tables#arsapp..2A_comp_type_-_Data_compression_type]]		\|COMP_TYPE\|\|CHARACTER\|\|Compression Type - See: [[Content_Manager_OnDemand_Database_Tables#arsapp..2A_comp_type_-_Data_compression_type\|Data Compression Types]]
	\|-		\|-
	\|ADD_DATE\|\|BIGINT\|\|Date the resource was added, as the number of seconds since the UNIX Epoch, midnight January 1st, 1970 UTC		\|ADD_DATE\|\|BIGINT\|\|Date the resource was added, as the number of seconds since the UNIX Epoch, midnight January 1st, 1970 UTC

Jderrick: Added more information on SM_CACHE_DELTA.

2019-07-29T12:56:53Z

Added more information on SM_CACHE_DELTA.

← Older revision		Revision as of 12:56, 29 July 2019
Line 67:		Line 67:
	\|MIGR_SRVR_STR		\|MIGR_SRVR_STR
	\|-		\|-
	\|SM_CACHE_DELTA		\|SM_CACHE_DELTA\|\|90,720,3652\|\|Integer\|\|The delta between the previous cache retention setting (SM_CACHE_DOC) and the current value. This allows CMOD to properly retain (or expire) data in the cache that was loaded to the cache filesystem prior to the change of the cache retention setting. Prior to CMOD v7.1.2.8, data loaded into the cache before changing an Application Groups cache retention setting would expire on the schedule that was in effect at the time it was loaded. The value in this field is used during cache expiration processing with [[arsmaint]] to help determine if data should be removed from the cache or not. See [https://www-01.ibm.com/support/docview.wss?uid=swg1PK81019 IBM CMOD APAR on SM_CACHE_DELTA - March 2009]
	\|-		\|-
	\|DATABASE_NAME		\|DATABASE_NAME

Jderrick: /* IBM CMOD Internal Database Tables */

2018-06-12T23:29:37Z

IBM CMOD Internal Database Tables

← Older revision		Revision as of 23:29, 12 June 2018
Line 3:		Line 3:
	= IBM CMOD Internal Database Tables =		= IBM CMOD Internal Database Tables =

	This article is a reference of the contents of database tables inside Content Manager OnDemand. The data on this page is to be considered informational, and may change from version to version, platform to platform. There are also constraints on some fields and values, meaning that unless you fully understand how the values in specific fields work, you may combine features or options that are NOT compatible with each other, leading to unexpected, erroneous, or unintended behavior, up to and including problems with stability and/or reliability, and/or data loss. Use this information at your own risk.		This article is a reference of the contents of database tables inside Content Manager OnDemand. The data on this page is to be considered informational, and may change from version to version, platform to platform. There are also constraints on some fields and values, meaning that unless you fully understand how the values in specific fields work, you may combine features or options that are NOT compatible with each other, leading to unexpected, erroneous, or unintended behavior, up to and including problems with stability and/or reliability, and/or data loss. Use this information at your own risk. This page aims to be a more detailed and complete version of the [https://www.ibm.com/support/knowledgecenter/SSEPCD_9.5.0/com.ibm.ondemand.administeringmp.doc/tables1.htm IBM CMOD System Control Tables].

	= arsag - Application Group Table =		= arsag - Application Group Table =

Jderrick: /* arsag.type - Storage Management Configuration */

2018-06-11T19:20:14Z

arsag.type - Storage Management Configuration

← Older revision		Revision as of 19:20, 11 June 2018
Line 92:		Line 92:
	!Database Value!!Button!!Description		!Database Value!!Button!!Description
	\|-		\|-
	\|1\|\|~~Cache~~: ~~Yes~~\|\|Specifies that the ~~data~~ should be ~~cached~~ in a ~~cache filesystem~~		\|1\|\|Tablespace Type: None\|\|Specifies that the next table for this Application Group should be placed in the default tablespace, which is USERSPACE1 on DB2.
			\|-
			\|16\|\|Tablespace Type: SMS\|\|Specifies that table should be placed in a new SMS table space.
			\|-
			\|65535\|\|Tablespsce Type: Automatic\|\|Specifies that tables should be placed in tablespaces automatically, as determined by your Database Administrator.
			\|-
			\|524288\|\|Compress tables/Tablespaces\|\| If this bit is on, the database will compress table/tablespace data.
	\|-		\|-
	\|}		\|}

Jderrick: Added IBM CMOD arsseg table

2018-03-22T14:43:33Z

Added IBM CMOD arsseg table

← Older revision		Revision as of 14:43, 22 March 2018
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.
	\|}		\|}

Jderrick: Corrected hierarchy of IBM CMOD tables in Table of Contents.

2018-03-22T14:08:54Z

Corrected hierarchy of IBM CMOD tables in Table of Contents.

← Older revision		Revision as of 14:08, 22 March 2018
Line 5:		Line 5:
	This article is a reference of the contents of database tables inside Content Manager OnDemand. The data on this page is to be considered informational, and may change from version to version, platform to platform. There are also constraints on some fields and values, meaning that unless you fully understand how the values in specific fields work, you may combine features or options that are NOT compatible with each other, leading to unexpected, erroneous, or unintended behavior, up to and including problems with stability and/or reliability, and/or data loss. Use this information at your own risk.		This article is a reference of the contents of database tables inside Content Manager OnDemand. The data on this page is to be considered informational, and may change from version to version, platform to platform. There are also constraints on some fields and values, meaning that unless you fully understand how the values in specific fields work, you may combine features or options that are NOT compatible with each other, leading to unexpected, erroneous, or unintended behavior, up to and including problems with stability and/or reliability, and/or data loss. Use this information at your own risk.

	== arsag - Application Group Table ==		= arsag - Application Group Table =

	This table contains all of the configuration data for Application Group Configuration in Content Manager OnDemand.		This table contains all of the configuration data for Application Group Configuration in Content Manager OnDemand.
Line 86:		Line 86:
	\|}		\|}

	=== arsag.type - Storage Management Configuration ===		== arsag.type - Storage Management Configuration ==

	{\|class="wikitable"		{\|class="wikitable"
Line 96:		Line 96:
	\|}		\|}

	== arsag2fol - Application Group to Folder Mapping ==		= arsag2fol - Application Group to Folder Mapping =
	This table is used to map individual Application Groups to individual folders. An Application Group (AGID) may appear multiple times in multiple Folders (FID). ARSAG2FOL also maps individual fields in a folder to specific fields in Application Groups.		This table is used to map individual Application Groups to individual folders. An Application Group (AGID) may appear multiple times in multiple Folders (FID). ARSAG2FOL also maps individual fields in a folder to specific fields in Application Groups.

Line 115:		Line 115:
	\|}		\|}

	== arsagfld - Application Group Fields Table ==		= arsagfld - Application Group Fields Table =

	This table contains a list of all of the fields defined in CMOD Application Groups.		This table contains a list of all of the fields defined in CMOD Application Groups.
Line 161:		Line 161:
	\|}		\|}

	=== arsagfld.mask ===		== arsagfld.mask ==
	'''CAUTION:''' Changing these values without knowledge of how they inter-operate or conflict with each other is dangerous and not supported.		'''CAUTION:''' Changing these values without knowledge of how they inter-operate or conflict with each other is dangerous and not supported.

Line 209:		Line 209:
	\|}		\|}

	== arsann - OnDemand Document Annotation Table ==		= arsann - OnDemand Document Annotation Table =

	{\|class="wikitable"		{\|class="wikitable"
Line 256:		Line 256:
	\|}		\|}

	== arsapp - OnDemand Application Definition Table ==		= arsapp - OnDemand Application Definition Table =

	{\|class="wikitable"		{\|class="wikitable"
Line 299:		Line 299:
	\|}		\|}

	=== arsapp.doc_type - Document type to store ===		== arsapp.doc_type - Document type to store ==

	{\|class="wikitable"		{\|class="wikitable"
Line 328:		Line 328:
	\|}		\|}

	=== arsapp.*_comp_type - Data compression type ===		== arsapp.*_comp_type - Data compression type ==

	{\|class="wikitable"		{\|class="wikitable"
Line 351:		Line 351:
	'''What's the difference between 'None' and 'Disable'?''' The 'none' option doesn't compress the file when it's loaded into CMOD, but WILL attempt to compress it before sending it to the end user at the time it's retrieved. There so few examples of why this would be beneficial, that I can't even think of any to tell you.		'''What's the difference between 'None' and 'Disable'?''' The 'none' option doesn't compress the file when it's loaded into CMOD, but WILL attempt to compress it before sending it to the end user at the time it's retrieved. There so few examples of why this would be beneficial, that I can't even think of any to tell you.

	=== arsapp.idx_type - Indexer for the Application ===		== arsapp.idx_type - Indexer for the Application ==

	{\| class="wikitable" style="text-align:center;"		{\| class="wikitable" style="text-align:center;"

Jderrick: IBM CMOD arsres resource table

2018-02-07T00:46:40Z

IBM CMOD arsres resource table

← Older revision		Revision as of 00:46, 7 February 2018
Line 378:		Line 378:
	\|}		\|}

	=arsres - IBM CMOD Document Resource Table=		= arsres - IBM CMOD Document Resource Table =
			One of the ways that Content Manager OnDemand acheives best-in-class compression is to perform de-duplication on loaded and indexed documents. These duplicate portions of documents are bundled into 'resources' which are stored separately from the data itself, referred to at the time a document is retrieved.

			{\| class="wikitable" style="text-align:left;"
			\|+ IBM CMOD Resource Table Structure
			!Column Name
			!Type
			!Description
			\|-
			\|RID\|\|INTEGER\|\|Unique Resource ID
			\|-
			\|AGID\|\|INTEGER\|\|Numeric Application Group ID that the resource belongs to - See: [[Content_Manager_OnDemand_Database_Tables#arsag_-_Application_Group_Table]]
			\|-
			\|PRI_NID\|\|INTEGER\|\|"Primary" Node ID where the resource is stored
			\|-
			\|SEC_NID\|\|INTEGER\|\|Deprecated
			\|-
			\|COMP_TYPE\|\|CHARACTER\|\|Compression Type - See: [[Content_Manager_OnDemand_Database_Tables#arsapp..2A_comp_type_-_Data_compression_type]]
			\|-
			\|ADD_DATE\|\|BIGINT\|\|Date the resource was added, as the number of seconds since the UNIX Epoch, midnight January 1st, 1970 UTC
			\|-
			\|COMP_SIZE\|\|INTEGER\|\|Compressed Size in bytes
			\|-
			\|DECOMP_SIZE\|\|INTEGER\|\|Decompressed Size in bytes
			\|-
			\|EXP_DATE\|\|BIGINT\|\|Expiration date of the resource, as the number of seconds since the UNIX Epoch, midnight January 1st, 1970 UTC
			\|-
			\|HOLD\|\|SMALLINT\|\|Is the resource part of a document being held by IBM CMOD Enhanced Retention Management?
			\|-
			\|ADD_DT\|\|TIMESTAMP\|\|Date & Time the resource was added in database-native time format.
			\|-
			\|EXP_DT\|\|TIMESTAMP\|\|Date & Time the resource is expected to expire, in database-native time format. This date will be updated as new loads are added to Content Manager OnDemand.
			\|-
			\|HASH_VAL\|\|CHARACTER\|\|Cryptographic Hash of the contents of the resource bundle.
			\|-
			\|CRYPT_STATUS\|\|SMALLINT\|\|Encryption status
			\|}

	= SA2 - IBM CMOD System Load Table =		= SA2 - IBM CMOD System Load Table =

Jderrick: Added IBM CMOD arsres table.

2018-02-06T15:22:59Z

Added IBM CMOD arsres table.

← Older revision		Revision as of 15:22, 6 February 2018
Line 378:		Line 378:
	\|}		\|}

			=arsres - IBM CMOD Document Resource Table=

	= SA2 - IBM CMOD System Load Table =		= SA2 - IBM CMOD System Load Table =

Jderrick: Added Xerox Metacode to IBM CMOD data types table

2017-06-19T15:02:16Z

Added Xerox Metacode to IBM CMOD data types table

← Older revision		Revision as of 15:02, 19 June 2017
Line 313:		Line 313:
	\|x'4A'\|\|J\|\|JPEG\|\|Joint Photographic Experts Group		\|x'4A'\|\|J\|\|JPEG\|\|Joint Photographic Experts Group
	\|-		\|-
	\|x'4C'\|\|L\|\|TXT\|\|L for ~~"log"~~ data. ASCII text.		\|x'4C'\|\|L\|\|TXT\|\|Line data - also used for System Log data. ASCII or EBCDIC text.
			\|-
			\|x'4D'\|\|M\|\|IMG\|\|Xerox Metacode aka 'DJDE'
	\|-		\|-
	\|x'4E'\|\|N\|\|None\|\|There is no document data, just metadata. Primarily used for the System Log.		\|x'4E'\|\|N\|\|None\|\|There is no document data, just metadata. Primarily used for the System Log.