|
Problem IT38576
|
Status: Closed |
DB2DIAG.LOG MESSAGE WITH ERROR "FILE NOT FOUND" IN "SQLPGOPENLOGEXTENTANDUNCOMPRESSFORLFR, PROBE:4075" MAY BE MISLEADING
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
Customers may encounter the following error in db2diag.log:
2021-09-20-03.57.53.172245-420 I95863A871 LEVEL: Error
PID : 5001 TID : 4390773582096 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : BPMDB
HOSTNAME: MYHOST1
EDUID : 97 EDUNAME: db2lfr.0 (BPMDB) 0
FUNCTION: DB2 UDB, data protection services,
sqlpgOpenLogExtentAndUncompressForLFR, probe:4075
MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found."
DIA8411C A file "" could not be found.
DATA #1 : db2LogStreamIDType, PD_TYPE_DB2_LOG_STREAM_ID, 2 bytes
0
DATA #2 : String, 0 bytes
Object not dumped: Address: 0x0000000000000000 Size: 0 Reason:
Address is NULL
DATA #3 : SQLPG_EXTENT_NUM, PD_TYPE_SQLPG_EXTENT_NUM, 4 bytes
1490160
This message should be at INFO level as it's not considered an
ERROR at this layer. This APAR will change this message to INFO
level. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Databases using log archiving *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Message can be ignored on its own. To avoid frequency *
* install the latest fix pack. *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Databases using log archiving *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Message can be ignored on its own. To avoid frequency *
* install the latest fix pack. *
**************************************************************** |
| Comment |
Problem was first fixed in Db2 Version 11.5.6.0. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 01.10.2021
02.12.2021
03.04.2022 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
