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

DB2FLSN RUNS VERY SLOWLY WITH NON-INSTANCE USER

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
By default, non-instance user has no read permission on 
transaction logs. So, when a non-instance user calls db2flsn, 
reading of logs should fail with "Access Denied" error, after 
that, db2flsn will attempt to use the history file to determine 
the correct log file. In this case, db2flsn may run very slowly 
if the database has a big size history file. 
 
To determinate this problem, you can collect a db2trc. You 
should find sqlpScanHistFileForRecoveryList() takes long time to 
return: 
 
29082          8.323103056   sqlpScanHistFileForRecoveryList 
entry 
<skipped> 
628801        28.911907613   sqlpScanHistFileForRecoveryList 
exit
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* N/A                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2  V10.5 FIXPACK 7.                             * 
****************************************************************
Local Fix:
PRUNE HISTORY FILE to reduce its size.
Solution
The problem is firstly fixed on V10.5 FIXPACK 7.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.01.2015
20.01.2016
20.01.2016
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList