Tuxedo ULOG With Incorrect Timestamp Order

(Doc ID 1539959.1)

Last updated on MARCH 17, 2017

Applies to:

Oracle Tuxedo - Version 9.1 and later
Information in this document applies to any platform.


 In ULOG we can see

110502.xxxxx!tux_dist.22667.1.0: LIBTUX_CAT:262: INFO: Standard main starting
111711.xxxxx!tmadmin.18532.1.-2: 03-13-2013: Tuxedo Version 9.1, 32-bit
111711.xxxxx!tmadmin.18532.1.-2: TMADMIN_CAT:1330: INFO: Command: bbc
101711.xxxxx!BBL.2173.1.0: LIBTUX_CAT:541: WARN: Server GRP_EXP/3580 terminated
101711.xxxxx!TMSYSEVT.2205.1.0: LIBTUX_CAT:1477: ERROR: .SysServerDied: tux_ulog, group GRP_EXP, id 3580 server died


It seems like the timestamps are in incorrect order.




Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms