2 Obtaining and Running Repository Creation Utility

This chapter describes how obtain RCU, then run RCU to create and drop schemas using both the graphical interface and command line interface.

The following topics are covered:

Section 2.1, "Before You Begin"
Section 2.2, "Required Schemas and Dependencies"
Section 2.3, "Obtaining RCU"
Section 2.4, "Starting RCU"
Section 2.5, "Creating Schemas"
Section 2.6, "Dropping Schemas"
Section 2.7, "Creating the Portal Demo Schema"

2.1 Before You Begin

Before you begin, make sure you have read Section 1.1, "RCU System and Database Requirements". You should have a properly configured certified database that is up and running before you continue.

2.2 Required Schemas and Dependencies

This section lists the required schemas and their dependencies for Oracle Fusion Middleware components. Before you run RCU, you should make a note of the schemas you will need to create.

Oracle SOA Suite Schemas
Oracle WebCenter Portal Schemas
Oracle Application Developer Schema
Oracle Identity Management Schemas
Oracle Data Integrator Schema
Oracle Business Intelligence Schemas
Oracle Portal, Forms, Reports and Discoverer Schemas
Oracle WebCenter Content Schemas

2.2.1 Oracle SOA Suite Schemas

Table 2-1 lists the required schemas and dependencies for Oracle SOA Suite products on Oracle and Microsoft SQL Server databases:

Table 2-1 Required Schemas for Oracle SOA Suite Products on Oracle and Microsoft SQL Server Databases

Component Schema Owner Dependencies

Component	Schema Owner	Dependencies
SOA Infrastructure	`prefix_SOAINFRA`	`prefix_MDS` (Metadata Services) `prefix_ORASDPM` (User Messaging)
Business Activity Monitoring	`prefix_ORABAM`	`prefix_MDS` (Metadata Services) `prefix_ORASDPM` (User Messaging)
User Messaging Service	`prefix_ORASDPM`	`prefix_MDS` (Metadata Services)

SOA Infrastructure

prefix_SOAINFRA

prefix_MDS (Metadata Services)

prefix_ORASDPM (User Messaging)

Business Activity Monitoring

prefix_ORABAM

prefix_MDS (Metadata Services)

prefix_ORASDPM (User Messaging)

User Messaging Service

prefix_ORASDPM

prefix_MDS (Metadata Services)

Note:

On Oracle databases, if you create schemas with a database user other than SYS or SYSTEM, you must grant that user the following AQ roles and privileges to successfully load the prefix_SOAINFRA schema:

GRANT ALL ON dbms_aqadm TO new_user WITH GRANT OPTION;
GRANT ALL ON dbms_aq TO new_user WITH GRANT OPTION;
GRANT aq_user_role TO new_user;
GRANT EXECUTE ON dbms_aqin to new_user WITH GRANT OPTION;
GRANT EXECUTE ON dbms_aqjms to new_user WITH GRANT OPTION;

Table 2-2 lists the required schemas and dependencies for Oracle SOA Suite products on IBM DB2 databases:

Table 2-2 Required Schemas for Oracle SOA Suite Products in IBM DB2 Databases

Component Schema Owner Dependencies Required Operating System Users

Component	Schema Owner	Dependencies	Required Operating System Users
SOA Infrastructure	`prefix_SOA`	`prefix_MDS` (Metadata Services) `prefix_UMS` (User Messaging)	`prefix_soa` `prefix_mds` `prefix_ums`
User Messaging Service	`prefix_UMS`	`prefix_MDS` (Metadata Services)	`prefix_ums` `prefix_mds`

SOA Infrastructure

prefix_SOA

prefix_MDS (Metadata Services)

prefix_UMS (User Messaging)

prefix_soa

prefix_mds

prefix_ums

User Messaging Service

prefix_UMS

prefix_MDS (Metadata Services)

prefix_ums

prefix_mds

2.2.2 Oracle WebCenter Portal Schemas

All of the Oracle WebCenter Portal schemas are supported on all certified databases.

