Oracle Business Intelligence Requirements 3-3
3.3.2 Sharing Schemas Required by Oracle Business Intelligence
If your organization has an MDS schema installed in a supported database, you do not need to install the MDS schema again with RCU. You can use the existing MDS
schema for your Oracle Business Intelligence installation. For this option, deselect the Metadata Services schema in the Select Components screen of RCU. Then, when you
install Oracle Business Intelligence, specify the details for the existing MDS schema in the
MDS Schema screen.
However, each Oracle Business Intelligence system BI domain requires its own BIPLATFORM schema. Two or more systems cannot share the same BIPLATFORM
schema, although they can share the same database. Therefore, you must run RCU and install the BIPLATFORM schema and the MDS schema if no MDS schema exists
before installing each distinct Oracle Business Intelligence system BI domain. For example, if you plan to install two Oracle Business Intelligence systems, you must run
RCU and install the required schemas twice, or once for each system.
This requirement does not apply when you scale out an Oracle Business Intelligence system. In a scaled out clustered system, you only run RCU and install the database
schemas once, before installing the primary node of the Oracle Business Intelligence cluster the BI domain for the cluster is created at that time. Additional Oracle
Business Intelligence nodes that you install during the scale-out process become members of that domain and, therefore, use the same set of schemas.
3.3.3 Creating Oracle Business Intelligence 11g Schemas on IBM DB2
When using Repository Creation Utility RCU with an IBM DB2 database, ensure that the database schemas created by RCU have the required permissions to use the
DataDirect ODBC drivers. If these permissions are not set, then Oracle BI Scheduler fails to start because it cannot query the Oracle BI Scheduler tables. You can find the
correct permissions in the DataDirect driver documentation at the following location:
http:www.datadirect.comdocspublictutorialsConnect-for-ODBC odbcdb2bind.pdf
Additionally, when using RCU to install the BIPLATFORM and MDS schemas on an IBM DB2 database in a Linux environment, note the following:
■
Ensure that the schema names are eight characters or less.
For example, if you use the prefix dev, you must edit the default schema name of dev_BIPLATFORM to be eight characters or less. You can shorten the suffix, but
the prefix for both schema names must be the same. You can edit the schema name by clicking the name to make it an editable field.
If you do not shorten the schema name to eight characters or less, then RCU returns an error on the Password page that states, Please enter valid
usernamepassword. This is the same error that is returned if the user on the DB2 instance does not have the same password as entered in RCU.
■
There may be a name length restriction for the temporary tablespace name. If the BIPLATFORM tablespace name is too long, then see Oracle Fusion Middleware
Repository Creation Utility Users Guide for information about creating a new tablespace with a shorter name. You can also use the same tablespace as that for
the MDS schema.
Note: The prefix for both the BIPLATFORM and MDS schema names
must be the same.
3-4 Installation Guide for Oracle Business Intelligence
3.3.4 Database Privileges Granted to Oracle Business Intelligence Users
The following privileges are granted to users created by RCU:
■
resource
■
connect
■
create sequence For information about the use of RCU, refer to Repository Creation Utility Overview
in Oracle Fusion Middleware Repository Creation Utility Users Guide.
3.3.5 Obtaining RCU
