Collecting diagnostic data

To diagnose Db2 problems you might need to collect symptom descriptions, traces, logs, and dump data sets.

Before you begin

Prior to a problem occurring, you can set up your z/OS® environment to collect diagnostic data. Collecting data before you open a support case with IBM® Support can help expedite the resolution of the problem.

About this task

The type of data that is needed to diagnose a problem depends on the problem that is being investigated. Sometimes you cannot solve a problem with only a description of its symptoms. In such cases, you need to collect diagnostic data. Collecting data starts with answering questions like these to narrow down the list of system components that are involved:
  • With which components are errors associated?
  • Do the symptoms match any known problems? If so, has a fix or workaround been published?
  • Can the problem be identified and resolved without a code fix?
  • Under what conditions does the problem occur?

When you are researching the cause of your problem, you need to describe your problem and collect diagnostic data.

Procedure

  1. Write a clear description of the problem and any steps that are required to re-create the problem.
  2. Identify and record all messages and codes that were issued as a result of the problem.
  3. Search the Db2 information for troubleshooting topics about your problem.
  4. Search to check whether a fix or solution already exists for your problem.
  5. Use the recommended procedures to diagnose the problem and to determine your next actions.

What to do next

If you cannot find documented procedures to solve your problem, you can contact IBM Support. You might be asked to collect logs, data sets, and dumps that can help determine the source of your problem. For certain problem symptoms, or for problems in a specific component, you might need to collect additional data. Follow the instructions to collect diagnostic data for problems of your type.