IBM Support

IC65090: DATABASE WAS MARKED BAD THE FOLLOWING STEP, IF THE CLIENT SEND BAD BUFFER.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DATABASE was MARKED BAD the following step, if the client send
    bad buffer.
    
    From db2diag.log
    2009-11-07-09.27.17.114687+540 I11711164A443      LEVEL: Severe
    PID     : 1232938              TID  : 1           PROC :
    db2agent (XXXX) 0
    INSTANCE: db2inst1                 NODE : 000         DB   :
    XXXX
    APPHDL  : 0-1605               APPID:
    XXX.XXX.XXX.XXX.5380.091106234124
    AUTHID  : XXXX
    FUNCTION: DB2 UDB, global services, sqlzeMapZrc, probe:45
    DATA #2 : Hexdump, 4 bytes
    0x0FFFFFFFFFFEEF88 : 8736 0009
    .6..
    
    2009-11-07-09.27.17.162175+540 I11711608A439      LEVEL: Severe
    PID     : 1232938              TID  : 1           PROC :
    db2agent (XXXX) 0
    INSTANCE: db2inst1                 NODE : 000         DB   :
    XXXX
    APPHDL  : 0-1605               APPID:
    XXX.XXX.XXX.XXX.5380.091106234124
    AUTHID  : XXXX
    FUNCTION: DB2 UDB, relation data serv, sqlrr_signal_handler,
    probe:50
    MESSAGE : DIA0505I Execution of a component signal handling
    function has begun.
    
    ... snip ...
    
    2009-11-07-09.27.17.213713+540 I11730442A485      LEVEL: Severe
    PID     : 1232938              TID  : 1           PROC :
    db2agent (XXXX) 0
    INSTANCE: db2inst1                 NODE : 000         DB   :
    XXXX
    APPHDL  : 0-1605               APPID:
    XXX.XXX.XXX.XXX.5380.091106234124
    AUTHID  : XXXX
    FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:20
    RETCODE : ZRC=0x87360009=-2026504183=SQLJC_ERROR_BEOF "DATA DOES
    NOT EXIST"
              DIA8506C Unexpected end of file was reached.
    
    ... snip ...
    
    2009-11-07-09.27.17.214189+540 I11730928A769      LEVEL: Severe
    PID     : 1232938              TID  : 1           PROC :
    db2agent (XXXX) 0
    INSTANCE: db2inst1                 NODE : 000         DB   :
    XXXX
    APPHDL  : 0-1605               APPID:
    XXX.XXX.XXX.XXX.5380.091106234124
    AUTHID  : XXXX
    FUNCTION: DB2 UDB, trace services, sqlt_logerr_data, probe:0
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
     sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -902   sqlerrml: 1
     sqlerrmc: 9
     sqlerrp : SQLRI1EC
     sqlerrd : (1) 0x87360009      (2) 0x00000009      (3)
    0x00000000
               (4) 0x00000000      (5) 0xFFFFFE0C      (6)
    0x00000000
     sqlwarn : (1)      (2)      (3)      (4)        (5)       (6)
               (7)      (8)      (9)      (10)        (11)
     sqlstate:
    
    2009-11-07-09.27.17.304362+540 E11786942A394      LEVEL: Severe
    PID     : 1232938              TID  : 1           PROC :
    db2agent (XXXX) 0
    INSTANCE: db2inst1                 NODE : 000         DB   :
    XXXX
    APPHDL  : 0-1605               APPID:
    XXX.XXX.XXX.XXX.5380.091106234124
    AUTHID  : XXXX
    FUNCTION: DB2 UDB, base sys utilities, sqleMarkDBad, probe:10
    MESSAGE : ADM7518C  "XXXX    " marked bad.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Server may trap.                                             *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See the APAR description.                                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 UDB version 9.1 fixpack 9.                    *
    ****************************************************************
    

Problem conclusion

  • Problem was first fixed in DB2 UDB Version 9.1 FixPack 9.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC65090

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-12-10

  • Closed date

    2010-04-13

  • Last modified date

    2010-04-13

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

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

    IC65092 IC65093

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R910 PSN

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
13 April 2010