2 Running Repository Creation Utility (RCU)

This chapter describes how to use RCU to create and drop schemas using both the graphical interface and command line interface.

The following topics are covered:

2.1 Starting RCU

To start RCU, insert the RCU CD-ROM and start RCU from the rcuHome/bin (on UNIX) or rcuHome\bin (on Windows) directory:

On UNIX:

./rcu

On Windows:

rcu.bat

You can also download a .zip file containing RCU from Oracle Technology Network (OTN):

http://www.oracle.com/technology/

After downloading the .zip file, extract the contents to a directory of your choice, and run RCU from the RCU_HOME/bin (on UNIX) or RCU_HOME\bin (on Windows) directory with the commands shown above, where RCU_HOME is the folder where RCU was unzipped, or the drive or mount point of the CD-ROM.

Note:

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

Note:

RCU is available only on Linux and Windows platforms. Either the Linux RCU or Windows RCU may be used to create schemas on any supported database platform.

2.2 Using RCU with Java Access Bridge (Windows Only)

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.

2.2.1 Install Java Access Bridge

To install Java Access Bridge:

  1. Download Java Access Bridge from the following URL:

    http://java.sun.com/javase/technologies/accessibility/accessbridge/
    
  2. Install Java Access Bridge.

  3. Copy the access-bridge.jar and jaccess-1_4.jar from your installation location to the jre\lib\ext directory.

  4. Copy the WindowsAccessBridge.dll, JavaAccessBridge.dll, and JAWTAccessBridge.dll files from your installation location to the jre\bin directory.

  5. Copy the accessibility.properties file to the jre\lib directory.

2.2.2 Configure RCU to Use Java Access Bridge

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:

  1. Display System in the Control Panel.

  2. Select the Advanced tab.

  3. Click the New button under the System Variable list. The New System Variable dialog appears.

  4. In the Variable Name field, enter ORACLE_OEM_CLASSPATH.

  5. In the Variable Value field, enter the full path to access-bridge.jar and jaccess-1_4.jar.

    Use a semicolon to separate the two paths. Do not use quotes or character spaces.

  6. Click OK.

2.3 Creating Schemas

RCU is used to create the various component schemas in an existing database.

2.3.1 Do all Schemas Have to Reside in the Same Database?

You can choose to create all the schemas in a single database or distribute them throughout multiple databases.

2.3.2 Are Multiple Versions of the Same Schema Supported?

You can use RCU to create multiple versions of each schema using custom prefixes (for example, you could have a test version of the Metadata Services schema called TEST_MDS and also a production or live version of the same schema called PROD_MDS on the same database).

2.3.3 What Happens When a Schema is Created?

The following sequence takes place when a schema is created with RCU:

  1. Prior to the schema being created, RCU performs global and component level prerequisite checks to ensure that certain minimum requirements are met.

  2. The schemas are created; the required tablespaces and data files are created.

  3. The schema_version_registry table is updated so that the schema type is mapped to the actual schema name (for example, Test_MDS might be mapped to the MDS Schema type).

  4. The scripts provided by the various component owners are invoked; these scripts perform the following:

    1. Create the user and grant the required roles.

    2. Run ALTER SESSION SET CURRENT SCHEMA to switch the schema to user context.

    3. Create the schema objects.

2.3.4 Creating Schemas

After successfully starting RCU (see Section 2.1, "Starting RCU"), follow the instructions in Table 2-1 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-1 How to Create Schemas

No. RCU Screen Instructions and Action Required

1

Welcome Screen

None.

2

Create Repository Screen

Select Create.

3

Database Connection Details Screen

Specify the connection details for your Oracle database.

4

Select Components Screen (for Create Operation)

Specify a schema prefix and select the components for which you want to create schemas in the database.

You must remember the prefix and schema names for the components you are installing; you will need this information during the configuration phase of Fusion Middleware product installation. It is recommended that you write these values down.

5

Schema Passwords Screen

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 Fusion Middleware product installation. It is recommended that you write these values down.

6

Map Tablespaces Screen

Configure the desired tablespace mapping for the schemas you want to create.

7

Summary Screen (for Create Operation)

Review the information on this screen, then click Create to begin schema creation.

8

Completion Summary Screen (for Create Operation)

Note the location of the log files, then click Close to dismiss the screen.


2.4 Dropping Schemas

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

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-2 How to Drop Schemas

No. Screen Instructions and Action Required

1

Welcome Screen

None.

2

Create Repository Screen

Select Drop.

3

Database Connection Details Screen

Specify the connection details for your database.

4

Select Components Screen (for Drop Operation)

Select the prefix and the schemas you want to drop.

5

Summary Screen (for Drop Operation)

Review the information on this screen, then click Drop to drop the schemas.

6

Completion Summary Screen (for Drop Operation)

Note the location of the log files, then click Close to dismiss the screen.


2.5 Using the Repository Creation Utility CLI

This section describes how to use the Repository Creation Utility's (RCU) command line interface (CLI). The CLI is necessary for integration with both the Oracle Fusion Middleware installer and Enterprise Manager during application deployment. Additionally, you can use the CLI in cases where Xserver is not configured or if you are using a telnet terminal that does not have proper display capabilities.

This section contains the following topics:

2.5.1 CLI Syntax and Parameters

The syntax for the RCU command line interface is:

rcu [-silent | -interactive] {<command> <options>}

Table 2-3 describes the various command line options.

Table 2-3 RCU Command Line Interface Options and Descriptions

Option Description

-silent or -interactive

Specify -silent if you want to run RCU with minimal interaction once you have entered the commend. You must specify all necessary command line parameters.

Specify -interactive if you want to run RCU and be prompted for each parameter.

command

One of the following:


2.5.2 RCU and Password Handling

If you use the -silent flag, RCU will prompt you for the database and schema passwords. If you use the -randomizePasswords parameter and “false” is passed as the value, then RCU will prompt for the schema passwords. If they are not entered, RCU will generate random passwords and use those.

2.5.3 Creating a Repository

The full syntax for the RCU command line interface to create a repository is shown below:

rcu [-silent | -interactive] -createRepository
   [-compInfoXMLLocation <location of ComponentInfo.xml file>]
   [-storageXMLLocation <location of Storage.xml file>]
   [-databaseType ORACLE]
   -connectString <database connect string (for example: host:port:service_id)>
   -dbUser <database username>
   [-dbRole <database role>]
   [-variables <comma separated variables in the format: variablename=value>]
   [-lockSchemas <true|false>]
   [-randomizePasswords <true|false>]
   [-schemaPrefix <schema prefix (optional for non-prefixable components)>]
   -component <component name>
]

Note:

When loading schemas, you must be aware of and specify all dependencies for the component you are loading. For example, the SOAINFRA schema depends on the MDS and ORASDPM schemas; if you try to load the SOAINFRA schema without specifying both the MDS and ORASDPM schemas, RCU will stop before any loading takes place.

In order to work properly, make sure that the parameters are specified in the same order that they are listed. For example, do not specify the -compInfoXMLLocation parameter before the -component parameter.

2.5.4 Dropping a Repository

The full syntax for the RCU command line interface to drop a repository is shown below:

rcu [-silent | -interactive] -dropRepository
   [-compInfoXMLLocation <location of ComponentInfo.xml file>]
   [-storageXMLLocation <location of Storage.xml file>]
   [-databaseType ORACLE]
   -connectString <database connect string (for example: host:port:service_id)>
   -dbUser <database username>
   [-dbRole <database role>]
   [-variables <comma separated variables in the format: variablename=value>]
   [-schemaPrefix <schema prefix (optional for non-prefixable components)>]
   -component <component name>

In order to work properly, make sure that the parameters are specified in the same order that they are listed. For example, do not specify the -compInfoXMLLocation parameter before the -component parameter.

2.5.5 RCU Environment Variables

Table 2-4 shows the variables picked up by RCU from the environment. If the environment variable is not set, then RCU uses the default value.

Table 2-4 RCU Environment Variables

Variable Default Description

RCU_LOG_LOCATION

ORACLE_HOME/rcu/log (UNIX)

ORACLE_HOME\rcu\log (Windows)

Location of the RCU log file.

RCU_TIMESTAMP_LOG_DIR

true

Determines whether or not a directory with the format logdir.yyyy-dd_hh-mm is created for the RCU log file.

Set this variable to true or false.

RCU_LOG_NAME

rcu.log

Name of the RCU log file.

RCU_LOG_LEVEL

ERROR

Determines the RCU log level.

Set this variable to one of SEVERE, ERROR, NOTIFICATION, or TRACE.