Skip to main content
LinkedIn
Copied!

Table of Contents

Values of the pxOutcomeTime property are not unique in the Oracle database

Version:

Only available versions of this content are shown in the dropdown

The type of the pxOutcomeTime property in the PR_DATA_IH_FACT table is by default set to DateTime. In the Oracle database, any records that are written into the PR_DATA_IH_FACT table of the interaction history are stored with one-second precision.

In the Oracle database, records in the PR_DATA_IH_FACT table might be displayed and stored at the same second because of the quick processing of customer responses and the asynchronous execution of web page impressions.

For more information, see When using materialized IH Summaries - latest event counts twice.

Cause

This issue occurs because the Oracle database maintains one-second precision for the DateTime type column.

Records in the PR_DATA_IH_FACT table that have the same time stamp
Eight records have the same time stamp in the px outcome time
                            column.

Solution

  1. Ask the Oracle database administrator to update the PXOUTCOMETIME column type from DATE to TIMESTAMP to increase the time precision.

    After this change, the fractional precision of a second can be set to any number from 0 to 9 (the default is 6).

    For more information, see the Oracle documentation about the TIMESTAMP datatype.

Did you find this content helpful?

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us