Oracle® Fusion Middleware

Repository Creation Utility User's Guide

11g Release 1 (11.1.1.7.0)

E14259-15

June 2013

Oracle Fusion Middleware Repository Creation Utility User's Guide, 11g Release 1 (11.1.1.7.0)

E14259-15

Copyright © 2013, Oracle and/or its affiliates. All rights reserved.

Primary Author:  Kevin Hwang

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

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

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on 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. 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.

Contents

Preface

- Intended Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 Repository Creation Utility Overview

- 1.1 RCU System and Database Requirements

- 1.1.1 Supported Platforms

- 1.1.2 Finding a Certified Database

- 1.1.3 Configuring Your Database

- 1.1.4 Important Information for IBM DB2 Databases

- 1.1.5 Granting Roles and System Privileges on Oracle Databases

- 1.2 RCU Features

- 1.2.1 Creating Custom Schemas and Tablespaces

- 1.2.1.1 Creating Schemas in Multiple Databases

- 1.2.1.2 Using Custom Prefixes

- 1.2.1.3 Using Custom Prefixes in IBM DB2 Databases

- 1.2.1.4 What Happens When a Schema is Created?

- 1.2.2 Creating Schemas in a Multi-Domain Environment

- 1.2.3 Launching RCU with a Variety of Methods

- 1.2.3.1 Launching RCU Locally

- 1.2.3.2 Launching RCU Remotely

- 1.2.3.3 Launching RCU in Silent Mode (Using the CLI)

- 1.2.4 Checking Global and Component Level Prerequisites

- 1.2.5 Integrating Components Using Declarative XML

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

- 1.3.1 Install Java Access Bridge

- 1.3.2 Configure RCU to Use Java Access Bridge

2 Obtaining and Running Repository Creation Utility

- 2.1 Before You Begin

- 2.2 Required Schemas and Dependencies

- 2.2.1 Oracle SOA Suite Schemas

- 2.2.2 Oracle WebCenter Portal Schemas

- 2.2.3 Oracle Application Developer Schema

- 2.2.4 Oracle Identity Management Schemas

- 2.2.5 Oracle Data Integrator Schema

- 2.2.6 Oracle Business Intelligence Schemas

- 2.2.7 Oracle Portal, Forms, Reports and Discoverer Schemas

- 2.2.8 Oracle WebCenter Content Schemas

- 2.3 Obtaining RCU

- 2.4 Starting RCU

- 2.5 Creating Schemas

- 2.6 Dropping Schemas

- 2.6.1 Dropping Shared Tablespaces

- 2.6.2 Dropping Schemas and Deleting Datafiles (Windows Only)

- 2.7 Creating the Portal Demo Schema

3 Extending Repository Creation Utility to Configure Custom Application Repositories

- 3.1 RCU Integration Options

- 3.1.1 RCU JDBC Engine Compliant SQL*Plus Scripts

- 3.1.2 Pure JDBC Scripts

- 3.1.3 SQL*Plus Scripts

- 3.1.4 External Processes

- 3.1.5 Java Code Using JavaAction

- 3.2 RCU Configuration Files

- 3.2.1 XML DTDs Defined by RCU

- 3.2.1.1 Component Descriptor Configuration File

- 3.2.1.2 Repository Configuration File

- 3.2.1.3 Master List of Supported Components

- 3.2.1.4 Storage Attributes Configuration File

- 3.2.2 Component Repository Configuration File

- 3.2.3 Component List Configuration File

- 3.2.4 Soft-Prerequisite Support

- 3.2.5 Default Tablespaces Configuration File

- 3.3 RCU Script Writing Guidelines

- 3.3.1 Guidelines for RCU JDBC Engine Compliant SQL*Plus Scripts

- 3.3.2 Guidelines for Pure JDBC Scripts

- 3.3.3 Guidelines for SQL*Plus Scripts

- 3.3.4 Guidelines for SQL Server-Based Scripts

4 Running Repository Creation Utility from the Command Line

- 4.1 Command Line Syntax and Parameters

- 4.2 Using the -silent Command

- 4.3 Using the -interactive Command

- 4.4 Creating a Repository from the Command Line

- 4.5 Dropping a Repository from the Command Line

- 4.6 RCU Environment Variables

A Repository Creation Utility Screens

- A.1 Welcome

- A.2 Create Repository

- A.3 Drop Repository

- A.4 Database Connection Details

- A.4.1 Specifying Connection Credentials for Oracle Databases and Oracle Databases with Edition-Based Redefinition

- A.4.2 Specifying Connection Credentials for MySQL Databases

- A.4.3 Specifying Connection Credentials for Microsoft SQL Server Databases

- A.4.4 Specifying Connection Credentials for IBM DB2 Databases

- A.5 Select Components (for Create Operation)

- A.5.1 Creating Database Users for IBM DB2 Databases

- A.5.2 Creating Prefixes

- A.5.3 Selecting Components and Dependencies

- A.5.4 Specifying Custom Schema Names

- A.5.5 Checking Schema Prerequisites

- A.6 Select Components (for Drop Operation)

- A.7 Schema Passwords

- A.8 Custom Variables

- A.8.1 Specifying Custom Variables for Master and Work Repository (ODI)

- A.8.2 Specifying Custom Variables for Oracle WebCenter Portal's Activity Graph and Analytics

- A.9 Map Tablespaces

- A.9.1 Default Tablespace Mappings

- A.9.2 Changing Default and Temporary Tablespaces

- A.9.3 Viewing and Changing Additional Tablespaces

- A.9.4 Managing Tablespaces and Datafiles

- A.9.4.1 Adding, Modifying, and Removing Tablespaces

- A.9.4.2 Adding, Modifying, and Removing Datafiles

- A.10 Summary (for Create Operation)

- A.11 Summary (for Drop Operation)

- A.12 Completion Summary (for Create Operation)

- A.13 Completion Summary (for Drop Operation)

B Repository Creation Utility Schemas, IDs, and Tablespaces

C Troubleshooting Repository Creation Utility

- C.1 General Troubleshooting Tips

- C.2 RCU Log Files

- C.3 Finding Schemas in the Database

- C.4 Need More Help?

Index

Preface

The Oracle Fusion Middleware Repository Creation Utility User's Guide contains overview information and usage instructions for Oracle Repository Creation Utility (RCU).

Intended Audience

This guide is intended for users who are installing Oracle Fusion Middleware 11g Release 1 (11.1.1) products for the first time and are comfortable running some system administration operations, such as creating users and groups, adding users to groups, and installing operating system patches on the computer where Oracle Fusion Middleware 11g Release 1 (11.1.1) products will be installed. Users on UNIX systems need root access to run some scripts.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

For additional information, see the following manuals:

- Oracle Fusion Middleware Installation Planning Guide

- Oracle Fusion Middleware Administrator's Guide

- Oracle Fusion Middleware High Availability Guide

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.

1 Repository Creation Utility Overview

Many of the Oracle Fusion Middleware components require the existence of schemas in a database prior to installation. These schemas are created and loaded in your database using the Repository Creation Utility (RCU).

This chapter contains the following content:

- Section 1.1, "RCU System and Database Requirements"

- Section 1.2, "RCU Features"

- Section 1.3, "Using RCU with Java Access Bridge (Windows Only)"

1.1 RCU System and Database Requirements

This section contains links to important information about supported platforms for RCU, certified databases, and database configuration information. Read this information carefully before you obtain and run RCU.

1.1.1 Supported Platforms

To see the platforms on which you can run RCU, review the "RCU Supported Platforms" section in the Oracle Fusion Middleware System Requirements and Specifications document.

1.1.2 Finding a Certified Database

For a list of certified databases that can be used with RCU:

1. Go to the Oracle Fusion Middleware Supported System Configurations page.

2. In the table, find the System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 document, which is in .xls format.

3. Open the document, and go to the FMW on WLS - DB tab, which contains the database certifications.

1.1.3 Configuring Your Database

Before you begin using RCU, review the following sections in the Oracle Fusion Middleware System Requirements and Specifications document:

- "RCU Privileges for System Packages"
This section contains important information about the privileges required on your database system packages in order for RCU to run without errors.

- "Repository Creation Utility (RCU) Requirements"
This section contains important information about general and component-specific database requirements that should be met before you run RCU.

Note that not all schemas are supported on all databases. Make sure you have read the information in this section carefully so that you configure a certified database that supports the schemas you need for your Fusion Middleware components.

1.1.4 Important Information for IBM DB2 Databases

In addition to the typical space and configuration database requirements, IBM DB2 databases also have the following special requirements:

- On IBM DB2 databases running on Linux operating systems, there is a limitation with regards to the length of the schema names.

- One database operating system user must be created for each schema that is created in an IBM DB2 database.

For more information, refer to the "RCU Prerequisites for IBM DB2 Databases" section in the Oracle Fusion Middleware System Requirements and Specifications document.

1.1.5 Granting Roles and System Privileges on Oracle Databases

Creating schemas on Oracle databases may require that elevated permissions and privileges are granted. Schemas are created with certain roles, which grants them certain privileges on the database.

To further understand these roles and grants and the repercussions of revoking certain roles, refer to "Using Database Roles/Grants for Oracle Identity Manager Database" in Oracle Fusion Middleware Administrator's Guide for Oracle Identity Manager.

1.2 RCU Features

Repository Creation Utility is a graphical and CLI-based tool used to create and manage Oracle Fusion Middleware database schemas.

Some key features of RCU are listed below:

- Creating Custom Schemas and Tablespaces

- Launching RCU with a Variety of Methods

- Checking Global and Component Level Prerequisites

- Integrating Components Using Declarative XML

1.2.1 Creating Custom Schemas and Tablespaces

RCU provides the flexibility to create custom schemas and tablespaces. You can choose to rename schemas, or change the tablespace allocation so that components can share a single or multiple tablespaces. In addition, auxiliary schemas can be mapped to additional tablespaces.

1.2.1.1 Creating Schemas in Multiple Databases

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

1.2.1.2 Using Custom Prefixes

You can use RCU to create multiple schemas of each component using custom prefixes. In this way, the schema is used to group related schemas together, which is necessary when creating schemas in an environment with multiple domains (see Section 1.2.2, "Creating Schemas in a Multi-Domain Environment").

The prefix is prepended to and separated from the schema name with an underscore (_) character, as shown below:

prefix_schemaname

The default prefix used by RCU is DEV; if DEV has already been used, then RCU will default to DEV1, then DEV2, and so on. Prefixes are used to create and organize logical groups of schemas. For example, you may want to create a test version of the Metadata Services (schema name MDS) called TEST_MDS; then, when are ready for your production version, you can create a second version of the schema called PROD_MDS. Both TEST_MDS and PROD_MDS may reside on the same or separate databases.

Note:

The Oracle Internet Directory (ODS) component cannot be prepended with a custom prefix; there can only be one repository for this component per database.

You are only allowed to use a prefix once per schema within a single database. For example, if you had a version of the Metadata Services schema called DEV_MDS, then you can not use the DEV prefix again to create another version of the Metadata Services schema (for example, DEV_MDS2).

If you want to create another version of the schema using the same prefix, you must first drop the existing schema and then create the schema again.

The mapping between the prefixes and schemas is maintained in schema_version_registry.

1.2.1.3 Using Custom Prefixes in IBM DB2 Databases

For important information regarding custom prefixes in IBM DB2 databases, refer to "Size Limit for Schema Prefixes" in the Oracle Fusion Middleware System Requirements and Specifications document.

1.2.1.4 What Happens When a Schema is Created?

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

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

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

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

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

1. Create the user and grant the required roles.

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

3. Create the schema objects.

1.2.2 Creating Schemas in a Multi-Domain Environment

Schemas are grouped together using custom prefixes (see Section 1.2.1.2, "Using Custom Prefixes"). Each set of schemas can be used by a single domain only; in a multi-domain environment, you must create a separate set of schemas for each domain.

In Figure 1-1, two WebLogic domains are present with a single database. The servers configured in "WebLogic Domain 1" are for Oracle SOA Suite, and the corresponding schemas in the database have the "DEV1" prefix. The servers configured in "WebLogic Domain 2" are for Oracle WebCenter Spaces and the corresponding schemas in the database have the "DEV2" prefix.

Figure 1-1 Schema Creation on a single Database in a Multi-Domain Environment

It is also possible to create schemas on separate databases in a multi-domain environment, as shown in Figure 1-2.

Figure 1-2 Schema Creation on Multiple Databases in a Multi-Domain Environment

Note that in this case, both sets of schemas use the "DEV1" prefix, but because they are on separate machines there is no conflict.

1.2.3 Launching RCU with a Variety of Methods

RCU can be run locally (from the CD or download location) or remotely. In either case, both a graphical interface and command line (CLI) options are available.

1.2.3.1 Launching RCU Locally

In situations where the application administrator is not allowed to install components on the server, RCU can be started directly from the CD. The CD contains the extracted Oracle Client software and RCU uses SQLPLUS and other scripts and libraries from the CD to perform its operations.

When RCU is launched from the CD, log files are written to the user's TEMP directory.

If the administrator is allowed to install components, then RCU can be downloaded and the archive file can be extracted to a local directory.

1.2.3.2 Launching RCU Remotely

In situations where a database is not accessible locally for application administrators, RCU can be launched against a remote database. The SQLNET client is packaged with RCU to support this operation.

1.2.3.3 Launching RCU in Silent Mode (Using the CLI)

RCU provides a command line interface in situations where Xserver is not available or you have access to telnet terminals without display capabilities. The command line interface also allows you to embed RCU from command line scripts or with some Oracle Fusion Middleware components (for example, Enterprise Manager).

For more information using the CLI, see Chapter 4, "Running Repository Creation Utility from the Command Line".

1.2.4 Checking Global and Component Level Prerequisites

At runtime, RCU performs checks against both global and component level prerequisites. If a prerequisite is not met, RCU may issue a warning and allow the procedure to continue (soft stop), or will notify the user that a prerequisite must be met before the operation can continue (hard stop).

For more information about component level prerequisites see "Repository Creation Utility (RCU) Requirements" in the Oracle Fusion Middleware System Requirements and Specifications document.

1.2.5 Integrating Components Using Declarative XML

RCU provides extensibility with XML DTDs. Using these DTDs, component owners can integrate their components and prerequisites with RCU by providing a configuration file that adheres to the provided DTD.

For more information, refer to Chapter 3, "Extending Repository Creation Utility to Configure Custom Application Repositories".

1.3 Using RCU with Java Access Bridge (Windows Only)

Java Access Bridge enables assistive technologies, such as JAWS screen reader, to read Java applications running on the Windows platform. Assistive technologies can read Java-based interfaces, such as Oracle Universal Installer and Oracle Enterprise Manager.

1.3.1 Install Java Access Bridge

To install Java Access Bridge:

1. Download Java Access Bridge from the following URL:

http://java.sun.com/javase/technologies/accessibility/accessbridge/

2. Install Java Access Bridge.

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

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

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

1.3.2 Configure RCU to Use Java Access Bridge

To configure RCU to use Java Access Bridge after you complete the installation, set the system variable ORACLE_OEM_CLASSPATH to point to the installed Java Access Bridge files:

1. Display System in the Control Panel.

2. Select the Advanced tab.

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

4. In the Variable Name field, enter ORACLE_OEM_CLASSPATH.

5. In the Variable Value field, enter the full path to access-bridge.jar and jaccess-1_4.jar.
Use a semicolon to separate the two paths. Do not use quotes or character spaces.

6. Click OK.

2 Obtaining and Running Repository Creation Utility

This chapter describes how obtain RCU, then run RCU to create and drop schemas using both the graphical interface and command line interface.

The following topics are covered:

- Section 2.1, "Before You Begin"

- Section 2.2, "Required Schemas and Dependencies"

- Section 2.3, "Obtaining RCU"

- Section 2.4, "Starting RCU"

- Section 2.5, "Creating Schemas"

- Section 2.6, "Dropping Schemas"

- Section 2.7, "Creating the Portal Demo Schema"

2.1 Before You Begin

Before you begin, make sure you have read Section 1.1, "RCU System and Database Requirements". You should have a properly configured certified database that is up and running before you continue.

2.2 Required Schemas and Dependencies

This section lists the required schemas and their dependencies for Oracle Fusion Middleware components. Before you run RCU, you should make a note of the schemas you will need to create.

- Oracle SOA Suite Schemas

- Oracle WebCenter Portal Schemas

- Oracle Application Developer Schema

- Oracle Identity Management Schemas

- Oracle Data Integrator Schema

- Oracle Business Intelligence Schemas

- Oracle Portal, Forms, Reports and Discoverer Schemas

- Oracle WebCenter Content Schemas

2.2.1 Oracle SOA Suite Schemas

Table 2-1 lists the required schemas and dependencies for Oracle SOA Suite products on Oracle and Microsoft SQL Server databases:

Table 2-1 Required Schemas for Oracle SOA Suite Products on Oracle and Microsoft SQL Server Databases

Component

Schema Owner

Dependencies

SOA Infrastructure

prefix_SOAINFRA

prefix_MDS (Metadata Services)

prefix_ORASDPM (User Messaging)

Business Activity Monitoring

prefix_ORABAM

prefix_MDS (Metadata Services)

prefix_ORASDPM (User Messaging)

User Messaging Service

prefix_ORASDPM

prefix_MDS (Metadata Services)

Note:

On Oracle databases, if you create schemas with a database user other than SYS or SYSTEM, you must grant that user the following AQ roles and privileges to successfully load the prefix_SOAINFRA schema:

GRANT ALL ON dbms_aqadm TO new_user WITH GRANT OPTION;
GRANT ALL ON dbms_aq TO new_user WITH GRANT OPTION;
GRANT aq_user_role TO new_user;
GRANT EXECUTE ON dbms_aqin to new_user WITH GRANT OPTION;
GRANT EXECUTE ON dbms_aqjms to new_user WITH GRANT OPTION;

Table 2-2 lists the required schemas and dependencies for Oracle SOA Suite products on IBM DB2 databases:

Table 2-2 Required Schemas for Oracle SOA Suite Products in IBM DB2 Databases

Component

Schema Owner

Dependencies

Required Operating System Users

SOA Infrastructure

prefix_SOA

prefix_MDS (Metadata Services)

prefix_UMS (User Messaging)

prefix_soa

prefix_mds

prefix_ums

User Messaging Service

prefix_UMS

prefix_MDS (Metadata Services)

prefix_ums

prefix_mds

2.2.2 Oracle WebCenter Portal Schemas

All of the Oracle WebCenter Portal schemas are supported on all certified databases.

Table 2-3 lists the required schemas and dependencies for Oracle WebCenter Portal products on Oracle and Microsoft SQL Server databases:

Table 2-3 Required Schemas for Oracle WebCenter Portal Products on Oracle and Microsoft SQL Server Databases

Component

Schema Owner

Dependencies

Spaces and Services

prefix_WEBCENTER

prefix_MDS (Metadata Services)

Portlet Producers

prefix_PORTLET

None.

Discussions

prefix_DISCUSSIONS

None.

Activity Graph and Analytics

prefix_ACTIVITIES

None.

Table 2-4 lists the required schemas for Oracle WebCenter Portal products for IBM DB2 databases:

Table 2-4 Required Schemas for Oracle WebCenter Portal Products on IBM DB2 Databases

Component

Schema Owner

Dependencies

Required Operating System Users

Spaces and Services

prefix_WC

prefix_MDS (Metadata Services)

prefix_wc

prefix_mds

Portlet Producers

prefix_PT

None.

prefix_pt

Discussions

prefix_DS

None.

prefix_ds

Activity Graph and Analytics

prefix_AG

None.

prefix_ag

If you are an application developer and want to build WebCenter Portal applications, you must run RCU a second time to create a second version of the Spaces and Services (prefix_WEBCENTER on Oracle and Microsoft SQL Server databases or prefix_WC on IBM DB2 databases) schema. Note that this schema is separate from the Spaces and Services schema used by Oracle WebCenter Portal: Spaces, so you should make sure you use a different schema prefix. For information about the WebCenter services that require the WebCenter schema, see Table 5-1 in Oracle Fusion Middleware Installation Guide for Oracle WebCenter.

2.2.3 Oracle Application Developer Schema

Oracle Application Developer includes Oracle WSM Policy Manager and Oracle WSM-PM Extension. These components require that the Metadata Services (MDS) schema exists in your database prior to installation.

On all databases, you must create the schema prefix_MDS. On IBM DB2 databases, you must also create the operating system user prefix_mds.

2.2.4 Oracle Identity Management Schemas

Oracle Identity Management schemas are not supported on Microsoft SQL Server or IBM DB2 databases.

Table 2-5 lists the required schemas and dependencies for Oracle Identity Management products on Oracle databases:

Table 2-5 Required Schemas for Oracle Identity Management Components on Oracle Databases

Component

Schema Owner

Dependencies

Oracle Internet Directory

ODS

None.

Oracle Identity Federation

prefix_OIF

None.

Oracle Identity Manager

prefix_OIM

prefix_MDS (Metadata Services)

prefix_SOAINFRA (SOA Infrastructure)

prefix_ORASDPM (User Messaging Service)

Oracle Access Manager

prefix_OAM

prefix_IAU (Audit Services)

Oracle Adaptive Access Manager

prefix_OAAM

prefix_MDS (Metadata Services)

Oracle Adaptive Access Manager (Partition Support)

prefix_OAAM_PARTN

prefix_MDS (Metadata Services)

Oracle Entitlements Server

prefix_APM

prefix_MDS (Metadata Services)

2.2.5 Oracle Data Integrator Schema

Oracle Data Integrator requires that the Oracle Data Integrator (prefix_ODI_REPO) schema exists in your Oracle or Microsoft SQL Server database prior to installation.

Note:

If you are creating the repository on Oracle Database 12c, you must assign a quota to allow the user to create objects. Choose the quota to accommodate the expected size of your repository. If you are not sure about the size of your repository, you can grant unlimited tablespace. For example:

GRANT UNLIMITED TABLESPACE TO odi_DB_repos_user

On IBM DB2 databases, the Oracle Data Integrator schema name is prefix_ODI, and you must also create the operating system user prefix_odi.

2.2.6 Oracle Business Intelligence Schemas

Oracle Business Intelligence requires that the Business Intelligence Platform (prefix_BIPLATFORM) schema exists in your Oracle or Microsoft SQL Server database prior to installation.

On IBM DB2 databases, the Business Intelligence Platform schema name is prefix_BI, and you must also create the operating system user prefix_bi.

2.2.7 Oracle Portal, Forms, Reports and Discoverer Schemas

Oracle Portal and Oracle Discoverer schemas are not supported on Microsoft SQL Server or IBM DB2 databases.

Table 2-6 lists the required schemas and dependencies for Oracle Portal and Oracle Discoverer on Oracle databases:

Table 2-6 Required Schemas for Oracle Portal and Oracle Discoverer on Oracle Databases

Component

Schema Owner

Dependencies

Oracle Portal

prefix_PORTAL

Oracle Portlet Producers (prefix_PORTLET)

Oracle Discoverer

prefix_DISCOVERER

None.

2.2.8 Oracle WebCenter Content Schemas

Table 2-7 lists the required schemas and dependencies for Oracle WebCenter Content on Oracle and Microsoft SQL Server databases:

Table 2-7 Required Schemas for WebCenter Content - Oracle and Microsoft SQL Server Databases

Component

Schema Owner

Dependencies

Oracle Information Rights Management

prefix_ORAIRM

None.

Oracle WebCenter Content Server 11g - Complete

prefix_OCS

None.

Oracle WebCenter Content Server 11g - Search Only

prefix_OCSSEARCH

None.

Oracle WebCenter Content: Records

prefix_URMSERVER

None.

Oracle WebCenter Content: Imaging

prefix_IPM

None.

Table 2-8 lists the required schemas for Oracle WebCenter Content components for IBM DB2 databases:

Table 2-8 Required Schemas for WebCenter Content - IBM DB2 Databases

Component

Schema Owner

Dependencies

Required Operating System Users

Oracle Information Rights Management

prefix_IRM

None.

prefix_irm

Oracle Content Server 11g - Complete

prefix_OCS

None.

prefix_ocs

Oracle WebCenter Content: Records

prefix_URM

None.

prefix_urm

Oracle WebCenter Content: Imaging

prefix_IPM

None.

prefix_ipm

2.3 Obtaining RCU

To obtain the proper version of RCU for your release, go to the Oracle Fusion Middleware Download, Installation, and Configuration ReadMe Files page, which contains links and important information for obtaining Oracle Fusion Middleware software.

After downloading the .zip file, extract the contents to a directory of your choice; this directory will be referred to as the RCU_HOME directory.

Note:

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

2.4 Starting RCU

Start RCU from the bin directory inside the RCU_HOME directory.

Note:

If you are running RCU using a non-English database, set the following environment variables:

setenv LANG en_US.UTF8
setenv LC_ALL $LANG
setenv NLS_LANG american_america

On Linux operating systems:

cd RCU_HOME/bin
./rcu

On Windows operating systems:

cd RCU_HOME\bin
rcu.bat

If you are creating schemas in your database, go to Section 2.5, "Creating Schemas".

If you are dropping schemas from your database, go to Section 2.6, "Dropping Schemas".

2.5 Creating Schemas

Follow the instructions in Table 2-9 to create schemas.

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

Table 2-9 RCU Screens and Descriptions for Creating Schemas

RCU Screen

Instructions and Action Required

Welcome

None.

Create Repository

Select Create.

Database Connection Details

Specify the connection details for your database, then click Next.

Remember that if you are creating schemas on an IBM DB2 database, you must have already created one operating system user for each schema you want to create. See Section 1.1.4, "Important Information for IBM DB2 Databases" for more information.

A separate dialog window will appear while RCU checks connectivity and some database prerequisites. When the database checking as passed without errors, click OK to dismiss the dialog window and go to the next screen.

Select Components (for Create Operation)

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

To see which schemas are required for your product, see Section 2.2, "Required Schemas and Dependencies".

You must remember the prefix and schema names for the components you are installing; you will need this information during the configuration phase of your product installation. Oracle recommends that you write these values down.

Schema Passwords

Specify the passwords for your schema owners.

You must remember the passwords you enter on this screen; you will need this information during the configuration phase of your product installation. Oracle recommends that you write these values down.

Custom Variables

If selected either Master and Work Repository (ODI_REPO) or Activity Graph and Analytics (ACTIVITES) on the Select Components (for Create Operation), you must supply additional configuration information for custom variables.

Map Tablespaces

Configure the desired tablespace mapping for the schemas you want to create, then click Next.

A separate dialog window will appear asking you to confirm that you want to create these tablespaces. Click OK to proceed and dismiss the dialog window.

A second dialog window will appear showing the progress of tablespace creation. After this is complete, click OK to dismiss this window and go to the next screen.

Summary (for Create Operation)

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

Completion Summary (for Create Operation)

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

2.6 Dropping Schemas

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

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

Table 2-10 RUC Screens and Description for Dropping Schemas

Screen

Instructions and Action Required

Welcome

None.

Create Repository

Select Drop.

Database Connection Details

Specify the connection details for your database, then click Next.

A separate dialog window will appear while RCU checks connectivity and some database prerequisites. When the database checking as 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 you want to drop, then click Next.

A separate dialog window will appear 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 you are dropping. After this is complete, click OK to dismiss this window and go to the next 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.

2.6.1 Dropping Shared Tablespaces

Tablespaces that are shared among multiple schemas will not be 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 Section A.9.1, "Default Tablespace Mappings").

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

2.6.2 Dropping Schemas and Deleting Datafiles (Windows Only)

If your database is running on a Windows operating system, and you are using RCU to drop schemas from that database, some components datafiles are not dropped. These datafiles are located in the oradata directory in the database Oracle home.

For example, the following datafiles must be removed for Oracle Internet Directory (OID):

- ATTRS1_OID.DBF

- BATTRS1_OID.DBF

- GCATS1_OID.DBF

- GDEFAULT1_OID.DBF

- SVRMG1_OID.DBF

- IASTEMP.DBF

In the event you want to re-create the dropped schema, you must first manually delete the datafiles before re-creating the schema.

2.7 Creating the Portal Demo Schema

The Oracle Portal repository includes a demo schema (portal_schema_user_name_DEMO) that can not be installed using RCU. If you want to install this schema for testing purposes, you must do so using the instdemo.sql script:

> sqlplus /nolog
SQL> connect sys as sysdba
SQL> @instdemo.sql portal_schema_user_name
portal_schema_user_password
default_tablespace
temporary_table_space
name_of_the_demo_schema_user
password_of_the_demo_schema_user
name_of_the_log_file
database_connection_string

For example:

SQL> @instdemo.sql portal portalpassword portal ias_temp portal_demo portaldemopassword example_app.log (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=db.example.com)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=orcl)))

3 Extending Repository Creation Utility to Configure Custom Application Repositories

RCU provides an XML-based framework for component owners to plug-in your schema creation and deletion scripts into RCU. This chapter provides some details of the configuration XML files and script-writing guidelines that are used to integrate your components with RCU.

The following topics are covered in this chapter:

- Section 3.1, "RCU Integration Options"

- Section 3.2, "RCU Configuration Files"

- Section 3.3, "RCU Script Writing Guidelines"

3.1 RCU Integration Options

RCU provides the following options for integrating component scripts:

- RCU JDBC Engine Compliant SQL*Plus Scripts

- Pure JDBC Scripts

- SQL*Plus Scripts

- External Processes

- Java Code Using JavaAction

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

3.1.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 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 development environment. However, Oracle recommends that the RCU JDBCEngine tool is also used in your development environment to ensure that these scripts run properly when integrated with RCU.

3.1.2 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() or 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 a more significant re-work for component teams to re-write the scripts in this format.

- Difficult to maintain as every DDL statement has to be wrapped with in EXECUTE IMMEDIATE.

- Cannot be run using SQL*Plus in development environment.

- Less useful error support since the whole block would fail in case of any errors.

Below is an example:

<Action TYPE="JDBC" PERCENT_PROGRESS="20">
<ValidIf DBTYPE="ORACLE" />
<Command TYPE="INLINE">DROP USER %SCHEMA_USER% CASCADE</Command>
</Action>

And a second example:

<Action TYPE="Java" PERCENT_PROGRESS="100">
<Command TYPE="METHOD">
oracle.ias.version.SchemaVersionUtil:utilSetComponentValid
</Command>

<Parameters>
<Parameter TYPE="String">MDS</Parameter>
</Parameters>
</Action>

3.1.3 SQL*Plus Scripts

This option is mainly for the consumption of legacy components that need to be loaded from RCU. This option is available only when running RCU from the CD or standalone shiphome. RCU will use Oracle client on the CD or database server. Any 11g component that is expected to be loaded by launching RCU from the Oracle Home should not use this option.

Example:

<Action TYPE="SQLPlus" PERCENT_PROGRESS="100">
<Command TYPE="SCRIPT">%SCRIPT_HOME%/oid/scripts/seedldap.sql</Command>
<IgnorableErrors>
<Error Type="ORA-01918">user name does not exist</Error>
</IgnorableErrors>
</Action>

And a second example:

<Action TYPE="JDBCSqlScript" PERCENT_PROGRESS="20">
<ValidIf DBTYPE="ORACLE" />
<Command TYPE="SCRIPT">%SCRIPT_HOME%/mds/sql/mds_user.sql</Command>
<Parameters>
<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>

3.1.4 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 RCU error handling framework.

Example:

<Action TYPE="HostCmd">
<Command TYPE="SCRIPT">%RCU_HOME%/rcu/integration/cdb/config/bin/configure</Command>
<Parameters>
<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>

3.1.5 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 LOBs need to be created.

Example:

<Action TYPE="Java">
<Command TYPE="METHOD">
oracle.ias.version.SchemaVersionUtil:utilCreateRegistryEntry
</Command>

<Parameters>
<Parameter TYPE="Connection"></Parameter>
<Parameter TYPE="String">%SCHEMA_USER%</Parameter>
</Parameters>
</Action>

A second example:

<Action TYPE="Java">
<Command TYPE="METHOD">oracle.webdb.config.PortalConfigAssistant:main</Command>
<Parameters>
<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>

3.2 RCU Configuration Files

RCU provides the following configuration files types for component integration:

- Section 3.2.1, "XML DTDs Defined by RCU"

- Section 3.2.2, "Component Repository Configuration File"

- Section 3.2.3, "Component List Configuration File"

- Section 3.2.4, "Soft-Prerequisite Support"

- Section 3.2.5, "Default Tablespaces Configuration File"

3.2.1 XML DTDs Defined by RCU

This section describes the XML DTDs defined by RCU:

- Component Descriptor Configuration File

- Repository Configuration File

- Master List of Supported Components

- Storage Attributes Configuration File

3.2.1.1 Component Descriptor Configuration File

Each component owner would provide a configuration file adhering to following DTD, which lists the pre-requisites and actions:

The Component Descriptor configuration file is called ComponentInfo.dtd and is located in the RCU_HOME/rcu/config (on UNIX operating systems) or RCU_HOME\rcu\config (on Windows operating systems) directory:

<?xml version="1.0" encoding="UTF-8" ?>
<!ENTITY % commonDTD SYSTEM "RCUCommon.dtd">
%commonDTD;
<!ELEMENT ComponentInfo (Display, PrefixSettings, Component*, PrerequisiteDescriptor*, ExecutionDescriptor?, FatalErrors?, IgnorableErrors?)>
<!ATTLIST ComponentInfo
VERSION CDATA #REQUIRED
TYPE CDATA #REQUIRED
RESOURCE_BUNDLE_PACKAGE CDATA #IMPLIED>
<!ELEMENT PrefixSettings (DetectQuery*)>
<!ATTLIST PrefixSettings
USE_SCHEMA_PREFIX (TRUE|FALSE) "TRUE"
USE_TABLESPACE_PREFIX (TRUE|FALSE) "TRUE">
<!ELEMENT Component (ValidIfSet?, ValidIf?, Display, 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 RepositoryConfigFile (#PCDATA)>
<!ELEMENT DetectQuery (#PCDATA)>
<!ATTLIST DetectQuery
OPERATION (CREATE|DROP) 'CREATE'
TYPE (ORACLE|SQLSERVER|IBMDB2|EBR|MYSQL) 'ORACLE'>
<!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" >
<!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|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*)>
<!ATTLIST Variable
TYPE (STRING|NUMBER|PASSWORD|EXISTING_PASSWORD|FILE) "STRING"
MAX_LENGTH CDATA "30"
MIN_LENGTH CDATA "0"
OPERATION (CREATE|DROP|BOTH) "BOTH"
DEFAULT_VALUE CDATA "">
<!ELEMENT Variable (Name,Display)><!ELEMENT Name (#PCDATA)>

3.2.1.2 Repository Configuration File

The Repository configuration file is called RepositoryConfig.dtd and is located in the RCU_HOME/rcu/config (on UNIX operating systems) or RCU_HOME\rcu\config (on Windows operating systems) directory:

<?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*)>

3.2.1.3 Master List of Supported Components

RCU maintains a master list of supported components, which contains entries for each supported component. Every time a new component is added, the master list of supported components is updated with the reference of the XML integration file provided by component owner.

This configuration file is called RCUCommon.dtd and is located in the RCU_HOME/rcu/config (on UNIX operating systems) or RCU_HOME\rcu\config (on Windows operating systems) directory:

<?xml version="1.0" encoding="UTF-8" ?>
<!ELEMENT PrerequisiteDescriptor (DBPrerequisiteSet*, DBPrerequisite*)>
<!ATTLIST PrerequisiteDescriptor
TYPE (CREATE|DROP|REGISTER|DEREGISTER) 'CREATE'>
<!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
PREREQ_TYPE (InitParameter|DBOption|Java|DBComponent|DBVersion|DBObject|CustomSQL|TablespaceFreeMB) "CustomSQL"
DATA_TYPE (STRING|NUMBER) "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) "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"
RESET_SESSION (TRUE|FALSE) "FALSE">
<!ELEMENT Command (#PCDATA)>
<!ATTLIST Command
TYPE (SCRIPT|INLINE|METHOD) "SCRIPT">
<!ELEMENT Parameters (Parameter*)>
<!ELEMENT Parameter (#PCDATA)>
<!ATTLIST Parameter
TYPE (BindVar|CmdLine|ProcessInput|EnvVar|Connection|int|String|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
OPERATOR (OR|AND) "OR">
<!ELEMENT ValidIf (CustomQueryFilter?)>
<!ATTLIST ValidIf
DBTYPE CDATA #IMPLIED
DBVERSION CDATA #IMPLIED
OSNAME CDATA #IMPLIED >
<!ELEMENT CustomQueryFilter (#PCDATA)>
<!ATTLIST CustomQueryFilter
DATA_TYPE (STRING|NUMBER) "STRING"
COMPARE_OPERATOR (EQ|GT|LT|NE|GE|LE|COMPARE_VERSION) "EQ"
VALUE CDATA #REQUIRED >

3.2.1.4 Storage Attributes Configuration File

RCU would maintain the list of tablespaces/datafiles and their attributes 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 RCU_HOME/rcu/config (on UNIX operating systems) or RCU_HOME\rcu\config (on Windows operating systems) directory:

<?xml version="1.0" encoding="UTF-8" ?>
<!ELEMENT StorageAttributes (TablespaceAttributes*)>
<!ELEMENT TablespaceAttributes (Type?,DefaultTemp?,BlockSize?,ExtentSize?,PageSize?,AutoResize?,IncreaseSize?,MaxSize?,Bigfile?,AutoSegmentSpaceManagement?, DatafilesList)>
<!ATTLIST TablespaceAttributes
NAME CDATA #REQUIRED>
<!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>
<!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'>

3.2.2 Component Repository Configuration File

A Component Repository Configuration File (<component>.xml) lists the pre-requisites 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 Component List Configuration File (ComponentInfo.xml).

Each <component>.xml file can be found in the RCU_HOME/rcu/integrationcomponent/component.xml (on UNIX operating systems) or RCU_HOME\rcu\integrationcomponent\component.xml (on Windows operating systems) file.

Component owners can use a set of predefined RCU parameters which will be substituted at runtime by RCU based on user input. Here is the list of predefined parameters:

Table 3-1 Predefined RCU Parameters

RCU Parameter

Description

%ORACLE_HOME%

Location of the Oracle Home directory.

In this book, the actual location is referred to as RCU_HOME; this is the location where RCU was extracted on your system.

%SCRIPT_HOME%

Location where scripts are located. It may be same as RCU_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 or SYSTEM) is none is set.

%DEFAULT_TEMP_TABLESPACE%

Default temporary tablespace in the database (for example, TEMP in 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.

%DB_PORTNUMBER%

Database port number that is provided on the Database Connection Details.

%RCU_HOME%

Directory where RCU is installed.

%SQLPLUS_HOME%

RCU_HOME where SQL*Plus is located.

%RCU_LOG_LOCATION%

Location of the directory where RCU log files are created.

%DATABASE_NMAE%

Database name (for SQLServer database).

Below is a sample Component Repository Configuration file for MDS (mds.xml), which lists the series of prerequisites and actions:

<?xml version="1.0" encoding="UTF-8" ?>
<!-- DOCTYPE RepositoryConfig SYSTEM "file:////home/mmehta/development/XML/latest/RepositoryConfig.dtd" -->
<!--
DESCRIPTION

MDS's RCU configuration file for creating MDS repository.

MODIFIED (MM/DD/YY)
jhsi      07/06/11 - (12700444) Update version number to 11.1.1.6.0
jhsi      04/26/11 - Add ebr support
jhsi      02/23/11 - Bump up version to 11.1.1.5.0
erwang    01/13/11 - Added support for MySQL database.
erwang    10/01/10 - XbranchMerge erwang_bug-10150062 from main
erwang    09/30/10 - #(10150062) Removed SYSDBA requirement
erwang    07/13/10 - #(9831116) Added SYSDBA role check.
????????  ??/??/?? - Creation

-->

<!DOCTYPE RepositoryConfig SYSTEM "RepositoryConfig.dtd">
<RepositoryConfig COMP_ID="MDS">
<PrerequisiteDescriptor>
<DBPrerequisite PREREQ_TYPE="TablespaceFreeMB" DATA_TYPE="NUMBER" COMPARE_OPERATOR="GT">
<ValidIf DBTYPE="ORACLE" />
<PrereqIdentifier>%DEFAULT_TABLESPACE%</PrereqIdentifier>
<PrereqValue>50</PrereqValue>
</DBPrerequisite>
<DBPrerequisite PREREQ_TYPE="TablespaceFreeMB" DATA_TYPE="NUMBER" COMPARE_OPERATOR="GT">
<ValidIf DBTYPE="ORACLE" />
<PrereqIdentifier>%TEMPORARY_TABLESPACE%</PrereqIdentifier>
<PrereqValue>20</PrereqValue>
</DBPrerequisite>
<DBPrerequisite PREREQ_TYPE="CustomSQL" DATA_TYPE="STRING"
COMPARE_OPERATOR="EQ">
<ValidIf DBTYPE="SQLSERVER"/>
<PrereqIdentifier>select is_read_committed_snapshot_on from
sys.databases where name='%DATABASE_NAME%'
</PrereqIdentifier>
<PrereqValue>1</PrereqValue>
<PrereqErrorMsg>
------------------------------------------------------------------------------
Component     : MDS
Error         : Repository creation check failed.
Cause         : Database: '%DATABASE_NAME%' is not configured correctly.
Action        : Alter database to turn on the READ_COMMITTED_SNAPSHOT option.
Ensure you have DBA priviliges. Also the DBA should not have
multiple logins on this database - else it will result in a
lock error.
Command       : ALTER database %DATABASE_NAME% SET READ_COMMITTED_SNAPSHOT ON
-------------------------------------------------------------------------------
</PrereqErrorMsg>
</DBPrerequisite>
<DBPrerequisite PREREQ_TYPE="CustomSQL"
DATA_TYPE="NUMBER"
COMPARE_OPERATOR="GE">
<ValidIf DBTYPE="SQLSERVER"/>
<PrereqIdentifier>select count(*) from sys.databases
where name='%DATABASE_NAME%' AND
patindex('%%[_]CS[_]%%', collation_name) > 0
</PrereqIdentifier>
<PrereqValue>1</PrereqValue>
<PrereqErrorMsg>
-------------------------------------------------------------------------------
Component     : MDS
Error         : Repository creation check failed.
Cause         : Database: '%DATABASE_NAME%' is not configured correctly.
Action        : Alter database to apply the correct collate to the database.
Ensure you have DBA priviliges. Also, the DBA should not have
multiple logins on this database - else it will result in a
lock error.
Command       : DECLARE @collate   sysname
SELECT @collate = convert(sysname, serverproperty('COLLATION'))
IF ( charindex(N'_CI', @collate) > 0 )
BEGIN
select @collate = replace(@collate, N'_CI', N'_CS')
exec ('ALTER database $(DATABASE_NAME) COLLATE ' + @collate)
END
GO
-------------------------------------------------------------------------------
</PrereqErrorMsg>
</DBPrerequisite>

</PrerequisiteDescriptor>

<PrerequisiteDescriptor TYPE="DROP">
<DBPrerequisite PREREQ_TYPE="CustomSQL" DATA_TYPE="NUMBER" COMPARE_OPERATOR="EQ">

<ValidIf DBTYPE="ORACLE" />
<PrereqIdentifier>select count(*) from v$session where
username='%SCHEMA_USER%'</PrereqIdentifier>
<PrereqValue>0</PrereqValue>
<PrereqErrorMsg>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">

<ValidIf DBTYPE="EBR" />
<PrereqIdentifier>select count(*) from v$session where
username='%SCHEMA_USER%'</PrereqIdentifier>
<PrereqValue>0</PrereqValue>
<PrereqErrorMsg>The schema owner '%SCHEMA_USER%' is connected to the
database. Please disconnect and try again.</PrereqErrorMsg>
</DBPrerequisite>
</PrerequisiteDescriptor>

<ExecutionDescriptor>
<Action TYPE="Java">
<Command TYPE="METHOD">oracle.ias.version.SchemaVersionUtil:utilCreateRegistryEntry</Command>
<Parameters>
<Parameter TYPE="Connection"></Parameter>
<Parameter TYPE="String">MDS</Parameter>
<Parameter TYPE="String">Metadata Services</Parameter>
<Parameter TYPE="String">%PREFIX_NAME%</Parameter>
<Parameter TYPE="String">MDS</Parameter>
<Parameter TYPE="String">MDS</Parameter>
<Parameter TYPE="String">%SCHEMA_USER%</Parameter>
<Parameter TYPE="String">11.1.1.6.0</Parameter>
<Parameter TYPE="String">LOADING</Parameter>
</Parameters>
</Action>
<Action TYPE="JDBCSqlScript" PERCENT_PROGRESS="20">
<ValidIf DBTYPE="ORACLE" />
<Command TYPE="SCRIPT">%SCRIPT_HOME%/mds/sql/mds_user.sql</Command>
<Parameters>
<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>
<Action TYPE="JDBCSqlScript" PERCENT_PROGRESS="20">
<ValidIf DBTYPE="EBR" />
<Command TYPE="SCRIPT">%SCRIPT_HOME%/mds/oracle_ebr/mds_user.sql</Command>
<Parameters>
<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>
</Action>
<Action TYPE="JDBCSqlScript" PERCENT_PROGRESS="20">
<ValidIf DBTYPE="SQLSERVER" />
<Command TYPE="SCRIPT">%SCRIPT_HOME%/mds/MSSQL/cremduser-rcu.sql</Command>
<Parameters>
<Parameter TYPE="CmdLine">%DATABASE_NAME%</Parameter>
<Parameter TYPE="CmdLine">%SCHEMA_USER%</Parameter>
<Parameter TYPE="CmdLine">%SCHEMA_PASSWORD%</Parameter>
</Parameters>
</Action>
<Action TYPE="JDBCSqlScript" PERCENT_PROGRESS="20">
<ValidIf DBTYPE="IBMDB2" />
<Command TYPE="SCRIPT">%SCRIPT_HOME%/mds/db2/cremduser-rcu.db2</Command>
<Parameters>
<Parameter TYPE="CmdLine">%SCHEMA_USER%</Parameter>
<Parameter TYPE="CmdLine">%DEFAULT_TABLESPACE%</Parameter>
<Parameter TYPE="CmdLine">%TEMPORARY_TABLESPACE%</Parameter>
</Parameters>
</Action>
<Action TYPE="JDBCSqlScript" PERCENT_PROGRESS="20">
<ValidIf DBTYPE="MYSQL" />
<Command TYPE="SCRIPT">%SCRIPT_HOME%/mds/mysql/cremduser-rcu.sql</Command>
<Parameters>
<Parameter TYPE="CmdLine">%SCHEMA_USER%</Parameter>
<Parameter TYPE="CmdLine">%SCHEMA_PASSWORD%</Parameter>
</Parameters>
</Action>
<Action TYPE="JDBCSqlScript" PERCENT_PROGRESS="20">
<ValidIf DBTYPE="ORACLE" />
<Command TYPE="SCRIPT">%SCRIPT_HOME%/mds/sql/cremds-rcu.sql</Command>
<Parameters>
<Parameter TYPE="CmdLine">%SCHEMA_USER%</Parameter>
</Parameters>
</Action>
<Action TYPE="JDBCSqlScript" PERCENT_PROGRESS="20">
<ValidIf DBTYPE="EBR" />
<Command TYPE="SCRIPT">%SCRIPT_HOME%/mds/oracle_ebr/cremds-rcu.sql</Command>
<Parameters>
<Parameter TYPE="CmdLine">%SCHEMA_USER%</Parameter>
<Parameter TYPE="CmdLine">%EDITION_NAME%</Parameter>
</Parameters>
</Action>
<Action TYPE="JDBCSqlScript" PERCENT_PROGRESS="20" CONNECT_AS_OWNER="TRUE">
<ValidIf DBTYPE="SQLSERVER" />
<Command TYPE="SCRIPT">%SCRIPT_HOME%/mds/MSSQL/cremds-rcu.sql</Command>
<Parameters>
<Parameter TYPE="CmdLine">%DATABASE_NAME%</Parameter>
<Parameter TYPE="CmdLine">%RCU_VARCHAR%</Parameter>
</Parameters>
</Action>
<Action TYPE="JDBCSqlScript" PERCENT_PROGRESS="20" CONNECT_AS_OWNER="TRUE">
<ValidIf DBTYPE="IBMDB2" />
<Command TYPE="SCRIPT">%SCRIPT_HOME%/mds/db2/cremds-rcu.db2</Command>
<Parameters>
<Parameter TYPE="CmdLine">%DEFAULT_TABLESPACE%</Parameter>
</Parameters>
</Action>
<Action TYPE="JDBCSqlScript" PERCENT_PROGRESS="20" CONNECT_AS_OWNER="TRUE">
<ValidIf DBTYPE="MYSQL" />
<Command TYPE="SCRIPT">%SCRIPT_HOME%/mds/mysql/cremds-rcu.sql</Command>
<Parameters>
<Parameter TYPE="CmdLine">%SCHEMA_USER%</Parameter>
</Parameters>
</Action>
<Action TYPE="Java">
<Command TYPE="METHOD">oracle.ias.version.SchemaVersionUtil:utilSetComponentValid</Command>
<Parameters>
<Parameter TYPE="String">MDS</Parameter>
</Parameters>
</Action>
</ExecutionDescriptor>
<DeleteDescriptor>
<Action TYPE="JDBC" PERCENT_PROGRESS="20">
<ValidIf DBTYPE="ORACLE" />
<Command TYPE="INLINE">DROP USER %SCHEMA_USER% CASCADE</Command>
</Action>
<Action TYPE="JDBC" PERCENT_PROGRESS="20">
<ValidIf DBTYPE="EBR" />
<Command TYPE="INLINE">DROP USER %SCHEMA_USER% CASCADE</Command>
</Action>
<Action TYPE="JDBCSqlScript" PERCENT_PROGRESS="20">
<ValidIf DBTYPE="SQLSERVER" />
<Command TYPE="SCRIPT">%SCRIPT_HOME%/mds/MSSQL/dropmduser-rcu.sql</Command>
<Parameters>
<Parameter TYPE="CmdLine">%DATABASE_NAME%</Parameter>
<Parameter TYPE="CmdLine">%SCHEMA_USER%</Parameter>
</Parameters>
</Action>
<Action TYPE="JDBCSqlScript" PERCENT_PROGRESS="20">
<ValidIf DBTYPE="IBMDB2" />
<Command TYPE="SCRIPT">%SCRIPT_HOME%/mds/db2/dropmds-rcu.db2</Command>
<Parameters>
<Parameter TYPE="CmdLine">%SCHEMA_USER%</Parameter>
</Parameters>
</Action>
<Action TYPE="Java">
<ValidIf DBTYPE="IBMDB2" />
<Command TYPE="METHOD">oracle.sysman.assistants.common.dbutil.jdbc.DB2DropUtil:dropCompRepos</Command>
<Parameters>
<Parameter TYPE="Connection"></Parameter>
<Parameter TYPE="String">%SCHEMA_USER%</Parameter>
</Parameters>
</Action>
<Action TYPE="JDBC" PERCENT_PROGRESS="20">
<ValidIf DBTYPE="MYSQL" />
<Command TYPE="INLINE">DROP USER %SCHEMA_USER% ,%SCHEMA_USER%@'localhost' </Command>
</Action>
<Action TYPE="JDBC" PERCENT_PROGRESS="20">
<ValidIf DBTYPE="MYSQL" />
<Command TYPE="INLINE">DROP SCHEMA IF EXISTS %SCHEMA_USER% </Command>
</Action>
<Action TYPE="Java">
<Command TYPE="METHOD">oracle.ias.version.SchemaVersionUtil:utilDropRegistryEntry</Command>
<Parameters>
<Parameter TYPE="Connection"></Parameter>
<Parameter TYPE="String">MDS</Parameter>
<Parameter TYPE="String">%PREFIX_NAME%</Parameter>
<Parameter TYPE="String">MDS</Parameter>
</Parameters>
</Action>
</DeleteDescriptor>
</RepositoryConfig>

3.2.3 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 pre-requisite 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.

This file can be found in the RCU_HOME/rcu/config (on UNIX operating systems) or RCU_HOME\rcu\config (on Windows operating systems) directory.

Below is a sample ComponentInfo.xml file:

<?xml version="1.0" encoding="UTF-8" ?>
<!-- DOCTYPE ComponentInfo SYSTEM "dtds/ComponentInfo.dtd" -->
<!DOCTYPE ComponentInfo SYSTEM "ComponentInfo.dtd" [
<!ENTITY mds SYSTEM "../integration/mds/mds_ComponentInfo.xml">
<!ENTITY oid SYSTEM "../integration/oid/oid_ComponentInfo.xml">
<!ENTITY soainfra SYSTEM "../integration/soainfra/soainfra_ComponentInfo.xml">
<!ENTITY bam SYSTEM "../integration/bam/bam_ComponentInfo.xml">
<!ENTITY WebCenterSuite SYSTEM "../integration/webcenter/WebCenterSuite_ComponentInfo.xml">
<!ENTITY iau SYSTEM "../integration/iau/iau_ComponentInfo.xml">
<!ENTITY iauoes SYSTEM "../integration/iauoes/iauoes_ComponentInfo.xml">
<!ENTITY discoverer SYSTEM "../integration/dc/discoverer_ComponentInfo.xml">
<!ENTITY sdpm SYSTEM "../integration/sdpm/sdpm_ComponentInfo.xml">
<!ENTITY portal SYSTEM "../integration/portal/portal_ComponentInfo.xml">
<!ENTITY oif SYSTEM "../integration/oif/oif_ComponentInfo.xml">
<!ENTITY oim SYSTEM "../integration/oim/oim_ComponentInfo.xml">
<!ENTITY oam SYSTEM "../integration/oam/oam_ComponentInfo.xml">
<!ENTITY oaam SYSTEM "../integration/oaam/oaam_ComponentInfo.xml">
<!ENTITY oaam_with_partition SYSTEM "../integration/oaam/oaam_with_partition_ComponentInfo.xml">
<!ENTITY oaam_with_mssql_unicode SYSTEM "../integration/oaam/oaam_with_mssql_unicode_ComponentInfo.xml">
<!ENTITY irm SYSTEM "../integration/irm/irm_ComponentInfo.xml">
<!ENTITY ess SYSTEM "../integration/ess/ess_ComponentInfo.xml">
<!ENTITY odi SYSTEM "../integration/odi/odi_ComponentInfo.xml">
<!ENTITY biplatform SYSTEM "../integration/biplatform/biplatform_ComponentInfo.xml">
<!ENTITY contentserver11 SYSTEM "../integration/contentserver11/contentserver11_ComponentInfo.xml">
<!ENTITY contentserver11search SYSTEM "../integration/contentserver11search/contentserver11search_ComponentInfo.xml">
<!ENTITY urm SYSTEM "../integration/urm/urm_ComponentInfo.xml">
<!ENTITY ipm SYSTEM "../integration/ipm/ipm_ComponentInfo.xml">
<!ENTITY commspresence SYSTEM "../integration/commspresence/commspresence_ComponentInfo.xml">
<!ENTITY commssds SYSTEM "../integration/commssds/commssds_ComponentInfo.xml">
<!ENTITY commsls SYSTEM "../integration/commsls/commsls_ComponentInfo.xml">
<!ENTITY epm SYSTEM "../integration/epm/epm_ComponentInfo.xml">
<!ENTITY apm SYSTEM "../integration/apm/apm_ComponentInfo.xml">
<!ENTITY opss SYSTEM "../integration/opss/opss_ComponentInfo.xml">
]>
<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>
<PrefixSettings USE_SCHEMA_PREFIX="TRUE" USE_TABLESPACE_PREFIX="TRUE">
<DetectQuery>
Select distinct mrc_name from schema_version_registry
</DetectQuery>
<DetectQuery TYPE="IBMDB2">
Select distinct mrc_name from NULLID.schema_version_registry
</DetectQuery>
</PrefixSettings>

<!-- AS Common GROUP START -->
<Component ID="AS_COMMON" IS_GROUPING_COMPONENT="TRUE">
<Display NLS_ID="AS_COMMON_ID">AS Common Schemas</Display>
</Component>
&mds;
&iau;
&iauoes;
&ess;
&opss;
<!-- AS Common GROUP END -->

<!-- OID GROUP START -->
<Component ID="IDM" IS_GROUPING_COMPONENT="TRUE">
<Display NLS_ID="IDM_ID">Identity Management</Display>
</Component>
&oid;
&oif;
&oim;
&oam;
&oaam;
&oaam_with_partition;
&oaam_with_mssql_unicode;
&apm;

<!-- OID GROUP START -->

<!-- ECM_SUITE START -->
<Component ID="ECM_SUITE" IS_GROUPING_COMPONENT="TRUE">
<Display NLS_ID="ECM_SUITE">WebCenter Content</Display>
</Component>
&irm;
&contentserver11;
&contentserver11search;
&urm;
&ipm;
<!-- ECM_SUITE END -->

<!-- ODI_SUITE START -->
<Component ID="ODI_REPOSITORIES" IS_GROUPING_COMPONENT="TRUE">
<Display NLS_ID="ODI_REPOSITORIES">Oracle Data Integrator</Display>
</Component>
&odi;
<!-- ODI_SUITE END -->

<!-- BI_SUITE START -->
<Component ID="BUSINESS INTELLIGENCE" IS_GROUPING_COMPONENT="TRUE">
<Display NLS_ID="BUSINESS INTELLIGENCE">Oracle Business Intelligence</Display>
</Component>
&biplatform;
<!-- BI_SUITE END -->

<!-- OWLCS START -->
<Component ID="OWLCS" IS_GROUPING_COMPONENT="TRUE">
<ValidIf DBTYPE="ORACLE" />
<Display NLS_ID="OWLCS_ID">WebLogic Communication Services</Display>
</Component>
&commspresence;
&commssds;
&commsls;
<!-- OWLCS END -->

<!-- SOA INFRA GROUP START -->
<Component ID="SOA" IS_GROUPING_COMPONENT="TRUE">
<Display NLS_ID="SOA_ID">SOA and BPM Infrastructure</Display>
</Component>
&soainfra;
&bam;
&sdpm;
<!-- SOA INFRA GROUP END -->

<!-- WEBCENTER_SUITE START -->
<Component ID="WEBCENTER_SUITE" IS_GROUPING_COMPONENT="TRUE">
<Display NLS_ID="WEBCENTER_SUITE_ID">WebCenter Portal</Display>
</Component>
&WebCenterSuite;
<!-- WEBCENTER_SUITE END -->

<!-- PORTAL_BI START -->
<Component ID="PORTAL_BI" IS_GROUPING_COMPONENT="TRUE">
<ValidIf DBTYPE="ORACLE" />
<Display NLS_ID="PORTAL_BI_ID">Portal and BI</Display>
</Component>

&portal;
&discoverer;

&epm;
<!-- AS Common GROUP END -->

<!-- PORTAL_BI END -->

<!--
<Component ID="CAS" PROGRESS_UNITS="30">
<Display NLS_ID="CAS_ID">Management Administration Server</Display>
<RepositoryConfigFile>%SCRIPT_HOME%/cas/cas.xml</RepositoryConfigFile>
<DetectQuery>select owner from schema_version_registry where mr_type = 'CAS' and mrc_name = '%PREFIX_NAME%'</DetectQuery>
<SchemaUser>MAS</SchemaUser>
<Tablespaces>
<Tablespace TYPE="DEFAULT_TABLESPACE">
<Prompt NLS_ID="DEFAULT_TABLESPACE">Default Tablespace</Prompt>
<TablespaceName>IAS_MAS</TablespaceName>
</Tablespace>
<Tablespace TYPE="TEMPORARY_TABLESPACE">
<Prompt NLS_ID="TEMPORARY_TABLESPACE">Temporary Tablespace</Prompt>
<TablespaceName>IAS_TEMP</TablespaceName>
</Tablespace>
</Tablespaces>
</Component>

<Component ID="MID" IS_GROUPING_COMPONENT="TRUE">
<Display NLS_ID="MID_ID">Middleware Components</Display>
</Component>

<Component ID="BPEL" PROGRESS_UNITS="30" CHILD_OF="MID">
<Display NLS_ID="BPEL_ID">BPEL DB Checkpoint Store</Display>
<RepositoryConfigFile>%SCRIPT_HOME%/cas/cas.xml</RepositoryConfigFile>
<DetectQuery>select owner from schema_version_registry where mr_type = 'BPEL' and mrc_name = '%PREFIX_NAME%'</DetectQuery>
<SchemaUser>BPEL</SchemaUser>
<Tablespaces>
<Tablespace TYPE="DEFAULT_TABLESPACE">
<Prompt NLS_ID="DEFAULT_TABLESPACE">Default Tablespace</Prompt>
<TablespaceName>IAS_MID</TablespaceName>
</Tablespace>
<Tablespace TYPE="TEMPORARY_TABLESPACE">
<Prompt NLS_ID="TEMPORARY_TABLESPACE">Temporary Tablespace</Prompt>
<TablespaceName>IAS_TEMP</TablespaceName>
</Tablespace>
</Tablespaces>
</Component>

<Component ID="OPTM" PROGRESS_UNITS="30" CHILD_OF="MID">
<Display NLS_ID="OPTM_ID">Optimization</Display>
<RepositoryConfigFile>%SCRIPT_HOME%/cas/cas.xml</RepositoryConfigFile>
<DetectQuery>select owner from schema_version_registry where mr_type = 'OPTM' and mrc_name = '%PREFIX_NAME%'</DetectQuery>
<SchemaUser>OPTM</SchemaUser>
<Tablespaces>
<Tablespace TYPE="DEFAULT_TABLESPACE">
<Prompt NLS_ID="DEFAULT_TABLESPACE">Default Tablespace</Prompt>
<TablespaceName>IAS_MID</TablespaceName>
</Tablespace>
<Tablespace TYPE="TEMPORARY_TABLESPACE">
<Prompt NLS_ID="TEMPORARY_TABLESPACE">Temporary Tablespace</Prompt>
<TablespaceName>IAS_TEMP</TablespaceName>
</Tablespace>
</Tablespaces>
</Component>

<Component ID="RFID" PROGRESS_UNITS="30" CHILD_OF="MID">
<Display NLS_ID="RFID_ID">RFID Sensor Store</Display>
<RepositoryConfigFile>%SCRIPT_HOME%/cas/cas.xml</RepositoryConfigFile>
<DetectQuery>select owner from schema_version_registry where mr_type = 'RFID' and mrc_name = '%PREFIX_NAME%'</DetectQuery>
<SchemaUser>RFID</SchemaUser>
<Tablespaces>
<Tablespace TYPE="DEFAULT_TABLESPACE">
<Prompt NLS_ID="DEFAULT_TABLESPACE">Default Tablespace</Prompt>
<TablespaceName>IAS_MID</TablespaceName>
</Tablespace>
<Tablespace TYPE="TEMPORARY_TABLESPACE">
<Prompt NLS_ID="TEMPORARY_TABLESPACE">Temporary Tablespace</Prompt>
<TablespaceName>IAS_TEMP</TablespaceName>
</Tablespace>
</Tablespaces>
</Component>

<Component ID="WKP" PROGRESS_UNITS="30" CHILD_OF="MID">
<Display NLS_ID="WKP_ID">Workplace</Display>
<RepositoryConfigFile>%SCRIPT_HOME%/cas/cas.xml</RepositoryConfigFile>
<DetectQuery>select owner from schema_version_registry where mr_type = 'WKP' and mrc_name = '%PREFIX_NAME%'</DetectQuery>
<SchemaUser>WKP</SchemaUser>
<Tablespaces>
<Tablespace TYPE="DEFAULT_TABLESPACE">
<Prompt NLS_ID="DEFAULT_TABLESPACE">Default Tablespace</Prompt>
<TablespaceName>IAS_MID</TablespaceName>
</Tablespace>
<Tablespace TYPE="TEMPORARY_TABLESPACE">
<Prompt NLS_ID="TEMPORARY_TABLESPACE">Temporary Tablespace</Prompt>
<TablespaceName>IAS_TEMP</TablespaceName>
</Tablespace>
</Tablespaces>
</Component>

-->

<PrerequisiteDescriptor>
<DBPrerequisiteSet OPERATOR="OR">
<ValidIf DBTYPE="ORACLE" />
<DBPrerequisite PREREQ_TYPE="InitParameter" DATA_TYPE="NUMBER" COMPARE_OPERATOR="GE">
<PrereqIdentifier>SHARED_POOL_SIZE</PrereqIdentifier>
<PrereqValue UNIT="KB">147456</PrereqValue>
</DBPrerequisite>
<DBPrerequisite PREREQ_TYPE="InitParameter" DATA_TYPE="NUMBER" COMPARE_OPERATOR="GE">
<PrereqIdentifier>SGA_MAX_SIZE</PrereqIdentifier>
<PrereqValue UNIT="KB">147456</PrereqValue>
</DBPrerequisite>
</DBPrerequisiteSet>

<DBPrerequisite PREREQ_TYPE="InitParameter" DATA_TYPE="NUMBER" COMPARE_OPERATOR="GE">
<ValidIf DBTYPE="ORACLE" />
<PrereqIdentifier>DB_BLOCK_SIZE</PrereqIdentifier>
<PrereqValue UNIT="KB">8</PrereqValue>
</DBPrerequisite>
<!--DBPrerequisite PREREQ_TYPE="CustomSQL" DATA_TYPE="STRING" COMPARE_OPERATOR="NE">
<ValidIf  DBTYPE="ORACLE" >
<CustomQueryFilter DATA_TYPE="NUMBER" COMPARE_OPERATOR="EQ" VALUE="0">
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>
<PrereqValue>11.1.0.6.0</PrereqValue>
<PrereqErrorMsg>
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">
<ValidIf  DBTYPE="ORACLE" >
<CustomQueryFilter DATA_TYPE="NUMBER" COMPARE_OPERATOR="EQ" VALUE="0">
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>
<PrereqValue>10.2.0.4.0</PrereqValue>
<PrereqErrorMsg>
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>

<DBPrerequisite PREREQ_TYPE="CustomSQL" DATA_TYPE="NUMBER" COMPARE_OPERATOR="EQ">
<ValidIf  DBTYPE="ORACLE" >
<CustomQueryFilter DATA_TYPE="NUMBER" COMPARE_OPERATOR="EQ" VALUE="0">
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>
<PrereqValue>0</PrereqValue>
<PrereqErrorMsg>
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>

<DBPrerequisite PREREQ_TYPE="CustomSQL" DATA_TYPE="NUMBER" COMPARE_OPERATOR="EQ">
<ValidIf DBTYPE="IBMDB2"/>
<PrereqIdentifier>select count(*) from syscat.tablespaces where tbspace = 'SYSCATSPACE' and pagesize >= 32768
</PrereqIdentifier>
<PrereqValue>1</PrereqValue>
<PrereqErrorMsg>
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>

<DBPrerequisite PREREQ_TYPE="CustomSQL" DATA_TYPE="STRING" COMPARE_OPERATOR="EQ">
<ValidIf DBTYPE="SQLSERVER" />
<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>
<PrereqValue>0</PrereqValue>
<PrereqErrorMsg>
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>

<DBPrerequisite PREREQ_TYPE="CustomSQL" DATA_TYPE="STRING" COMPARE_OPERATOR="EQ">
<ValidIf DBTYPE="IBMDB2" />
<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 )) &lt; 7 OR INT(substr(service_level, POSSTR(service_level, 'v')+1, LOCATE('.', service_level,POSSTR(service_level, 'v') +1) - POSSTR(service_level, 'v') -1 ) ) &lt; 9</PrereqIdentifier>
<PrereqValue>0</PrereqValue>
<PrereqErrorMsg>
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">
<ValidIf DBTYPE="ORACLE" />
<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>
<PrereqValue>DBA</PrereqValue>
<PrereqErrorMsg>
User should have sysdba or dba privilages.
</PrereqErrorMsg>
</DBPrerequisite>

<DBPrerequisite PREREQ_TYPE="CustomSQL" DATA_TYPE="STRING" COMPARE_OPERATOR="EQ">
<ValidIf DBTYPE="SQLSERVER" />
<PrereqIdentifier>select Is_Member('db_owner')</PrereqIdentifier>
<PrereqValue>1</PrereqValue>
<PrereqErrorMsg>
User should have sysdba or dba privilages.
</PrereqErrorMsg>
</DBPrerequisite>

<DBPrerequisite PREREQ_TYPE="CustomSQL" DATA_TYPE="STRING" COMPARE_OPERATOR="EQ" SOFT="TRUE">
<ValidIf DBTYPE="ORACLE" />
<PrereqIdentifier>select value from nls_database_parameters where parameter = 'NLS_CHARACTERSET'</PrereqIdentifier>
<PrereqValue>AL32UTF8</PrereqValue>
<PrereqErrorMsg>
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">
<ValidIf  DBTYPE="ORACLE" >
<CustomQueryFilter DATA_TYPE="NUMBER" COMPARE_OPERATOR="EQ" VALUE="0">
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>
<PrereqValue>0</PrereqValue>
<PrereqErrorMsg>
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">
<ValidIf  DBTYPE="ORACLE" >
<CustomQueryFilter DATA_TYPE="NUMBER" COMPARE_OPERATOR="EQ" VALUE="0">
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 not like '11.2._._._'</PrereqIdentifier>
<PrereqValue>0</PrereqValue>
<PrereqErrorMsg>
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">
<ValidIf  DBTYPE="ORACLE" >
</ValidIf>
<PrereqIdentifier>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') </PrereqIdentifier>
<PrereqValue>0</PrereqValue>
<PrereqErrorMsg>
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 matrixfor supported DB versions
</PrereqErrorMsg>
</DBPrerequisite>

<DBPrerequisite PREREQ_TYPE="CustomSQL" DATA_TYPE="STRING" COMPARE_OPERATOR="EQ" SOFT="TRUE">
<ValidIf DBTYPE="SQLSERVER" />
<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>
<PrereqValue>0</PrereqValue>
<PrereqErrorMsg>
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">
<ValidIf DBTYPE="IBMDB2" />
<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 )) &gt; 7 or INT(substr(service_level, POSSTR(service_level, 'v')+1, LOCATE('.', service_level, POSSTR(service_level, 'v') +1) - POSSTR(service_level, 'v') -1 ) ) &gt; 9</PrereqIdentifier>
<PrereqValue>0</PrereqValue>
<PrereqErrorMsg>
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">
<ValidIf DBTYPE="MYSQL" />
<PrereqIdentifier>select version() &lt; '5.5.14'</PrereqIdentifier>
<PrereqValue>0</PrereqValue>
<PrereqErrorMsg>
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">
<ValidIf DBTYPE="MYSQL" />
<PrereqIdentifier>select version() &gt; '5.6' or version() = '5.6'</PrereqIdentifier>
<PrereqValue>0</PrereqValue>
<PrereqErrorMsg>
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">
<ValidIf DBTYPE="MYSQL" />
<PrereqIdentifier>select VARIABLE_VALUE from INFORMATION_SCHEMA.GLOBAL_VARIABLES where VARIABLE_NAME = 'INNODB_FILE_PER_TABLE'</PrereqIdentifier>
<PrereqValue>ON</PrereqValue>
<PrereqErrorMsg>
DB Init Param Prerequisite failure for INNODB_FILE_PER_TABLE. Its value should be 'ON'.
</PrereqErrorMsg>
</DBPrerequisite>

<DBPrerequisite PREREQ_TYPE="CustomSQL" DATA_TYPE="STRING" COMPARE_OPERATOR="EQ">
<ValidIf DBTYPE="MYSQL" />
<PrereqIdentifier>select VARIABLE_VALUE from INFORMATION_SCHEMA.GLOBAL_VARIABLES where VARIABLE_NAME = 'INNODB_FILE_FORMAT'</PrereqIdentifier>
<PrereqValue>Barracuda</PrereqValue>
<PrereqErrorMsg>
DB Init Param Prerequisite failure for INNODB_FILE_FORMAT. Its value should be 'Barracuda'.
</PrereqErrorMsg>
</DBPrerequisite>

<DBPrerequisite PREREQ_TYPE="CustomSQL" DATA_TYPE="STRING" COMPARE_OPERATOR="EQ">
<ValidIf DBTYPE="MYSQL" />
<PrereqIdentifier>select VARIABLE_VALUE from INFORMATION_SCHEMA.GLOBAL_VARIABLES where VARIABLE_NAME = 'INNODB_LARGE_PREFIX'</PrereqIdentifier>
<PrereqValue>ON</PrereqValue>
<PrereqErrorMsg>
DB Init Param Prerequisite failure for INNODB_LARGE_PREFIX. Its value should be 'ON'.
</PrereqErrorMsg>
</DBPrerequisite>

</PrerequisiteDescriptor>

<ExecutionDescriptor TYPE="PreLoad">
<Action TYPE="Java" PERCENT_PROGRESS="60">
<ValidIf DBTYPE="ORACLE">
<CustomQueryFilter DATA_TYPE="NUMBER" COMPARE_OPERATOR="EQ" VALUE="1">
select count(*) from  dba_views where VIEW_NAME = 'APP_REGISTRY' and not exists (select view_name from  dba_views where VIEW_NAME= 'SCHEMA_VERSION_REGISTRY')
</CustomQueryFilter>
</ValidIf>
<Command TYPE="METHOD">oracle.ias.version.SchemaVersionUtil:utilCreateRegistryAndCopyData</Command>
<Parameters>
<Parameter TYPE="Connection"></Parameter>
</Parameters>
</Action>
<Action TYPE="Java" PERCENT_PROGRESS="60">
<ValidIf DBTYPE="ORACLE">
<CustomQueryFilter DATA_TYPE="NUMBER" COMPARE_OPERATOR="EQ" VALUE="0">
select count(*) from  dba_views where VIEW_NAME= 'SCHEMA_VERSION_REGISTRY'
</CustomQueryFilter>
</ValidIf>
<Command TYPE="METHOD">oracle.ias.version.SchemaVersionUtil:utilCreateRegistryTable</Command>
<Parameters>
<Parameter TYPE="Connection"></Parameter>
</Parameters>
</Action>
<Action TYPE="Java" PERCENT_PROGRESS="60">
<ValidIf DBTYPE="SQLSERVER">
<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>
<Parameter TYPE="Connection"></Parameter>
</Parameters>
</Action>
<Action TYPE="Java" PERCENT_PROGRESS="60">
<ValidIf DBTYPE="IBMDB2">
<CustomQueryFilter DATA_TYPE="NUMBER" COMPARE_OPERATOR="EQ" VALUE="0">
select count(*) from syscat.tables where TABNAME='SCHEMA_VERSION_REGISTRY'
</CustomQueryFilter>
</ValidIf>
<Command TYPE="METHOD">oracle.ias.version.SchemaVersionUtil:utilCreateRegistryTable</Command>
<Parameters>
<Parameter TYPE="Connection"></Parameter>
</Parameters>
</Action>
<Action TYPE="Java" PERCENT_PROGRESS="60">
<ValidIf DBTYPE="EBR">
<CustomQueryFilter DATA_TYPE="NUMBER" COMPARE_OPERATOR="EQ" VALUE="1">
select count(*) from  dba_views where VIEW_NAME = 'APP_REGISTRY' and not exists (select view_name from  dba_views where VIEW_NAME= 'SCHEMA_VERSION_REGISTRY')
</CustomQueryFilter>
</ValidIf>
<Command TYPE="METHOD">oracle.ias.version.SchemaVersionUtil:utilCreateRegistryAndCopyData</Command>
<Parameters>
<Parameter TYPE="Connection"></Parameter>
</Parameters>
</Action>
<Action TYPE="Java" PERCENT_PROGRESS="60">
<ValidIf DBTYPE="EBR">
<CustomQueryFilter DATA_TYPE="NUMBER" COMPARE_OPERATOR="EQ" VALUE="0">
select count(*) from  dba_views where VIEW_NAME= 'SCHEMA_VERSION_REGISTRY'
</CustomQueryFilter>
</ValidIf>
<Command TYPE="METHOD">oracle.ias.version.SchemaVersionUtil:utilCreateRegistryTable</Command>
<Parameters>
<Parameter TYPE="Connection"></Parameter>
</Parameters>
</Action>

<Action TYPE="Java" PERCENT_PROGRESS="60">
<ValidIf DBTYPE="MYSQL">
<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>
<Parameter TYPE="Connection"></Parameter>
</Parameters>
</Action>
</ExecutionDescriptor>

<FatalErrors>
<Error Type="ORA-17439">Invalid SQL type</Error>
<Error Type="ORA-01435">user does not exist</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>

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

3.2.4 Soft-Prerequisite Support

In the ComponentInfo.xml file, If a particular <DBPrerequisiteSet> or <DBPrerequisite> is not mandatory, then you can use the soft-prerequisite option by setting the SOFT attribute to TRUE. When a soft-prerequisite is not met, a pop-up dialog window with an error or warning message will appear; the user will have the option to ignore the message or abort the operation. You can define a soft-prerequisite at the <DBPrerequisiteSet> level, the <DBPrerequisite> level, or both; if both are defined, then <DBPrerequisiteSet> will take higher precedence.

Below is an example of setting a soft-prerequisite at the <DBPrerequisite> level:

<DBPrerequisiteSet>
...
<DBPrerequisite PREREQ_TYPE="CustomSQL" DATA_TYPE="STRING" COMPARE_OPERATOR="EQ" SOFT="TRUE">
<PrereqIdentifier>select value from nls_database_parameters where parameter = 'NLS_CHARACTERSET'</PrereqIdentifier>
<PrereqValue>AL32UTF8</PrereqValue>
<PrereqErrorMsg>
The database you are connecting is with non-AL32UTF8 character set.
Oracle strongly recommends using AL32UTF8 as the database character
set.
</PrereqErrorMsg>
</DBPrerequisite>
...
<DBPrerequisiteSet>

3.2.5 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 RCU_HOME/rcu/config (on UNIX operating systems) or RCU_HOME\rcu\config (on Windows operating systems) directory.

The actual tablespace configuration file for each component is located in the RCU_HOME/rcu/integrationcomponent/component_Storage.xml (on UNIX operating systems) or RCU_HOME\rcu\integrationcomponent\component_Storage.xml (on Windows operating systems) file. Each component has its own tablespaces configuration file.

Below is a sample soainfra_Storage.xml file:

<?xml version="1.0" encoding="UTF-8"?>
<!-- SOAINFRA -->
<TablespaceAttributes NAME="SOAINFRA" >
<DatafilesList>
<DatafileAttributes ID="%DATAFILE_LOCATION%/soainfra.dbf">
<Size UNIT="MB">
200
</Size>
<Reuse>
True
</Reuse>
<AutoExtend>
True
</AutoExtend>
<Increment UNIT="MB">
50
</Increment>
<Maxsize UNIT="GB">
2
</Maxsize>
</DatafileAttributes>
</DatafilesList>
</TablespaceAttributes>

<!-- End 0f SOAINFRA -->

3.3 RCU Script Writing Guidelines

Below are some common RCU script writing guidelines:

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 using the parameters passed in 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 creating 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.

- SCHEMA_VERSION_REGISTRY should be updated before and after loading schema. This can be done using JavaAction as shown in Section 3.1.5, "Java Code Using JavaAction" or with in the component scripts using SCHEMA_VERSION PL/SQL package.

- Block comments that contain line comments (/* -- comment */) are not supported.

3.3.1 Guidelines for RCU JDBC Engine Compliant SQL*Plus Scripts

Below are some guidelines for writing RCU JDBC Engine SQL*Plus scripts:

- All statements must be terminated with appropriate terminating chars. CREATE PACKAGE, TYPE needs to be terminated with “;” with “/” on the next line. All other statements (Create TABLE, VIEW, etc.) need to be terminated by “;” or “/” (only one of them, not both).

- EXECUTE calls should be replaced with “BEGIN/END blocks”.

- DEFINE statements should be in one line, no comments in the same line and no “;” at the end.

- SET, SHOW, SPOOL, WHENEVER, BREAK, EXIT statements are simply 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 “ValidIf” tag to specify the condition.

3.3.2 Guidelines for Pure JDBC Scripts

Below are some guidelines for writing Pure JDBC scripts for RCU:

- Should not contain any SQL*Plus directives (like SET, WHENEVER, etc.).

- 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 preceding 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().

3.3.3 Guidelines for SQL*Plus Scripts

Below are some 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.

3.3.4 Guidelines for SQL Server-Based Scripts

Below are some 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">
<ValidIf DBTYPE="ORACLE" />
<PrereqIdentifier>%DEFAULT_TABLESPACE%</PrereqIdentifier>
<PrereqValue>50</PrereqValue>
</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 preceding the “go” statement will be executed as a single statement over JDBC.

- The JDBC connection is created in the auto-commit “on” mode.

- Currently, begin transaction and commit transaction statements are not supported.

- Variables passed to scripts via the XML file will be passed as follows:

Script.sql –v v1=value1 v2=value2

This is only for scripts called using the XML files. If a script calls another script, you can use any other variable name.

4 Running Repository Creation Utility from the Command Line

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

This chapter contains the following topics:

- Section 4.1, "Command Line Syntax and Parameters"

- Section 4.2, "Using the -silent Command"

- Section 4.3, "Using the -interactive Command"

- Section 4.4, "Creating a Repository from the Command Line"

- Section 4.5, "Dropping a Repository from the Command Line"

- Section 4.6, "RCU Environment Variables"

4.1 Command Line Syntax and Parameters

The syntax for the RCU command line interface is:

rcu [-silent | -interactive] [-createRepository | -dropRepository] {parameters}

Table 4-1 lists the CLI commands and their descriptions.

Table 4-1 RCU CLI Commands and Description

Command

Description

-silent

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

For more information, see Section 4.2, "Using the -silent Command".

-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 pre-populate certain screens with information as specified from the command line. You can pre-populate the Create Repository and Database Connection Details.

For more information, see Section 4.3, "Using the -interactive Command".

-createRepository

Run RCU with either -silent or -interactive to create a repository.

For more information, see Section 4.4, "Creating a Repository from the Command Line".

-dropRepository

Run RCU with either -silent or -interactive to drop a repository.

For more information, see Section 4.5, "Dropping a Repository from the Command Line".

Table 4-2 lists the various parameters and their descriptions.

Table 4-2 RCU CLI Parameters and Descriptions

Parameter

Required?

Valid for Create or Drop?

Description

-compInfoXMLLocation

No

Both

Full path to the location of the ComponentInfo.xml file. The default location is RCU_HOME/rcu/config (on UNIX operating systems) or RCU_HOME\rcu\config (on Windows operating systems).

-storageXMLLocation

No

Both

Full path to the location of the StorageInfo.xml file. The default location is RCU_HOME/rcu/config (on UNIX operating systems) or RCU_HOME\rcu\config (on Windows operating systems).

-databaseType

No

Both

Type of database to which you are connecting. Valid options are ORACLE, IBMDB2, SQLSERVER, EBR, or MYSQL.

-connectString

Yes

Both

Credentials for connecting to your database.

- Oracle or EBR-enabled databases: use the format host:port:sid.

- Microsoft SQL Server, IBM DB2, or MySQL databases: use the format server name or host:port:database name.

-edition

No

Both

Edition name. This is only valid if you specify databaseType=EBR.

-dbUser

Yes

Both

Database user name (for example, the default user name on Oracle databases is SYS).

-dbRole

No

Both

Database user role (for example, SYSDBA for the SYS user on Oracle databases).

-unicodeSupport

No

Both

Whether or not your database creates schemas that support encodings. Valid values are Yes or No. The default value is Yes. This parameter is valid for the SQLSERVER database type only.

-skipCleanupOnFailure

No

Create

Whether or not you want to skip the schema cleanup if schema creation fails. Valid values are Yes or No. The default is No.

-useSamePasswordForAllSchemaUsers

No

Create

Whether or not you want to use the same password for all schemas. Valid values are true or false. The default is false.

-selectDependentsForComponents

No

Create

Whether or not you want to have RCU automatically select dependent schemas for your components. Valid values are true or false. The default is false.

-variables

No

Both

Comma separated variables in the format variablename=value. See Section 4.6, "RCU Environment Variables" for a list of RCU environment variables.

-schemaPrefix

No

Both

Prefix for your schemas. For more information about schema prefixes, refer to Section 1.2.1, "Creating Custom Schemas and Tablespaces" and Section A.5, "Select Components (for Create Operation)".

-component

Yes

Both

ID of the component(s) 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, refer to Appendix B, "Repository Creation Utility Schemas, IDs, and Tablespaces". Multiple components are sometimes necessary because of dependencies; for example, you cannot create the Oracle Portal (PORTAL) schema if the Portlet Producers (PORTLET) schemas does not already exist. In this case, you must specify both schemas:

-component PORTAL -component PORTLET

For more information about schemas and their dependencies, see Appendix B, "Repository Creation Utility Schemas, IDs, and Tablespaces".

-tablespace

Yes

Create

Tablespace name of the component. This tablespace must exist in the database if you are using this option.

-tempTablespace

Yes

Create

TEMP tablespace name of the component. This tablespace must exist in the database if you are using this option.

4.2 Using the -silent Command

Specify -silent if you want to run RCU with minimal interaction once you have entered the commend. 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 will prompt you for the database and component schema passwords from the command line. If you specify multiple components, you will be prompted for the passwords in the order in which the components are specified.

If you want to avoid all interaction from the command line, you can create a text file containing 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

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.

If you are creating the ODI Repository, RCU will present you with an additional screen; the Custom Variables. The values required for this screen can also be specified in a password file as follows:

database_user_password
master_repository_password
master_repository_ID
supervisor_password
work_repository_type
work_repository_ID
work_repository_name
work_repository_password

Below is an example:

welcome1
welcome1
001
welcome1
D
001
WORKREP
welcome1

4.3 Using the -interactive Command

Specify -interactive to run the RCU graphical interface. This is the default 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:

rcu

The Database Connection Details page contains blank fields, as shown below:

But if you run RCU with a few parameters from the command line:

rcu -interactive -createRepository -connectString example_db.example.com:1521:example_sid -dbUser SYS -component MDS

The Database Connection Details page contains the information supplied from the command line:

4.4 Creating a Repository from the Command Line

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

rcu [-silent | -interactive] -createRepository
[-compInfoXMLLocation omponentInfo.xml_file_location]
[-storageXMLLocation Storage.xml_file_location]
[-databaseType [ORACLE|SQLSERVER|IBMDB2|EBR|MYSQL]]
-connectString database_connect_string
[-edition edition_name]
-dbUser database_username
[-dbRole database_user_role]
[-unicodeSupport [Yes|No]]
[-skipCleanupOnFailure [Yes|No]
[-useSamePasswordForAllSchemaUsers [true|false]]
[-selectDependentsForComponents [true|false]]
[-variables variablename=value]
[-schemaPrefix schema_prefix]
-component component_ID
-tablespace component_tablespace_name
-tempTablespace component_temp_tablespace_name
]

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

When specifying the -component, you must use the correct component IDs, which are listed in Appendix B, "Repository Creation Utility Schemas, IDs, and Tablespaces".

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

Below is a sample command to create the SOA Infrastructure schemas on a UNIX operating system:

./rcu -silent -createRepository -databaseType ORACLE -connectString examplehost.exampledomain.com:1521:exampleSID -dbUser sys -dbRole sysdba -schemaPrefix TEST -component SOAINFRA -component MDS -component ORASDPM

4.5 Dropping a Repository from the Command Line

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|SQLSERVER|DB2|EBR|MYSQL]]
-connectString database_connect_string
[-edition edition_name]
-dbUser database_username
[-dbRole database_user_role]
[-unicodeSupport [Yes|No]]
[-variables variablename=value]
[-schemaPrefix schema prefix]
-component component_ID

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

You must also be aware of schema dependencies when dropping schemas (see Appendix B, "Repository Creation Utility Schemas, IDs, and Tablespaces"). For example, several schemas require the MDS schema to be present; if you choose to drop the MDS schema, then all the schemas that require the MDS schema will stop working.

Below is a sample command to drop the WebCenter Spaces schemas on a UNIX operating system:

./rcu -silent -dropRepository -databaseType ORACLE -connectString host1.oracle.com:1521:orcl -dbUser sys -dbRole sysdba -schemaPrefix TEST -component WEBCENTER

4.6 RCU Environment Variables

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

Table 4-3 RCU Environment Variables

Variable

Default

Description

RCU_LOG_LOCATION

RCU_HOME/rcu/log (UNIX operating systems)

RCU_HOME\rcu\log (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 or false.

RCU_LOG_NAME

rcu.log

Name of the RCU log file.

RCU_LOG_LEVEL

ERROR

Determines the RCU log level.

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

A Repository Creation Utility Screens

This appendix contains screenshots and descriptions for all of the Repository Creation Utility screens:

- Welcome

- Create Repository

- Drop Repository

- Database Connection Details

- Select Components (for Create Operation)

- Select Components (for Drop Operation)

- Schema Passwords

- Custom Variables

- Map Tablespaces

- Summary (for Create Operation)

- Summary (for Drop Operation)

- Completion Summary (for Create Operation)

- Completion Summary (for Drop Operation)

A.1 Welcome

This is the first screen that appears when RCU is started. Note the navigation pane on the left that summarizes the tasks that RCU will help you complete. Each item in the navigation pane represents a specific screen that will prompt you for information required to create or drop your schemas.

Click Skip This Page Next Time if you do not want to see the Welcome screen the next time you start RCU.

A.2 Create Repository

Use this screen to select the action you want to perform:

- Select Create to create component schemas in the database.

- Select Drop to remove component schemas from the database.

A.3 Drop Repository

Use this screen to select the action you want to perform:

- Select Create to create component schemas in the database.

- Select Drop to remove component schemas from the database.

A.4 Database Connection Details

Use this screen to specify the connection credentials to the database in which you will be creating or dropping your schemas. Select one of the following depending on your database:

- Specifying Connection Credentials for Oracle Databases and Oracle Databases with Edition-Based Redefinition

- Specifying Connection Credentials for MySQL Databases

- Specifying Connection Credentials for Microsoft SQL Server Databases

- Specifying Connection Credentials for IBM DB2 Databases

Click Next when you are finished entering the connection credentials for your database. The following screen appears, indicating the progress of the installer establishing the connection with the specified database:

If an error occurs while the connection is being established, the error message(s) 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 11gR1 document, which is available on the Oracle Fusion Middleware Supported System Configurations page.

A.4.1 Specifying Connection Credentials for Oracle Databases and Oracle Databases with Edition-Based Redefinition

For Oracle databases and Oracle databases with edition-based redefinition, specify the following connection credentials:

Table A-1 Oracle Database Connection Credentials

Field

Description

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.

Port

Enter the port number for your database. The default port number for Oracle databases is 1521.

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 database's initialization parameter file. 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

Username

Enter the user name for your database. The default user name is SYS.

Password

Enter the password for your database user.

Role

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

- Normal

- SYSDBA

All schemas installed on an Oracle database require the SYSDBA role. If you are creating schemas for Oracle Internet Directory (OID) or Oracle Identity Manager (OIM), you must use the user SYS and the SYSDBA role. See "Required Privileges for Oracle Databases" in the Oracle Fusion Middleware System Requirements and Specifications document for more information.

A.4.2 Specifying Connection Credentials for MySQL Databases

For MySQL databases, specify the following connection credentials:

Table A-2 Oracle MySQL Database Connection Credentials

Field

Description

Host 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 DBA or SYSDBA privileges.

Password

Enter the password for your database user.

A.4.3 Specifying Connection Credentials for Microsoft SQL Server Databases

For Microsoft SQL Server databases, specify the following connection credentials:

Table A-3 Microsoft SQL Server Database Connection Credentials

Field

Description

Unicode Support

Select Yes or No from the drop-down list.

NOTE: Oracle SOA Infrastructure schemas are created with Unicode support (database tables created with NVARCHAR) only, regardless of the option selected in this field.

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

Enter the user name for your database. The user must have SYSDBA or DBA privileges.

Password

Enter the password for your database user.

A.4.4 Specifying Connection Credentials for IBM DB2 Databases

For IBM DB2 databases, specify the following connection credentials:

Table A-4 IBM DB2 Database Connection Credentials

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.

A.5 Select Components (for Create Operation)

Below is the Select Components screen if you selected Create on the Create Repository screen.

Note:

RCU supports additional products not included with Oracle Fusion Middleware. The schemas for these products may appear in RCU but should not be selected if you are only configuring an Oracle Fusion Middleware environment.

Oracle Fusion Middleware schemas are listed in Appendix B, "Repository Creation Utility Schemas, IDs, and Tablespaces".

The following topics are covered in this section:

- Section A.5.1, "Creating Database Users for IBM DB2 Databases"

- Section A.5.2, "Creating Prefixes"

- Section A.5.3, "Selecting Components and Dependencies"

- Section A.5.4, "Specifying Custom Schema Names"

- Section A.5.5, "Checking Schema Prerequisites"

Note:

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

A.5.1 Creating Database Users for IBM DB2 Databases

IBM DB2 authenticates its database users using equivalent operating system users. Therefore, prior to running RCU, one operating system user must be created for each schema. The operating system user name must match the schema owner name and must contain only lowercase letters; no all-uppercase or mixed-case names are allowed. For example, if you create a schema named DEV_ODI using RCU, then the operating system user must be named dev_odi (all lowercase letters).

A.5.2 Creating Prefixes

Prefixes are used to create logical groupings of schemas in a database. For example, if you want to create two versions of the MDS schema in the database, you can use different prefixes to uniquely identify each one (for example, TEST_MDS and PROD_MDS). Note that the prefix name and schema name are separated by an underscore (_) character.

Note:

The Oracle Internet Directory (ODS) component cannot be prepended with a custom prefix; there can only be one repository for this component per database.

If you want to create a new prefix for your schemas, select Create a New Prefix and specify a new prefix name in the field. 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.

Note:

For IBM DB2 databases, prefixes are limited to four characters in length (not including the underscore character).

The default new prefix is DEV. If DEV already exists as a prefix, then DEV1 is used; if DEV1 exists, then DEV2 is the default, and so on.

Use existing prefixes to add additional components to an existing repository in the database. To use an existing prefix, select Select an Existing Prefix and choose a prefix from the drop-down list.

A.5.3 Selecting Components and Dependencies

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 SOA and BPM Infrastructure, then all schemas in this category are selected along with the Metadata Services schema. The Metadata Services schema is required by each component in SOA and BPM Infrastructure.

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 (+).

A.5.4 Specifying Custom Schema Names

Click on the name of any schema in the "Schema Owner" column to change the name of the schema. Schema names can only contain alphanumeric characters (0-9, a-z, or A-Z) and are case-sensitive.

Note:

The Oracle Internet Directory (ODS) component cannot be prepended with a custom prefix; there can only be one repository for this component per database.

A.5.5 Checking Schema Prerequisites

Click Next when you are finished specifying your prefix, schema names, and selecting components. The following screen appears, indicating the progress of component prerequisite checking before the schemas are created.

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.

A.6 Select Components (for Drop Operation)

Below is the Select Components screen if you selected Drop on the Create Repository screen.

First, select the prefix associated with the schema(s) you want to drop.

Then, select the component(s) whose schemas you want to drop.

Click Next when you are finished. The following screen appears:

Click OK to continue. The following screen 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.

A.7 Schema Passwords

Below is the Schema Passwords screen.

There are three ways to specify schema passwords on this screen; they are described in the following table:

Table A-5 Options for Specifying Schema Passwords

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 will be visible in the table. For each schema, you must enter each schema's password in the 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 will be visible in the table. For each schema and auxiliary schema, you must enter the password in the 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 will need this information during the configuration phase of Fusion Middleware product installation. Oracle recommends that you write these values down.

A.8 Custom Variables

This page allows one or more components to specify additional configuration information required by the components during runtime.

This screen only appears if you selected a component on the Select Components (for Create Operation) that supports custom variables:

- Specifying Custom Variables for Master and Work Repository (ODI)

- Specifying Custom Variables for Oracle WebCenter Portal's Activity Graph and Analytics

A.8.1 Specifying Custom Variables for Master and Work Repository (ODI)

Specify the following for the Master and Work Repository Custom Variables:

Table A-6 Master and Work Repository Custom Variables

Variable

Description

Master Repository ID

A specific ID for the new Master Repository. Master Repository ID values must be between 0 and 999. Default value is 001.

Supervisor PAssword

Password of the supervisor user. You must confirm this password on the following line.

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.

Work Repository ID

A specific ID for the new Work Repository. Default value is 001.

Work Repository Name

A unique name for the Work Repository (for example: DEVWORKREP1).

Work Repository Password

(Optional) - Provide a password for the Work Repository. If you provide a password, you must confirm the password on the following line.

A.8.2 Specifying Custom Variables for Oracle WebCenter Portal's Activity Graph and Analytics

Specify Y if you want to install Activity Graph and Analytics with database partitioning enabled, or N if you do not want to enable database partitioning.

A.9 Map Tablespaces

This screen only appears if you selected the Create option on the Create Repository. The following topics are covered:

- Section A.9.1, "Default Tablespace Mappings"

- Section A.9.2, "Changing Default and Temporary Tablespaces"

- Section A.9.3, "Viewing and Changing Additional Tablespaces"

- Section A.9.4, "Managing Tablespaces and Datafiles"

Click Next when you are finished with your tablespace information. The following screen appears, asking you to confirm the creation of tablespaces for any new schemas.

Note:

RCU only creates tablespaces for those components associated with RCU.

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

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

A.9.1 Default Tablespace Mappings

The default tablespace mapping for each component are shown in Appendix B, "Repository Creation Utility Schemas, IDs, and Tablespaces".

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.

Note:

OID tablespace names cannot be user specified.

A.9.2 Changing Default and Temporary Tablespaces

To change the default tablespace for a component, select the tablespace name in the "Default Tablespace" column, then select the tablespace name you want to use from the drop-down list. You can have your components use as many or as few tablespaces as desired to suit your configuration.

To change the temporary tablespace for a component, select the tablespace name in the "Temp Tablespace" column, then select the tablespace name you want to use from the drop-down list.

A.9.3 Viewing and Changing Additional Tablespaces

Some components have additional tablespaces associated with their schemas. If this is the case, the Additional Tablespaces button will appear on this screen. If none of the selected components have additional tablespaces, then this button will not appear.

To view additional tablespaces associated with the selected components, click the Additional Tablespaces button. You will see a screen similar to the following:

Only those components with additional tablespaces as defined in the configuration files will appear on this screen.

To change the tablespace you want to use for a component, click in the "Tablespace Name" column and select the tablespace you want to use from the drop-down list.

Click OK when you are finished.

A.9.4 Managing Tablespaces and Datafiles

To manage your tablespaces and datafiles, click the Manage Tablespaces button. You will see a screen similar to the following:

The following topics are covered in this section:

- Section A.9.4.1, "Adding, Modifying, and Removing Tablespaces"

- Section A.9.4.2, "Adding, Modifying, and Removing Datafiles"

A.9.4.1 Adding, Modifying, and Removing Tablespaces

Only tablespaces that will be 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 will not be 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:

Table A-7 Modifying a Tablespace

Field

Description

Name

Edit the tablespace name 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 will not get created.

A.9.4.2 Adding, Modifying, and Removing Datafiles

In the Datafiles section, specify the datafiles that make up the selected tablespace. Select one of the following for more information:

- Section A.9.4.2.1, "Adding a Datafile"

- Section A.9.4.2.2, "Modifying a Datafile"

- Section A.9.4.2.3, "Deleting a Datafile"

A.9.4.2.1 Adding a Datafile

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

The Add Datafile screen appears:

Provide the information described in the following table:

Table A-8 Adding a Datafile

Field

Description

File Name

Specify the name of the datafile.

NOTE: Datafile names must be less than 30 characters in length, and 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) if you want 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.

A.9.4.2.2 Modifying a Datafile

To modify or edit a datafile, select the icon next to the datafile name you want to edit, then click the icon with the pencil:

The Edit Datafile screen appears:

Provide the information described in the following table:

Table A-9 Modifying a Datafile

Field

Description

File Name

Specify the name of the datafile.

NOTE: Datafile names must be less than 30 characters in length, and names with a dash or hyphen (-) character are not permitted.

File Directory

Specify the location where this datafile resides.

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) if you want 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.

A.9.4.2.3 Deleting a Datafile

To delete a datafile, select the icon next to the datafile name you want to delete, then click the icon with the "X":

A.10 Summary (for Create Operation)

Below is the Summary screen if you selected Create on the Create Repository screen.

Review the information on this screen, and click Create to begin schema creation. The operations summarized on this page will be performed when you click Create.

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

Click Stop if you want to stop creating the schemas.

A.11 Summary (for Drop Operation)

Below is the Summary screen if you selected Drop on the Create Repository screen.

Review the information on this screen, and click Drop to begin the operations summarized on this page.

While the schema(s) are being dropped, you will see the following progress screen:

Click Stop if you want to cancel the operation.

A.12 Completion Summary (for Create Operation)

Below is the Completion Summary screen if you selected Create on the Create Repository screen.

Note the log file names for each component that are visible in the "Logfile" column.

The main RCU log and component log files are written to the following directory on UNIX operating systems:

RCU_HOME/rcu/log/logdir.date_timestamp

On Windows operating systems:

RCU_HOME\rcu\log\logdir.date_timestamp

If there were any problems encountered during schema creation, you can troubleshoot the issue using the log files. For more information, see Appendix C, "Troubleshooting Repository Creation Utility".

If errors are encountered during a Create operation, or if a Create operation fails for any component, the Cleanup for failed components checkbox appears on this page and is selected by default. If selected, RCU will perform cleanup operations for the component that failed during the Create operation. If you choose not to select this checkbox, you can cleanup the failed component at a later time by performing a Drop operation for the failed component(s).

Review the information on this screen, then click Close to dismiss this screen.

A.13 Completion Summary (for Drop Operation)

Below is the Completion Summary screen if you selected Drop on the Create Repository screen.

Note the log file names for each component that are visible in the "Logfile" column.

The main RCU log and component log files are written to the following directory on UNIX operating systems:

RCU_HOME/rcu/log/logdir.date_timestamp

On Windows operating systems:

RCU_HOME\rcu\log\logdir.date_timestamp

If there were any problems encountered during schema creation, you can troubleshoot the issue using the log files. For more information, see Appendix C, "Troubleshooting Repository Creation Utility".

Review the information on this screen, then click Close to dismiss this screen.

B Repository Creation Utility Schemas, IDs, and Tablespaces

This appendix lists the available schemas that can be created using RCU, and also their component IDs and dependencies.

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 will see in RCU and is also the name you must provide in the Fusion Middleware Configuration Wizard on the Configure JDBC Component Schema screen.

The "Component ID" is the value you must specify with the -component parameter when you are creating or dropping schemas using the command line.

Note:

Not all schemas are supported on all database types. For more information, refer to "Repository Creation Utility (RCU) 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

Audit Services

IAU

IAU

IAS_IAU

IAS_TEMP

None

Audit Services for OES

IAUOES

IAUOES

IAS_IAUOES

IAS_TEMP

None

Enterprise Scheduler Service

ORAESS

ORAESS

ORAESS

IAS_TEMP

None

Oracle Platform Security Services

OPSS

OPSS

IAS_OPSS

IAS_TEMP

Metadata Services (MDS)

Identity Management Schemas

Oracle Internet Directory

ODS

OID

OLTS_DEFAULT

IAS_TEMP

None

Oracle Identity Federation

OIF

OIF

IAS_OIF

IAS_TEMP

None

Oracle Identity Manager

OIM

OIM

OIM

OIM_TEMP

Metadata Services (MDS)

SOA Infrastructure (SOAINFRA)

User Messaging Service (ORASDPM)

Oracle Access Manager

OAM

OAM

OAM

OAM_TEMP

Audit Services (IAU)

Oracle Adaptive Access Manager

OAAM

OAAM

BRSADATA

BRSATEMP

Metadata Services (MDS)

Oracle Adaptive Access Manager (Partition Support)

OAAM_PARTN

OAAM_PARTN

TBS_OAAM_DATA

TBS_OAAM_TEMP

Metadata Services (MDS)

Oracle Entitlements Server

APM

APM

APM

APM_TEMP

Metadata Services (MDS)

WebCenter Content Schemas

Oracle Information Rights Management

ORAIRM

IRM

ORAIRM

ORAIRM_TEMP

None

Oracle WebCenter Content Server - Complete

OCS

CONTENTSERVER11

OCS

OCS_TEMP

None

Oracle WebCenter Content Server - Search Only

OCSSEARCH

CONTENTSERVER11SEARCH

OCSSEARCH

OCSSEARCH_TEMP

None

Oracle WebCenter Content: Records

URMSERVER

URM

URMSERVER

URMSERVER_TEMP

None

Oracle WebCenter Content: Imaging

IPM

IPM

IPM

IPM_TEMP

None

Oracle Data Integrator Schemas

Master and Work Repository

ODI_REPO

ODI

ODI_USER

ODI_TEMP

None

Oracle Business Intelligence Schemas

Business Intelligence Platform

BIPLATFORM

BIPLATFORM

BIPLATFORM

BIPLATFORM_TEMP

Metadata Services (MDS)

WebLogic Communication Services Schemas

Presence

ORASDPXDMS

ORASDPXDMS

IAS_ORASDPXDMS

IAS_TEMP

Metadata Services (MDS)

SIP Infrastructure Subscriber Data Service (ORASDPSDS)

SIP Infrastructure Location Service (ORASDPLS)

User Messaging Service (ORASDPM)

SIP Infrastructure Subscriber Data Service

ORASDPSDS

ORASDPSDS

IAS_ORASDPSDS

IAS_TEMP

Metadata Services (MDS)

SIP Infrastructure Location Service (ORASDPLS)

SIP Infrastructure Location Service

ORASDPLS

ORASDPLS

IAS_ORASDPLS

IAS_TEMP

Metadata Services (MDS)

SIP Infrastructure Subscriber Data Service (ORASDPSDS)

SOA and BPM Infrastructure Schemas

SOA Infrastructure

SOAINFRA

SOAINFRA

SOAINFRA

IAS_TEMP

Metadata Services (MDS)

User Messaging Service (ORASDPM)

Business Activity Monitoring

ORABAM

BAM

ORABAM

IAS_TEMP

Metadata Services (MDS)

User Messaging Service (ORASDPM)

User Messaging

ORASDPM

ORASDPM

IAS_ORASDPM

IAS_TEMP

Metadata Services (MDS)

WebCenter Portal Schemas

Portlet Producers

PORTLET

PORTLET

IAS_PORTLET

IAS_TEMP

None

Spaces and Services

WEBCENTER

WEBCENTER

IAS_WEBCENTER

IAS_TEMP

Metadata Services (MDS)

Discussions

DISCUSSIONS

DISCUSSIONS

IAS_DISCUSS

IAS_TEMP

None

Activity Graph and Analytics

ACTIVITIES

ACTIVITIES

IAS_ACTIVITY

IAS_TEMP

None

Portal and Business Intelligence Schemas

Discoverer

DISCOVERER

DISCOVERER

DISCO_PTM5_META

IAS_TEMP

None

Portal

PORTAL

PORTAL

PORTAL

IAS_TEMP

Portlet Producers (PORTLET)

Enterprise Performance Management Schemas

Registry

EPM

EPMREGISTRY

EPM

IAS_TEMP

None

In addition to the component IDs listed in the table, there is also a SAMPLE schema that can be used for testing purposes.

C Troubleshooting Repository Creation Utility

This appendix describes solutions to common problems that you might encounter when running Repository Creation Utility (RCU). It contains the following sections:

- Section C.1, "General Troubleshooting Tips"

- Section C.2, "RCU Log Files"

- Section C.3, "Finding Schemas in the Database"

- Section C.4, "Need More Help?"

C.1 General Troubleshooting Tips

If you encounter an error during installation:

- Read the Oracle Fusion Middleware Release Notes for the latest updates. The most current version of the release notes is available on Oracle Technology Network in the Oracle Fusion Middleware Documentation page.

Select the documentation library for your specific product release to view the release notes.

- Verify that your computer meets the requirements specified in the Oracle Fusion Middleware System Requirements and Specifications document.
Select the document that is applicable for your release.

- Verify that your environment meets the certification requirements as specified in the System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 document, which can be found 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 hand 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 Section C.2, "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 be forced to restart RCU.

3. Continue or restart RCU to complete your desired operation.

C.2 RCU Log Files

The main RCU log file is written to the RCU_HOME/rcu/log/logdir.date_timestamp/rcu.log (on UNIX operating systems) or RCU_HOME\rcu\log\logdir.date_timestamp\rcu.log (on Windows operating systems) file. For example, on a UNIX operating system:

RCU_HOME/rcu/log/logdir.2010-01-02_03-00/rcu.log

In addition to this general log file, each component writes a log file of its own. All component log files are also written to the RCU_HOME/rcu/log/logdir.date_timestamp (on UNIX operating systems) or RCU_HOME\rcu\log\logdir.date_timestamp (on Windows operating systems) directory.

Table C-1 lists the component log file names in alphabetical order by log file name.

Table C-1 RCU Component Log File Names

Component

Log File Name

Activity Graph and Analytics

activities.log

Authorization Policy Manager

apm.log

Business Activity Monitoring

bam.log

Business Intelligence Platform

biplatform.log

Oracle WebCenter Content Server 11g - Complete

contentserver11.log

Oracle WebCenter Content Server 11g - Search

contentserver11search.log

Oracle Content Server 10g

contentserver.log

Discoverer

discoverer.log

Oracle Discussions Crawler

discussions_crawler.log

Oracle Discussions

discussions.log

Registry

epmregistry.log

Audit Services

iau.log

Audit Services for OES

iauoes.log

Oracle Imaging and Process Management

ipm.log

Oracle Information Rights Management

irm.log

Metadata Services

mds.log

Oracle Access Manager

oam.log

Oracle Adaptive Access Manager

oaam.log

Oracle Adaptive Access Manager (Partition Support)

oaam_partn.log

Master and Work Repository

odi.log

Oracle Internet Directory

oid.log

Oracle Identity Federation

oif.log

Oracle Identity Manager

oim.log

Enterprise Scheduler Service

oraess.log

SIP Infrastructure Location Service

orasdpls.log

User Messaging Service

orasdpm.log

SIP Infrastructure Subscriber Data Service

orasdpsds.log

Presence

orasdpxdms.log

Portal

portal.log

Portlet Producers

portlet.log

SOA Infrastructure

soainfra.log

Social Schema

socialnetwork.log

Social View Schema

socialnetwork_views.log

Social CEF Schema

socialnetwork_cef.log

Oracle WebCenter Content: Records

urm.log

Spaces and Services

webcenter.log

C.3 Finding Schemas in the Database

In situations where you need to find which schemas are already installed in your database, there are two methods for accomplishing this.

You can run RCU (Section 2.4, "Starting RCU") and select Drop on the Create Repository screen. After specifying your database credentials, you will be able to see the schemas available for your drop operation, which are the schemas installed on the database.

You can also connect to and query the database using the following SQL command:

SELECT OWNER, VERSION, STATUS FROM SCHEMA_VERSION_REGISTRY;

C.4 Need More Help?

If this appendix does not solve the problem you encountered, try looking for a solution on My Oracle Support (formerly OracleMetaLink):

https://support.oracle.com/

If you are unable to find a solution for your problem, open a service request.

Index
A  C  D  E  I  J  L  M  O  P  R  S  T

A

access-bridge.jar file, 1.3.1

accessibility software, Java Access Bridge, A

adding datafiles, A.9.4.2

adding tablespaces, A.9.4.1

C

changing default and temporary tablespaces, A.9.2

command line options, 4.1

complete list of RCU schemas, B

component dependencies, 4.4

component ID, 4.1

ComponentInfo.dtd file, 3.2.1.1

ComponentInfo.xml file, 3.2.3

creating a repository from the command line, 4.4

creating custom schemas and tablespaces, 1.2.1

creating schemas, 2.5

custom schema names, A.5.4

D

datafiles

adding, A.9.4.2

deleting, A.9.4.2

modifying, A.9.4.2

default tablespace mappings, A.9.1 deleting datafiles, A.9.4.2 deleting tablespaces, A.9.4.1 demo schema, 2.7 distributing schemas, 1.2.1.1 dropping a repository from the command line, 4.5 dropping schemas, 2.6 dropping shared tablespaces, 2.6.1

E

environment variables for RCU, 4.6

error messages, 3.2.3

extending RCU, 3

I

instdemo.sql script, 2.7

integrating component scripts, 3.1

integrating components using declarative XML, 1.2.5

J

jaccess_1.4.jar file, 1.3.1

Java Access Bridge, 1.3

JAWS screen reader, 1.3

L

log files, A.12

log files for RCU, C.2

M

mapping tablespaces, A.9

modifying datafiles, A.9.4.2

modifying tablepsaces, A.9.4.1

My Oracle Support, C.4

O

Oracle Portal

demo schema, 2.7

Oracle Technology Network, C.1 Oracle WSM Policy Manager, 2.2.3

creating schemas for, 2.2.3

Oracle WSM-PM Extension, 2.2.3

creating schemas for, 2.2.3

ORACLE_OEM_CLASSPATH variable, 1.3.2

P

password handling in RCU, 4.2

prefixes, A.5.2

R

RCU error messages, 3.2.3

RCU integration options

Java code for Java components, 3.1.5

JDBC engine compliant SLQ*Plus scripts, 3.1.1

pure JDBC scripts for non-Oracle databases, 3.1.2

SQL*Plus scripts for legacy components, 3.1.3

RCU JDBCEngine Tool, 3.1.1 RCU log files, A.12, C.2 RCU screens, A RCUCommon.dtd file, 3.2.1.3 removing tablespaces, A.9.4.1 Repository Creation Utility

creating and loading schemas, 1

creating custom schemas and tablespaces, 1.2.1

creating schemas, 2.5

dropping schemas, 2.6

dropping shared tablespaces, 2.6.1

environment variables, 4.6

extending, 3

integrating components, 1.2.5

integration options, 3.1

key features, 1.2

overview, 1.2

password handling, 4.2

required schemas for Fusion Middleware products, 2.2

screens, A

starting, 2.4

starting in silent mode (no GUI), 1.2.3.3

tablespace mappings, A.9.1

troubleshooting, C

using in silent mode, 4

using the CLI, 4

using with Java Access Bridge, 1.3

RepositoryConfig.dtd file, 3.2.1.2 required schemas for Fusion Middleware products, 2.2 root access, Preface

S

SAMPLE schema, B

schema dependencies, 4.4

schema ID, 4.1

schema names

customizing, A.5.4

schema passwords, A.7 schema prefix, 1.2.1.2, 2.5 schema_version_segistry

mapping schemas and prefixes, 1.2.1.2

schemas, 1

complete list, B

required for Application Developer, 2.2.3

required for Identity Management, 2.2.4

required for Oracle Business Intelligence, 2.2.6

required for Oracle Data Integrator, 2.2.5

required for Oracle ECM (IBM DB2 databases), 2.2.8

required for Oracle ECM (Oracle and SQL Server databases), 2.2.8

required for Oracle Portal and Oracle Discoverer, 2.2.7

required for Oracle SOA Suite and Oracle BAM (IBM DB2 databases), 2.2.1

required for Oracle SOA Suite and Oracle BAM (Oracle and SQL Server databases), 2.2.1

required for WebCenter (IBM DB2 databases), 2.2.2

required for WebCenter (Oracle and SQL Server databases), 2.2.2

setting soft-prerequisite, 3.2.4 soft-prerequisite, 3.2.4 specifying schema passwords, A.7 SQL*Plus Scripts, 3.1 starting RCU, 2.4 starting RCU in silent mode (no GUI), 1.2.3.3 Storage.dtd file, 3.2.1.4 Storage.xml file, 3.2.5 system requirements, 1.1.3

T

tablespaces

adding, A.9.4.1

changing, A.9.2

mapping, A.9

modifying, A.9.4.1

removing, A.9.4.1

tablespaces and datafiles, A.9.4 troubleshooting, B, C troubleshooting RCU, C

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2014, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

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

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

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.

Warranty Disclaimer

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.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

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.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on 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. 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.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.