Handling Catalog Files on Various Platforms Known Issues with Catalog Files

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. Configuring and Managing the Oracle BI Presentation Catalog 17-11 The elements have the values that are described in the following list: ■ None — Specifies that no validation is performed. ■ Report — Specifies that details about each inconsistent object are written to the sawlog.log file. For information, see Section 8.3.2, What Are Diagnostic Log Configuration Files and Where Are They Located? ■ Clean — Specifies that details about each inconsistent object are written to the sawlog.log file and that each object is removed from the catalog.

17.3 About Catalog Manager

Catalog Manager is a tool that lets you perform online and offline management of Oracle BI Presentation Catalogs. It should be installed on a secure computer that is accessible only to Oracle BI Administrators. Table 17–1 Elements for Validating the Catalog Element Description Default Value Validate Performs the validation of the catalog according to the values of the other Validate-related elements in this section. Values are described in the following list: ■ None — Performs no validation. ■ OnStartup — Performs the validation when Presentation Services starts. ■ OnStartupAndExit — Performs the validation when Presentation Services both starts and stops. This value allows re-running of the validation, performing as many cycles of Report and Clean until the catalog is as clean as appropriate. If this value is not None, then all privileges and each objects ACLs in the entire catalog are cleaned of terminated accounts, regardless of the settings of the other Validate-related elements. None ValidateAccounts Verifies that all information about users, roles, and groups in the catalog is consistent. Values are described in the list after this table. None ValidateHomes Verifies that all information about home directories in the catalog is consistent. Values are described in the list after this table. None ValidateItems Verifies that all information about objects in the catalog is consistent. Values are described in the list after this table. None ValidateLinks Verifies that all information about links in the catalog is consistent. Values are described in the list after this table. None