Question
Is it okay to truncate milliseconds from timestamps when migrating from Pega 7.2.1 on Postgres to Pega 7.2.1 on Oracle?
I am migrating from Pega 7.2.1 on postgres to Pega 7.2.1 on Oracle. For some base Pega tables, such as case history tables, the data types are different and create a potential problem. Because these are parts of the Pega platform, not custom elements from my application, I want to take direction on this from Pega. I don't want to make a decision that breaks an essential part of the Platform.
For instance,
pc_history_work.pxcreatedatetime
- in Postgres, the column is of time timestamp, with 6 digits of millisecond precision in the data. Example: 2016-03-30 13:38:07.641238
- in Oracle, the column is of time Date
pc_history_work.pxsavedatetime
- in Postgres, the column is of time timestamp, with 3 digits of millisecond precision in the data. Example: 2016-03-30 13:38:07.545
- in Oracle, the column is of time Date
On Oracle, the Date type will not accept the milliseconds. Which is the recommended practice:
- truncate the milliseconds?
- change the column type?
- something else?
The attached .txt file is a sample of date, exported from Postgres, in .csv format. This website won't allow me to post .csv, so I changed the extension.
Cheers,
Elliott
Hi,
Are you facing any issues while migrating data from Postgress to Oracle database ?, If you are not facing the issue please ignore this milliseconds. Oracle database stores without this.