Enabling Tracing for the ODBC Client Core

Enabling tracing for the ODBC Client Core tracks network calls, internal driver calls, external calls from the driver and provides ErrorStack information that is useful when troubleshooting network and SSL-related problems. When enabled, CCORE-trace messages are written to the slxpid.log file in the following location, where installdir is your OpenAccess Client installation directory:

To enable tracing for the ODBC Client Core, define a log level in the following section in the ivoa27.ini file:

[Logging]
Logging=LogLevel

where LogLevel is one of the following values:

1 logs externals calls.

2 logs the contents of the ErrorStack.

3 logs log external calls and logs the contents of the ErrorStack.

4 logs internal calls.

7 logs all information.

Example slxpid.log File

The following example shows sample contents of an slxpid.log file when Logging is set to 2 (ErrorStack logging):

CORE: Dump ErrorStack...
CORE: # Errors: 14
CORE: Severity: 50
CORE: Time: Wed Apr 24 07:14:28 2014
CORE: Id: 11004
CORE: Origin: 27
CORE: Description: The requested name is valid, but no data of the requested type was found.
CORE: FromFunction: getaddrinfo
CORE: InFunction: TrEndPoint_ActiveOpen
CORE: Line: 6047
CORE: Params: <NULL>
CORE: ----------------
CORE: Severity: 50
CORE: Time: Wed Apr 24 07:14:28 2014
CORE: Id: 9
CORE: Origin: 51
CORE: Description: Transport endpoint error
CORE: FromFunction: TrEndPoint_ActiveOpen
CORE: InFunction: SESSION_TrEndPoint_Connect
CORE: Line: 6154
CORE: Params: <NULL>
...