Learning more about troubleshooting tools
The following topics can help you to acquire the conceptual
information that you need to effectively troubleshoot problems with
the DB2 product:
Checking archive log files with the db2cklog tool
Checking your archive log files ensures that known good
log files are available in case a rollforward recovery becomes necessary
and that the recovery operation does not fail because of a problem
with a log file. The information in this topic tells you how to check
log files with the db2cklog tool, and what to do
if a log file does fail validation.
Overview of the db2dart tool
The db2dart command can be used to verify the
architectural correctness of databases and the objects within them. It can
also be used to display the contents of database control files in order to
extract data from tables that might otherwise be inaccessible.
Analyzing db2diag log files using db2diag tool
The primary log file intended for use by database and system
administrators is the administration notification log. The db2diag log
files are intended for use by IBM Software Support for troubleshooting purposes.
Mimicking databases using db2look
There are many times when it is advantageous to be able
to create a database that is similar in structure to another database.
For example, rather than testing out new applications or recovery
plans on a production system, it makes more sense to create a test
system that is similar in structure and data, and to then do the tests
against it instead.
Collecting environment information with the db2support command
When it comes to collecting information for a DB2 problem, the most important DB2 utility you need to run is db2support.
The db2support command automatically collects all DB2 and system diagnostic information
available. It also has an optional interactive "Question and Answer"
session, which poses questions about the circumstances of your problem.
Basic trace diagnostics
If you experience a recurring and reproducible problem
with DB2, tracing sometimes
allows you to capture additional information about it. Under normal
circumstances, you should only use a trace if asked to by IBM Software Support.
The process of taking a trace entails setting up the trace facility,
reproducing the error and collecting the data.
DB2 10.5 for Linux, UNIX, and Windows