IT22632: SCRIPTS FAILS WITH SQLSTATE 42702 / SQLCODE: -204

Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod4 Fix Pack4 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 4 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 6 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 5 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 7 for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error description

• It is possible for multiple 'db2' frontends issued from
  different shell sessions or scripts to
  end up using the same 'db2bp' agent and causing unexpected
  results / errors. For example:
  
    Window 1
  Window 2
  
    tst1.sh (pid N)
  tst2.sh (pid M)
      db2 -tvf script1
        connect to db
                                   db2bp created
        set schema WHATEVER1
        insert into tab1
                                   db2bp performs insert
  
  db2 -tvf script2
  
  connect to tst
        insert into tab1
                                   db2bp already connected
                                   but with this problem we
                                   use same db2bp for both
                                   frontend
  
  set schema WHATEVER2
        insert into tab1
                                   db2bp now inserts into
                                   WHATEVER2.tab1 !!!!
  

Local fix

• na
  

Problem summary

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

Problem conclusion

• First fixed in Db2 11.1 Mod 2 Fix Pack 2 iFix002
  

Temporary fix

Comments

APAR Information

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

  IT21485

• 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