IT24361: DB2 V11.1 DB2DIAG.LOG MESSAGE WITH ERROR "FILE NOT FOUND" IN "SQLPGOPENLOGEXTENT, PROBE:10000" MAY BE MISLEADING

Db2 Version 11.1 Mod4 Fix Pack4 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 4 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 6 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 5 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 7 for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error description

• With DB2 v11.1 customers may encounter the following error in
  db2diag.log:
  
  2018-02-14-20.04.05.495876+060 I1719476E537          LEVEL:
  Error
  PID     : 28251                TID : 140728109885184 PROC :
  db2sysc 0
  INSTANCE: db2                NODE : 000            DB   : SAMPLE
  HOSTNAME: myhost
  EDUID   : 2678                 EDUNAME: db2lfr.0 (FPR) 0
  FUNCTION: DB2 UDB, data protection services, sqlpgOpenLogExtent,
  probe:10000
  MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found."
            DIA8411C A file "" could not be found.
  DATA #1 : <preformatted>
  Error opening database log extent NNNN.
  
  This can typically happen when an online backup need to include
  a log file that was meanwhile archived and deleted.
  We have also seen the message when log files have to be
  reclaimed. As such this is typically not an error situation, but
  expected.
  
  An db2diag.log message that indicates an ERROR will typically
  alert the DBA and should be avoided if there is no problem.
  We will revisit the error handling in sqlpgOpenLogExtent to
  avoid this problem in the future.
  

Local fix

• Ignore the error message if there are no other problems
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * ALL                                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to Db2 11.1 Mod 4 Fixpack 4 or higher                *
  ****************************************************************
  

Problem conclusion

• First fixed in Db2 11.1 Mod 4 Fixpack 4
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  DB2 FOR LUW

• Fixed component ID

  DB2FORLUW

Applicable component levels

• RB10 PSN

     UP