SAP BusinessObjects Enterprise Repository Diagnostic Tool User's Guide
■ SAP BusinessObjects Enterprise XI 4.0
2011-01-12
Copyright
© 2011 SAP AG. All rights reserved.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP
Business ByDesign, and other SAP products and services mentioned herein as well as their respective
logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business
Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web
Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the
United States and in other countries. Business Objects is an SAP company.All other product and
service names mentioned are the trademarks of their respective companies. Data contained in this
document serves informational purposes only. National product specifications may vary.These materials
are subject to change without notice. These materials are provided by SAP AG and its affiliated
companies ("SAP Group") for informational purposes only, without representation or warranty of any
kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The
only warranties for SAP Group products and services are those that are set forth in the express
warranty statements accompanying such products and services, if any. Nothing herein should be
construed as constituting an additional warranty.
2011-01-12
Contents
Repository Diagnostic Tool.....................................................................................................5Chapter 1
Using the Repository Diagnostic Tool.....................................................................................7Chapter 2
2.1
2.2
Index 21
To use the Repository Diagnostic Tool.....................................................................................7
Repository Diagnostic Tool Parameters...................................................................................8
Inconsistencies between the CMS and the FRS...................................................................13Chapter 3
Inconsistences in the CMS metadata...................................................................................15Chapter 4
More Information...................................................................................................................19Appendix A
2011-01-123
Contents
2011-01-124
Repository Diagnostic Tool
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.
2011-01-125
Repository Diagnostic Tool
2011-01-126
Using the Repository Diagnostic Tool
Using 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 SAP BusinessObjects Enterprise services are down.
The RDT does not require the CMS service to be running. The RDT runs directly against the CMS
database.
2.1 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>\SAP BusinessObjects Enterprise XI 4.0\win64_x64\reposcan.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>/sap_bobj/enterprise_xi40/<platform>/boe_reposcan.sh <argu
ments> where <platform> is either “linux_x64”, “solaris_sparcv9”, “hpux_ia64”, or “aix_rs6000_64”,
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_Re
pair_yyyy_mm_dd_hh_mm_ss.xml.
2011-01-127
Using the Repository Diagnostic Tool
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 <INSTALLDIR>\SAP BusinessObjects Enterprise XI
4.0\reposcan on Windows, and ./sap_bobj/enterprise_xi40/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 <INSTALLDIR>\SAP BusinessObjects Enterprise XI 4.0\reposcan
on Windows, and ./sap_bobj/enterprisexi_40/reposcan on UNIX
For a list of the warning messages and recommended actions that the RDT takes when it finds
inconsistencies, see
.
Related Topics
• Inconsistences in the CMS metadata
• Inconsistencies between the CMS and the FRS
Inconsistences in CMS metadata
and
Inconsistencies between the CMS and FRS
2.2 Repository Diagnostic Tool Parameters
The RDT accepts the parameters in the following table:
Note:
Command-line arguments override any parameter file entries while executing.
Table 2-1: General Parameters
Parameter
Optional or
Mandatory
Mandatorydbdriver
Description
The type of driver used to connect to the CMS
database. Accepted values are:
• db2databasesubsystem
• maxdbdatabasesubsystem
• mysqldatabasesubsystem
• oracledatabasesubsystem
• sqlserverdatabasesubsystem
• sybasedatabasesubsystem
2011-01-128
Using the Repository Diagnostic Tool
Parameter
Optional or
Mandatory
Mandatoryconnect
Mandatoryinputfrsdir
Mandatoryoutputfrsdir
Description
The connection details that are used to connect to
the CMS database.
For example: -connect
"UID=root;PWD=<pass
word>;DSN=<dsn>;HOSTNAME=<host
name>;PORT=<portnumber>"
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.
The file path where the RDT writes the log files.
The default value is <INSTALLDIR>\SAP
Optionaloutputdir
BusinessObjects Enterprise XI
4.0\reposcan on Windows, and
./sap_bobj/enterprise_xi40/reposcan on
UNIX.
The number of approximate errors to scan. This
helps ensure optimum performance. The upper
Optionalcount
count is 2e31 - 1. A value of 0 is interpreted as the
entire repository.
The default value is 0.
Tells the RDT to repair all inconsistencies it may
find. The default behavior is to only report inconsis-
Optionalrepair
tencies but not to perform any repairs. If the -repair
paramater exists on the command line, the RDT
reports and repairs all inconsistencies.
2011-01-129
Using the Repository Diagnostic Tool
Parameter
Optional or
Mandatory
Optionalscanfrs
Optionalscancms
Optionalsubmitterid
Description
Specifies whether the RDT scans the CMS and FRS
for inconsistencies. Acceptable values are True and
False.
The default value is True.
Specifies whether the RDT scans the CMS for inconsistencies between InfoObjects. Acceptable values
are True and False.
The default value is True.
Specifies the User ID to replace missing or invalid
IDs for scheduled objects. If no value is provided,
the RDT does not replace the invalid IDs. If the
provided User ID doesn't exist in the CMS, the RDT
prompts for a valid ID.
This parameter is only used when the RDT operates
in repair mode.
Specifies the object in the CMS database to start
the scan for. For example, if you've already scanned
Optionalstartid
the first 500 objects in your repository, you can set
-startid=501 to start a new scan at the 501st object.
The default value is 1.
Specifies the file path to a parameter file. The parameter file is a text file that lists each commandline option and its values. The file should have one
parameter per line.
Optionaloptionsfile
Note:
With this option, you can set all parameters in a Text
file as described above. Use this option to point to
the parameter file without entering the parameters
on the command-line.
The following parameters are used if the Repository Diagnostic Tool is running on an active clustered
CMS.
2011-01-1210
Using the Repository Diagnostic Tool
Table 2-2: Using the RDT against a clustered CMS
Parameter
Optional or
Mandatory
Optionalrequestport
Optionalnumericip
Optionalipv6
Description
The port number that the RDT uses to communicate to the CMS. Accepts whole, positive
numbers. By default, the tool uses the value
from the operating system of the machine that
the RDT is running on.
Whether the RDT uses the numeric IP address
instead of the hostname for communication
between the CMS and the machine that the
RDT is running on. Acceptable values are True
and False.
The default value is False.
The ipv6 name of the machine that the RDT is
running on. Accepts a string.
The default value is the hostname of the machine that the RDT is running on.
The ipv4 name of the machine that the RDT is
running on. Accepts a string.
Optionalport
The default value is the hostname of the machine that the RDT is running on.
The number of threads to use. Accepts whole,
Optionalthreads
positive numbers.
The default value is 12.
The following parameters are used when the RDT uses SSL to communicate with the CMS database
that it scans.
2011-01-1211
Using the Repository Diagnostic Tool
Table 2-3: Using the RDT with SSL
Parameter
Optional or
Mandatory
Optionalprotocol
Optionalssl_certdir
Optionalssl_trustedcertificate
Optionalssl_mycertificate
Optionalssl_mykey
Optionalssl_mykey_passphrase
Description
Specifies whether the tool should run in SSL
mode.
The only accepted value is ssl.
The directory that contains the SSL certificates.
The file name of the certificate.
The file name of the signed certificate.
The file name of the file that contains the private SSL key.
The file name of the file that contains SSL
passphrase.
Example:
The following example scans the CMS and FRS for both kinds of inconsistencies, and repairs the
inconsistencies that it finds.
reposcan.exe
-dbdriver mysqldatabasesubsystem
-connect “UID=root;PWD=Password1;DSN=myDsn;HOSTNAME=myHostname;PORT=3306”
-repair
-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”
2011-01-1212
Inconsistencies between the CMS and the FRS
Inconsistencies between the CMS and the FRS
The following table describes the inconsistencies that may between a Central Management Server
(CMS) data base and the File Repository Servers (FRS) that are recognized by the Repository Diagnostic
Tool (RDT). The table has 4 columns:
• Warning Message
The warning message that is written to the scan and repair log files.
• Inconsistency
An explanation of the inconsistency that the RDT finds for the object.
• Recommendation
The recommended action that the RDT should take when it finds an inconsistency. This is found in
the scan log file.
• Action
The action that the RDT takes to repair an inconsistency. This is found in the repair log file.
2011-01-1213
Inconsistencies between the CMS and the FRS
ActionRecommendationInconsistencyWarning Message
<Object Name> object
<Object Type> (Object
ID: <ID>) is referencing
some files that do not exist
in the FRS (<File Name>)
<File Name> exists in the
Input or Output FRS, but
there is no corresponding
InfoObject in the repository.
<Object Type> Object
<Object Name> (Object
ID <ID>) has a file size
<Size>. The stored file size
is <Size> which does not
match the actual file size
<Size>.
<Folder Path> contains
no files.
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.
“Allow the application
to remove the missing
files from the object's
file list.”
“Please republish the
file. The application will
not publish this file for
you.”
“Allow the application
to update the object
with the correct file
size.”
“Allow the application
to remove the directory.”
The RDT removes
the object from the
CMS database.
When you republish
the file, an object is
created in the CMS
database.
The RDT updates
the file size in the
CMS database.
The RDT removes
the empty directory.
2011-01-1214
Inconsistences in the CMS metadata
Inconsistences in the CMS metadata
The following table describes the inconsistencies that can occur in the metadata of the objects that are
in a Central Management Server (CMS) system data base that are recognized by the Repository
Diagnostic Tool (RDT). The table has 4 columns:
• Warning Message
The warning message that is written to the scan and repair log files.
• Inconsistency
An explanation of the inconsistency that the RDT finds for the object.
• Recommendation
The recommended action that the RDT should take when it finds an inconsistency. This is found in
the scan log file.
• Action
The action that the RDT takes to repair an inconsistency. This is found in the repair log file.
2011-01-1215
Inconsistences in the CMS metadata
ActionRecommendationInconsistencyWarning Message
<Object Type> Object
<Object Name> (Object
ID: <Object
Name><ID>)'s parent ob-
ject is missing (Parent
Object ID = <ID>).
<Object Type> Object
<Object Name> (Object
ID: <ID>)'s owner object
is missing (Owner Object
ID = <ID>).
<Object Type> Object
<Object Name> (Object
ID: <ID>)'s submitter object is missing (Submitter
Object ID = <ID> ).
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.
“Allow RDT to move the
object to the BO Repair
folder. ”
“Allow the RDT to assign
the object to the Administrator. ”
The recommendation that
the RDT displays depends
on whether you've provided a value for the -submitterid parameter.
• If you provide this pa-
rameter, the recommendation is “Allow
the application to update the object with
the provided submitter
ID”.
• If you don't provide this
parameter, the recommendation is “
Reschedule the object
or submit a user ID to
use to replace the invalid submitter ID”.
The RDT moves the object and any child objects
to a repair folder. Only the
administrator has access
to this folder.
The RDT assigns the value of the Administrator's
ID to the objects Owner
ID.
If you provide a value from
the -submitterid parameter, the RDT applies the
value for the object's submitter ID.
If you don't provide a value for this parameter, the
RDT takes no action.
When you reschedule the
object, the CMS applies a
new ID.
<Object Type> Object
'<Object Name>' (Object
ID: <ID>)'s last successful instance property
refers to a missing object
(Object ID = <ID>).
The object's last
sucessful instance
is missing or invalid.
“Allow the application to
recalculate the property.”
When you reschedule the
object, the CMS automatically recalculates the ID.
2011-01-1216
Inconsistences in the CMS metadata
ActionRecommendationInconsistencyWarning Message
<Object Type> Object
'<Object Name>' (Object ID: <ID>)'s calendar
object is missing (Calendar ID = <ID>).
<Object Type> Object
'<Object Name>' (Object
ID: <ID>) 's required
scheduling server group
is missing (Server Group
Object ID = <ID>)..
<Object Type> Object
'<Object Name>' (Object
ID: <ID>)'s list of events
to wait for contains missing object(s) (Object ID(s)
= <ID>).
<Object Type> Object
'<Object Name>' (Object
ID: <ID>)'s list of events
to trigger contains missing
object(s) (Object ID(s) =
<ID>).
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.
“Reschedule the object
with an existing calendar.
No action can be taken by
this application.”
“ Reschedule the object
and choose an existing
server group. No action
can be taken by this application.”
“Allow the application to
remove the missing
events from the object's
list of events to wait for.”
“Allow the application to
remove the missing
events from the object's
list of events to trigger.”
When you reschedule the
object, the CMS applies a
calendar to the object.
When you reschedule the
object, the CMS applies a
server group to the object.
The RDT removes the
missing events.
The RDT removes the
missing events.
2011-01-1217
Inconsistences in the CMS metadata
ActionRecommendationInconsistencyWarning Message
<Object Type> Object
'<Object Name>' (Object
ID: <ID>) Access Control
List references a missing
principal (Object ID =
<ID>).
<Object Type> Object
'<Object Name>' (Object
ID: <ID>) has invalid
Server Group entries
<Server Group
Entries>.
<Object Type> Object
<Object Name> (Object
ID: <ID>) has multiple
Favorites folders.
Orphaned Access
Control entry.
The preferred server does not exist.
A specific user account has multiple
favorites folders.
“ Allow the application to
remove the missing principal(s) from the object's
Access Control List.”
“Allow the tool to remove
the object's invalid entries
from its Server Group list.”
“Allow the application to
consolidate multiple Favorites folders into a single Favorites folder.”
The RDT removes the
missing principal(s).
The RDT removes the objects missing entries from
the object's server group
list.
The RDT consolidates the
user's Favorites folders
into a single folder.
2011-01-1218
More Information
More Information
LocationInformation Resource
SAP BusinessObjects product information
SAP Help Portal
SAP Service Marketplace
http://www.sap.com
Navigate to http://help.sap.com/businessobjects and on the "SAP BusinessObjects Overview" side panel click All Products.
You can access the most up-to-date documentation covering all SAP
BusinessObjects products and their deployment at the SAP Help Portal.
You can download PDF versions or installable HTML libraries.
Certain guides are stored on the SAP Service Marketplace and are not
available from the SAP Help Portal. These guides are listed on the Help
Portal accompanied by a link to the SAP Service Marketplace. Customers
with a maintenance agreement have an authorized user ID to access
this site. To obtain an ID, contact your customer support representative.
http://service.sap.com/bosap-support > Documentation
• Installation guides: https://service.sap.com/bosap-instguides
• Release notes: http://service.sap.com/releasenotes
The SAP Service Marketplace stores certain installation guides, upgrade
and migration guides, deployment guides, release notes and Supported
Platforms documents. Customers with a maintenance agreement have
an authorized user ID to access this site. Contact your customer support
representative to obtain an ID. If you are redirected to the SAP Service
Marketplace from the SAP Help Portal, use the menu in the navigation
pane on the left to locate the category containing the documentation you
want to access.
Docupedia
Developer resources
https://cw.sdn.sap.com/cw/community/docupedia
Docupedia provides additional documentation resources, a collaborative
authoring environment, and an interactive feedback channel.
https://boc.sdn.sap.com/
https://www.sdn.sap.com/irj/sdn/businessobjects-sdklibrary
2011-01-1219
More Information
LocationInformation Resource
SAP BusinessObjects articles on
the SAP Community Network
Notes
Forums on the SAP Community
Network
Training
Online customer support
https://www.sdn.sap.com/irj/boc/businessobjects-articles
These articles were formerly known as technical papers.
https://service.sap.com/notes
These notes were formerly known as Knowledge Base articles.
https://www.sdn.sap.com/irj/scn/forums
http://www.sap.com/services/education
From traditional classroom learning to targeted e-learning seminars, we
can offer a training package to suit your learning needs and preferred
learning style.
http://service.sap.com/bosap-support
The SAP Support Portal contains information about Customer Support
programs and services. It also has links to a wide range of technical information and downloads. Customers with a maintenance agreement
have an authorized user ID to access this site. To obtain an ID, contact
your customer support representative.
Consulting
http://www.sap.com/services/bysubject/businessobjectsconsulting
Consultants can accompany you from the initial analysis stage to the
delivery of your deployment project. Expertise is available in topics such
as relational and multidimensional databases, connectivity, database
design tools, and customized embedding technology.
2011-01-1220
Index
R
repository diagnostic tool
inconsistencies
diagnose and repair 5
object to file 5
repository diagnostic tool
inconsistencies
scenarios 5
overview 5
parameters 7
(continued)
(continued)
repository diagnostic tool
table of inconsistencies
recommendations 13, 15
using
Windows and Unix 7
(continued)
2011-01-1221
Index
2011-01-1222
Loading...