DM_AUDIT
| Column Section | Top of Page |
Table-level Detail
| Description: | used to generically store misc logging information from data management processe |
| Definition: | used to generically store misc logging information from data management processes |
| Table Type: | ACTIVITY |
Column Detail - DM_AUDIT
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| ACTION | VC2(12) | Y | string field describing the type of audit message this row represents |
| AUDIT_DT_TM | DATE | N | date/time row was written |
| AUDIT_ID | NUMBER | N | primary key, uniquely defines the row |
| AUDIT_LEVEL | NUMBER | Y | indicates level of logging each row represents |
| AUDIT_NAME | VC2(100) | N | name field to segregate applications logging from each other |
| TEXT | LONG | Y | actual logged message |
DM_CHG_LOG
| Column Section | Relationship Section | Top of Page |
Table-level Detail
| Description: | DATA MANAGEMENT CHANGE LOG |
| Definition: | Data Management Change Log |
| Table Type: | REFERENCE |
Column Detail - DM_CHG_LOG
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| BLOCKING_LOG_ID | NUMBER | N | Log ID in target environment's dm_chg_log that caused this row to not be allowed to move. This can only happen when the target is a PTAM (Pending Target As Master) target for this row. |
| CHG_DT_TM | DATE | N | Date and Time the log entry was made |
| CHG_LOG_REASON_TXT | VC2(2000) | Y | Column to hold reason for particular LOG_TYPE |
| COL_STRING | VC2(4000) | Y | Column to hold other column values not stored in PK_WHERE |
| CONTEXT_NAME | VC2(256) | Y | Used to group rows together so that they can be moved together later. It is possible to have the same logical row for the same environment but with different context names. |
| DELETE_IND | NUMBER | N | Indicates that data was deleted from the table. |
| DM_CHG_LOG_EXCEPTION_ID | NUMBER | Y | A logical Foreign Key to the top-level column on the DM_CHG_LOG_EXCEPTION table |
| DM_REFCHG_PKW_VERS_ID | NUMBER | N | Indicates format that the pk_where column uses. |
| LOG_ID | NUMBER | N | identifier for log entry |
| LOG_TYPE | VC2(6) | N | Type of item logged. (i.e. REFCHG for reference data changes.) |
| PK_WHERE | VC2(2000) | N | Where clause to qualify using primary key of the table involved. |
| PK_WHERE_HASH | FLOAT | Y | Hash value of PK_WHERE template |
| PK_WHERE_VALUE | NUMBER | N | Where clause to qualify using primary key of the table involved that has been encoded. |
| PTAM_MATCH_HASH | FLOAT | Y | Hash Value of PTAM_MATCH_TEMPLATE |
| PTAM_MATCH_QUERY | VC2(2000) | Y | Column to hold the query that PTAM logic should use to find a blocking row |
| PTAM_MATCH_RESULT | FLOAT | Y | Column to hold the result that PTAM logic should use to find a blocking row. The PTAM_MATCH_RESULT will just be a numerical value that comes from a string being run through the oracle hash function. |
| PTAM_MATCH_RESULT_STR | VC2(4000) | Y | This column will hold the string generated by the PTAM_MATCH_QUERY function whose hash value is already stored in PTAM_MATCH_RESULT |
| RDBHANDLE | VC2(30) | Y | Records the CURRDBHANDLE that inserts/updates the row into this table. |
| SINGLE_PASS_LOG_ID | NUMBER | Y | Column to hold the DM_CHG_LOG.LOG_ID value that required this row to be added to the DM_CHG_LOG. |
| TABLE_NAME | VC2(30) | N | Table name of changed table. |
| TARGET_ENV_ID | NUMBER | N | environment id of target database |
| UPDT_APPLCTX | NUMBER | N | The application context number from the record info block. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
| UPDT_CNT | NUMBER | N | Set to 0 on insert. Incremented by 1 on update. Used to recognize update conflict where data in a row updated by one application is at risk of being lost by a second application attempting to update the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
| UPDT_DT_TM | DATE | N | The date and time the row was last inserted or updated. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
| UPDT_ID | NUMBER | N | The person_id of the person from the personnel table (prsnl) that caused the last insert or update of the row in the table. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
| UPDT_TASK | NUMBER | N | The registered (assigned) task number for the process that inserted or updated the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
Relationship Detail - DM_CHG_LOG
| Child Column in DM_CHG_LOG(FK) | Parent Table Name | Parent Column Name | |
|---|---|---|---|
| Parents: | DM_REFCHG_PKW_VERS_ID | DM_REFCHG_PKW_VERS | DM_REFCHG_PKW_VERS_ID |
DM_CHG_LOG_AUDIT
| Column Section | Top of Page |
Table-level Detail
| Description: | DM Change Log Audit |
| Definition: | Stores audit information generated by the RDDS data mover |
| Table Type: | ACTIVITY |
Column Detail - DM_CHG_LOG_AUDIT
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| ACTION | VC2(15) | Y | Identifies the action taken by the data mover |
| AUDIT_DT_TM | DATE | N | Date and time of the audit |
| DM_CHG_LOG_AUDIT_ID | NUMBER | N | Unique identifier for this table |
| LOG_ID | NUMBER | N | Identifies the change log row being worked on from the Source database (not the same database this table is in). |
| TABLE_NAME | VC2(30) | Y | Identifies the table being worked on |
| TEXT | VC2(1000) | Y | Detail information about the audit |
| UPDT_APPLCTX | NUMBER | N | The application context number from the record info block. |
| UPDT_CNT | NUMBER | N | Set to 0 on insert. Incremented by 1 on update. Used to recognize update conflict where data in a row updated by one application is at risk of being lost by a second application attempting to update the row. |
| UPDT_DT_TM | DATE | N | The date and time the row was last inserted or updated. |
| UPDT_ID | NUMBER | N | The person_id of the person from the personnel table (prsnl) that caused the last insert or update of the row in the table. |
| UPDT_TASK | NUMBER | N | The registered (assigned) task number for the process that inserted or updated the row. |
DM_CHG_LOG_EXCEPTION
| Column Section | Top of Page |
Table-level Detail
| Description: | DM Change Log Exceptions |
| Definition: | Exception table to store reasons for merge exceptions during RDDS process |
| Table Type: | REFERENCE |
Column Detail - DM_CHG_LOG_EXCEPTION
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| COLUMN_NAME | VC2(30) | N | Name of column with exception |
| DM_CHG_LOG_EXCEPTION_ID | NUMBER | Y | A top-level column on the DM_CHG_LOG_EXCEPTION table |
| FROM_VALUE | FLOAT | N | Primary key value from source |
| LOG_TYPE | VC2(6) | N | Type of item logged. For example REFCHG for reference data changes |
| TABLE_NAME | VC2(30) | N | Name of table with exception |
| TARGET_ENV_ID | NUMBER | N | Environment id of target database |
| UPDT_APPLCTX | NUMBER | N | The application context number from the record info block. |
| UPDT_CNT | NUMBER | N | Set to 0 on insert. Incremented by 1 on update. Used to recognize update conflict where data in a row updated by one application is at risk of being lost by a second application attempting to update the row. |
| UPDT_DT_TM | DATE | N | The date and time the row was last inserted or updated. |
| UPDT_ID | NUMBER | N | The person_id of the person from the personnel table (prsnl) that caused the last insert or update of the row in the table. |
| UPDT_TASK | NUMBER | N | The registered (assigned) task number for the process that inserted or updated the row. |
DM_CHG_LOG_SMRY
| Column Section | Top of Page |
Table-level Detail
| Description: | DM Change Log Summary. |
| Definition: | Summary table to store high level condensed information about data stored in DM_CHG_LOG (used in RDDS). It stores row counts of DML changes. |
| Table Type: | ACTIVITY |
Column Detail - DM_CHG_LOG_SMRY
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| LOG_TYPE | VC2(6) | N | Type of item logged. For example REFCHG for reference data changes |
| ROW_COUNT | NUMBER | Y | Number of rows for specified table |
| TABLE_NAME | VC2(30) | N | Name of table changed |
| TARGET_ENV_ID | NUMBER | N | Environment id of target database |
| UPDT_APPLCTX | NUMBER | N | The application context number from the record info block. |
| UPDT_CNT | NUMBER | N | Set to 0 on insert. Incremented by 1 on update. Used to recognize update conflict where data in a row updated by one application is at risk of being lost by a second application attempting to update the row. |
| UPDT_DT_TM | DATE | N | The date and time the row was last inserted or updated. |
| UPDT_ID | NUMBER | N | The person_id of the person from the personnel table (prsnl) that caused the last insert or update of the row in the table. |
| UPDT_TASK | NUMBER | N | The registered (assigned) task number for the process that inserted or updated the row. |