IBM Support

IT27263: FAILED REORG CAN BE SHOWED IN THE LIST HISTORY WITHOUT ERROR

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Even though a reorg command is forced by the force command,
    'list history' might not record the error such as SQL1224N which
    reorg command got from the command line. The procedure could be
    like as follows.
    
    1. Issued a reorg with the following command
    db2 reorg indexes all for table DBO.TESTTABLE allow write access
    cleanup all
    
    2. Force the thread running the reorg
    user1@server $ db2 force application"(34846)"
    DB20000I The FORCE APPLICATION command completed successfully.
    DB21024I This command is asynchronous and may not be effective
    immediately.
    
    3. And the reorg gets the following error
    SQL1224N The database manager is not able to accept new
    requests, has
    terminated all requests in progress, or has terminated the
    specified request
    because of an error or a forced interrupt. SQLSTATE=55032
    
    4. but list history shows no errors
    Op Obj Timestamp+Sequence Type Dev Backup ID
     -- --- ------------------ ---- --- --------------
     G I 20180926114435     N
    
    ----------------------------------------------------------------
    ------------
     Table: "DBO    "."TESTTABLE"
    
    ----------------------------------------------------------------
    ------------
     Log Stream ID Earliest Log Current Log
     ------------- ------------ ------------
                0 S0004000.LOG S0004000.LOG
    
    ----------------------------------------------------------------
    ------------
       Comment: REORG INDEXES CLEANUP ALL
     Start Time: 20180926114435
      End Time: 20180926114439
        Status: A
    
    ----------------------------------------------------------------
    ------------
     EID: 9845
    

Local fix

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

    IT27263

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-12-10

  • Closed date

    2020-01-20

  • Last modified date

    2020-01-20

  • 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":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
20 January 2020