IBM Support

IT25589: LIST HISTORY COMMAND FAILS WITH DB21018E ERROR WHEN THE HISTORY FILE CONTAINS A DROPPED TABLE EVENT WITH LONGER TABLE NAME.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • LIST HISTORY command fails with DB21018E error when the history
    file contains a DROPPED TABLE event which the length of the
    table name is longer than 128KB.
    
    
    $ db2 list history dropped table all for sample
    
                        List History File for sample
    
    Number of matching file entries = 1
    
    
     Op Obj Timestamp+Sequence Type Dev Earliest Log Current Log
    Backup ID
     -- --- ------------------ ---- --- ------------ ------------
    --------------
      D  T  20180628135510
    000000000000253700040004
    
    ----------------------------------------------------------------
    ------------
      "DB2INST1 "."TABLE1" resides in 1 tablespace(s):
    
     00001 TS8K
    
    ----------------------------------------------------------------
    ------------
        Comment: DROP TABLE
     Start Time: 20180628135510
       End Time: 20180628135510
         Status: A
    
    ----------------------------------------------------------------
    ------------
      EID: 5
    
    DB21018E  A system error occurred. The command line processor
    could not
    continue processing.
    
    
    The db2diag.log shows SQLO_QUE_BAD_HANDLE error as follows:
    
    2018-06-28-14.11.52.809384-240 E82157A699           LEVEL: Error
    (OS)
    PID     : 29294808             TID : 1              PROC : db2bp
    INSTANCE: db2inst1             NODE : 000
    HOSTNAME: db2server
    EDUID   : 1
    FUNCTION: DB2 UDB, oper system services, sqlowqueInternal,
    probe:40
    MESSAGE : ZRC=0x870F003E=-2029060034=SQLO_QUE_BAD_HANDLE "Bad
    Queue Handle"
              DIA8555C An invalid message queue handle was
    encountered.
    CALLED  : OS, -, msgsnd
    OSERR   : EINVAL (22) "A system call received a parameter that
    is not valid."
    DATA #1 : system V message queue identifier.,
    PD_TYPE_SYSV_QUEUE_ID, 4 bytes
    0x43544554
    DATA #2 : Pointer, 8 bytes
    0x000000011088f080
    DATA #3 : unsigned integer, 8 bytes
    65527
    

Local fix

  • Delete the problematic event by PRUNE HISTORY command.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher                *
    ****************************************************************
    

Problem conclusion

  • First fixed in Db2 11.1 Mod 4 Fixpack 5
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT25589

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    A50

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-07-05

  • Closed date

    2020-01-16

  • Last modified date

    2020-01-16

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

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

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RB10 PSN

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.5","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
04 May 2022