Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC63891 Status: Closed

A GLOBAL SNAPSHOT FOR LOCKS IN A DPF ENVIRONMENT CAN FAIL WITH SQL0804,
REASONCODE 103

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
A "db2 get snapshot for locks on db global" can fail with: 
 
SQL0804N  The application program parameters for the current 
request are not valid.  Reason code "103".  If a host variable 
or SQLVAR in the SQLDA is invalid then:  host variable/SQLVAR 
number = "10", SQLTYPE = "405", SQLLEN = "-1407283840", host 
variable/SQLVAR type = "INPUT". 
SQLSTATE=07002 
 
In addition, the following entries can be found in db2diag.log 
file: 
 
2007-11-06-11.31.04.924830 060 I1853374062A1106   LEVEL: Error 
PID     : 13357176             TID  : 1           PROC : 
db2agent (instance) 0 
INSTANCE: db2instc             NODE : 000 
APPHDL  : 0-334                APPID: *xxxxxxxx 
FUNCTION: DB2 UDB, base sys utilities, sqlesrsp, probe:116 
MESSAGE : Stopping subagents failed with SQLCA: 
DATA #1 : Hexdump, 136 bytes 
0x000000011148B288 : 5351 4C43 4120 2020 0000 0088 0000 0646 
0x000000011148B298 : 0000 2020 2020 2020 2020 2020 2020 2020 
0x000000011148B2A8 : 2020 2020 2020 2020 2020 2020 2020 2020 
0x000000011148B2B8 : 2020 2020 2020 2020 2020 2020 2020 2020 
0x000000011148B2C8 : 2020 2020 2020 2020 2020 2020 2020 2020 
0x000000011148B2D8 : 2020 2020 2020 2020 5351 4C4D 5052 524F 
0x000000011148B2E8 : 0000 0000 0000 0000 0000 0000 0000 0000 
0x000000011148B2F8 : 0000 0000 0000 0000 2020 2020 2020 2020 
0x000000011148B308 : 2020 2020 2020 2020 
 
SQL0804 is triggered because the snapshot is requested with a 
size larger 2GB.
Problem Summary:
USERS AFFECTED: 
All 
 
PROBLEM DESCRIPTION: 
See ERROR DESCRIPTION 
 
PROBLEM SUMMARY: 
See ERROR DESCRIPTION
Local Fix:
Run local snapshots per node.
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 UDB Version 9.7, FixPak 1
Workaround
See LOCAL FIX.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.10.2009
15.12.2009
15.12.2009
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList