DB2 - Problem description
Problem IT17828 | Status: Closed |
AUTOMATIC CLIENT REROUTE FAILS WITH SQL1776N WHEN HADR ENVIRONMENT CONFIGURED TO ACCEPT ONLY SSL CONNECTIONS | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
Configuration: DB2 V10.1 client connecting to AIX DB2 V10.5 fp7 servers. HADR Environment configured to only use SSL connections and not allow connections connecting with TCPIP only. Databases configured using: Primary Database Entry: Database alias = SAMPLE Database name = SAMPLE Local database directory = /home/db2inst1 Database release level = 10.00 Comment = Directory entry type = Indirect Catalog database partition number = 0 Alternate server hostname = ts-john.canlab.ibm.com Alternate server port number = 50003 DBM CFG info: DB2COMM=SSL SSL_SVCENAME=50003 SVCENAME= Standby Database entry: Database alias = SAMPLE Database name = SAMPLE Local database directory = /home/db2inst1 Database release level = 10.00 Comment = Directory entry type = Indirect Catalog database partition number = 0 Alternate server hostname = ts-johng.canlab.ibm.com Alternate server port number = 50003 DBM CFG info: DB2COMM=SSL SSL_SVCENAME=50003 SVCENAME= Client entry : Database entry: Database alias = SAMPLE Database name = SAMPLE Node name = DB2NODE1 Database release level = f.00 Comment = Directory entry type = Remote Authentication = SERVER Catalog database partition number = -1 Alternate server hostname = Alternate server port number = Node 1 entry: Node name = DB2NODE1 Comment = Directory entry type = LOCAL Protocol = TCPIP Hostname = ts-john.canlab.ibm.com Service name = 50003 Security type = SSL Remote instance name = System = Operating system type = None Connection to primary server works succeeds, but the ALTERNATE SERVER and PORT are not updated on the Client database catalog entry once the connection is made. After successfully running failover to switch Standby to become new Primary, Client connections fail with SQL1776N indicating it cannot connect to the standby server. If the SVCENAME is not set to a valid port or value in /etc/services file the Server List will not be sent to the client. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users using HADR with ACR Automatic Client Reroute with SSL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 LUW Version 11. * **************************************************************** | |
Local Fix: | |
If using DB2COMM=SSL make sure you set db2 update dbm cfg using SVCENAME= db2 update dbm cfg using SSL_SVCENAME= | |
Solution | |
Workaround | |
Configure SVCENAME in the DBM cfg db2 update dbm cfg using SVCENAME | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 07.11.2016 11.01.2017 11.01.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |