| Oracle® Fusion Middleware Repository Creation Utility User's Guide 11g Release 1 (11.1.1) Part Number E14259-03 |
|
|
View PDF |
| Oracle® Fusion Middleware Repository Creation Utility User's Guide 11g Release 1 (11.1.1) Part Number E14259-03 |
|
|
View PDF |
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:
Repository Creation Utility is a graphical and CLI-based tool used to create and manage Oracle Fusion Middleware database schemas.
Some key features of RCU are listed below:
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 TEMP directory.
In situations where a database is not accessible locally for application administrators, RCU can be launched 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.7, "Using the Repository Creation Utility CLI".
RCU provides the flexibility to create custom schemas and tablespaces.
Note:
The Oracle Internet Directory (
ODS) component cannot be prepended with a custom prefix; there can only be one repository for this component per database.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).
For more information about component level prerequisites for Oracle databases, refer to the System Requirements document:
http://www.oracle.com/technology/software/products/ias/files/fusion_requirements.htm
RCU also supports the concept of prefixes, which are used to group related schemas together. For more information, see Section 2.4.2, "Are Multiple Schemas Supported?".
The mapping between the prefixes and schemas is maintained in schema_version_registry.
RCU is available either on its own installation CD-ROM in the bin directory, or in a ZIP file on Oracle Technology Network (OTN):
http://www.oracle.com/technology/software/products/middleware/htdocs/111110_fmw.html
If you download the ZIP file from OTN, 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.zip file to a directory name containing spaces.
|
 Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|