IT26704: ADMIN_MOVE_TABLE: OUTPUT OF OPERATION ESTIMATE MAY RETURN SOURCETABLE SIZES OF -4 AND SMALLER

APAR status

• Closed as program error.

Error description

• When the stored procedure ADMIN_MOVE_TABLE is called with
  operation ESTIMATE, the size of the target table is estimated.
  
  The result set also shows the calculated size of the source
  table (SOURCE_SIZE) in kB:
  e.g.:
  CALL
  SYSPROC.ADMIN_MOVE_TABLE('<SCHEMA>','<TABANME>','','','ESTIMATE'
  )
  
  
  	  Result set 1
  	  --------------
  
  	  TABSCHEMA TABNAME ROWS_SAMPLED         SOURCE_SIZE
  TARGET_SIZE          SOURCE_PCTPAGESSAVED TARGET_PCTPAGESSAVED
  	  --------- ------- -------------------- --------------------
  -------------------- -------------------- --------------------
  	  <SCHEMA>    <TABNAME>                    0
  -4
  0                   -1                    0
  
  	  1 record(s) selected.
  
  	  Return Status = 0
  
  The field SOURCE_SIZE is calculated by multiplying the field
  NPAGES of the catalog view SYSCAT.TABLES of the source table
  with its pagesize/1024. In case the statistics of the source
  table are missing (i.e NPAGES is -1) the calculated SOURCE_SIZE
  is shown directly in the result set of the stored procedure.
  
  With this APAR the reported SOURCE_SIZE is limited to -1 instead
  of displaying values as shown in the example above.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * users calling stored procedure ADMIN_MOVE_TABLE with         *
  * operation ESTIMATE                                           *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to the latest fix pack.                              *
  ****************************************************************
  

Problem conclusion

• Problem was first fixed in DB2 UDB Version 11.1 mod pack 4 fix
  pack 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