DB2 - Problem description
Problem IT08264 | Status: Closed |
Possible exhaustion of connection handles due to cli handle leak in the DBMS_SQL and XCOMP modules can lead to -901 | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
When trying to run a package or drop a package, randomly Sql0901N error is seen as below: DROP PACKAGE package_name DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned: SQL0901N The SQL statement or command failed because of a database system error. (Reason "XCOMP1: SQLAllocHandle".) SQLSTATE=58004 Below messages can be seen in diag log: When customer is trying to run : DROP PACKAGE COMPAT.DBMS_LOG DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned: SQL0901N The SQL statement or command failed because of a database system error. (Reason "XCOMP1: SQLAllocHandle".) SQLSTATE=58004 There are getting below error in diaglog: 2015-04-03-02.56.21.143599-240 E127050E1523 LEVEL: Info (Origin) PID : 7073 TID : 139782466299648 PROC : db2sysc 0 INSTANCE: db2inst NODE : 000 DB : sample APPHDL : 0123 APPID: * local AUTHID : ABC HOSTNAME: hostname EDUID : 57926 EDUNAME: db2agent ( sample) 0 FUNCTION: DB2 UDB, SW- common services, sqlnn_cmpl, probe:650 MESSAGE : ZRC=0x8012006D=-2146303891=SQLR_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: -901 sqlerrml: 22 sqlerrmc: XCOMP1: SQLAllocHandle sqlerrp : SQL10054 sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000 (4) 0x00000000 (5) 0x000000AF (6) 0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: 58004 DATA #8 : Hex integer, 4 bytes 0x00000000 DATA #9 : String with size, 51 bytes begin ?:= set_client_identifier(?);END; DATA #10: String, 103 bytes Compiler error stack for rc = -2146303891: sqlnn_cmpl[300] sqlnp_main[110] sqlnp_handle_procedural[90] 2015-04-03-02.56.21.144606-240 I128574E1006 LEVEL: Error PID : 7073 TID : 139782466299648 PROC : db2sysc 0 INSTANCE: db2inst NODE : 000 DB : sample APPHDL : 0123 APPID: * local AUTHID : ABC HOSTNAME: hostname EDUID : 57926 EDUNAME: db2agent ( sample) 0 FUNCTION: DB2 UDB, access plan manager, sqlraProcessPrepAnonBlock, probe:310 MESSAGE : ZRC=0x8012006D=-2146303891=SQLR_CA_BUILT "SQLCA has already been built" DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 sqlerrml: 22 sqlerrmc: XCOMP1: SQLAllocHandle sqlerrp : SQL10054 sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000 (4) 0x00000000 (5) 0x000000AF (6) 0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: 58004 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 10.5 FP7 * **************************************************************** | |
Local Fix: | |
Recycle instance | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.04.2015 20.01.2016 20.01.2016 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.7 |