Problematic processing might happen during REBIND processing
after upgrade of the DB2 server to the newer version. Reason for
the error is exceeded limit in the catalog tables for static
SQLs. Root cause of the problem is extended size of the static
SQL section after the upgrade to newer version (extended section
size does not fit in the catalog limit although fit correctly in
previous version before upgrade).
The problem manifests it self as SQL0101N error:
SQL0101N The statement was not processed because a limit such
as a
memory limit, an SQL limit, or a database limit was reached.
SQLSTATE=54001
Once you hit this issue, following errors are logged in the
db2diag.log:
2015-04-28-08.07.48.441000+120 E1156675F2515 LEVEL: Info
(Origin)
PID : 5432 TID : 9648 PROC :
db2syscs.exe
INSTANCE: DB2INST1 NODE : 000 DB :
SAMPLE
APPHDL : 0-673 APPID: ::0.5021.CEDD2F4E6CBB
AUTHID : U005005 HOSTNAME: HOST1
EDUID : 9648 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, SW- common services, sqlnn_cmpl, probe:650
MESSAGE : ZRC=0x801A006D=-2145779603=SQLZ_CA_BUILT
"SQLCA has already been built"
DATA #1 : String, 62 bytes
An unexpected error was detected during statement compilation.
DATA #2 : Boolean, 1 bytes
true
DATA #3 : Boolean, 1 bytes
false
DATA #4 : Boolean, 1 bytes
true
DATA #5 : Boolean, 1 bytes
false
DATA #6 : Hex integer, 4 bytes
0x00000000
DATA #7 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -101 sqlerrml: 33
sqlerrmc: Statement too long or too complex
sqlerrp : SQLNG0C3
sqlerrd : (1) 0x801A006D (2) 0x00000000 (3)
0x00000000
(4) 0x00000000 (5) 0xFFFFF276 (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:
DATA #8 : Hex integer, 4 bytes
0x00000040
DATA #9 : String with size, 1000 bytes
UPDATE COL1 ...
...
DATA #10: String, 118 bytes
Compiler error stack for rc = -2145779603"
sqlnn_cmpl[415]
sqlng_main[2990]
sqlng_main[2528]
sqlngSectLinearize[3466]
...
This APAR change is to process SQL statements hitting the limit
in the incremental bind fashion. |
