Creating Schemas with the Repository Creation Utility

Oracle

Fusion Middleware

12c (12.2.1)

E58101–01

October 2015

Documentation for database and system administrators that

describes how to create database schemas for Oracle Fusion

Middleware products.

Oracle Fusion Middleware Creating Schemas with the Repository Creation Utility, 12c (12.2.1)

E58101–01

Primary Author: Phil Stubbs

This software and related documentation are provided under a license agreement containing restrictions on

use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your

license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,

transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse

engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is

prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If

you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on

behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,

any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are

"commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-

specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the

programs, including any operating system, integrated software, any programs installed on the hardware,

and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.

No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications.

It is not developed or intended for use in any inherently dangerous applications, including applications that

may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you

shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its

safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this

software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of

their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are

used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron,

the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro

Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products,

and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly

disclaim all warranties of any kind with respect to third-party content, products, and services unless

otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates

will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party

content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

Preface............................................................................................................................................................... vii

Intended Audience ..................................................................................................................................... vii

Documentation Accessibility .................................................................................................................... vii

Related Documents..................................................................................................................................... vii

Conventions................................................................................................................................................. vii

What's New in This Guide.......................................................................................................................... ix

New and Changed Features for Release 12c (12.2.1) .............................................................................. ix

Other Significant Changes in this Document for Release 12c (12.2.1) ................................................. ix

1 Understanding Repository Creation Utility

1.1 Verifying RCU System and Database Requirements ................................................................. 1-1

1.1.1 RCU Supported Platforms .................................................................................................. 1-1

1.1.2 Finding a Certified Database .............................................................................................. 1-1

1.1.3 Database Requirements for RCU ....................................................................................... 1-1

1.1.4 Additional Requirements for IBM DB2 Databases.......................................................... 1-2

1.2 Preparing for Schema Creation...................................................................................................... 1-2

1.2.1 Understanding System Load and Product Load ............................................................. 1-3

1.2.2 Granting Permissions to Users for Querying System Load Objects ............................. 1-4

1.2.3 Understanding Custom Prefixes........................................................................................ 1-4

1.2.4 Understanding the Service Table Schema ........................................................................ 1-5

1.2.5 Planning Your Schema Creation ........................................................................................ 1-5

1.2.6 About Integrating Components Using Declarative XML............................................... 1-8

1.3 Using RCU with Java Access Bridge (Windows Only) .............................................................. 1-8

1.3.1 Install Java Access Bridge.................................................................................................... 1-8

1.3.2 Configure RCU to Use Java Access Bridge....................................................................... 1-9

2 Obtaining and Running Repository Creation Utility

2.1 Obtaining RCU................................................................................................................................. 2-1

2.2 Starting RCU..................................................................................................................................... 2-1

2.3 Creating Schemas............................................................................................................................. 2-2

iii

2.3.1 Creating Schemas as a User with Full SYS or SYSDBA Privileges ............................... 2-2

2.3.2 Creating Schemas as a User With Limited Database Privileges.................................... 2-4

2.3.3 Verifying Schema Version Numbers................................................................................. 2-6

2.4 Dropping Schemas........................................................................................................................... 2-7

2.4.1 About Dropping Shared Tablespaces................................................................................ 2-8

2.4.2 Dropping Schemas and Deleting Datafiles (Windows Only)........................................ 2-9

3 Running Repository Creation Utility from the Command Line

3.1 Command Line Syntax and Parameters....................................................................................... 3-1

3.1.1 RCU Modes Available from the Command Line ............................................................ 3-2

3.1.2 RCU Operations Available from the Command Line..................................................... 3-2

3.1.3 RCU Command Line Parameters....................................................................................... 3-3

3.2 Using the -silent Command ........................................................................................................... 3-7

3.2.1 Using a Wallet to Store Passwords .................................................................................... 3-8

3.3 Using the -interactive Command .................................................................................................. 3-9

3.4 Using Response Files..................................................................................................................... 3-11

3.4.1 Understanding Response Files ......................................................................................... 3-12

3.4.2 Creating a RCU Response File from the Graphical Interface....................................... 3-12

3.4.3 Creating a RCU Response File from the Command Line............................................. 3-12

3.4.4 Performing RCU Operations Using a Response File..................................................... 3-13

3.5 Creating a Repository from the Command Line....................................................................... 3-14

3.6 Generating a System Load Script From the Command Line................................................... 3-14

3.7 Loading Data Into the Repository From the Command Line ................................................. 3-15

3.8 Dropping a Repository from the Command Line..................................................................... 3-16

3.9 Generating a List of Components in an Oracle Home from the Command Line ................ 3-16

3.10 RCU Environment Variables...................................................................................................... 3-16

A Understanding Repository Creation Utility Screens

A.1 Welcome........................................................................................................................................... A-2

A.2 Create Repository ........................................................................................................................... A-3

A.2.1 Create Repository................................................................................................................ A-3

A.2.2 Drop Repository .................................................................................................................. A-4

A.3 Database Connection Details ........................................................................................................ A-5

A.3.1 Connection Credentials for Oracle Databases and Oracle Databases with Edition-

Based Redefinition...................................................................................................................... A-6

A.3.2 Connection Credentials for MySQL Databases .............................................................. A-7

A.3.3 Connection Credentials for Microsoft SQL Server Databases ...................................... A-7

A.3.4 Connection Credentials for IBM DB2 Databases............................................................ A-7

A.4 Select Components (for Create Operation)................................................................................. A-7

A.5 Select Components (for Drop Operation) ................................................................................. A-10

A.6 Schema Passwords ....................................................................................................................... A-11

A.7 Custom Variables.......................................................................................................................... A-12

A.7.1 Custom Variables for Oracle Data Integrator ............................................................... A-12

A.7.2 Custom Variables for Oracle SOA Suite ........................................................................ A-14

A.7.3 Custom Variable for Oracle WebCenter Portal Analytics........................................... A-15

A.8 Map Tablespaces........................................................................................................................... A-16

A.8.1 Default Tablespace Mappings ......................................................................................... A-17

A.8.2 Changing Default and Temporary Tablespaces ........................................................... A-17

A.8.3 Viewing and Changing Additional Tablespaces .......................................................... A-18

A.8.4 Managing Tablespaces and Datafiles ............................................................................. A-18

A.8.5 Encrypting Tablespaces.................................................................................................... A-20

A.9 Summary (for Create Operation) ............................................................................................... A-20

A.10 Summary (for Drop Operation)................................................................................................ A-22

A.11 Completion Summary (for Create Operation) ....................................................................... A-24

A.12 Completion Summary (for Drop Operation).......................................................................... A-25

B Understanding Repository Creation Utility Schemas, IDs, and Tablespaces

B.1 Repository Creation Utility Schemas, IDs, and Tablespaces .................................................... B-1

C Extending Repository Creation Utility to Configure Custom Application

Repositories

C.1 RCU Integration Options............................................................................................................... C-1

C.1.1 RCU JDBC Engine Compliant SQL*Plus Scripts ............................................................ C-1

C.1.2 Pure JDBC Scripts ................................................................................................................ C-2

C.1.3 SQL*Plus Scripts .................................................................................................................. C-2

C.1.4 External Processes ............................................................................................................... C-3

C.1.5 Java Code Using JavaAction .............................................................................................. C-3

C.2 RCU Configuration Files................................................................................................................ C-4

C.2.1 XML DTDs Defined by RCU.............................................................................................. C-4

C.2.2 Component Repository Configuration File ..................................................................... C-8

C.2.3 Component List Configuration File............................................................................... C-15

C.2.4 Soft-Prerequisite Support ................................................................................................ C-27

C.2.5 Default Tablespaces Configuration File ........................................................................ C-27

C.3 RCU Script Writing Guidelines ................................................................................................. C-28

C.3.1 Guidelines for RCU JDBC Engine Compliant SQL*Plus Scripts ............................... C-28

C.3.2 Guidelines for Pure JDBC Scripts................................................................................... C-29

C.3.3 Guidelines for SQL*Plus Scripts..................................................................................... C-29

C.3.4 Guidelines for SQL Server-Based Scripts...................................................................... C-29

D Troubleshooting Repository Creation Utility

