DB2 - Problem description
Problem IT17665 | Status: Closed |
IN PURESCALE WHEN AN APP RECEIVES SQL0997W MESSAGES ARE LOGGED WITH LEVEL SEVERE/ERROR THAT SHOULD BE INFORMATIONAL | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
In a pureScale environment when an XA Read only transaction completes and the app receives SQL0997W, probes will appear in the db2diag.log that have a Severe or Error level but should really be Informational. No action is required by the customer in this case and there is no problem with any DB2 functionality. Here are example probes: ----- 2016-10-13-05.30.02.035269+540 I94484A992 LEVEL: Severe PID : 31260800 TID : 159347 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : XXXXXX APPHDL : 0-32951 APPID: XXX.XXX.161013010910 AUTHID : db2inst1 HOSTNAME: XXXXXXXX EDUID : 159347 EDUNAME: db2agent (TESTDB) 0 FUNCTION: DB2 UDB, base sys utilities, sqeIcoordCB::PostCompletion, probe:734 RETCODE : ZRC=0x8005006D=-2147155859=SQLE_CA_BUILT "SQLCA has been built and saved in component specific control block." DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: 997 sqlerrml: 2 sqlerrmc: 35 sqlerrp : SQLRR0AC sqlerrd : (1) 0x80100023 (2) 0x00000023 (3) 0x00000000 (4) 0x00000000 (5) 0x00000000 (6) 0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: 2016-10-13-05.30.02.035665+540 I95477A1052 LEVEL: Severe PID : 31260800 TID : 210901 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : XXXXXX APPHDL : 1-13585 APPID: XX.X.XX.XXX.53904.161012202801 AUTHID : db2inst1 HOSTNAME: XXXXXXXX EDUID : 210901 EDUNAME: db2agntp (TESTDB) 0 FUNCTION: DB2 UDB, base sys utilities, sqeIcoordCB::WaitForCompletion, probe:674 RETCODE : ZRC=0x8005006D=-2147155859=SQLE_CA_BUILT "SQLCA has been built and saved in component specific control block." DATA #1 : ZRC, PD_TYPE_ZRC, 4 bytes 0x8005006D DATA #2 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: 997 sqlerrml: 2 sqlerrmc: 35 sqlerrp : SQLRR0AC sqlerrd : (1) 0x80100023 (2) 0x00000023 (3) 0x00000000 (4) 0x00000000 (5) 0x00000000 (6) 0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: 2016-10-13-05.30.02.036135+540 I96530A1014 LEVEL: Severe PID : 31260800 TID : 210901 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : XXXXXX APPHDL : 1-13585 APPID: XX.X.XX.XXX.53904.161012202801 AUTHID : db2inst1 HOSTNAME: XXXXXXXX EDUID : 210901 EDUNAME: db2agntp (TESTDB) 0 FUNCTION: DB2 UDB, base sys utilities, sqeIcoordCB::DispatchIndependentDBAgent, probe:125 RETCODE : ZRC=0x8005006D=-2147155859=SQLE_CA_BUILT "SQLCA has been built and saved in component specific control block." DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: 997 sqlerrml: 2 sqlerrmc: 35 sqlerrp : SQLRR0AC sqlerrd : (1) 0x80100023 (2) 0x00000023 (3) 0x00000000 (4) 0x00000000 (5) 0x00000000 (6) 0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: 2016-10-13-05.30.02.036535+540 I97545A573 LEVEL: Error PID : 31260800 TID : 210901 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : XXXXXX APPHDL : 1-13585 APPID: XX.X.XX.XXX.53904.161012202801 AUTHID : db2inst1 HOSTNAME: XXXXXXXX EDUID : 210901 EDUNAME: db2agntp (TESTDB) 0 FUNCTION: DB2 UDB, base sys utilities, sqleInvokeXaIcoord, probe:109 MESSAGE : ZRC=0x8005006D=-2147155859=SQLE_CA_BUILT "SQLCA has been built and saved in component specific control block." ----- | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DB2 UDB Version 11.1 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 11.1 FixPack 1. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in DB2 UDB Version 11.1 FixPack 1. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 26.10.2016 23.06.2017 23.06.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |