Troubleshooting a Q Replication pod not connecting to a database after backup and restore

Created by Liam Seston on Tue, 06/27/2023 - 20:21

Published URL:

https://www.ibm.com/support/pages/node/7007681

7007681

Troubleshooting

Problem

Some users with a Q Replication deployment might struggle to connect to a database after performing a backup and restore.

Symptom

The following output might be seen after trying to connect to a database:

[dsadm - Client CLI /]\> db2 connect to bludb user dsadm using $(cat /secrets/dsadmpwd/password)
SQL30081N  A communication error has been detected. Communication protocol
being used: "SSL".  Communication API being used: "SOCKETS".  Location where
the error was detected: "".  Communication function detecting the error:
"sqlccSSLSocketSetup".  Protocol specific error code(s): "414", "*", "*".
SQLSTATE=08001

Resolving The Problem

Complete a backup and restore procedure. For more information, see Backing up and restoring Db2.
After restoring, run the following script:
- bludr-change-ports.sh
Exchange SSL certificates for your deployment. For more information, see Performing a SSL certificate exchange for Db2 replication.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB76","label":"Data Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS5MAX","label":"IBM Cloud Pak for Data Db2"},"ARM Category":[{"code":"a8m3p000000UoTDAA0","label":"Recovery-\u003EBackup"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]