DB2 FOR LUW / DB2FORLUW / A50 - DB2

APAR IC74008 may prevent certain statements from getting 
properly stored in the package cache. As a result, when a 
dynamic sql snapshot operation fetches such statements and tries 
to do code page conversion (because the application code page is 
different from database code page), it receives a truncation 
error because the last few characters at the end of such 
statements were invalid. This causes the snapshot invocation to 
exit with SQLO_DBCSTRUNC error (seen in db2diag.log). 
 
Example : 
- db2 get snapshot for dynamic sql on <dbname> 
- Quering SYSIBMADM.SNAPDYN_SQL : 
  db2 "SELECT  NUM_EXECUTIONS "NUM EXECS" ,TOTAL_EXEC_TIME "EXEC 
TIME" , TOTAL_USR_CPU_TIME "USER CPU TIME" ,TOTAL_SYS_CPU_TIME 
"SYS CPU TIME", round((total_usr_cpu_time + 
total_sys_cpu_time)/num_executions,3) "Cpu (s)/execution", 
cast(STMT_TEXT as varchar(5000)) "SQL_TEXT" FROM 
SYSIBMADM.SNAPDYN_SQL where total_usr_cpu_time > 2 and 
num_executions > 5 order by total_usr_cpu_time desc" 
 
On command line prompt you will see : 
SQL1224N  The database manager is not able to accept new 
requests, has terminated all requests in progress, or has 
terminated the specified request because of an error or a forced 
interrupt.  SQLSTATE=55032 
 
In db2diag.log you will see : 
 
2013-01-30-08.36.11.657111+480 I8342394A488       LEVEL: Severe 
PID     : 5505504              TID  : 96123       PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000 
APPHDL  : 0-63253              APPID: 
*LOCAL.db2inst1.130130003612 
AUTHID  : DB2INST1 
EDUID   : 96123                EDUNAME: db2agent (instance) 0 
FUNCTION: DB2 UDB, database monitor, sqlm_generic_convert, 
probe:60 
RETCODE : ZRC=0x870F00C0=-2029059904=SQLO_DBCSTRUNC 
          "last unconverted char is truncated"

APAR IC74008 may prevent certain statements from getting 
properly stored in the package cache. As a result, when a 
dynamic sql snapshot operation fetches such statements and tries 
to do code page conversion (because the application code page is 
different from database code page), it receives a truncation 
error because the last few characters at the end of such 
statements were invalid. This causes the snapshot invocation to 
exit with SQLO_DBCSTRUNC error (seen in db2diag.log). 
 
Example : 
- db2 get snapshot for dynamic sql on <dbname> 
- Quering SYSIBMADM.SNAPDYN_SQL : 
  db2 "SELECT  NUM_EXECUTIONS "NUM EXECS" ,TOTAL_EXEC_TIME "EXEC 
TIME" , TOTAL_USR_CPU_TIME "USER CPU TIME" ,TOTAL_SYS_CPU_TIME 
"SYS CPU TIME", round((total_usr_cpu_time + 
total_sys_cpu_time)/num_executions,3) "Cpu (s)/execution", 
cast(STMT_TEXT as varchar(5000)) "SQL_TEXT" FROM 
SYSIBMADM.SNAPDYN_SQL where total_usr_cpu_time > 2 and 
num_executions > 5 order by total_usr_cpu_time desc" 
 
On command line prompt you will see : 
SQL1224N  The database manager is not able to accept new 
requests, has terminated all requests in progress, or has 
terminated the specified request because of an error or a forced 
interrupt.  SQLSTATE=55032 
 
In db2diag.log you will see : 
 
2013-01-30-08.36.11.657111+480 I8342394A488       LEVEL: Severe 
PID     : 5505504              TID  : 96123       PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000 
APPHDL  : 0-63253              APPID: 
*LOCAL.db2inst1.130130003612 
AUTHID  : DB2INST1 
EDUID   : 96123                EDUNAME: db2agent (instance) 0 
FUNCTION: DB2 UDB, database monitor, sqlm_generic_convert, 
probe:60 
RETCODE : ZRC=0x870F00C0=-2029059904=SQLO_DBCSTRUNC 
          "last unconverted char is truncated"

NA

DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
 

First fixed in DB2 Version 10.5 Fix Pack 3

NA

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

26.09.2013
22.07.2014
22.07.2014