(Ep. 11) - Exploring the Db2 Error Log

The error log can be intimidating. Sometimes the error log seems to have too much information to parse, sometimes it doesn't seem to have enough. This episode will cover how to find the error log, how to effectively mine information found inside, and some oddball tips to help you along.
Timestamps:
00:44 - Where is it the error log?
02:16 - What is in the error log?
03:43 - Cool ways to look up error codes
06:35 - Command line walkthrough
09:59 - How to use PD_GET_DIAG_HIST
GitHub Repository:
github.com/MKrafick/DiscoverDB2
PARSE_DIAG.ksh
A quick script that takes a database name and pulls 24 hours of
DB2DIAG.log details via PD_GET_DIAG_HIST.
Useful Links:
(Blog) DB2 Error Logging - tinyurl.com/ybxgzzs8
(Blog) db2diag tool for Parsing the Diagnostic Log - tinyurl.com/7q3pnqu

[@donbryan5551]

I did not know about the PD_GET_DIAG_HIST, Thanks

[@technicalknowledge9828]

Could you please me the query which you are using

[@donbryan5551]

Can you talk about managing the db2diag log file size (DIAGSIZE) in a future. I have seen diag files get to several GB and they are difficult to open in an editor.

[@DISCOVERDB2]

Don Bryan in hindsight, most old school DBA’s wouldn’t even think of this. Someone established like me would have a script that runs nightly to rename the db2diag.log to db2diag.date.log and holds 30 days worth of logs before pruning. So your log is never more than 24 hours. I know there are DB CFG parameters for this now as well but I like the format I have and the auto-pruning. This script should be accessible in my GitHub account if you need something similar. (GitHub: mkrafick). But yeah, I have seen the multi-gig log as well. All you need is one crazy dump and your file system is hosed.