Invalid Timestamp Found in CHANGE_HISTORY Table of Agile Database for a Specific Change Even Though the Local Client Time in the History tab Shows Correctly
(Doc ID 2981852.1)
Last updated on JANUARY 24, 2024
Applies to:
Oracle Agile Product Collaboration - Version 9.3.6.0 and laterInformation in this document applies to any platform.
Symptoms
Invalid Timestamp in AGILE.CHANGE_HISTORY table for a specific change.
When querying for CHANGE_HISTORY record of the change, see there is row with TIMESTAMP having date before the creation date.
The Local Client Time in the History tab of the Change shows correctly.
The issue can be reproduced at will with the following steps:
- Log into Web Client, and open a Change, and check the date showing in Date Originate field. (i.e. 07-SEP-23)
- Log into sql developer as agile database user, and run below sql:
- See there is row that shows timestamp older than the date created. (i.e. 01-DEC-02)
- From Web Client, go to History tab of the Change. Can see the dates in Local Client Time field show correctly.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |