Creating Schemas with the Repository Creation Utility

Oracle® Fusion Middleware

Creating Schemas with the Repository

Creation Utility

12c (12.2.1.4.0)

E95101-16

October 2023

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

E95101-16

Primary Author: Oracle Corporation

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, software documentation, data (as defined in the Federal Acquisition Regulation), 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 embedded, installed, or activated on delivered hardware, and modifications of such programs)

and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end

users are "commercial computer software," "commercial computer software documentation," or "limited rights

data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental

regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation

of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated

software, any programs embedded, installed, or activated on delivered hardware, and modifications of such

programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and

limitations specified in the license contained in the applicable contract. The terms governing the U.S.

Government's use of Oracle cloud services are defined by the applicable contract for such services. 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®, Java, and MySQL are registered trademarks of Oracle and/or its affiliates. Other names may be

trademarks of their respective owners.

Intel and Intel Inside 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, Epyc,

and the AMD 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

Intended Audience vii

Documentation Accessibility vii

Diversity and Inclusion vii

Related Documents

For additional information, see the following resources:

• Preparing for an Oracle Fusion Middleware Installation in Planning an Installation

of Oracle Fusion Middleware

This document contains important information about planning and preparing for

Oracle Fusion Middleware product installations.

• Installing the Infrastructure Software in 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:

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.

Preface

viii

About the Repository Creation Utility

Many of the Oracle Fusion Middleware components require the existence of schemas in a

database before configuration. These schemas are created and loaded in your database by

using the Repository Creation Utility (RCU).

The following topics introduce you to the concepts and features that you should be familiar

with before you use RCU:

• Verifying RCU System and Database Requirements

Use the certification and system requirements documents to find important information

about supported platforms for RCU, certified databases, and database configuration

information.

• Preparing for Schema Creation

Before you create your schemas, ensure that you understand the concepts regarding

schema creation and organization.

• Prerequisites for Schema Creation on an Autonomous Transaction Processing Database

Before you create schemas on an Autonomous Transaction Processing database (both

Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous

Transaction Processing-Shared (ATP-S)), you must modify the wallet settings and set the

environment variables, and apply patches on

ORACLE HOME

• Using RCU with Java Access Bridge (Windows Only)

Java Access Bridge enables assistive technologies, such as JAWS screen reader, to

read Java applications that run on the Windows platform.

Verifying RCU System and Database Requirements

Use the certification and system requirements documents to find important information about

supported platforms for RCU, certified databases, and database configuration information.

Read this information carefully before you obtain and run RCU.

• RCU Supported Platforms

Use the system requirements document to review the supported platforms on which you

can run RCU.

• Finding a Certified Database

If you do not have a database where you can install schemas, you must install and

configure a certified database.

• Database Requirements for RCU

Ensure to review the general and component-specific database requirements that must

be met before you run RCU.

• Additional Requirements for IBM DB2 Databases

If you are creating component schemas on an IBM DB2 database, there are additional

requirements to consider.

1-1

RCU Supported Platforms

Use the system requirements document to review the supported platforms on which

you can run RCU.

To know the platforms on which you can run RCU, see Oracle Fusion Middleware

System Requirements and Specifications document.

Finding a Certified Database

If you do not have a database where you can install schemas, you must install and

configure a certified database.

For a list of certified databases that can be used with RCU, see System Requirements

and Supported Platforms for Oracle Fusion Middleware 12c certification document for

your release, located on the Oracle Fusion Middleware Supported System

Configurations page.

Database Requirements for RCU

Ensure to review the general and component-specific database requirements that

must be met before you run RCU.

Not all schemas are supported on all databases. So, before you begin using RCU, see

the System Requirements and Supported Platforms for Oracle Fusion Middleware 12c

document in Oracle Fusion Middleware Supported System Configurations page. In the

certification information, you can see that MySQL database is supported for Oracle

Data Integrator and Oracle GoldenGate Studio Fusion Middleware components only.

Make sure you have read the information in this section carefully so that you configure

a certified database that supports the schemas that you need for your Fusion

Middleware components.

Additional Requirements for IBM DB2 Databases

If you are creating component schemas on an IBM DB2 database, there are additional

requirements to consider.

In addition to the typical space and configuration database requirements, IBM DB2

databases also have the following special requirements:

• On IBM DB2 databases running on Linux operating systems, there is a limitation

with regards to the length of the schema names.

• Create one database operating system user 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

Chapter 1

Verifying RCU System and Database Requirements

1-2

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.

• Create operating system level users in IBM DB2 for required schemas before you run the

RCU.

For example:

Audit Services – <prefix>_iau, <prefix>_iau_a (Audit Services Append), and

<prefix>_iau_v (Audit Services Viewer).

Service Table — <prefix>_stb

WebLogic Services - <prefix>_wls

• On IBM DB2/AIX, before you run the RCU or Upgrade Assistant Tool, you must ensure

that the auxiliary schemas are available for the following components:

WebLogic Services – <prefix>_wlsr

Preparing for Schema Creation

Before you create your schemas, ensure that you understand the concepts regarding schema

creation and organization.

• About 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.

• 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 certain permissions before they can query the system

load.

• About Custom Prefixes

Use custom prefixes to organize and group schemas in your database.

• About the Service Table Schema

The Service Table schema is a special schema that is automatically created once per

prefix. The service table stores basic schema configuration information (for example,

schema prefixes and passwords) that can then be accessed and used by other Oracle

Fusion Middleware components during domain creation.

• Planning Your Schema Creation

Before you run RCU, make sure that you understand how schemas can be grouped

together and distributed depending on your specific environment.

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

Chapter 1

Preparing for Schema Creation

1-3

About 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 creates the necessary tablespaces and

schemas. If it is not already present, RCU also creates the

schema_version_registry

. One entry for each component is created in

schema_version_registry

, and the entry will have the appropriate access and

status set to LOADED in the

schema_version_registry

table.

User with SYS or SYSDBA privileges must perform these actions; 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 the Prepare Scripts

for System Load on the Create Repository screen. This option generates a SQL

script that contains the same SQL statements and blocks that would have been

called if RCU were to execute the actions for the selected components. After the

script is generated, a user with the necessary SYS or SYSDBA privileges can

execute the script to complete the system load phase.

After the system load phase is complete, any user with the privileges described in

Granting Permissions to Users for Querying System Load Objects can then run

RCU again to complete the schema creation by performing the product load

phase.

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 creates procedures, functions, tables,

indexes, and other objects within schemas and runs 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, status is changed to VALID, if there is no

post -product load for that component.

• Optional Post-Product Load Phase

Chapter 1

Preparing for Schema Creation

1-4

This step is only needed for components that generate the

script_postDataLoad.sql

script that requires DBA privileges during the system load phase. After the product load

phase is complete, someone with SYS or SYSDBA privileges should execute the

script_postDataLoad.sql

script.

This step is required for the following components:

– Audit Services (

IAU

)

– Oracle Enterprise Scheduler (

ESS

)

Note:

The Repository Creation Utility fails to load schemas for

SOAINFRA

when you run

schemas on an Oracle hardened database. See SOAINFRA Schema Creation Fails

on a Hardened Database.

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 certain permissions 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 ignored.

After you perform the system load, grant the following permission to the same user in order

for them to perform data load:

grant REGISTRYACCESS to user;

grant STBROLE to user;

About Custom Prefixes

Use custom prefixes to organize and group schemas in your database.

Chapter 1

Preparing for Schema Creation

1-5

Note:

For important information regarding custom prefixes in IBM DB2 databases,

see Additional Requirements for IBM DB2 Databases.

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

(_) character, as shown below:

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.

Note:

The total length of the prefixed schema name (your custom prefix plus

the component schema name) must not be longer than 30 characters.

The default prefix used by RCU is

DEV

; if

DEV

has already been used, then RCU

defaults to

DEV1

, then

DEV2

, and so on. Prefixes are used to create and organize

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

Metadata Services (schema name

MDS

) called

TEST_MDS

; then, when you 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 have a version of the Metadata Services schema called

DEV_MDS

, then

you cannot 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

About the Service Table Schema

The Service Table schema is a special schema that is automatically created once per

prefix. The service table stores basic schema configuration information (for example,

schema prefixes and passwords) that can then be accessed and used by other Oracle

Fusion Middleware components during domain creation.

For example, the configuration wizard has screens which you can configure to use the

data that is 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

Chapter 1

Preparing for Schema Creation

1-6

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 about wiring various components together, see Wiring

Components to Work Together in Administering Oracle Fusion Middleware.

Planning Your Schema Creation

Before you run RCU, make sure that you understand how schemas can be grouped together

and distributed depending on your specific environment.

For more information, the following examples are provided:

• Organizing Schemas on a Single Database for a Single Domain

This example shows a set of schemas in a single database being used by a single

WebLogic domain.

• Organizing Schemas on Multiple Databases for a Single Domain

This example shows a single set of schemas that are distributed on multiple databases

being used by a single WebLogic domain.

• Organizing Schemas on a Single Database for Multiple Domains

This example shows how schemas on a single database should be grouped for multiple

domains.

• Organizing Schemas on Multiple Databases for Multiple Domains

This example shows how to organize schemas on multiple databases for use with

multiple WebLogic domains.

Organizing Schemas on a Single Database for a Single Domain

This example shows a set of schemas in a single database being used by a single WebLogic

domain.

This is the simple scenario in which all schemas using the

DEV

prefix are grouped together

and used by a single WebLogic domain.

Chapter 1

Preparing for Schema Creation

1-7

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

DEV_WLS_RUNTIME

Organizing Schemas on Multiple Databases for a Single Domain

This example shows a single set of schemas that are 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

Chapter 1

Preparing for Schema Creation

1-8

You can use the same schema prefix (in this case,

DEV

) can be used to group these related

schemas together, even across multiple databases.

Organizing Schemas on a Single Database for Multiple Domains

This example shows how schemas on a single database should be grouped for multiple

domains.

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

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.

Organizing Schemas on Multiple Databases for Multiple Domains

This example shows how to organize schemas on multiple databases for use with multiple

WebLogic domains.

Chapter 1

Preparing for Schema Creation

1-9

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

In this scenario, it is possible to have separate domains on the same host that use

schemas with the same name and prefix (

DEV

), since the schemas are located on

different databases.

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 about integrating various components, see Extending Repository

Creation Utility to Configure Custom Application Repositories.

Prerequisites for Schema Creation on an Autonomous

Transaction Processing Database

Before you create schemas on an Autonomous Transaction Processing database

(both Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle

Autonomous Transaction Processing-Shared (ATP-S)), you must modify the wallet

settings and set the environment variables, and apply patches on

ORACLE HOME

• Settings to connect to an Autonomous Transaction Processing Database

To connect to an Autonomous Transaction Processing database (both Oracle

Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous

Transaction Processing-Shared (ATP-S)), modify the wallet settings and set the

environment variables as described in this section.

Chapter 1

Prerequisites for Schema Creation on an Autonomous Transaction Processing Database

1-10

• Applying Patches on Oracle Home

This section lists the patches to be applied before you create schemas for an

Autonomous Transaction Processing database (both Oracle Autonomous Transaction

Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-Shared

(ATP-S)).

Settings to connect to an Autonomous Transaction Processing Database

To connect to an Autonomous Transaction Processing database (both Oracle Autonomous

Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-

Shared (ATP-S)), modify the wallet settings and set the environment variables as described in

this section.

Note:

For Oracle Internet Directory, to connect to an Autonomous database, see Settings

to connect to an Autonomous Transaction Processing Database for Oracle Internet

Directory.

To modify the wallet settings:

1. Download the wallet for the Autonomous Transaction Processing database, and unzip the

wallet to the /users/test/wallet_dbname/ directory.

Note:

/users/test/wallet_dbname/

directory is an example of wallet location. You

can download the wallet to the desired location.

You must ensure that the wallet contains keystore for JDBC connection.

2. In the wallet, modify the wallet location in the

sqlnet.ora

file as follows:

WALLET_LOCATION = (SOURCE=(METHOD=FILE)(METHOD_DATA=(DIRECTORY="/users/test/

wallet_dbname/")))

Note:

If you downloaded the wallet to a different location, change the directory

location to your wallet location.

3. In the wallet, add the following command at the end of the

ojdbc.properties

file:

SSL_SERVER_DN_MATCH=yes

To set the environment variables:

1. Before starting RCU, run the following commands:

export RCU_SSL_MODE=true

export TNS_ADMIN=/users/test/wallet_dbname/

Chapter 1

Prerequisites for Schema Creation on an Autonomous Transaction Processing Database

1-11

Note:

In the command to export TNS_ADMIN, change

/users/test/

wallet_dbname/

directory to your wallet location.

• Settings to connect to an Autonomous Transaction Processing Database for

Oracle Internet Directory

To connect to Autonomous Transaction Processing database (both Oracle

Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous

Transaction Processing-Shared (ATP-S)), for Oracle Internet Directory, modify the

wallet settings and set the environment variables as described in this section.

Settings to connect to an Autonomous Transaction Processing Database for

Oracle Internet Directory

To connect to Autonomous Transaction Processing database (both Oracle

Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous

Transaction Processing-Shared (ATP-S)), for Oracle Internet Directory, modify the

wallet settings and set the environment variables as described in this section.

To modify the wallet settings:

1. Download the wallet for the Autonomous Transaction Processing database to the

<$ORACLE_HOME>/network/admin

directory.

You must change

$ORACLE_HOME

to your Oracle Home location. For example,

users/test/network/admin

You must ensure that the wallet contains keystore for JDBC connection.

2. In the wallet, modify the wallet location in the

sqlnet.ora

file as follows:

WALLET_LOCATION = (SOURCE=(METHOD=FILE)

(METHOD_DATA=(DIRECTORY="<$ORACLE_HOME>/network/admin")))

You must change

$ORACLE_HOME

to your Oracle Home location. For example,

users/test/network/admin

3. In the wallet, add the following command at the end of the

ojdbc.properties

file:

SSL_SERVER_DN_MATCH=yes

To set the environment variables:

1. Before starting RCU, run the following commands:

export RCU_SSL_MODE=true

export TNS_ADMIN=<$ORACLE_HOME>/network/admin

You must change

$ORACLE_HOME

to your Oracle Home location. For example,

users/test/network/admin

Applying Patches on Oracle Home

This section lists the patches to be applied before you create schemas for an

Autonomous Transaction Processing database (both Oracle Autonomous Transaction

Chapter 1

Prerequisites for Schema Creation on an Autonomous Transaction Processing Database

1-12

Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-Shared

(ATP-S)).

You must apply the following patches on

ORACLE HOME

, before creating schemas using the

Repository Creation Utility screens.

Patch Number Product Applicable

31676526 Generic patch applicable to all ATP-D and ATP-S certified products

30540494 Generic patch applicable to all ATP-D and ATP-S certified products

31443286 Applicable to SOA components, Oracle Enterprise Scheduler and

Oracle Managed File Transfer, for both ATP-D and ATP-S

28186730

For Oracle Identity

Management and Oracle

Internet Directory, OPatch

13.9.4.2.5 is the mandatory

patch and OPatch 13.9.4.2.6

is the recommended patch.

Applicable to Oracle Identity Management and Oracle Internet

Directory, for both ATP-D and ATP-S

OIM Bundle Patch

(12.2.1.4.210428

(p32829648_122140_Generi

c.zip))

For information on bundle

patch, see Critical Patch

Update Oracle Fusion

Middleware 12.2.1.4.0 Known

Issues (Doc ID 2602696.1) at

https://support.oracle.com.

From April 2021 Bundle

Patch (12.2.1.4.210428

(p32829648_122140_Generi

c.zip)) onwards, ATP-D

support is available for all

OIM bundle patches released

thereafter.

Applicable to Oracle Identity Management for ATP-D only

OID Bundle Patch

12.2.1.4.210714

(p33115009_122140_Linux-

x86-64.zip)

Applicable to Oracle Internet Directory , for both ATP-D and ATP-S

33351665

(p33351665_122140_Generi

c.zip)

Applicable to SOA components, Oracle Enterprise Scheduler and

Oracle Managed File Transfer for ATP-S only.

33757456 (OIM Bundle Patch

12.2.1.4.220115)

From January 2022 OIM

Bundle Patch

12.2.1.4.220115 onwards,

support is available for both

ATP-D and ATP-S.

Applicable to Oracle Identity Management for both ATP-D and ATP-S.

Chapter 1

Prerequisites for Schema Creation on an Autonomous Transaction Processing Database

1-13

Note:

For Oracle Identity Management, ensure that you first apply the generic

patches, 31676526 and 30540494, followed by OPatch 28186730, and then

the OIM Bundle Patch. You must follow this sequence for OIM Bundle Patch

12.2.1.4.210428 and OIM Bundle Patch 12.2.1.4.220115.

For Oracle Internet Directory, ensure that you first apply the generic patches,

31676526 and 30540494, followed by OPatch 28186730, and then the OID

Bundle Patch.

Using RCU with Java Access Bridge (Windows Only)

Java Access Bridge enables assistive technologies, such as JAWS screen reader, to

read Java applications that run 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

Follow these steps to download and install Java Access Bridge.

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

Install Java Access Bridge

Follow these steps to download and install Java Access Bridge.

1. Download Java Access Bridge from the following URL:

http://www.oracle.com/technetwork/java/javase/tech/index-

jsp-136191.html

2. For complete information and procedure about Java Access Bridge installation,

see Java Access Bridge Installation procedure.

Configure RCU to Use Java Access Bridge

To configure RCU to use Java Access Bridge after you complete the installation, set

the system variable

ORACLE_OEM_CLASSPATH

to point to the installed Java Access

Bridge files.

1. Display System in the Control Panel.

2. Select the Advanced tab.

3. Click New button in the System Variable list. The New System Variable dialog

appears.

4. In the Variable Name field, enter

ORACLE_OEM_CLASSPATH

Chapter 1

Using RCU with Java Access Bridge (Windows Only)

1-14

5. In the Variable Value field, enter the full path for the

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.

Chapter 1

Using RCU with Java Access Bridge (Windows Only)

1-15

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

In 12c, RCU 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 Oracle

Autonomous Transaction Processing-Shared (ATP-S) database, and verify that they are

installed properly.

• Dropping Schemas

Follow these instructions to drop schemas from the database.

Obtaining RCU

In 12c, RCU 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.

2-1

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/jdk1.8.0_211

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 Oracle Autonomous Transaction Processing-Shared (ATP-S) 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).

Chapter 2

Starting RCU

2-2

For more information about using the Command Line Interface (CLI), see Running Repository

Creation Utility from the Command Line.

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

Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle

Autonomous Transaction Processing-Shared (ATP-S)) 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 Oracle Autonomous Transaction

Processing-Shared (ATP-S), 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.

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

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

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.

Chapter 2

Creating Schemas

2-3

Table 2-1 (Cont.) Schema Creation Steps for Full-Privilege Users

Screen Description

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 Oracle Autonomous

Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction

Processing-Shared (ATP-S)), 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. See Additional Requirements for IBM DB2 Databases for more information.

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 Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle

Autonomous Transaction Processing-Shared (ATP-S)), 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. 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.

•

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

Integrator are visible.

•

If you selected SOA Suite, the Custom Variables for Oracle SOA Suite are

visible.

•

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

WebCenter Portal Analytics is visible.

•

If you selected Oracle GoldenGate - Repository, the Custom Variables for

Oracle GoldenGate Studio are visible.

•

If you selected Oracle Data Integrator, SOA Suite, and WebCenter Portal -

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

and Oracle WebCenter Portal Analytics are visible on this screen.

Chapter 2

Creating Schemas

2-4

Table 2-1 (Cont.) Schema Creation Steps for Full-Privilege Users

Screen Description

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

To create schemas on an Autonomous Transaction Processing database (both

Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle

Autonomous Transaction Processing-Shared (ATP-S)), a user with limited database

privileges needs to follow the steps in Create Repository in Table 2-1.

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 About System Load and Product Load for more information about these

operations.

Chapter 2

Creating Schemas

2-5

Table 2-2 (Cont.) Schema Creation Steps for Limited-Privilege Users

Screen Description

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.

•

If you selected SOA Suite, the Custom Variables for Oracle SOA Suite are

visible.

•

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

WebCenter Portal Analytics is visible.

•

If you selected SOA Suite and WebCenter Portal - Analytics, the custom

variables for Oracle SOA Suite and Oracle WebCenter Portal Analytics are

visible on this screen.

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.

Chapter 2

Creating Schemas

2-6

Table 2-2 (Cont.) Schema Creation Steps for Limited-Privilege Users

Screen Description

N/A After the scripts are created, user with SYS or SYSDBA privileges must execute

the

script_systemLoad.sql

script:

1. Sign in to SQL*Plus.

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

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

•

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

Integrator are visible.

•

If you selected SOA Suite, the Custom Variables for Oracle SOA Suite are

visible.

•

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

WebCenter Portal Analytics is visible.

•

If you selected Oracle GoldenGate - Repository, the Custom Variables for

Oracle GoldenGate Studio are visible.

•

If you selected Oracle Data Integrator, SOA Suite, and WebCenter Portal -

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

and Oracle WebCenter Portal Analytics are visible on this screen.

Chapter 2

Creating Schemas

2-7

Table 2-2 (Cont.) Schema Creation Steps for Limited-Privilege Users

Screen Description

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.

1. Sign in to SQL*Plus.

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

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

12.2.1.4.0

Audit Service Append

12.2.1.4.0

Audit Service Viewer

12.2.1.4.0

COMP_NAME

Chapter 2

Creating Schemas

2-8

--------------------------------------------------------------------------------

VERSION

------------------------------

Metadata Services

12.2.1.4.0

Oracle Platform Security Services

12.2.1.4.0

Service Table

12.2.1.4.0

COMP_NAME

--------------------------------------------------------------------------------

VERSION

------------------------------

User Messaging Service

12.2.1.0.0

WebLogic Services

12.2.1.4.0

8 rows selected.

Creating Schemas for WebLogic Server on an ATP-S Database

Follow these instructions to create schemas for WebLogic Server on an Oracle Autonomous

Transaction Processing-Shared (ATP-S) 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 Oracle Autonomous Transaction Processing-

Shared (ATP-S) 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.

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.

Chapter 2

Creating Schemas for WebLogic Server on an ATP-S Database

2-9

Table 2-3 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. 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.

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.

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

Chapter 2

Creating Schemas for WebLogic Server on an ATP-S Database

2-10

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.

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

12.2.1.4.0

Audit Service Append

12.2.1.4.0

Audit Service Viewer

12.2.1.4.0

COMP_NAME

--------------------------------------------------------------------------------

VERSION

------------------------------

Metadata Services

12.2.1.4.0

Oracle Platform Security Services

12.2.1.4.0

Service Table

12.2.1.4.0

COMP_NAME

--------------------------------------------------------------------------------

VERSION

------------------------------

User Messaging Service

12.2.1.0.0

Chapter 2

Creating Schemas for WebLogic Server on an ATP-S Database

2-11

WebLogic Services

12.2.1.4.0

8 rows selected.

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

•

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

Integrator are visible.

•

If you selected SOA Suite, the Custom Variables for Oracle SOA Suite are

visible.

•

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

WebCenter Portal Analytics is visible.

•

If you selected Oracle Data Integrator, SOA Suite, and WebCenter Portal -

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

and Oracle WebCenter Portal Analytics are visible on this screen.

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.

Chapter 2

Dropping Schemas

2-12

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

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.

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.

Chapter 2

Dropping Schemas

2-13

Running Repository Creation Utility from the

Command Line

The command-line interface (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.

For more information on how to run RCU from the command line, see the following topics:

• Command-Line Syntax and Parameters

To run RCU from the command line, you need to specify a mode, an operation, and any

necessary parameters. Make sure that you understand the syntax and the various

command-line parameters you can use for your operation.

• Using the -silent Command

Use the

-silent

command if you want to run RCU with minimal interaction once you

have entered the command.

• Using the -interactive Command

Use the

-interactive

command to run the RCU graphical interface. This is the default

value if neither

-silent

nor

-interactive

is specified.

• Using Response Files

Before you run RCU, you can provide information that is required to perform a specific

operation in a response file. For example, you can provide your database connection

details, a list of components to be added or dropped, and the schema prefix to RCU

through a response file.

• Creating a Repository from the Command Line

If you are a user with full SYS or SYSDBA privileges, use the -createRepository

operation to create a repository.

• Generating a System Load Script From the Command Line

If you are a user without SYS or SYSDBA privileges, use the -generateScript

operation to generate a script. A user with DBA privileges can run the script later to

complete the system load phase.

• Loading Data Into the Repository From the Command Line

After the system load scripts are run by a user with DBA privileges, any user can then

use the -dataLoad operation to load data into a repository.

• Dropping a Repository from the Command Line

Use the -dropRepository operation to drop a repository.

• Generating a List of Components in an Oracle Home from the Command Line

Use the -listComponents command to generate a list of valid components that are

available in a given Oracle home. This command displays the name, component ID, and

the supported database types for each component that is available in the Oracle home in

which RCU was started.

• Generating a List of Schemas in a Database from the Command Line

Use the

-listSchemas

command to generate a list of valid schemas in a given database.

3-1

• RCU Environment Variables

The RCU environment variables are the variables picked up by RCU from the

environment. If an environment variable is not set, then RCU uses the default

value.

Command-Line Syntax and Parameters

To run RCU from the command line, you need to specify a mode, an operation, and

any necessary parameters. Make sure that you understand the syntax and the various

command-line parameters you can use for your operation.

The syntax for the RCU command-line interface is:

rcu mode operation {parameters}

There are two modes (

-silent

and

-interactive

) and eight operations (

generateResponseFile

-responseFile

-createRepository

-generateScript

dataLoad

-dropRepository

-listComponents

, and

-listSchemas

). So, the command

can be written out as follows:

rcu [-silent | -interactive] [-generateResponseFile | -responseFile | -

createRepository | -generateScript | -dataLoad |

-dropRepository | -listComponents | -listSchemas]

{parameters}

The following topics describe each of the modes, operations, and parameters:

• RCU Modes Available from the Command Line

There are two RCU modes available from the command line,

-silent

mode and

interactive

mode.

• RCU Operations Available from the Command Line

There are eight RCU operations that are available from the command-line.

• RCU Command Line Parameters

You can pass the RCU command-line parameters to RCU as input by directly

entering the parameters on the command line or by using a response file.

RCU Modes Available from the Command Line

There are two RCU modes available from the command line,

-silent

mode and

interactive

mode.

Table 3-1 RCU Modes Available from the Command Line

Command Description

-silent

Run RCU with minimal or no interaction from the command line.

For more information about silent mode, see Using the -silent Command.

Chapter 3

Command-Line Syntax and Parameters

3-2

Table 3-1 (Cont.) RCU Modes Available from the Command Line

Command Description

-interactive

Run the RCU graphical interface. This is the default if neither

-silent

nor

interactive

is specified.

This command (whether specified or not) allows you to prepopulate certain screens

with the information that is specified in the response file or from the command line.

You can prepopulate the Create Repository and Database Connection Details

screens.

For more information about graphical mode, see Using the -interactive Command.

RCU Operations Available from the Command Line

There are eight RCU operations that are available from the command-line.

Table 3-2 RCU Operations Available from the Command Line

Command Description

-generateResponseFile

Run RCU with

-silent

to generate a RCU response file that contains all valid RCU

command line parameters.

See Creating a RCU Response File from the Command Line

-responseFile

Run RCU with either

-silent

-interactive

to perform a RCU operation using

a response file.

See Performing RCU Operations by Using a Response File

-createRepository

Run RCU with either

-silent

-interactive

to create a repository.

See Creating a Repository from the Command Line.

-generateScript

Run RCU with either

-silent

-interactive

to generate a script for system

load.

See Generating a System Load Script From the Command Line.

-dataLoad

Run RCU with either

-silent

-interactive

to load data into the repository.

See Loading Data Into the Repository From the Command Line.

-dropRepository

Run RCU with either

-silent

-interactive

to drop a repository.

See Dropping a Repository from the Command Line.

-listComponents

Run RCU with

-silent

to generate a list of components for a given Oracle home.

See Generating a List of Components in an Oracle Home from the Command Line.

-listSchemas

Run RCU with

-silent

to list the schemas in a given database.

See Generating a List of Schemas in a Database from the Command Line.

RCU Command Line Parameters

You can pass the RCU command-line parameters to RCU as input by directly entering the

parameters on the command line or by using a response file.

Chapter 3

Command-Line Syntax and Parameters

3-3

Table 3-3 RCU Command Line Parameters and Descriptions

Parameter Required? Valid for Which

Operation?

Description

-compInfoXMLLocation

-createRepository

-generateScript

-dataLoad

-dropRepository

The full path to the location of the

ComponentInfo.xml

file. The default location

ORACLE_HOME/oracle_common/rcu/

config

(on UNIX operating systems) or

ORACLE_HOME\oracle_common\rcu\config

(on Windows operating systems).

-storageXMLLocation

-createRepository

-generateScript

-dataLoad

-dropRepository

The full path to the location of the

StorageInfo.xml

file. The default location is

ORACLE_HOME/oracle_common/rcu/config

(on UNIX operating systems) or

ORACLE_HOME\oracle_common\rcu\config

(on Windows operating systems).

-databaseType

-createRepository

-generateScript

-dataLoad

-dropRepository

-listSchemas

The type of database to which you are

connecting.

If you perform the system load and product load

concurrently as a user with full DBA privileges,

the valid options are

ORACLE

SQLSERVER

IBMBD2

MYSQL

, or

EBR

MySQL database is supported for Oracle Data

Integrator and Oracle GoldenGate Studio Fusion

Middleware components only.

If you do not have permissions to perform the

system load and product load concurrently and

need to generate a script, you can only use the

ORACLE

and

EBR

database types.

For more information about system load and

product load, see About System Load and

Product Load.

-connectString

Yes

-createRepository

-generateScript

-dataLoad

-dropRepository

-listSchemas

The credentials to connect to your database.

For Oracle or EBR-enabled databases, use the

following format:

host:port:sid

OR:

host:port/service

For all other database types, use:

server_name/host:port:database_name

-edition

-createRepository

-generateScript

-dataLoad

-dropRepository

-listSchemas

The edition name. This parameter is only valid if

you specify

databaseType=EBR

Chapter 3

Command-Line Syntax and Parameters

3-4

Table 3-3 (Cont.) RCU Command Line Parameters and Descriptions

Parameter Required? Valid for Which

Operation?

Description

-dbUser

Yes

-createRepository

-generateScript

-dataLoad

-dropRepository

generateResponseFi

-listSchemas

The database user name. For example, the

SYS

user on Oracle databases).

This parameter is required if the

—

createWallet

parameter is provided during

the

-generateResponseFile

operation. RCU

uses the database user name as the key or alias

to store the database user password when

generating a wallet. If the

—createWallet

parameter is not provided, the database user

name is optional.

-dbRole

-createRepository

-generateScript

-dataLoad

-dropRepository

-listSchemas

The database user role. For example,

SYSDBA

for the

SYS

user on Oracle databases).

This parameter is needed only if

-dbUser

specified and the role is

SYSDBA

-unicodeSupport

-createRepository

dropRepository

Specify either

Yes

for unicode support.

Default parameter is

Yes

. This parameter is only

valid if you specify

databaseType=SQLSERVER

skipCleanupOnFailure

-createRepository

-generateScript

-dataLoad

If the schema creation fails, specify whether you

want to skip the schema cleanup. The valid

values are

Yes

. The default value is

skipTablespaceDropon

Failure

-createRepository

-generateScript

-dataLoad

If schema creation fails, whether or not you want

to skip the schema cleanup. The valid values

are

Yes

. The default value is

Specify

Yes

to retain tablespaces for failed

components during schema cleanup. Specify

to drop tablespaces for failed components

during schema cleanup.

-scriptLocation

-generateScript

Specify the location to save the generated script

for system load repository.

useSamePasswordForAl

lSchemaUsers

-createRepository

-dataLoad

generateResponseFi

Whether you want to use the same password for

all schemas. The valid values are

true

false

. The default value is

false

selectDependentsForC

omponents

-createRepository

-generateScript

-dataLoad

-dropRepository

generateResponseFi

Whether you want to have RCU automatically

select dependent schemas for your components.

The valid values are

true

false

. The default

value is

false

STB schema is created independent of this

switch, whether the value is

true

false

Chapter 3

Command-Line Syntax and Parameters

3-5

Table 3-3 (Cont.) RCU Command Line Parameters and Descriptions

Parameter Required? Valid for Which

Operation?

Description

-honorOMF

-createRepository

-generateScript

If the value is set to

true

, RCU creates datafiles

using the Oracle-Managed Files (OMF) naming

format.

The valid values are

true

false

. The default

value is

false

-encryptTablespace

-createRepository

-generateScript

Specify whether you want to encrypt all new

tablespaces that are created by RCU. This

option is valid only if you have TDE (Transparent

Data Encryption) enabled in the database

(Oracle or Oracle EBR) when you start RCU.

TDE tablespace encryption allows you to

encrypt sensitive data stored in tablespaces.

The valid values are

true

false

. The default

value is

false

. If the value is set to

true

, all

new tablespaces created by RCU are encrypted

only if TDE is enabled in the database.

Tablespaces that were created before RCU was

launched cannot be encrypted by using this

option.

-skipTablespaceDrop

-dropRepository

This parameter allows you to skip dropping

tablespaces during the

-dropRepository

operation.

The valid values are

Yes

. Specify

Yes

skip tablespace drop. The default value is

-variables

-createRepository

-generateScript

-dataLoad

-dropRepository

Comma-separated variables in the format

variablename

value. See RCU Environment

Variables for a list of RCU environment

variables.

-schemaPrefix

-createRepository

-generateScript

-dataLoad

-dropRepository

generateResponseFi

Prefix for your schemas. For more information

about schema prefixes, see Planning Your

Schema Creation and Select Components (for

Create Operation).

This parameter is required for the

createRepository

-generateScript

dataLoad

, and

-dropRepository

operations.

Also, this parameter is required if the

—

createWallet

parameter is provided during

the

-generateResponseFile

operation. RCU

uses the prefixed schema name as the key or

alias to store schema passwords when

generating a wallet. If the

—createWallet

parameter is not provided, the schema prefix is

optional.

Chapter 3

Command-Line Syntax and Parameters

3-6

Table 3-3 (Cont.) RCU Command Line Parameters and Descriptions

Parameter Required? Valid for Which

Operation?

Description

-component

Yes

-createRepository

-generateScript

-dataLoad

-dropRepository

ID of the component that you want to add or

drop. To specify a single component, use the

format:

-component component_ID

To specify multiple components, use the format:

-component component_ID -component

component_ID

For a list of valid component (schema) IDs, see

About Repository Creation Utility Schemas, IDs,

and Tablespaces. Multiple components are

sometimes necessary because of

dependencies; for example, you can not create

the Oracle Platform Security Services (

OPSS

)

schema if the Audit Services (

IAU

) schema does

not exist. In this case, you must specify both

schemas:

-component OPSS -component IAU

-tablespace

-createRepository

-generateScript

Tablespace name of the component. This

tablespace must exist in the database if you are

using this option.

-tempTablespace

-createRepository

-generateScript

TEMP tablespace name of the component. This

tablespace must exist in the database if you are

using this option.

-createWallet

generateResponseFi

Provide this parameter if you want to create a

wallet file to securely store your RCU

passwords, such as the database user

password, schema passwords, and custom

variable passwords.

RCU accepts password credentials stored in an

Oracle Wallet. That is, you can use the

generated wallet later in silent situations to

provide your passwords to RCU without having

to directly enter any passwords on the command

line.

The wallet is generated in the same directory as

the response file.

Chapter 3

Command-Line Syntax and Parameters

3-7

Table 3-3 (Cont.) RCU Command Line Parameters and Descriptions

Parameter Required? Valid for Which

Operation?

Description

-walletDir

-createRepository

-generateScript

-dataLoad

-dropRepository

-listSchemas

The absolute path of the wallet directory where

your RCU passwords that are used for creating

or dropping schemas are stored. If you choose

to use a wallet to pass passwords to RCU, RCU

retrieves the required passwords from the

specified directory. This option is valid for silent

mode only.

If you use this option, the wallet must already

exist and contain the required passwords. If the

wallet does not contain the required passwords,

RCU prompts you for the missing passwords on

the command line.

This directory should contain a valid

cwallet.sso

file. RCU supports auto-login

wallets only (password is not needed to open

wallet).

-responseFileDir

generateResponseFi

The absolute path of the response file directory.

If specified, RCU generates a response file

named

rcuResponseFile.properties

in the

given directory.

If not specified, RCU generates a response file

in the

$HOME/.rcu

directory by default.

-componentList

generateResponseFi

Comma-separated list of component IDs for the

components in the Oracle home that you want to

add to the response file. To generate a list of

valid component IDs for a specific Oracle home,

see Generating a List of Components in an

Oracle Home from the Command Line.

If not specified, all valid components in the

Oracle home are added to the response file by

default.

-validate

-createRepository

-generateScript

-dataLoad

-dropRepository

Use this option to execute validation checks in

silent mode and verify that all prerequisites for

the specified operation have been met.

With this option, RCU only checks for the

prerequisites that are required to perform the

operation and then exits. For more information

about validate parameter, see Using the -

validate Parameter to Verify Prerequisites.

-schemaPrefixes

-listSchemas

Comma-separated list of schema prefixes. If

provided, RCU only lists the schemas with the

given prefixes.

Chapter 3

Command-Line Syntax and Parameters

3-8

Using the -silent Command

Use the

-silent

command if you want to run RCU with minimal interaction once you have

entered the command.

Run RCU for all databases in silent mode

You must specify all mandatory command-line parameters in the command. For example:

rcu -silent -createRepository -connectString database_connect_string -dbUser

database_user -component component

In this scenario, RCU prompts you for the database and component schema passwords from

the command line. If you specify multiple components, you are prompted for the passwords in

the order in which the components are specified.

Instead of directly entering all the RCU parameters on the command line, you can provide the

location and name of a file that contains certain input values. This file (called a response file)

allows you to pass values for all valid command-line parameters to RCU through a text file.

When you run RCU with a response file, all values are read from the file to create or drop

your schemas. For more information about response file, see Using Response Files.

If you want to avoid all interaction from the command line, you can create a text file contains

all the necessary passwords (one password per line) and then use the

-f

option to pass this

password file to RCU. For example, if you create a file called

passwordfile.txt

, you can use

the command below:

rcu -silent -createRepository -connectString database_connect_string -dbUser

database_user -component component1_name -component

component2_name -f < passwordfile.txt

The

passwordfile.txt

file would contain, in order:

database_password

component1_schema_password

component2_schema_password

When schemas are created for multiple components, -

tablespace

and -

tempTablespace

has

to be declared for each component individually.

For example:

./rcu -silent -createRepository -connectString <connectString> -dbUser SYS

-dbRole SYSDBA -schemaPrefix DEV01 -selectDependentsForComponents true \

-component MDS -tablespace FMW_INFRA -tempTablespace TEMP \

-component IAU -tablespace FMW_INFRA -tempTablespace TEMP \

-component IAU_APPEND -tablespace FMW_INFRA -tempTablespace TEMP \

-component IAU_VIEWER -tablespace FMW_INFRA -tempTablespace TEMP \

-component STB -tablespace FMW_INFRA -tempTablespace TEMP -f <

It is important to make sure that the passwords in the file are specified in the same order as

the components on the command line.

Once the installation is complete, the password file must be removed. The passwords are

maintained in cleartext format, and therefore present a security risk if the password file is left

in place after installation.

Chapter 3

Using the -silent Command

3-9

Instead of using a plain text password file, you can also create an Oracle Wallet file

that contains all the necessary passwords and then use the

-walletDir

parameter to

pass this file to RCU. In this case, RCU does not prompt you for any passwords that

are stored in the wallet. For more information about using wallet, see Using a Wallet to

Store Passwords.

For more information on running RCU in

-silent

mode, see the following topics:

Run RCU for Oracle GoldenGate on ATP databases in silent mode

Note:

To create schemas on an Autonomous Transaction Processing database

(both Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and

Oracle Autonomous Transaction Processing-Shared (ATP-S)) for Oracle

GoldenGate, you can use only the silent command and cannot use the

Repository Creation Utility screens (GUI mode).

For example, use the following command to run RCU in silent mode:

./rcu -silent -createRepository -connectString

'(description=(CONNECT_TIMEOUT=120)(RETRY_COUNT=20)(RETRY_DELAY=3) \

(TRANSPORT_CONNECT_TIMEOUT=3)(ADDRESS_LIST=(LOAD_BALANCE=on)

(ADDRESS=(PROTOCOL=protocol_name) \

(HOST=host_name)(PORT=port_number)))(CONNECT_DATA=(SERVICE_NAME=service_name))) -

dbUser admin -dbRole normal \

-useSSL -sslArgs javax.net.ssl.trustStore=/home/opc/veridata/

cwallet.sso,javax.net.ssl.trustStoreType=SSO, \

javax.net.ssl.keyStore=/home/opc/veridata/

cwallet.sso,javax.net.ssl.trustStoreType=SSO,oracle.net.ssl_server_dn_match=true,

oracle.net.ssl_version=1.2 -useSamePasswordForAllSchemaUsers true -

selectDependentsForComponents true \

-schemaPrefix OGG1ATP -component UCSUMS \

-component OPSS -component IAU -component STB -component WLS -component

IAU_APPEND -component IAU_VIEWER -component MDS -component VERIDATA \

-serverDN "CN=adwc.uscom-east-1.oraclecloud.com,OU=Oracle BMCS

US,O=OracleCorporation,L=Redwood City,ST=California,C=US"

Run RCU for Oracle WebLogic Server on ATP-S database in silent mode

Use the following command to run RCU in silent mode:

./rcu -silent -createRepository -databaseType ORACLE -connectString

jdbc:oracle:thin:@dbname_tp?TNS_ADMIN=/users/test/wallet_dbname/ -dbUser admin -

dbRole normal \

-useSamePasswordForAllSchemaUsers true -selectDependentsForComponents true \

-schemaPrefix WLS1001 -component STB -tablespace DATA -tempTablespace TEMP \

-component WLS -tablespace DATA -tempTablespace TEMP \

-component IAU_APPEND -tablespace DATA -tempTablespace TEMP \

-component IAU_VIEWER -tablespace DATA -tempTablespace TEMP \

-component OPSS -tablespace DATA -tempTablespace TEMP \

-component IAU -tablespace DATA -tempTablespace TEMP \

-component MDS -tablespace DATA -tempTablespace TEMP \

-f < ~/<rcu_atp_password>

Chapter 3

Using the -silent Command

3-10

• Using the -validate Parameter to Verify Prerequisites

Before you run an operation from the command line, you can use the

—validate

option in

silent mode to verify that all RCU prerequisites have been met.

• Using a Wallet to Store Passwords

If you are running RCU from the command line, password credentials (for example,

schema passwords) can be stored in an Oracle Wallet file. This wallet file can be

provided to RCU from the command line.

Using the -validate Parameter to Verify Prerequisites

Before you run an operation from the command line, you can use the

—validate

option in

silent mode to verify that all RCU prerequisites have been met.

When you run RCU with the

-validate

option, RCU performs validation checks to validate all

prerequisites for the specified operation, and then exits. For example, this command

validates the values for any command-line parameters and verifies that the minimum

requirements are met in the database prior to schema creation.

You can add the

—validate

option to any valid operation to run the validation checks, as

shown in the following example:

./rcu -silent -createRepository -useSamePasswordForAllSchemaUsers true -databaseType

ORACLE

-connectString examplehost.exampledomain.com:1521:exampleSID -dbUser sys -dbRole

sysdba

-selectDependentsForComponents true -schemaPrefix DEV -component MDS -component OPSS

-component STB -component BIPLATFORM -validate

If a prerequisite check fails, RCU returns a non-zero exit code and prints the issue to the

console. You can refer to the command output and log file to manually fix the issue, and then

rerun the

—validate

command to ensure that all checks are successful.

If all prerequisite checks pass, the exit status is zero (0).

If a validation check fails, the following table provides more information about the exit codes

returned by RCU.

Validation Check Description Exit Code Number

Database Connection Check Validates the provided connection

credentials for the database in which

you create or drop schemas.

This check ensures that a database

connection can be established by

using the values provided for the

database connect string, user name,

and password.

If the

-encryptTablespace true

option is provided, RCU verifies that

TDE (Transparent Data Encryption)

is enabled in the database.

• Database connection failed: 100

• Unsupported database type: 101

• Empty field: 102

• Invalid port: 103

Chapter 3

Using the -silent Command

3-11

Validation Check Description Exit Code Number

Global Prerequisites Check Verifies the global prerequisites listed

in the global

ComponentInfo.xml

file (in ORACLE_HOME/

oracle_common/rcu/

config).

For example, this check verifies the

database version and the values for

the database initialization

parameters.

• Global prerequisite failed: 200

• Metadata initialization failed: 201

• TDE not enabled: 202

Schema Prefix Check Validates the

-schemaPrefix

parameter.

• For the create operation, RCU

ensures that the prefix follows

the expected pattern and does

not exceed the allowed number

of characters.

• For the drop operation, RCU

ensures that the schema prefix

already exists.

• Schema prefix validation failed:

300

Component Name Check Validates the list of component

schema names provided.

For the create operation, RCU

ensures that the components do not

exist for the given prefix and any

dependent components are selected.

• Component validation failed: 400

• Component dependency

validation failed: 401

Schema Password Check Verifies that a given schema

password follows the supported

password pattern and does not

exceed 30 characters.

• Schema password validation

failed: 700

Component Prerequisites Check Validates the component-specific

prerequisites of each component.

The prerequisites are listed in the

component repository configuration

file (

component.xml

) in

ORACLE_HOME/

product_directory/

common/sql/component for

each component.

• Component prerequisite failed:

500

Tablespace Validation Check Validates the tablespace names and

verifies that the tablespace

prerequisites are met.

• Tablespace validation failed: 600

• Mapping tablespace to

component validation failed: 601

Custom Variables Check Validates component custom

variables and their values.

• Custom variable validation

failed: 800

Script Location Validation Check Validates the value provided for the

–

scriptLocation

argument and

checks whether the value is null or

empty.

• Value for

–scriptLocation

argument is invalid or not

provided: 900

Chapter 3

Using the -silent Command

3-12

Using a Wallet to Store Passwords

If you are running RCU from the command line, password credentials (for example, schema

passwords) can be stored in an Oracle Wallet file. This wallet file can be provided to RCU

from the command line.

When you run RCU from the command line, RCU prompts you to enter values for any

required passwords by default. To avoid entering passwords on the command line, you can

create a wallet file to securely store any necessary password credentials. You can then pass

the wallet to RCU by providing the wallet location with the

walletDir

parameter.

Creating a Wallet Using RCU

A wallet for providing RCU passwords can be generated by RCU as part of the response file

creation:

• To create a wallet using the RCU graphical interface, see Creating a RCU Response File

from the Graphical Interface.

• To create a wallet using the RCU command-line interface, see Creating a RCU Response

File from the Command Line.

Once the wallet is created, this file can be reused to store and provide passwords for multiple

sessions.

RCU only supports auto-login wallets (no password is needed to open a wallet). Password-

protected wallets are not supported.

When RCU generates the wallet, RCU uses the prefixed schema name as the key or alias for

storing schema passwords, which allows you to reuse the same wallet for multiple sessions.

For the database user password, the alias is the database user name (for example, SYS). If

the same password is used for all the schemas, then RCU uses the alias

prefix_COMMON_SCHEMA_PASSWORD to save the password in the wallet.

Example 3-1 Using the -walletDir Parameter

After the wallet is created and contains the necessary passwords, use the

—walletDir

parameter to pass this file to RCU so that you do not have to directly enter your passwords

on the command line. Alternatively, the wallet location can be provided to RCU through a

response file.

For example:

./rcu -silent -createRepository -connectString

examplehost.exampledomain.com:1521:example_sid -dbUser sys -dbRole sysdba

-schemaPrefix DEV -component MDS -component STB -walletDir /home/exampleuser/wallet

When you pass the wallet to RCU, RCU expects all the necessary passwords required to

perform an operation to be in the wallet, which include your:

• Database user password

• Schema passwords

• Custom Variable passwords (for Oracle Data Integrator)

In this example, the wallet should contain passwords for the database user (sys), the

Metadata Services (MDS) schema, and the Service Table (STB) schema. If a wallet does not

contain all the necessary passwords, you are prompted to enter the missing passwords on

the command line.

Chapter 3

Using the -silent Command

3-13

Using the -interactive Command

Use the

-interactive

command to run the RCU graphical interface. This is the default

value if neither

-silent

nor

-interactive

is specified.

You can specify information from the command line that would be populated in the

graphical interface to expedite your RCU operation.

For example, if you run RCU with the following command, the Database Connection

Details screen contains blank fields.

./rcu

But if you run RCU with a few parameters using the following command, the Database

Connection Details screen contains the information supplied from the command line.

./rcu -interactive -createRepository -connectString

examplehost.exampledomain.com:1521:example_sid -dbUser SYS -component MDS

When you run the RCU graphical interface, you can provide the location and name of

a file (called a response file) that contains certain input values (for example, your

database connection information). When you use the graphical interface, you are

prompted for these values. The values you enter in a response file can be used to

populate certain RCU screens. For more information about using response file, see

Using Response Files.

Using Response Files

Before you run RCU, you can provide information that is required to perform a specific

operation in a response file. For example, you can provide your database connection

details, a list of components to be added or dropped, and the schema prefix to RCU

through a response file.

You can use a response file to automate a RCU session. When you run RCU by using

a response file, RCU reads the information provided in the response file to complete

the operation.

For more information, see the following topics:

• About Response Files

A response file is a properties file in which all RCU command-line parameters can

be provided as input to RCU to perform an operation.

• Creating a RCU Response File from the Graphical Interface

Use the Save Response File option on the Summary screen to save the

information you provide in the RCU screens to a response file.

• Creating a RCU Response File from the Command Line

Use the -generateResponseFile command to generate a response file.

• Performing RCU Operations by Using a Response File

Use the -responseFile command to perform an operation with a response file.

You use a response file to provide input to RCU to automate an operation from the

command line or from the graphical interface.

Chapter 3

Using the -interactive Command

3-14

About Response Files

A response file is a properties file in which all RCU command-line parameters can be

provided as input to RCU to perform an operation.

Rather than directly entering the RCU Command Line Parameters on the command line, you

can provide values for these parameters to RCU through a text file. You can generate this file

from the RCU graphical interface by using the values you provide in the RCU screens or from

the command line. After you create a response file, the parameters can be modified in a text

editor or be used exactly as-is to perform an operation at a later time.

If you choose to run RCU from the command line with a response file, the values you specify

in a response file are the values for the RCU parameters that you would normally provide on

the command line during a typical silent RCU session. If you choose to run the RCU

graphical interface with a response file, the values you specify in a response file are used to

prepopulate the fields on certain screens.

Creating a RCU Response File from the Graphical Interface

Use the Save Response File option on the Summary screen to save the information you

provide in the RCU screens to a response file.

After you click the Save Response File option, you are prompted to specify a location to

create this file. By default, RCU saves the response file in the

$HOME/.rcu

directory.

Because the response file needs to contain password information, RCU provides the Save

Passwords in Wallet option to securely store any passwords that you provide on the RCU

screens in a wallet. You can use the wallet later in silent situations to provide the necessary

passwords to RCU so that you do not have to directly enter your passwords on the command

line. When you run RCU from the command line, the wallet location can be passed to RCU

on the command line or through a response file. If a wallet directory is not passed to RCU,

you are prompted for the required passwords.

Creating a RCU Response File from the Command Line

Use the -generateResponseFile command to generate a response file.

The full syntax for the RCU command-line interface to generate a RCU response file is

shown below:

rcu -silent -generateResponseFile

[-responseFileDir absolute_path_of_response_file_directory]

[-schemaPrefix schema_prefix]

[-componentList list_of_component_IDs]

[-createWallet]

[-useSamePasswordForAllSchemaUsers [true|false]]

[-selectDependentsForComponents [true|false]]

[-dbUser database_username]

If the

—createWallet

parameter is provided, then values for

—dbUser

and

—schemaPrefix

are

required. Otherwise, the

—dbUser

and

—schemaPrefix

parameters are optional. RCU uses the

prefixed schema name and the database user name as the key or alias to store schema

passwords and the database user password in the wallet, respectively.

Chapter 3

Using Response Files

3-15

If you provide the

—createWallet

and the

—useSamePasswordForAllSchemaUsers true

parameters on the command line, then all schema passwords are set to the same

value in the wallet.

If the

—createWallet

parameter is provided, RCU will prompt you to enter a value for

each password that is stored in the wallet.

Below is a sample command to generate a response file on a UNIX operating system:

./rcu -silent -generateResponseFile -componentList OPSS,IAU -schemaPrefix DEV -

createWallet

-responseFileDir /home/exampleuser/rcu -useSamePasswordForAllSchemaUsers true

-selectDependentsForComponents true -dbUser sys

In this example, a response file and wallet is created in the /home/

exampleuser/rcu directory, and the information provided on the command line

(such as the list of components) is added to the response file.

Performing RCU Operations by Using a Response File

Use the -responseFile command to perform an operation with a response file. You

use a response file to provide input to RCU to automate an operation from the

command line or from the graphical interface.

If you choose to run the graphical interface with a response file, RCU prepopulates

certain RCU screens (such as the Database Connection Details screen) based on the

input values that you provide in a response file. If you choose to run RCU from the

command line, you can use a response file to provide values for all valid RCU

parameters rather than directly entering these parameters on the command line.

The full syntax for the RCU command-line interface to perform a RCU operation with a

response file is shown below:

rcu [-silent|-interactive] -responseFile absolute_path_of_response_file

Following is a sample command to automate a silent RCU session by using a

response file on a UNIX operating system:

./rcu -silent -responseFile /home/exampleuser/rcu/rcuResponseFile.properties

Chapter 3

Using Response Files

3-16

Note:

• If you provide a value for a parameter on the command line and in the response

file, RCU uses the value that is provided on the command line.

• Before you run RCU, ensure that you have provided the required information in

the response file. If some of the mandatory properties in the response file are

missing values when you run RCU, RCU will notify you and exit.

• When you run RCU, the

dbRole

parameter is not normally required to connect

to certain databases (for example, SQL Server). However, when a RCU

response file is generated, the

dbRole

parameter is marked as required in the

response file by default. As a result, if you use a response file, the

dbRole

field

must not be left blank, even if the database role is not required to connect to a

database like SQL Server.

Creating a Repository from the Command Line

If you are a user with full SYS or SYSDBA privileges, use the -createRepository

operation to create a repository.

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

rcu [-silent | -interactive] -createRepository

[-compInfoXMLLocation ComponentInfo.xml_file_location]

[-storageXMLLocation Storage.xml_file_location]

[-databaseType [ORACLE|EBR]]

-connectString database_connect_string

[-edition edition_name]

-dbUser database_username

[-dbRole database_user_role]

[-unicodeSupport [Yes|No]]

[-skipCleanupOnFailure [true|false]]

[-skipTablespaceDropOnFailure [Yes|No]]

[-useSamePasswordForAllSchemaUsers [true|false]]

[-selectDependentsForComponents [true|false]]

[-honorOMF [true|false]]

[-encryptTablespace [true|false]]

[-variables variablename=value]

[-schemaPrefix schema_prefix]

-component component_ID

[-tablespace component_tablespace_name]

[-tempTablespace component_temp_tablespace_name]

[-walletDir absolute_path_of_wallet_directory]

[-validate]

When you specify the

-component

, you must use the correct component IDs, which are listed

in About Repository Creation Utility Schemas, IDs, and Tablespaces.

Before you create any schemas, you must be aware of and specify all dependencies for the

component that you are loading. For example, the

SOAINFRA

schema depends on the

MDS

and

ORASDPM

schemas; if you try to load the

SOAINFRA

schema without specifying both the

MDS

and

ORASDPM

schemas, or if the

MDS

and

ORASDPM

schemas do not already exist in the database,

RCU stops before any loading takes place.

Following is a sample command to create the OPSS schema on a UNIX operating system:

Chapter 3

Creating a Repository from the Command Line

3-17

./rcu -silent -createRepository -databaseType ORACLE -connectString

examplehost.exampledomain.com:1521:exampleSID -dbUser sys

-dbRole sysdba -schemaPrefix TEST -component OPSS -component MDS

Generating a System Load Script From the Command Line

If you are a user without SYS or SYSDBA privileges, use the -generateScript

operation to generate a script. A user with DBA privileges can run the script later to

complete the system load phase.

The full syntax for the RCU command-line interface to generate a system load script is

shown below:

rcu [-silent | -interactive] -generateScript

[-compInfoXMLLocation ComponentInfo.xml_file_location]

[-storageXMLLocation Storage.xml_file_location]

[-databaseType [ORACLE|EBR]]

-connectString database_connect_string

[-edition edition_name]

-dbUser database_username

[-dbRole database_user_role]

[-skipCleanupOnFailure [Yes|No]]

[-skipTablespaceDropOnFailure [Yes|No]]

[-scriptLocation script_location]

[-selectDependentsForComponents [true|false]]

[-honorOMF [true|false]]

[-encryptTablespace [true|false]]

[-variables variablename=value]

[-schemaPrefix schema_prefix]

-component component_ID

[-tablespace component_tablespace_name]

[-tempTablespace component_temp_tablespace_name]

[-walletDir absolute_path_of_wallet_directory]

[-validate]

When specifying the

-component

, you must use the correct component IDs, which are

listed in About Repository Creation Utility Schemas, IDs, and Tablespaces.

Before you create a script, you must be aware of and specify the all component

dependencies. For example, the

SOAINFRA

schema depends on the

MDS

and

ORASDPM

schemas; if you specify the

SOAINFRA

schema without specifying both the

MDS

and

ORASDPM

schemas, or if the

MDS

and

ORASDPM

schemas do not already exist in the

database, RCU stops before completing the operation.

Below is a sample command to create a system load script on a UNIX operating

system:

./rcu -silent -generateScript -databaseType ORACLE -connectString

examplehost.exampledomain.com:1521:exampleSID -dbUser sys

-dbRole sysdba -scriptLocation /tmp/RCUdate_timestamp_random_number/logs/ -

schemaPrefix TEST

-component OPSS -component MDS

Chapter 3

Generating a System Load Script From the Command Line

3-18

Loading Data Into the Repository From the Command Line

After the system load scripts are run by a user with DBA privileges, any user can then use the

-dataLoad operation to load data into a repository.

The full syntax for the RCU command-line interface to load data into a repository is shown

below:

rcu [-silent | -interactive] -dataLoad

[-compInfoXMLLocation ComponentInfo.xml_file_location]

[-storageXMLLocation Storage.xml_file_location]

[-databaseType [ORACLE|EBR]]

-connectString database_connect_string

[-edition edition_name]

-dbUser database_username

[-dbRole database_user_role]

[-skipCleanupOnFailure [Yes|No]]

[-skipTablespaceDropOnFailure [Yes|No]]

[-useSamePasswordForAllSchemaUsers [true|false]]

[-selectDependentsForComponents [true|false]]

[-variables variablename=value]

[-schemaPrefix schema_prefix]

-component component_ID

[-walletDir absolute_path_of_wallet_directory]

[-validate]

Below is a sample command to perform a data load on a UNIX operating system:

./rcu -silent -dataLoad -databaseType ORACLE -connectString

examplehost.exampledomain.com:1521:exampleSID -dbUser sys -dbRole

sysdba -schemaPrefix TEST -component OPSS -component MDS

Dropping a Repository from the Command Line

Use the -dropRepository operation to drop a repository.

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

rcu [-silent | -interactive] -dropRepository

[-compInfoXMLLocation ComponentInfo.xml_file_location]

[-storageXMLLocation Storage.xml_file_location]

[-databaseType [ORACLE|EBR]]

-connectString database_connect_string

[-edition edition_name]

-dbUser database_username

[-dbRole database_user_role]

[-unicodeSupport [Yes|No]]

[-selectDependentsForComponents [true|false]]

[-skipTablespaceDrop [Yes|No]]

[-variables variablename=value]

[-schemaPrefix schema prefix]

-component component_ID

[-walletDir absolute_path_of_wallet_directory]

[-validate]

You must also be aware of schema dependencies when dropping schemas (see About

Repository Creation Utility Schemas, IDs, and Tablespaces). For example, several schemas

Chapter 3

Loading Data Into the Repository From the Command Line

3-19

require the

MDS

schema to be present; if you choose to drop the

MDS

schema, then all

the schemas that require the

MDS

schema stops working.

Below is a sample command to drop the OPSS schema on a UNIX operating system:

./rcu -silent -dropRepository -databaseType ORACLE -connectString

examplehost.exampledomain.com:1521:exampleSID -dbUser sys -dbRole

sysdba -schemaPrefix TEST -component OPSS

Generating a List of Components in an Oracle Home from

the Command Line

Use the -listComponents command to generate a list of valid components that are

available in a given Oracle home. This command displays the name, component ID,

and the supported database types for each component that is available in the Oracle

home in which RCU was started.

The full syntax for the RCU command-line interface to generate a list of components is

shown below:

rcu -silent -listComponents

The Component ID and database type displayed for each component in the command

output are the values that you must specify with the

-component

and

—databaseType

parameters, respectively, when you create schemas from the command line.

Generating a List of Schemas in a Database from the

Command Line

Use the

-listSchemas

command to generate a list of valid schemas in a given

database.

The full syntax for the RCU command-line interface to list the schemas in a database

is shown below:

rcu -silent -listSchemas

[-databaseType [ORACLE|EBR]]

-connectString database_connect_string

[-edition edition_name]

-dbUser database_username

[-dbRole database_user_role]

[-schemaPrefixes comma_separated_list_of_prefixes]

[-walletDir absolute_path_of_wallet_directory]

Below is a sample command to list the schemas in an Oracle database on a UNIX

operating system:

./rcu -silent -listSchemas -databaseType ORACLE -connectString

examplehost.exampledomain.com:1521:exampleSID

-dbUser sys -dbRole sysdba

You can also specify a comma-separated list of prefixes using the

—schemaPrefixes

argument. If provided, RCU only displays the schemas with those prefixes.

For example:

Chapter 3

Generating a List of Components in an Oracle Home from the Command Line

3-20

./rcu -silent -listSchemas -databaseType ORACLE -connectString

examplehost.exampledomain.com:1521:exampleSID -dbUser sys

-dbRole sysdba -schemaPrefixes DEV,DEV1

RCU Environment Variables

The RCU environment variables are the variables picked up by RCU from the environment. If

an environment variable is not set, then RCU uses the default value.

Table 3-4 RCU Environment Variables

Variable Default Value Description

RCU_LOG_LOCATION /tmp

(UNIX operating

systems)

C:\Users\user_name\AppDa

ta\Local\Temp

(Windows

operating systems)

Location of the RCU log file.

RCU_TIMESTAMP_LOG_DIR true

Determines whether or not a directory with the

format

logdir.yyyy-dd_hh-mm

is created for the

RCU log file.

Set this variable to

true

false

RCU_LOG_NAME rcu.log

Name of the RCU log file.

RCU_LOG_LEVEL ERROR

Determines the RCU log level.

Set this variable to one of

SEVERE

ERROR

NOTIFICATION

, or

TRACE

RCU_JAVA_OPTIONS

N/A Set this variable to any Java Virtual Machine (JVM)

argument.

For example:

setenv RCU_JAVA_OPTIONS -Djava.io.tmpdir=/

scratch/mytmpDir

Chapter 3

RCU Environment Variables

3-21

Repository Creation Utility Screens

Use this information to learn more about the various features and elements of the Repository

Creation Utility (RCU) screens. Each screen will prompt you for information required to create

or drop your schemas.

Note:

The following sections are not applicable when you create schemas for Oracle

GoldenGate products on an Autonomous Transaction Processing database (both

Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle

Autonomous Transaction Processing-Shared (ATP-S)) as you can run RCU only in

silent mode for Oracle GoldenGate.

During schema creation for an Autonomous Transaction Processing database (both

Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle

Autonomous Transaction Processing-Shared (ATP-S)) database, if you encounter

warnings in the Repository Creation Utility screens, see Troubleshooting Tips for

Schema Creation on an Autonomous Transaction Processing Database.

• Welcome

The Welcome screen is the first screen that appears when you start RCU. Note the

navigation pane on the left that summarizes the tasks that RCU helps you complete.

• Create Repository

Use the Create Repository screen to select the action that you want to perform.

• Database Connection Details

Use the Database Connection Details screen to specify the connection credentials to the

database in which you will be create or drop your schemas.

• Select Components (for Create Operation)

Use the Select Components screen to select the components for which you want to

create schemas, and specify a prefix to group them together.

• Select Components (for Drop Operation)

Use the Select Components screen to select the prefix and the schemas that you want to

drop.

• Schema Passwords

Use the Schema Passwords screen to specify the passwords for your schema owners;

there are three ways to specify schema passwords on this screen.

• Custom Variables

If you are installing a product that requires custom variables, you will see the Custom

Variables screen. Use this screen to specify additional product configuration information.

• Map Tablespaces

Use the Map Tablespaces screen to configure the desired tablespace mapping for the

schemas that you want to create.

A-1

• Summary (for Create Operation)

On the Summary (for Create operation) screen, verify your information, then click

Create to begin schema creation.

• Summary (for Drop Operation)

On the Summary (for Drop operation) screen, verify your information, then click

Drop to drop the schemas.

• Completion Summary (for Create Operation)

The Completion Summary (for Create Operation) screen contains information

about the log files that were created from this RCU operation. You can click on the

name of a particular log file to view the contents of that file.

• Completion Summary (for Drop Operation)

The Completion Summary (for Drop operation) screen contains information about

the log files that are created from this RCU operation. Note the log file names for

each component that are visible in the Logfile column.

Welcome

The Welcome screen is the first screen that appears when you start RCU. Note the

navigation pane on the left that summarizes the tasks that RCU helps you complete.

Each item in the navigation pane represents a specific screen that prompts you for

information that is required to create or drop your schemas.

Create Repository

Use the Create Repository screen to select the action that you want to perform.

• Create Repository

Select Create Repository to create component schemas in the database.

• Drop Repository

Select Drop Repository to remove component schemas from the database.

Create Repository

Select Create Repository to create component schemas in the database.

The following table describes the options available:

Option Description

System Load and

Product Load

Select this option to perform both System Load and Product Load operations.

Users must have DBA or SYSDBA permissions to select this option.

For an Autonomous Transaction Processing database (both Oracle Autonomous

Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction

Processing-Shared (ATP-S)) database, 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.

This option can be performed on any certified database.

Appendix A

Welcome

A-2

Option Description

Prepare Scripts for

System Load

Select this option to perform actions that require DBA or SYSDBA permissions:

• Create tablespaces and schemas.

• Create the

schema_version_registry

(if not already present).

• Create entries in

schema_version_registry

for each selected component, set the

proper access permissions, and set the status of the component to LOADED in the

schema_version_registry

table.

Any SYSDBA user or non-DBA user with the privileges described in Granting Permissions

to Users for Querying System Load Objects can select this option. However, DBA

privileges are required to execute the SQL script to complete the system load phase.

This option is only supported on Oracle and Oracle EBR databases.

If you create schemas on an Autonomous Transaction Processing database (both Oracle

Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous

Transaction Processing-Shared (ATP-S)) database, you must not select this option.

Perform Product Load Select this option to load and 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 select this option.

Before you select this option, the user must be granted the following permissions to

perform data load:

grant REGISTRYACCESS to user;

grant STBROLE to user;

If you create schemas on an Autonomous Transaction Processing database (both Oracle

Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous

Transaction Processing-Shared (ATP-S)), you must not select this option.

Drop Repository

Select Drop Repository to remove component schemas from the database.

Database Connection Details

Use the Database Connection Details screen to specify the connection credentials to the

database in which you will be create or drop your schemas.

Click Next when you have finished typing the connection credentials for your database. A

screen indicating the progress of the installer establishing the connection with the specified

database appears.

If an error occurs while the connection is being established, the error messages appear in the

Messages field on the Database Connection Details screen.

Specific database requirements for the various schemas can be found in the Oracle Fusion

Middleware System Requirements and Specifications document.

For certified database versions, see the System Requirements and Supported Platforms for

Oracle Fusion Middleware 12c document, which is available on the Oracle Fusion

Middleware Supported System Configurations page.

Select one of the following depending on your database:

Appendix A

Database Connection Details

A-3

• Connection Credentials for Oracle Databases and Oracle Databases with Edition-

Based Redefinition

To connect to an Oracle database or Oracle database with edition-based

redefinition, you need to specify connection information about the database, such

as Host Name, Port, Service Name, Username, Password, and Role.

• Connection Credentials for Microsoft SQL Server Databases

To connect to a Microsoft SQL Server database, you need to specify connection

information about the database, such as Unicode Support, Server Name, Port,

Database Name, Username, and Password.

• Connection Credentials for IBM DB2 Databases

To connect to an IBM DB2 database, you need to specify connection information

about the database, such as Server Name, Port, Database Name, Username, and

Password.

• Connection Credentials for an Autonomous Transaction Processing Database

To connect to an Autonomous Transaction Processing database (both Oracle

Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous

Transaction Processing-Shared (ATP-S)), you need to specify connection

information about the database, such as Username and Password.

Connection Credentials for Oracle Databases and Oracle Databases

with Edition-Based Redefinition

To connect to an Oracle database or Oracle database with edition-based redefinition,

you need to specify connection information about the database, such as Host Name,

Port, Service Name, Username, Password, and Role.

Use the Database Connection Details screen to specify the connection credentials to

the database in which you want to create or drop schemas. You can select different

databases, however, all databases are not supported for all Fusion Middleware

components.

Note:

MySQL database is supported for Oracle Data Integrator and Oracle

GoldenGate Studio Fusion Middleware components only.

Database Connection Details screen provides two types of Connection String

formats as follows:

• Connection Parameters

• Connect String

Appendix A

Database Connection Details

A-4

Note:

To create schemas on an Autonomous Transaction Processing database (both

Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle

Autonomous Transaction Processing-Shared (ATP-S)), you can specify the

connection credentials only using the Connection String format. See

Connection Credentials for an Autonomous Transaction Processing Database.

For various database types and both Connection String Format, specify the following

connection credentials:

Element Description Database Types

Host Name Enter the name of the server where your database is

running. Use the following format:

examplehost.exampledomain.com

For Oracle RAC databases, specify the VIP name or one

of the node names in this field.

• Oracle Database

• Oracle Database enabled for edition-

based redefinition

• MySQL Database

Port Enter the port number for your database. The default

port number for Oracle databases is 1521.

• Oracle Database

• Oracle Database enabled for edition-

based redefinition

• Microsoft SQL Server

• IBM DB2

• MySQL Database

Service

Name

Specify the service name for the database. Typically, the

service name is the same as the global database name.

If you are unsure what the service name for your

database is, you can obtain it from the

SERVICE_NAMES

parameter in the initialization parameter file of the

database. If the initialization parameter file does not

contain the

SERVICE_NAMES

parameter, then the service

name is the same as the global database name, which is

specified in the

DB_NAME

and

DB_DOMAIN

parameters.

For Oracle RAC databases, specify the service name of

one of the nodes in this field. For example:

examplehost.exampledomain.com

• Oracle Database

• Oracle Database enabled for edition-

based redefinition

Username Enter the user name for your database. • Oracle Database

• Oracle Database enabled for edition-

based redefinition

• Microsoft SQL Server

• IBM DB2

• MySQL Database

Password Enter the password for your database user.

Password must not be more than 31 characters long and

can contain alphanumeric, pound, hash, comma,

underscore characters. It should not begin with a

number or a special character.

• Oracle Database

• Oracle Database enabled for edition-

based redefinition

• Microsoft SQL Server

• IBM DB2

• MySQL Database

Appendix A

Database Connection Details

A-5

Element Description Database Types

Role Select the database user's role from the drop-down list:

• Normal

• SYSDBA

• Oracle Database

• Oracle Database enabled for edition-

based redefinition

Unicode

Support

Select the Unicode Support from the drop-down list:

• Yes

• No

Microsoft SQL Server

Server Name For Microsoft SQL server, type one of the following:

• Hostname

• IP address

• Complete servername in host\server format.

For IBM DB2, type the IP address of the server.

• Microsoft SQL Server

• IBM DB2

Database

Name

Type the database name. It is case-sensitive. • Microsoft SQL Server

• IBM DB2

• MySQL Database

Connect

String

For Oracle Databases and Oracle Database enabled for

edition-based redefinition types, type Connect String in

one of the following formats:

• <host>:<port>/<service>

• <host>:<port>:<SID>

• DESCRIPTION=(ADDRESS=(host=host_name)

(protocol=protocol_name)(port=port_number))

(CONNECT_DATA=(SERVICE_NAME=service_na

me)))

For Microsoft SQL Server, IBM DB2, and MySQL

Database, type Connect String in <Sever name>/

<host>:<port>:<databaseName> format.

• Oracle Database

• Oracle Database enabled for edition-

based redefinition

• Microsoft SQL Server

• IBM DB2

• MySQL Database

Appendix A

Database Connection Details

A-6

Note:

From Oracle Data Integrator Release 12.2.1.4.0 and later, MySQL connector is

upgraded to version 8.0.XX. Due to this, the new MySQL connector performs time

offset adjustments on date-time value. For this function to work, you have to either

configure your MySQL server with a canonical time zone which is recognized by

Java or override the server's time zone by setting the connection property

serverTimezone, for example, serverTimezone=UTC or any other. The new jdbc

URL is in the following format:

jdbc:mysql://<host>:<port>/<databasename>?serverTimezone=<java

recognizable time

When you connect to a MySQL Database, you have to provide additional

information, depending on the Connection String format you use:

• Connection Parameters: In this format, provide the following additional

parameter:

serverTimezone=<java recognizable time zone>

along with

For example:

<databasename>?serverTimezone=<java recognizable time zone>

• Connect String: In this format, provide the following URL:

jdbc:mysql://<host>:<port>/<database name>?serverTimezone=<java

recognizable time zone>

Click Next after you have entered the connection credentials for your database. A screen

indicating the progress of the installer establishing the connection with the specified database

appears. If an error occurs while the connection is being established, the error message

appears in the Messages field on the Database Connection Details screen.

Specific database requirements for the various schemas can be found in the Oracle Fusion

Middleware System Requirements and Specifications document.

View the System Requirements and Supported Platforms for Oracle Fusion Middleware 12c

document for other certified databases that can be used with RCU. This document is

available on the Oracle Fusion Middleware Supported System Configurations page.

Connection Credentials for Microsoft SQL Server Databases

To connect to a Microsoft SQL Server database, you need to specify connection information

about the database, such as Unicode Support, Server Name, Port, Database Name,

Username, and Password.

Field

Description

Unicode Support Select Yes or No from the drop-down list.

Server Name Enter the host name, IP address, or complete server name in host\server format of the

server where your database is running.

Port Enter the port number for your database.

Database Name Specify the name of your database.

Appendix A

Database Connection Details

A-7

Field Description

Username Specify the name of a user with administrator privileges.

Password Enter the password for your database user.

Connection Credentials for IBM DB2 Databases

To connect to an IBM DB2 database, you need to specify connection information about

the database, such as Server Name, Port, Database Name, Username, and

Password.

Field Description

Server Name Enter the host name, IP address, or complete server name in host\server format of the

server where your database is running.

Port Enter the port number for your database.

Database Name Specify the name of your database.

Username Specify the name of a user with DB Owner privileges. The default user name for IBM DB2

databases is

db2admin

Password Enter the password for your database user.

Connection Credentials for an Autonomous Transaction Processing

Database

To connect to an Autonomous Transaction Processing database (both Oracle

Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous

Transaction Processing-Shared (ATP-S)), you need to specify connection information

about the database, such as Username and Password.

Appendix A

Database Connection Details

A-8

Field Description

Connect String for

Autonomous

Transaction

Processing database

(both Oracle

Autonomous

Transaction

Processing-

Dedicated (ATP-D)

and Oracle

Autonomous

Transaction

Processing-Shared

(ATP-S))

Enter connect string in the format:

jdbc:oracle:thin:@TNS_alias?TNS_ADMIN=<path

of the wallet files, ojdbc.properties, and tnsnames.ora>

In the connect string, you must pass

TNS_alias

as the database name found in

tnsnames.ora

, and

TNS_ADMIN

property to the location of the wallet files,

ojdbc.properties

, and

tnsnames.ora

Note: For an Oracle Autonomous Transaction Processing-Shared (ATP-S) database, you

must use only one of the database service names,

<databasename>_tpurgent

<databasename>_tp

, specified in

tnsnames.ora

. For database service name details, see

Database Service Names for Autonomous Transaction Processing and Autonomous JSON

Database in Using Oracle Autonomous Database on Shared Exadata Infrastructure.

Example connect string for Oracle Autonomous Transaction Processing-Dedicated (ATP-D)

database::

jdbc:oracle:thin:@dbname_medium?TNS_ADMIN=/users/test/

wallet_dbname/

Example connect string for Oracle Autonomous Transaction Processing-Shared (ATP-S)

database:

jdbc:oracle:thin:@dbname_tp?TNS_ADMIN=/users/test/wallet_dbname/

In case of Oracle Internet Directory, use the connect string specified in

tnsnames.ora

(located in $ORACLE_HOME/network/admin) for your service name or

TNS_alias

Example connect string for Oracle Internet Directory for Oracle Autonomous Transaction

Processing-Dedicated (ATP-D) database:

(DESCRIPTION=(CONNECT_TIMEOUT=120)(RETRY_COUNT=20)(RETRY_DELAY=3)

TRANSPORT_CONNECT_TIMEOUT=3)

(ADDRESS_LIST=(LOAD_BALANCE=on)(ADDRESS=(PROTOCOL=<protocol_name>)

(HOST=<host_name>)

(PORT=<port_number>)))

(CONNECT_DATA=(SERVICE_NAME=<service_name>.atp.oraclecloud.com)))

Example connect string for Oracle Internet Directory for Oracle Autonomous Transaction

Processing-Shared (ATP-S) database:

(DESCRIPTION=(CONNECT_TIMEOUT=120)=(RETRY_COUNT=20)(RETRY_DELAY=3)

(ADDRESS=(PROTOCOL=<protocol_name>)

(PORT=<port_number>)(HOST=<host_name>))

(CONNECT_DATA=(SERVICE_NAME=<service_name>.adb.oraclecloud.com))

(security=(ssl_server_cert_dn="CN=example.com,

OU=<organizational_unit>, O=<organization>, L=<city>, ST=<state>,

C=<country>")))

Username

Specify the name of a user with administrator privileges.

Password Enter the password for your database user.

Password must be minimum 12 characters, and must contain at least one uppercase, one

lower case, and one number.

Role Select Normal from the drop-down list.

When you select Normal, a warning message 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.

Appendix A

Database Connection Details

A-9

Select Components (for Create Operation)

Use the Select Components screen to select the components for which you want to

create schemas, and specify a prefix to group them together.

When you select Create Repository on the Create Repository screen, the Select

Component screens appears.

The following table describes the elements on this screen.

Element Description

Select existing prefix Use this option to create schemas by using an existing prefix, which you can select

from the drop-down list. If you select this option, you can only create schemas that

do not already have this prefix in the database. For example, if

DEV_MDS

already

exists, you are unable to select the MDS schema on the page to create it again).

Create new prefix Use this option to create a new custom prefix that can be used to group your

schema together. The prefix name must be a minimum of one character in length

and cannot exceed 12 alphanumeric characters (0-9, a-z, or A-Z) in length (not

including the underscore character). Prefixes should not start with a number. No

whitespace or special characters are allowed.

You can edit the schema name or prefix by clicking the item that you want to change

in the Schema Owner column and editing the table cell directly.

For more information about custom prefixes, see About Custom Prefixes.

Component Use the Component column in the table to select the component schema that you

want to create.

When you select a component, any other components that may be required by the

component you select are also selected. For example, if you select Oracle Platform

and Security Services, then the Audit Services schema is also automatically

selected, if it has not already been selected. The Audit Services schema is required

by the Oracle Platform and Security Services schema.

If a component has a plus sign (+) next to its name, then there are sub components

available. Click on the plus sign (+) to expand the category to view all sub

components. If you want to select a component with all its subcomponents, click on

the top-most box with the plus sign (+).

If you are creating component schemas on an IBM DB2 database, see important

information in Additional Requirements for IBM DB2 Databases.

Schema Owner This column shows the name of the schema owner for each component (custom

prefix and schema name). You can edit the schema owner value by clicking the item

that you want to change in this column and editing the table cell directly.

Note:

You must remember the Schema Owner name for the components that you

are installing; you need this information during the configuration phase of

your Oracle Fusion Middleware product installation. Oracle recommends that

you write this value down.

Appendix A

Select Components (for Create Operation)

A-10

Click Next when you are finished specifying your prefix and schema names, and when you

are finished selecting components. The screen indicating the progress of component

prerequisite checks before schema creation appears.

If an error occurs during the prerequisite checking, the error messages appear in the

Messages field on the Select Components screen.

Click OK to dismiss this screen.

Select Components (for Drop Operation)

Use the Select Components screen to select the prefix and the schemas that you want to

drop.

The Select Components screen appears if you selected Drop Repository on the Create

Repository screen.

The following table describes the elements on this screen:

Element Description

Select schemas with

prefix of

Use the drop-down list in this field to select an existing custom prefix.

Component Select the component schemas you want to remove.

Note:

Unlike create operations, schema dependencies are not

handled automatically by RCU for drop operations. When

you remove a schema, you must also remove the schemas

which depend on the schema you are removing. For

example, the Audit Services schema is required by the

Oracle Platform Security Services schema; if you remove

the Audit Services schema, the Oracle Platform Security

Services schema will no longer works.

Schema Owner This column shows the schema owner (custom prefix and schema name).

For drop operations, this column cannot be edited.

Click Next when you are finished. The screen indicating the progress of component

prerequisite checks appears.

If an error occurs during the prerequisite checking, the error message(s) appear in the

Messages field on the Select Components screen.

Click OK to dismiss this screen.

Schema Passwords

Use the Schema Passwords screen to specify the passwords for your schema owners; there

are three ways to specify schema passwords on this screen.

The following table describes the three ways that you can specify schema passwords:

Appendix A

Select Components (for Drop Operation)

A-11

Option Description

Use same password for all

schemas

Select this option if you want to use a single password for all schemas and

their auxiliary schemas. In the Password field, enter your password. Enter your

password again in the Confirm Password field.

Use main schema passwords

for auxiliary schemas

Select this option if you want to specify different passwords for the main

schemas, but still have the same password used for their respective auxiliary

schemas. If you select this option, only the main schemas are visible in the

table. For each schema, you must enter each schema's password in the

Schema Password column in the table, and enter the same password in the

Confirm Password column.

Specify different passwords for

all schemas

Select this option if you want to specify unique passwords for the main

schemas and auxiliary schemas. If you select this option, all main schemas

and auxiliary schemas are visible in the table. For each schema and auxiliary

schema, you must enter the password in the Schema Password column in the

table, and enter the same password in the Confirm Password column.

Note:

You must remember the passwords you enter on this screen; you need this

information during the configuration phase of your product installation. Oracle

recommends that you write down these values.

For an Autonomous Transaction Processing database (both Oracle

Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle

Autonomous Transaction Processing-Shared (ATP-S)), password must be

minimum 12 characters, and must contain at least one uppercase, one lower

case, and one number.

Custom Variables

If you are installing a product that requires custom variables, you will see the Custom

Variables screen. Use this 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.

• If you selected Oracle Data Integrator, the custom variables for Oracle Data

Integrator are visible.

• If you selected SOA Suite, the custom variables for Oracle SOA Suite are visible.

• If you selected WebCenter Portal - Analytics, the custom variable for Oracle

WebCenter Portal Analytics is visible.

• If you selected Oracle GoldenGate - Repository, the custom variables for Oracle

GoldenGate Studio are visible.

• If you selected Oracle Data Integrator, SOA Suite, and WebCenter Portal -

Analytics, the custom variables for Oracle Data Integrator, Oracle SOA Suite, and

Oracle WebCenter Portal Analytics are visible on this screen.

Appendix A

Custom Variables

A-12

For more information, see the following topics:

• Custom Variables for Oracle Data Integrator

For Oracle Data Integrator, use the Custom Variables screen to specify a password for

the supervisor user, the type of Work Repository to create, a password and unique name

for the Work Repository, and the length of the key to use for the encryption algorithm.

• Custom Variables for Oracle SOA Suite

For Oracle SOA Suite, use the Custom Variables screen to specify the database profile

that you want to use and whether or not you want to enable Healthcare Integration.

• Custom Variable for Oracle WebCenter Portal Analytics

For Oracle WebCenter Portal Analytics, use the Custom Variables screen to specify

whether or not you want to install Analytics with database partitioning enabled.

• Custom Variables for Oracle GoldenGate Studio

For Oracle GoldenGate Studio, use the Custom Variables screen to specify a password

for the supervisor user and the length of the key to use for the encryption algorithm.

Custom Variables for Oracle Data Integrator

For Oracle Data Integrator, use the Custom Variables screen to specify a password for the

supervisor user, the type of Work Repository to create, a password and unique name for the

Work Repository, and the length of the key to use for the encryption algorithm.

The custom variables for Oracle Data Integrator are described in the following table:

Variable Description

Supervisor Password Password of the supervisor user.

You must enter a password for the Supervisor Password and Confirm

Supervisor Password fields. These fields are required before you can

continue. The password should be between 6 and 12 characters.

Work Repository Type Specify how the Work Repository will be used:

•

Use Development (D) for creating a development repository. This type of

repository allows management of design-time objects such as data

models and projects (including interfaces, procedures, etc.) A

development repository also includes the run-time objects (scenarios and

sessions). This type of repository is suitable for development

environments.

•

Use Execution (E) for creating an execution repository: This type of

repository only includes run-time objects (scenarios, schedules and

sessions). It allows launching and monitoring of data integration jobs in

Operator Navigator. Such a repository cannot contain any design-time

artifacts. Designer Navigator cannot be used with it. An execution

repository is suitable for production environments.

This field is optional. The default value is D.

Work Repository Name A unique name for the Work Repository (for example:

DEVWORKREP1

This field is optional.

Work Repository Password Provide a password for the Work Repository. If you provide a password, you

must confirm the password on the following line.

The Work Repository Password and Confirm Work Repository Password

fields are optional.

Encryption Algorithm Select the encryption algorithmm, either

AES-128

AES-256

This field is optional. If this field is left blank, the default value is

AES-128

Appendix A

Custom Variables

A-13

Custom Variables for Oracle SOA Suite

For Oracle SOA Suite, use the Custom Variables screen to specify the database

profile that you want to use and whether or not you want to enable Healthcare

Integration.

The custom variables for Oracle SOA Suite are described in the following table:

Variable Description

Database Profile Specify the database profile that you want to use for Oracle SOA Suite. This

determines the size of the SOA database.

Use the drop-down list to specify the size. The available options are Small,

Medium, or Large. The default value is Small.

Healthcare Integration Specify whether you want to enable Healthcare Integration for Oracle SOA

Suite.

The default value is No.

Custom Variable for Oracle WebCenter Portal Analytics

For Oracle WebCenter Portal Analytics, use the Custom Variables screen to specify

whether or not you want to install Analytics with database partitioning enabled.

Specify

if you want to install Analytics with database partitioning enabled, or

if you

do not want to enable database partitioning. The default value is

Custom Variables for Oracle GoldenGate Studio

For Oracle GoldenGate Studio, use the Custom Variables screen to specify a

password for the supervisor user and the length of the key to use for the encryption

algorithm.

The custom variables for Oracle GoldenGate Studio are described in the following

table:

Variable Description

Supervisor Password Password of the supervisor user.

You must enter a password in the Supervisor Password and Confirm

Supervisor Password fields. These fields are required before you can

continue. The password should be between 6 and 12 characters.

Make a note of the password that you set on this screen; you need it later on

when you provide your Oracle GoldenGate Studio connection information to

connect to the repository after you start Oracle GoldenGate Studio.

Encryption Algorithm Select the encryption algorithm, either

AES-128

AES-256

This field is optional. If this field is left blank, the default value is

AES-128

Appendix A

Custom Variables

A-14

Map Tablespaces

Use the Map Tablespaces screen to configure the desired tablespace mapping for the

schemas that you want to create.

This screen only appears if you selected the Create Repository option on the Create

Repository screen.

Click Next when you are finished with your tablespace information. The screen prompting

you to confirm the creation of tablespaces for any new schemas appears.

Note:

• RCU only creates tablespaces for those components associated with RCU.

• The Encrypt Tablespace check box appears on this screen only if Transparent

Data Encryption (TDE) is enabled in the database (Oracle or Oracle EBR) when

RCU is started. For more information about encrypting Tablespaces, see

Encrypting Tablespaces.

• When you create schemas on ATP-D database, you may receive tablespace

creation error on the Map Tablespaces screen. For more information, see

Troubleshooting Tips for Schema Creation on an Autonomous Transaction

Processing Database.

• For an Oracle Autonomous Transaction Processing-Shared (ATP-S) database,

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.

Click OK to continue. The screen indicating the progress of the tablespace creation appears.

Click Stop to cancel tablespace creation. When the tablespaces are created, click OK to

dismiss this window.

See the following topics for more about the features and options on the Map Tablespaces

screen:

• Default Tablespace Mappings

In the Default Tablespace and Temp Tablespace columns, you can click on the

tablespace cell to select from a list of available additional tablespace names.

• Changing Default and Temporary Tablespaces

You can change the default tablespaces and the temporary tablespaces for the

components.

• Viewing and Changing Additional Tablespaces

To view and change additional tablespaces associated with the selected components,

click the Additional Tablespaces button. Only those components with additional

tablespaces as defined in the configuration files appear on this screen.

• Managing Tablespaces and Datafiles

To manage your tablespaces and datafiles, click the Manage Tablespaces button.

Appendix A

Map Tablespaces

A-15

• Encrypting Tablespaces

Select the Encrypt Tablespace check box on the Map Tablespaces screen to

encrypt all the new tablespaces that are created by RCU.

Default Tablespace Mappings

In the Default Tablespace and Temp Tablespace columns, you can click on the

tablespace cell to select from a list of available additional tablespace names.

The default tablespace mapping for each component are shown in About Repository

Creation Utility Schemas, IDs, and Tablespaces.

Changing Default and Temporary Tablespaces

You can change the default tablespaces and the temporary tablespaces for the

components.

You can have your components use as many or as few tablespaces as desired to suit

your configuration.

To change the default tablespace for a component, select the tablespace name in the

Default Tablespace column, then select the tablespace name that you want to use

from the drop-down list.

To change the temporary tablespace for a component, select the tablespace name in

the Temp Tablespace column, then select the tablespace name that you want to use

from the drop-down list.

Note:

For an Oracle Autonomous Transaction Processing-Shared (ATP-S)

database, 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.

Viewing and Changing Additional Tablespaces

To view and change additional tablespaces associated with the selected components,

click the Additional Tablespaces button. Only those components with additional

tablespaces as defined in the configuration files appear on this screen.

Some components have additional tablespaces associated with their schemas. If this

is the case, the Additional Tablespaces button appears on this screen. If none of the

selected components have additional tablespaces, then this button will not appear.

To change the tablespace you want to use for a component, click in the Tablespace

Name column and select the tablespace that you want to use from the drop-down list.

Appendix A

Map Tablespaces

A-16

Note:

For an Oracle Autonomous Transaction Processing-Shared (ATP-S) database,

override the tablespace name, and select DATA from the drop-down list in the

Tablespace Name column.

Managing Tablespaces and Datafiles

To manage your tablespaces and datafiles, click the Manage Tablespaces button.

The following topics are covered in this section:

• Adding, Modifying, and Removing Tablespaces

Only tablespaces that are created by RCU can be modified or removed. Tablespaces that

existed before RCU was launched are visible on this screen but are grayed out and

cannot be modified or removed.

• Adding, Modifying, and Removing Datafiles

In the Datafiles section, specify the datafiles that make up the selected tablespace.

Adding, Modifying, and Removing Tablespaces

Only tablespaces that are created by RCU can be modified or removed. Tablespaces that

existed before RCU was launched are visible on this screen but are grayed out and cannot

be modified or removed.

Only tablespaces that are used by a component are created. You can specify a new

tablespace here, but unless it is actually used by a component it is not created.

To modify a tablespace, select the tablespace name on the left-hand portion of the screen,

and edit the fields as described in the following table:

Field Description

Name Edit the tablespace name in this field to change the name of your tablespace.

Type Specify whether you want this tablespace to be a temporary tablespace or permanent

tablespace.

Block Size (KB) Specify the block size (in Kilobytes) to be used for data retrieval.

Storage Type

Select Use Bigfile Tablespace if you want to create a bigfile tablespace; this is

typically used if you have single large files instead of multiple small files. Select Use

Automatic Segment Space Management if you want to use bitmaps to manage the

free space within segments.

To add a tablespace, click Add and specify the same details as above (for modifying a

tablespace) for your new tablespace.

To remove a tablespace, select the tablespace name from the navigation tree, then click

Remove. This tablespace is not created.

Adding, Modifying, and Removing Datafiles

In the Datafiles section, specify the datafiles that make up the selected tablespace.

To add a datafile, click the icon with the plus sign (+):

Appendix A

Map Tablespaces

A-17

The Add Datafile screen appears:

Provide the information described in the following table:

Field Description

File Name Specify the name of the datafile.

Note:

Datafile names with a dash or hyphen (-) character are

not permitted.

File Directory Specify the location where this datafile will reside.

Size Specify the initial size of the datafile. Use the drop-down list to specify the size in

kilobytes (KB), megabytes (MB), or gigabytes (GB).

Automatically extend

datafile when full

(AUTOEXTEND)

Select Automatically extend datafile when full (AUTOEXTEND) to automatically

extend the size of your datafile when it becomes full. In the Increment field, specify

the size by which your datafile should be increased each time it becomes full. Use

the drop-down list to specify the size in kilobytes (KB), megabytes (MB), or gigabytes

(GB).

If you want to limit maximum size of the datafile, specify this value in the Maximum

Size field.

Similarly, to modify or edit a datafile, select the icon next to the datafile name that you

want to edit, then click the icon with the pencil:

To delete a datafile, select the icon next to the datafile name that you want to delete,

then click the icon with the "X":

Encrypting Tablespaces

Select the Encrypt Tablespace check box on the Map Tablespaces screen to encrypt

all the new tablespaces that are created by RCU.

When you start RCU, the Encrypt Tablespace check box appears on the Map

Tablespaces screen only if you have TDE (Transparent Data Encryption) enabled in

the database (Oracle or Oracle EBR) when you start RCU. If TDE is not enabled, this

Appendix A

Map Tablespaces

A-18

check box does not appear. If TDE is enabled in the database and you provide the

—

encryptTablespace true

option, the check box is selected by default.

TDE tablespace encryption allows you to encrypt sensitive data stored in tablespaces. For

more information about Transparent Data Encryption, see Introduction to Transparent Data

Encryption in Oracle Database Advanced Security Guide.

Note:

When you select this option, all new tablespaces created by RCU are encrypted.

You cannot select specific tablespaces on this screen to be encrypted. Also,

tablespaces that were created before RCU was launched cannot be encrypted by

using this option.

Summary (for Create Operation)

On the Summary (for Create operation) screen, verify your information, then click Create to

begin schema creation.

Note:

When you create schemas on an Autonomous Transaction Processing database

(both Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle

Autonomous Transaction Processing-Shared (ATP-S)) database, you may receive

warnings in case of Oracle WebCenter Content, Oracle Internet Directory, and

Oracle Enterprise Scheduler and Oracle Managed File Transfer SOA products. For

more information, see Troubleshooting Tips for Schema Creation on an

Autonomous Transaction Processing Database.

The Summary screen appears when you select Create Repository on the Create Repository

screen.

Click Save Response File to save the RCU session to a text file (called a response file). The

response file collects all the information that you have provided in the RCU screens.

The values in a response file can be used exactly as-is (or modified as needed) to run RCU

at a later time. If you choose to run the graphical interface, the data provided in a response

file can be used to prepopulate the RCU screens. If you choose to run RCU from the

command line, you can use a response file to provide values for all valid command-line

parameters to RCU rather than directly specifying these parameters on the command line.

For more information, see Using Response Files.

When you click Save Response File, you see the Save Response File dialog box.

The following table describes the fields on this dialog box:

Appendix A

Summary (for Create Operation)

A-19

Element Description

Directory to save Response file

Specify the full path of a directory. This directory is

where the response file is saved. By default, RCU saves

the response file in the

$HOME/.rcu

directory.

Click Browse to search for a specific directory.

Save Passwords in Wallet

Select this option to securely store the passwords that

you entered on the RCU screens in an Oracle Wallet file.

For example, the schema passwords entered on the

Schema Passwords screen are saved to this file.

By default, this option is not selected. RCU does not

save your passwords unless you select this option.

You can use the wallet later in silent situations to pass

the necessary passwords to RCU without having to

directly enter your passwords on the command line. If a

wallet is not passed to RCU in silent mode, you are

prompted to enter the required passwords.

Click OK to generate the wallet (if selected) and response file in the given location and

return to the Summary screen.

Review the information on the Summary screen, and click Create to begin schema

creation. When you click Create, the operations summarized on this page are

performed.

While the schemas are being created, you will see the progress screen.

Click Stop to stop creating the schemas.

Summary (for Drop Operation)

On the Summary (for Drop operation) screen, verify your information, then click Drop

to drop the schemas.

If you select Drop Repository on the Create Repository screen, the Summary

screen appears.

Click Save Response File to save the RCU session to a text file (called a response

file). The response file collects all the information that you have provided in the RCU

screens.

The values in a response file can be used exactly as-is (or modified as needed) to run

RCU at a later time. If you choose to run the graphical interface, the data provided in a

response file can be used to prepopulate the RCU screens. If you choose to run RCU

from the command line, you can use a response file to provide values for all valid

command-line parameters to RCU rather than directly specifying these parameters on

the command line. For more information, see Using Response Files.

When you click Save Response File, you see the Save Response File dialog box.

The following table describes the fields on this dialog box:

Appendix A

Summary (for Drop Operation)

A-20

Element Description

Directory to save Response file

Specify the full path of a directory. This directory is

where the response file is saved. By default, RCU saves

the response file in the

$HOME/.rcu

directory.

Click Browse to search for a specific directory.

Save Passwords in Wallet

Select this option to securely store the passwords that

you entered on the RCU screens in an Oracle Wallet file.

For example, the schema passwords entered on the

Schema Passwords screen are saved to this file.

By default, this option is not selected. RCU does not

save your passwords unless you select this option.

You can use the wallet later in silent situations to pass

the necessary passwords to RCU without having to

directly enter your passwords on the command line. If a

wallet is not passed to RCU in silent mode, you are

prompted to enter the required passwords.

Click OK to generate the wallet (if selected) and response file in the given location and return

to the Summary screen.

Review the information on the Summary screen, and click Drop to begin the operations

summarized on this page.

While the schema(s) are being dropped, you will see the progress screen.

Click Stop if you want to cancel the operation.

Completion Summary (for Create Operation)

The Completion Summary (for Create Operation) screen contains information about the log

files that were created from this RCU operation. You can click on the name of a particular log

file to view the contents of that file.

If you selected Create Repository on the Create Repository screen, Completion Summary

screen appears.

If there are any problems encountered during schema creation, you can troubleshoot the

issue by using the log files. For more information about using log files, see RCU Log Files.

If errors are encountered during a create operation, or if a create operation fails for any

component, the Cleanup for failed components and Drop tablespaces for failed

components check boxes that appear on this screen are selected by default.

If both options are selected, RCU performs cleanup operations and drops tablespaces for the

components that failed during the create operation.

If you select Cleanup for failed components but choose not to select Drop tablespaces for

failed components, the tablespaces for the failed components are retained during cleanup.

If you choose not to select the Cleanup for failed components check box, the cleanup of

failed components and tablespaces are skipped. You can clean up the failed components at a

later time by performing a drop operation for the failed components.

Review the information on this screen, then click Close to dismiss this screen.

Appendix A

Completion Summary (for Create Operation)

A-21

Completion Summary (for Drop Operation)

The Completion Summary (for Drop operation) screen contains information about the

log files that are created from this RCU operation. Note the log file names for each

component that are visible in the Logfile column.

If you select Drop Repository on the Create Repository screen, Completion

Summary screen appears.

By default, the main RCU log (

rcu.log

) and component log files are written to the

RCUdate_timestamp_random_number/logs

directory inside the temporary directory on

your system.

For example:

• On UNIX operating systems:

/tmp/RCUdate_timestamp_random_number/logs

• On Windows operating systems:

C:\Users\user_name\AppData\Local\Temp\RCUdate_timestamp_random_number\

logs

Click rcu.log to view the contents of the main RCU log in a separate window.

If there are any problems encountered during schema creation, you can troubleshoot

the issue using the log files. For more information about using log files, see

Troubleshooting Repository Creation Utility.

Review the information on this screen, then click Close to dismiss this screen.

Appendix A

Completion Summary (for Drop Operation)

A-22

About Repository Creation Utility Schemas,

IDs, and Tablespaces

Before you run RCU, make sure you understand the available schemas that can be created

by using RCU, and also their component IDs and dependencies.

Following sections explains about the RCU schemas and its dependencies:

• Repository Creation Utility Schemas, IDs, and Tablespaces

Each schema that can be created by using RCU has a schema owner, component ID,

and default tablespace mappings. You should also be aware of schema dependencies

when you create or drop schemas.

Repository Creation Utility Schemas, IDs, and Tablespaces

Each schema that can be created by using RCU has a schema owner, component ID, and

default tablespace mappings. You should also be aware of schema dependencies when you

create or drop schemas.

Table B-1 lists the schemas along with their component IDs, tablespace mappings, and

dependencies.

The Schema Owner is the name of the schema that you see in RCU, and is also the name

that you must provide in the Oracle Fusion Middleware Configuration Wizard on the JDBC

Component Schema screen, prepended by the custom prefix.

The Component ID is the value that you must specify with the

-component

parameter when

you create or drop schemas from the command line.

Note:

Not all schemas are supported on all database types. For more information about

supported schemas, see Repository Creation Utility Requirements in the Oracle

Fusion Middleware System Requirements and Specifications document.

Table B-1 Schema Component IDs, Tablespace Mappings, and Dependencies

Component Schema

Owner

Component ID Default

Tablespace

Temp

Tablespace

Dependencies

AS Common Schemas

Metadata Services

MDS MDS MDS IAS_TEMP

None

B-1

Table B-1 (Cont.) Schema Component IDs, Tablespace Mappings, and Dependencies

Component Schema

Owner

Component ID Default

Tablespace

Temp

Tablespace

Dependencies

Audit Services

IAU IAU IAU IAS_TEMP

Audit Services

Append

(

IAU_APPEND

)

Audit Services

Viewer

(

IAU_VIEWER

)

Audit Services Append

IAU_APPEND IAU_APPEND IAU IAS_TEMP

None

Audit Services Viewer

IAU_VIEWER IAU_VIEWER IAU IAS_TEMP

None

Oracle Platform Security

Services

OPSS OPSS IAS_OPSS IAS_TEMP

Audit Services

(

IAU

)

Audit Services

Append

(

IAU_APPEND

)

Audit Services

Viewer

(

IAU_VIEWER

)

User Messaging Service

UMS UCSUMS IAS_UMS IAS_TEMP

Metadata

Services (

MDS

)

WebLogic Services

WLS WLS WLS IAS_TEMP

None

Oracle Enterprise Scheduler

ESS ESS ESS IAS_TEMP

Metadata

Services (

MDS

)

Audit Services

(

IAU

)

Audit Services

Append

(

IAU_APPEND

)

Audit Services

Viewer

(

IAU_VIEWER

)

Oracle Platform

Security

Services (

OPSS

)

Common Infrastructure Services

(formerly Service Table)

STB STB STB IAS_TEMP

None

Oracle Data Integrator

Master and Work Repository

ODI_REPO ODI ODI_USER ODI_TEMP

SOA Suite

Appendix B

Repository Creation Utility Schemas, IDs, and Tablespaces

B-2

Table B-1 (Cont.) Schema Component IDs, Tablespace Mappings, and Dependencies

Component Schema

Owner

Component ID Default

Tablespace

Temp

Tablespace

Dependencies

SOA Infrastructure

SOAINFRA SOAINFRA SOAINFRA IAS_TEMP

Metadata

Services (

MDS

)

Audit Services

(

IAU

)

Audit Services

Append

(

IAU_APPEND

)

Audit Services

Viewer

(

IAU_VIEWER

)

Oracle Platform

Security

Services (

OPSS

)

User

Messaging

Service

(

UCSUMS

)

WebLogic

Services (

WLS

)

Managed File Transfer

MFT MFT MFT IAS_TEMP

Metadata

Services (

MDS

)

Audit Services

(

IAU

)

Audit Services

Append

(

IAU_APPEND

)

Audit Services

Viewer

(

IAU_VIEWER

)

Oracle Platform

Security

Services (

OPSS

)

User

Messaging

Service

(

UCSUMS

)

Oracle

Enterprise

Scheduler

(

ESS

)

Oracle Business Intelligence

Appendix B

Repository Creation Utility Schemas, IDs, and Tablespaces

B-3

Table B-1 (Cont.) Schema Component IDs, Tablespace Mappings, and Dependencies

Component Schema

Owner

Component ID Default

Tablespace

Temp

Tablespace

Dependencies

Business Intelligence Platform

BIPLATFORM BIPLATFORM BIPLATFORM IAS_TEMP

Metadata

Services (

MDS

)

Oracle Platform

Security

Services (

OPSS

)

Audit Services

(

IAU

)

Audit Services

Append

(

IAU_APPEND

)

Audit Services

Viewer

(

IAU_VIEWER

)

WebLogic

Services (

WLS

)

WebCenter Portal

Portal and Services

WEBCENTER WEBCENTER IAS_WEBCEN

TER

IAS_TEMP

Metadata

Services (

MDS

)

Oracle Platform

Security

Services (

OPSS

)

Audit Services

(

IAU

)

Audit Services

Append

(

IAU_APPEND

)

Audit Services

Viewer

(

IAU_VIEWER

)

Portlet Producers

PORTLET PORTLET IAS_PORTLE

IAS_TEMP

Oracle Platform

Security

Services (

OPSS

)

Audit Services

(

IAU

)

Audit Services

Append

(

IAU_APPEND

)

Audit Services

Viewer

(

IAU_VIEWER

)

Appendix B

Repository Creation Utility Schemas, IDs, and Tablespaces

B-4

Table B-1 (Cont.) Schema Component IDs, Tablespace Mappings, and Dependencies

Component Schema

Owner

Component ID Default

Tablespace

Temp

Tablespace

Dependencies

Analytics

ACTIVITIES ACTIVITIES IAS_ACTIVI

IAS_TEMP

Oracle Platform

Security

Services (

OPSS

)

Audit Services

(

IAU

)

Audit Services

Append

(

IAU_APPEND

)

Audit Services

Viewer

(

IAU_VIEWER

)

Discussions

DISCUSSIONS DISCUSSIONS IAS_DISCUS

IAS_TEMP

Oracle Platform

Security

Services (

OPSS

)

Audit Services

(

IAU

)

Audit Services

Append

(

IAU_APPEND

)

Audit Services

Viewer

(

IAU_VIEWER

)

WebCenter Content

Oracle WebCenter Content

Server — Search Only

OCSSEARCH CONTENTSEARC

OCSSEARCH OCSSEARCH_

TEMP

Common

Infrastructure

Services (

STB

)

WebLogic

Services (

WLS

)

Oracle WebCenter Content

Server — Complete

OCS CONTENT OCS OCS_TEMP

Common

Infrastructure

Services (

STB

)

Oracle Platform

Security

Services (

OPSS

)

Audit Services

(

IAU

)

Audit Services

Append

(

IAU_APPEND

)

Audit Services

Viewer

(

IAU_VIEWER

)

WebLogic

Services (

WLS

)

Appendix B

Repository Creation Utility Schemas, IDs, and Tablespaces

B-5

Table B-1 (Cont.) Schema Component IDs, Tablespace Mappings, and Dependencies

Component Schema

Owner

Component ID Default

Tablespace

Temp

Tablespace

Dependencies

Oracle WebCenter Enterprise

Capture

CAPTURE CAPTURE CAPTURE CAPTURE_TE

Common

Infrastructure

Services (

STB

)

Metadata

Services (

MDS

)

Oracle Platform

Security

Services (

OPSS

)

Audit Services

(

IAU

)

Audit Services

Append

(

IAU_APPEND

)

Audit Services

Viewer

(

IAU_VIEWER

)

WebLogic

Services (

WLS

)

WebCenter Sites

WCSITES WCSITES TS_WCSITES TS_TMP_WCS

ITES

Oracle Platform

Security

Services (

OPSS

)

Audit Services

(

IAU

)

Audit Services

Append

(

IAU_APPEND

)

Audit Services

Viewer

(

IAU_VIEWER

)

WebCenter Sites — Visitor

Services

WCSITES_VS WCSITESVS TS_WCSITES

_VS

TS_TMP_WCS

ITES_VS

Oracle Platform

Security

Services (

OPSS

)

Audit Services

(

IAU

)

Audit Services

Append

(

IAU_APPEND

)

Audit Services

Viewer

(

IAU_VIEWER

)

Oracle GoldenGate

Repository

OGGSTUDIO_R

EPO

OGGSTUDIO OGGSTUDIO_

USER

OGGSTUDIO_

TEMP

None

Oracle Enterprise Data Quality

(EDQ)

Appendix B

Repository Creation Utility Schemas, IDs, and Tablespaces

B-6

Table B-1 (Cont.) Schema Component IDs, Tablespace Mappings, and Dependencies

Component Schema

Owner

Component ID Default

Tablespace

Temp

Tablespace

Dependencies

EDQ Config Repository

EDQCONFIG EDQ_CONF EDQ_CONF EDQ_CONFTE

Oracle Platform

Security

Services (

OPSS

)

Audit Services

(

IAU

)

Audit Services

Append

(

IAU_APPEND

)

Audit Services

Viewer

(

IAU_VIEWER

)

EDQ Results Repository

EDQRESULTS EDQ_RES EDQ_RES EDQ_RESTEM

Oracle Platform

Security

Services (

OPSS

)

Audit Services

(

IAU

)

Audit Services

Append

(

IAU_APPEND

)

Audit Services

Viewer

(

IAU_VIEWER

)

EDQ Config

Repository

(

EDQ_CONF

)

EDQ Staging Repository

EDQSTAGING EDQ_STAGING EDQ_STAGIN

EDQ_STAGIN

GTEMP

Oracle Platform

Security

Services (

OPSS

)

Audit Services

(

IAU

)

Audit Services

Append

(

IAU_APPEND

)

Audit Services

Viewer

(

IAU_VIEWER

)

EDQ Config

Repository

(

EDQ_CONF

)

EDQ Results

Repository

(

EDQ_RES

)

Oracle Access Manager (OAM)

Appendix B

Repository Creation Utility Schemas, IDs, and Tablespaces

B-7

Table B-1 (Cont.) Schema Component IDs, Tablespace Mappings, and Dependencies

Component Schema

Owner

Component ID Default

Tablespace

Temp

Tablespace

Dependencies

Oracle Access Manager

OAM OAM OAM OAM_TEMP

Common

Infrastructure

Services (

STB

)

Metadata

Services (

MDS

)

Oracle Platform

Security

Services (

OPSS

)

Audit Services

(

IAU

)

Audit Services

Append

(

IAU_APPEND

)

Audit Services

Viewer

(

IAU_VIEWER

)

WebLogic

Services (

WLS

)

Oracle Identity Manager (OIM)

Oracle Identity Manager

OIM OIM OIM OIM_TEMP

Common

Infrastructure

Services (

STB

)

Metadata

Services (

MDS

)

Oracle Platform

Security

Services (

OPSS

)

SOA

Infrastrucure

(SOAINFRA)

Audit Services

(

IAU

)

Audit Services

Append

(

IAU_APPEND

)

Audit Services

Viewer

(

IAU_VIEWER

)

User

Messaging

Service

(

UCSUMS

)

WebLogic

Services (

WLS

)

Oracle Internet Directory (OID)

Appendix B

Repository Creation Utility Schemas, IDs, and Tablespaces

B-8

Table B-1 (Cont.) Schema Component IDs, Tablespace Mappings, and Dependencies

Component Schema

Owner

Component ID Default

Tablespace

Temp

Tablespace

Dependencies

Oracle Internet Directory

ODS ODS OLTS_DEFAU

IAS_TEMP

Oracle Platform

Security

Services (

OPSS

)

Audit Services

(

IAU

)

Audit Services

Append

(

IAU_APPEND

)

Audit Services

Viewer

(

IAU_VIEWER

)

WebLogic

Services (

WLS

)

Common

Infrastructure

Services (

STB

)

If Oracle

Internet

Directory in

configured in a

standalone

mode, only the

Common

Infrastructure

Service (STB)

schema is

applicable.

For more information about the Service Table schema, see About the Service Table Schema.

As an example, Table B-2 provides the schema details for Oracle HTTP Server configuration.

Table B-2 Schemas for Oracle HTTP Server Configured in WebLogic Server Domain

Component Schema Schema Owner

LocalSvcTbl Schema

STB

WLS Schema

WLS_RUNTIME

OPSS Audit Schema

IAU_APPEND

OPSS Audit Viewer Schema

IAU_VIEWER

OPSS Schema

OPSS

Appendix B

Repository Creation Utility Schemas, IDs, and Tablespaces

B-9

Extending Repository Creation Utility to

Configure Custom Application Repositories

You can use configuration XML files to generate custom schema creation and deletion

scripts.

RCU provides an XML-based framework for component owners to plug in your schema

creation and deletion scripts into RCU. The following topics provide some details of the

configuration XML files and script-writing guidelines that are used to integrate your

components with RCU:

• RCU Integration Options

RCU provides several options for integrating component scripts.

• RCU Configuration Files

RCU provides several configuration file types for component integration.

• RCU Script Writing Guidelines

Use these guidelines when writing RCU scripts.

RCU Integration Options

RCU provides several options for integrating component scripts.

RCU JDBC Engine Compliant SQL*Plus Scripts is the recommended option for integrating

component scripts. SQL*Plus and External Processes are only intended for integrating

Legacy or Classic components such as Oracle Portal 10g or Identity Management.

Components that have a dependency on SQL*Plus scripts cannot be loaded with RCU when

running from the installed Oracle home. They can only be used when running RCU from CD.

• RCU JDBC Engine Compliant SQL*Plus Scripts

The RCU JDBC Engine emulates a set of SQL*Plus features over JDBC. This set is

broad enough to cover the requirements of schema creation.

• Pure JDBC Scripts

This option is recommended for non-Oracle databases (for Oracle databases, RCU

JDBC Engine Compliant SQL*Plus scripts should be used).

• SQL*Plus Scripts

This option is mainly for the consumption of legacy components that need to be loaded

from RCU.

• External Processes

This option is provided only for those components that have their own configuration tool

for schema creation, like OPCA (Oracle Portal 10g).

• Java Code Using JavaAction

This option is provided to components that have Java code, which can accept a JDBC

connection and execute SQL statements.

C-1

RCU JDBC Engine Compliant SQL*Plus Scripts

The RCU JDBC Engine emulates a set of SQL*Plus features over JDBC. This set is

broad enough to cover the requirements of schema creation.

Your component teams can integrate existing SQL*Plus scripts with a few minor

changes.

The RCU JDBC Engine parses the SQL*Plus script to get individual statements and

then runs each statement over JDBC. Command-line arguments to scripts and

substitution using DEFINE variables are supported. Script can be nested, for example,

one script can call other scripts. Component teams can specify a list of expected

errors and fatal errors to RCU through configuration files and RCU would interpret

these when running the scripts.

These scripts are easy to maintain and use as they can be run in SQL*Plus in a

development environment. However, Oracle recommends that you also use the RCU

JDBCEngine tool in your development environment to ensure that these scripts run

properly when integrated with RCU.

Pure JDBC Scripts

This option is recommended for non-Oracle databases (for Oracle databases, RCU

JDBC Engine Compliant SQL*Plus scripts should be used).

Contents of the script file should be a valid PL/SQL block, which can be called with

Connection.prepareCall()

Connection.createStatement()

. Standard JDBC Bind

variables with '?' convention are supported.

Some disadvantages of this option are:

• No nested scripts, which can mean a larger number of scripts.

• May require significant rework for component teams to rewrite the scripts in this

format.

• Difficult to maintain as every DDL statement has to be wrapped with in EXECUTE

IMMEDIATE.

• Cannot be run by using SQL*Plus in a development environment.

• Less useful error support since the whole block would fail in case of any errors.

Below is an example:

<Command TYPE="INLINE">DROP USER %SCHEMA_USER% CASCADE</Command>

</Action>

And a second example:

oracle.ias.version.SchemaVersionUtil:utilSetComponentValid

</Command>

Appendix C

RCU Integration Options

C-2

</Parameters>

</Action>

SQL*Plus Scripts

This option is mainly for the consumption of legacy components that need to be loaded from

RCU.

Example:

<Command TYPE="SCRIPT">%SCRIPT_HOME%/oid/scripts/seedldap.sql</Command>

<Error Type="ORA-01918">user name does not exist</Error>

</IgnorableErrors>

</Action>

And a second example:

<Command TYPE="SCRIPT">%SCRIPT_HOME%/mds/sql/mds_user.sql</Command>

<Parameter TYPE="CmdLine">%SCHEMA_USER%</Parameter>

<Parameter TYPE="CmdLine">%SCHEMA_PASSWORD%</Parameter>

<Parameter TYPE="CmdLine">%DEFAULT_TABLESPACE%</Parameter>

<Parameter TYPE="CmdLine">%TEMPORARY_TABLESPACE%</Parameter>

</Parameters>

</Action>

External Processes

This option is provided only for those components that have their own configuration tool for

schema creation, like OPCA (Oracle Portal 10g).

This is not a recommended option for any new component, as this option cannot make use of

the RCU error handling framework.

Example:

<Command TYPE="SCRIPT">%RCU_HOME%/rcu/integration/cdb/config/bin/configure</Command>

<Parameter TYPE="ProcessInput">%JDBC_CONNECT_STRING%</Parameter>

<Parameter TYPE="ProcessInput">%DBADMIN_USER%</Parameter>

<Parameter TYPE="ProcessInput">%DBADMIN_PASSWORD%</Parameter>

<Parameter TYPE="ProcessInput">%PREFIX_NAME%</Parameter>

<Parameter TYPE="ProcessInput">%SCHEMA_USER%</Parameter>

<Parameter TYPE="ProcessInput">%SCHEMA_PASSWORD%</Parameter>

<Parameter TYPE="ProcessInput">%DEFAULT_TABLESPACE%</Parameter>

<Parameter TYPE="ProcessInput">%TEMPORARY_TABLESPACE%</Parameter>

</Parameters>

</Action>

Appendix C

RCU Integration Options

C-3

Java Code Using JavaAction

This option is provided to components that have Java code, which can accept a JDBC

connection and execute SQL statements.

This is generally used when huge amounts of data has to be seeded or Large Objects

(LOBs) need to be created.

Example:

oracle.ias.version.SchemaVersionUtil:utilCreateRegistryEntry

</Command>

<Parameter TYPE="String">%SCHEMA_USER%</Parameter>

</Parameters>

</Action>

A second example:

<Command TYPE="METHOD">oracle.webdb.config.PortalConfigAssistant:main</

Command>

<Parameter TYPE="StringArray">-mode PORTAL -s %SCHEMA_USER% -p

%DBADMIN_PASSWORD% -c %DB_HOSTNAME%:%DB_PORTNUMBER%:%DB_SERVICE% -silent -

verbose -owa -u %DEFAULT_TABLESPACE% -t %TEMPORARY_TABLESPACE% -d

%SCHEMA_USER%_DOC -l %SCHEMA_USER%_LOG -in %SCHEMA_USER%_IDX -demo -report -voh

%RCU_HOME% -log %RCU_LOG_LOCATION% -oh %SQLPLUS_HOME% -mrc %PREFIX_NAME% -rcu </

Parameter>

</Parameters>

</Action>

RCU Configuration Files

RCU provides several configuration file types for component integration.

The following are the configuration files defined by RCU:

• XML DTDs Defined by RCU

These are the XML DTDs defined by RCU; they are located in the ORACLE_HOME/

oracle_common/rcu/config directory.

• Component Repository Configuration File

A Component Repository Configuration File (

component.xml

) lists the

prerequisites and the list of scripts or actions that need to be performed to load or

drop a schema.

• Component List Configuration File

The Component List configuration file (

ComponentInfo.xml

) lists all the

components, their respective configuration files and their default user and

tablespace mappings.

Appendix C

RCU Configuration Files

C-4

• Soft-Prerequisite Support

If a particular

is not mandatory, then you can

use the soft-prerequisite option by setting the

SOFT

attribute to

TRUE

in the

ComponentInfo.xml

file

• Default Tablespaces Configuration File

The default tablespaces configuration file (

Storage.xml

) lists the components, for which,

tablespaces are created out-of-the-box. This file is located in the

ORACLE_HOME/

oracle_common/rcu/config

directory on UNIX operating systems or in the

ORACLE_HOME\oracle_common\rcu\config

directory on Windows operating systems.

XML DTDs Defined by RCU

These are the XML DTDs defined by RCU; they are located in the ORACLE_HOME/

oracle_common/rcu/config directory.

Following are the configuration files:

• Component Descriptor Configuration File

The Component Descriptor configuration file is called

ComponentInfo.dtd

and is located

in the ORACLE_HOME/oracle_common/rcu/config directory on UNIX operating

systems or in the ORACLE_HOME\oracle_common\rcu\config directory on Windows

operating systems.

• Repository Configuration File

The Repository configuration file is called

RepositoryConfig.dtd

and is located in the

ORACLE_HOME/oracle_common/rcu/config

directory on UNIX operating systems directory

or in the

ORACLE_HOME\oracle_common\rcu\config

directory on Windows operating

systems.

• Primary List of Supported Components

RCU maintains a primary list of supported components, which contains entries for each

supported component. Every time a new component is added, the primary list of

supported components is updated with the reference of the XML integration file, which is

provided by component owner.

• Storage Attributes Configuration File

RCU maintains the list of tablespaces or datafiles and their attributes that needs to be

created. This way the tablespaces and datafiles attributes can be modified externally.

Component Descriptor Configuration File

The Component Descriptor configuration file is called

ComponentInfo.dtd

and is located in

the ORACLE_HOME/oracle_common/rcu/config directory on UNIX operating systems or

in the ORACLE_HOME\oracle_common\rcu\config directory on Windows operating

systems.

Each component owner would provides a configuration file that adheres to the following DTD,

which lists the prerequisites and actions:

<?xml version="1.0" encoding="UTF-8" ?>

<!ENTITY % commonDTD SYSTEM "RCUCommon.dtd">

%commonDTD;

<!ELEMENT ComponentInfo (Display?, PrefixSettings?, Component*,

ComponentConfigFiles?, PrerequisiteDescriptor*,

ExecutionDescriptor*, FatalErrors?, IgnorableErrors?)>

<!ATTLIST ComponentInfo

Appendix C

RCU Configuration Files

C-5

VERSION CDATA #IMPLIED

TYPE CDATA #IMPLIED

RESOURCE_BUNDLE_PACKAGE CDATA #IMPLIED>

<!ELEMENT PrefixSettings (DetectQuery*)>

<!ATTLIST PrefixSettings

USE_SCHEMA_PREFIX (TRUE|FALSE) "TRUE"

USE_TABLESPACE_PREFIX (TRUE|FALSE) "TRUE">

<!ELEMENT ComponentConfigFiles (ConfigFile*)>

<!ATTLIST ConfigFile

ID CDATA #REQUIRED>

<!ELEMENT ConfigFile (#PCDATA)>

<!ELEMENT Component (ValidIfSet?, ValidIf?, Display,Consolidate*,SchemaBase*,

RepositoryConfigFile?, DetectQuery*, SchemaVersion?,

SchemaUser?, AdditionalSchemaUser*, Dependents?, DatabaseName?, Tablespaces?,

CustomVariables?)>

<!ATTLIST Component

ID CDATA #REQUIRED

PROGRESS_UNITS CDATA #IMPLIED

IS_GROUPING_COMPONENT (TRUE|FALSE) "FALSE"

DEFAULT_SELECTED (TRUE|FALSE) "FALSE"

CHILD_OF CDATA #IMPLIED

MANDATORY_SELECTED (TRUE|FALSE) "FALSE">

<!ELEMENT Display (#PCDATA)>

<!ATTLIST Display

NLS_ID CDATA #IMPLIED>

<!ELEMENT Consolidate EMPTY>

<!ATTLIST Consolidate

VALID (TRUE|FALSE) "FALSE"

DYNAMIC_OBJECTS (TRUE|FALSE) "FALSE">

<!ELEMENT SchemaBase (#PCDATA) >

<!ATTLIST SchemaBase

PARENT (TRUE|FALSE) "FALSE"

TBS_OVERRIDE (TRUE|FALSE) "FALSE"

TBS_OVERRIDE_USE_CUSTOM (TRUE|FALSE) "FALSE"

COMPONENT_DROP (TRUE|FALSE) "FALSE">

<!ELEMENT RepositoryConfigFile (#PCDATA)>

<!ELEMENT DetectQuery (#PCDATA)>

<!ATTLIST DetectQuery

OPERATION (CREATE|DROP|DATALOAD) 'CREATE'

<!ELEMENT SchemaVersion (#PCDATA)>

<!ELEMENT SchemaUser (#PCDATA)>

<!ATTLIST SchemaUser

USER_EDITABLE (TRUE|FALSE) "TRUE"

PREFIXABLE (TRUE|FALSE) "TRUE"

IS_CREATED (TRUE|FALSE) "TRUE"

MAX_LENGTH CDATA "30">

<!ELEMENT AdditionalSchemaUser (#PCDATA)>

<!ATTLIST AdditionalSchemaUser

STARTS_WITH_SCHEMA_USER (TRUE|FALSE) "TRUE"

COMPONENT_ID CDATA #IMPLIED>

<!ELEMENT Dependents (Dependent*)>

<!ELEMENT Dependent (#PCDATA)>

<!ATTLIST Dependent

COMPONENT_ID CDATA #REQUIRED

ALT_COMPONENT_ID CDATA #IMPLIED>

<!ELEMENT DatabaseName (#PCDATA)>

<!ELEMENT Tablespaces (Tablespace*)>

<!ATTLIST Tablespace TYPE (DEFAULT_TABLESPACE|TEMPORARY_TABLESPACE|

ADDITIONAL_TABLESPACE1|ADDITIONAL_TABLESPACE2|ADDITIONAL_TABLESPACE3|

ADDITIONAL_TABLESPACE4|ADDITIONAL_TABLESPACE5|ADDITIONAL_TABLESPACE6|

Appendix C

RCU Configuration Files

C-6

ADDITIONAL_TABLESPACE7|ADDITIONAL_TABLESPACE8|ADDITIONAL_TABLESPACE9|

ADDITIONAL_TABLESPACE10|ADDITIONAL_TABLESPACE11|ADDITIONAL_TABLESPACE12|

ADDITIONAL_TABLESPACE13|ADDITIONAL_TABLESPACE14|ADDITIONAL_TABLESPACE15|

ADDITIONAL_TABLESPACE16|ADDITIONAL_TABLESPACE17|ADDITIONAL_TABLESPACE18|

ADDITIONAL_TABLESPACE19|ADDITIONAL_TABLESPACE20|ADDITIONAL_TABLESPACE21|

ADDITIONAL_TABLESPACE22|ADDITIONAL_TABLESPACE23|ADDITIONAL_TABLESPACE24|

ADDITIONAL_TABLESPACE25|ADDITIONAL_TABLESPACE26|ADDITIONAL_TABLESPACE27|

ADDITIONAL_TABLESPACE28|ADDITIONAL_TABLESPACE29|ADDITIONAL_TABLESPACE30|

ADDITIONAL_TABLESPACE31) "DEFAULT_TABLESPACE">

<!ELEMENT Tablespace (Prompt, TablespaceName)>

<!ELEMENT Prompt (#PCDATA)>

<!ATTLIST Prompt NLS_ID CDATA #IMPLIED>

<!ELEMENT TablespaceName (#PCDATA)>

<!ELEMENT CustomVariables (Variable*, ValidationDescriptor*)>

<!ATTLIST Variable

MAX_LENGTH CDATA "30"

MIN_LENGTH CDATA "0"

MAX_VALUE CDATA #IMPLIED

MIN_VALUE CDATA #IMPLIED

OPERATION (CREATE|DROP|SYSTEM_LOAD|DATA_LOAD|BOTH) "BOTH"

DEFAULT_VALUE CDATA ""

PROMPT_ON_DEFAULT_VALUE (YES|NO) "YES"

VALUES CDATA "">

<!ELEMENT Variable (Name,Display)>

<!ELEMENT ValidationDescriptor (Action*)>

<!ATTLIST ValidationDescriptor

OPERATION (CREATE|DROP|SYSTEM_LOAD|DATA_LOAD|BOTH) "BOTH">

<!ELEMENT Name (#PCDATA)>

Repository Configuration File

The Repository configuration file is called

RepositoryConfig.dtd

and is located in the

ORACLE_HOME/oracle_common/rcu/config

directory on UNIX operating systems directory or

in the

ORACLE_HOME\oracle_common\rcu\config

directory on Windows operating systems.

<?xml version="1.0" encoding="UTF-8" ?>

<!ENTITY % commonDTD SYSTEM "RCUCommon.dtd">

%commonDTD;

<!ELEMENT RepositoryConfig (PrerequisiteDescriptor*, ExecutionDescriptor,

DeleteDescriptor?)>

<!ATTLIST RepositoryConfig

COMP_ID CDATA #REQUIRED>

<!ELEMENT DeleteDescriptor (Action*)>

Primary List of Supported Components

RCU maintains a primary list of supported components, which contains entries for each

supported component. Every time a new component is added, the primary list of supported

components is updated with the reference of the XML integration file, which is provided by

component owner.

This configuration file is called

RCUCommon.dtd

and is located in the

ORACLE_HOME/

oracle_common/rcu/config

directory on UNIX operating systems or in the

ORACLE_HOME\oracle_common\rcu\config

directory on Windows operating systems:

<?xml version="1.0" encoding="UTF-8" ?>

<!ELEMENT PrerequisiteDescriptor (DBPrerequisiteSet*, DBPrerequisite*)>

<!ATTLIST PrerequisiteDescriptor

Appendix C

RCU Configuration Files

C-7

<!ELEMENT DBPrerequisiteSet (ValidIfSet?, ValidIf?, PrereqSetErrorMsg?,

DBPrerequisite*)>

<!ATTLIST DBPrerequisiteSet

OPERATOR (OR|AND) "OR"

SOFT (TRUE|FALSE) "FALSE">

<!ELEMENT DBPrerequisite (ValidIfSet?, ValidIf?, PrereqIdentifier, PrereqValue,

PrereqErrorMsg?)>

<!ATTLIST DBPrerequisite

CustomSQL|TablespaceFreeMB) "CustomSQL"

DATA_TYPE (STRING|NUMBER|VERSION) "STRING"

COMPARE_OPERATOR (EQ|GT|LT|NE|GE|LE|COMPARE_VERSION) "EQ"

SOFT (TRUE|FALSE) "FALSE">

<!ELEMENT PrereqIdentifier (#PCDATA)>

<!ELEMENT PrereqValue (#PCDATA)>

<!ELEMENT PrereqSetErrorMsg (#PCDATA)>

<!ATTLIST PrereqSetErrorMsg

NLS_ID CDATA #IMPLIED>

<!ELEMENT PrereqErrorMsg (#PCDATA)>

<!ATTLIST PrereqErrorMsg

NLS_ID CDATA #IMPLIED>

<!ATTLIST PrereqValue

UNIT (KB|MB|NoUnit) 'NoUnit'>

<!ELEMENT ExecutionDescriptor (Action*)>

<!ATTLIST ExecutionDescriptor

TYPE (Load|PreLoad|PostLoad|DataLoad|PostDataLoad) "Load">

<!ELEMENT Action (ValidIfSet?, ValidIf?, Command, Parameters?, FatalErrors?,

IgnorableErrors?)>

<!ATTLIST Action

TYPE (JDBCSqlScript|JDBC|SQLPlus|HostCmd|Java) "JDBCSqlScript"

DB_VERSION CDATA #IMPLIED

PERCENT_PROGRESS CDATA #IMPLIED

CONNECT_AS_OWNER (TRUE|FALSE) "FALSE"

CONNECT_AS_REGISTRYOWNER (TRUE|FALSE) "FALSE"

RESET_SESSION (TRUE|FALSE) "FALSE">

<!ELEMENT Command (#PCDATA)>

<!ATTLIST Command

TYPE (SCRIPT|INLINE|METHOD) "SCRIPT">

<!ELEMENT Parameters (Parameter*)>

<!ELEMENT Parameter (#PCDATA)>

<!ATTLIST Parameter

StringArray|boolean) "CmdLine">

<!ELEMENT FatalErrors (Error*)>

<!ELEMENT IgnorableErrors (Error*)>

<!ELEMENT Error (#PCDATA)>

<!ATTLIST Error

Type CDATA #REQUIRED>

<!ELEMENT ValidIfSet (ValidIf*)>

<!ATTLIST ValidIfSet

DBTYPE CDATA #IMPLIED

DBVERSION CDATA #IMPLIED

OSNAME CDATA #IMPLIED

OPERATION_TYPE CDATA "ALL"

OPERATOR (OR|AND) "OR">

<!ELEMENT ValidIf (CustomQueryFilter?)>

<!ATTLIST ValidIf

DBTYPE CDATA #IMPLIED

DBVERSION CDATA #IMPLIED

Appendix C

RCU Configuration Files

C-8

OSNAME CDATA #IMPLIED

OPERATION_TYPE CDATA "ALL">

<!ELEMENT CustomQueryFilter (#PCDATA)>

<!ATTLIST CustomQueryFilter

DATA_TYPE (STRING|NUMBER) "STRING"

COMPARE_OPERATOR (EQ|GT|LT|NE|GE|LE|COMPARE_VERSION) "EQ"

VALUE CDATA #REQUIRED >

Storage Attributes Configuration File

RCU maintains the list of tablespaces or datafiles and their attributes that needs to be

created. This way the tablespaces and datafiles attributes can be modified externally.

The Storage Attributes configuration file is called

Storage.dtd

and is located in the

ORACLE_HOME/oracle_common/rcu/config

directory on UNIX operating systems) or in the

ORACLE_HOME\oracle_common\rcu\config

directory on Windows operating systems.

<?xml version="1.0" encoding="UTF-8" ?>

<!ELEMENT StorageAttributes ( ComponentStorageFiles?, TablespaceAttributes*)>

<!ELEMENT ComponentStorageFiles (StorageFile*)>

<!ATTLIST StorageFile

ID CDATA #REQUIRED>

<!ELEMENT StorageFile (#PCDATA)>

<!ELEMENT TablespaceAttributes (ValidIfSet?,

ValidIf?,Type?,DefaultTemp?,BlockSize?,ExtentSize?,PageSize?,AutoResize?,IncreaseSize?,

MaxSize?,Bigfile?,AutoSegmentSpaceManagement?, DatafilesList)>

<!ATTLIST TablespaceAttributes

NAME CDATA #REQUIRED

OMF (TRUE|FALSE) "FALSE">

<!ELEMENT ValidIfSet (ValidIf*)>

<!ATTLIST ValidIfSet

DBTYPE CDATA #IMPLIED

DBVERSION CDATA #IMPLIED

OSNAME CDATA #IMPLIED

OPERATOR (OR|AND) "OR">

<!ELEMENT ValidIf (CustomQueryFilter?)>

<!ATTLIST ValidIf

DBTYPE CDATA #IMPLIED

DBVERSION CDATA #IMPLIED

OSNAME CDATA #IMPLIED >

<!ELEMENT Type (#PCDATA)>

<!ELEMENT DefaultTemp (#PCDATA)>

<!ELEMENT BlockSize (#PCDATA)>

<!ELEMENT ExtentSize (#PCDATA)>

<!ELEMENT PageSize (#PCDATA)>

<!ATTLIST PageSize

UNIT (KB|NoUnit) 'KB'>

<!ELEMENT AutoResize (#PCDATA)>

<!ELEMENT IncreaseSize (#PCDATA)>

<!ATTLIST IncreaseSize

UNIT (KB|MB|GB) 'MB'>

<!ELEMENT MaxSize (#PCDATA)>

<!ATTLIST MaxSize

UNIT (KB|MB|GB) 'MB'>

<!ELEMENT Bigfile (#PCDATA)>

<!ELEMENT AutoSegmentSpaceManagement (#PCDATA)>

<!ELEMENT DatafilesList (DatafileAttributes+)>

<!ELEMENT DatafileAttributes (Size, Reuse?, AutoExtend?, Increment?, Maxsize?)>

<!ATTLIST DatafileAttributes

ID CDATA #REQUIRED>

Appendix C

RCU Configuration Files

C-9

<!ELEMENT Size (#PCDATA)>

<!ATTLIST Size

UNIT (KB|MB|GB) 'MB'>

<!ELEMENT Reuse (#PCDATA)>

<!ELEMENT AutoExtend (#PCDATA)>

<!ELEMENT Increment (#PCDATA)>

<!ATTLIST Increment

UNIT (KB|MB|GB) 'KB'>

<!ELEMENT Maxsize (#PCDATA)>

<!ATTLIST Maxsize

UNIT (KB|MB|GB) 'MB'>

Table C-1 RCU XML Configuration File Details

Element Attribute Description Supported Values

TablespaceAttributes Name Indicates the name of the

tablespace

—

Type — Indicates the type of the tablespace,

default or temporary

• Temporary

• Permanent

Bigfile — Indicates whether the tablespace is

a bigfile tablespace based on the

value

• True

• False

DatafilesList — Groups the datafile information —

DatafileAttributes:

Size

For example,

<DatafileAttributes

ID="%DATAFILE_LO

CATION%/mds.dbf">

100 </Size>

Indicates the size of tablespace Integer value

DatafileAttributes:

Reuse

— Allows to reuse an existing file • True

• False

DatafileAttributes:

AutoExtend

— Allows to enable or disable the

automatic extension of a new

datafile or tempfile based on value

• True

• False

DatafileAttributes:

Increment

— Indicates the size of the next extent

to be allocated to the object in bytes

Integer value

DatafileAttributes:

Maxsize

— Indicates maximum size of

segments

Value is -1, if maxsize is

unlimited, else specify required

value

— UNIT Indicates the unit of the tablespace

size

KB/MB/GB

Default value is MB.

AutoSegmentSpace

Management

Indicates dictionary managed

tablespace or local managed

tablespace based on value

• True

• False

'True' indicates dictionary

managed tablespace and

'False' indicates local managed

tablespace.

For more information about database tablespaces, see DBA_TABLESPACES in

Oracle® Database Reference guide.

Appendix C

RCU Configuration Files

C-10

Component Repository Configuration File

A Component Repository Configuration File (

component.xml

) lists the prerequisites and the

list of scripts or actions that need to be performed to load or drop a schema.

This file is provided and maintained by component owners. This configuration file is

referenced from the Component List Configuration File (

ComponentInfo.xml

Each

component.xml

file can be found in the

ORACLE_HOME/oracle_common/common/sql/

component/component.xml

directory on UNIX operating systems) or in the

ORACLE_HOME\oracle_common\common\sql\component\component.xml

directory on Windows

operating systems.

Component owners can use a set of predefined RCU parameters, which are substituted at

runtime by RCU based on user input. Here is the list of predefined parameters:

Table C-2 Predefined RCU Parameters

RCU Parameter Description

%ORACLE_HOME%

Location of the Oracle home directory.

%SCRIPT_HOME%

Location where scripts are located. It may be same as

ORACLE_HOME

%SCHEMA_USER%

Database schema name (owner) entered by the user in RCU.

%SCHEMA_PASSWORD%

Database schema password entered by the user in RCU.

%ADDITIONAL_SCHEMA_USER%

Additional schema users as defined in the

ComponentInfo.xml

file

%ADDITIONAL_SCHEMA_PASSWORD<n>%

Password for the additional schema users.

%DEFAULT_TABLESPACE%

Default tablespace assigned to the component by the user.

%TEMPORARY_TABLESPACE%

Temporary tablespace assigned to the component by the user.

%ADDITIONAL_TABLESPACE<n>%

Additional tablespace assigned to the component by the user. Up to

three additional tablespaces are supported.

%DEFAULT_PERMANENT_TABLESPACE%

Default permanent tablespace in the database (for example,

USERS

SYSTEM

) is none is set.

%DEFAULT_TEMP_TABLESPACE%

Default temporary tablespace in the database (for example,

TEMP

Oracle shipped databases or

SYSTEM

) if none is set.

%DATAFILE_LOCATION%

Default location where the tablespace/datafile will be created.

%JDBC_CONNECT_STRING%

JDBC connect string.

%PREFIX_NAME%

User-specified prefix for schema and tablespace names.

%CONNECTION%

Already-connected

java.sql.Connection

object to be passed into

JavaAction.

%DBADMIN_USER%

Database admin user that is provided on the Database Connection

Details.

%DBADMIN_PASSWORD%

Database admin user password that is provided on the Database

Connection Details.

%DBADMIN_ROLE%

Database admin user role that is provided on the Database

Connection Details.

%DB_HOSTNAME%

Database hostname that is provided on the Database Connection

Details.

%DB_SERVICE%

Database service name.

Appendix C

RCU Configuration Files

C-11

Table C-2 (Cont.) Predefined RCU Parameters

RCU Parameter Description

%DB_PORTNUMBER%

Database port number that is provided on the Database Connection

Details.

%RCU_HOME%

Directory where RCU is installed.

%SQLPLUS_HOME% ORACLE_HOME

where SQL*Plus is located.

%RCU_LOG_LOCATION%

Location of the directory where RCU log files are created.

%DATABASE_NAME%

Database name (for SQLServer database).

Below is a sample Component Repository Configuration file for OPSS (

opss.xml

which lists the series of prerequisites and actions:

<?xml version="1.0" encoding="UTF-8" ?>

<!DOCTYPE RepositoryConfig SYSTEM "RepositoryConfig.dtd">

<DBPrerequisite PREREQ_TYPE="TablespaceFreeMB" DATA_TYPE="NUMBER"

COMPARE_OPERATOR="GT">

<PrereqIdentifier>%DEFAULT_TABLESPACE%</PrereqIdentifier>

</DBPrerequisite>

<DBPrerequisite PREREQ_TYPE="TablespaceFreeMB" DATA_TYPE="NUMBER"

COMPARE_OPERATOR="GT">

<PrereqIdentifier>%TEMPORARY_TABLESPACE%</PrereqIdentifier>

</DBPrerequisite>

<DBPrerequisite PREREQ_TYPE="TablespaceFreeMB" DATA_TYPE="NUMBER"

COMPARE_OPERATOR="GT">

<PrereqIdentifier>%DEFAULT_TABLESPACE%</PrereqIdentifier>

</DBPrerequisite>

<DBPrerequisite PREREQ_TYPE="TablespaceFreeMB" DATA_TYPE="NUMBER"

COMPARE_OPERATOR="GT">

<PrereqIdentifier>%TEMPORARY_TABLESPACE%</PrereqIdentifier>

</DBPrerequisite>

</PrerequisiteDescriptor>

Appendix C

RCU Configuration Files

C-12

<DBPrerequisite PREREQ_TYPE="CustomSQL" DATA_TYPE="NUMBER"

COMPARE_OPERATOR="EQ">

select count(*) from v$session where username='%SCHEMA_USER%'

</PrereqIdentifier>

The schema owner %SCHEMA_USER% is connected to the

database. Please disconnect and try again.

</PrereqErrorMsg>

</DBPrerequisite>

<DBPrerequisite PREREQ_TYPE="CustomSQL" DATA_TYPE="NUMBER"

COMPARE_OPERATOR="EQ">

<PrereqIdentifier>select count(*) from v$session where

username='%SCHEMA_USER%'</PrereqIdentifier>

<PrereqErrorMsg NLS_ID="WC_USER_CONNECTED">The schema owner

%SCHEMA_USER% is connected to the database. Please disconnect and try again.</

PrereqErrorMsg>

</DBPrerequisite>

</PrerequisiteDescriptor>

<Command

TYPE="METHOD">oracle.ias.version.SchemaVersionUtil:utilCreateRegistryEntry</Command>

<Parameter TYPE="String">Oracle Platform Security Services</Parameter>

<Parameter TYPE="String">%PREFIX_NAME%</Parameter>

<Parameter TYPE="String">%SCHEMA_USER%</Parameter>

<Parameter TYPE="String">LOADING</Parameter>

</Parameters>

</Action>

<Command TYPE="SCRIPT">%SCRIPT_HOME%/opss/scripts/opss_user.sql</Command>

<Parameter TYPE="CmdLine">%SCHEMA_USER%</Parameter>

<Parameter TYPE="CmdLine">%SCHEMA_PASSWORD%</Parameter>

<Parameter TYPE="CmdLine">%DEFAULT_TABLESPACE%</Parameter>

<Parameter TYPE="CmdLine">%TEMPORARY_TABLESPACE%</Parameter>

</Parameters>

<Error Type="ORA-01918">user name does not exist</Error>

Appendix C

RCU Configuration Files

C-13

</IgnorableErrors>

</Action>

<Command TYPE="SCRIPT">%SCRIPT_HOME%/opss/scripts/oracleEbr/

opss_user.sql</Command>

<Parameter TYPE="CmdLine">%SCHEMA_USER%</Parameter>

<Parameter TYPE="CmdLine">%SCHEMA_PASSWORD%</Parameter>

<Parameter TYPE="CmdLine">%DEFAULT_TABLESPACE%</Parameter>

<Parameter TYPE="CmdLine">%TEMPORARY_TABLESPACE%</Parameter>

<Parameter TYPE="CmdLine">%EDITION_NAME%</Parameter>

</Parameters>

<Error Type="ORA-01918">user name does not exist</Error>

</IgnorableErrors>

</Action>

<Command TYPE="SCRIPT">%SCRIPT_HOME%/opss/scripts/sqlserver/

opss_user.sql</Command>

<Parameter TYPE="CmdLine">%SCHEMA_USER%</Parameter>

<Parameter TYPE="CmdLine">%SCHEMA_PASSWORD%</Parameter>

<Parameter TYPE="CmdLine">%DATABASE_NAME%</Parameter>

</Parameters>

</Action>

<Command TYPE="SCRIPT">%SCRIPT_HOME%/opss/scripts/db2/opss_user.sql</

Command>

<Parameter TYPE="CmdLine">%SCHEMA_USER%</Parameter>

<Parameter TYPE="CmdLine">%DEFAULT_TABLESPACE%</Parameter>

<Parameter TYPE="CmdLine">%SCHEMA_USER%</Parameter>

</Parameters>

</Action>

<Command TYPE="SCRIPT">%SCRIPT_HOME%/opss/scripts/opss_tables.sql</

Command>

<Parameter TYPE="CmdLine">%SCHEMA_USER%</Parameter>

</Parameters>

<Error Type="ORA-00942">table or view does not exist</Error>

</IgnorableErrors>

</Action>

<Command TYPE="SCRIPT">%SCRIPT_HOME%/opss/scripts/oracleEbr/

opss_tables.sql</Command>

<Parameter TYPE="CmdLine">%SCHEMA_USER%</Parameter>

<Parameter TYPE="CmdLine">%EDITION_NAME%</Parameter>

</Parameters>

<Error Type="ORA-00942">table or view does not exist</Error>

</IgnorableErrors>

Appendix C

RCU Configuration Files

C-14

</Action>

<Command TYPE="SCRIPT">%SCRIPT_HOME%/opss/scripts/sqlserver/opss_tables.sql</

Command>

<Parameter TYPE="CmdLine">%DATABASE_NAME%</Parameter>

</Parameters>

</Action>

<Command TYPE="SCRIPT">%SCRIPT_HOME%/opss/scripts/db2/opss_tables.sql</

Command>

<Parameter TYPE="CmdLine">%SCHEMA_USER%</Parameter>

<Parameter TYPE="CmdLine">%DEFAULT_TABLESPACE%</Parameter>

<Parameter TYPE="CmdLine">%TEMPORARY_TABLESPACE%</Parameter>

</Parameters>

</Action>

<Command TYPE="SCRIPT">%SCRIPT_HOME%/opss/scripts/opss_version.sql</Command>

<Parameter TYPE="CmdLine">%SCHEMA_USER%</Parameter>

</Parameters>

</Action>

<Command TYPE="SCRIPT">%SCRIPT_HOME%/opss/scripts/oracleEbr/opss_version.sql</

Command>

<Parameter TYPE="CmdLine">%SCHEMA_USER%</Parameter>

<Parameter TYPE="CmdLine">%EDITION_NAME%</Parameter>

</Parameters>

</Action>

<Command TYPE="SCRIPT">%SCRIPT_HOME%/opss/scripts/sqlserver/opss_version.sql</

Command>

<Parameter TYPE="CmdLine">%DATABASE_NAME%</Parameter>

</Parameters>

</Action>

<Command TYPE="SCRIPT">%SCRIPT_HOME%/opss/scripts/db2/opss_version.sql</

Command>

<Parameter TYPE="CmdLine">%SCHEMA_USER%</Parameter>

</Parameters>

</Action>

<Command TYPE="SCRIPT">%SCRIPT_HOME%/opss/scripts/opss_gencatalog.sql</

Command>

<Parameter TYPE="CmdLine">%SCHEMA_USER%</Parameter>

Appendix C

RCU Configuration Files

C-15

</Parameters>

</Action>

<Command TYPE="SCRIPT">%SCRIPT_HOME%/opss/scripts/sqlserver/

opss_gencatalog.sql</Command>

<Parameter TYPE="CmdLine">%DATABASE_NAME%</Parameter>

</Parameters>

</Action>

<Command TYPE="SCRIPT">%SCRIPT_HOME%/opss/scripts/db2/

opss_gencatalog.sql</Command>

<Parameter TYPE="CmdLine">%SCHEMA_USER%</Parameter>

</Parameters>

</Action>

<Command TYPE="SCRIPT">%SCRIPT_HOME%/opss/scripts/oracleEbr/

opss_gencatalog.sql</Command>

<Parameter TYPE="CmdLine">%SCHEMA_USER%</Parameter>

<Parameter TYPE="CmdLine">%EDITION_NAME%</Parameter>

</Parameters>

</Action>

<Action TYPE="JDBCSqlScript" CONNECT_AS_OWNER="TRUE"

PERCENT_PROGRESS="100">

<Command TYPE="SCRIPT">%SCRIPT_HOME%/opss/scripts/upgd_mgmt_schema.sql</

Command>

</Action>

<Command

TYPE="METHOD">oracle.ias.version.SchemaVersionUtil:utilSetComponentValid</

Command>

</Parameters>

</Action>

</ExecutionDescriptor>

<Command TYPE="INLINE">DROP USER %SCHEMA_USER% CASCADE</Command>

</Action>

<Command TYPE="INLINE">DROP USER %SCHEMA_USER% CASCADE</Command>

</Action>

<Command TYPE="SCRIPT">%SCRIPT_HOME%/opss/scripts/sqlserver/

Appendix C

RCU Configuration Files

C-16

opss_drop_table.sql</Command>

<Parameter TYPE="CmdLine">%DATABASE_NAME%</Parameter>

</Parameters>

</Action>

<Command TYPE="SCRIPT">%SCRIPT_HOME%/opss/scripts/sqlserver/

opss_drop_user.sql</Command>

<Parameter TYPE="CmdLine">%DATABASE_NAME%</Parameter>

<Parameter TYPE="CmdLine">%SCHEMA_USER%</Parameter>

</Parameters>

</Action>

<Command

TYPE="METHOD">oracle.sysman.assistants.common.dbutil.jdbc.DB2DropUtil:dropCompRepos</

Command>

<Parameter TYPE="String">%SCHEMA_USER%</Parameter>

</Parameters>

</Action>

<Command

TYPE="METHOD">oracle.ias.version.SchemaVersionUtil:utilDropRegistryEntry</Command>

<Parameter TYPE="String">%PREFIX_NAME%</Parameter>

</Parameters>

</Action>

</DeleteDescriptor>

</RepositoryConfig>

Component List Configuration File

The Component List configuration file (

ComponentInfo.xml

) lists all the components, their

respective configuration files and their default user and tablespace mappings.

This file also lists the high-level prerequisite checks and high level actions (like creating

schema_version_registry

table) to be done globally for all the components. Also, a list of

global Ignorable or Fatal errors can be specified.

Note:

RCU uses dynamic discovery to detect the available components. As a result, all of

the components might not be listed in the Component List configuration file.

This file can be found in the

ORACLE_HOME/oracle_common/rcu/config

directory on UNIX

operating systems or in the

ORACLE_HOME\oracle_common\rcu\config

directory on Windows

operating systems.

Appendix C

RCU Configuration Files

C-17

Below is a sample

ComponentInfo.xml

file:

<?xml version="1.0" encoding="UTF-8" ?>

<!DOCTYPE ComponentInfo SYSTEM "ComponentInfo.dtd" []>

<ComponentInfo VERSION="11.0.0.0" TYPE="AS_REPOSITORY"

RESOURCE_BUNDLE_PACKAGE="oracle.sysman.rcu.as.ASBundle">

<Display NLS_ID="ASREP_ID">Oracle AS Repository Components</Display>

Select distinct mrc_name from schema_version_registry

</DetectQuery>

Select distinct mrc_name from NULLID.schema_version_registry

</DetectQuery>

Select distinct mrc_name from ORACLEFMW.schema_version_registry

</DetectQuery>

</PrefixSettings>

<Display NLS_ID="AS_COMMON_ID">AS Common Schemas</Display>

</Component>

<Display NLS_ID="SOA">SOA Suite</Display>

</Component>

<Display NLS_ID="ODI_REPOSITORIES">Oracle Data Integrator</Display>

</Component>

<ConfigFile ID="MDS">%RCU_HOME%/../oracle_common/common/sql/mds/

mds_ComponentInfo.xml</ConfigFile>

<ConfigFile ID="IAU">%RCU_HOME%/../oracle_common/common/sql/iau/

iau_ComponentInfo.xml</ConfigFile>

<ConfigFile ID="OPSS">%RCU_HOME%/../oracle_common/common/sql/opss/

opss_ComponentInfo.xml</ConfigFile>

<ConfigFile ID="UCSMESSAGING">%RCU_HOME%/../oracle_common/common/sql/

ucs.messaging/ucs.messaging_ComponentInfo.xml</ConfigFile>

<ConfigFile ID="WLS">%RCU_HOME%/../oracle_common/common/sql/wlsservices/

wlsservices_ComponentInfo.xml</ConfigFile>

<ConfigFile ID="ESS">%RCU_HOME%/../oracle_common/common/sql/ess/

ess_ComponentInfo.xml</ConfigFile>

<ConfigFile ID="SOAINFRA">%RCU_HOME%/../soa/common/sql/soainfra/

soainfra_ComponentInfo.xml</ConfigFile>

<ConfigFile ID="ODI">%RCU_HOME%/../odi/common/sql/odi/odi_ComponentInfo.xml</

ConfigFile>

<ConfigFile ID="OER">%RCU_HOME%/../oer/common/sql/oer/oer_ComponentInfo.xml</

ConfigFile>

<ConfigFile ID="OWLCS">%RCU_HOME%/../oracle_common/common/sql/ucs.callcontrol/

ucs.callcontrol_ComponentInfo.xml</ConfigFile>

<ConfigFile ID="SVCTBL">%RCU_HOME%/../oracle_common/common/sql/svctbl/

svctbl_ComponentInfo.xml</ConfigFile>

<ConfigFile ID="MFT">%RCU_HOME%/../mft/common/sql/mft/mft_ComponentInfo.xml</

ConfigFile>

Appendix C

RCU Configuration Files

C-18

</ComponentConfigFiles>

<DBPrerequisite PREREQ_TYPE="InitParameter" DATA_TYPE="NUMBER"

COMPARE_OPERATOR="GE">

<PrereqIdentifier>SHARED_POOL_SIZE</PrereqIdentifier>

</DBPrerequisite>

<DBPrerequisite PREREQ_TYPE="InitParameter" DATA_TYPE="NUMBER"

COMPARE_OPERATOR="GE">

</DBPrerequisite>

</DBPrerequisiteSet>

<DBPrerequisite PREREQ_TYPE="CustomSQL" DATA_TYPE="NUMBER" COMPARE_OPERATOR="EQ"

SOFT="TRUE">

select 1 from dual where exists (select column_name from dba_tab_columns where

table_name(+) like 'V_$INSTANCE' and column_name(+) = 'EDITION') union select 0 from

dual where not exists (select column_name from dba_tab_columns where table_name(+)

like 'V_$INSTANCE' and column_name(+) = 'EDITION')

</CustomQueryFilter>

</ValidIf>

<PrereqIdentifier>select count (*) from V_$INSTANCE where EDITION = 'XE'</

PrereqIdentifier>

The database you are connecting is not a

supported version. Refer to the certification matrix for supported DB versions.

</PrereqErrorMsg>

</DBPrerequisite>

select 1 from dual where exists (select column_name from dba_tab_columns where

table_name(+) like 'V_$INSTANCE' and column_name(+) = 'EDITION') union select 0 from

dual where not exists (select column_name from dba_tab_columns where table_name(+)

like 'V_$INSTANCE' and column_name(+) = 'EDITION')

</CustomQueryFilter>

</ValidIf>

<PrereqIdentifier>select count(*) from product_component_version where

product like 'Oracle%Database%' AND version >= '12.0.0.0.0' AND version <

'12.1.0.1.0'</PrereqIdentifier>

The database you are connecting is not a supported

version. Enter Database with version equal to or higher than 12.1.0.1.0 in 12c. Refer

to the certification matrix for supported DB versions.

</PrereqErrorMsg>

</DBPrerequisite>

<DBPrerequisite PREREQ_TYPE="CustomSQL" DATA_TYPE="NUMBER" COMPARE_OPERATOR="EQ"

SOFT="TRUE">

Appendix C

RCU Configuration Files

C-19

select 1 from dual where exists (select column_name from dba_tab_columns

where table_name(+) like 'V_$INSTANCE' and column_name(+) = 'EDITION') union

select 0 from dual where not exists (select column_name from dba_tab_columns

where table_name(+) like 'V_$INSTANCE' and column_name(+) = 'EDITION')

</CustomQueryFilter>

</ValidIf>

<PrereqIdentifier>select count(*) from product_component_version where

product like 'Oracle%Database%' AND version > '12.1.0.1.9'</PrereqIdentifier>

The database you are connecting to, is a more recent one than the

supported version. Refer to the certification matrix for supported DB versions.

</PrereqErrorMsg>

</DBPrerequisite>

</DBPrerequisiteSet>

<DBPrerequisite PREREQ_TYPE="InitParameter" DATA_TYPE="NUMBER"

COMPARE_OPERATOR="GE">

<PrereqIdentifier>DB_BLOCK_SIZE</PrereqIdentifier>

</DBPrerequisite>

<!--DBPrerequisite PREREQ_TYPE="CustomSQL" DATA_TYPE="STRING"

COMPARE_OPERATOR="NE">

select 1 from dual where exists (select column_name from

dba_tab_columns where table_name(+) like 'V_$INSTANCE' and column_name(+) =

'EDITION') union select 0 from dual where not exists (select column_name from

dba_tab_columns where table_name(+) like 'V_$INSTANCE' and column_name(+) =

'EDITION')

</CustomQueryFilter>

</ValidIf>

<PrereqIdentifier>version</PrereqIdentifier>

The database you are connecting is 11.1.0.6.0

version. 11.1.0.6.0 is not a supported version. The database version should be

11.1.0.7.0 or greater.

</PrereqErrorMsg>

</DBPrerequisite-->

<DBPrerequisite PREREQ_TYPE="DBVersion" DATA_TYPE="STRING"

COMPARE_OPERATOR="GE">

select 1 from dual where exists (select column_name from

dba_tab_columns where table_name(+) like 'V_$INSTANCE' and column_name(+) =

'EDITION') union select 0 from dual where not exists (select column_name from

dba_tab_columns where table_name(+) like 'V_$INSTANCE' and column_name(+) =

'EDITION')

</CustomQueryFilter>

</ValidIf>

<PrereqIdentifier>version</PrereqIdentifier>

The database you are connecting is not a supported version. Enter Database

with version equal to or higher than 10.2.0.4.0 in 10g or version equal to or

Appendix C

RCU Configuration Files

C-20

higher than 11.1.0.7.0 in 11g. Refer to the certification matrix for supported DB

versions

</PrereqErrorMsg>

</DBPrerequisite>

select 1 from dual where exists (select column_name from dba_tab_columns

where table_name(+) like 'V_$INSTANCE' and column_name(+) = 'EDITION') union select 0

from dual where not exists (select column_name from dba_tab_columns where

table_name(+) like 'V_$INSTANCE' and column_name(+) = 'EDITION')

</CustomQueryFilter>

</ValidIf>

<PrereqIdentifier>select count(*) from product_component_version where

product like 'Oracle%Database%' AND version BETWEEN '11' AND '11.1.0.6.0' </

PrereqIdentifier>

The database you are connecting is not a supported

version. Enter Database with version equal to or higher than 10.2.0.4.0 in 10g or

version equal to or higher than 11.1.0.7.0 in 11g. Refer to the certification matrix

for supported DB versions

</PrereqErrorMsg>

</DBPrerequisite>

<PrereqIdentifier>select count(*) from syscat.tablespaces where tbspace =

'SYSCATSPACE' and pagesize >= 32768

</PrereqIdentifier>

Component : RCU

Error : Database prerequisite check failed.

Cause : Database: '%DATABASE_NAME%' needs to be

configured with

default pagesize 32768 or 32K.

Action : Modify the default of the current database or

create a new

database with the required default pagesize.

</PrereqErrorMsg>

</DBPrerequisite>

<PrereqIdentifier>SELECT count(*) where

CAST(SERVERPROPERTY('productversion') as VARCHAR(20)) like '1.%' or

CAST(SERVERPROPERTY('productversion') as VARCHAR(20)) like '4.%' or

CAST(SERVERPROPERTY('productversion') as VARCHAR(20)) like '6.%' or

CAST(SERVERPROPERTY('productversion') as VARCHAR(20)) like '7.%' or

CAST(SERVERPROPERTY('productversion') as VARCHAR(20)) like '8.%'</PrereqIdentifier>

The database you are connecting is not a supported version. Enter

Database with version equal to or higher than 2005. Refer to the certification matrix

for supported DB versions.

</PrereqErrorMsg>

</DBPrerequisite>

Appendix C

RCU Configuration Files

C-21

<DBPrerequisite PREREQ_TYPE="CustomSQL" DATA_TYPE="STRING"

COMPARE_OPERATOR="EQ">

<PrereqIdentifier>select count(*) FROM TABLE

(sysproc.env_get_inst_info()) where INT(substr(service_level,

POSSTR(service_level, 'v')+1, LOCATE('.', service_level,POSSTR(service_level,

'v') +1) - POSSTR(service_level, 'v') -1 ) ) = 9 AND INT(substr(service_level,

POSSTR(service_level, '.')+1, LOCATE('.',service_level,POSSTR(service_level,

'.') +1) - POSSTR(service_level, '.') -1 )) < 7 OR INT(substr(service_level,

POSSTR(service_level, 'v')+1, LOCATE('.', service_level,POSSTR(service_level,

'v') +1) - POSSTR(service_level, 'v') -1 ) ) < 9</PrereqIdentifier>

The database you are connecting is not a supported

version. Enter Database with version equal to or higher than 9.7. Refer to the

certification matrix for supported DB versions.

</PrereqErrorMsg>

</DBPrerequisite>

<DBPrerequisite PREREQ_TYPE="CustomSQL" DATA_TYPE="STRING"

COMPARE_OPERATOR="EQ">

<PrereqIdentifier>select GRANTED_ROLE from DBA_ROLE_PRIVS

where((GRANTED_ROLE='DBA' and GRANTEE=(select user from dual) and

lower(SYS_CONTEXT ('USERENV', 'SESSION_USER'))='sys') OR(GRANTED_ROLE='DBA' and

GRANTEE=(select user from dual)))</PrereqIdentifier>

User should have sysdba or dba privilages.

</PrereqErrorMsg>

</DBPrerequisite>

<PrereqIdentifier>select Is_Member('db_owner')</

PrereqIdentifier>

User should have sysdba or dba privilages.

</PrereqErrorMsg>

</DBPrerequisite>

<DBPrerequisite PREREQ_TYPE="CustomSQL" DATA_TYPE="STRING"

COMPARE_OPERATOR="EQ" SOFT="TRUE">

<PrereqIdentifier>select value from nls_database_parameters

where parameter = 'NLS_CHARACTERSET'</PrereqIdentifier>

The database you are connecting is with non-

AL32UTF8 character set. Oracle strongly recommends using AL32UTF8 as the

database character set.

</PrereqErrorMsg>

</DBPrerequisite>

<DBPrerequisite PREREQ_TYPE="CustomSQL" DATA_TYPE="NUMBER"

COMPARE_OPERATOR="EQ" SOFT="TRUE">

Appendix C

RCU Configuration Files

C-22

select 1 from dual where exists (select column_name from dba_tab_columns

where table_name(+) like 'V_$INSTANCE' and column_name(+) = 'EDITION') union select 0

from dual where not exists (select column_name from dba_tab_columns where

table_name(+) like 'V_$INSTANCE' and column_name(+) = 'EDITION')

</CustomQueryFilter>

</ValidIf>

<PrereqIdentifier>select count(*) from product_component_version where

product like 'Oracle%Database%' AND version BETWEEN '10.2.0.6.0' AND '10.9.9.9.9' </

PrereqIdentifier>

The database you are connecting to, is a more recent than the

supported version. Refer to the certification matrix for supported DB versions.

</PrereqErrorMsg>

</DBPrerequisite>

<DBPrerequisite PREREQ_TYPE="CustomSQL" DATA_TYPE="NUMBER"

COMPARE_OPERATOR="EQ" SOFT="TRUE">

select 1 from dual where exists (select column_name from dba_tab_columns

where table_name(+) like 'V_$INSTANCE' and column_name(+) = 'EDITION') union select 0

from dual where not exists (select column_name from dba_tab_columns where

table_name(+) like 'V_$INSTANCE' and column_name(+) = 'EDITION')

</CustomQueryFilter>

</ValidIf>

<PrereqIdentifier>select count(*) from product_component_version where

product like 'Oracle%Database%' AND version > '11.1.0.7.0' AND version <=

'11.1.9.9.9'</PrereqIdentifier>

The database you are connecting to, is a more recent one than the

supported version. Refer to the certification matrix for supported DB versions.

</PrereqErrorMsg>

</DBPrerequisite>

<DBPrerequisite PREREQ_TYPE="CustomSQL" DATA_TYPE="NUMBER"

COMPARE_OPERATOR="EQ" SOFT="TRUE">

select 1 from dual where exists (select column_name from dba_tab_columns

where table_name(+) like 'V_$INSTANCE' and column_name(+) = 'EDITION') union select 0

from dual where not exists (select column_name from dba_tab_columns where

table_name(+) like 'V_$INSTANCE' and column_name(+) = 'EDITION')

</CustomQueryFilter>

</ValidIf>

<PrereqIdentifier>select count(*) from product_component_version where

product like 'Oracle%Database%' AND version between '11.2.0.4.0' AND '11.2.9.9.9' </

PrereqIdentifier>

The database you are connecting to, is a more recent one than the

supported version. Refer to the certification matrix for supported DB versions.

</PrereqErrorMsg>

</DBPrerequisite>

select 1 from dual where exists (select column_name from dba_tab_columns

Appendix C

RCU Configuration Files

C-23

where table_name(+) like 'V_$INSTANCE' and column_name(+) = 'EDITION') union

select 0 from dual where not exists (select column_name from dba_tab_columns

where table_name(+) like 'V_$INSTANCE' and column_name(+) = 'EDITION')

</CustomQueryFilter>

</ValidIf>

<PrereqIdentifier>select count(*) from

product_component_version where product like 'Oracle%Database%' AND version

between '11.2.0.0.0' AND '11.2.0.2.9' </PrereqIdentifier>

The database you are connecting is not a

supported version. Enter Database with version equal to or higher than

11.2.0.3.0 in 11g. Refer to the certification matrix for supported DB versions.

</PrereqErrorMsg>

</DBPrerequisite>

<!--

<DBPrerequisite PREREQ_TYPE="CustomSQL" DATA_TYPE="NUMBER" COMPARE_OPERATOR="EQ"

SOFT="TRUE">

select 1 from dual where exists (select column_name from

dba_tab_columns where table_name(+) like 'V_$INSTANCE' and column_name(+) =

'EDITION') union select 0 from dual where not exists (select column_name from

dba_tab_columns where table_name(+) like 'V_$INSTANCE' and column_name(+) =

'EDITION')

</CustomQueryFilter>

</ValidIf>

<PrereqIdentifier>select count(*) from

product_component_version where product like 'Oracle%Database%' AND version >=

'12.2._._._' </PrereqIdentifier>

The database you are connecting to, is a more recent one than the

supported version. Refer to the certification matrix for supported DB versions.

</PrereqErrorMsg>

</DBPrerequisite>

select 1 from dual where exists (select column_name from

dba_tab_columns where table_name(+) like 'V_$INSTANCE' and column_name(+) =

'EDITION') union select 0 from dual where not exists (select column_name from

dba_tab_columns where table_name(+) like 'V_$INSTANCE' and column_name(+) =

'EDITION')

</CustomQueryFilter>

</ValidIf>

<PrereqIdentifier>select count(*) from product_component_version where

product like 'Oracle%Database%' AND version like '12.0._._._' </

PrereqIdentifier>

The database you are connecting is not a

supported version. Enter Database with version equal to or higher than

12.1.0.0.0 in 12c. Refer to the certification matrix for supported DB versions.

</PrereqErrorMsg>

</DBPrerequisite>

-->

<DBPrerequisite PREREQ_TYPE="CustomSQL" DATA_TYPE="STRING"

COMPARE_OPERATOR="EQ" SOFT="TRUE">

Appendix C

RCU Configuration Files

C-24

<PrereqIdentifier>SELECT count(*) where

CAST(SERVERPROPERTY('productversion') as VARCHAR(20)) not like '1.%' and

CAST(SERVERPROPERTY('productversion') as VARCHAR(20)) not like '4.%' and

CAST(SERVERPROPERTY('productversion') as VARCHAR(20)) not like '6.%' and

CAST(SERVERPROPERTY('productversion') as VARCHAR(20)) not like '7.%' and

CAST(SERVERPROPERTY('productversion') as VARCHAR(20)) not like '8.%' and

CAST(SERVERPROPERTY('productversion') as VARCHAR(20)) not like '9.%' and

CAST(SERVERPROPERTY('productversion') as VARCHAR(20)) not like '10.%' </

PrereqIdentifier>

The database you are connecting to, is a more recent than the

supported version. Refer to the certification matrix for supported DB versions.

</PrereqErrorMsg>

</DBPrerequisite>

<DBPrerequisite PREREQ_TYPE="CustomSQL" DATA_TYPE="STRING"

COMPARE_OPERATOR="EQ" SOFT="TRUE">

<PrereqIdentifier>select count(*) FROM TABLE (sysproc.env_get_inst_info()) where

INT(substr(service_level, POSSTR(service_level, 'v')+1, LOCATE('.', service_level,

POSSTR(service_level, 'v') +1) - POSSTR(service_level, 'v') -1 ) ) = 9 and

INT(substr(service_level, POSSTR(service_level, '.')+1, LOCATE('.', service_level,

POSSTR(service_level, '.') +1) - POSSTR(service_level, '.') -1 )) > 7 or

INT(substr(service_level, POSSTR(service_level, 'v')+1, LOCATE('.', service_level,

POSSTR(service_level, 'v') +1) - POSSTR(service_level, 'v') -1 ) ) > 9</

PrereqIdentifier>

The database you are connecting to, is a more recent than

the supported version. Refer to the certification matrix for supported DB versions.

</PrereqErrorMsg>

</DBPrerequisite>

<DBPrerequisite PREREQ_TYPE="Java" DATA_TYPE="STRING" COMPARE_OPERATOR="NE"

SOFT="TRUE">

<PrereqIdentifier>%RCU_HOME%/../oracle_common/rcu/config/

JavaDB.jar:javadbproject.JavaDB:checkJavaDBVersion</PrereqIdentifier>

<PrereqValue>SOFTPASS</PrereqValue>

The database you are connecting to, is a more recent than the supported

version. Refer to the certification matrix for supported DB versions.

</PrereqErrorMsg>

</DBPrerequisite>

<PrereqIdentifier>%RCU_HOME%/../oracle_common/rcu/config/

JavaDB.jar:javadbproject.JavaDB:checkJavaDBVersion</PrereqIdentifier>

The database you are connecting is not a supported version. Enter Database

with version equal to or higher than 10.5.3.0. Refer to the certification matrix for

supported DB versions.

</PrereqErrorMsg>

</DBPrerequisite>

Appendix C

RCU Configuration Files

C-25

<DBPrerequisite PREREQ_TYPE="CustomSQL" DATA_TYPE="NUMBER"

COMPARE_OPERATOR="EQ">

<PrereqIdentifier>select version() < '5.5.14'</

PrereqIdentifier>

The database you are connecting is not a supported

version. Enter Database with version equal to or higher than 5.5.14. Refer to

the certification matrix for supported DB versions.

</PrereqErrorMsg>

</DBPrerequisite>

<DBPrerequisite PREREQ_TYPE="CustomSQL" DATA_TYPE="NUMBER"

COMPARE_OPERATOR="EQ" SOFT="TRUE">

<PrereqIdentifier>select version() > '5.6' or version() =

'5.6'</PrereqIdentifier>

The database you are connecting to, is a more recent

than the supported version. Refer to the certification matrix for supported DB

versions.

</PrereqErrorMsg>

</DBPrerequisite>

<PrereqIdentifier>select VARIABLE_VALUE from

INFORMATION_SCHEMA.GLOBAL_VARIABLES where VARIABLE_NAME =

'INNODB_FILE_PER_TABLE'</PrereqIdentifier>

DB Init Param Prerequisite failure for

INNODB_FILE_PER_TABLE. Its value should be 'ON'.

</PrereqErrorMsg>

</DBPrerequisite>

<PrereqIdentifier>select VARIABLE_VALUE from

INFORMATION_SCHEMA.GLOBAL_VARIABLES where VARIABLE_NAME = 'INNODB_FILE_FORMAT'</

PrereqIdentifier>

<PrereqValue>Barracuda</PrereqValue>

DB Init Param Prerequisite failure for INNODB_FILE_FORMAT.

Its value should be 'Barracuda'.

</PrereqErrorMsg>

</DBPrerequisite>

<PrereqIdentifier>select VARIABLE_VALUE from

INFORMATION_SCHEMA.GLOBAL_VARIABLES where VARIABLE_NAME = 'INNODB_LARGE_PREFIX'</

PrereqIdentifier>

DB Init Param Prerequisite failure for

INNODB_LARGE_PREFIX. Its value should be 'ON'.

</PrereqErrorMsg>

Appendix C

RCU Configuration Files

C-26

</DBPrerequisite>

<PrereqIdentifier>select VARIABLE_VALUE from

INFORMATION_SCHEMA.GLOBAL_VARIABLES where VARIABLE_NAME

='log_bin_trust_function_creators'</PrereqIdentifier>

DB Init Param Prerequisite failure for

log_bin_trust_function_creators. Its value should be 'ON'.

</PrereqErrorMsg>

</DBPrerequisite>

</PrerequisiteDescriptor>

select count(*) from dba_views where VIEW_NAME= 'SCHEMA_VERSION_REGISTRY'

</CustomQueryFilter>

</ValidIf>

<Command

TYPE="METHOD">oracle.ias.version.SchemaVersionUtil:utilCreateRegistryTable</Command>

</Parameters>

</Action>

select count(*) from INFORMATION_SCHEMA.TABLES where

TABLE_NAME='SCHEMA_VERSION_REGISTRY'

</CustomQueryFilter>

</ValidIf>

<Command

TYPE="METHOD">oracle.ias.version.SchemaVersionUtil:utilCreateRegistryTable</Command>

</Parameters>

</Action>

select count(*) from syscat.tables where

TABNAME='SCHEMA_VERSION_REGISTRY'

</CustomQueryFilter>

</ValidIf>

<Command

TYPE="METHOD">oracle.ias.version.SchemaVersionUtil:utilCreateRegistryTable</Command>

</Parameters>

</Action>

<CustomQueryFilter DATA_TYPE="NUMBER" COMPARE_OPERATOR="EQ"

VALUE="0">

SELECT COUNT(*) FROM SYS.SYSTABLES INNER JOIN SYS.SYSSCHEMAS ON

SYS.SYSTABLES.SCHEMAID = SYS.SYSSCHEMAS.SCHEMAID WHERE SCHEMANAME='ORACLEFMW' AND

Appendix C

RCU Configuration Files

C-27

TABLENAME='SCHEMA_VERSION_REGISTRY_T'

</CustomQueryFilter>

</ValidIf>

<Command

TYPE="METHOD">oracle.ias.version.SchemaVersionUtil:utilCreateRegistryTable</

Command>

</Parameters>

</Action>

<CustomQueryFilter DATA_TYPE="NUMBER" COMPARE_OPERATOR="EQ"

VALUE="0">

select count(*) from INFORMATION_SCHEMA.TABLES where

TABLE_NAME='SCHEMA_VERSION_REGISTRY'

</CustomQueryFilter>

</ValidIf>

<Command

TYPE="METHOD">oracle.ias.version.SchemaVersionUtil:utilCreateRegistryTable</

Command>

</Parameters>

</Action>

</ExecutionDescriptor>

<Command

TYPE="METHOD">oracle.ias.version.SchemaVersionUtil:utilSetEditionName</Command>

<Parameter TYPE="String">%EDITION_NAME%</Parameter>

</Parameters>

</Action>

<Command

TYPE="METHOD">com.oracle.cie.rcu.ComponentSchemaUtil:loadCompSchemaInfo</Command>

<Parameter TYPE="String">%SERVICE_TABLE_STRING%</Parameter>

<Parameter TYPE="String">%PREFIX_NAME%</Parameter>

<Parameter TYPE="String">%DB_HOSTNAME%</Parameter>

<Parameter TYPE="String">%DB_SERVICE%</Parameter>

<Parameter TYPE="String">%DB_PORTNUMBER%</Parameter>

</Parameters>

</Action>

<Command

TYPE="METHOD">com.oracle.cie.rcu.ComponentSchemaUtil:loadNonOracleCompSchemaInfo<

/Command>

<Parameter TYPE="String">%SERVICE_TABLE_STRING%</Parameter>

<Parameter TYPE="String">%PREFIX_NAME%</Parameter>

Appendix C

RCU Configuration Files

C-28

<Parameter TYPE="String">%DB_HOSTNAME%</Parameter>

<Parameter TYPE="String">%DB_PORTNUMBER%</Parameter>

<Parameter TYPE="String">%DATABASE_NAME%</Parameter>

</Parameters>

</Action>

</ExecutionDescriptor>

<Error Type="ORA-17439">Invalid SQL type</Error>

<Error Type="ORA-01435">user does not exist</Error>

<Error Type="ORA-00955">name is already used by an existing object</Error>

<Error Type="ORA-01031">name is already used by an existing object</Error>

</FatalErrors>

<Error Type="ORA-02289">sequence does not exist</Error>

<Error Type="ORA-00904">invalid identifier</Error>

<Error Type="ORA-01920">user name conflicts with another user or role name</Error>

<Error Type="ORA-01418">specified index does not exist</Error>

<Error Type="ORA-00942">table or view does not exist</Error>

<Error Type="ORA-06512">Not found</Error>

<Error Type="ORA-01403">no data found</Error>

<Error Type="ORA-04043">does not exist</Error>

<Error Type="ORA-04080">Trigger does not exist</Error>

<Error Type="ORA-00959">Tablespace does not exist</Error>

<Error Type="ORA-24035">AQ agent not subscriber</Error>

<Error Type="ORA-24185">Transformation not found</Error>

<Error Type="ORA-24042">Does not exist</Error>

<Error Type="ORA-24088">Does not exist</Error>

</IgnorableErrors>

</ComponentInfo>

Soft-Prerequisite Support

If a particular

is not mandatory, then you can use

the soft-prerequisite option by setting the

SOFT

attribute to

TRUE

in the

ComponentInfo.xml

file

When a soft-prerequisite is not met, a pop-up dialog window with an error or warning

message appears; the user has the option to ignore the message or abort the operation. You

can define a soft-prerequisite at the

level, the

level,

or both; if both are defined, then

takes higher precedence.

Below is an example of setting a soft-prerequisite at the

level:

...

<DBPrerequisite PREREQ_TYPE="CustomSQL" DATA_TYPE="STRING" COMPARE_OPERATOR="EQ"

SOFT="TRUE">

<PrereqIdentifier>select value from nls_database_parameters where parameter =

'NLS_CHARACTERSET'</PrereqIdentifier>

The database you are connecting is with non-AL32UTF8 character set.

Oracle strongly recommends using AL32UTF8 as the database character

set.

</PrereqErrorMsg>

</DBPrerequisite>

Appendix C

RCU Configuration Files

C-29

...

Default Tablespaces Configuration File

The default tablespaces configuration file (

Storage.xml

) lists the components, for

which, tablespaces are created out-of-the-box. This file is located in the

ORACLE_HOME/

oracle_common/rcu/config

directory on UNIX operating systems or in the

ORACLE_HOME\oracle_common\rcu\config

directory on Windows operating systems.

The actual tablespace configuration file for each component is located in the

ORACLE_HOME/oracle_common/rcu/integrationcomponent/component_Storage.xml

directory on UNIX operating systems or in the

ORACLE_HOME\oracle_common\rcu\integrationcomponent\component_Storage.xml

directory on Windows operating systems. Each component has its own tablespaces

configuration file.

Below is a sample

opss_Storage.xml

file:

<?xml version="1.0" encoding="UTF-8" ?>

<Type>Permanent</Type>

<DefaultTemp>False</DefaultTemp>

<Bigfile>False</Bigfile>

</DatafileAttributes>

</DatafilesList>

</TablespaceAttributes>

For RCU XML Configuration File Details, refer Table C-1 in Storage Attributes

Configuration File

RCU Script Writing Guidelines

Use these guidelines when writing RCU scripts.

Schema user names and passwords should not be hard coded. They should be coded

as substitutable variables.

• If schema user needs to be created, it should be created first by using the

parameters passed by RCU.

• Tablespace and temporary tablespace references should not be hard coded; they

should be coded as variables.

• Do not use CONNECT; instead, use ALTER SESSION SET CURRENT_SCHEMA

= <SCHEMA_OWNER> after you create the schema user.

• The set of ignorable and fatal ORA errors (if any) should be listed in the RCU XML

component configuration file.

• Avoid any shutdown or startup that would bounce the database instance.

Appendix C

RCU Script Writing Guidelines

C-30

• SCHEMA_VERSION_REGISTRY should be updated before and after loading schema.

This can be done by using JavaAction as shown in Java Code Using JavaAction or within

the component scripts by using the SCHEMA_VERSION PL/SQL package.

• Block comments that contain line comments (/* -- comment */) are not supported.

The following are the guidelines for RCU for various scripts:

• Guidelines for RCU JDBC Engine Compliant SQL*Plus Scripts

Use these guidelines for writing the RCU JDBC Engine SQL*Plus scripts.

• Guidelines for Pure JDBC Scripts

Use these guidelines for writing Pure JDBC scripts for RCU.

• Guidelines for SQL*Plus Scripts

Use these guidelines for writing SQL*Plus scripts for RCU.

• Guidelines for SQL Server-Based Scripts

Use these guidelines for writing SQL Server-based scripts for RCU.

Guidelines for RCU JDBC Engine Compliant SQL*Plus Scripts

Use these guidelines for writing the RCU JDBC Engine SQL*Plus scripts.

• All statements must be terminated with appropriate terminating chars. CREATE

PACKAGE, TYPE needs to be terminated with a ; (semicolon) with / (forward slash) on

the next line. All other statements (Create TABLE, VIEW, and so on.) need to be

terminated by either ; (semicolon) or / (froward slash).

• EXECUTE calls should be replaced with BEGIN/END blocks.

• DEFINE statements should be in one line, no comments in the same line and no ;

(semicolon) at the end.

• SET, SHOW, SPOOL, WHENEVER, BREAK, EXIT statements are ignored.

• HOST command is not supported yet.

• VARIABLE and COL(UMN) are not supported.

Dynamically calling another SQL Script within a PL/SQL block using the following

technique is not supported:

VARIABLE initfile VARCHAR2(32)

COLUMN :initfile NEW_VALUE init_file NOPRINT;

BEGIN

IF (some condition) THEN

:initfile := 'initcdc.sql';

ELSE

:initfile := 'nothing.sql';

END IF;

END;

SELECT :initfile FROM DUAL;

@@&init_file

The work around is to have a separate Action with a ValidIf tag to specify the condition.

Appendix C

RCU Script Writing Guidelines

C-31

Guidelines for Pure JDBC Scripts

Use these guidelines for writing Pure JDBC scripts for RCU.

• Should not contain any SQL*Plus directives (like SET, WHENEVER, and so on.).

• All DEFINES should be changed to PL/SQL variable declarations.

• All SQL statements should be wrapped in EXECUTE IMMEDIATE.

• PL/SQL style comments are allowed, but SQL*Plus style (REM) comments are not

allowed.

• DROP statements that preceds CREATE statements do not work. DROP should

only be done after checking for the existence of the object. Ideally, all DROP

statements should put into different PL/SQL script and RCU can call this script

before calling a CREATE script, if that is desired.

• Contents of the script file should be a valid PL/SQL block, which can be called

within

Connection.prepareCall()

Guidelines for SQL*Plus Scripts

Use these guidelines for writing SQL*Plus scripts for RCU.

• Should not have any exit statements or WHENEVER ERROR EXIT directives.

This would cause RCU SQL*Plus session to exit unexpectedly and may impact

other component scripts to be executed later.

• Scripts should not have any spool commands. RCU would generate a spool log for

each component.

Guidelines for SQL Server-Based Scripts

Use these guidelines for writing SQL Server-based scripts for RCU.

• Support is a subset of what is supported in t-sql scripts that can be executed by

sqlcmd

• ValidIf tags should be added around all database-specific Actions and

Prerequisites. For example:

<DBPrerequisite PREREQ_TYPE="TablespaceFreeMB" DATA_TYPE="NUMBER"

COMPARE_OPERATOR="GT">

<PrereqIdentifier>%DEFAULT_TABLESPACE%</PrereqIdentifier>

</DBPrerequisite>

• RCU supports recursive variable definitions such as:

setvar var1 value1

setvar var2 $(var1)

• There should be a go statement to end blocks of statements. All statements that

precedes the go statement are executed as a single statement over JDBC.

• The JDBC connection is created in the auto-commit on mode.

• Currently, the begin transaction and commit transaction statements are not

supported.

Appendix C

RCU Script Writing Guidelines

C-32

• Variables passed to scripts through the XML file are passed as follows:

Script.sql –v v1=value1 v2=value2

This is only for scripts called by using the XML files. If a script calls another script, you

can use any other variable name.

Appendix C

RCU Script Writing Guidelines

C-33

Troubleshooting Repository Creation Utility

Review this information to help you understand and troubleshoot any errors or issues that

you encounter while you run the RCU.

• General Troubleshooting Tips

Use these tips to help troubleshoot any errors that you encounter during installation.

• RCU Log Files

When you run RCU to create or drop your schemas, the main RCU log file is written to

the

/tmp/RCUdate_timestamp_random_number/logs

directory on UNIX operating systems

C:\Users\user_name\AppData\Local\Temp\RCUdate_timestamp_random_number\logs

directory on Windows operating systems, by default.

• RCU Fails to Connect with ORA-604 ORA-1882 Error Codes

Error codes ORA-604 and ORA-1882.

• SOAINFRA Schema Creation Fails on a Hardened Database

Use this workaround if the RCU schemas for

SOAINFRA

does not load successfully on an

Oracle hardened database.

• Troubleshooting Tips for Schema Creation on an Autonomous Transaction Processing

Database

Use these tips to troubleshoot any errors you encounter during schema creation on an

Autonomous Transaction Processing database (both Oracle Autonomous Transaction

Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-Shared

(ATP-S)).

• Known Limitation for Oracle WebCenter Sites ATP-S Migration

• Troubleshooting Database Configuration Error for Microsoft SQL Server

When running Repository Creation Utility (RCU) for Oracle Business Intelligence or

Oracle Analytics Server on a Microsoft SQL Server database, an SQL SERVER RCU

error can occur due to incorrect database configuration.

• Need More Help?

If this guide does not solve the problem that you encountered, try looking for a solution on

My Oracle Support (formerly Oracle MetaLink).

General Troubleshooting Tips

Use these tips to help troubleshoot any errors that you encounter during installation.

• See Install and Configure in the Release Notes for Oracle Fusion Middleware

Infrastructure for the latest updates and issues related to Oracle Fusion Middleware

product installation and configuration.

• Verify that your computer meets the requirements as specified in the Oracle Fusion

Middleware System Requirements and Specifications document.

Select the document that is applicable for your release.

D-1

• Verify that your environment meets the certification requirements for your release

and platform, as specified on the Oracle Fusion Middleware Supported System

Configurations page.

• Make sure that your database is up and running.

• If you entered incorrect information on one of the screens, use the navigation pane

on the left most side of the graphical interface to return to that screen.

• If an error occurred while running RCU:

1. Note the error and review the installation log files (see RCU Log Files).

2. Correct the issue that caused the error. Depending on the type of error, you

may either continue with your RCU operation, or you are forced to restart

RCU.

3. Continue or restart RCU to complete your desired operation.

RCU Log Files

When you run RCU to create or drop your schemas, the main RCU log file is written to

the

/tmp/RCUdate_timestamp_random_number/logs

directory on UNIX operating

systems or

C:\Users\user_name\AppData\Local\Temp\RCUdate_timestamp_random_number\logs

directory on Windows operating systems, by default.

For example, on a UNIX operating system:

/tmp/RCU2014-01-02_03-00_412547075/logs/rcu.log

Accessing RCU Log Files on Windows

On Windows operating systems, the AppData folder might be hidden. To be able to

navigate to the RCU log files on Windows, ensure that the AppData folder is visible:

1. From the Start menu, select Control Panel, then Appearance and

Personalization, and then Folder Options.

The Folder Options window appears.

2. Select the View tab.

3. Under Advanced settings, ensure that Show hidden files, folders, and drives is

selected and click OK.

RCU Component Log Files

In addition to the general log file, each component writes a log file of its own. All

component log files are also written to the same directory as the

rcu.log

file.

Table D-1 lists the component log file names in alphabetical order by log file name.

Table D-1 RCU Component Log File Names

Component Log File Name

Analytics

activities.log

Business Intelligence Platform

biplatform.log

Appendix D

RCU Log Files

D-2

Table D-1 (Cont.) RCU Component Log File Names

Component Log File Name

Oracle WebCenter Enterprise Capture

capture.log

Oracle WebCenter Content Server — Complete

content.log

Oracle WebCenter Content Server — Search Only

contentsearch.log

Discussions

discussions.log

EDQ Config Repository

edq_conf.log

EDQ Results Repository

edq_res.log

Oracle Enterprise Scheduler

ess.log

Audit Services

iau.log

Audit Services Append

iau_append.log

Audit Services Viewer

iau_viewer.log

Metadata Services

mds.log

Managed File Transfer

mft.log

Master and Work Repository

odi.log

Monitor Server

oggmon.log

Oracle GoldenGate Studio Repository

oggstudio.log

Oracle Platform Security Services

opss.log

Portlet Producers

portlet.log

SOA Infrastructure

soainfra.log

Common Infrastructure Services

stb.log

User Messaging Service

ucsums.log

Veridata Repository

veridata.log

WebCenter Sites

wcsites.log

WebCenter Sites — Visitor Services

wcsitesvs.log

Portal and Services

webcenter.log

WebLogic Services

wls.log

RCU Fails to Connect with ORA-604 ORA-1882 Error Codes

Error codes ORA-604 and ORA-1882.

RCU fails to connect database with the following errors:

• ORA-604: error occurred at recursive SQL level 1

• ORA-1882: timezone region not found

Setting RCU_JAVA_OPTIONS before Invoking RCU

Set the below property and invoke RCU:

Appendix D

RCU Fails to Connect with ORA-604 ORA-1882 Error Codes

D-3

RCU_JAVA_OPTIONS -Doracle.jdbc.timezoneAsRegion=false

SOAINFRA Schema Creation Fails on a Hardened

Database

Use this workaround if the RCU schemas for

SOAINFRA

does not load successfully on

an Oracle hardened database.

In case of an Oracle hardened database, when the public grants are revoked for the

PL/SQL packages, the schema creation for

SOAINFRA

fails with the following error:

Received Non-Ignorable Error: ORA-04063: package body "XDB.DBMS_CSX_INT"

has errors

Grant the following permission to the user and run the Repository Creation Utility

(RCU) again to create the schemas for

SOAINFRA

GRANT EXECUTE ON DBMS_LOB TO XDB;

Troubleshooting Tips for Schema Creation on an

Autonomous Transaction Processing Database

Use these tips to troubleshoot any errors you encounter during schema creation on an

Autonomous Transaction Processing database (both Oracle Autonomous Transaction

Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-

Shared (ATP-S)).

• See Issues Pertaining to Product Installation and Configuration with Autonomous

Database in the Release Notes for Oracle Fusion Middleware Infrastructure for

issues related to installation and configuration for Oracle Fusion Middleware

products on an Autonomous Transaction Processing database.

• In the Database Connection Details screen, when you select the database user

role as Normal, the following warning is displayed:

Sysdba or dba privileges are required to load schema

You can click Ignore and continue with the schema creation.

• If you are creating schemas on an Oracle Autonomous Transaction Processing-

Dedicated (ATP-D) database, in the Map Tablespaces screen, if you receive any

tablespace creation error due to insufficient privileges or exceeding of maximum

number of DB_FILES, you can override the default and temporary tablespaces for

the selected components by selecting existing tablespaces from the drop-down list

in the Default Tablespace column and Temp Tablespace column.

For example, to override the default and temporary tablespaces, you can select

DATA from the drop-down list in the Default Tablespace column, and TEMP from

the drop-down list in the Temp Tablespace column.

Appendix D

SOAINFRA Schema Creation Fails on a Hardened Database

D-4

Note:

If you are creating schemas on an Oracle Autonomous Transaction Processing-

Shared (ATP-S) database, in the Map Tablespaces screen, you must override

the default and temporary tablespaces. See Map Tablespaces.

• During Oracle WebCenter Content schema creation, warnings are displayed in the

Summary screen.

You can click Ignore and continue with the schema creation.

Example warning messages:

ORA-01031: insufficient privileges

File:/home/opc/idm/oracle_common/../wcccontent/common/sql/content/sql/oracle/

contentserverrole.sql

Statement: GRANT SELECT ON CTXSYS.DR$PENDING TO contentserver_role

ORA-01450: maximum key length (6398) exceeded

File:/home/opc/jrf/oracle_common/../wcccontent/common/sql/content/sql/oracle/

contentserverrole.sql

Statement: CREATE TABLE RunTimeConfigData

ORA-01450: maximum key length (6398) exceeded

File:/home/opc/jrf/oracle_common/../wcccontent/common/sql/content/sql/oracle/

intradoc.sql

STATEMENT Create table Subscription

where,

/home/opc/idm

and

/home/opc/jrf

are the

ORACLE HOME

locations.

• During Oracle Internet Directory schema creation, when the schemas are loading, the

warning

ORA-28007: the password cannot be reused

is displayed in the Summary

screen.

You can click Ignore and continue with the schema creation.

• During SOAINFRA schema creation, for Oracle Identity Management, the warning

ORA-24010: QUEUE DEV24_SOAINFRA.IP_IN_QUEUE does not exist

is displayed in the

RCU logs. This warning does not have any functional impact and can be ignored.

• During schema creation of Oracle Enterprise Scheduler and Oracle Managed File

Transfer SOA products, in the Summary screen, the following warning

"ORA-01031:

insufficient privileges"

is displayed and the schema creation fails.

Add the create any job privilege to the

ADMIN

user, and restart the schema creation.

• During schema creation of Oracle Enterprise Scheduler and Oracle Managed File

Transfer SOA products, even after adding the create any job privilege, in the Summary

screen, the warning

"ORA-01031: insufficient privileges"

is displayed.

For ATP-D, you can apply the patch 31443286 and restart the schema creation., and for

ATP-S, you can apply the patch 33351665 and restart the schema creation.

Known Limitation for Oracle WebCenter Sites ATP-S Migration

For Oracle WebCenter Sites, you cannot install and configure FirstSiteII sample site, and

therefore, you cannot create new promotion assets, after you migrate an on-premises

database to an Oracle Autonomous Transaction Processing (ATP-S) database.

Appendix D

Known Limitation for Oracle WebCenter Sites ATP-S Migration

D-5

As there is no workaround available, you must exclude FirstSiteII during the

installation.

Troubleshooting Database Configuration Error for Microsoft

SQL Server

When running Repository Creation Utility (RCU) for Oracle Business Intelligence or

Oracle Analytics Server on a Microsoft SQL Server database, an SQL SERVER RCU

error can occur due to incorrect database configuration.

Perform the following steps to resolve the SQL SERVER RCU error:

1. Launch SQL Server Management Studio, use SQL Server Authentication and

2. Create a new database.

Note:

You can also modify an existing repository database.

3. Set the collation to a case sensitive collation as follows:

SQL_Latin1_General_CP1_CS_AS

For more information about how to check case-sensitivity in SQL Server, see How

to Check Case-Sensitivity in SQL Server.

4. Right-click on the database name.

5. Select New Query from the pop-up menu.

6. In the Query window, run the following commands on the database to ensure all

RCU database requirements are complete:

ALTER DATABASE database_name SET allow_snapshot_isolation ON

ALTER DATABASE database_name SET SINGLE_USER WITH ROLLBACK IMMEDIATE

ALTER DATABASE database_name SET read_committed_snapshot ON

ALTER DATABASE database_name SET MULTI_USER

ALTER DATABASE database_name SET READ_COMMITTED_SNAPSHOT ON WITH

NO_WAIT

7. Run the Repository Creation Utility.

8. Verify the process is complete.

Need More Help?

If this guide does not solve the problem that you encountered, try looking for a solution

on My Oracle Support (formerly Oracle MetaLink).

https://support.oracle.com/

If you are unable to find a solution for your problem, open a service request.

Appendix D

Troubleshooting Database Configuration Error for Microsoft SQL Server

D-6