IBM Support

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

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error 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.
    

Local fix

  • None.  If you see error SQL0804N, consider the possibility that
    the error might be masking a deadlock condition (SQL0911N)
    instead.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 Version 9.7 Fix Pack 7.                       *
    ****************************************************************
    

Problem conclusion

  • This problem is first fixed in DB2 Version 9.7 Fix Pack 7.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC85989

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-08-20

  • Closed date

    2012-10-20

  • Last modified date

    2012-10-20

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    IC88629

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.7","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
20 October 2012