Caches stay in deleting state in Watson Query

Important: IBM Cloud Pak® for Data Version 4.6 will reach end of support (EOS) on 31 July, 2025. For more information, see the Discontinuance of service announcement for IBM Cloud Pak for Data Version 4.X.

Upgrade to IBM Software Hub Version 5.1 before IBM Cloud Pak for Data Version 4.6 reaches end of support. For more information, see Upgrading IBM Software Hub in the IBM Software Hub Version 5.1 documentation.

When an interrupt occurs during the deleting of caches, such as a Db2® restart, you might see that caches get stuck in a Deleting state in Watson Query. You cannot delete the cache even after the interrupt is resolved.

Symptoms

When you try to delete a cache, the state of the cache is marked as Deleting. If the cache pod loses its JDBC connection because of an interrupt such as a Db2 restart, the state of the cache remains as Deleting. When you try to delete the cache again, the cache remains in the Deleting state, and the delete request is ignored.

Resolving the problem

To solve this issue, restart the Watson Query caching pod.

Log in to the Watson Query head pod.
```
oc rsh c-db2u-dv-db2u-0 bash
```
Switch to the Watson Query database instance owner db2inst1.
```
su - db2inst1
```
Run the following command to restart the Watson Query caching pod.
```
oc delete <caching-pod-name>
```