home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT06639 Status: Geschlossen

DB2FLSN RUNS VERY SLOWLY WITH NON-INSTANCE USER

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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.
Lösung
The problem is firstly fixed on V10.5 FIXPACK 7.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
21.01.2015
20.01.2016
20.01.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList