DB2 - Problem description
Problem IT25035 | Status: Closed |
DB2 MAY REPORT A 'SEVERE' LEVEL MESSAGE WITHIN THE DB2OPTSTATS LOG WHEN COLLECTING RUNSTATS ON A TABLE IN LOAD PENDING STATE | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
When collecting RUNSTATS on a table that is in LOAD PENDING state, Db2 may report a 'Severe' level message in the db2optstats diagnostic log with message text "ACCESS TABLE WHEN IN RESTRICTED STATE". This message is expected, but the message level should not be 'Severe'. The following is an example of such an entry in the db2optstats log: 2018-05-10-10.35.54.881135-240 I1614704E1100 LEVEL: Severe PID : 16018 TID : 140464682428160 PROC :db2sysc INSTANCE: NODE : 000 DB : TESTDB APPHDL : 0-53 APPID: AUTHID : HOSTNAME: EDUID : 70 EDUNAME: db2agent (TESTDB) FUNCTION: DB2 UDB, relation data serv, sqlrLocalRunstats, probe:12996 MESSAGE : ZRC=0x8004002E=-2147221458=SQLD_ACCESSRESTRICTED "ACCESS TABLE WHEN IN RESTRICTED STATE" DIA8070C Attempt to access a table in a restricted state. DATA #1 : unsigned integer, 8 bytes 10954 DATA #2 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -668 sqlerrml: 12 sqlerrmc: 3 SCHEMA.MYTABLE sqlerrp : sqldTblR sqlerrd : (1) 0x8004002E (2) 0x0000002E (3) 0x00000000 (4) 0x00000000 (5) 0xFFFFD536 (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: * * None * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : IT25023 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 10.05.2018 11.12.2018 11.12.2018 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |