Data Virtualization online restore post hooks time out

When you do an online restore, Data Virtualization worker pods might bypass waiting for the check that is used for an online restore. This issue leads the worker pods to fail and be removed before the online restore post hooks run.

Symptoms

The online post-restore step times out.

Diagnosing the problem

Complete these steps on worker pod 1 to check whether the database is still in the write suspend mode.

Run the following bash command:
```
oc rsh c-db2u-dv-db2u-1 bash
```
Run the following command to switch to the db2inst1 user:
```
su - db2inst1
```
Run the following command to check whether the write suspend mode is enabled for Big SQL:
```
db2pd -db bigsql -dbcfg | grep -i 'write suspend' | grep -i yes
```
If your results show Database is in write suspend state YES YES, then complete the following resolution steps.

Resolving the problem

Run the following command to restart the Data Virtualization worker pods:

oc delete pod $(oc get pods | grep -i c-db2u-dv-db2u | grep -v "db2u-0" | cut -d' ' -f 1)

Run the following command to re-run the online BAR post-restore hook script from the Data Virtualization head pod:

oc rsh c-db2u-dv-db2u-0 bash
su - db2inst1
/db2u/scripts/bigsql-exec.sh /usr/ibmpacks/current/bigsql/bigsql/bigsql-cli/BIGSQL/package/scripts/bigsql-db2ubar-hook.sh -H POST -M RESTORE -L