BusinessObjects Enterprise XI 3.0
Repository Diagnostic Tool User's
Guide
BusinessObjects Enterprise XI 3.0
Copyright
© 2008 Business Objects. All rights reserved. Business Objects owns the following
U.S. patents, which may cover products that are offered and licensed by Business
Objects: 5,555,403; 5,857,205; 6,289,352; 6,247,008; 6,490,593; 6,578,027;
6,831,668; 6,768,986; 6,772,409; 6,882,998; 7,139,766; 7,299,419; 7,194,465;
7,222,130; 7,181,440 and 7,181,435. Business Objects and the Business Objects
logo, BusinessObjects, Business Objects Crystal Vision, Business Process On
Demand, BusinessQuery, Crystal Analysis, Crystal Applications, Crystal Decisions,
Crystal Enterprise, Crystal Insider, Crystal Reports, Desktop Intelligence, Inxight,
the Inxight Logo, 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. 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-02-29
Contents
Working with the Repository Diagnostic Tool 5Chapter 1
Repository Diagnostic Tool..........................................................................6
Repository Diagnostic Tool - table of inconsistencies..................................7
Using the Repository Diagnostic Tool..........................................................8
Get More Help 13Appendix A
Index 17
BusinessObjects Enterprise XI 3.0 Repository Diagnostic Tool User's Guide 3
Contents
4 BusinessObjects Enterprise XI 3.0 Repository Diagnostic Tool User's Guide
Working with the Repository Diagnostic Tool
1
Working with the Repository Diagnostic Tool
1
Repository Diagnostic Tool
Repository Diagnostic Tool
The Repository Diagnostic Tool (RDT) is new for BusinessObjects Enterprise
XI 3.0. 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.
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.
Objects are elements of the BusinessObjects Enterprise system, including:
reports, users, folders, groups, servers, connections, universes, etc.
The inconsistencies that the RDT will scan for are:
• Object to file inconsistencies. For example, a file stored in the FRS may
not have a corresponding object within the CMS system database.
The RDT performs two functions; diagnosis and repair:
1. It scans the CMS system database, reports inconsistencies, and outputs
a log file in XML format with suggested actions to repair the
inconsistencies.
2. It scans and repairs the inconsistencies identified in the CMS system
database and reports all actions taken and changes made in XML format.
Here are two scenarios in you may experience with the RDT:
6 BusinessObjects Enterprise XI 3.0 Repository Diagnostic Tool User's Guide
Working with the Repository Diagnostic Tool
Repository Diagnostic Tool - table of inconsistencies
Scenario 1: The system is undergoing a restore process and all services
including the CMS are stopped. Len (the administrator) wants to check the
CMS system database (repository) consistency.
1. Len has backed up the CMS system database using a database vendor
hot back-up tool.
2. Len has backed up the FRS file system using a third-party tool like Backup
Exec.
3. A disaster occurs that compromises the CMS system database and FRS
file system. Len restores the CMS database and FRS file system with the
backup versions.
4. To ensure consistency of the restored FRS and CMS database prior to
restarting services, Len runs the RDT to identify and fix any
inconsistencies.
Scenario 2: System is in production mode and the CMS and both input FRS
and output FRS are running.
1. Len wants to validate the system and find out if any inconsistencies are
detected.
2. Len runs the RDT to identify and fix any inconsistencies.
Note: The XSL will be stored in the following directory path:
1
• For Windows: <Install Directory>\Business
Objects\BusinessObjects Enterprise 12.0\reposcan
• For Unix: ./bobje/enterprise120/reposcan
Repository Diagnostic Tool - table of
inconsistencies
The following table describes the two types of inconsistencies that may occur
in a Central Management Server (CMS) system database that is recognized
by the Repository Diagnostic Tool (RDT). The warning message is displayed
after the scan. RDT recommends an action it will apply to the object when
you choose “Repair”. See the following table for FRS filestore inconsistencies.
BusinessObjects Enterprise XI 3.0 Repository Diagnostic Tool User's Guide 7
Working with the Repository Diagnostic Tool
1
Using the Repository Diagnostic Tool
cy
RecommendationsWarningInconsisten-
Object exists,
no file though
File exists, but
no object
<Object Name> object
<Object Type> (Object ID:
<ID>) is referencing some
files that do not exist in the
FRS (<File Name>)
FileName exists in the “In-
put” or “Output” FRS, but
there is no corresponding
object in the repository.
Allow the tool to delete this object
and any objects left in an inconsistent state due to its removal.
Note: If the object links to multi-
ple files, and only some are
missing, then references to the
missing files are removed and the
object remains.
Please republish the file. The
RDT will not republish this for
you.
Using the Repository Diagnostic Tool
The Repository Diagnostic Tool (RDT) is available on any machine where
the Central Configuration Manager (CCM) is installed. This command line
tool can scan, diagnose, and repair inconsistencies that may occur between
the Central Management Server (CMS) system database and the File
Repository Servers (FRS) filestore.
Output:
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:
8 BusinessObjects Enterprise XI 3.0 Repository Diagnostic Tool User's Guide
Working with the Repository Diagnostic Tool
Using the Repository Diagnostic Tool
• ..<Install Directory>/<platform>/boe_reposcan<arguments>,
where <platform> is either 'linux_x86', 'solaris_sparc', 'hpux_pa-risc', or
'aix_rs6000'.
For Windows users, scan with the Repository Diagnostic Tool from:
<Install Directory>\BusinessObjects Enterprise
12.0\win32_x86\reposcan.exe<arguments>
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:
1
Parameter
file
or Mandatory
Optional-options-
DescriptionOptional
This is the file path to a parameter file. The parameter
file is a text file that lists each of the command line
options and their values; one argument per line. For
example:
-dbdriver mysqldatabasesubsystem
-connect UID=root;PWD=bobobo;DSN=BOE120
-repair
-count 1000
-inputfrsdir<Install Directory>\BusinessOb-
jects Enterprise 12.0\FileStore\Input
-outputfrsdir <Install Directory>BusinessOb-
jects Enterprise 12.0\FileStore\Output
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 parameters on the command line.
BusinessObjects Enterprise XI 3.0 Repository Diagnostic Tool User's Guide 9
Working with the Repository Diagnostic Tool
1
Using the Repository Diagnostic Tool
Parameter
dir
or Mandatory
Mandatory-dbdriver
Mandatory-connect
Mandatory-inputfrsdir
Mandatory-ouptutfrs-
DescriptionOptional
The driver type used to connect to the CMS database.
Accepted values are:
•
sqlserverdatabasesubsystem
•
oracledatabasesubsystem
•
db2databasesubsystem
•
mysqldatabasesubsystem
The connection used to connect to the CMS database.
Ex. -dbdriver mysqldatabasesubsystem -connect
UID=root;PWD=bobobo;DSN=BOE120
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.
The file path of the Output 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.
Optional-outputdir
Optional-count
Optional-repair
10 BusinessObjects Enterprise XI 3.0 Repository Diagnostic Tool User's Guide
The file path where you would like the log files to be
placed. The default value for this is the current directory.
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.
Tells the Repository Diagnostic Tool to repair the inconsistencies 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”.
Working with the Repository Diagnostic Tool
Using the Repository Diagnostic Tool
Note: Command line arguments override any parameter file entries while
executing.
1
BusinessObjects Enterprise XI 3.0 Repository Diagnostic Tool User's Guide 11
Working with the Repository Diagnostic Tool
Using the Repository Diagnostic Tool
1
12 BusinessObjects Enterprise XI 3.0 Repository Diagnostic Tool User's Guide
Get More Help
A
A
Get More Help
Online documentation library
Business Objects offers a full documentation set covering all products and
their deployment. The online documentation library has the most up-to-date
version of the Business Objects product documentation. You can browse
the library contents, do full-text searches, read guides on line, and download
PDF versions. The library is updated regularly with new content as it becomes
available.
http://support.businessobjects.com/documentation/product_guides/
Additional developer resources
http://devlibrary.businessobjects.com
Online customer support
The Business Objects Customer Support web site contains information about
Customer Support programs and services. It also has links to a wide range
of technical information including knowledgebase articles, downloads, and
support forums.
http://www.businessobjects.com/support/
Looking for the best deployment solution for your company?
Business Objects consultants can accompany you from the initial analysis
stage to the delivery of your deployment project. Expertise is available in
relational and multidimensional databases, in connectivities, database design
tools, customized embedding technology, and more.
For more information, contact your local sales office, or contact us at:
http://www.businessobjects.com/services/consulting/
Looking for training options?
From traditional classroom learning to targeted e-learning seminars, we can
offer a training package to suit your learning needs and preferred learning
style. Find more information on the Business Objects Education web site:
http://www.businessobjects.com/services/training
14 BusinessObjects Enterprise XI 3.0 Repository Diagnostic Tool User's Guide
Get More Help
Send us your feedback
Do you have a suggestion on how we can improve our documentation? Is
there something you particularly like or have found useful? Drop us a line,
and we will do our best to ensure that your suggestion is included in the next
release of our documentation:
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/.
Business Objects product information
For information about the full range of Business Objects products, visit:
http://www.businessobjects.com.
A
BusinessObjects Enterprise XI 3.0 Repository Diagnostic Tool User's Guide 15
A
Get More Help
16 BusinessObjects Enterprise XI 3.0 Repository Diagnostic Tool User's Guide
Index
R
Repository Diagnostic Tool 6, 7, 8
T
table of inconsistencies 7
U
using 8
BusinessObjects Enterprise XI 3.0 Repository Diagnostic Tool User's Guide 17
Index
18 BusinessObjects Enterprise XI 3.0 Repository Diagnostic Tool User's Guide
Loading...