|
Problem IC63780
|
Status: Closed |
SQL1619N MAY BE ENCOUNTERED WHEN DROPPING AN EVENT MONITOR. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
A timing hole exists when the event monitor is shutting down
(set event monitor state 0) and when the event monitor is
dropped. The condition may arise where the event monitor cannot
be dropped due to the state 0 invocation. Event monitors may
still exist even though the client has requested it to be
dropped. As this occurs after the shutting down of the event
monitor; no real harm exists to the database or instance.
DROP EVENT MONITOR <name>
leads to
>>
DB21034E The command was processed as an SQL statement because
it was not a valid Command Line Processor command. During SQL
processing it
returned:
SQL1619N Cannot DROP an active event monitor. SQLSTATE=55034 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* A timing hole exists when the event monitor is shutting down *
* (set event monitor state 0) and when the event monitor is *
* dropped. The condition may arise where the event monitor *
* cannot be dropped due to the state 0 invocation. Event *
* monitors may still exist even though the client has *
* requested it to be dropped. As this occurs after the *
* shutting down of the event monitor; no real harm exists to *
* the database or instance. *
* DROP EVENT MONITOR <name> leads to *
* *
* >> *
* *
* DB21034E The command was processed as an SQL statement *
* because *
* it was not a valid Command Line Processor command. During *
* SQL *
* processing it *
* *
* returned: *
* *
* SQL1619N Cannot DROP an active event monitor. SQLSTATE=55034 *
****************************************************************
* RECOMMENDATION: *
* Recommended to upgrade to v97FP1 *
**************************************************************** |
| Local Fix: |
You should be able to bypass the issue by adding a sleep
between the deactivate and the drop. |
| 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 |
The problem has been fixed in v97 fix pack 1. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 15.10.2009
24.02.2010
24.02.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
|
 |
