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

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

product:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problem description:
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 Summary:
**************************************************************** 
* 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.
Solution
This problem has been fixed in DB2 Version 9.8 Fix Pack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.05.2012
18.06.2012
18.06.2012
Problem solved at the following versions (IBM BugInfos)
9.8.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.8.0.5 FixList