This parameter specifies the type of diagnostic errors
that will be recorded in the db2diag log file.
- Configuration type
- Database manager
- Applies to
-
- Database server with local and remote clients
- Client
- Database server with local clients
- Partitioned database server with local and remote clients
- Parameter type
- Configurable Online
- Propagation class
- Immediate
- Default [range]
- 3 [ 0 — 4 ]
Valid values for this parameter are:
- 0 – Starting in Fix Pack 1, only administration notification
messages are captured on the client side. Critical errors, event messages,
and administration notification messages are still captured on the
server side.
- 1 – Only severe errors, critical errors, event messages,
and administration notification messages are captured.
- 2 – All errors, event messages, and administration notification
messages are captured.
- 3
- All errors, warnings, event messages, and administration notification messages are captured. Some
key informational messages might be captured at this level as well.
- 4 – All errors, warnings, informational messages, event
messages, and administration notification messages are captured.
The diagpath configuration parameter
is used to specify the directory that will contain the error file,
alert log file, and any dump files that might be generated, based
on the value of the diaglevel parameter.
Usage
notes- The dynamic behaviour for diaglevel does
not extend to all processes.
- The db2sysc DB2® server
process can detect dynamic changes, for example, when you issue the UPDATE
DATABASE MANAGER CONFIGURATION command over an instance
attachment.
- When DB2 client and application
processes start, they use the diaglevel configuration
parameter setting and do not detect any dynamic changes.
- To help resolve a problem, you can increase the value of this
parameter to gather additional problem determination data.
DB2 10.5 for Linux, UNIX, and Windows