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

Db2 Version 11.1 Mod 4 Fix Pack 5 for Linux, UNIX, and Windows

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