In the Column List:
- P = Primary key
- M = Mandatory field
- F = Foreign key (where the term is used loosely to indicate a surrogate key reference to a field in another table, not a formal constraint)
- DV = Default value
- In the Data Type column, varchar/nvarchar means that the data type is varchar except in multi-language databases that use Unicode, in which case the data type is nvarchar. (The Info Mart database in Cloud deployments is not multi-language.)
This table stores information about errors that Genesys Info Mart encounters during transformation of configuration data. Errors are detected through verification of relationships between primary and foreign keys in tables that store related data.
For example, a record in a table that stores configuration object relationship data (such as GIDB_GCX_CAMPLIST_INFO) would refer to a record in a table that stores configuration object data (such as GIDB_GC_CAMPAIGN). The transformation logic interprets the absence of the record that has the primary key as an error (in the GIDB_GC_CAMPAIGN table, in the example); the error indicates the absence of the related data (such as the Campaign configuration object). As a result, the transformation job encounters a foreign key constraint violation and stores a record in the STG_IDB_FK_VIOLATION table that identifies the two involved tables and the key that caused the violation.
Hint: For easiest viewing, open the downloaded CSV file in Excel and adjust settings for column widths, text wrapping, and so on as desired. Depending on your browser and other system settings, you might need to save the file to your desktop first.
The primary key for this table.
The surrogate key that is used to join to the CTL_AUDIT_LOG dimension.
The name of the table whose record includes a foreign key that violates the foreign key constraint. (Continuing with the example that is used in the table description, the value of this field would be GIDB_GCX_CAMPLIST_INFO.)
The name of the table in which a record appears to be missing, based on the foreign key constraint violation in another table. (In the preceding example, the value of this field would be GIDB_GC_CAMPAIGN.)
The primary key of the record that exists in the table that is specified by FK_TABLE_NAME and that violates the foreign key constraint. Use this value to identify the problematic record. (In the preceding example, the value would come from the GIDB_GCX_CAMPLIST_INFO.ID field, which is the primary key of the GIDB_GCX_CAMPLIST_INFO table.)
The foreign key of the record that exists in the table that is specified by FK_TABLE_NAME and that violates the foreign key constraint. Use this value to identify the missing record in the table that is specified by PK_TABLE_NAME. (In the preceding example, the value would come from the GIDB_GCX_CAMPLIST_INFO.CAMPAIGNID field, which is the foreign key of the GIDB_GCX_CAMPLIST_INFO table and which points to the primary key in the GIDB_GC_CAMPAIGN table. Thus, a Campaign object data is detected to be missing.)
The UTC-equivalent date and time at which the ETL job created a record in this table.
Identifies the 15-minute interval in which the ETL job created a record in this table.
No subject area information available.