SQL30081N RC 115,*,* error for selectForReceiveTimeout function after instance restore

Your database instance fails after restoring and you see the error SQL30081N RC 115,*,*.

Symptoms

The IBM® Software Hub web client returns an Unknown or Error status from the instance after restoring.
You can run the following command to check your instance logs: 
oc logs zen-database-core-<instance_id> | grep "level-error"
  • Replace <instance_id> with the name of your database instance.
Run the following command to check if the pod was restored correctly.
oc exec -it c-db2oltp-<instance_id>-db2u-0 bash

db2set -all | grep DB2COMM=
  • Replace <instance_id> with the name of your database instance.

If there is no output, or the communication COMM port is missing, then the pod was not restored correctly.

Refer to the following output for an example of the error: 

error="SQLDriverConnect: {08001} [IBM][CLI Driver] SQL30081N A communication error has been detected. Communication protocol being used: \"TCP/IP\". Communication API being used: \"SOCKETS\". Location where the error was detected: \"155.55.555.555\". Communication function detecting the error: \"selectForConnectTimeout\". Protocol specific error code(s): \"115\", \"*\", \"*\". SQLSTATE=08001\n"

Resolving the problem

To resolve the problem:
  1. Log in to your db2oltp pod.
  2. Run the following command to restore the Db2 registry to its original state and restart Db2:
    oc exec -it c-db2oltp-<instance_id>-db2u-0 bash 
db2set DB2COMM= TCPIP,SSL 
db2stop 
db2start
    • Replace <instance_id> with the name of your database instance.