This document was uploaded by user and they confirmed that they have the permission to share
it. If you are author or own the copyright of this book, please report to us by using this DMCA
report form. Report DMCA
Overview
Download & View Xi3 Bip Repository Diagnostic Tool En as PDF for free.
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 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 Appendix A
Get More Help
Index
13
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
1
Working with the Repository Diagnostic Tool 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:
•
For Windows: \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
1
1
Working with the Repository Diagnostic Tool Using the Repository Diagnostic Tool