|
Problem IC88629
|
Status: Closed |
A ROLLBACK DURING EXECUTION OF AN ANONYMOUS BLOCK REPORTS SQLCODE -804 (INVALID MODE), INSTEAD OF SQLCODE -911 |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
Under certain circumstances, the SQL compiler can report error
SQL0804N in response to a rollback, instead of the expected
error SQL0911N. This can happen during compilation of any SQL
procedure, compiled SQL function, or compiled trigger, but it
is most likely to occur during execution of a SQL PL compiled
compound statement, or PL/SQL anonymous block.
You will also see 'invalid mode' entries in db2diag.log,
similar to the following:
2011-09-16-17.51.39.952576-240 I2027A547 LEVEL: Error
PID : 1175556 TID : 1544 PROC : db2sysc
INSTANCE: devinst NODE : 000 DB : DB2
APPHDL : 0-7 APPID:
*LOCAL.devinst.110916215119
AUTHID : DEVINST
EDUID : 1544 EDUNAME: db2agent (DB2)
FUNCTION: DB2 UDB, relation data serv, sqlrr_spec_mode,
probe:150
MESSAGE : Invalid mode 1 is not supported for request 2.
DATA #1 : Hexdump, 4 bytes
0x070000000EBEF220 : 801A 006D
The SQL0804N error does not represent a functional problem in
and of itself, except that it can mask the actual error and
make it more difficult for you to determine why a compilation
has failed. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 Fix Pack 2. *
**************************************************************** |
| Local Fix: |
None. If you see error SQL0804N, consider the possibility that
the error might be masking a deadlock condition (SQL0911N)
instead. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
This problem is fixed in DB2 Version 10.1 Fix Pack 2. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.11.2012
18.01.2013
18.01.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.2
|
 |
| 10.5.0.2
|
|
