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

DB column of datatype Timestamp stores data without milliseconds



Initiating a Connect SQL rule to insert a DateTime property to a TIMESTAMP column in an Oracle database, stores milliseconds as 000000 instead of the actual value.

For example,

Inserted property value: 20170915T125422.195 GMT
Value actually stored in database column: 15-SEP-2017 08:54:22.000000

Error Messages

Not Applicable

Steps to Reproduce

  1. Create an external database table in Oracle database where one of the columns is a TIMESTAMP.
  2. Create an Connect SQL rule to insert to the table.
  3. Insert a Timestamp value with milliseconds in it when invoking the RDB-SAVE.

Root Cause

This issue was determined to be a product enhancement request.


Perform the following local-change:
  1. Map a class to the database table using the external database class mapping wizard.
  2. Use Obj-Save instead of RDB-Save. Obj-Save stores the millisecond precision.
Suggest Edit

Published February 18, 2018 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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