Fixes are available
APAR status
Closed as program error.
Error description
When issuing a runstats, reorg or some other DB2 utility such as a "get db cfg", from a remote DB2 client may fail with a -104 error. . The problem will happen if using a DB2 v9.5 or greater client, and connecting to a DB2 v9.1 server, and if the db2set registry variable DB2CONNECT_IN_APP_PROCESS=NO is set on the client. . For example, when issuing a runstats command, the following error may occur: . SQL2310N The utility could not generate statistics. Error "-104" was returned. . The DB2 v9.1 server will print the following error in the db2diag.log: . 2010-03-15-11.00.29.054870-240 I1627A1160 LEVEL: Warning PID : 1372320 TID : 1 PROC : db2agent (SAMPLE) INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-30 APPID: 9.26.50.81.55006.100315150025 AUTHID : TESTUID FUNCTION: DB2 UDB, trace services, sqlt_logerr_data, probe:0 MESSAGE : sqlerCallDL: prepare of uncat procedure failed! DATA #1 : Hexdump, 136 bytes 5351 4C43 4120 2020 0000 0088 FFFF FF98 SQLCA ........ 0023 4341 4C4C 2032 37FF 4245 4749 4E2D .#CALL 27.BEGIN- 4F46 2D53 5441 5445 4D45 4E54 FF3C 7661 OF-STATEMENT.<va 6C75 6573 3E20 2020 2020 2020 2020 2020 lues> 2020 2020 2020 2020 2020 2020 2020 2020 2020 2020 2020 2020 5351 4C4E 5030 3132 SQLNP012 801A 006D 0000 0000 0000 0000 0000 0000 ...m............ FFFF FD3F 0000 0000 2020 2020 2020 2020 ...?.... 2020 2020 2020 2020 . 2010-03-15-11.00.29.055469-240 I2788A423 LEVEL: Severe PID : 1372320 TID : 1 PROC : db2agent (SAMPLE) INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-30 APPID: 9.26.50.81.55006.100315150025 AUTHID : TESTUID FUNCTION: DB2 UDB, routine_infrastructure, sqlerCallDL, probe:190 RETCODE : ZRC=0x80310021=-2144272351=SQLNN_E_SYNTAX "Syntax error" . This APAR is a server-side problem that will fix this problem on the DB2 v9.1 server. This problem does not happen against DB2 v9.5 or v9.7 servers, or if the client is running DB2 v9.1
Local fix
Unset DB2CONNECT_IN_APP_PROCESS from the db2set registry on the client
Problem summary
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * When issuing a runstats, reorg or some other DB2 utility * * such as a "get db cfg", from a remote DB2 client may fail * * with a -104 error. * * * * The problem will happen if using a DB2 v9.5 or greater * * client, and connecting to a DB2 v9.1 server, and if the * * db2set registry variable DB2CONNECT_IN_APP_PROCESS=NO is set * * on the client. * * * * For example, when issuing a runstats command, the following * * error may occur: * * * * SQL2310N The utility could not generate statistics. Error * * "-104" was returned. * * * * The DB2 v9.1 server will print the following error in the * * db2diag.log: * * * * 2010-03-15-11.00.29.054870-240 I1627A1160 LEVEL: * * Warning * * PID : 1372320 TID : 1 PROC : * * db2agent (SAMPLE) * * INSTANCE: db2inst1 NODE : 000 DB : SAMPLE * * * * APPHDL : 0-30 APPID: * * 9.26.50.81.55006.100315150025 * * AUTHID : TESTUID * * FUNCTION: DB2 UDB, trace services, sqlt_logerr_data, probe:0 * * MESSAGE : sqlerCallDL: prepare of uncat procedure failed! * * DATA #1 : Hexdump, 136 bytes * * 5351 4C43 4120 2020 0000 0088 FFFF FF98 SQLCA ........ * * 0023 4341 4C4C 2032 37FF 4245 4749 4E2D .#CALL 27.BEGIN- * * 4F46 2D53 5441 5445 4D45 4E54 FF3C 7661 OF-STATEMENT.<va * * 6C75 6573 3E20 2020 2020 2020 2020 2020 lues> * * 2020 2020 2020 2020 2020 2020 2020 2020 * * 2020 2020 2020 2020 5351 4C4E 5030 3132 SQLNP012 * * 801A 006D 0000 0000 0000 0000 0000 0000 ...m............ * * FFFF FD3F 0000 0000 2020 2020 2020 2020 ...?.... * * 2020 2020 2020 2020 * * . * * * * 2010-03-15-11.00.29.055469-240 I2788A423 LEVEL: * * Severe * * PID : 1372320 TID : 1 PROC : * * db2agent (SAMPLE) * * INSTANCE: db2inst1 NODE : 000 DB : SAMPLE * * APPHDL : 0-30 APPID: * * 9.26.50.81.55006.100315150025 * * AUTHID : TESTUID * * FUNCTION: DB2 UDB, routine_infrastructure, sqlerCallDL, * * probe:190 * * RETCODE : ZRC=0x80310021=-2144272351=SQLNN_E_SYNTAX "Syntax * * error" * * * * This APAR is a server-side problem that will fix this * * problem on the DB2 v9.1 server. This problem does not * * happen against DB2 v9.5 or v9.7 servers, or if the client is * * running DB2 v9.1. * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 9.1 Fix Pack 10 * ****************************************************************
Problem conclusion
Problem was first fixed in Version 9.1 Fix Pack 10
Temporary fix
see Local Fix.
Comments
APAR Information
APAR number
IZ72921
Reported component name
DB2 CUE SOLARIS
Reported component ID
5724B6202
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-03-15
Closed date
2011-06-20
Last modified date
2011-06-20
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 CUE SOLARIS
Fixed component ID
5724B6202
Applicable component levels
R910 PSN
UP
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910"}]
Document Information
Modified date:
07 October 2021