|
Problem IC97523
|
Status: Closed |
DB2FLSN -LSO MAY RETURN A WRONG LOG FILE NAME |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
db2flsn -lso option returns the log file name which includes
given LSO. Since an LSO is a 64 bit integer, it could take up as
many as 20 digits. However, db2flsn may return a wrong file name
when the LSO is more than 10 digits.
For example,
$ db2flsn -db qtest -lso 3799977715223
Given PSO is contained in log page 61122 in log file
S0000014.LOG.
$ db2flsn -db qtest -lso 3799977715
Given PSO is contained in log page 61122 in log file
S0000014.LOG.
After the fix, we can get a correct number:
$ db2flsn -db qtest -lso 3799977715223
Given PSO is contained in log page 9 in log file S0013008.LOG. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users using db2flsn command *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.5 Fix Pack 3. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 Version 10.5 Fix Pack 3. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.11.2013
24.03.2014
24.03.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
