Register Login

Checking pool tables and cluster tables

Updated May 18, 2018

You want to check all pool tables or cluster tables in the system.

This SAP Note provides an overview of the available check reports.


This report is available in all Releases >=46C via SAP Note 1077403. It checks if there are corrupt or initial cluster records. You can check individual table clusters (for example RFBLG) or all table cluster sequentially in one run.
The report may have long runtimes for large datasets (see also section "Runtime" in SAP Note 1309728).


The report is available in all Releases with SAP BASIS 6.20 or higher. For a certain table pool, you can check the contained pool tables for their readability.
An improved version of the report is provided shortly with SAP Note 1807959. This version handles all table pools sequentially in a mass check.


The report is available in all Releases as of SAP BASIS 6.20 or higher (see SAP Note 700486). It checks if the BCD number are correct in a table that you must specify individually.
SAP Note 1807959 provides an improved version of the report. As a result, all pool tables and cluster tables can then be handled sequentially in a mass check.


Completely independent of scheduled migrations, the reports SDBI_CLUSTER_CHECK and SDBI_POOL_CHECK should be executed every once in a while (for example, once a year). The reports are designed in such a way that they should not disturb the production operation.

For the Unicode and SAP HANA migrations, we recommend that you execute the reports SDBI_CLUSTER_CHECK for all cluster tables as well as SDBI_CHECK_BCD_NUMBERS for all pool tables and cluster tables in time before the scheduled migration date. You should execute the reports several months before the migration date because they can have very long runtimes and if errors should occur, you need time to correct them.
In addition, you must carry out a test migration, if possible with a copy of the productive data. If there is not enough time to execute the reports and to carry out the test migration, you should in any case carry out the test migration. If no errors occur during this, the reports would normally not find anything either. If there are errors during the test migration:

  • The errors hint at problems with decimal numbers (packed numbers, BCD numbers): You can use report SDBI_CHECK_BCD_NUMBERS to analyze the problem selectively. For an SAP HANA migration and pool tables, the problems would become visible during the mass conversion in the target system; you can execute the report either in the source or in the target system. For cluster tables, such problems would occur mainly during the INSERT into the tables that are now transparent during the import to the SAP HANA database; you would have to execute the report in the source system and repeat the export after the data correction.
  • During the R3load export with declustering or Unicode migration, decompression errors occur in cluster tables or initial cluster records. You can use report SDBI_CLUSTER_CHECK in the source system to analyze the problem in more detail. After you correct the data in the source system, you must repeat the export.