ULOG Timestamp Is Not Accurate With ULOGMILLISEC On Windows Platform
(Doc ID 2868060.1)
Last updated on JUNE 20, 2023
Applies to:
Oracle Tuxedo - Version 12.2.2 and laterMicrosoft Windows x64 (64-bit)
Microsoft Windows (32-bit)
Symptoms
When setting ULOGMILLISEC=Y on Windows platform, sometimes ULOG timestamp seems not correct for seconds and milliseconds. we can see 1 seconds shift case like this:
000706.932.SERVER!APPLICATION.640.8760.0:
000706.940.SERVER!APPLICATION.640.8760.0:
000707.993.SERVER!APPLICATION.640.8760.0:
000707.997.SERVER!APPLICATION.640.8760.0:
000707.037.SERVER!APPLICATION.640.8760.0:
000707.039.SERVER!APPLICATION.640.8760.0:
000707.041.SERVER!APPLICATION.640.8760.0:
000706.940.SERVER!APPLICATION.640.8760.0:
000707.993.SERVER!APPLICATION.640.8760.0:
000707.997.SERVER!APPLICATION.640.8760.0:
000707.037.SERVER!APPLICATION.640.8760.0:
000707.039.SERVER!APPLICATION.640.8760.0:
000707.041.SERVER!APPLICATION.640.8760.0:
Above case, 000707.993 and 000707.997 are should be 000706.xxx
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 |