1. technology and computing
2. software
3. databases

SAP BusinessObjects Business Intelligence Platform
Document Version: 4.0 Support Package 11 – 2015-02-19
Business Intelligence Platform
Repository Diagnostic Tool User Guide
Content
1
Document History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2
Overview of the Repository Diagnostic Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3
Using the Repository Diagnostic Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1
To use the Repository Diagnostic Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2
Repository Diagnostic Tool Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
4
Inconsistencies between the CMS and the FRS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5
Inconsistencies in the CMS metadata. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Business Intelligence Platform Repository Diagnostic Tool User Guide
Content
1
Document History
The following table provides an overview of the most important document changes.
Table 1:
Version
Date
SAP BusinessObjects Business Intelli­
gence platform 4.0 Support Package 11
Feb 2015
Business Intelligence Platform Repository Diagnostic Tool User Guide
Document History
Description
●
Updated the "Repository Diagnostic
Tool Parameters" section with the trace command-line parameter.
●
Removed description related to the
boolean argument for scanfrs and
scancms parameters in the "Repo­
sitory Diagnostic Tool Parameters"
section as the boolean argument is
no longer supported.
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
3
2
Overview of the 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 Server
(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 performs 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.
4
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Business Intelligence Platform Repository Diagnostic Tool User Guide
Overview of the Repository Diagnostic Tool
3
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 Server (FRS) filestore, or
inconsistencies that may occur in an InfoObject's metadata.
It is recommended that you back up your CMS database and FRS filestore, and run the RDT against the backedup version while your SAP BusinessObjects Business Intelligence platform services are down. If this is not
possible, the RDT can be run on an active database.
If you want to run the RDT on an active database please keep the following considerations in mind:
● The RDT will use one database connection while it runs.
● The RDT will only check the consistency of the database to the point in time where it started running. Any
inconsistencies that occur while the RDT is running will not be logged or fixed.
● It is recommended that the host machine running the RDT have memory above the normal system
recommendations available for processing RDT transactions:
○ A database of 50,000 InfoObjects or fewer should have an additional 350 MB available for processing
○ A database of 50,000 to 400,000 InfoObjects should have an additional 1.7 GB available for processing
○ A database of 400,000 to 1,000,000 InfoObjects should have an additional 4 GB available for processing
● The RDT does not have to be run from your CMS server. Running it on a separate machine can help reduce
any impact on system performance.
● The tool may have a moderate impact on database performance while being run.
The RDT does not require the CMS service to be running; the RDT runs directly against the CMS database.
3.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 <arguments> 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.
Note
When entering Unix command-line parameters, you may need to escape or multiply escape special shell
characters. For example, if the exclamation mark “!” is used in a password, you may need to escape the
exclamation mark, like this: ./ccm.sh -display -username Administrator -password Abc\!
defgh123 -cms cmsname.
Business Intelligence Platform Repository Diagnostic Tool User Guide
Using the Repository Diagnostic Tool
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
5
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 inconsistencies 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. This file
details which objects are repaired and any orphaned files that were deleted. If there are inconsistencies that could
not be repaired these will also be listed.
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 Inconsistencies in CMS metadata and Inconsistencies between the CMS and FRS .
Related Information
Inconsistencies in CMS metadata [page 14]
Inconsistencies between the CMS and FRS [page 13]
3.2
Repository Diagnostic Tool Parameters
Syntax
The RDT accepts the parameters in the following table:
Note
Command-line arguments override any parameter file entries while executing.
6
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Business Intelligence Platform Repository Diagnostic Tool User Guide
Using the Repository Diagnostic Tool
Table 2: General Parameters
Parameter
Optional or Manda­ Description
tory
dbdriver
Mandatory
The type of driver used to connect to the CMS database. Ac­
cepted values are:
connect
Mandatory
●
db2databasesubsystem
●
maxdbdatabasesubsystem
●
mysqldatabasesubsystem
●
oracledatabasesubsystem
●
sqlserverdatabasesubsystem
●
sybasedatabasesubsystem
●
sqlanywheredatabasesubsystem
The connection details that are used to connect to the CMS data­
base.
For example: -connect
"UID=root;PWD=<password>;DSN=<dsn>;HOSTNAME
=<hostname>;PORT=<portnumber>"
Business Intelligence Platform Repository Diagnostic Tool User Guide
Using the Repository Diagnostic Tool
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
7
Parameter
Optional or Manda­ Description
tory
dbkey
Mandatory
Enter the cluster key for your BI platform deployment.
If you do not know the cluster key, reset the cluster key by fol­
lowing these steps:
Note
If the machine is in a cluster, these steps will have to be done
for all cluster members. Back up the CMS database and file­
store before proceeding.
1.
Launch the Central Configuration Manager (CCM).
2. In the CCM, right-click the Server Intelligence Agent (SIA)
and choose Stop. Do not proceed to Step 3 until the SIA sta­
tus is “Stopped”.
3. Right-click the SIA and choose Properties.
4. On the Configuration tab, click Change next to CMS Cluster
Key Configuration.
5. A warning message is displayed. Click Yes to continue.
6. In the Change Cluster Key dialog box, enter the same eightcharacter key in both the New Cluster Key and Confirm New
Cluster Key fields.
Note
The RDT will not run if the dbkey parameter is omitted, or if
the cluster key is incorrect.
Note
The cluster key displayed in the CCM is encrypted, and can­
not be used in the dbkey parameter.
For more information on cluster keys see “Securing BI Platform”
in the SAP BusinessObjects Business Intelligence Platform Ad­
ministrator Guide.
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 lo­
cation.
8
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Business Intelligence Platform Repository Diagnostic Tool User Guide
Using the Repository Diagnostic Tool
Parameter
Optional or Manda­ Description
tory
outputfrsdir
Mandatory
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 lo­
cation.
outputdir
Optional
The file path where the RDT writes the log files.
The default value is <INSTALLDIR>\SAP
BusinessObjects Enterprise XI 4.0\reposcan
on Windows, and ./sap_bobj/enterprise_xi40/
reposcan on Unix.
count
Optional
The number of approximate errors to scan. This helps ensure op­
timum performance. The upper count is 2e31 - 1. A value of 0 is
interpreted as the entire repository.
The default value is 0.
repair
Optional
Tells the RDT to repair all inconsistencies it may find. The default
behavior is to only report inconsistencies but not to perform any
repairs. If the -repair parameter exists on the command line, the
RDT reports and repairs all inconsistencies.
Caution
This process will delete any orphaned objects or files in the re­
pository database.
scanfrs
Optional
Specifies whether the RDT scans the CMS and FRS for inconsis­
tencies.
scancms
Optional
Specifies whether the RDT scans the CMS for inconsistencies
between InfoObjects.
submitterid
Optional
Specifies the User ID to replace missing or invalid IDs for sched­
uled 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.
Business Intelligence Platform Repository Diagnostic Tool User Guide
Using the Repository Diagnostic Tool
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
9
Parameter
Optional or Manda­ Description
tory
startid
Optional
Specifies the object in the CMS database to start the scan for.
For example, if you've already scanned 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.
optionsfile
Optional
Specifies the file path to a parameter file. The parameter file is a
text file that lists each command-line option and its values. The
file should have one parameter per line.
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.
syscopy
Optional
This parameter is used when you copy the repository database.
You must run the tool on the newly created copy, which will up­
date the copy to prevent it from clustering with the source sys­
tem servers. If the copy will not be able to communicate with the
source system, this is not necessary. It should only be used with
the mandatary parameters and not be combined with other op­
tional parameters in this list.
Note
Be careful not to run the RDT with the syscopy parameter on
your source system.
trace
Optional
This parameter generates traces (recordings of events that oc­
cur during the operation of a monitored component) and collects
them in log files with the .glf extension at the location:
<SAP_BOBJ_INST_DIR>\SAP BusinessObjects\SAP
BusinessObjects Enterprise XI 4.0\logging
The following parameters are used if the Repository Diagnostic Tool is running on an active clustered CMS.
Table 3: Using the RDT against a clustered CMS
Parameter
Optional or Manda­
tory
Description
requestport
Optional
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.
10
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Business Intelligence Platform Repository Diagnostic Tool User Guide
Using the Repository Diagnostic Tool
Parameter
Optional or Manda­
tory
Description
numericip
Optional
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.
ipv6
Optional
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.
port
Optional
The ipv4 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.
threads
Optional
The number of threads to use. Accepts whole, 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.
Table 4: Using the RDT with SSL
Parameter
Optional or Manda­
tory
Description
protocol
Optional
Specifies whether the tool should run in SSL mode.
The only accepted value is ssl.
ssl_certdir
Optional
The directory that contains the SSL certificates.
ssl_trustedcertificate
Optional
The file name of the certificate.
ssl_mycertificate
Optional
The file name of the signed certificate.
ssl_mykey
Optional
The file name of the file that contains the private SSL key.
ssl_mykey_passphrase
Optional
The file name of the file that contains SSL passphrase.
Example
The following Windows 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>”
Business Intelligence Platform Repository Diagnostic Tool User Guide
Using the Repository Diagnostic Tool
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
11
-dbkey <cluster key>
-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”
Example
Unix example:
./boe_reposcan.sh
-dbdriver oracledatabasesubsystem
-connect "UID=<bi_admin>;PWD=<Password1>;DSN=<myDsn>;PORT=<6400>"
-inputfrsdir /apps/frs/bi/frsinput
-outputfrsdir /apps/frs/bi/frsoutput
-dbkey <cluster key>
12
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Business Intelligence Platform Repository Diagnostic Tool User Guide
Using the Repository Diagnostic Tool
4
Inconsistencies between the CMS and the
FRS
Syntax
The following table describes the inconsistencies that may exist between a Central Management Server (CMS)
database 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.
Warning Message
<Object Name> object
<Object Type> (Object ID:
<ID>) is referencing some
Inconsistency
Recommendation
Action
The object exists in the CMS
database, but there is no
corresponding file in the FRS.
“Allow the application to
The RDT removes the object
remove the missing files from from the CMS database.
the object's file list.”
The file exists in the FRS, but
there is no corresponding file
in the CMS database.
“Please republish the file. The When you republish the file,
application will not publish
an object is created in the
this file for you.”
CMS database.
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 size of the file does not
“Allow the application to
match the InfoObject file size. update the object with the
correct file size.”
The RDT updates the file size
in the CMS database.
The FRS folder is empty.
The RDT removes the empty
directory.
The stored file size is <Size>
which does not match the
actual file size <Size>.
<Folder Path> contains no
files.
Business Intelligence Platform Repository Diagnostic Tool User Guide
Inconsistencies between the CMS and the FRS
“Allow the application to
remove the directory.”
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
13
5
Inconsistencies in the CMS metadata
Syntax
The following table describes the inconsistencies that can occur in the metadata of the objects that are in a
Central Management Server (CMS) system database, 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.
Warning Message
Inconsistency
Recommendation
Action
<Object Type> Object
The object has a missing or
“Allow RDT to move the
The RDT moves the object
<Object Name> (Object ID:
invalid Parent Object ID.
object to the BO Repair
and any child objects to a
folder. ”
repair folder. Only the
<Object Name> <ID>)'s
parent object is missing
administrator has access to
(Parent Object ID = <ID>).
this folder.
<Object Type> Object
The object has a missing or
“Allow the RDT to assign the
The RDT assigns the value of
<Object Name> (Object ID:
invalid Owner Object ID.
object to the Administrator. ”
the Administrator's ID to the
objects Owner ID.
<ID>)'s owner object is
missing (Owner Object ID =
<ID>).
<Object Type> Object
The object has a missing or
The recommendation that
<Object Name> (Object ID:
invalid Submitter Object ID.
the RDT displays depends on
<ID>)'s submitter object is
whether you've provided a
missing (Submitter Object ID
value for the -submitterid
= <ID >).
parameter.
●
If you provide this
parameter, the
recommendation is
“Allow the application to
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.
update the object with
the provided submitter
ID”.
14
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Business Intelligence Platform Repository Diagnostic Tool User Guide
Inconsistencies in the CMS metadata
Warning Message
Inconsistency
Recommendation
●
Action
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”.
<Object Type> Object
The object's last successful
“Allow the application to
When you reschedule the
'<Object Name>' (Object ID:
instance is missing or invalid.
recalculate the property.”
object, the CMS
<ID>)'s last successful
automatically recalculates
instance property refers to a
the ID.
missing object (Object ID =
<ID>).
<Object Type> Object
The object references a
“Reschedule the object with
When you reschedule the
'<Object Name'> (Object
calendar that doesn't exist.
an existing calendar. No
object, the CMS applies a
ID: <ID>)'s calendar object is
action can be taken by this
calendar to the object.
missing (Calendar ID =
application.”
<ID>).
<Object Type> Object
The preferred server does not “ Reschedule the object and
When you reschedule the
'<Object Name>' (Object ID:
exist.
choose an existing server
object, the CMS applies a
<ID>) 's required scheduling
group. No action can be
server group to the object.
server group is missing
taken by this application.”
(Server Group Object ID =
<ID>)..
<Object Type> Object
The event or events that this
“Allow the application to
The RDT removes the
'<Object Name>' (Object ID:
object is waiting on does not
remove the missing events
missing events.
<ID>)'s list of events to wait
exist.
from the object's list of
events to wait for.”
for contains missing object(s)
(Object ID(s) = <ID>).
<Object Type> Object
This object triggers an event
“Allow the application to
The RDT removes the
'<Object Name>' (Object ID:
that does not exist.
remove the missing events
missing events.
<ID>)'s list of events to
from the object's list of
trigger contains missing
events to trigger.”
object(s) (Object ID(s) =
<ID>).
<Object Type> Object
Orphaned Access Control
“ Allow the application to
The RDT removes the
'<Object Name>' (Object ID:
entry.
remove the missing
missing principal(s).
<ID>) Access Control List
principal(s) from the object's
references a missing
Access Control List.”
principal (Object ID = <ID>).
Business Intelligence Platform Repository Diagnostic Tool User Guide
Inconsistencies in the CMS metadata
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
15
Warning Message
Inconsistency
<Object Type> Object
The preferred server does not “Allow the tool to remove the
The RDT removes the objects
'<Object Name>' (Object ID:
exist.
object's invalid entries from
missing entries from the
its Server Group list.”
object's server group list.
<ID>) has invalid Server
Recommendation
Action
Group entries <Server
Group Entries>.
<Object Type> Object
A specific user account has
“Allow the application to
The RDT consolidates the
<Object Name> (Object ID:
multiple favorites folders.
consolidate multiple
user's Favorites folders into a
<ID>) has multiple Favorites
Favorites folders into a single
single folder.
folders.
Favorites folder.”
16
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Business Intelligence Platform Repository Diagnostic Tool User Guide
Inconsistencies in the CMS metadata
Important Disclaimers and Legal Information
Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system
environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP
intentionally or by SAP's gross negligence.
Accessibility
The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a
binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does
not apply in cases of wilful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.
Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales
person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not
exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.
Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not
warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages
caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency
(see: http://help.sap.com/disclaimer).
Business Intelligence Platform Repository Diagnostic Tool User Guide
Important Disclaimers and Legal Information
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
17
www.sap.com/contactsap
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any
form or for any purpose without the express permission of SAP SE
or an SAP affiliate company. The information contained herein may
be changed without prior notice.
Some software products marketed by SAP SE and its distributors
contain proprietary software components of other software
vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company
for informational purposes only, without representation or warranty
of any kind, and SAP or its affiliated companies shall not be liable for
errors or omissions with respect to the materials. The only
warranties for SAP or SAP affiliate company 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.
SAP and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks
of SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the
trademarks of their respective companies.
Please see http://www.sap.com/corporate-en/legal/copyright/
index.epx for additional trademark information and notices.