BIGSQL database remains in a "backup pending" state after you upgrade Data Virtualization

After you upgrade a Data Virtualization instance, the database remains in a "backup pending" state.

Symptoms

After the service instance upgrade completes, the database is in backup pending state. The c-db2u-dv-db2u-0 pod restarts due to the liveness probe failing.

Diagnosing the problem

To check if the database is in the backup pending state, look for the following message in the /mnt/PV/versioned/logs/liveness.err or /mnt/PV/versioned/logs/liveness.log file in the c-db2u-dv-db2u-0 pod:
SQL1116N A connection to or activation of database "BIGSQL" failed because the database is in BACKUP PENDING state. SQLSTATE=57019

Resolving the problem

  1. Run the following command:

    oc rsh c-db2u-dv-db2u-0 bash
/db2u/db2u_engn_update_or_upgrade_job.sh
  2. Verify that the liveness probe is now passing as expected:
    su - db2inst1
/opt/dv/current/run_time/liveness.sh
echo $?

    The output shows a value of "0".