|
Problem IC63167
|
Status: Closed |
CREATE EVENT MONITOR MAY CREATE TABLES IN SYSTOOLSPACE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When the CREATE EVENT MONITOR statement is used without
specifying a tablespace, the SYSTOOLSPACE tablespace may be
selected. In DPF configurations, this tablespace only exists on
the catalog partition. So the event monitor would only be able
to collect event information on the catalog partition.
This is an unpredictable problem in the sense that the
SYSTOOLSPACE is created automatically under the covers, so
depending on when it is created, it may or may not be used by
the event monitor. This problem affects write to table activity
event monitors and all event monitors that support the
unformatted event table target type. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* When the CREATE EVENT MONITOR statement is used without *
* *
* specifying a tablespace, the SYSTOOLSPACE tablespace may be *
* *
* selected. In DPF configurations, this tablespace only exists *
* on *
* the catalog partition. So the event monitor would only be *
* able *
* to collect event information on the catalog partition. This *
* affects the following *
* types of event monitors: *
* (a) activity event monitors using the write to table target *
* type *
* (b) any event monitor using an unformatted event table *
* target type. *
* *
* This is an unpredictable problem in the sense that the *
* *
* SYSTOOLSPACE is created automatically under the covers, so *
* *
* depending on when it is created, it may or may not be used *
* by *
* the event monitor. For example, if an event monitor were *
* created before *
* SYSTOOLSPACE were created, it would not use SYSTOOLSPACE and *
* there would be no problem. *
****************************************************************
* RECOMMENDATION: *
* Either explicitly specify a tablespace when creating a write *
* to table activity event monitor or an event monitor that *
* uses the unformatted event table target type, or upgrade to *
* DB2 Version 9.7 Fix Pack 1. *
**************************************************************** |
| Local Fix: |
The local workaround is to explicitly specify the tablespace
name as part of the CREATE EVENT MONITOR statement. As a best
practice, this should be done anyways, so that the user
controls where the tables are placed. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in DB2 Version 9.7 Fix Pack 1. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.09.2009
14.01.2010
14.01.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