Table 2-3 lists the required schemas and dependencies for Oracle WebCenter Portal products on Oracle and Microsoft SQL Server databases:

Table 2-3 Required Schemas for Oracle WebCenter Portal Products on Oracle and Microsoft SQL Server Databases

Component	Schema Owner	Dependencies
Spaces and Services	`prefix_WEBCENTER`	`prefix_MDS` (Metadata Services)
Portlet Producers	`prefix_PORTLET`	None.
Discussions	`prefix_DISCUSSIONS`	None.
Activity Graph and Analytics	`prefix_ACTIVITIES`	None.

Table 2-4 lists the required schemas for Oracle WebCenter Portal products for IBM DB2 databases:

Table 2-4 Required Schemas for Oracle WebCenter Portal Products on IBM DB2 Databases

Component	Schema Owner	Dependencies	Required Operating System Users
Spaces and Services	`prefix_WC`	`prefix_MDS` (Metadata Services)	`prefix_wc` `prefix_mds`
Portlet Producers	`prefix_PT`	None.	`prefix_pt`
Discussions	`prefix_DS`	None.	`prefix_ds`
Activity Graph and Analytics	`prefix_AG`	None.	`prefix_ag`

If you are an application developer and want to build WebCenter Portal applications, you must run RCU a second time to create a second version of the Spaces and Services (prefix_WEBCENTER on Oracle and Microsoft SQL Server databases or prefix_WC on IBM DB2 databases) schema. Note that this schema is separate from the Spaces and Services schema used by Oracle WebCenter Portal: Spaces, so you should make sure you use a different schema prefix. For information about the WebCenter services that require the WebCenter schema, see Table 5-1 in Oracle Fusion Middleware Installation Guide for Oracle WebCenter.

2.2.3 Oracle Application Developer Schema

Oracle Application Developer includes Oracle WSM Policy Manager and Oracle WSM-PM Extension. These components require that the Metadata Services (MDS) schema exists in your database prior to installation.

On all databases, you must create the schema prefix_MDS. On IBM DB2 databases, you must also create the operating system user prefix_mds.

2.2.4 Oracle Identity Management Schemas

Oracle Identity Management schemas are not supported on Microsoft SQL Server or IBM DB2 databases.

Table 2-5 lists the required schemas and dependencies for Oracle Identity Management products on Oracle databases:

Table 2-5 Required Schemas for Oracle Identity Management Components on Oracle Databases

Component	Schema Owner	Dependencies
Oracle Internet Directory	`ODS`	None.
Oracle Identity Federation	`prefix_OIF`	None.
Oracle Identity Manager	`prefix_OIM`	`prefix_MDS` (Metadata Services) `prefix_SOAINFRA` (SOA Infrastructure) `prefix_ORASDPM` (User Messaging Service)
Oracle Access Manager	`prefix_OAM`	`prefix_IAU` (Audit Services)
Oracle Adaptive Access Manager	`prefix_OAAM`	`prefix_MDS` (Metadata Services)
Oracle Adaptive Access Manager (Partition Support)	`prefix_OAAM_PARTN`	`prefix_MDS` (Metadata Services)
Oracle Entitlements Server	`prefix_APM`	`prefix_MDS` (Metadata Services)

2.2.5 Oracle Data Integrator Schema

Oracle Data Integrator requires that the Oracle Data Integrator (prefix_ODI_REPO) schema exists in your Oracle or Microsoft SQL Server database prior to installation.

On IBM DB2 databases, the Oracle Data Integrator schema name is prefix_ODI, and you must also create the operating system user prefix_odi.

2.2.6 Oracle Business Intelligence Schemas

Oracle Business Intelligence requires that the Business Intelligence Platform (prefix_BIPLATFORM) schema exists in your Oracle or Microsoft SQL Server database prior to installation.

On IBM DB2 databases, the Business Intelligence Platform schema name is prefix_BI, and you must also create the operating system user prefix_bi.

2.2.7 Oracle Portal, Forms, Reports and Discoverer Schemas

Oracle Portal and Oracle Discoverer schemas are not supported on Microsoft SQL Server or IBM DB2 databases.

Table 2-6 lists the required schemas and dependencies for Oracle Portal and Oracle Discoverer on Oracle databases:

Table 2-6 Required Schemas for Oracle Portal and Oracle Discoverer on Oracle Databases

Component	Schema Owner	Dependencies
Oracle Portal	`prefix_PORTAL`	Oracle Portlet Producers (`prefix_PORTLET`)
Oracle Discoverer	`prefix_DISCOVERER`	None.

2.2.8 Oracle WebCenter Content Schemas

Table 2-7 lists the required schemas and dependencies for Oracle WebCenter Content on Oracle and Microsoft SQL Server databases:

Table 2-7 Required Schemas for WebCenter Content - Oracle and Microsoft SQL Server Databases

Component	Schema Owner	Dependencies
Oracle Information Rights Management	`prefix_ORAIRM`	None.
Oracle WebCenter Content Server 11g - Complete	`prefix_OCS`	None.
Oracle WebCenter Content Server 11g - Search Only	`prefix_OCSSEARCH`	None.
Oracle WebCenter Content: Records	`prefix_URMSERVER`	None.
Oracle WebCenter Content: Imaging	`prefix_IPM`	None.

Table 2-8 lists the required schemas for Oracle WebCenter Content components for IBM DB2 databases:

Table 2-8 Required Schemas for WebCenter Content - IBM DB2 Databases

Component	Schema Owner	Dependencies	Required Operating System Users
Oracle Information Rights Management	`prefix_IRM`	None.	`prefix_irm`
Oracle Content Server 11g - Complete	`prefix_OCS`	None.	`prefix_ocs`
Oracle WebCenter Content: Records	`prefix_URM`	None.	`prefix_urm`
Oracle WebCenter Content: Imaging	`prefix_IPM`	None.	`prefix_ipm`

2.3 Obtaining RCU

To obtain the latest version of RCU:

Go to the Oracle Fusion Middleware 11g Software Downloads page on Oracle Technology Network:
```
http://www.oracle.com/technetwork/middleware/downloads/fmw-11-download-092893.html
```
If you have not already done so, read the OTN License Agreement, then click on Accept License Agreement.
Look for Repository Creation Utility in the "Required Additional Software" table near the bottom of the page.

After downloading the .zip file, extract the contents to a directory of your choice; this directory will be referred to as the RCU_HOME directory.

Note:
On Windows operating systems, make sure that you do not unzip the RCU .zip file to a directory name containing spaces.

2.4 Starting RCU

Start RCU from the bin directory inside the RCU_HOME directory.

Note:

If you are running RCU using a non-English database, set the following environment variables:

setenv LANG en_US.UTF8
setenv LC_ALL $LANG
setenv NLS_LANG american_america

On Linux operating systems:

cd RCU_HOME/bin
./rcu

On Windows operating systems:

cd RCU_HOME\bin
rcu.bat

If you are creating schemas in your database, go to Section 2.5, "Creating Schemas".

If you are dropping schemas from your database, go to Section 2.6, "Dropping Schemas".

2.5 Creating Schemas

Follow the instructions in Table 2-9 to create schemas.

Click on the screen name to see more detailed information for that screen. Unless otherwise noted, click Next to continue to the next screen.

Table 2-9 RCU Screens and Descriptions for Creating Schemas

RCU Screen	Instructions and Action Required
Welcome	None.
Create Repository	Select Create.
Database Connection Details	Specify the connection details for your database, then click Next. Remember that if you are creating schemas on an IBM DB2 database, you must have already created one operating system user for each schema you want to create. See Section 1.1.4, "Important Information for IBM DB2 Databases" for more information. A separate dialog window will appear while RCU checks connectivity and some database prerequisites. When the database checking as passed without errors, click OK to dismiss the dialog window and go to the next screen.
Select Components (for Create Operation)	Specify a schema prefix and select the components for which you want to create schemas in the database. To see which schemas are required for your product, see Section 2.2, "Required Schemas and Dependencies". You must remember the prefix and schema names for the components you are installing; you will need this information during the configuration phase of your product installation. Oracle recommends that you write these values down.
Schema Passwords	Specify the passwords for your schema owners. You must remember the passwords you enter on this screen; you will need this information during the configuration phase of your product installation. Oracle recommends that you write these values down.
Custom Variables	If selected either Master and Work Repository (`ODI_REPO`) or Activity Graph and Analytics (`ACTIVITES`) on the Select Components (for Create Operation), you must supply additional configuration information for custom variables.
Map Tablespaces	Configure the desired tablespace mapping for the schemas you want to create, then click Next. A separate dialog window will appear asking you to confirm that you want to create these tablespaces. Click OK to proceed and dismiss the dialog window. A second dialog window will appear showing the progress of tablespace creation. After this is complete, click OK to dismiss this window and go to the next screen.
Summary (for Create Operation)	Review the information on this screen, then click Create to begin schema creation.
Completion Summary (for Create Operation)	Note the location of the log files, then click Close to dismiss the screen.

2.6 Dropping Schemas

To drop schemas from the database, start RCU (see Section 2.4, "Starting RCU"), then follow the instructions in Table 2-10.

Click on the screen name to see more detailed information for that screen. Unless otherwise noted, click Next to continue to the next screen.

Table 2-10 RUC Screens and Description for Dropping Schemas

Screen	Instructions and Action Required
Welcome	None.
Create Repository	Select Drop.
Database Connection Details	Specify the connection details for your database, then click Next. A separate dialog window will appear while RCU checks connectivity and some database prerequisites. When the database checking as passed without errors, click OK to dismiss the dialog window and go to the next screen.
Select Components (for Drop Operation)	Select the prefix and the schemas you want to drop, then click Next. A separate dialog window will appear asking you to verify that you want to drop the selected schemas. Click OK to dismiss this window. A second dialog window appears while RCU checks the prerequisites for the schemas you are dropping. After this is complete, click OK to dismiss this window and go to the next screen.
Summary (for Drop Operation)	Review the information on this screen, then click Drop to drop the schemas.
Completion Summary (for Drop Operation)	Note the location of the log files, then click Close to dismiss the screen.

2.6.1 Dropping Shared Tablespaces

Tablespaces that are shared among multiple schemas will not be dropped. For example, if you created both the Audit Services (for example, DEV_IAU) and Metadata Services (for example, DEV_MDS) schemas, both schemas would use the temporary tablespace DEV_IAS_TEMP (see Section A.9.1, "Default Tablespace Mappings").

If you then drop the DEV_IAU schema, the DEV_IAS_TEMP tablespace would not be dropped since it is also being used by the DEV_MDS schema.

2.6.2 Dropping Schemas and Deleting Datafiles (Windows Only)

If your database is running on a Windows operating system, and you are using RCU to drop schemas from that database, some components datafiles are not dropped. These datafiles are located in the oradata directory in the database Oracle home.

For example, the following datafiles must be removed for Oracle Internet Directory (OID):

ATTRS1_OID.DBF
BATTRS1_OID.DBF
GCATS1_OID.DBF
GDEFAULT1_OID.DBF
SVRMG1_OID.DBF
IASTEMP.DBF

In the event you want to re-create the dropped schema, you must first manually delete the datafiles before re-creating the schema.

2.7 Creating the Portal Demo Schema

The Oracle Portal repository includes a demo schema (portal_schema_user_name_DEMO) that can not be installed using RCU. If you want to install this schema for testing purposes, you must do so using the instdemo.sql script:

> sqlplus /nolog
SQL> connect sys as sysdba
SQL> @instdemo.sql portal_schema_user_name
                   portal_schema_user_password
                   default_tablespace
                   temporary_table_space
                   name_of_the_demo_schema_user
                   password_of_the_demo_schema_user
                   name_of_the_log_file
                   database_connection_string

For example:

SQL> @instdemo.sql portal portalpassword portal ias_temp portal_demo portaldemopassword example_app.log (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=db.example.com)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=orcl)))