Repository Diagnostic Tool (RDT) is going to be the topic of discussion today. It is always possible in every business objects deployment to have inconsistencies between CMS database and File Repository Servers. This may occur during events such as Backup restoration, disaster recovery or network outage. CMS system database may be interrupted during these events and causes inconsistencies with objects in the CMS database.
Repository Diagnostic Tool (RDT) comes into picture here. It scans the CMS system database and identifies inconsistencies in infoobjects, diagnoses and repairs them. Types of inconsistencies are
- Object to file inconsistencies
Inconsistency between info objects in CMS database and the corresponding file in FRS
- Infoobjects metadata inconsistencies
Inconsistency in metadata of an infoobjects in CMS database.
Running RDT Tool
You can find the RDT tool here:
The executable is “reposcan.exe” and is available in
“<INSTALLDIR>\BusinessObjects Enterprise 12.0\win32_x86\”
The Shell script is “boe_reposcan.sh” and is in “<INSTALLDIR>/bobje/”
Sample RDT Usage Pattern (Windows):
We need to execute the below in Command prompt from the reposcan.exe’s installation directory. The below sample is for CMS database in SQL SERVER.
-connect “UID=XXX;PWD= XXX;DSN=XXX”
-inputfrsdir “E:\Program Files (x86)\Business Objects\BusinessObjects Enterprise 12.0\FileStore\Input”
-outputfrsdir “E:\Program Files (x86)\Business Objects\BusinessObjects Enterprise 12.0\FileStore\Output”
-outputdir “E:\Program Files (x86)\Business Objects\BusinessObjects Enterprise 12.0\reposcan”
XXX has to be replaced with your DSN credentials.
Viewing Repository Diagnostic Tool’s result set
The output files would be generated at the below directory by default: <BOE install>\BusinessObjects Enterprise 12.0\reposcan. You can change the default location with a different directory using -outputdir option in reposcan execution usage pattern.
The output files generated would be
- The name format of scan output file is Repo_Scan_YYYY_MM_DD_HH_MM_SS.xml
- The name format of repair output file is Repo_Repair_YYYY_MM_DD_HH_MM_SS.xml
Scan Summary report
Based on the reports we can proceed further with remedial action.
Hope this blog is interesting.
Thanks for reading.