Troubleshooting Db2 and Db2 Warehouse

Use these solutions to resolve problems that you might encounter with the Db2 and Db2 Warehouse database services.

Updating the service instance configmap post upgrade
After upgrading, when you back up and restore a service instance, it will end up in an UNKNOWN state.
Troubleshooting the Db2 or Db2 Warehouse service instance failures
When upgrading Db2 or Db2 Warehouse service instances, you might encounter a failure scenario where service instance state returns UNKNOWN or provision status returns FAILED.
Updating the Db2 SSL certificate after the IBM Software Hub self-signed certificate is updated
When the IBM® Software Hub self-signed certificate is updated, the Db2 SSL certificate must also be updated.
Db2 licensing issues
When deploying Db2®, if you see a message about a valid product license not being found in the log you might need to remove the deployment, run a command, and redeploy.
Issues with NFS Version 4
When you use NFS v4, NFS might mount storage incorrectly and show all files with ownership as nobody:nobody. This issue would cause your Db2 deployment on IBM Software Hub to fail.
Enabling PureData System for Operational Analytics workloads
When deploying Db2 Warehouse, you can specify to use IBM PureData® System for Operational Analytics (PDOA), but the capability is not automatically enabled and you must take manual steps to use it.
Reinitializing an HADR configuration to resolve errors
You can reinitialize a Db2 or Db2 Warehouse High Availability Disaster Recovery (HADR) configuration to resolve an error condition that prevents the primary and standby databases from connecting and achieving a peer state.
Db2 pod restarts repeatedly
Your Db2 engine pod might restart repeatedly due to an issue with the liveness probe.
SQL30081N RC 115,*,* error for selectForReceiveTimeout function after instance restore
Your database instance fails after restoring and you see the error SQL30081N RC 115,*,*.

Parent topic: Troubleshooting database services