IT23318: INCORRECT MISSING LOG FILE NUMBER IS REPORTED IN ERROR MESSAGES

Db2 Version 11.1 Mod 4 Fix Pack 5 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 6 for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error description

• Readlog program may receive the following error when log file
  present in the log path it is reading from.
  
  SQL1273N  An operation reading the logs on database "SAMPLE"
  cannot continue because of a missing log file "S0011959.LOG" on
  database partition "0" and log stream "0".
  
  db2diag.log:
  
  2016-09-22-11.52.37.445655+480 E117441A544          LEVEL: Error
  PID     : 5767254              TID : 14740          PROC :
  db2sysc 0
  INSTANCE: db2inst1          NODE : 000           DB   :  SAMPLE
  APPHDL  : 0-148                APPID:
  *LOCAL.db2inst1.160922035241
  AUTHID  : db2inst1              HOSTNAME: myhost
  EDUID   : 14740                EDUNAME: db2agent (SAMPLE) 0
  FUNCTION: DB2 UDB, data protection services, sqlpgReadLogAPI,
  probe:1
  DATA #1 : String, 12 bytes
  S0011959.LOG
  DATA #2 : String, 1 bytes
  0
  DATA #3 : String, 1 bytes
  0
  
  Checking db2diag.log, the missing log file is actually
  S0011958.LOG:
  
  2016-09-22-11.55.29.957502+480 E228419A996          LEVEL: Error
  PID     : 5767254              TID : 15511          PROC :
  db2sysc 0
  INSTANCE: db2inst1          NODE : 000           DB   : SAMPLE
  APPHDL  : 0-171                APPID:
  *LOCAL.db2inst1.160922035530
  AUTHID  : db2inst1            HOSTNAME: myhost
  EDUID   : 15511                EDUNAME: db2shred (SAMPLE) 0
  FUNCTION: DB2 UDB, recovery manager, sqlpshrFindExtentForLfsLsn,
  probe:700
  MESSAGE : ZRC=0x86100026=-2045771738=SQLPR_MISSING_LOG_EXT
            "Used by various operations reading the logs to
  indicate a missing log extent."
  DATA #1 : String, 200 bytes
  Could not find an extent with starting LFS/LSN value prior to
  the given LFS/LSN.
  Check if previous logs are missing, starting from
  missingExtentNum.
  startSearchExtent / missingExtentNum / searchLfsLsn
  DATA #2 : unsigned integer, 4 bytes
  11960
  DATA #3 : unsigned integer, 4 bytes
  11958
  DATA #4 : LFS/LSN, PD_TYPE_SQLP_LFS_LSN_PAIR, 16 bytes
  14852930/000000008C1661FB
  

Local fix

• Check db2diag.log, searching key word "missingExtentNum" to find
  the correct missing log file number manually.
  

Problem summary

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

Problem conclusion

• First fixed in Db2 11.1 Mod 4 Fixpack 5
  

Temporary fix

Comments

APAR Information

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

  IT17551

• 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