Handling Heterogeneous Nodes File System Guidelines for Catalogs

Configuring and Managing the Oracle BI Presentation Catalog 17-9 For information, see Section 10.2, Using Fusion Middleware Control to Upload a Repository and Set the Oracle BI Presentation Catalog Location.

17.2.4 Validating the Catalog

Over time, inconsistencies can develop in the catalog as links are broken, users are deleted, or NFS file system issues are encountered. These inconsistencies can eventually lead to incorrect behavior, such as the inability to edit an agents recipient list. You can periodically take the production system offline and validate the catalog, to be informed of and to take corrective action on inconsistencies.

17.2.4.1 Performing a Basic Validation of the Catalog

Use the following procedure to perform a basic validation of the catalog. To validate the catalog: 1. Stop Presentation Services. For information, see Section 4.3, Using Fusion Middleware Control to Start and Stop Oracle Business Intelligence System Components and Java Components. 2. In 11g only, regenerate the user GUIDs for the catalog. See Regenerating User GUIDs in Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition for information 3. Back up the catalog by using the 7-Zip utility to create a compressed file for it. 4. Create a backup copy of the instanceconfig.xml file. For the location of the file, see Section 3.6, Where Are Configuration Files Located? 5. Edit the instanceconfig.xml file so that it contains the appropriate elements for performing the validation. For information on these elements, see Section 17.2.4.2, Specifying the Elements for Validating the Catalog. 6. Start Presentation Services to run the validation according to the values that you specified in the instanceconfig.xml file. 7. Stop Presentation Services. 8. Create a backup copy of the instanceconfig.xml file in which you added the validation elements, renaming the file similar to instanceconfig_validate.xml. In this way, you have a version of the file to use as a starting point for subsequent validations. 9. Restore the backup version of the instanceconfig.xml that you created earlier to use as the current version. 10. Start Presentation Services. Caution: Ensure that you regenerate the user GUIDs before validating the catalog. Failure to do so can result in the removal of all accounts, permissions, and privileges from the catalog. 17-10 System Administrators Guide for Oracle Business Intelligence Enterprise Edition

17.2.4.2 Specifying the Elements for Validating the Catalog

As part of the process of validating the catalog, you include elements in the instanceconfig.xml file that run the validation when you restart Presentation Services. The following procedure describes how to edit the instanceconfig.xml file to include these elements. Before you begin this procedure, ensure that you are familiar with the information in Section 3.4, Using a Text Editor to Update Configuration Settings. To specify the element for validating the catalog: 1. Open the instanceconfig.xml file for editing as described in Section 3.6, Where Are Configuration Files Located?

2. Locate the Catalog section in which you must add the elements that are described

in Table 17–1 .

3. Include the elements and their ancestor element as appropriate, as shown in the

following example. In this example, the validation runs when Presentation Services starts. Inconsistent accounts such as those for deleted users, links, and objects are removed. Inconsistent users home directory names are logged but directories are not removed. ServerInstance ps:Catalog xmlns:ps=oracle.bi.presentation.servicesconfigv1.1 ps:ValidateOnStartupAndExitps:Validate ps:ValidateAccountsCleanps:ValidateAccounts ps:ValidateHomesReportps:ValidateHomes ps:ValidateItemsCleanps:ValidateItems ps:ValidateLinksCleanps:ValidateLinks ps:Catalog ServerInstance

4. Save your changes and close the file.

Caution: Include only one Catalog element in the instanceconfig.xml file or unexpected results might occur. Unless expressly noted, include most nodes in an XML document only once.