Many of the Oracle Fusion Middleware components require the existence of schemas in a database prior to installation. These schemas are created and loaded in your database using the Repository Creation Utility (RCU).
This chapter contains the following content:
Note:For 11gR1 (11.1.1) only Oracle databases are supported. For specific Oracle database version information, refer to the system requirements document, available on Oracle Technology Network (OTN):
RCU provides extensibility with XML DTDs. Using these DTDs, component owners can integrate their components and prerequisites with RCU by providing a configuration file that adheres to the provided DTD.
RCU can be run locally from the CD or remotely. In either case, both a graphical interface and command line (CLI) options are available.
In situations where the application administrator is not allowed to install components in the database server, RCU can be started directly from the CD. The CD contains the extracted Oracle Client software and RCU uses SQLPLUS and other scripts and libraries from the CD to perform its operations.
When RCU is launched from the CD, log files are written to the user's
In situations where a database is not accessible locally for application administrators, RCU can be lunched against a remote database. The SQLNET client is packaged with RCU to support this operation.
RCU provides a command line interface in situations where Xserver is not available or you have access to telnet terminals without display capabilities. The command line interface also allows you to embed RCU from command line scripts or with some Oracle Fusion Middleware components (for example, Enterprise Manager).
For more information using the CLI, see Section 2.5, "Using the Repository Creation Utility CLI".
Note:Oracle Internet Directory schema names cannot be customized. Other Identity Management schemas names, like OIF (Oracle Identity Federation), can be customized.
Users can choose to rename schemas, or change the tablespace allocation so that components can share a single or multiple tablespaces.
In addition, auxiliary schemas can be mapped to additional tablespaces.
At runtime, RCU performs checks against both global and component level prerequisites. If a prerequisite is not met, RCU may issue a warning and allow the procedure to continue (soft stop), or will notify the user that a prerequisite must be met before the operation can continue (hard stop).
RCU supports multiple repositories (collection of related schemas) within a single physical database. For example, you could have one repository with only one schema named
MDS and a second repository with two schemas named
PORTAL. Both of these repositories can reside on the same database.
RCU also supports the concept of prefixes, which are used to group related schemas together. For example, you could have two versions of the MDS schema in your database: a test version and a production version. You could create a "Test" prefix for your test MDS schema (
Test_MDS) and then a "Prod" prefix for your production MDS schema (
RCU is available either on its own installation CD-ROM in the
bin directory, or in a ZIP file on Oracle Technology Network (
http://www.oracle.com/technology/). If you download the ZIP file, you should extract the contents to a folder on your local system, then run RCU from the
bin directory in that folder.
Note:On Windows systems, make sure that you do not unzip the RCU
.zipfile to a directory name containing spaces.