IBM Support

IT20198: THE IMPLICIT CONNECT RESET WHEN IN A DB2DBDFT ENVIRONMENT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In a DB2DBDFT environment implicit  CONNECT RESET unsets session
    variables. See the following example:
    
        db2set DB2DBDFT=repro
        db2 create db repro
        db2 connect to db repro
        db2 "create procedure test.proc(OUT a CHAR(32)) begin set a
    = application_id(); end"
        db2 terminate
        # repeat the following steps
        db2 "values(substr(application_id(),1,32))"
        db2 "call test.proc(?)"
        db2 "values(substr(application_id(),1,32))"
        db2 terminate
    
    While using here the CALL statement there is a a new connection
    and reset made to an already existing connection.What happens is
    the implicit CONNECT RESET when in a DB2DBDFT environment. In
    this demonstration the application ID changes as evidence of the
    CONNECT RESET.
    
    This reset has ramifications for SESSION variables - they change
    because the session has changed.
    

Local fix

  • There are a few ways to work this around.  There can be issued
    some other statement that'll require the implicit connection
    prior to first access of the global variable, they'll avoid the
    issue. (e.g. create a dummy procedure that does nothing and call
    it first.)
    
    Other more typical solutions are:
    - Avoid using DB2DFTDB. Be explicit about the database you're
    using.
    - Use USER not CURRENT USER in the variable definition.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 11.1 Mod 2 Fix Pack 2 or higher               *
    ****************************************************************
    

Problem conclusion

  • First fixed in DB2 11.1 Mod 2 Fix Pack 2
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT20198

  • 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

    2017-04-13

  • Closed date

    2017-06-27

  • Last modified date

    2017-06-27

  • 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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"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:
29 June 2020