Fixes are available
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 number
IT22632
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-10-02
Closed date
2017-12-22
Last modified date
2017-12-22
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":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
22 December 2017