Administering an Oracle Tuxedo Application at Run Time

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

About Oracle Tuxedo Diagnostic Tool

This topic includes the following sections:



Diagnostic tool is a Tuxedo command. It provides a convenient way of collecting Tuxedo runtime information, especially when system administrators analyze problems that can only be reproduced in production environment.


Installation Requirements

To use diagnostic tool, install the commands listed in the following table, depending on your platform, and set them in environment variable PATH.

Table 10-1 Installation Requirements
cp, file, gdb, gstack, ldd, lsb_release, ps, rm, strace, which
Solaris X86
cp, dbx, dirname, file, ldd, ps, psig, pstack, rm, showrev, truss, uname, which
Solaris Sparc
cp, dbx, dirname, file ,ldd, ps, psig, pstack, rm showrev, truss, uname, which
cp, dbx, dirname, file, instfix, ldd, oslevel, procstack, ps, rm, truss, uname, which, grep
cp, dirname, file, gdb, ldd, lstrace, ps, pstack, rm, uname, which, ldd,gdb,pstack,uname, swlist
DUMPBIN.exe, cbd.exe, systeminfo.exe, windbg.exe


Using Diagnostic Tool

Diagnostic tool is a Tuxedo command named diagnosetool under TUXDIR/bin.

Setting up Environment Variables

Before using the diagnostic tool, manually fill up diagnoseToolEnvFile file with the following environment variables and put it in TUXDIR/bin directory.

TUXDIR=<Value of Tuxedo Environment Variable TUXDIR>

Absolute pathname of Oracle Tuxedo

APPDIR=<Value of Tuxedo Environment Variable APPDIR>

Absolute pathname of Tuxedo application on the target managed node

TUXCONFIG=<Value of Tuxedo Environment Variable TUXCONFIG>

Absolute pathname of TUXCONFIG file on the target managed node

BDMCIBFUG=<Value of Tuxedo Environment Variable BDMCONFIG>

Absolute pathname of BDMCOBFIG file on the target managed domain


Absolute pathname of diagnosetool
Note: The configuration needs to be done at least one time. All environment variables are indispensable; any configuration change should be manually updated in diagnoseToolEnvFile.

Getting Runtime Information


Diagnostic Tool Options

type <error|crash|hang>

Before using this tool, specify the bug type properly.
Note: For more information about bug type, please see Debug Information.


Turn on TMTRACE and collect the corresponding ULOG file.


Turn on Audit Log and collect the corresponding Audit log if the issue relates to Tuxedo Domain.





trace <executable_with_option>

Collect trace from a specific program by executable_with_option.

core <core_path>

This option is used with option type crash to specify the absolute pathname of core file.

pid <process_number>

This option only can be used with option type hang to specify the process ID.


Debug Information

Debug Information Categories

There are three problem types.

Debug Information for Each Category

You can get different debug information according to different problem types.

Note: Please run diagnostic tool by the same owner during the running process.

The followings are general information.

Under product root directory, log/<year>.<month>.<day>-<hour>.<minute>.<second> sub-directory keeps all debug information and may contain the following files.


It is required. It contains general information.


It is required. It is BB dump file.


It contains OS Patch information.
Note: It is not supported on Linux platforms.


It contains Get System Call Trace when specific commands are running.
Note: It is not supported on Windows platforms.


It is UBBCONFIG file, only generated when option UBB is used.


It is DMCONFIG file, only generated when option DMC is used.

  Back to Top       Previous  Next