Traces for Error Diagnosis

This section describes the traces available for error diagnosis when using Natural with Entire Access:

Use these traces only when Software AG Support requests you to do so.


Traces Under UNIX

Natural Client Trace

Natural can invoke a trace as follows:

$ SQL_TRACE=4
$ export SQL_TRACE

This trace is located in the Temporary Files Path directory. It uses your user ID and trace iteration number; for example: JOHNDOE001.TRC

The Natural client trace can also be enabled via the Natural Configuration Utility (Natural Version 6.2 or above).

Entire Access Client Trace

An Entire Access client can invoke a trace as follows:

$ VORTEX_API_LOGFILE=$OSXDIR/$OSXVERS/trace
$ VORTEX_API_LOGOPTS=FULL
$ export VORTEX_API_LOGFILE VORTEX_API_LOGOPTS

Entire Access Server Trace

An Entire Access server can invoke a trace as follows:

$ VORTEX_HOST_LOGFILE=$OSXDIR/$OSXVERS/htrace
$ VORTEX_HOST_LOGOPTS=FULL
$ export VORTEX_HOST_LOGFILE VORTEX_HOST_LOGOPTS

Traces Under Windows

Natural Client Trace

Natural can invoke a trace as follows:

SQL_TRACE=4

This trace is located in the Temporary Files Path directory. It uses your user ID and trace iteration number; for example: JOHNDOE001.TRC

The Natural client trace can also be enabled via the Natural Configuration Utility (Natural Version 6.2 or above).

Entire Access Client Trace

An Entire Access client can invoke a trace as follows:

VORTEX_API_LOGFILE=file-name
VORTEX_API_LOGOPTS=FULL

Entire Access Server Trace

An Entire Access server can invoke a trace as follows:

VORTEX_HOST_LOGFILE=file-name
VORTEX_HOST_LOGOPTS=FULL

ODBC Trace

ODBC tracing is enabled using the ODBC Manager.