Tuxedo With Oracle XA: Some Tuxedo Servers Stay Attached For Ever To Old Oracle XA Logging Files (xa_[NAME_In_OpenInfo|NULL]MMDDYYYY.trc)
(Doc ID 1575811.1)
Last updated on MAY 19, 2020
Applies to:Oracle Tuxedo - Version 10.3.0 and later
Information in this document applies to any platform.
When the Oracle XA logging (set in the OPENINFO String the parameters: DbgFL, Log, NAME) feature had been enabled, the output of Unix command: fuser against xa_[NAME_In_OpenInfo|NULL]MMDDYYYY.trc files contains Tuxedo Server PIDs against old xa_xa_[NAME_In_OpenInfo|NULL]MMDDYYYY.trc files (not the one of current day).
Here after the output on Unix prompt of command "date ; fuser":
Tuxedo servers with pids: PID1 PID2 PID3 PID4 are still attached to the old xa_NULL05202013.trc when you expected it would be attached to current trc.
Note that Tuxedo Serves will stay attached to these old xa_[NAME_In_OpenInfo|NULL]MMDDYYYY.trc files for ever.
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