Obtaining and Running Repository Creation Utility

2 Obtaining and Running Repository Creation Utility

Use these instructions to obtain and run the Repository Creation Utility (RCU) to create and drop schemas.

Obtaining RCU
The Repository Creation Utility is available with the Oracle Fusion Middleware Infrastructure distribution.
Starting RCU
After you install Oracle Fusion Middleware Infrastructure and create your Oracle home, you can start RCU from the ORACLE_HOME/oracle_common/bin directory.
Creating Schemas
Follow these instructions to create schemas in the database and verify that they are installed properly.
Creating Schemas for WebLogic Server on an ATP-S Database
Follow these instructions to create schemas for WebLogic Server on an Autonomous Transaction Processing-Shared database, and verify that they are installed properly.
Dropping Schemas
Follow these instructions to drop schemas from the database.

Obtaining RCU

The Repository Creation Utility is available with the Oracle Fusion Middleware Infrastructure distribution.

For information about how to install and obtain RCU, see Installing the Infrastructure Software in Installing and Configuring the Oracle Fusion Middleware Infrastructure.

Parent topic: Obtaining and Running Repository Creation Utility

Starting RCU

After you install Oracle Fusion Middleware Infrastructure and create your Oracle home, you can start RCU from the ORACLE_HOME/oracle_common/bin directory.

Note:

If you run the RCU by using a non-English database, you will need to set the following language environment variables: LANG, LC_ALL, and NLS_LANG. Use the environment commands that are appropriate for your environment.

For example, for UNIX operating systems running csh run the following:
```
setenv LANG en_US.UTF8
setenv LC_ALL $LANG
setenv NLS_LANG american_america
```
To start RCU, you do not need to set the JAVA_HOME environment variable. But, in case you want to use a specific JDK, ensure that the JAVA_HOME environment variable is set to the location of a certified JDK on your system.
For example, on UNIX operating systems, if your JDK is located in /home/Oracle/Java/:
```
setenv JAVA_HOME /home/Oracle/Java/jdk17.0.12
```
Be sure to replace the JDK location in this example with the actual JDK location on your system.

On Linux operating systems:

cd ORACLE_HOME/oracle_common/bin
./rcu

On Windows operating systems:

cd ORACLE_HOME\oracle_common\bin
rcu.bat

Note:

For Autonomous Transaction Processing-Shared database,Oracle Data Integrator supports only RCU silent mode for schema loading. For more information, see Starting the Repository Creation Utility (RCU).

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 about using the Command Line Interface (CLI), see Running Repository Creation Utility from the Command Line.

Parent topic: Obtaining and Running Repository Creation Utility

Creating Schemas

Follow these instructions to create schemas in the database and verify that they are installed properly.

Note:

The following sections are not applicable when you create schemas for Oracle GoldenGate products on Autonomous Transaction Processing database (both Autonomous Transaction Processing - Dedicated and Autonomous Transaction Processing-Shared) as you need to run RCU in silent mode for Oracle GoldenGate. See Run RCU for Oracle GoldenGate on ATP databases in silent mode.

To create schemas for WebLogic Server on an Autonomous Transaction Processing-Shared, see Creating Schemas for WebLogic Server on an ATP-S Database and Run RCU for Oracle WebLogic Server on ATP-S database in silent mode.

Creating Schemas as a User with Full SYS or SYSDBA Privileges
If you are a user with full SYS or SYSDBA privileges and are able to provide valid authentication credentials for database access, follow these instructions to create schemas.
Verifying Schema Version Numbers
When the schemas are created in your database, RCU creates and maintains a table called schema_version_registry. This table contains schema information such as version number, component name and ID, date of creation and modification, and custom prefix.
Creating Schemas as a User With Limited Database Privileges
If you are a user without SYS or SYSDBA privileges, follow these instructions to create schemas.

Parent topic: Obtaining and Running Repository Creation Utility

Creating Schemas as a User with Full SYS or SYSDBA Privileges

If you are a user with full SYS or SYSDBA privileges and are able to provide valid authentication credentials for database access, follow these instructions to create schemas.

Note:

The following schema creation steps are applicable for all components except Oracle Access Manager (OAM) and Oracle Internet Directory (OID). For OAM and OID, see Creating Schemas for Oracle Access Manager and Oracle Internet Directory As a User with Full SYS or SYSDBA Privileges.

Click the screen name to see detailed information for that screen. Unless otherwise noted, click Next to continue to the next screen.

Table 2-1 Schema Creation Steps for Full-Privilege Users