D.1 General Troubleshooting Tips ...................................................................................................... D-1

D.2 RCU Log Files.................................................................................................................................. D-1

D.3 Need More Help?............................................................................................................................ D-3

Preface

The Creating Schemas with the Repository Creation Utility book contains overview

information and usage instructions for Oracle Repository Creation Utility (RCU).

Intended Audience

This guide is intended for users who are installing Oracle Fusion Middleware

products and are comfortable running some system administration operations, such as

creating users and groups, adding users to groups, and installing operating system

patches on the computer where Oracle Fusion Middleware products will be installed.

Users on UNIX systems need root access to run some scripts.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle

Accessibility Program website at http://www.oracle.com/pls/topic/lookup?

ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support

through My Oracle Support. For information, visit http://www.oracle.com/pls/

topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/

topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

For additional information, see the following manuals:

• Planning an Installation of Oracle Fusion Middleware

This document contains important information about planning and preparing for

Oracle Fusion Middleware product installations.

• Installing and Configuring the Oracle Fusion Middleware Infrastructure

The Repository Creation Utility is included with the Oracle Fusion Middleware

Infrastructure distribution.

Conventions

The following text conventions are used in this document:

vii

Convention Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or

terms defined in text or the glossary.

italic Italic type indicates book titles, emphasis, or placeholder variables for which you

supply particular values.

monospace Monospace type indicates commands within a paragraph, URLs, code in examples,

text that appears on the screen, or text that you enter.

viii

What's New in This Guide

The following topics introduce the new and changed features of the Repository

Creation Utility and other significant changes that are described in this guide, and

provide pointers to additional information. This document is the new edition of the

formerly titled Oracle Fusion Middleware Repository Creation Utility User's Guide.

New and Changed Features for Release 12c (12.2.1)

Repository Creation Utility 12c (12.2.1) includes the following new and changed

schema creation features.

• If Transparent Data Encryption (TDE) is enabled in an Oracle database, RCU

provides an option on the command line and in the graphical interface to create

encrypted tablespaces.

For more information, see Encrypting Tablespaces.

• In 12c (12.1.3), RCU used ORACLE_HOME/oracle_common/rcu/log/

logdir.date_timestamp/rcu.log as the default log location. In 12c (12.2.1),

log files are now written (by default) to the

RCUdate_timestamp_random_number\logs directory inside the temporary

directory on your system.

For more information, see RCU Log Files.

• RCU operations can be performed using a response file, which allows you to pass

all valid RCU command-line parameters to RCU via a text file.

For more information, see Using Response Files.

• A wallet can be used in silent mode to store and provide password credentials to

RCU rather than directly entering passwords on the command line.

For information on running RCU from the command line, see Using the -silent

Command.

• A silent RCU operation was introduced to generate a list of component IDs for a

given Oracle home.

For more information, see Generating a List of Components in an Oracle Home

from the Command Line.

Other Significant Changes in this Document for Release 12c (12.2.1)

For 12c (12.2.1), this guide has been updated in several ways. Following are the

sections that have been added or changed:

• Added a section to describe how to create encrypted tablespaces with RCU if TDE

(Transparent Data Encryption) is enabled in the database (Oracle or Oracle EBR).

See Encrypting Tablespaces.

• Added a section to describe how to generate and use a response file to perform a

RCU operation. See Using Response Files.

• Added a section to describe how to generate a list of component IDs for a given

Oracle home from the command line. See Generating a List of Components in an

Oracle Home from the Command Line.

• Modified the RCU default log location. For example, on UNIX operating systems,

the main RCU log (rcu.log) and component log files are now written to

the /tmp/RCUdate_timestamp_random_number/logs directory by default.

See RCU Log Files.

Understanding Repository Creation Utility

This chapter introduces you to the concepts and features you should be familiar with

before using the Repository Creation Utility (RCU).

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:

• Verifying RCU System and Database Requirements

• Preparing for Schema Creation

• Using RCU with Java Access Bridge (Windows Only)

1.1 Verifying RCU System and Database Requirements

This section contains links to important information about supported platforms for

RCU, certified databases, and database configuration information. Read this

information carefully before you obtain and run RCU.

