Checking the block size when installing the Discoverer Catalog Certifying Discoverer Plus OLAP with Oracle Database 11g Release 2 11.2

Configuring Discoverer Plus OLAP 5-5

6. Click Continue.

If a Discoverer Catalog already exists in the specified database, a warning message is displayed indicating that if you proceed with the installation process, the existing Catalog will be overwritten.

7. Click Yes to proceed.

The Install Catalog: D4OSYS Details page is displayed. 8. Enter the password that you want to use for the D4OSYS user. In the Tablespace field, select the tablespace into which you want to install the Discoverer Catalog. You created this tablespace in step 1.

9. Click Finish.

A window is displayed prompting you to confirm whether you want to install the Discoverer Catalog.

10. Click Yes to complete the installation process.

5.2.2.1 Checking the block size when installing the Discoverer Catalog

An analytic workspace has a recommended 8-KB block size; so you might want to use that specification for the block size of the tablespace into which you install the Discoverer Catalog. Depending on requirements such as the character set in use, however, the block size may need to be changed. When creating a custom tablespace with an 8-KB block size, specify 8192 as the block size value. If the block size is not large enough, you might see an error message such as the following one when you try to install the Discoverer Catalog: oracle.dss.d4o.administration.D4OInstallationException: D4O-1125 Post-install verification failed, not all Discoverer Catalog objects are installed. Expected xx, found yy. xx represents the number of objects expected. yy represents the number of objects found. This error message indicates that, during the creation of the Discoverer Catalog, an attempt was made to create an index using a key size that is larger than the maximum allowed value. The index key size is limited by the value of the block size for the database or for the tablespace, because a key value cannot span multiple blocks. Tip: Ask your database administrator for information about the block sizes of tablespaces and of the database.

5.2.2.2 Certifying Discoverer Plus OLAP with Oracle Database 11g Release 2 11.2

To certify a Discoverer Plus OLAP installation with Oracle Database 11.2, perform the following steps: 1. After installing Oracle Database 11.2, download the following Oracle OLAP patches from My Oracle Support and install these patches: Note: Alternatively, you can install the Discoverer Catalog by using the Discoverer Plus OLAP command line utility. For more information, see Section 5.9, Using the Discoverer Plus OLAP command line utility to manage the Discoverer Catalog. 5-6 Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer ■ Patch ID: 9037279 ■ Patch ID: 9212228 2. To connect an OLAP 10.2 analytic workspace to a Oracle Database 11.2 instance, set either of the following modes: ■ SupportMTM = FALSE, MetadataReaderMode = DEFAULT Run the following script: alter system set _xsolapi_support_mtm = FALSE scope=spfile; alter system set _xsolapi_metadata_reader_mode=DEFAULT In this mode, you can either connect to OLAP 10g or OLAP 11g analytic workspaces, but you should apply the naming rules for the OLAP 11g objects to avoid naming conflicts. To connect to OLAP 10g analytic workspaces in this mode, you should run the INITIALIZE_CUBE_UPGRADE PLSQL procedure for the schema. This procedure generates a table that maps old OLAP 10.2 objects to the corresponding OLAP 11.2 object names. The OLAP API uses this mapping to enable OLAP 10.2 analytic workspaces to work with the OLAP 11.2 metadata reader logic. For more information about executing the INITIALIZE_CUBE_UPGRADE PLSQL procedure, see Oracle Database PLSQL Packages and Types Reference. ■ SupportMTM = TRUE, MetadataReaderMode = 10_ONLY Run the following script: alter system set _xsolapi_support_mtm = TRUE scope=spfile; alter system set _xsolapi_metadata_reader_mode=10_ONLY In this mode, you can connect only to OLAP 10g analytic workspaces. The 11g naming rules need not be applied here.

5.2.3 Uninstalling a Discoverer Catalog