BusinessObjects-Repository Scan and Repair

A clean system is the best starting point for your company. BusinessObjects has a repair tool for your environment. With reposcan you can check the inconsistency between your CMS database and your file system.

For example "An error occurred while searching: The property with ID SI_CUID does not exist in the object" error on search can occur due to file system and repository inconsistency.

You can find the reposcan.exe file under "<INSTALLDIR>\SAP BusinessObjects Enterprise XI 4.0\win64_x64\". Reposcan has a lot of parameters therefore i prefer to create a batch file with the parameters i needed.

Here is the repo_repair.bat file code:

reposcan.exe -dbdriver sqlserverdatabasesubsystem -connect "UID=XXX1;PWD=XXX2;DSN=XXX3;HOSTNAME=XXX4;PORT=XXX5" -dbkey XXX6 -inputfrsdir "C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\FileStore\Input" -outputfrsdir "C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\FileStore\Output"

For this example CMS repository database is SQL Server.

XXX1= Your SQL username for logging CMS repository database.
XXX2= Your password of the SQL user.
XXX3= ODBC DSN name of the CMS repository database.
XXX4= SQL Server hostname
XXX5= SQL Server portname
XXX6= Cluster key of your CMS

To find your cluster key open CCM. Right click on SIA and choose properties.

Now go to the configuration tab. At the bottom you will see your CMS Cluster Key.

With this information your command should look like this;

reposcan.exe -dbdriver sqlserverdatabasesubsystem -connect "UID=sqluser;PWD=sqlpass;DSN=bo_cms;HOSTNAME=server_name\instance_name;PORT=1433" -dbkey [[XX1g0FVBi9VFBiCIAnAQ]]  -inputfrsdir "C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\FileStore\Input" -outputfrsdir "C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\FileStore\Output"

After you run your batch file it creates a log file under "<INSTALLDIR>\SAP BusinessObjects Enterprise XI 4.0\reposcan". Open the xml files with your browser and you fill see the results.

List of inconsistency, by type, which can be found by RDT.

Inconsistencies between the CMS and the FRS:

• The object exists in the CMS database, but there is no corresponding file in the FRS.
• The file exists in the FRS, but there is no corresponding file in the CMS database.
• The size of the file does not match the InfoObject file size.
• The FRS folder is empty.

Inconsistencies in the CMS metadata:

• The object has a missing or invalid Parent Object ID.
• The object has a missing or invalid Owner Object ID.
• The object has a missing or invalid Submitter Object ID.
• The object's last successful instance is missing or invalid.
• The object references a calendar that doesn't exist.
• The preferred server does not exist.
• The event or events that this object is waiting on does not exist.
• This object triggers an event that does not exist.
• Orphaned Access Control entry.
• The preferred server does not exist.
• A specific user account has multiple favorites folders.

More information : http://wiki.sdn.sap.com/wiki/display/BOBJ/How+to+use+Repository+Diagnostic+Tool

For other databases and reposcan parameters refer to xi4_bip_repository_diagnostic_tool_en.pdf on SAP market.

Tweet