Skip to Content
Author's profile photo Shailesh Patil

Corrective actions related to Partition Table errors


There are some specific scenarios where we need to delete entries from partition tables starting with /BIC/B* without which it does not allow deleting data from tables like PSA table, change log table etc.

  1. While deleting particular request from DSO object, the request becomes RED and it doesn’t allow deleting it.

  2. While deleting data from PSA or change log table either manually or through process chain.

When we go and check “Display log” for the deletion, it will give error saying that “Data inconsistency; Partition /BIC/B* not deleted” (different loads has different partition tables).

This error is basically due to system fails to delete the entries from partition table /BIC/B*, which is specified in error message.

Steps for Correction:

  1. Open the Program SAP_PSA_PARTNO_CORRECT in SE38 transaction               

  2. Specify partition table name (/BIC/B* mentioned in error message) in I_TABLNM input parameter and execute it. The data entries can be seen that are still present in the partition table.

  3. Execute this program again in Repair mode by setting I_REPAIR to delete data entries. After that, it will allow deleting DSO request or data in the PSA or Change log table.



This check report is used to deduct the possible problems of indices and other database related issues of the PSA. This report helps in deducting the following inconsistencies:

  1. Partitioning with global index
  2. Inconsistencies between DDIC definition and DB tables
  3. PSA definition without DDIC entry and vice-versa.

This report is available only for release 7.x.

 The following symptoms can be noticed during the activation of DTP, DSO and Data-sources. They may also occur during the write or activation of the data:

  1. ORA-01502: index ‘SAPDAT. /BIC/A*KE’ or partition of such index is in unusable state.

  2. ORA-20000: index “SAPGBP”.” /BIC/B*KE” or partition of such index is in unusable state. 


Run the report in check mode first and then execute the report in repair mode by setting i_repair = ‘X’. Refer the note 1012607 and 1558849 for more details.

Assigned tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.