• RCU Supported Platforms

• Finding a Certified Database

• Database Requirements for RCU

• Additional Requirements for IBM DB2 Databases

1.1.1 RCU Supported Platforms

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.

1.1.2 Finding a Certified Database

For a list of certified databases that can be used with RCU, refer to the certification

document for your release, located on the Oracle Fusion Middleware Supported System

Configurations page.

1.1.3 Database Requirements for RCU

Before you begin using RCU, review the "Repository Creation Utility (RCU)

Requirements" section in the Oracle Fusion Middleware System Requirements and

Specifications document.

Understanding Repository Creation Utility

1-1

This section contains important information about general and component-specific

database requirements that should be met before you run RCU.

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.

1.1.4 Additional Requirements for IBM DB2 Databases

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 root:

passwd -u dev_stb

passwd dev_stb

Refer to your system documentation for more information.

For more information about RCU prerequisites for IBM DB2 databases, refer to the

Oracle Fusion Middleware System Requirements and Specifications document.

1.2 Preparing for Schema Creation

This section contains important information and concepts regarding schema creation

and organization.

The following topics are covered:

• Understanding System Load and Product Load

• Granting Permissions to Users for Querying System Load Objects

• Understanding Custom Prefixes

• Understanding the Service Table Schema

• Planning Your Schema Creation

• About Integrating Components Using Declarative XML

Preparing for Schema Creation

1-2 Creating Schemas with the Repository Creation Utility

1.2.1 Understanding System Load and Product Load

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

schema_version_registry table.

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 can then run RCU again to

complete the schema creation by performing the product load phase.

Note:

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 schema_version_registry.

• Optional Post-Product Load Phase

This optional step is needed for components that must execute product load scripts

requiring DBA privileges.

This step is required for the following components:

– Audit Services (IAU)

Preparing for Schema Creation

Understanding Repository Creation Utility 1-3

– Oracle Enterprise Scheduler (ESS)

1.2.2 Granting Permissions to Users for Querying System Load Objects

If you want to give a user with limited privileges the ability to query the system load

objects, you must grant the user the following before they can query the system load:

Note:

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;

Note:

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;

1.2.3 Understanding Custom Prefixes

Schemas in your database can be grouped together using custom prefixes.

Note:

For important information regarding custom prefixes in IBM DB2 databases,

refer to "Size Limit for Schema Prefixes" in the Oracle Fusion Middleware System

Requirements and Specifications document.

The prefix is prepended to and separated from the schema name with an underscore

(_) character, as shown below:

prefix_schemaname

Prefixes:

• 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 default prefix used by RCU is DEV; if DEV has already been used, then RCU will

default to DEV1, then DEV2, and so on. Prefixes are used to create and organize logical

Preparing for Schema Creation

1-4 Creating Schemas with the Repository Creation Utility

groups of schemas. For example, you may want to create a test version of the

Metadata Services (schema name MDS) called TEST_MDS; then, when are ready for

your production version, you can create a second version of the schema called

PROD_MDS. Both TEST_MDS and 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, DEV_MDS2).

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

schema_version_registry.

1.2.4 Understanding the Service Table Schema

The Service Table schema is a special schema that is installed automatically whenever

RCU is run. 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 "Cross-Component Wiring" in Administering Oracle

Fusion Middleware.

1.2.5 Planning Your Schema Creation

This topic provides examples to help you understand how schemas can be grouped

together and distributed depending on your specific environment.

The following examples are provided:

• Organizing Schemas on a Single Database for a Single Domain

• Organizing Schemas on Multiple Databases for a Single Domain

• Organizing Schemas on a Single Database for Multiple Domains

• Organizing Schemas on Multiple Databases for Multiple Domains

1.2.5.1 Organizing Schemas on a Single Database for a Single Domain

Figure 1-1 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.

Preparing for Schema Creation

Understanding Repository Creation Utility 1-5

Figure 1-1 Schemas on a Single Database for a Single Domain

DBHOST

Database with schemas

APPHOST

WebLogic Domain

Cluster (infra_cluster_1)

Machine (infra_machine_1)

Managed Server

(infra_server_1)

Managed Server

(infra_server_2)

Infrastructure Infrastructure

Administration Server

Enterprise Manager

DEV_MDS

DEV_IAU

DEV_IAU_APPEND

DEV_IAU_VIEWER

DEV_OPSS

DEV_STB

1.2.5.2 Organizing Schemas on Multiple Databases for a Single Domain

Figure 1-2 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

DBHOST 1 DBHOST 2

DEV_MDS

DEV_IAU

DEV_IAU_APPEND

DEV_IAU_VIEWER

DEV_OPSS

DEV_UMS

DEV_WLS

DEV_STB

APPHOST

WebLogic Domain

Cluster (infra_cluster_1)

Machine (infra_machine_1)

Managed Server

(infra_server_1)

Managed Server

(infra_server_2)

Infrastructure Infrastructure

Administration Server

Enterprise Manager

Database with schemas Database with schemas

Note that the same schema prefix (in this case, DEV) can be used to group these related

schemas together, even across multiple databases.

1.2.5.3 Organizing Schemas on a Single Database for Multiple Domains

Figure 1-3 shows how schemas on a single database should be grouped for multiple

domains.

Preparing for Schema Creation

1-6 Creating Schemas with the Repository Creation Utility

Figure 1-3 Schemas on a Single Database for Multiple Domains

DBHOST

APPHOST

WebLogic Domain 1

Cluster (infra_cluster_1)

Machine (infra_machine_1)

Managed Server

(infra_server_1)

Managed Server

(infra_server_2)

Infrastructure Infrastructure

Administration Server

Enterprise Manager

Database with schemas

WebLogic Domain 2

Cluster (infra_cluster_2)

Machine (infra_machine_2)

Managed Server

(infra_server_1)

Managed Server

(infra_server_2)

Infrastructure Infrastructure

Administration Server

Enterprise Manager

DEV2_MDS

DEV2_IAU

DEV2_IAU_APPEND

DEV2_IAU_VIEWER

DEV2_OPSS

DEV2_STB

DEV1_MDS

DEV1_IAU

DEV1_IAU_APPEND

DEV1_IAU_VIEWER

DEV1_OPSS

DEV1_STB

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.

1.2.5.4 Organizing Schemas on Multiple Databases for Multiple Domains

Figure 1-4 shows one way to organize schemas on multiple databases for use with

multiple WebLogic domains.

Preparing for Schema Creation

Understanding Repository Creation Utility 1-7

Figure 1-4 Schemas on Multiple Databases for Multiple Domains

DBHOST 2DBHOST 1

APPHOST

WebLogic Domain 1

Cluster (infra_cluster_1)

Machine (infra_machine_1)

Managed Server

(infra_server_1)

Managed Server

(infra_server_2)

Infrastructure Infrastructure

Administration Server

Enterprise Manager

Database

with

schemas

WebLogic Domain 2

Cluster (infra_cluster_2)

Machine (infra_machine_2)

Managed Server

(infra_server_1)

Managed Server

(infra_server_2)

Infrastructure Infrastructure

Administration Server

Enterprise Manager

Database

with

schemas

DEV_MDS

DEV_IAU

DEV_IAU_APPEND

DEV_IAU_VIEWER

DEV_OPSS

DEV_STB

DEV_MDS

DEV_IAU

DEV_IAU_APPEND

DEV_IAU_VIEWER

DEV_OPSS

DEV_STB

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.

1.2.6 About Integrating Components Using Declarative XML

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.

1.3 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.

For more information, see the following topics:

• Install Java Access Bridge

• Configure RCU to Use Java Access Bridge

1.3.1 Install Java Access Bridge

To install Java Access Bridge:

Download Java Access Bridge from the following URL:

Using RCU with Java Access Bridge (Windows Only)

1-8 Creating Schemas with the Repository Creation Utility

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.

1.3.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:

Display System in the Control Panel.

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.

Using RCU with Java Access Bridge (Windows Only)

Understanding Repository Creation Utility 1-9

Using RCU with Java Access Bridge (Windows Only)

1-10 Creating Schemas with the Repository Creation Utility

Obtaining and Running Repository Creation

Utility

This chapter contains instructions for obtaining and running the Repository Creation

