IT32346: "BOTH LOG PATHS SEEM TO BE BAD, TRY PATH1" MESSAGES IN DB2DIAG.LOG MAY CAUSE PERFORMANCE DEGRADATION

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

• "Both log paths seem to be bad, try path1" messages in
  db2diag.log
  
  FUNCTION: DB2 UDB, data protection services,
  sqlplfrGetFileHandleToReadFrom, probe:5250
  DATA #1 : <preformatted>
  LFR Scan Num            = xxx
  LFR Scan Caller's EDUID = xxx
  Both log paths seem to be bad, try path1. extentNum = xxx
  
  If this message is produced repeatedly, it may cause a
  performance problem.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Db2 V11.1                                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to Db2 V11.1 FP6                                     *
  ****************************************************************
  

Problem conclusion

• First fixed in  Db2 V11.1 FP6
  

Temporary fix

Comments

APAR Information

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

  IT31753

• 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 PSY

     UP