Screen	Description
Welcome	This screen introduces you to RCU.
Create Repository	Select Create Repository, then select System Load and Product Load. If you do not have full SYS or SYSDBA privileges on the database, select Prepare Scripts for System Load and follow the schema creation instructions in Creating Schemas as a User With Limited Database Privileges. For an Autonomous Transaction Processing database (both Autonomous Transaction Processing - Dedicated and Autonomous Transaction Processing-Shared), you must create schemas as a Normal user, and though, you do not have full SYS or SYSDBA privileges on the database, you must select System Load and Product Load.
Database Connection Details	Specify your database connection credentials. Remember that if you are creating schemas on an IBM DB2 database, you must have already created one operating system user for each schema that you want to create. Click Next when you have specified your credentials. A separate dialog window appears while RCU checks connectivity and the database prerequisites. When the database checking has passed without errors, click OK to dismiss the dialog window and go to the next screen. If you are creating schemas on an Autonomous Transaction Processing database (both Autonomous Transaction Processing - Dedicated and Autonomous Transaction Processing-Shared), you receive a warning message on selecting the database user role as `Normal`. You can ignore the warning and continue with the schema creation. For more information, see Troubleshooting Tips for Schema Creation on an Autonomous Transaction Processing Database.
Select Components (for Create Operation)	Select the components for which you want to create schemas, and specify a prefix to group them together. You must remember the prefix and schema names for the components you are installing; you need this information during the configuration phase of your product installation. Oracle recommends that you write down these values.
Schema Passwords	Specify the passwords for your schema owners. You must remember the passwords you enter on this screen; you need this information during the configuration phase of your product installation.
Custom Variables	Use the Custom Variables screen to specify additional product configuration information. The Custom Variables screen appears only if you selected one or more of the following components on the Select Components screen. You can select a component on the Select Components screen only if the Oracle home in which RCU was started contains that component.
Map Tablespaces	Use this screen to configure the desired tablespace mapping for the schemas that you want to create. When you click Next, a separate dialog window appears asking you to confirm that you want to create these tablespaces. Click OK to proceed and dismiss the dialog window. A second dialog window appears showing the progress of tablespace creation. After the tablespaces are created, click OK to dismiss this window and go to the next screen.
Summary (for Create Operation)	Verify the information on this screen, then click Create to begin schema creation.
Completion Summary (for Create Operation)	Review the information on this screen to verify that the operation was completed successfully. Click Close to complete the schema creation and dismiss RCU.

Creating Schemas for Oracle Access Manager and Oracle Internet Directory As a User with Full SYS or SYSDBA Privileges
If you are a user with full SYS or SYSDBA privileges and are able to provide valid authentication credentials for database access, follow these instructions to create schemas for Oracle Access Manager (OAM) and Oracle Internet Directory (OID).

Parent topic: Creating Schemas

Creating Schemas for Oracle Access Manager and Oracle Internet Directory As a User with Full SYS or SYSDBA Privileges

If you are a user with full SYS or SYSDBA privileges and are able to provide valid authentication credentials for database access, follow these instructions to create schemas for Oracle Access Manager (OAM) and Oracle Internet Directory (OID).

Note:

IDM schemas do not support EBR, so you must invoke RCU twice when creating schemas. When you invoke RCU the first time, select the Database type as Oracle Database enabled for edition-based redefinition and load the EBR-dependent components (STB, OPSS, IAU, IAU_Append, IAU_Viewer, and WLS). When you invoke RCU the second time, select Database type as Oracle Database and load IDM schemas

To create schemas for OAM and OID, perform the following steps:

Start RCU from the ORACLE_HOME/oracle_common/bin directory.
./rcu
Create schemas for Oracle Fusion Middleware components that support Edition-Based Redefinition (EBR) using Oracle Database enabled for edition-based redefinition database type. For schema creation steps, see Table 2-2.
Start RCU from the ORACLE_HOME/oracle_common/bin directory.
./rcu
Create schemas for Oracle Fusion Middleware components, OAM and OID that do not support Edition-Based Redefinition (EBR) using Oracle Database database type. For schema creation steps, see Table 2-3.

Table 2-2 describes the screens and the steps to be performed to create schemas for Oracle Fusion Middleware components that support EBR, for a user with full SYS or SYSDBA privileges.

Click the screen name to see detailed information for that screen. Unless otherwise noted, click Next to continue to the next screen.

Table 2-2 Creating Schemas As a User with Full Privileges for Components That Support EBR

