Gathering information for Db2 support

You can gather information about your Db2 environment to be used by IBM Support, including running a support tool and viewing diagnostic logs.

Using the db2support tool in Db2
You can run a command to gather information about your Db2 environment to be used by IBM Support for Db2.
Viewing Db2 log files
In general, there are two categories of Db2 log files, container logs and Db2 diagnostic logs.
Using the OpenShift must-gather utility for Db2
You can gather data about the Red Hat® OpenShift® cluster where your Db2 service runs, and database-specific information, by using the OpenShift must-gather utility.
Db2 node failure behavior and expectations
When stateful applications such as Db2 are deployed on Kubernetes or OpenShift, managing the application lifecycle during cluster-wide events such as worker node failures is the responsibility of cluster administrators and not the application itself. In most cases, Kubernetes cannot automatically mitigate such events, and hence applications running on Kubernetes cannot automatically manage these events either.
Managing Db2 transaction logs
Transaction logs are stored for your Db2 database. You can use the prune history command to remove certain log files and create more storage space.
Managing diagnostic directories for Db2
As a database administrator, you can clean up diagnostic files that are created by Db2.
Automating tasks with the Administrative Task Scheduler (ATS) for the Db2 service
You can use the Db2 Administrative Task Scheduler (ATS) command-line interface to manage diagnostic log files.
Monitoring the Db2 service
You can monitor the data from your Db2 databases by first enabling monitoring. Monitor the startup progress of a Db2 database after you restart a node to make sure that it starts up successfully. Determine a Db2U instance status by monitoring the custom resource.