Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Issue with PXCREATEDATETIME mapping to DATE data type



The Reporting performance degrades when using the PXCREATEDATETIME in the Where clause. 

Pega application is a multi-tenant and work tables are partitioned based on the tenant and sub-partitioned using the PXCREATEDATETIME. Most reports (real-time and offline) use PXCREATEDATETIME.

The sub-partition is ignored when the Pega application sends milliseconds part of PXCREATEDATETIME (which is mapped to the Date datatype in Oracle).

Database used: Oracle 12G

Error Messages

Not Applicable

Steps to Reproduce

  1. Create a subpartition on the PXCREATEDATETIME in the work table.
  2. Run the report with PXCREATEDATETIME in the Where clause.  

Root Cause

The Pega application sent milliseconds to the JDBC Driver API irrespective of the DATE or the TIMESTAMP column type because it used the same function call for both. The Driver API formatted the data accordingly as per the column type in the database.


Perform the following local-change:

​​​​​​​Change the column type to TIMESTAMP. It is recommended to revise the partitioning approach.

Published August 15, 2019 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration 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.

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