Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Modifying column definitions to use the TIMESTAMP data type in an Oracle database

Updated on December 20, 2021

This content applies only to On-premises and Client-managed cloud environments

If you have an Oracle database, 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, map the DateTime properties to TIMESTAMP columns.

Examples of DateTime properties include the following properties in the PR_DATA_IH_FACTinteraction history table:

  • pxOutcomeTime
  • pxDecisionTime
Pega Customer Decision Hub Installation Guide
The Oracle database administrator performs this task.
  1. Connect to the Pega Platform database.
  2. Modify the column definition for a DateTime property by running the following ALTER script on the database:
    ALTER TABLE <Schema_Name>.<Table_Name> MODIFY <Column_Name> TIMESTAMP
    where:<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:


    To update the column definition for the pxDecisionTime property in the PR_DATA_IH_FACT, run the following script:

    Result: This change does not affect existing records.
  • Previous topic Configuring and starting agent schedules
  • Next topic Removing withdrawn data sets from interaction history summaries

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us