How to set the APPX_DBG_CODE to log specific RDBMS activity

The APPX_DBG_CODE environment variable controls the amount of information written to the APPX_SQL_CMD log file.  APPX_DBG_CODE is a 32-bit bit mask - if a bit is on, the corresponding information will be logged.


Here are the current (01/22/98) bit definitions:


0x00000001 -    Log all generated SQL commands

0x00000002 -    Log status codes returned from server (*)

0x00000004 -    Log all fetch attempts (*)

0x00000008 -    Log all engine level operations (*)

0x00000010 -    Log all connection-related operations (*)

0x00000020 -    Log binding summary (*)

0x00000040 -    Log binding details (*)

0x00000080 -    Log column/field mappings

0x00000100 -    Enable server logging mechanism (Oracle only)

0x00000200 -    Enable result (null/non-null) logging (*)

0x00000400 -    Log negotiations for server options (such as packet size)

0x00000800 -    Log all records returned from server

0x00001000 -    Currently undefined

0x00002000 -    Log proxy locking operations (Sybase/ODBC only)

0x00004000 -    Time individual operations (use 0x10000 instead)

0x00008000 -    Enable server-side statistics (if capable)

0x00010000 -    Gather per-table timing statistics

0x00020000 -    Enable "show plan" feature on server, generates voluminous logs

0x08000000 -    Write server-based log to "/tmp/syblog" (Sybase only)

0xFFFFFFFF -    Logging all activity


Definitions marked with (*) are for internal debugging purposes only - they
provide very little useful information.