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 NOVEMBER 04, 2016

Applies to:

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

Symptoms



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":

 

       $ fuser xa_NULL05202013.trc
       Tue May 28 15:35:04 CEST 2013
       xa_NULL05202013.trc: 11862114 35782730 36044908 36765822


So even the current date is May the 28th, the Tuxedo servers with pids: 11862114, 35782730, 36044908 and 36765822 are still attached to the xa_NULL05202012.trc created on May the 20th whereas you expected it would be attached to xa_NULL05282012.trc.

So it means that Tuxedo Serves will stay attached to these old xa_[NAME_In_OpenInfo|NULL]MMDDYYYY.trc files for ever.



Cause

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