DB2 - Problem description
Problem IT29181 | Status: Closed |
DPF PHYSICAL PARTITIONED CONFIGURED ENABLED FOR ONLY SSL DB2COMM, CONNECT TO REMOTE NODE FAILS WITH SQL1468N | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
Physical Partitioned DPF. Instance is fully configured to accept ONLY encrypted SSL connections. Registry variable : DB2COMM=SSL and DBM cfg parameters: SVCENAME= NULL (SSL_SVCENAME) = SSL Configuration: (SSL_SVR_KEYDB) = /SSL.kdb (SSL_SVR_STASH) = /SSL.sth (SSL_SVR_LABEL) = (SSL_SVCENAME) = (SSL_CIPHERSPECS) = TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_S HA384 (SSL_VERSIONS) = TLSV12 Logged to a local instance NODE, in the attempt to connect to a remote member by $ db2 -v "SET CLIENT CONNECT_MEMBER 5" Or export DB2NODE=5 The next CONNECT TO command : $ db2 -v "connect to user using " fails with : SQL1468N The database manager TCP/IP listener must be configured and running on the server instance "" (database partition number "5") before attempting to CONNECT or ATTACH to node "5". SQLSTATE=08004 The CONNECT works succesfully only with LOCAL nodes (node in the same server) or if the DB2 instance has TCPIP communication protocol enabled: DB2COMM=SSL,TCPIP an SVCENAME configured. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 17.05.2019 20.01.2020 20.01.2020 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |