DB2 FOR LUW / DB2FORLUW / A50 - DB2

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

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5, Fixpack 5                       * 
****************************************************************

Explicitly rebind the invalid package using the REBIND command 
or the db2rbind utility prior to executing the autonomous 
transaction.

First fixed in DB2 Version 10.5, Fixpack 5

see Local Fix.

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

31.07.2014
16.03.2015
16.03.2015