DB2 - Problem description
Problem IC96306 | Status: Closed |
SQLNN_E_SYNTAX SYNTAX ERROR ON 'CALL 47' STORED PROCEDURE CALL SEEN IN DB2DIAG.LOG | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
Under rare conditions, stored procedure execution might fail and report an error into the db2diag.log in the form of: FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary logging function), probe:50 MESSAGE : sqlerCallDL: prepare of uncat procedure failed! DATA #1 : Hexdump, 136 bytes 0x0000000208197E08 : 5351 4C43 4120 2020 8800 0000 98FF FFFF SQLCA ........ 0x0000000208197E18 : 2300 4341 4C4C 2034 37FF 4245 4749 4E2D #.CALL 47.BEGIN- 0x0000000208197E28 : 4F46 2D53 5441 5445 4D45 4E54 FF3C 7661 OF-STATEMENT.<va 0x0000000208197E38 : 6C75 6573 3E20 2020 2020 2020 2020 2020 lues> 0x0000000208197E48 : 2020 2020 2020 2020 2020 2020 2020 2020 0x0000000208197E58 : 2020 2020 2020 2020 5351 4C4E 5030 3146 SQLNP01F 0x0000000208197E68 : 6D00 1A80 0000 0000 0000 0000 0000 0000 m............... 0x0000000208197E78 : 3FFD FFFF 0000 0000 2020 2020 2020 2020 ?....... 0x0000000208197E88 : 2020 2020 2020 2020 ... FUNCTION: DB2 UDB, routine_infrastructure, sqlerCallDL, probe:190 RETCODE : ZRC=0x80310021=-2144272351=SQLNN_E_SYNTAX "Syntax error" While this problem might be observed by any user application, customers who have reported this problem observed the problem during DB2 automatic statistics collection. In these situations, the statistics log will contain messages such as: FUNCTION: DB2 UDB, Automatic Table Maintenance, AtmTable::get_cols, probe:100 MESSAGE : ECF=0x90000002=-1879048190=ECF_FAILED Failed DATA #1 : signed integer, 8 bytes -104 DATA #2 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -104 sqlerrml: 35 sqlerrmc: CALL 47 BEGIN-OF-STATEMENT <values> sqlerrp : SQLNP01F sqlerrd : (1) 0x801A006D (2) 0x00000000 (3) 0x00000000 (4) 0x00000000 (5) 0xFFFFFD3F (6) 0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: 42601 When automatic statistics collection encounters this problem, automatic statistics collection might not occur for one or more tables when it should have occurred. However, in the next automatic statistics collection evaluation, unless the problem occurs again, and occurs at a time when automatic statistics collection wants to process the same tables, the tables should be successfully processed. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * stored procedure users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v10.5 FP3 or latest release. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 26.09.2013 06.08.2014 06.08.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.3 | |
10.5.0.3 |