Before you can change partitioning storage conditions, you must unload data; after you have changed the partitioning storage conditions, you must reload the data. It is important that you check that the original number of items of data before the change matches the number of items of data after the data has been re-registered. The two methods described below are provided for this purpose. If you need a highly accurate check of the number of data items, we recommend that you use the second method.

• Using the number of data items output by the utility
  
  1. Record the number of items of data that were unloaded, which is indicated in the KFPL00723-I message that is output when the database reorganization utility has executed.
  2. After you change the partitioning storage conditions, record the number of items of data that are loaded, which is indicated in the KFPL00723-I message that is output during data loading. If you load data into multiple RDAREAs, record the grand total.
  3. Make sure that the number of data items in step 1 matches the number of data items in step 2.
• Executing the database condition analysis utility before and after a change in partitioning storage conditions
  You can check the number of items of data stored in RDAREAs by executing a condition analysis for each table with the database condition analysis utility (pddbst).
  
  1. Execute a condition analysis for each table with the database condition analysis utility (pddbst) and record the grand total of the values shown as the Row Count for each target RDAREA, as indicated in the following example:
     

     pddbst -t table-name -s

     The following are the execution results:
     

     RD Area Name : RD002 Server : bes1 Status : Original RD Area Name : RD002 Generation Number : 0 Replica RD Area Count : 0 History1 Hold Status : Hold Code : 0 Hold Time : History2 Hold Status : Hold Code : 0 Hold Time : Job Name : Line Count : Index Method : Unused Segment: 3999 Search Mode : INS Segment Reuse : - segments Reuse Search Failure : 0/ 0 Used(Full) Used( Full) Sum Segment 100%( 0%) 1( 0) 1 Page 30%( 0%) 3( 0) 10 Row Count : 200 RD Area Name : RD004 Server : bes2 Status : Original RD Area Name : RD004 Generation Number : 0 Replica RD Area Count : 0 History1 Hold Status : Hold Code : 0 Hold Time : History2 Hold Status : Hold Code : 0 Hold Time : Job Name : Line Count : Index Method : Unused Segment: 3999 Search Mode : INS Segment Reuse : - segments Reuse Search Failure : 0/ 0 Used(Full) Used( Full) Sum Segment 100%( 0%) 1( 0) 1 Page 20%( 0%) 2( 0) 10 Row Count : 100

  2. After you change the partitioning storage conditions and use the database load utility to load the data, use the same procedure as in step 1 and again record the grand total.
  3. Check that the grand total obtained in step 1 matches the grand total obtained in step 2.

If the numbers of data items do not match, the following are possible causes and corrective measures:

Possible cause	Corrective measure
When the database load utility was executed to load data, the creation mode was used. You must use the addition mode.	You must use a backup to restore the system, then re-execute the utility.
Data loading was not executed for the RDAREA into which the data was supposed to be loaded.	Load data from the unload data file into the correct RDAREA.