Decimal

Hexadecimal

Description

0

0

Tracing is disabled.

1

0x1

Writes log messages to the trace file in addition to trace information.

2

0x2

Traces all SQL commands as the DATABridge Client passes them to the relational database. Typically, these messages are SELECT or UPDATE SQL statements and stored procedure calls.

4

0x4

Traces all DBServer or DBEnterprise communications and key actions associated with DATABridge on the host, including RPC calls such as DB_SELECT and DB_READ and their responses.

8

0x8

Traces information on the DATABridge Client control tables as they are loaded from the relational database (that is, load tracing).

16

0x10

Relational database API tracing, which traces calls from the DATABridge Client to the ODBC, OCI or CLI APIs.

32

0x20

Traces the records that are written to temporary data files (or UNIX pipes) and used by the bulk loader utility during the data extraction phase of cloning.

64

0x40

Traces information exchanged between the DBServer on the host or DBEnterprise and the DATABridge Client. The blocks of data are traced as they are read and written to the TCP interface. The messages are listed in DEBUG format, which is an offset followed by 16 bytes in hexadecimal, followed by the same 16 bytes interpreted as EBCDIC text. The non-printable EBCDIC characters are displayed as periods (.).

128

0x80

Traces all messages that are routed through the Client service (primarily messages from the Client Console and Client Configurator to the client, DBClient).

256

0x100

Traces debugging output that is temporarily added to the DATABridge Client (primarily engineering releases).

512

0x200

Displays the configuration file parameters as they are processed.

1024

0x400

Traces information exchanged between DBClient (or DBClntCfgServer) and the service. The output looks like a DBServer protocol trace, except for the fact that all the data is ASCII.

2048

0x800

Enables SQL tracing while running user scripts during define and redefine commands.

4096

0X1000

Controls whether or not the Read_CB exit line is printed in the trace file. This option is useful only for determining when the execution of a SQL statement ends because the start of the subsequent wait for TCP input is not traced.

Log Option Example
(Decimal and Hexadecimal)

Result

dbutility -t 7
dbutility -t 0x7

Traces log data (1), SQL (2) and host events (4)

dbutility -t 8191
dbutility -t 0x1FF
dbutility -d

Traces all events listed in the table on the previous page