Skip to main content

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

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

Updated on May 17, 2024

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.


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.


  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.

  • Previous topic pyApplication and pyApplicationVersion properties are not captured in the interaction history
  • Next topic Troubleshooting NLP

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