The following topics introduce you to the concepts and features you should be familiar with before using the Repository Creation Utility (RCU).
Use the certification and system requirements documents to find important information about supported platforms for RCU, certified databases, and database configuration information.
Read this information carefully before you obtain and run RCU.
Use the system requirements document to review the supported platforms on which you can run RCU.
To see the platforms on which you can run RCU, review the "RCU Supported Platforms" section in the Oracle Fusion Middleware System Requirements and Specifications document.
If you don’t already have a database where you can install schemas, you must install and configure a certified database.
For a list of certified databases that can be used with RCU, refer to the System Requirements and Supported Platforms for Oracle Fusion Middleware 12c certification document for your release, located on the Oracle Fusion Middleware Supported System Configurations page.
Make sure you review the general and component-specific database requirements that should be met before you run RCU.
Before you begin using RCU, review the "Repository Creation Utility Requirements" section in the Oracle Fusion Middleware System Requirements and Specifications document.
Note that not all schemas are supported on all databases. Make sure you have read the information in this section carefully so that you configure a certified database that supports the schemas you need for your Fusion Middleware components.
If you’re creating component schemas on an IBM DB2 database, there are additional requirements to consider.
In addition to the typical space and configuration database requirements, IBM DB2 databases also have the following special requirements:
On IBM DB2 databases running on Linux operating systems, there is a limitation with regards to the length of the schema names.
One database operating system user must be created for each schema that is created in an IBM DB2 database.
For example, if you plan to create a schema named
DEV_STB using RCU, then the operating system user must be named
dev_stb (all lowercase letters).
You can create the operating system user by running the following command as
root (this example creates the operating system user
dev_stb and assigns the provided password to the user):
/usr/sbin/useradd dev_stb -p password -d /scratch/dev_stb
You can then set the password of the user (for example,
dev_stb) by running the following commands as
passwd -u dev_stb passwd dev_stb
Refer to your system documentation for more information.
Before you create your schemas, ensure that you understand the concepts regarding schema creation and organization.
Schema creation in RCU is performed in multiple phases; each phase requires a different level of access to your database.
System Load Phase
During the system load phase, RCU will create the necessary tablespaces and schemas and also the
schema_version_registry, if it is not already present. One entry for each component will be created in
schema_version_registry, and the entry will have the appropriate access and status set to "LOADED" in the
These actions must be performed by someone with SYS or SYSDBA privileges; authentication credentials must be provided on the Database Connection Details screen when running RCU.
If you do not have the necessary privileges, you can select Prepare Scripts for System Load on the Create Repository screen. This will generate a SQL script containing all the same SQL statements and blocks that would have been called if RCU were to execute the actions for the selected components. After the script is generated, a user with the necessary SYS or SYSDBA privileges can execute the script to complete the system load phase.
After the system load phase is complete, any user with the privileges described in Granting Permissions to Users for Querying System Load Objects can then run RCU again to complete the schema creation by performing the product load phase.
If you need to generate the script for system load, you can only create schemas on Oracle and Oracle EBR databases; the system load script is not supported on any other database.
If you are performing the system load with full SYS or SYSDBA privileges, then you can create the schemas on any certified database.
Product Load Phase
During the product load phase, RCU will create procedures, functions, tables, indexes and other objects within schemas and run any action that does not require DBA access. Any non DBA user or the REGISTRYOWNER user can be used for this step.
Before performing the product load phase, the user must be granted the following:
grant REGISTRYACCESS to user; grant STBROLE to user;
After the product load phase is complete, the status for each component will change from ‘LOADED’ to ‘VALID’ in the
Optional Post-Product Load Phase
This step is only needed for components that generate the
script_postDataLoad.sql script requiring DBA privileges during the system load phase. After the product load phase is complete, someone with SYS or SYSDBA privileges should execute the
This step is required for the following components:
Audit Services (
Oracle Enterprise Scheduler (
If you want to give a user with limited privileges the ability to query the system load objects, you must grant the user certain permissions before they can query the system load.
This user will be used for connecting to the system for queries, but the generated scripts from the system load phase must be run by someone with DBA privileges.
grant select_catalog_role to user; grant select any dictionary to user; grant create session to user; grant select on schema_version_registry to user;
You may encounter a "Table or view does not exist" error message when you execute the last command; this can be safely ignored.
After performing the system load, grant the following to the same user in order for them to perform data load:
grant REGISTRYACCESS to user; grant STBROLE to user;
Use custom prefixes to group together schemas in your database.
For important information regarding custom prefixes in IBM DB2 databases, see Additional Requirements for IBM DB2 Databases.
The prefix is prepended to and separated from the schema name with an underscore (_) character, as shown below:
Can only contain alpha-numeric characters; no spaces or other special characters.
Must begin with a letter.
Must not be longer than 12 characters.
The total length of the prefixed schema name (your custom prefix plus the component schema name) must not be longer than 30 characters.
The default prefix used by RCU is
DEV has already been used, then RCU will default to
DEV2, and so on. Prefixes are used to create and organize logical groups of schemas. For example, you may want to create a test version of the Metadata Services (schema name
TEST_MDS; then, when are ready for your production version, you can create a second version of the schema called
PROD_MDS may reside on the same or separate databases.
You are only allowed to use a prefix once per schema within a single database. For example, if you had a version of the Metadata Services schema called
DEV_MDS, then you can not use the
DEV prefix again to create another version of the Metadata Services schema (for example,
If you want to create another version of the schema using the same prefix, you must first drop the existing schema and then create the schema again.
The mapping between the prefixes and schemas is maintained in
The Service Table schema is a special schema that is automatically created once per prefix. The service table stores basic schema configuration information (for example, schema prefixes and passwords) that can then be accessed and used by other Oracle Fusion Middleware components during domain creation.
For example, the configuration wizard has screens which you can configure to use the data stored in the service table when RCU was run. After you provide the service table schema credentials, the data from the service table is used to populate the fields on the screen, thus saving you the need to manually populate that data yourself.
Once created, service tables are used to wire Oracle Fusion Middleware components together. For more information, see Wiring Components to Work Together in Oracle Fusion Middleware Administering Oracle Fusion Middleware.
Before you run RCU, make sure you understand how schemas can be grouped together and distributed depending on your specific environment.
For more information, the following examples are provided:
This example shows a set of schemas in a single database being used by a single WebLogic domain.
This is the simplest scenario in which all schemas using the
DEV prefix are grouped together and used by this single WebLogic domain.
Figure 1-1 Schemas on a Single Database for a Single Domain
This example shows a single set of schemas distributed on multiple databases being used by a single WebLogic domain.
Figure 1-2 Schemas on Multiple Databases for a Single Domain
Note that the same schema prefix (in this case,
DEV) can be used to group these related schemas together, even across multiple databases.
This example shows how schemas on a single database should be grouped for multiple domains.
Figure 1-3 Schemas on a Single Database for Multiple Domains
In this example, the prefixes are grouped together by using
DEV1 for one set of schemas (used by WebLogic Domain 1), and
DEV2 for the second set (used by WebLogic Domain 2).
It is not possible to share a single set of schemas across multiple domains; each domain must have its own set of schemas.
This example shows one way to organize schemas on multiple databases for use with multiple WebLogic domains.
Figure 1-4 Schemas on Multiple Databases for Multiple Domains
Note that in this scenario it is possible to have separate domains on the same host use schemas with the same name and prefix (
DEV), since the schemas are located on different databases.
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.
For more information, refer to Extending Repository Creation Utility to Configure Custom Application Repositories.
Java Access Bridge enables assistive technologies, such as JAWS screen reader, to read Java applications running on the Windows platform.
Assistive technologies can read Java-based interfaces, such as Oracle Universal Installer and Oracle Enterprise Manager.
For more information, see the following topics:
Follow these steps to download and install Java Access Bridge.
jaccess-1_4.jarfrom your installation location to the
JAWTAccessBridge.dllfiles from your installation location to the
accessibility.propertiesfile to the
To configure RCU to use Java Access Bridge after you complete the installation, set the system variable
ORACLE_OEM_CLASSPATH to point to the installed Java Access Bridge files.
Use a semicolon to separate the two paths. Do not use quotes or character spaces.