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:
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.
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.
Table 2-2 lists the Oracle SOA Suite schemas and their supported databases.
Table 2-1 Oracle SOA Suite Schemas and Supported Datases
Component | Supported Databases |
---|---|
SOA Infrastructure |
Oracle, Microsoft SQL Server, IBM DB2 |
Business Activity Monitoring |
Oracle |
User Messaging Service |
Oracle, Microsoft SQL Server, IBM DB2 |
Table 2-2 lists the required schemas and dependencies for Oracle SOA Suite products on Oracle and Microsoft SQL Server databases:
Table 2-2 Required Schemas for Oracle SOA Suite Products on Oracle and Microsoft SQL Server Databases
Component | Schema Owner | Dependencies |
---|---|---|
SOA Infrastructure |
|
|
Business Activity Monitoring |
|
|
User Messaging Service |
|
|
Note:
On Oracle databases, if you create schemas with a database user other thanSYS
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;
Table 2-3 lists the required schemas and dependencies for Oracle SOA Suite products on IBM DB2 databases:
Table 2-3 Required Schemas for Oracle SOA Suite Products in IBM DB2 Databases
Component | Schema Owner | Dependencies | Required Operating System Users |
---|---|---|---|
SOA Infrastructure |
|
|
|
User Messaging Service |
|
|
|
All of the Oracle WebCenter schemas are supported on all certified databases.
Table 2-4 lists the required schemas and dependencies for Oracle WebCenter products on Oracle and Microsoft SQL Server databases:
Table 2-4 Required Schemas for Oracle WebCenter Components on Oracle and Microsoft SQL Server Databases
Component | Schema Owner | Dependencies |
---|---|---|
WebCenter Spaces |
|
|
Portlet Producers |
|
None. |
Discussions |
|
None. |
Discussions Crawler |
|
|
Wiki and Blogs |
|
None. |
Oracle Content Server 10g |
|
None. |
Table 2-5 lists the required schemas for Oracle WebCenter components for IBM DB2 databases:
Table 2-5 Required Schemas for Oracle WebCenter Components on IBM DB2 Databases
Component | Schema Owner | Dependencies | Required Operating System Users |
---|---|---|---|
WebCenter Spaces |
|
|
|
Portlet Producers |
|
None. |
|
Discussions |
|
None. |
|
Discussions Crawler |
|
|
|
Wiki and Blogs |
|
None. |
|
Oracle Content Server 10g |
|
None. |
|
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
.
Oracle Identity Management schemas are not supported on Microsoft SQL Server or IBM DB2 databases.
Table 2-6 lists the required schemas and dependencies for Oracle Identity Management products on Oracle databases:
Table 2-6 Required Schemas for Oracle Identity Management Components on Oracle Databases
Component | Schema Owner | Dependencies |
---|---|---|
Oracle Internet Directory |
|
None. |
Oracle Identity Federation |
|
None. |
Oracle Identity Manager |
|
|
Oracle Access Manager |
|
|
Oracle Adaptive Access Manager |
|
|
Oracle Adaptive Access Manager (Partition Support) |
|
|
Authorization Policy Manager |
|
|
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
, andyou must also create the operating system user prefix_
odi
.
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
, andyou must also create the operating system user prefix_
bi
.
Oracle Portal and Oracle Discoverer schemas are not supported on Microsoft SQL Server or IBM DB2 databases.
Table 2-7 lists the required schemas and dependencies for Oracle Portal and Oracle Discoverer on Oracle databases:
Table 2-8 lists the Oracle Enterprise Content Management (Oracle ECM) Suite schemas and their supported databases.
Table 2-8 Oracle ECM Suite Schemas and Supported Datases
Component | Supported Databases |
---|---|
Oracle Information Rights Management |
Oracle, Microsoft SQL Server, IBM DB2 |
Oracle Content Server 11g - Complete |
Oracle, Microsoft SQL Server, IBM DB2 |
Oracle Content Server 11g - Search Only |
Oracle |
Oracle Universal Records Management 11g |
Oracle, Microsoft SQL Server, IBM DB2 |
Oracle Imaging and Process Management |
Oracle, Microsoft SQL Server, IBM DB2 |
Table 2-9 lists the required schemas and dependencies for Oracle ECM Suite on Oracle and Microsoft SQL Server databases:
Table 2-9 Required Schemas for Oracle ECM Components on Oracle and Microsoft SQL Server Databases
Component | Schema Owner | Dependencies |
---|---|---|
Oracle Information Rights Management |
|
None. |
Oracle Content Server 11g - Complete |
|
None. |
Oracle Content Server 11g - Search Only |
|
None. |
Oracle Universal Records Management 11g |
|
None. |
Oracle Imaging and Process Management |
|
None. |
Table 2-10 lists the required schemas for Oracle ECM components for IBM DB2 databases:
Table 2-10 Required Schemas for Oracle ECM Components on IBM DB2 Databases
Component | Schema Owner | Dependencies | Required Operating System Users |
---|---|---|---|
Oracle Information Rights Management |
|
None. |
|
Oracle Content Server 11g - Complete |
|
None. |
|
Oracle Universal Records Management 11g |
|
None. |
|
Oracle Imaging and Process Management |
|
None. |
|
To obtain the latest version of RCU, go to the Oracle Fusion Middleware 11gR1 Software Download page on Oracle Technology Network:
http://www.oracle.com/technology/software/products/middleware/htdocs/fmw_11_download.html
Look for Repository Creation Utility in the "Required Additional Software" table. 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.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".
Follow the instructions in Table 2-11 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-11 How to Create Schemas
No. | RCU Screen | Instructions and Action Required |
---|---|---|
1 |
None. |
|
2 |
Select Create. |
|
3 |
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. |
|
4 |
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. |
|
5 |
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. |
|
6 |
If selected the Oracle Data Integrator schema on the Select Components Screen (for Create Operation), you must supply additional configuration information for this schema. |
|
7 |
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. |
|
8 |
Review the information on this screen, then click Create to begin schema creation. |
|
9 |
Note the location of the log files, then click Close to dismiss the screen. |
To drop schemas from the database, start RCU (see Section 2.4, "Starting RCU"), then follow the instructions in Table 2-12.
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-12 How to Drop Schemas
No. | Screen | Instructions and Action Required |
---|---|---|
1 |
None. |
|
2 |
Select Drop. |
|
3 |
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. |
|
4 |
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. |
|
5 |
Review the information on this screen, then click Drop to drop the schemas. |
|
6 |
Note the location of the log files, then click Close to dismiss the screen. |
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.
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 (for example, OID).
In the event you want to re-create the dropped schema, you must first manually delete the datafile before creating the 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)))