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:
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.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.
To install Java Access Bridge:
Download Java Access Bridge from the following URL:
http://java.sun.com/javase/technologies/accessibility/accessbridge/
Install Java Access Bridge.
Copy the access-bridge.jar and jaccess-1_4.jar from your installation location to the jre\lib\ext directory.
Copy the WindowsAccessBridge.dll, JavaAccessBridge.dll, and JAWTAccessBridge.dll files from your installation location to the jre\bin directory.
Copy the accessibility.properties file to the jre\lib directory.
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:
Display System in the Control Panel.
Select the Advanced tab.
Click the New button under the System Variable list. The New System Variable dialog appears.
In the Variable Name field, enter ORACLE_OEM_CLASSPATH.
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.
Click OK.
RCU is used to create the various component schemas in an existing database.
You can choose to create all the schemas in a single database or distribute them throughout multiple databases.
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).
The following sequence takes place when a schema is created with RCU:
Prior to the schema being created, RCU performs global and component level prerequisite checks to ensure that certain minimum requirements are met.
The schemas are created; the required tablespaces and data files are created.
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).
The scripts provided by the various component owners are invoked; these scripts perform the following:
Create the user and grant the required roles.
Run ALTER SESSION SET CURRENT SCHEMA to switch the schema to user context.
Create the schema objects.
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
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.
| No. | Screen | Instructions and Action Required |
|---|---|---|
|
1 |
None. |
|
|
2 |
Select Drop. |
|
|
3 |
Specify the connection details for your database. |
|
|
4 |
Select the prefix and the schemas you want to drop. |
|
|
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. |
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:
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 |
|---|---|
|
|
Specify Specify |
|
command |
One of the following:
|
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.
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, theSOAINFRA 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.
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.
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 |
|---|---|---|
|
|
|
Location of the RCU log file. |
|
|
|
Determines whether or not a directory with the format Set this variable to |
|
|
|
Name of the RCU log file. |
|
|
|
Determines the RCU log level. Set this variable to one of |