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 IT03452 Status: Geschlossen

db2top's Utility screen can list utilities running against database
different from specified database

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
If you run db2top with the -d <databasename> parameter, when you 
take the option to list utilities (u) you will see the utilities 
(BACKUP, RUNSTATS, REORG, LOAD,  or RESTORE ) running for any 
database not just for the database that was defined with the -d 
parameter when running db2top. 
 
For example, if you have two databases called SAMPLE and TEST. 
Start a backup on the SAMPLE database and then run 'db2top -d 
test'. If you then type 'u' you will see the backup running on 
the SAMPLE database.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All user of db2top                                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW 10.1 Fix Pack 5                           * 
****************************************************************
Local-Fix:
Lösung
First fixed in DB2 LUW 10.1 Fix Pack 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
29.07.2014
13.07.2015
13.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList