RP/TUX 8.1/TUX 9.1 - TM_TRACE_DISABLE="YES" . ULOG in $APPDIR as well as ULOGPFX (Doc ID 777300.1)

Last updated on NOVEMBER 04, 2016

Applies to:

Oracle Tuxedo - Version: 8.1 to 9.1
Information in this document applies to any platform.
Information in this document applies to any platform
***Checked for relevance on 21-07-2010***

Goal

DESCRIPTION:
If you set ULOGPFX="<SPECIFIED DIRECTORY PATH>" (Where <SPECIFIED DIRECTORY PATH> is something
other than APPDIR) and set the variable TM_TRACE_DISABLE=YES. Every time you perform a tmboot, the process pid is
getting logged in the ULOG under $SWNET_BIN_PATH (APPDIR) in addition to the normal entries in the ulog specified in
the ULOGPFX path thus fragmenting the ulog between two files in different locations. Setting the variable
TM_TRACE_DISABLE=NO stops this ulog fragmentation. 

Further you have an explanation for why you are observing an entry approximately every 2 minutes in an SNL. After
further investigation, found that in SNL a tuxedo client is started every time heart beat is being sent (either 4
minutes or 2 minutes).
The client's pid is getting logged in the ULOG under $SWNET_BIN_PATH (APPDIR).
 
Currently in SNL the variable TM_TRACE_DISABLE has been introduced in the environment. This is leading to a side
effect. 
ULOG's are getting created in every directory from where tmboot and tmshutdown is run. Also a ULOG is getting created
under $SWNET_BIN_PATH (Tuxedo Application Directory). 

When the variable TM_TRACE_DISABLE is set to YES, Tuxedo creates an additional ULOG file under $SWNET_HOME/bin
directory that contains the following lines:

143030.snl!tmshutdown.15034.1.-2: 06-05-2006: Tuxedo Version 8.1, 32-bit 
143030.snl!tmshutdown.15034.1.-2: INFO: TM_TRACE_DISABLE set to YES 
143033.snl!?proc.15035.1.0: 06-05-2006: Tuxedo Version 8.1, 32-bit 
143033.snl!?proc.15035.1.0: INFO: TM_TRACE_DISABLE set to YES 
143033.snl!tmadmin.15039.1.-2: 06-05-2006: Tuxedo Version 8.1, 32-bit 
143033.snl!tmadmin.15039.1.-2: INFO: TM_TRACE_DISABLE set to YES 
143033.snl!tmshutdown.15042.1.-2: 06-05-2006: Tuxedo Version 8.1, 32-bit 
143033.snl!tmshutdown.15042.1.-2: INFO: TM_TRACE_DISABLE set to YES 
143036.snl!tmshutdown.15044.1.-2: 06-05-2006: Tuxedo Version 8.1, 32-bit 
143036.snl!tmshutdown.15044.1.-2: INFO: TM_TRACE_DISABLE set to YES 
143039.snl!tmshutdown.15049.1.-2: 06-05-2006: Tuxedo Version 8.1, 32-bit 
143039.snl!tmshutdown.15049.1.-2: INFO: TM_TRACE_DISABLE set to YES 
143042.snl!tmshutdown.15054.1.-2: 06-05-2006: Tuxedo Version 8.1, 32-bit 
143042.snl!tmshutdown.15054.1.-2: INFO: TM_TRACE_DISABLE set to YES 
143046.snl!tmshutdown.15069.1.-2: 06-05-2006: Tuxedo Version 8.1, 32-bit 
143046.snl!tmshutdown.15069.1.-2: INFO: TM_TRACE_DISABLE set to YES 
143052.snl!tmshutdown.15076.1.-2: 06-05-2006: Tuxedo Version 8.1, 32-bit 
143052.snl!tmshutdown.15076.1.-2: INFO: TM_TRACE_DISABLE set to YES 
143106.snl!?proc.15090.1.0: 06-05-2006: Tuxedo Version 8.1, 32-bit 
143106.snl!?proc.15090.1.0: INFO: TM_TRACE_DISABLE set to YES 
143106.snl!tmshutdown.15094.1.-2: 06-05-2006: Tuxedo Version 8.1, 32-bit 
143106.snl!tmshutdown.15094.1.-2: INFO: TM_TRACE_DISABLE set to YES 

If the variable is not set, the above file is not created. The duplicate file should not be created.

CONFIGURATION:
Tuxedo 8.1  
Sun OS and AIX

Solution

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