skip to main content
Troubleshooting the OpenAccess SDK Server : Debug Log Files : Session Debug Log Files
 

Session Debug Log Files

The OpenAccess SDK Server session debug log files contain information related to all processing that occurs in the context of a client session. This pair of files includes a server session debug file and an IP session debug file. The IP session debug file contains information from the IP and the OpenAccess SDK SQL engine. Each debug log file includes a fixed header that contains installation-specific information.
When you consult technical support, you may be asked for the contents of these log files. The names and location of the OpenAccess SDK Server Session debug log files depend on your OpenAccess SDK Server platform.
The information that is logged depends on the value set for the ServiceDebugLogLevel and the ServiceIPLogOption service attributes. By default, logging is enabled for Fatal Error messages in ServiceDebugLogLevel and Enable Error Tracing in ServiceIPLogOption. Enabling additional logging levels uses large amounts of disk space and slows processing. We recommend that you enable these additional levels only while you are troubleshooting. How you turn on and off the logging option depends on your OpenAccess SDK Server platform. See Configuring Logging for information about setting debug levels.

Log File Names

The session debug log file name is:
servicename_processid_sessionid.log
where:
servicename is the name of the OpenAccess SDK service.
processid is the numeric process identifier assigned by the operating system for the OpenAccess SDK service process.
sessionid is a unique numeric identifier of the session. For example:
OpenAccessSDK810_C_5992_0000001.log
The IP session debug log file name has a suffix of -IP appended to the file name, for example:
OpenAccessSDK810_5992_0000001-IP.log

Log File Location

The ServiceDebugLogPath service attribute specifies the location of the files. For more information about specifying OpenAccess SDK service attributes, refer to the OpenAccess SDK Administrator’s Guide.