What Database Activity Can Be Monitored?

You can monitor runtime errors (debug) and SQL trace information (trace); and you can collect timed statistics (timestats) data. The administrator configures the content and location of the log files using parameters in the error logging level%LACFGDIR%\dblog.cfg file. Each logging function can be configured separately.

Messages are writing to the following files, depending on the configuration specified in the dblog.cfg file:

%LALOGDIR%\DBLog.program.debug.xxx

%LALOGDIR%\DBLog.program.timestats.xxx

%LALOGDIR%\ladb.log

The %LALOGDIR% directory can be overwritten with an entry in the dblog.cfg file.

Log Level Values

A message is logged to the associated file when the severity of the message is less than or equal to the severity level specified for that logger. The severity ranges from FATAL (1, or the highest severity) to TIMESTATS (8, the lowest severity).

You can use a numeric or text value for the logging level. The log level values shown in the following table can be used with the DEBUGLEVEL and LADBLOGLEVEL parameters.


Level	#	Description
`NONE`	`0`	No logging will be done for the specified log (DEBUG, TRACE, or LADB).
`FATAL`	`1`	FATAL is the highest level of severity. When FATAL is specified, only messages with this level of severity are reported.
`ERROR`	`2`	error logging leve Error and fatal messages are written to the log file.
`WARNING`	`3`	Warning, error, and fatal messages are written to the specified log file.
`INFO` `ALL` `DEFAULT` `APICALL`	`4`	All informational messages will be written to the specified log file. Note: APICALL is a database-specific level value.
`SQL`	`5`	Note: SQL is a database-specific level value.
`TIMESTATS`	`8`	Note: TIMESTATS is a database-specific level value.

Logging Configuration Example

In this example, the following values are set in the %LACFGDIR%\dblog.cfg file:

DEBUG = TRUE
DEBUGLEVEL = WARNING
LADBLOGLEVEL=ERROR

When a message is produced with a severity of ERROR the message would be written to

ladb.log – the value of LADBLOGLEVEL in the dblog.cfg file is ERROR, and this equals the message's level (ERROR)
DBLog.program.debug.xxx – the value of DEBUGLEVEL in the dblog.cfg file is WARNING, which is greater than the message's level (ERROR)

When a message with severity of INFO is produced, it would be written to the trace log but not to ladb.log or the debug log.