Question

6
Replies
475
Views
SATEESH YENNAM (S_Yennam)
Virtusa Corporation
Senior System Architect
Virtusa Corporation
US
S_Yennam Member since 2014 32 posts
Virtusa Corporation
Posted: May 24, 2017
Last activity: July 12, 2017
Posted: 24 May 2017 1:53 EDT
Last activity: 12 Jul 2017 6:59 EDT
Closed
Solved

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://pdn.pega.com/support-articles/timestamp-column-millisec-issue

Data Integration
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.