DB2 - Problem description
Problem IT24963 | Status: Closed |
CHANGE PROBE WARNING IN DB2DIAG.LOG MESSAGE FROM "ERROR" TO "WARNING" FOR RETCODE : ZRC=0X801A006D=-2145779603=SQLZ_CA_BUILT (WL | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
You can observe a lot of entries like the one below in the db2diag.log of their different db2 instances (see full db2diag.log entry further down): 2017-07-12-09.13.21.967068+120 I7780153A926 LEVEL: Error ... FUNCTION: DB2 UDB, database application extension for utilities, wlmCaptureActivityInProgress, probe:40 RETCODE : ZRC=0x801A006D=-2145779603=SQLZ_CA_BUILT "SQLCA has already been built" ... ### db2diag.log 2017-07-12-09.13.21.967068+120 I7780153A926 LEVEL: Error PID : 32506286 TID : 69654 PROC : db2sysc INSTANCE: db2inst1 NODE : 000 DB : SAMPLE HOSTNAME: db2host EDUID : 69654 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, database application extension for utilities, wlmCaptureActivityInProgress, probe:40 RETCODE : ZRC=0x801A006D=-2145779603=SQLZ_CA_BUILT "SQLCA has already been built" DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -4702 sqlerrml: 20 sqlerrmc: 15256 [0-15256] 47 1 sqlerrp : SQLRW119 sqlerrd : (1) 0x801A006D (2) 0x00000000 (3) 0x00000000 (4) 0x00000000 (5) 0xFFFFFFD8 (6) 0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.1 Mod 4 Fixpack 4 or higher * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : IT23768 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 04.05.2018 27.11.2018 27.11.2018 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |