Troubleshooting
Problem
Collecting data when a DB2 abend or DB2 crash has happened on an instance or database. Collecting this information before calling IBM support will help you understand the problem and save time analyzing the data.
Resolving The Problem
Learning more about DB2 LUW Abend (crash)
- 1. Learning more
- 2. Troubleshooting
- 3. Collecting data- selected tab,
- 4. Analyzing data
This section lists the required information DB2 Support would like to have gathered. Alternatively you may contact DB2 Technical support for further questions.
* At a minimum you should collect detailed system information using the -s option of db2support. For example:
db2support . -d <dbname> -s
* Provide the time when the DB2 Instance/Database crashed. You can identify the time of when the DB2 crash occurred on the server by checking the db2diag.log. As a reference you can search for a db2diag.log entry such as the following:
2007-04-02-10.57.19.404173+600 E10819A511 LEVEL: Severe
PID : 348186 TID : 1 PROC : db2sysc 0
INSTANCE: db2v8 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler, probe:10
MESSAGE : ADM0503C An unexpected internal processing error has occurred. ALL
DB2 PROCESSES ASSOCIATED WITH THIS INSTANCE HAVE BEEN SHUTDOWN.
Diagnostic information has been recorded. Contact IBM Support for
further assistance.
FOR AIX ONLY:
If the Operating system is AIX then we can also collect the following:
* Identify the directory where db2 diagnostic information will be collected. You can check the DIAGPATH database manager configuration parameter or by default it is: $HOME/sqllib/db2dump
* In that directory check for any directories starting with c.00x. Look for any directories that were created around the time when the instance/database crashed.
* In this directory there should be a file named core. Identify the program which created the core file. In this example it is the db2sysc program
/home/db2v8/sqllib/db2dump/c348186.000> file core
core: AIX core file fulldump 64-bit, db2sysc
* We need to identify where this program is located, so using the last example we issue:
’which db2sysc’
This yields:
/home/v82ee/sqllib/adm/db2sysc
* Now we want to collect information about the core file. We can use the snapcore utility in AIX to collect this information. So for our example above we would issue:
snapcore -d<dir name> <core file name> <program name>
Example:
snapcore -d/home/db2v8/sqllib/db2dump/c348186.000 core /home/db2v8/sqllib/adm/db2sysc
Ensure that there is adequate space in the directory specified above.
* This will create a pax archive of all the relevant files necessary to elicit information from the core. In our example the file created is: snapcore_.pax.Z
* You can upload this file along with the db2support output above to the ftp server
Submitting information to IBM Support
Once you have collected your information, you can begin Problem Determination through the product Support web page, or simply submit the diagnostic information to IBM support. Use the document below for submitting information to IBM Support.
Submitting diagnostic information to IBM Technical Support for problem determination
Related Information
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21326400