IBM Support

IT29181: DPF PHYSICAL PARTITIONED CONFIGURED ENABLED FOR ONLY SSL DB2COMM, CONNECT TO REMOTE NODE FAILS WITH SQL1468N

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error 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 service name>
    
    SSL Configuration:
    (SSL_SVR_KEYDB) = <path>/SSL.kdb
    (SSL_SVR_STASH) = <path>/SSL.sth
    (SSL_SVR_LABEL) = <SSL label>
    (SSL_SVCENAME) = <SSL service name>
    (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 <DATABASE > command :
    $ db2 -v "connect to <db name> user <user> using <password>"
    
    fails with :
    SQL1468N The database manager TCP/IP listener must be configured
    and running
    on the server instance "<instance name>" (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.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher                *
    ****************************************************************
    

Problem conclusion

  • First fixed in Db2 11.1 Mod 4 Fixpack 5
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT29181

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-05-17

  • Closed date

    2020-01-20

  • Last modified date

    2020-01-20

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RB10 PSN

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
04 May 2022