Service instance fails to start

Provisioning a Data Virtualization service instance can take a few minutes, depending on your environment. If the service instance status does not change to Running, the provisioning process might have failed or timed out.

For more information about possible statuses, see Service statuses.

Symptoms

The Data Virtualization service instance does not have a Running status. To view the status, navigate to Services > Instances. Click the data-virtualization service instance.

Causes

The root cause might be several possibilities. The following sections describe some of the issues and how to resolve them. For example, on a cluster with performance problems, you might get an error if the service provisioning process takes longer than 30 minutes.

Note: The sample commands assume that you provision a Data Virtualization service instance called dv in the dv project or namespace.

Resolving the problem

Before you begin, determine whether the pods are running and what their status is.

Use the following command to see the status of the Data Virtualization instance pods.

oc get pods -n ${PROJECT_CPD_INST_OPERANDS} | grep dv

For example, run the following command.

oc get pods -n dv | grep dv

You might see something similar to the following pods.


c-db2u-dv-db2u-0                         1/1   Running 0 152m
c-db2u-dv-db2u-1                         1/1   Running 0 152m
c-db2u-dv-dvapi-7664954698-7nsst         1/1   Running 0 135m
c-db2u-dv-dvcaching-854db58866-2zdq4     1/1   Running 0 135m
c-db2u-dv-dvutils-0                      1/1   Running 0 136m
c-db2u-dv-hurricane-dv-69bd69fb4f-wf86h  2/2   Running 0 147m
c-db2u-dv-restore-morph-mk4f5            0/1   Completed 0 145m
dv-addon-858ff597cf-kpbq6                1/1   Running 0 162m
dv-extension-translations-job-qbxc4      0/1   Completed 0 162m
dv-service-provider-59997b484b-9m5jn     1/1   Running 0 162m

The provisioning process can take several minutes until all the pods start and are ready. If the Data Virtualization service instance is successfully provisioned, the following service pods show a status of Ready.

c-db2u-dv-db2u-0
c-db2u-dv-db2u-x
c-db2u-dv-dvapi
c-db2u-dv-dvcaching
c-db2u-dv-dvutils-0
c-db2u-dv-hurricane-dv
dv-addon
dv-service-provider

If the service provisioning process takes longer than 30 minutes, you get an error message that indicates that the service instance failed to start. Additionally, when you run the oc get pods command, values in the AGE column are higher than 30 minutes.

Use the following command to see the status of the Data Virtualization instance pods.

oc get pods -n ${PROJECT_CPD_INST_OPERANDS} | grep dv

See the following example.

c-db2u-dv-db2u-0                           1/1 Running 0 152m
c-db2u-dv-db2u-1                           1/1 Running 0 152m
c-db2u-dv-dvapi-7664954698-7nsst           1/1 Running 0 135m
c-db2u-dv-dvcaching-854db58866-2zdq4       1/1 Running 0 135m
c-db2u-dv-dvutils-0                        1/1 Running 0 136m
c-db2u-dv-hurricane-dv-69bd69fb4f-wf86h    2/2 Running 0 147m
c-db2u-dv-restore-morph-mk4f5              0/1 Completed 0 145m
dv-addon-858ff597cf-kpbq6                  1/1 Running 0 162m
dv-extension-translations-job-qbxc4        0/1 Completed 0 162m
dv-service-provider-59997b484b-9m5jn       1/1 Running 0 162m

Ensure that the following service pods are in Ready status:
- c-db2u-dv-db2u-0
- c-db2u-dv-db2u-x
- c-db2u-dv-dvapi
- c-db2u-dv-dvcaching
- c-db2u-dv-dvutils-0
- c-db2u-dv-hurricane-dv
- dv-addon
- dv-service-provider
If service pods listed in step 2 are in Ready status, check whether you can access the Data Virtualization service in the Cloud Pak for Data user interface. If you cannot access the service, follow these steps:
1. Refresh your browser.
2. On the navigation menu, click Services > Instances.
3. Find data-virtualization, and click Open in the instance options menu.