What's New in This Guide

The following topics introduce the new and changed features of the Repository Creation Utility and other significant changes that are described in this guide, and provide pointers to additional information. This document is the new edition of the formerly titled Oracle Fusion Middleware Repository Creation Utility User's Guide.

New and Changed Features for Release 12c (12.2.1)

Repository Creation Utility 12c (12.2.1) includes the following new and changed schema creation features.

  • If Transparent Data Encryption (TDE) is enabled in an Oracle database, RCU provides an option on the command line and in the graphical interface to create encrypted tablespaces.

    For more information, see Encrypting Tablespaces.

  • In 12c (12.1.3), RCU used ORACLE_HOME/oracle_common/rcu/log/logdir.date_timestamp/rcu.log as the default log location. In 12c (12.2.1), log files are now written (by default) to the RCUdate_timestamp_random_number\logs directory inside the temporary directory on your system.

    For more information, see RCU Log Files.

  • RCU operations can be performed using a response file, which allows you to pass all valid RCU command-line parameters to RCU via a text file.

    For more information, see Using Response Files.

  • A wallet can be used in silent mode to store and provide password credentials to RCU rather than directly entering passwords on the command line.

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

  • A silent RCU operation was introduced to generate a list of component IDs for a given Oracle home.

    For more information, see Generating a List of Components in an Oracle Home from the Command Line.

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

For 12c (12.2.1), this guide has been updated in several ways. Following are the sections that have been added or changed:

  • Added a section to describe how to create encrypted tablespaces with RCU if TDE (Transparent Data Encryption) is enabled in the database (Oracle or Oracle EBR). See Encrypting Tablespaces.

  • Added a section to describe how to generate and use a response file to perform a RCU operation. See Using Response Files.

  • Added a section to describe how to generate a list of component IDs for a given Oracle home from the command line. See Generating a List of Components in an Oracle Home from the Command Line.

  • Modified the RCU default log location. For example, on UNIX operating systems, the main RCU log (rcu.log) and component log files are now written to the /tmp/RCUdate_timestamp_random_number/logs directory by default. See RCU Log Files.