TMA-DB2-3.1.3
Set Diagnostic Logging to Capture Errors and Warnings (DIAGLEVEL)
MediumLevel 1Automateddb2
Description
The DIAGLEVEL parameter specifies the type of diagnostic errors that will be recorded in the db2diag.log file. It is recommended that the DIAGLEVEL parameter be set to at least 3. DIAGLEVEL must be 3 or higher. Run as the instance owner (or with sqllib/db2profile sourced) so the db2 CLP reads this instance's configuration.
How it is checked
Audit method: Shell command
shell
out=$(db2 get dbm cfg 2>/dev/null) || exit 1; printf '%s\n' "$out" | awk '{ if (match($0, /\([A-Z0-9_]+\) *=/)) { k = substr($0, RSTART + 1, RLENGTH); sub(/\).*/, "", k); v = $0; sub(/^[^=]*=/, "", v); gsub(/[ \t]/, "", v); c[k] = v } } END { if (c["DIAGLEVEL"] != "" && c["DIAGLEVEL"] + 0 >= 3) print "compliant"; else print "noncompliant: " c["DIAGLEVEL"] }'- Expected output
compliant
How it is fixed
Fix method: Guidance or infrastructure patch
1. Attach to the Db2 instance db2 => attach to <db2instance> 2. Run the following command: db2 => update database manager configuration using diaglevel 3
Properties
- Operating systems
- Any
- Tags
- db2databaselogging
- Reference
- CIS IBM Db2 12.1 Benchmark v1.0.0 - 3.1.3 Set Diagnostic Logging to Capture Errors and Warnings (DIAGLEVEL)
Check this host
Run this on a machine you are allowed to audit. The scan is read-only.
shell
tmaegis scan --target db2