Modifying column definitions to use the TIMESTAMP data type in an Oracle database
This content applies only to On-premises and Client-managed cloud environments
If you have an Oracle database and you use materialized interaction history summaries, modify the column definitions for DateTime properties to use the TIMESTAMP data type.
TIMESTAMP columns provide high-precision time to track customer responses by milliseconds. To store records with greater precision and to avoid duplicate data issues that might occur when you use DATE data type columns, convert the DateTime properties to make them map to TIMESTAMP columns.
Examples of DateTime properties include the following properties in the PR_DATA_IH_FACTinteraction history table:
- pxOutcomeTime
- pxDecisionTime
- Connect to the Pega Platform database.
- Modify the column definition for a DateTime property by running the following
ALTER script on the database:where:
ALTER TABLE <Schema_Name>.<Table_Name> MODIFY <Column_Name> TIMESTAMP<Schema_Name> is the name of the schema that contains the table. <Table_Name> is the name of the table that you want to modify. <Column_Name> is the name of the column whose definition you want to modify. For example: To update the column definition for the pxOutcomeTime property in the PR_DATA_IH_FACT table, run the following script:
ALTER TABLE pegadata.PR_DATA_IH_FACT MODIFY pxOutcomeTime TIMESTAMPTo update the column definition for the pxDecisionTime property in the PR_DATA_IH_FACT, run the following script:
ALTER TABLE pegadata.PR_DATA_IH_FACT MODIFY pxDecisionTime TIMESTAMPResult: This change does not affect existing records.
Previous topic Enabling decision management nodes Next topic Optional: Enabling the FinalizeFileDBTemplate queue processor