suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT31753 Status: Closed

"BOTH LOG PATHS SEEM TO BE BAD, TRY PATH1" MESSAGES IN DB2DIAG.LOG

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem 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 : 
LFR Scan Num            = xxx
LFR Scan Caller's EDUID = xxx
Both log paths seem to be bad, try path1. extentNum = xxx
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* Db2 V10.5 FP 10 and below                                    *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 V10.5 FP 11                                   *
****************************************************************
Local Fix:
This is not an error from Db2 side and these messages can be
ignored
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* Db2 V10.5 FP 10 and below                                    *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 V10.5 FP 11                                   *
****************************************************************
Comment
First fixed in Db2 V10.5 FP 11
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.02.2020
30.06.2020
30.06.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)