SAP Business objects Enterprise XI 3.1 Repository Diagnostic Tool User's Guide

BusinessObjects Enterprise Repository Diagnostic Tool User's Guide

BusinessObjects Enterprise XI 3.1

© 2008 Business Objects, an SAP company. All rights reserved. Business Objects owns the following U.S. patents, which may cover products that are offered and licensed by Business Objects: 5,295,243; 5,339,390; 5,555,403; 5,590,250; 5,619,632; 5,632,009; 5,857,205; 5,880,742; 5,883,635; 6,085,202; 6,108,698; 6,247,008; 6,289,352; 6,300,957; 6,377,259; 6,490,593; 6,578,027; 6,581,068; 6,628,312; 6,654,761; 6,768,986; 6,772,409; 6,831,668; 6,882,998; 6,892,189; 6,901,555; 7,089,238; 7,107,266; 7,139,766; 7,178,099; 7,181,435; 7,181,440; 7,194,465; 7,222,130; 7,299,419; 7,320,122 and 7,356,779. Business Objects and its logos, BusinessObjects, Business Objects Crystal Vision, Business Process On Demand, BusinessQuery, Cartesis, Crystal Analysis, Crystal Applications, Crystal Decisions, Crystal Enterprise, Crystal Insider, Crystal Reports, Crystal Vision, Desktop Intelligence, Inxight and its logos , LinguistX, Star Tree, Table Lens, ThingFinder, Timewall, Let There Be Light, Metify, NSite, Rapid Marts, RapidMarts, the Spectrum Design, Web Intelligence, Workmail and Xcelsius are trademarks or registered trademarks in the United States and/or other countries of Business Objects and/or affiliated companies. SAP is the trademark or registered trademark of SAP AG in Germany and in several other countries. All other names mentioned herein may be trademarks of their respective owners.

Third-party Contributors

Business Objects products in this release may contain redistributions of software licensed from third-party contributors. Some of these individual components may also be available under alternative licenses. A partial listing of third-party contributors that have requested or permitted acknowledgments, as well as required notices, can be found at: http://www.businessobjects.com/thirdparty

2008-09-03

Repository Diagnostic Tool 5Chapter 1

Using the Repository Diagnostic Tool 9Chapter 2

To use the Repository Diagnostic Tool......................................................10

Repository Diagnostic Tool Parameters....................................................11

Inconsistencies between the CMS and the FRS 19Chapter 3

Inconsistences in the CMS metadata 23Chapter 4

Get More Help 29Appendix A

Index 33

BusinessObjects Enterprise Repository Diagnostic Tool User's Guide 3

Contents

4 BusinessObjects Enterprise Repository Diagnostic Tool User's Guide

Repository Diagnostic Tool

The Repository Diagnostic Tool (RDT) is a command-line tool that scans, diagnoses, and repairs inconsistencies that may occur between your Central Management Server (CMS) system database and the File Repository Servers (FRS) filestore, or inconsistencies that can occur in the metadata of InfoObjects stored in the CMS database.

During normal operations, it is unusual for the CMS system database to have inconsistencies. However, inconsistencies may occur during unexpected events such as disaster recovery, back-up restoration, or network outages. During these events, the CMS system database may be interrupted while performing a task. This can cause inconsistencies with objects in the CMS system database.

The RDT scans the CMS system database and identifies inconsistencies in such objects as reports, users, user groups, folders, servers, universes, universe connections, and other objects.

The RDT scans for two types of inconsistencies.

• Object to file inconsistencies.

These are inconsistencies that can occur between InfoObjects in the CMS database and the corresponding files in the File Repositories. For example, a file that is stored in the FRS may be missing a corresponding object in the CMS system database.

• InfoObject metadata inconsistencies.

These are inconsistencies that may exist in an InfoObject's object definition (metadata) in the CMS database. For example, an InfoObject may reference another InfoObject that does not exist in the CMS database.

The RDT peforms two functions, depending on the parameters that you provide when you run the tool:

• It scans the CMS system database and FRS filestore, reports

inconsistencies, and outputs a log file in XML format with suggested actions to repair the inconsistencies.

• It scans and repairs the inconsistencies identified in the CMS system

database and FRS, and outputs the actions taken to a log file in XML format.

6 BusinessObjects Enterprise Repository Diagnostic Tool User's Guide

Repository Diagnostic Tool

Note:

Use the RDT as an aid only. While this tool can identify the majority of inconsistencies in your deployment, it may not detect all types of discrepancies.

BusinessObjects Enterprise Repository Diagnostic Tool User's Guide 7

Repository Diagnostic Tool

8 BusinessObjects Enterprise Repository Diagnostic Tool User's Guide

Using the Repository Diagnostic Tool

To use the Repository Diagnostic Tool

The Repository Diagnostic Tool (RDT) is available on any machine with a Central Configuration Manager (CCM) installed on it. This command-line tool scans, diagnoses, and repairs inconsistencies that may occur between the Central Management Server (CMS) system database and the File Repository Servers (FRS) filestore, or inconsistencies that may occur in an InfoObject's metadata.

Do not run the RDT against a live CMS database and FRS. Changes that your users make to the CMS or FRS while the RDT is running can create new inconsistencies in your deployment. Repair actions that the RDT takes while users are accessing your deployment can create further inconsistencies.

Instead, it is recommended that you back up your CMS database and FRS filestore, and run the RDT against the backed-up version while your BusinessObjects Enterprise services are down.

The RDT does not require the CMS service to be running. The RDT runs directly against the CMS database.

To use the Repository Diagnostic Tool

1. If you are running the tool on a Windows computer, open a command

window and run the following command.

<INSTALLDIR>\BusinessObjects Enterprise 12.0\win32_x86\re poscan.exe<arguments>, where <arguments> is the list of parameters

that you want to specify.

2. If you are running the tool on a UNIX computer, open a /usr/bin/sh

compatible shell, and run the following command.

.<INSTALLDIR>/<platform>/boe_reposcan<arguments> where

<platform> is either “linux_x86”, “solaris_sparc”, “hpux_pa-risc”, or

“aix_rs6000”, and <arguments> is the list of parameters that you want to specify.

The Repository Diagnostic Tool scans your repository for inconsistencies. Depending on the parameters that you specify, it either diagnoses and logs inconsistencies, or it repairs inconsistences and logs the action that it takes.

Repo_Scan_yyyy_mm_dd_hh_mm_ss.xml lists the inconsistencies that the

tool finds. If you had the tool repair the discrepancies that it finds, it also creates the file Repo_Repair_yyyy_mm_dd_hh_mm_ss.xml.

10 BusinessObjects Enterprise Repository Diagnostic Tool User's Guide

Using the Repository Diagnostic Tool

Repository Diagnostic Tool Parameters

The path to the log files can be specified by the outputdir parameter. If this parameter is not specified, the default directory for the log files is <IN

STALLDIR>\BusinessObjects Enterprise 12.0\reposcan on Windows,

and ./bobje/enterprise120/reposcan on UNIX.

Note:

The application also provides a default XSL file that is used with the XML file to produce an HTML page. The XSL file is stored in <IN

STALLDIR>\BusinessObjects Enterprise 12.0\reposcan on Windows,

and ./bobje/enterprise120/reposcan on UNIX

For a list of the warning messages and recommended actions that the RDT takes when it finds inconsistencies, see Inconsistences in CMS metadata and Inconsistencies between the CMS and FRS .