|
Problem IT22632
|
Status: Closed |
SCRIPTS FAILS WITH SQLSTATE 42702 / SQLCODE: -204 |
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem 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 !!!! |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.1 Mod 2 Fix Pack 2 iFix002 or higher *
**************************************************************** |
| Local Fix: |
na |
| available fix packs: |
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
|
| Solution |
First fixed in Db2 11.1 Mod 2 Fix Pack 2 iFix002 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 02.10.2017
22.12.2017
22.12.2017 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
