Академический Документы
Профессиональный Документы
Культура Документы
0
Repository Diagnostic Tool User's
Guide
Third-party Business Objects products in this release may contain redistributions of software
Contributors 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-02-29
Contents
Chapter 1 Working with the Repository Diagnostic Tool 5
Repository Diagnostic Tool..........................................................................6
Repository Diagnostic Tool - table of inconsistencies..................................7
Using the Repository Diagnostic Tool..........................................................8
Index 17
1
1 Working with the Repository Diagnostic Tool
Repository Diagnostic Tool
The RDT scans the CMS system database and identifies inconsistencies. It
also repairs any logged inconsistencies, and reports the repair status and
completed actions. To determine synchronization between the file system
and database, use RDT after you first complete a hot back-up. Or use the
RDT after a restoration and prior to the starting BusinessObjects Enterprise
services. You may limit of the number of errors the RDT will find and/or repair
before stopping.
Note: Use the RDT as an aid only. While this tool can identify the majority
of inconsistencies between the CMS and FRS, it may not detect all types of
discrepancies.
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 in
an inconsistent state; while executing a database write, insert or update.
This can cause inconsistencies with objects in the CMS system database.
File exists, but FileName exists in the “In- Please republish the file. The
no object put” or “Output” FRS, but RDT will not republish this for
there is no corresponding you.
object in the repository.
The Repository Diagnostic Tool creates XML files of both the scan results
and the repair results. The location of these XML files is configurable.
• The scan file contains the inconsistencies found in the scan. The file name
is in the format:
Repo_Scan_yyyy_mm_dd_hh_mm.xml
• The repair file contains the repair actions and results. The file name is in
the format:
Repo_Repair_yyyy_mm_dd_hh_mm.xml
For Unix users, scan with the Repository Diagnostic Tool from within a
/usr/bin/sh compatible shell:
Note: The application also provides a default XSL file that can be used with
XML file to produce an HTML page. The XSL will be stored in the following
directory paths: <Install Directory>\BusinessObjects Enterprise
12.0\reposcan and ./bobje/enterprise120/reposcan
The command line tool is installed with the Central Configuration Manager
(CCM). The Repository Diagnostic Tool will accept the following parameters:
-connect UID=root;PWD=bobobo;DSN=BOE120
-repair
-count 1000
-inputfrsdir<Install Directory>\BusinessOb-
jects Enterprise 12.0\FileStore\Input
Note: With this option, you can set all you parameters
in a .txt file as described above. And use this option
to point to the parameter file without entering the pa-
rameters on the command line.
-inputfrsdir Mandatory The file path of the Input File Repository Server.
Note: The user account you are logged on with is
used to execute the command line tool. It must have
full control to the file location.
-ouptutfrs- Mandatory The file path of the Output File Repository Server.
dir
Note: The user account you are logged on with is
used to execute the command line tool. It must have
full control to the file location.
-outputdir Optional The file path where you would like the log files to be
placed. The default value for this is the current direc-
tory.
-count Optional The number of approximate errors to stop scanning.
This is used to help ensure performance. Upper count
is 2e31 - 1. A value of 0 is interpreted as the entire
repository. The default value of this is 1,000.
-repair Optional Tells the Repository Diagnostic Tool to repair the in-
consistencies it finds. The default behavior is to only
report inconsistencies but do not perform any repairs.
Acceptable values are “False” and “True”. True forces
the tool to make repairs. “False” forces the tool to leave
the inconsistencies as is. The default value is “False”.
A
A Get More Help
http://support.businessobjects.com/documentation/product_guides/
http://www.businessobjects.com/support/
For more information, contact your local sales office, or contact us at:
http://www.businessobjects.com/services/consulting/
http://www.businessobjects.com/services/training
mailto:documentation@businessobjects.com
Note: If your issue concerns a Business Objects product and not the
documentation, please contact our Customer Support experts. For information
about Customer Support visit: http://www.businessobjects.com/support/.