Troubleshooting general issues in Data Virtualization

Resolve the general problems that you might encounter connecting to or accessing Data Virtualization.

Resolving metastore issues after a storage outage or the restarting of all pods
In Data Virtualization, the metastore is not functional after a storage outage, such as after an upgrade of an OpenShift® cluster and OCS storage or after a power outage at a data centre, or after all pods are restarted.
SQL6031N error in the db2nodes.cfg file in Data Virtualization
Data Virtualization requires the no_root_squash option to be set on all NFS-based storage. If this option is not set, provisioning of Data Virtualization fails and you see the following error message SQL6031N Error in the db2nodes.cfg file at line number "2". Reason code "14".
Validation hangs when you run a query after you scale worker pods in Data Virtualization
After you scale down Data Virtualization, a query might hang. In the c-db2u-dv-db2u-0 pod in the log file, you might see a message such as Error while waiting for connect() completion with node 2.
Worker pods cannot connect in Data Virtualization
When worker pods cannot connect, you must restart the head pod manually.

Parent topic: Troubleshooting the Data Virtualization service