My Oracle Support Banner

Date/Time Fields Not Correctly Audit Logged For Times Between 00:00 And 00:59 (Doc ID 2419747.1)

Last updated on FEBRUARY 28, 2019

Applies to:

Oracle Argus Safety - Version 8.1.2 and later
Information in this document applies to any platform.

Symptoms

Audit records for date/time fields are missing the time component if the time is between 00:00 and 00:59.

E.g. a date/time of 25-DEC-2017 00:45, this will be audited as 25-DEC-2017 with no time component.
When the date/time field updated to 25-DEC-2017 00:59, the audit log would not capture this as a change since it see this as 25-DEC-2017.
If the change is to 25-DEC-2017 01:00 then this will be audited since it is now capturing the time change.

The User Defined Date Fields seem to be audited as expected.

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
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.