DB2 - Problem description
Problem IC75908 | Status: Closed |
DB2CAEM TOOL FAILS FOR ACTIVTY EVENT MONITORS THAT DON'T HAVE THE DEFAULT EVENT MONITOR TABLE NAMES | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
When an activity event monitor is created, a user can specify the target table schemas and names. The db2caem tool takes activity event monitor name as input. If the user has created the activity event monitor this way, db2caem fails with -204. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * N/A * **************************************************************** * PROBLEM DESCRIPTION: * * When an activity event monitor is created, a user can * * specify the target table schemas and names. The db2caem tool * * takes activity event monitor name as input. If the user has * * created the activity event monitor this way, db2caem fails * * with -204. * **************************************************************** * RECOMMENDATION: * * Upgrade to V97FP5 and above releases. * **************************************************************** | |
Local Fix: | |
The workaround for this would be to create public aliases for the event monitor tables which match the default names the event monitor would generate. E.g. if your activity table in your activity event monitor (called mymon) is called act1, you would create a public alias for act1 called activity_mymon. Similarly if your activitystmt table is actstmt2, you would create alias for actstmt2 with activitystmt_mymon. Same should be done for your activityvals table, if your activityvals table has name actvals3, you would create alias for actvals3 with activityvals_mymon. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
In V97FP5, db2caem -d <db> -actevm -appid -uowid -actid will support the activity event monitor with user specified table names and schemas. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 20.04.2011 07.12.2011 07.12.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP5 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.5 |