How to Trace a Gateway Server
Each gateway server process is traced separately. If you are running more than one gateway server (for example, Microsoft SQL Server and Oracle) and both servers require tracing to be initiated, trace configuration information must be defined for each individual gateway.
To trace a gateway server, three configuration parameters need to be defined:
trace_init
Specifies the type of tracing to be performed. Valid values are provided in the Trace Identifiers table. This parameter defaults to OFF. To specify tracing, enter the desired trace identifiers using the syntax conventions described in Tracing Methods.
trace_file
Specifies the full path name of the file containing the trace output. See Trace Output File for examples.
trace_full
Controls whether time stamps are included with every trace. In addition to time stamps, process ids are included to facilitate tracking specific application clients. Valid values are true (full trace) and false (disable full trace). The default is false. The trace identifiers, ST (disable full trace) and FT (full trace) which are specified with the SET TRACE command, are equivalent to the true and false values in CBF and VCBF.
These configuration parameters are maintained in CBF and VCBF, and are stored in config.dat. Tracing must be explicitly configured using the trace_init parameter to indicate the type of tracing to be performed. For additional details regarding these configuration parameters, see the chapter Gateway Configuration Variables.
Windows example:
Configuration Parameter | Parameter Value |
|---|---|
ii.hostname.gateway.mssql.trace_init: | ERWR |
ii.hostname.gateway.mssql.trace_file: | C:\\EA\\ingres\\files\\my_tracefile.log |
ii.hostname.gateway.mssql.trace_full: | true |
Traces all errors and warning messages to C:\EA\ingres\files\my_tracefile.log. 
UNIX example:
Configuration Parameters | Parameter Value |
|---|---|
ii.hostname.gateway.oracle.trace_init: | ERWR |
ii.hostname.gateway.oracle.trace_file: | /tmp/my_tracefile.log |
ii.hostname.gateway.oracle.trace_full: | true |
Traces all errors and warning messages to /tmp/my_tracefile.log. 
Trace Output File
The trace output file is specified for gateway server tracing in CBF or VCBF using the "trace_file" parameter. If a trace output file is specified, a valid path and filename must be included.
Windows example:
ii.hostname.gateway.mssql.trace_file:'C:\\EA\\ingres\\files\\my_tracefile%p.log' 
Note: Double backslashes indicate the directory path is escaped.
UNIX example:
ii.hostname.gateway.oracle.trace_file: /tmp/my_tracefile%p.log 
Tip: If "%p" is used in the trace file name, a trace file is created per session. The "%p" is replaced with the gateway slave process id.
If no output file is specified, the gateway writes the trace data to a default file based on server class as shown in the following table:
Server Class | Gateway Trace File Name |
|---|---|
mssql | gwmssql.log |
oracle | gworacle.log |
db2udb | gwdb2udb.log |
Last modified date: 08/22/2022