home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC62592 Status: Geschlossen

SQL1619N MAY BE ENCOUNTERED WHEN DROPPING AN EVENT MONITOR.

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 LUW server environments are affected.                * 
**************************************************************** 
* 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 DB2 LUW v95 fix pack 5.            * 
****************************************************************
Local-Fix:
You should be able to bypass the issue by adding a sleep 
between the deactivate and the drop.
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
The problem has been fixed in DB2 LUW v95 fix pack 5.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC63780 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
17.08.2009
24.02.2010
24.02.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP5
Problem behoben lt. FixList in der Version
9.5.0.5 FixList