|
Problem IT22464
|
Status: Closed |
DB2DIAG.LOG FILLED WITH ERROR ON FUNCTION SQLBFINDPAGEINBPORSIMPROBE: 1952 SQL0003N THE DATABASE NAME IS NOT VALID |
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
After upgrading to DB2 11.1 FP2, error messages similar to the
following can be seen:
2017-09-17-01.27.19.467245+120 E3696412E3814 LEVEL:
Error
PID : 10599 TID : 103
PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
DB : DB1
APPHDL : 0-10 APPID: xx.xx.xx.xx
AUTHID : DB2INST1 HOSTNAME: localhost
EDUID : 714 EDUNAME: db2agnts (DB1) 0
FUNCTION: DB2 UDB, buffer pool services, sqlbFindPageInBPOrSim,
probe:1952
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
100
DATA #3 : Buffer page descriptor, PD_TYPE_SQLB_BPD, 112 bytes
Pagekey: {pool:886;obj:4;type:0} PPNum:4485018
.....
This message is expected and can be ignored if there are no
other symptoms. This message should not be logged as an Error. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.1 Mod 3 Fix Pack 3 or higher *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
|
| Solution |
First fixed in Db2 11.1 Mod 3 Fix Pack 3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 20.09.2017
19.03.2018
19.03.2018 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
