Worker pods cannot connect in Data Virtualization

When worker pods cannot connect, you must restart the head pod manually.

Symptoms

If the Data Virtualization head pod c-db2u-dv-db2u-0 is deleted manually by using the oc delete pod c-db2u-dv-db2u-0 command, Data Virtualization worker pods cannot connect to the Data Virtualization head pod.

To see whether you are experiencing this issue, run the following steps.

Change to the project where Data Virtualization pods are installed.
```
oc project ${PROJECT_CPD_INST_OPERANDS}
```
Log in to the Data Virtualization head pod.
```
oc rsh c-db2u-dv-db2u-0 bash
```
Switch to the Data Virtualization database instance owner db2inst1.
```
su - db2inst1
```
Run the following command to test the connection to the Big SQL database.
```
db2 connect to bigsql
```

Check whether you see the following error message.

SQL30082N  Security processing failed with reason "37" ("INVALID SERVER PRINCIPAL NAME").  SQLSTATE=08001

Resolving the problem

You can resolve this problem by choosing one of the following options.

Option 1

Log in to the Data Virtualization head pod.
```
oc rsh c-db2u-dv-db2u-0 bash
```
Restart the Data Virtualization head component with the following commands:
```
bigsql stop -n 0
```
```
bigsql start -n 0
```

Option 2

Wait for Data Virtualization liveness probe on the Data Virtualization head pod to restart the pod automatically.

You do not have to run any manual steps if you choose this option. However, you must wait for 90 minutes for the liveness probe to finish all the retries before it restarts the Data Virtualization head pod.