10.7 Error handling procedures

  1. If pdrbal's return code is 8, check the error message, correct the error, then re-execute pdrbal.
  2. If the KFPL33003-I message (STATUS=END) is displayed during the execution of pdrbal, table rebalance processing has terminated normally. Therefore, once this message is issued, there is no need to re-execute pdrbal, even if an error occurs thereafter.
  3. If an error occurs during batch index creation in the exclusive mode (return code = 8), eliminate the cause of the error and then execute batch index creation (-k ixmk) using pdrorg along with the index information files for the index that resulted in an error. Then, execute pdrbal.
  4. If the KFPL15240-E message (memory shortage) is issued while a compressed table is being rebalanced in the shared mode, and if you can allocate the required memory in the shared mode, re-execute the utility in the shared mode. For details about the memory capacity required for execution, see the HiRDB Version 9 Installation and Design Guide.
  5. If rollback occurs during the execution of pdrbal, the action to be taken depends on the log acquisition method (-l option). The table below the action to be taken in the event of rollback during execution of pdrbal.

    Table 10-13 Action to be taken in the event of a rollback during the execution of pdrbal

    Log acquisition method (-l option)pdrbal processing
    RebalancingBatch index creation (exclusive mode)
    aDatabase statusThe row data that was rolled back has not been moved. The preceding row data have already been moved.Index is placed in unfinished status.
    ActionRe-execute pdrbal.Execute batch index creation (-k ixmk) using pdrorg. In this case, use the index information files that resulted in an error.
    nDatabase statusThere is no guarantee.There is no guarantee.
    ActionRestore the database from its backup copy, then re-execute pdrbal.Reinitialize the corresponding index storage RDAREAs and re-create the index (-k ixrc) using pdrorg.