Basis Errors and Solutions

Symptom
1. You want all cluster tables to be checked for incorrect records (for example, before a Unicode migration or as regular maintenance measure).2. When you use SDBI_CLUSTER_CHECK to check cluster tables, the following problems occur:The report SDBI_CLUSTER_CHECK_PERFORM always terminates with the error TSV_TNEW_PAGE_ALLOC_FAILED.Non-Unicode systems report errors for the tables DSYO1 and DSYO2, even though the records are correct.Duplicates in logical tables are not found since the relevant check was missing.In the “Error report for SAP”, der system does not display the number of found faulty records correctly.Messages ERR_NOTF or ERR_ADD exist for cluster records that were deleted or modified during the check run.

Other terms

SDBI_CLUSTER_CHECK, R3check, TSV_TNEW_PAGE_ALLOC_FAILED
Reason and Prerequisites

The program R3check, which must be started at operating system level, is available to check cluster tables for incorrect records (for example, records that cannot be compressed) The program requires a special input file and it is not easy to operate (also see Note 89384).
The ABAP report SDBI_CLUSTER_CHECK facilitates a simplified check of cluster tables.
However, earlier versions of this report contained errors:
An internal table was not reset and this resulted in TSV_TNEW_PAGE_ALLOC_FAILED terminations.The system displayed very old cluster records as defective. Only non-Unicode systems contain these records. The tables DYSO1 and DSYO2 were previously affected by this error.In the “Error report for SAP”, the system issued an incorrect number of errors found if each table contained more than 9 errors.For Oracle databases in particular, the system issues the error messages ERR_ADD and ERR_NOTF for no reason. In the new versions of the check report, ERR_NOTF is no longer used. Before the system issues error message ERR_ADD, it checks whether an error actually occurred.

New attributes include:
Newer versions of the check report recognize errors in the sorting of the logical records of a cluster record.A version ID exists and the system displays this on the initial screen of the report SDBI_CLUSTER_CHECK and makes a note of this in the check log. The report SDBI_CLUSTER_CHECK_ERRREPORT also outputs the version ID.

Solution

The current version of the report has the ID01.2009.
Always use the latest version of the report.
This current report version is available directly in the Support Packages specified in this note. Alternatively, you can use transaction SNOTE to implement the version for Basis Release 6.20 and higher.For Releases 46C and 46D only, use the attached transport (also see Note 13719).

For more information, see Note1309728(operating instructions) and Note1309804(function and error messages).