home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC94114 Status: Closed

DB2FLSN -LSO MAY RETURN A WRONG LOG FILE NAME

product:
DB2 FOR LUW / DB2FORLUW / A10 - 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:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 3.                      * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in Version 10.1 Fix Pack 3.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC97523 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.07.2013
24.10.2013
24.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList