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

THE SYSIBMADM.SNAPDB ADMINISTRATIVE VIEW AND THE SYSPROC.SNAP_GE T_DB_V97(
<DBNAME> ) TABLE FUNCTION ARE MISSING ROWS.

Produkt:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problembeschreibung:
The SYSIBMADM.SNAPDB administrative view and 
SYSPROC.SNAP_GET_DB_V97( <dbname> ) table function should return 
one row of data for each member where the currently connected 
database is activated. On DB2 version 9.8 Fix Pack 2, 3 and 4 
this view and table function will return either no rows (if 
there is no member with the identifier 0 in the currently 
connected database) or 1 row for member 0.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users invoking the SYSIBMADM.SNAPDB view or the              * 
* SYSPROC.SNAP_GET_DB_V97(<dbname>) table function             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.8 Fix Pack 5.                       * 
****************************************************************
Local-Fix:
Use the SYSPROC.SNAP_GET_DB_V97(<dbname>,<member>) table 
function to explicitly request database snapshot data for each 
member of interest.
Lösung
This problem has been fixed in DB2 Version 9.8 Fix Pack 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
11.05.2012
18.06.2012
18.06.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.8.FP5
Problem behoben lt. FixList in der Version
9.8.0.5 FixList