Screen	Description
Welcome	This screen introduces you to RCU.
Create Repository	Select Create Repository, then select System Load and Product Load.
Database Connection Details	Select Oracle Database enabled for edition-based redefinition and then specify the other database connection credentials. Click Next when you have specified your credentials. A separate dialog window appears while RCU checks connectivity and the database prerequisites. When the database checking has passed without errors, click OK to dismiss the dialog window and go to the next screen.
Select Components (for Create Operation)	To create schemas, select only the components that support EBR, and specify a prefix to group the selected schemas together. For Oracle Access Manager, select the following dependent components that support EBR: Common Infrastructure Services Oracle Platform Security Services Audit Services Audit Services Append Audit Services Viewer Metadata Services WebLogic Services For Oracle Internet Directory, select the following dependent components that support EBR: Common Infrastructure Services Oracle Platform Security Services Audit Services Audit Services Append Audit Services Viewer WebLogic Services Note: The components, Oracle Access Manager (OAM) and Oracle Internet Directory (OID) do not support EBR. Hence, when you create schemas for OAM, do not select Oracle Access Manager, and when you create schemas for OID, do not select Oracle Internet Directory. You must remember the prefix and schema names for the components you are installing; you need this information during the configuration phase of your product installation. Oracle recommends that you write down these values.
Schema Passwords	Specify the passwords for your schema owners. You must remember the passwords you enter on this screen; you need this information during the configuration phase of your product installation.
Map Tablespaces	Use this screen to configure the desired tablespace mapping for the schemas that you want to create. When you click Next, a separate dialog window appears asking you to confirm that you want to create these tablespaces. Click OK to proceed and dismiss the dialog window. A second dialog window appears showing the progress of tablespace creation. After the tablespaces are created, click OK to dismiss this window and go to the next screen.
Summary (for Create Operation)	Verify the information on this screen, then click Create to begin schema creation.
Completion Summary (for Create Operation)	Review the information on this screen to verify that the operation was completed successfully. Click Close to complete the schema creation and dismiss RCU.

Table 2-3 describes the screens and the steps to be performed to create schemas for OAM and OID Oracle Fusion Middleware components, for a user with full SYS or SYSDBA privileges.

Table 2-3 Creating Schemas As a User with Full Privileges for OAM and OID Components

Screen	Description
Welcome	This screen introduces you to RCU.
Create Repository	Select Create Repository, then select System Load and Product Load.
Database Connection Details	Select Oracle Database and then specify the other database connection credentials. Click Next when you have specified your credentials. A separate dialog window appears while RCU checks connectivity and the database prerequisites. When the database checking has passed without errors, click OK to dismiss the dialog window and go to the next screen.
Select Components (for Create Operation)	Select Select Existing prefix and use the existing schema prefix you specified when you created schemas for components that support EBR. See Table 2-2. If you create schemas for OAM, select Oracle Access Manager, and if you create schemas for OID, select, Oracle Internet Directory. You must remember the prefix and schema names for the components you are installing; you need this information during the configuration phase of your product installation. Oracle recommends that you write down these values.
Schema Passwords	Specify the passwords for your schema owners. You must remember the passwords you enter on this screen; you need this information during the configuration phase of your product installation.
Map Tablespaces	Use this screen to configure the desired tablespace mapping for the OAM or OID schema that you want to create. When you click Next, a separate dialog window appears asking you to confirm that you want to create these tablespaces. Click OK to proceed and dismiss the dialog window. A second dialog window appears showing the progress of tablespace creation. After the tablespaces are created, click OK to dismiss this window and go to the next screen.
Summary (for Create Operation)	Verify the information on this screen, then click Create to begin schema creation.
Completion Summary (for Create Operation)	Review the information on this screen to verify that the operation was completed successfully. Click Close to complete the schema creation and dismiss RCU.

Parent topic: Creating Schemas as a User with Full SYS or SYSDBA Privileges

Verifying Schema Version Numbers

When the schemas are created in your database, RCU creates and maintains a table called schema_version_registry. This table contains schema information such as version number, component name and ID, date of creation and modification, and custom prefix.

To verify that the schemas are installed properly, run the following query after you sign in to SQL*Plus:

select comp_name, version from schema_version_registry;

The comp_name argument retrieves the name of the component, and version retrieves the version number. For example:

SQL> select comp_name, version from schema_version_registry;

COMP_NAME
--------------------------------------------------------------------------------
VERSION
------------------------------
Audit Service
14.1.2.0.0
 
Audit Service Append
14.1.2.0.0
 
Audit Service Viewer
14.1.2.0.0
 
 
COMP_NAME
--------------------------------------------------------------------------------
VERSION
------------------------------
Metadata Services
14.1.2.0.0
 
Oracle Platform Security Services
14.1.2.0.0
 
Service Table
14.1.2.0.0
 
 
COMP_NAME
--------------------------------------------------------------------------------
VERSION
------------------------------
 
WebLogic Services
14.1.2.0.0
 
 7 rows selected.

Parent topic: Creating Schemas

Creating Schemas as a User With Limited Database Privileges

If you are a user without SYS or SYSDBA privileges, follow these instructions to create schemas.

Note:

To create schemas in PDB using a user other than SYSDBA, RCU users need to create a common user and grant DBA to that common user, before running RCU. Local user with DBA privilege will not work correctly.

The following schema creation steps are applicable for all components except Oracle Access Manager (OAM). For OAM, see Creating Schemas for Oracle Access Manager as a User with Limited Database Privileges.

Table 2-4 Schema Creation Steps for Limited-Privilege Users

Screen	Description
Welcome	This screen introduces you to RCU.
Create Repository	Select Create Repository, then select Prepare Scripts for System Load. See About System Load and Product Load for more information about these operations.
Database Connection Details	Specify your database connection credentials. Click Next when you have specified your credentials. A separate dialog window appears while RCU checks connectivity and the database prerequisites. When the database checking has passed without errors, click OK to dismiss the dialog window and go to the next screen. Note: Performing system load and product load separately is only supported on Oracle and Oracle EBR databases.
Select Components (for Create Operation)	Select the components for which you want to create schemas, and specify a prefix to group them together. You must remember the prefix and schema names for the components you are installing; you need this information during the configuration phase of your product installation. Oracle recommends that you write down these values.
Custom Variables	Use the Custom Variables screen to specify additional product configuration information. The Custom Variables screen appears only if you selected one or more of the following components on the Select Components screen. You can select a component on the Select Components screen only if the Oracle home in which RCU was started contains that component.
Map Tablespaces	Use this screen to configure the desired tablespace mapping for the schemas that you want to create.
Summary (for Create Operation)	Verify the information on this screen, then click Generate to begin script generation. By default, the scripts are generated in the `RCUdate_timestamp_random_number/logs` directory inside the temporary directory on your system. For example, on UNIX operating systems, the scripts are generated in the `/tmp/RCUdate_timestamp_random_number/logs` directory, by default. If you want to specify a different location, click Browse and select a location on your system. The names of the scripts generated are `script_systemLoad.sql` and `script_postDataLoad.sql`.
Completion Summary (for Create Operation)	Review the information on this screen to verify that the operation was completed successfully. Click Close to complete the script generation and dismiss RCU.
N/A	After the scripts are created, user with SYS or SYSDBA privileges must execute the `script_systemLoad.sql` script: Sign in to SQL*Plus. Enter the following command to execute the `script_systemLoad.sql` script (replace the path to the script if you chose to save it in a custom location): @/tmp/RCUdate_timestamp_random_number/logs/script_systemLoad.sql While the script is running, the user is prompted to set the schema password for each schema being created. Specify the passwords as prompted. You are returned to your system prompt when the script has been executed.
N/A	After the script is executed, start RCU again and perform the product load phase to complete schema creation.
Welcome	This screen introduces you to RCU.
Create Repository	Select Create Repository, then select Perform Product Load. See About System Load and Product Load for more information about these operations.
Database Connection Details	Specify your database connection credentials. Click Next when you have specified your credentials. A separate dialog window appears while RCU checks connectivity and the database prerequisites. When the database checking has passed without errors, click OK to dismiss the dialog window and go to the next screen.
Select Components (for Create Operation)	From the drop-down list, select the prefix you specified earlier in this procedure. Then, select the components for which you want to perform the product load.
Schema Passwords	Specify the passwords for your schema owners. Ensure to specify the same passwords that were entered while running the `script_systemLoad.sql` script through SQL*Plus. You must remember the passwords you enter on this screen; you need this information during the configuration phase of your product installation.
Custom Variables	Use the Custom Variables screen to specify additional product configuration information. The Custom Variables screen appears only if you selected one or more of the following components on the Select Components screen. You can select a component on the Select Components screen only if the Oracle home in which RCU was started contains that component.
Summary (for Create Operation)	Verify the information on this screen, then click Data Load to begin schema creation.
Completion Summary (for Create Operation)	Review the information on this screen to verify that the operation was completed successfully. Click Close to complete the schema creation and dismiss RCU.
N/A	This optional step is needed for components that generate and must execute product load scripts requiring DBA privileges. After the product load phase is complete, someone with SYS or SYSDBA privileges must execute the `script_postDataLoad.sql` script. This step is needed for the Audit Services (`IAU`) and Oracle Enterprise Scheduler (`ESS`) components. Sign in to SQL*Plus. Enter the following command to execute the `script_postDataLoad.sql` script (replace the path to the script if you chose to save it in a custom location): @/tmp/RCUdate_timestamp_random_number/logs/script_postDataLoad.sql You are returned to your system prompt when the script has been executed.

Creating Schemas for Oracle Access Manager as a User with Limited Database Privileges
If you are a user without SYS or SYSDBA privileges, follow these instructions to create schemas for Oracle Access Manager (OAM).

Parent topic: Creating Schemas

Creating Schemas for Oracle Access Manager as a User with Limited Database Privileges

If you are a user without SYS or SYSDBA privileges, follow these instructions to create schemas for Oracle Access Manager (OAM).

Note:

To create schemas in PDB using a user other than SYSDBA, RCU users need to create a common user without DBA privileges, before running RCU.

To create schemas for OAM, perform the following steps:

Grant the following permissions to the user before querying the system load objects:
```
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;
```
Note:
When you execute the last command, you may encounter the Table or view does not exist error message. You may ignore this message.
Start RCU from the ORACLE_HOME/oracle_common/bin directory.
./rcu
Using Prepare Scripts for System Load, create schemas for Oracle Fusion Middleware components that support Edition-Based Redefinition (EBR) using Oracle Database enabled for edition-based redefinition database type. For schema creation steps, see Table 2-5.
Start RCU from the ORACLE_HOME/oracle_common/bin directory.
./rcu
Using Prepare Scripts for System Load, create schemas for OAM component that does not support Edition-Based Redefinition (EBR) using Oracle Database database type and with a schema prefix, which is different than the schema prefix you used for components that support Edition-Based Redefinition (EBR). For schema creation steps, see Table 2-6.
After the scripts are created, a user with SYS or SYSDBA privileges must run the script_systemLoad.sql scripts generated from step 3 and step 5 as follows:
1. Sign in to SQL*Plus.
2. Enter the following command to run the script_systemLoad.sql script (replace the path to the script if you chose to save it in a custom location):
```
@/tmp/RCUdate_timestamp_random_number/logs/script_systemLoad.sql
```
3. While the script is running, the user is prompted to set the schema password for each schema being created. Specify the passwords as prompted.
  You are returned to your system prompt when the script execution is complete.
While running with SYS or SYSDBA privileges, grant the following permissions to the user before performing the product load:
```
grant REGISTRYACCESS to user;
grant STBROLE to user;
```
Start RCU from the ORACLE_HOME/oracle_common/bin directory.
./rcu
Using Perform Product Load, create schemas for Oracle Fusion Middleware components that support EBR using Oracle Database enabled for edition-based redefinition database type and with the same prefix you used when you created schemas for these Oracle Fusion Middleware components in step 3. For schema creation steps, see Table 2-7.
Start RCU from the ORACLE_HOME/oracle_common/bin directory.
./rcu
Using Perform Product Load, create schemas for OAM using Oracle Database database type and with the same schema prefix that you used when you created schemas for OAM in step 5. For schema creation steps, see Table 2-8.
After the product load phase is complete, user with SYS or SYSDBA privileges must run the script_postDataLoad.sql generated from step 3 and step 5 as follows:
1. Sign in to SQL*Plus.
2. Enter the following command to run the script_postDataLoad.sql script (replace the path to the script if you chose to save it in a custom location):
```
@/tmp/RCUdate_timestamp_random_number/logs/script_postDataLoad.sql
```
  You are returned to your system prompt when the script execution is complete.

Table 2-5 describes the screens and the steps to be performed to create schemas for Oracle Fusion Middleware components that support EBR, for a user with limited database privileges.

Table 2-5 Creating Schemas As a User with Limited-Privileges for Components That Support EBR

Screen	Description
Welcome	This screen introduces you to RCU.
Create Repository	Select Create Repository, then select Prepare Scripts for System Load. See About System Load and Product Load for more information about these operations.
Database Connection Details	Select Oracle Database enabled for edition-based redefinition and then specify the other database connection credentials. Click Next when you have specified your credentials. A separate dialog window appears while RCU checks connectivity and the database prerequisites. When the database checking has passed without errors, click OK to dismiss the dialog window and go to the next screen.
Select Components (for Create Operation)	To create schemas, select only the following components that support EBR: Common Infrastructure Services, Oracle Platform Security Services, Audit Services, Audit Services Append, Audit Services Viewer, Metadata Services, and WebLogic Services, and then specify a prefix to group the selected schemas together. Note:The Oracle Access Manager (OAM) component does not support EBR. Hence, when you create schemas for OAM, do not select Oracle Access Manager. You must remember the prefix and schema names for the components you are installing; you need this information during the configuration phase of your product installation. Oracle recommends that you write down these values.
Map Tablespaces	Use this screen to configure the desired tablespace mapping for the schemas that you want to create.
Summary (for Create Operation)	Verify the information on this screen, then click Generate to begin script generation. By default, the scripts are generated in the `RCUdate_timestamp_random_number/logs` directory inside the temporary directory on your system. For example, on UNIX operating systems, the scripts are generated in the `/tmp/RCUdate_timestamp_random_number/logs` directory, by default. If you want to specify a different location, click Browse and select a location on your system. The names of the scripts generated are `script_systemLoad.sql` and `script_postDataLoad.sql`.
Completion Summary (for Create Operation)	Review the information on this screen to verify that the operation was completed successfully. Click Close to complete the script generation and dismiss RCU.

Table 2-6 describes the screens and the steps to be performed to create schemas for OAM component, for a user with limited database privileges.

Table 2-6 Creating Schemas As a User with Limited-Privileges for OAM

Screen	Description
Welcome	This screen introduces you to RCU.
Create Repository	Select Create Repository, then select Prepare Scripts for System Load. See About System Load and Product Load for more information about these operations.
Database Connection Details	Select Oracle Database and then specify the other database connection credentials. Click Next when you have specified your credentials. A separate dialog window appears while RCU checks connectivity and the database prerequisites. When the database checking has passed without errors, click OK to dismiss the dialog window and go to the next screen.
Select Components (for Create Operation)	Select Create new prefix and specify a prefix name different than the prefix name you specified when you created schemas for components that support EBR. To create schemas for OAM, select Oracle Access Manager, and the dependent mandatory components, Common Infrastructure Services and WebLogic Services. You must remember the prefix and schema names for the components you are installing; you need this information during the configuration phase of your product installation. Oracle recommends that you write down these values.
Map Tablespaces	Use this screen to configure the desired tablespace mapping for the schemas that you want to create.
Summary (for Create Operation)	Verify the information on this screen, then click Generate to begin script generation. By default, the scripts are generated in the `RCUdate_timestamp_random_number/logs` directory inside the temporary directory on your system. For example, on UNIX operating systems, the scripts are generated in the `/tmp/RCUdate_timestamp_random_number/logs` directory, by default. If you want to specify a different location, click Browse and select a location on your system. The names of the scripts generated are `script_systemLoad.sql` and `script_postDataLoad.sql`.
Completion Summary (for Create Operation)	Review the information on this screen to verify that the operation was completed successfully. Click Close to complete the script generation and dismiss RCU.

Table 2-7 describes the screens and the steps to be performed to create schemas for Oracle Fusion Middleware components that support EBR with the same schema prefix in Table 2-5, for a user with limited database privileges.

Table 2-7 Creating Schemas As a User with Limited-Privileges for Components That Support EBR with the Same Schema Prefix Used for EBR-Compatible Components

Screen	Description
Welcome	This screen introduces you to RCU.
Create Repository	Select Create Repository, then select Perform Product Load. See About System Load and Product Load for more information about these operations.
Database Connection Details	Select Oracle Database enabled for edition-based redefinition and then specify the other database connection credentials. Click Next when you have specified your credentials. A separate dialog window appears while RCU checks connectivity and the database prerequisites. When the database checking has passed without errors, click OK to dismiss the dialog window and go to the next screen.
Select Components (for Create Operation)	Select Select Existing prefix and use the existing schema prefix you specified when you created schemas for components that support EBR. See Table 2-5. To create schemas, select only the following components that support EBR: Common Infrastructure Services, Oracle Platform Security Services, Audit Services, Audit Services Append, Audit Services Viewer, Metadata Services, and WebLogic Services. Note:The Oracle Access Manager (OAM) component does not support EBR. Hence, when you create schemas for OAM, do not select Oracle Access Manager. You must remember the prefix and schema names for the components you are installing; you need this information during the configuration phase of your product installation. Oracle recommends that you write down these values.
Schema Passwords	Specify the passwords for your schema owners. Ensure to specify the same passwords that were entered while running the `script_systemLoad.sql` script through SQL*Plus. You must remember the passwords you enter on this screen; you need this information during the configuration phase of your product installation.
Summary (for Create Operation)	Verify the information on this screen, then click Data Load to begin schema creation.
Completion Summary (for Create Operation)	Review the information on this screen to verify that the operation was completed successfully. Click Close to complete the script generation and dismiss RCU.

Table 2-8 describes the screens and the steps to be performed to create schemas for OAM component with the same prefix in Table 2-6, for a user with limited database privileges.

Table 2-8 Creating Schemas As a User with Limited-Privileges for OAM Component with the Same Schema Prefix Used for OAM

Screen	Description
Welcome	This screen introduces you to RCU.
Create Repository	Select Create Repository, then select Perform Product Load. See About System Load and Product Load for more information about these operations.
Database Connection Details	Select Oracle Database and then specify the other database connection credentials. Click Next when you have specified your credentials. A separate dialog window appears while RCU checks connectivity and the database prerequisites. When the database checking has passed without errors, click OK to dismiss the dialog window and go to the next screen.
Select Components (for Create Operation)	Select Select Existing prefix and use the existing schema prefix you specified when you created schemas for OAM component. See Table 2-6. To create schemas for OAM, select Oracle Access Manager, and the dependent mandatory components, Common Infrastructure Services and WebLogic Services.
Schema Passwords	Specify the passwords for your schema owners. Ensure to specify the same passwords that were entered while running the `script_systemLoad.sql` script through SQL*Plus. You must remember the passwords you enter on this screen; you need this information during the configuration phase of your product installation.
Summary (for Create Operation)	Verify the information on this screen, then click Data Load to begin schema creation.
Completion Summary (for Create Operation)	Review the information on this screen to verify that the operation was completed successfully. Click Close to complete the script generation and dismiss RCU.

Parent topic: Creating Schemas as a User With Limited Database Privileges

Creating Schemas for WebLogic Server on an ATP-S Database

Follow these instructions to create schemas for WebLogic Server on an Autonomous Transaction Processing-Shared database, and verify that they are installed properly.

Ensure that you have completed the prerequisites for schema creation. See Settings to connect to an Autonomous Transaction Processing Database.

To create schemas for WebLogic server on an Autonomous Transaction Processing-Shared database in silent mode, see Run RCU for Oracle WebLogic Server on ATP-S database in silent mode.

Creating Schemas as a User with Full Database Privileges
If you are a user with full database privileges and are able to provide valid authentication credentials for database access, follow these instructions to create schemas.
Creating Schemas as a User With Limited Database Privileges
If you are a user without full database privileges, follow these instructions to create schemas.
Verifying Schema Version Numbers
When the schemas are created in your database, RCU creates and maintains a table called schema_version_registry. This table contains schema information such as version number, component name and ID, date of creation and modification, and custom prefix.

Parent topic: Obtaining and Running Repository Creation Utility

Creating Schemas as a User with Full Database Privileges

If you are a user with full database privileges and are able to provide valid authentication credentials for database access, follow these instructions to create schemas.

Click the screen name to see detailed information for that screen. Unless otherwise noted, click Next to continue to the next screen.

Table 2-9 Schema Creation Steps for Full-Privilege Users

Screen	Description
Welcome	This screen introduces you to RCU.
Create Repository	Select Create Repository, then select System Load and Product Load.
Database Connection Details	Specify your database connection credentials using the Connection String format only. See Settings to connect to an Autonomous Transaction Processing Database. After you have specified your credentials, click Next. The user privileges warning is displayed. You can ignore the warning and continue with the schema creation. For more information, see Troubleshooting Tips for Schema Creation on an Autonomous Transaction Processing Database.
Select Components (for Create Operation)	Select the components for which you want to create schemas, and specify a prefix to group them together. You must remember the prefix and schema names for the components you are installing; you need this information during the configuration phase of your product installation. Oracle recommends that you write down these values.
Schema Passwords	Specify the passwords for your schema owners. You must remember the passwords you enter on this screen; you need this information during the configuration phase of your product installation.
Map Tablespaces	Use this screen to configure the desired tablespace mapping for the schemas that you want to create. Note: If you created the schemas using an existing prefix. override the default and temporary tablespaces by selecting DATA from the drop-down list in the `Default Tablespace` column, and TEMP from the drop-down list in the `Temp Tablespace` column. In case of additional tablespaces, override the tablespace name by selecting DATA from the drop-down list in the `Tablespace Name` column. When you click Next, the user privileges warning is displayed. You can ignore the warning and continue with the schema creation. For more information, see Troubleshooting Tips for Schema Creation on an Autonomous Transaction Processing Database. On the confirmation window, click OK to confirm that you want to create these tablespaces. You can view progress of tablespace creation. After the tablespaces are created, click Next to go to the next screen.
Summary (for Create Operation)	Verify the information on this screen, then click Create to begin schema creation.
Completion Summary (for Create Operation)	Review the information on this screen to verify that the operation was completed successfully. Click Close to complete the schema creation and dismiss RCU.

Parent topic: Creating Schemas for WebLogic Server on an ATP-S Database

Creating Schemas as a User With Limited Database Privileges

If you are a user without full database privileges, follow these instructions to create schemas.

To create schemas, a user with limited database privileges needs to follow the steps in Create Repository in Creating Schemas as a User with Full Database Privileges

Note:

To create schemas in PDB using a user other than a user with full database privileges, Repository Creation Utility (RCU) users need to create a common user and grant DBA to that common user, before running RCU. Local user with DBA privilege will not work correctly.

Parent topic: Creating Schemas for WebLogic Server on an ATP-S Database

Verifying Schema Version Numbers

To verify that the schemas are installed properly, run the following query after you sign in to SQL*Plus:

select comp_name, version from schema_version_registry;

The comp_name argument retrieves the name of the component, and version retrieves the version number. For example:

SQL> select comp_name, version from schema_version_registry;

COMP_NAME
--------------------------------------------------------------------------------
VERSION
------------------------------
Audit Service
14.1.2.0.0
 
Audit Service Append
14.1.2.0.0
 
Audit Service Viewer
14.1.2.0.0
 
 
COMP_NAME
--------------------------------------------------------------------------------
VERSION
------------------------------
Metadata Services
14.1.2.0.0
 
Oracle Platform Security Services
14.1.2.0.0
 
Service Table
14.1.2.0.0
 
 
COMP_NAME
--------------------------------------------------------------------------------
VERSION
------------------------------
 
WebLogic Services
14.1.2.0.0
 
 7 rows selected.

Parent topic: Creating Schemas for WebLogic Server on an ATP-S Database

Dropping Schemas

Follow these instructions to drop schemas from the database.

To see detailed information for a particular screen, click on the screen name. Unless otherwise noted, click Next to continue to the next screen.

Table 2-10 RCU Screens and Description for Dropping Schemas

Screen	Instructions and Action Required
Welcome	This screen introduces you to RCU.
Create Repository	Select Drop Repository.
Database Connection Details	Specify your database connection credentials. Click Next when you have specified your credentials. A separate dialog window appears while RCU checks connectivity and the database prerequisites. When the database checking has passed without errors, click OK to dismiss the dialog window and go to the next screen.
Select Components (for Drop Operation)	Select the prefix and the schemas that you want to drop, then click Next. A separate dialog window appears asking you to verify that you want to drop the selected schemas. Click OK to dismiss this window. A second dialog window appears while RCU checks the prerequisites for the schemas that you are dropping. After prerequisite checking is complete, click OK to dismiss this window and go to the next screen.
Custom Variables	The Custom Variables screen appears only if you selected one or more of the following components on the Select Components screen. You can select a component on the Select Components screen only if the Oracle home in which RCU was started contains that component.
Summary (for Drop Operation)	Review the information on this screen, then click Drop to drop the schemas.
Completion Summary (for Drop Operation)	Note the location of the log files, then click Close to dismiss the screen.

About Dropping Shared Tablespaces
Tablespaces that are shared among multiple schemas are not dropped.
Dropping Schemas and Deleting Datafiles (Windows Only)
If you used RCU to drop a schema from a Windows-based database, and you want to recreate the dropped schema, you will have to manually delete the datafiles that were not automatically removed when the schema was dropped.

Parent topic: Obtaining and Running Repository Creation Utility

About Dropping Shared Tablespaces

Tablespaces that are shared among multiple schemas are not dropped.

For example, if you created both the Audit Services (for example, DEV_IAU) and Metadata Services (for example, DEV_MDS) schemas, both schemas would use the temporary tablespace DEV_IAS_TEMP (see Default Tablespace Mappings).

If you then drop the DEV_IAU schema, the DEV_IAS_TEMP tablespace would not be dropped since it is also used by the DEV_MDS schema.

Parent topic: Dropping Schemas

Dropping Schemas and Deleting Datafiles (Windows Only)

If you used RCU to drop a schema from a Windows-based database, and you want to recreate the dropped schema, you will have to manually delete the datafiles that were not automatically removed when the schema was dropped.

Change to the DB_HOME\oradata directory and manually delete any remaining datafiles before you recreate the schema.

Oracle recommends that you check this directory for any remaining datafiles before you attempt to recreate any dropped schema.

Parent topic: Dropping Schemas