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 IT36569 Status: Closed

DB2FLSN TOOL INCORRECTLY DISPLAYS "N/A" AS THE MAXIMUM LSN FOR ALOG FILE
INSTEAD OF THE ACTUAL MAXIMUM LSN VALUE.

product:
DB2 FOR LUW / DB2FORLUW / B50 - DB2
Problem description:
In some cases, when a log file has a maximum LSN value, the
db2flsn tool may display the maximum LSN value as "N/A" instead
of the actual value.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* All                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to v11.5.6.0                                         *
****************************************************************
Local Fix:
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* All                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to v11.5.6.0                                         *
****************************************************************
Comment
Apply Db2 v11.5.6.0
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.04.2021
09.06.2021
09.06.2021
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)