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".
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 ?
Posted: 4 years ago
Posted: 30 May 2017 8:17 EDT
Celeste Dufresne (CelesteDufresne_GCS)
Principal Software Solutions Engineer
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?
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.