Try OpenEdge Now
skip to main content
DataServer for Oracle
Connecting the DataServer : Connection failures and OpenEdge responses : Accessing the DataServer log using qt_debug logging options

Accessing the DataServer log using qt_debug logging options

OpenEdge supports a log file named dataserv.lg that is dedicated to tracking information related to DataServers. Information about the processes for all DataServers is located in this single file. The log file provides a useful record of connection and disconnection processes and error messages that you can use to diagnose problems or failures. In addition, for platforms that dynamically load the Oracle shared library, information about the library is stored in the log file. For each process, the log provides the process identification number, physical database name, database type, user ID, and a message about the status of the process. Here is an excerpt from a sample DataServer log file:
Wed Oct 29 12:28:53 2007
12:28:53 (pid 242) : Remote ORACLE server begin. (1897)
12:28:53 (pid 242) : Executable was compiled on Sep 2 2003 at 20:11:23 (5067)
12:28:53 (pid 242) : Login to dataserver db as user X. (2689)
12:28:54 (pid 242) : ORASRV version 12 (6440)
12:28:54 (pid 242) : Using shared library c:\orant\Oracle901\bin\OCI.DLL (oci 8.1)
12:28:54 (pid 242) : ORACLE_HOME set to 'c:\orant\oracle901'
12:28:55 (pid 242) : -Dsrv qt_debug: 0 (0x0 None) (6489)
12:28:55 (pid 242) : Cursor limit: 84 (-c setting) (6490)
Note: The log output sample shown above is generated using the qt_debug logging option and not the Enhanced logger.
The query-tuning DEBUG option causes the DataServer to write information about the SQL that it generates to the dataserv.lg file as well. You can access the DataServer log file using the host machine.
* Naming the log file
* Setting the log file location
* Handling log file creation errors
* Restrictions on dynamic changes to log file
* Using the $UNIQUE_DSLOG environment variable