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 IT03464 Status: Geschlossen

SQL20540N (-1224) WHEN RUNNING AUTONOMOUS TRANSACTION DUE TO PLAN LOCK WHEN
INTERNAL CLI PACKAGE IS INVALID

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
An autonomous transaction can fail with the following error when 
being executed from the command line: 
 
SQL20540N  An autonomous transaction executing a procedure has 
been terminated 
abnormally. Routine name: "BEGIN...END". Specific name: 
"SYSIBMINTER". Reason 
code: "-1224".  SQLSTATE=560D2 
 
This can happen if an internal DB2 "CLI" package package (eg, 
NULLID.SYSSH200 or NULLID.SYSLH202) is invalid.   This creates 
an exclusive Internal Plan Lock which ultimately causes the CLP 
and autonomous transaction to deadlock. 
 
Example lock scenario: 
 
 $ db2pd -wlocks -db origins 
 
AppHandl [nod-index] TranHdl    Lockname                   Type 
Mode Conv Sts CoorEDU    AppName  AuthID   AppID 
 
19336    [000-19336] 29         5359534C564C3031956EB7B441 
Internal P ..X       G   131168     db2bp    db2abc 
*LOCAL.db2abc.140716171832 
19358    [000-19358] 26         5359534C564C3031956EB7B441 
Internal P ..S       W   58608      prepAnon db2abc 
*LOCAL.DB2.140716172013
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1, Fixpack 5                       * 
****************************************************************
Local-Fix:
Explicitly rebind the invalid package using the REBIND command 
or the db2rbind utility prior to executing the autonomous 
transaction.
Lösung
Fixed in DB2 Version 10.1, Fixpack 5
Workaround
see Local Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
29.07.2014
14.07.2015
14.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList