Implementing the Repository Diagnostic Tool (RDT)

Repository Diagnostic Tool (RDT) is a command line tool provided on SAP BusinessObjects BI Platform 2025. This tool has to be executed on the application server host only to scan and repair inconsistencies between the CMS system database and the FRS file store directory.

Definition:

Administrators use Repository Diagnostic Tool (RDT) to aid in the identification and resolution of potential problems within the BI repository.

• Repository Diagnostic Tool (RDT) can scan and diagnose inconsistencies between the CMS system database and Input and Output FRS.
• Repository Diagnostic Tool (RDT) can also repair scanned inconsistencies.
  Note

  We strongly recommend to backup the CMS system database and the File Story Directory content before running RDT in repair mode. There is no turning back possible in repair mode with RDT.

Inconsistencies:

Incorrect backup restoration (for instance, due to non-synchronized CMS system database and File Story Directory backups) can corrupt or cause inconsistencies with object references in the CMS system database.

The RDT is a command line diagnostic tool. It compares each CMS database objects with the corresponding object in the Input and Output FRS. It also compares each object in the Input and Output FRS with the corresponding object in the CMS system database.

• The RDT scans for two types of inconsistencies:
  1. Object inconsistency:

     These inconsistencies can happen when an InfoObject in the CMS system database doesn't have the corresponding file in the file store repository.

  2. File Inconsistency:

     These inconsistencies can happen when a file that is located in the file store directory doesn't have the corresponding InfoObject in the CMS system database.

• A report is generated in a XML format that can be viewed in a web browser (Internet Explorer only supported at this moment):
  • In scan mode: Only the XML report is generated with suggested actions to repair the inconsistencies.
  • In repair mode: After inconsistencies are identified, the RDT will repair what it can and an XML report is generated with suggested actions and what items it repaired.

Note

The RDT doesn't need the CMS service to be running. The RDT runs directly against the CMS database.

Follow the link to know how use the Repository Diagnostic Tool: (To use the Repository Diagnostic Tool).

Follow the link to know all the Repository Diagnostic Tool parameters: (Repository Diagnostic Tool Parameters).

Repository Diagnostic Tool (RDT) scans and repairs inconsistencies between the CMS system database and the FRS file store directory.

Definition:

Inconsistencies can be found between a CMS database and FRS using the the RDT in scan mode or in repair mode.

Note

The following links show you what inconsistencies can be found between a CMS database and FRS using the RDT:

Inconsistencies between the CMS and the FRS

Repository Diagnostic Tool (RDT) scans and repairs inconsistencies between the CMS system database and the FRS file store directory.

Definition:

Inconsistencies can be found between a CMS database and FRS using the the RDT in scan mode or in repair mode.

Note

The following link shows you the inconsistencies that can happen in the metadata of CMS objects found by the RDT:

Inconsistencies in the CMS Metadata