IC66213: DBEXPORT SHOULD CHECK IF THE NUMBER OF ROWS IN COMMENT MATCHES THE NUMBER OF ROWS IN THE UNLOAD FILE

APAR status

• Closed as program error.

Error description

• It might happen that the number of rows in the unload file does
  not match the number of rows in the comment. In such cases the
  dbimport will fail.
  
  dbimport often runs several hours and it is painful when it
  aborts after hours leaving a corrupted database. Customers rely
  that a successful dbexport is usable for dbimport.
  
  Example:
  mstab00100.unl contains 5 rows instead of 3
  
  { TABLE "informix".mstab row size = 14 number of columns = 2
  index size = 0 }
  { unload file name = mstab00100.unl number of rows = 3 }
  
  create table "informix".mstab
    (
      id serial not null ,
      c1 char(10)
    );
  
  revoke all on "informix".mstab from "public" as "informix";
  Import data is corrupted!
  
  Do you want to abort?y
  This import is now invalid.
  
  Calling dbimport with -c or continue although the number of rows
  is wrong is not an option because the imported data might not be
  consistent.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IDS 11.50 dbexport users with incorrect partition header     *
  * information.                                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * If users have a database with incorrect partition page       *
  * information (due to various reasons like page corruptions,   *
  * wrong statistics in partition page, running dbexport on HDR  *
  * secondary (before 11.50.xC6) or other unknown reasons).      *
  * dbexport didn't tell the user that it discovered this        *
  * problem and the exported data is invalid. The user could     *
  * only figure that out by dbimporting the invalid data, then   *
  * dbimport will throw an error. This is time consuming because *
  * dbimport could take a long time.                             *
  *                                                              *
  * Fix is to have dbexport tell the user that there are some    *
  * incorrect partition page information and the dbexport data   *
  * won't work with dbimport. Then user will have to go fix      *
  * their partition page.                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * upgrade to 11.50.xC8                                         *
  ****************************************************************
  

Problem conclusion

• Fix in 11.50.xC8 and newer.
  After dbexport, there will be a dbexport.out file, and inside
  that file user will see a message associated with the
  problematic table saying something like this...
  
  **Row count in partition page does not match the number of
  unloaded rows in this
   table : tab1. Run oncheck -cDl database:table and check for
  page consistency
  

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

  IBM IDS ENTRP E

• Fixed component ID

  5724L2304

Applicable component levels

• RB15 PSY

     UP