Timestamp column millisec Issue
After upgrading from Pega 7.1 to 7.2.2, (DB Oracle 11g) the timestamp part of the log no longer stores milliseconds.
The table is created with the affected column as TIMESTAMP(6) datatype intended to store fractional seconds with a precision of 6 digits.
In production and lower environments, all fractional seconds are stored as 000000.
I have seen artical on this please check below URL. I didn't understand if it says this issue resolved from 7.1.8 but I see issue in 7.2.2.
Please suggest me on this.
Node ID: 1271836
After upgrading from Pega 7.1 to 7.2.2, (DB Oracle 11g) the timestamp part of the log no longer stores milliseconds.
The table is created with the affected column as TIMESTAMP(6) datatype intended to store fractional seconds with a precision of 6 digits.
In production and lower environments, all fractional seconds are stored as 000000.
I have seen artical on this please check below URL. I didn't understand if it says this issue resolved from 7.1.8 but I see issue in 7.2.2.
Please suggest me on this.
Node ID: 1271836
SA ID: SA-30961
https://collaborate.pega.com/question/timestamp-column-millisec-issue
Accepted Solution
Virtusa Corporation
US
Hi Celeste,
I have raised SR for this and Pega has confirmed that BIX process is truncating milliseconds while saving it into DB in 7.2.2 and gave HotFix for this issue.
SR No : SR-B51989
HotFix : Hfix-34986
Virtusa
AU
Hello,
Currently PRPC product doesn't have support for TIMESTAMP(6) WITH LOCAL TIME ZONE or TIMESTAMP(6), etc. Only the column type "TIMESTAMP " is supported from PRPC 7.1.8 version. Can you please check if the issue is seen when the column type is "TIMESTAMP".
PFB the support article for your reference:
https://community.pega.com/support/support-articles/oracle-timestamp-not-supported-pega-718
Regards,
Madhuri
Virtusa Corporation
US
Thanks for response Madhuri,
I tried to write a test activity and insert DateTime property into Timestamp Column in DB. Its inserting with Milli seconds as expected. But it’s only issue with BIX Extraction. When I define a Mapping property with DateTime in extract rule and try to execute that rule using BIX process. Its inserting with milli seconds as 000000000.
Any Idea on this ?
Pegasystems Inc.
US
Are you saying that your instance with a datetime property has milliseconds stored in it but when you extract it to a target Oracle database with a timestamp column the millisecond part of the time is replaced with 0s?
Pegasystems Inc.
US
BIX is just writing the property value content. If the instance has the millisecond portion it doesn't make sense that bix would truncate it. Please provide screenshots of the datetime property on the clipboard. Also did you confirm that the target database column is timestamp and not any variation of it.
Accepted Solution
Virtusa Corporation
US
Hi Celeste,
I have raised SR for this and Pega has confirmed that BIX process is truncating milliseconds while saving it into DB in 7.2.2 and gave HotFix for this issue.
SR No : SR-B51989
HotFix : Hfix-34986