The following tools are available to help collect, format or analyze diagnostic data.
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.
The db2diag tool serves to filter and format the volume of information available in the db2diag log files. Filtering records in db2diag log files can reduce the time required to locate the records needed when troubleshooting problems.
You can view and edit the Global Registry with the db2greg tool.
The db2level command will help you determine the version and service level (build level and fix pack number) of your DB2 instance.
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 the test system without adversely affecting the production system. You can use the db2look tool to extract the required DDL statements needed to reproduce the database objects of one database in another database. The tool can also generate the required SQL statements needed to replicate the statistics from the one database to the other, and the statements needed to replicate the database configuration, database manager configuration, and registry variables.
With the ability to install multiple copies of DB2 products on your system and the flexibility to install DB2 products and features in the path of your choice, you need a tool to help you keep track of what is installed and where it is installed. On supported Linux and UNIX operating systems, the db2ls command lists the DB2 products and features installed on your system, including the DB2 Version 9 HTML documentation.
The db2pd tool is used for troubleshooting because it can return quick and immediate information from the DB2 memory sets.
When it comes to collecting information for a DB2 problem, the most important DB2 utility you must run is db2support. The db2support utility 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.
The db2val tool verifies the core function of a DB2 copy by validating installation files, instances, database creation, connections to that database, and the state of partitioned database environments.
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.
Useful diagnostic tools provided with the Windows, Linux, and UNIX operating systems can be used to gather and process data that can help identify the cause of a problem you are having with your system.