home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC85989 Status: Closed

A ROLLBACK DURING EXECUTION OF AN ANONYMOUS BLOCK REPORTS SQLCODE -804
(INVALID MODE), INSTEAD OF SQLCODE -911

product:
DB2 FOR LUW / DB2FORLUW / 970 - 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 9.7 Fix Pack 7.                       * 
****************************************************************
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 9.7 Fix Pack 7 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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
This problem is first fixed in DB2 Version 9.7 Fix Pack 7.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC88629 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.08.2012
20.10.2012
20.10.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP7
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.7 FixList