Utility (RCU).

This chapter contains the following sections:

• Obtaining RCU

• Starting RCU

• Creating Schemas

• Dropping Schemas

2.1 Obtaining RCU

In 12c (12.2.1), RCU is available with the Oracle Fusion Middleware Infrastructure

distribution. For information about how to install this software and obtain RCU, see

Installing and Configuring the Oracle Fusion Middleware Infrastructure.

2.2 Starting RCU

After Oracle Fusion Middleware Infrastructure is installed, start RCU from the

ORACLE_HOME/oracle_common/bin directory.

Note:

If you are running RCU 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 enter the following:

setenv LANG en_US.UTF8

setenv LC_ALL $LANG

setenv NLS_LANG american_america

It is generally a good practice to set the JAVA_HOME environment variable so

it references the location of the JDK software you will be using to run the

Repository Creation Utility (RCU). This ensures that RCU is using the proper

version of the JDK software.

On Linux operating systems:

Obtaining and Running Repository Creation Utility

2-1

cd ORACLE_HOME/oracle_common/bin

./rcu

On Windows operating systems:

cd ORACLE_HOME\oracle_common\bin

rcu.bat

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 Running Repository Creation Utility from the

Command Line.

2.3 Creating Schemas

This section contains the following topics:

• Creating Schemas as a User with Full SYS or SYSDBA Privileges

• Creating Schemas as a User With Limited Database Privileges

• Verifying Schema Version Numbers

2.3.1 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 the instructions in this topic 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 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.

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 you want to

create. See Additional Requirements for IBM DB2 Databases for more

information.

Click Next when you have specified your credentials. A separate dialog window

will appear while RCU checks connectivity and some database prerequisites.

When the database checking has passed without errors, click OK to dismiss the

dialog window and go to the next screen.

Creating Schemas

2-2 Creating Schemas with the Repository Creation Utility

Screen Description

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 will need this information during the configuration phase of your

product installation. Oracle recommends that you write these values down.

Schema Passwords 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 your product installation. Oracle

recommends that you write these values down.

Custom Variables Custom variables are required by some products for additional product

configuration information. This screen appears only if you selected Oracle Data

Integrator, SOA Suite, or WebCenter Portal — Analytics on the Select

Components screen. You can select Oracle Data Integrator, SOA Suite, or

WebCenter Portal — Analytics only if the Oracle home in which RCU was started

contains Oracle Data Integrator, Oracle SOA Suite, or Oracle WebCenter Portal,

respectively.

•

If Oracle Data Integrator is selected, the Custom Variables for Oracle Data

Integrator will be visible.

•

If SOA Suite is selected, the Custom Variables for Oracle SOA Suite will be

visible.

•

If WebCenter Portal - Analytics is selected, the Custom Variable for Oracle

WebCenter Portal Analytics will be visible.

•

If Oracle Data Integrator, SOA Suite, and WebCenter Portal - Analytics are

selected, the custom variables for Oracle Data Integrator, Oracle SOA Suite,

and Oracle WebCenter Portal Analytics will be visible on this screen.

Map Tablespaces

Use this screen to configure the desired tablespace mapping for the schemas you

want to create.

When you click Next, a separate dialog window will appear asking you to

confirm that you want to create these tablespaces. Click OK to proceed and

dismiss the dialog window.

A second dialog window will appear showing the progress of tablespace creation.

After this is complete, 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

Obtaining and Running Repository Creation Utility 2-3

2.3.2 Creating Schemas as a User With Limited Database Privileges

If you are a user without SYS or SYSDBA privileges, or you are unable to provide

valid authentication credentials for database access, follow the instructions in this

topic to create schemas.

Table 2-2 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 Understanding 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

will appear while RCU checks connectivity and some database prerequisites.

When the database checking has passed without errors, click OK to dismiss the

dialog window and go to the next screen.

NOTE: When performing system load and product load separately, RCU will not

verify that the database version you are using is supported and certified. For a list

of certified databases that can be used with RCU, refer to the certification

document for your release, located on the Oracle Fusion Middleware Supported

System Configurations page.

NOTE: Performing system load and product load separately is only supported on

Oracle or Oracle EBR databases.