|
Problem IT25952
|
Status: Closed |
DB2 V11.1: GETTING STMM DATABASE NAME IS NOT VALID MESSAGES IN DB2DIAG.LOG
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
2018-07-30-13.20.19.555084-360 E3010603A3836 LEVEL: Warning
PID : 7995728 TID : 59083 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : ***
APPHDL : 0-58922 APPID: ***
AUTHID : DB2INST1 HOSTNAME: ***
EDUID : 59083 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, buffer pool services, sqlbFindPageInBPOrSim,
probe:2006
MESSAGE : ZRC=0x00000003=3
SQL0003N The database name is not valid.
DIA8003C The interrupt has been received.
DATA #1 : String, 41 bytes
Excessive retries while removing STMM BPD
DATA #2 : unsigned integer, 4 bytes
300
DATA #3 : Buffer page descriptor, PD_TYPE_SQLB_BPD, 112 bytes
Pagekey: {pool:4;obj:337;type:0} PPNum:51226
objectPageNum: 0
bucketGroupHashIndex: -1
hashnext: 0x0000000000000000
hashprev: 0x0000000000000000
bpdLatch:
SXLatch :etc....
This does not affect the performance and/or functionality of
your database. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL using Self Tuning Memory *
****************************************************************
* PROBLEM DESCRIPTION: *
* db2diag.log file is recording messages like: *
* 2018-07-30-13.20.19.555084-360 E3010603A3836 LEVEL: Warning *
* PID : 7995728 TID : 59083 PROC : db2sysc 0 *
* INSTANCE: db2inst1 NODE : 000 DB : SAMPLE *
* APPHDL : 0-58922 APPID: 192.168.1.1.46277.180731100134 *
* AUTHID : DB2INST1 HOSTNAME: bugdbug *
* EDUID : 59083 EDUNAME: db2agent (SAMPLE) 0 *
* FUNCTION: DB2 UDB, buffer pool services, *
* sqlbFindPageInBPOrSim, *
* probe:2006 *
* MESSAGE : ZRC=0x00000003=3 *
* SQL0003N The database name is not valid. *
* *
* DIA8003C The interrupt has been received. *
* DATA #1 : String, 41 bytes *
* Excessive retries while removing STMM BPD *
* DATA #2 : unsigned integer, 4 bytes *
* 300 *
* DATA #3 : Buffer page descriptor, PD_TYPE_SQLB_BPD, 112 *
* bytes *
* Pagekey: {pool:4;obj:337;type:0} PPNum:51226 *
* objectPageNum: 0 *
* bucketGroupHashIndex: -1 *
* hashnext: 0x0000000000000000 *
* hashprev: 0x0000000000000000 *
* bpdLatch: *
* *
* SXLatch :etc.... *
* *
* This does not affect the performance and/or functionality of *
* your database, other than STMM may be a bit slower to tune *
* memory. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 11.1.4 *
**************************************************************** |
| Local Fix: |
- Upgrade to v11.1m4fp4 |
| Solution |
|
| Workaround |
To stop the error you could update the diaglevel to 2 but this
will also reduce other useful information that may be written to
the db2diag.log file at diaglevel 3
ie db2 update dbm cfg using diaglevel 2 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.08.2018
03.06.2019
03.06.2019 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
