Caches stay in deleting state in Watson Query

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.

Run the following command to find the caching pod name:
```
oc get pods -n <namespace> | grep dv
```

Run the following command to restart the Watson Query caching pod.
```
oc delete <caching-pod-name>
```