Oracle® Fusion Middleware

Installing Oracle GoldenGate Studio

12c (12.2.1.1)

E72770-02

November 2016

Documentation for installers and system administrators that describes how to install Oracle GoldenGate Studio.

Oracle Fusion Middleware Installing Oracle GoldenGate Studio, 12c (12.2.1.1)

E72770-02

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

Primary Author: Sreevalli Setty

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

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

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

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

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

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

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

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 Preparing to Install Oracle GoldenGate Studio

- 1.1 Roadmap for Installing Oracle GoldenGate Studio

- 1.2 Roadmap for Verifying Your System Environment

- 1.2.1 Verifying Certification, System, and Interoperability Requirements

- 1.2.2 Selecting an Installation User

- 1.2.2.1 Understanding User Permissions

- 1.2.2.2 Understanding Non-Default User Permissions on UNIX Operating Systems

- 1.2.2.3 Verifying the Installation User has Administrator Privileges on Windows Operating Systems

- 1.2.3 About the Oracle Home Directory

- 1.2.4 Understanding JDK Requirements for an Oracle Fusion Middleware Installation

- 1.2.5 Understanding Database Requirements for an Oracle Fusion Middleware Installation

- 1.3 Obtaining the Product Distribution

2 Installing the Oracle GoldenGate Studio Software

- 2.1 Verifying the Installation Checklist

- 2.2 Starting the Installation Program

- 2.3 Navigating the Installation Screens

- 2.4 Verifying the Installation

- 2.4.1 Reviewing the Installation Log Files

- 2.4.2 Checking the Directory Structure

- 2.4.3 Viewing the Contents of the Oracle Home

3 Creating the Oracle GoldenGate Studio Repository Schema

- 3.1 Installing and Configuring a Certified Database

- 3.2 Starting the Repository Creation Utility

- 3.3 Navigating the Repository Creation Utility Screens to Create the Schemas

- 3.3.1 Introducing the RCU

- 3.3.2 Selecting a Method of Schema Creation

- 3.3.3 Providing Database Connection Details

- 3.3.4 Specifying a Custom Prefix and Selecting the Oracle GoldenGate Repository Schema

- 3.3.5 Specifying Schema Passwords

- 3.3.6 Specifying Custom Variables

- 3.3.7 Completing Schema Creation

- 3.4 Verifying the Installation

4 Next Steps After Installing Oracle GoldenGate Studio

- 4.1 Starting Oracle GoldenGate Studio

- 4.2 Performing Oracle GoldenGate Studio Tasks

5 Deinstalling or Reinstalling Oracle GoldenGate Studio

- 5.1 About Product Deinstallation

- 5.2 Stopping Oracle Fusion Middleware

- 5.3 Removing Your Database Schemas

- 5.4 Deinstalling the Software

- 5.4.1 Starting the Deinstallation Program

- 5.4.2 Selecting the Product to Deinstall

- 5.4.3 Navigating the Deinstallation Screens

- 5.5 Removing the Oracle Home Directory Manually

- 5.6 Removing the Program Shortcuts on Windows Operating Systems

- 5.7 Removing the Oracle GoldenGate Studio Cache Directory

- 5.8 Reinstalling the Software

Preface

This document describes how to install Oracle GoldenGate Studio.

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

Audience

This document is intended for system administrators or application developers who are installing Oracle GoldenGate Studio. It is assumed that readers have a general understanding of Windows and UNIX platforms.

Documentation Accessibility

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

Access to Oracle Support

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

Related Documents

Refer to the Oracle Fusion Middleware Library for additional information.

- For installation information, see Fusion Middleware Installation Documentation.

- For upgrade information, see Fusion Middleware Upgrade Documentation.

- For administration-related information, see Fusion Middleware Administration Documentation.

- For release-related information, see Fusion Middleware Release Notes.

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 Preparing to Install Oracle GoldenGate Studio

To prepare for your Oracle GoldenGate Studio installation, verify that your system meets the basic requirements. Then obtain the correct installation software.

- Roadmap for Installing Oracle GoldenGate Studio
This roadmap has all the steps required to install Oracle GoldenGate Studio, such as verifying your environment, running the installer, creating the Repository schema, and starting Oracle GoldenGate Studio after installation.

- Roadmap for Verifying Your System Environment
Before you begin the installation process, read and understand the important information in this roadmap; it identifies important tasks and checks to perform to ensure that your environment is properly prepared for installing Oracle GoldenGate Studio.

- Obtaining the Product Distribution
You install Oracle GoldenGate Studio using the Oracle Fusion Middleware GoldenGate Studio distribution, which you can obtain from the Oracle Technology Network (OTN).

1.1 Roadmap for Installing Oracle GoldenGate Studio

This roadmap has all the steps required to install Oracle GoldenGate Studio, such as verifying your environment, running the installer, creating the Repository schema, and starting Oracle GoldenGate Studio after installation.

Table 1-1 Standard Installation Roadmap

Task

Description

Documentation

Verify your system environment

Before beginning the installation, verify that the minimum system and network requirements are met.

See Roadmap for Verifying Your System Environment.

Check for any mandatory patches that will be required before or after the installation

Review the Oracle Fusion Middleware Infrastructure release notes to see if there are any mandatory patches required for the software products you are installing.

See Install and Configure in Release Notes for Oracle Fusion Middleware Infrastructure.

Obtain the appropriate distribution

Obtain the Oracle GoldenGate Studio distribution.

See Obtaining the Product Distribution.

Determine your installation directories

Verify that the installer can access or create the installer directories that it must access or create. Also, verify that the directories exist on systems that meet the minimum requirements.

Note: Oracle does not recommend installing the Oracle GoldenGate Studio binaries on a NFS mounted file system.

See What are the Key Oracle Fusion Middleware Directories? in Understanding Oracle Fusion Middleware.

Install the software

Run the Oracle Universal Installer to install Oracle GoldenGate Studio.

Installing the software transfers the software to your system and creates the Oracle home directory.

See Installing the Oracle GoldenGate Studio Software.

Create the Oracle GoldenGate Studio Repository schema.

Run the Repository Creation Utility to create the Oracle GoldenGate Studio Repository schema.

See Creating the Oracle GoldenGate Studio Repository Schema.

Start and use Oracle GoldenGate Studio.

Discover additional tools and resources to use Oracle GoldenGate Studio.

See Next Steps After Installing Oracle GoldenGate Studio.

1.2 Roadmap for Verifying Your System Environment

Before you begin the installation process, read and understand the important information in this roadmap; it identifies important tasks and checks to perform to ensure that your environment is properly prepared for installing Oracle GoldenGate Studio.

Table 1-2 Roadmap for Verifying Your System Environment

Task

Description

Documentation

Verify certification and system requirements

Verify that your operating system is certified and properly configured for installation and configuration.

See Verifying Certification, System, and Interoperability Requirements.

Identify a proper installation user

Verify that the installation user has the proper permissions to install the software.

See Selecting an Installation User.

Select the Oracle home directory on your system.

Verify that you can create the necessary Oracle home directory for installation, according to the recommended directory structure.

Oracle GoldenGate Studio is a standalone installation. The Oracle home directory should be a new, empty directory.

See About the Oracle Home Directory.

Install a certified JDK

The installation program for the distribution requires a certified JDK present on your system.

See Understanding JDK Requirements for an Oracle Fusion Middleware Installation.

Install and configure a database for mid-tier schemas

You must have access to a certified database that is properly configured for the Repository schema required by Oracle GoldenGate Studio.

See Understanding Database Requirements for an Oracle Fusion Middleware Installation.

- Verifying Certification, System, and Interoperability Requirements
Oracle recommends that you use the certification matrix and system requirements documents with each other to verify that your environment meets the requirements for installation.

- Selecting an Installation User
The user who performs installation and configuration on your system requires sufficient permissions and privileges.

- About the Oracle Home Directory
When you install any Oracle Fusion Middleware product, you must use an Oracle home directory.

- Understanding JDK Requirements for an Oracle Fusion Middleware Installation
Most Fusion Middleware products are in .jar file format. These distributions do not include a JDK. To run a .jar distribution installer, you must have a certified JDK already installed on your system.

- Understanding Database Requirements for an Oracle Fusion Middleware Installation
Many Oracle Fusion Middleware products require database schemas prior to configuration. If you do not already have a database where you can install these schemas, you must install and configure a certified database.

1.2.1 Verifying Certification, System, and Interoperability Requirements

Oracle recommends that you use the certification matrix and system requirements documents with each other to verify that your environment meets the requirements for installation.

1. Verifying your environment meets certification requirements
Make sure that you are installing your product on a supported hardware and software configuration. For more information, see the certification document for your release on the Oracle Fusion Middleware Supported System Configurations page.

Oracle has tested and verified the performance of your product on all certified systems and environments. Whenever new certifications occur, they are added to the proper certification document right away. New certifications can be released at any time. Therefore, the certification documents are kept outside the documentation libraries and are available on Oracle Technology Network.

2. Using the system requirements document to verify certification
Oracle recommends that you use the Oracle Fusion Middleware System Requirements and Specifications document to verify that the certification requirements are met. For example, if the certification document indicates that your product is certified for installation on 64-Bit Oracle Linux 6.5, use this document to verify that your system meets the required minimum specifications. These include disk space, available memory, specific platform packages and patches, and other operating system-specific items. System requirements can change in the future. Therefore, the system requirement documents are kept outside of the documentation libraries and are available on Oracle Technology Network.

3. Verifying interoperability among multiple products
See Oracle Fusion Middleware 12c Interoperability and Compatibility in Understanding Interoperability and Compatibility to learn how to install and run multiple Fusion Middleware products from the same release or mixed releases with each other.

1.2.2 Selecting an Installation User

The user who performs installation and configuration on your system requires sufficient permissions and privileges.

- Understanding User Permissions
The user who installs a Fusion Middleware product owns the files and has certain permissions on the files.

- Understanding Non-Default User Permissions on UNIX Operating Systems
Changing the default permissions setting reduces the security of the installation and possibly your system. Oracle does not recommend changing default permission settings.

- Verifying the Installation User has Administrator Privileges on Windows Operating Systems
To update the Windows Registry, you must have Administrator privileges.

1.2.2.1 Understanding User Permissions

The user who installs a Fusion Middleware product owns the files and has certain permissions on the files.

The user who installs a Fusion Middleware product has the following permissions on them:

- Read and write permissions on all non-executable files (for example, .jar, .properties, or .xml). All other users in the same group as the file owner have read permissions only.

- Read, write, and execute permissions on all executable files (for example, .exe, .sh, or .cmd). All other users in the same group as the file owner have read and execute permissions only.

This means that someone other than the person who installs the software can use the installed binaries in the Oracle home to configure a domain or set of Fusion Middleware products.

Below are some additional considerations to make prior to running the installer:

- On UNIX operating systems, Oracle recommends that you set the umask to 027 on your system prior to installation. This ensures that file permissions are set properly during installation. Use the following command:
umask 027

You must enter this command in the same terminal window from which you plan to run the product installer.

- On UNIX operating systems, do not run the installation program as the root user. The installer startup validation will fail and you will not be able to continue.

- When managing a product installation (for example, applying patches), you must use the same user ID as was used to perform the initial product installation.

- On Windows operating systems, the user performing the installation must have Administrator privileges. See Verifying the Installation User has Administrator Privileges on Windows Operating Systems for more information.

1.2.2.2 Understanding Non-Default User Permissions on UNIX Operating Systems

Changing the default permissions setting reduces the security of the installation and possibly your system. Oracle does not recommend changing default permission settings.

If other users require access to particular files or executable, consider using the UNIX sudo command (or other similar command) in lieu of changing file permissions.

Refer to your UNIX operating system Administrator's Guide or contact your operating system vendor if you need further assistance.

1.2.2.3 Verifying the Installation User has Administrator Privileges on Windows Operating Systems

To update the Windows Registry, you must have Administrator privileges.

By default, members with the Administrator privilege sign in to the system with regular privileges, but can request elevated permissions to perform administrative tasks.

To perform a task with elevated privileges:

1. Find the Command Prompt item, either from the Start menu or the Windows icon in the lower-left hand corner.

2. Right-click Command Prompt and select Run as administrator.
This opens a new command prompt window, and all actions performed in this window will be done with administrator privileges.

Note:
If you have User Access Control enabled on your system, you may see an additional window asking you to confirm this action. Confirm and continue with this procedure.

3. Perform the desired task.

For example, to start the product installer:

For a jar file, enter:

java —jar distribution_name.jar

For an executable (.exe, .bin, or .sh file), enter:

distribution_name.exe

1.2.3 About the Oracle Home Directory

When you install any Oracle Fusion Middleware product, you must use an Oracle home directory.

This directory is a repository for common files that are used by multiple Fusion Middleware products installed on the same machine. These files are essential to ensuring that Fusion Middleware operates correctly on your system. They facilitate checking of cross-product dependencies during installation. For this reason, you can consider the Oracle home directory a central support directory for all Oracle Fusion Middleware products installed on your system.

Fusion Middleware documentation refers to the Oracle home directory as ORACLE_HOME.

Oracle Home Considerations

Keep the following in mind when creating the Oracle home directory and installing Fusion Middleware products:

- Do not include spaces in the name of your Oracle home directory; the installer gives you an error message if your Oracle home directory path contains spaces.

- You can install only one instance of each Oracle Fusion Middleware product in a single Oracle home directory. If you need to maintain separate versions of a product on the same machine, each version must be in its own Oracle home directory.
Although you can have several different products in a single Oracle home, only one version of each product can be in the Oracle home.

Multiple Home Directories

Although in most situations, a single Oracle home directory is sufficient, it is possible to create more than one Oracle home directory. For example, you need to maintain multiple Oracle home directories in the following situations:

- You prefer to maintain separate development and production environments, with a separate product stack for each. With two directories, you can update your development environment without modifying the production environment until you are ready to do so.

- You want to maintain two different versions of a Fusion Middleware product at the same time. For example, you may want to install a new version of a product while keeping your existing version intact. In this case, you must install each product version in its own Oracle home directory.

- You need to install multiple products that are not compatible with each other. See Oracle Fusion Middleware 12c (12.2.1.1) Interoperability and Compatibility in Understanding Interoperability and Compatibility for more information.

Note:
If you create more than one Oracle home directory, you must provide non-overlapping port ranges during the configuration phase for each product.

1.2.4 Understanding JDK Requirements for an Oracle Fusion Middleware Installation

Most Fusion Middleware products are in .jar file format. These distributions do not include a JDK. To run a .jar distribution installer, you must have a certified JDK already installed on your system.

Make sure that the JDK is installed outside of the Oracle home. If you install the JDK under the Oracle home, you will encounter problems when you try to perform tasks in the future. Oracle Universal Installer validates that the Oracle home directory is empty; the install will not progress until you specify an empty directory. Oracle recommends that you locate your JDK installation in the /home/oracle/products/jdk directory.

Some products (such as Oracle HTTP Server and Oracle JDeveloper) are available as platform-specific distributions. Platform-specific distributions have a .bin (for UNIX operating systems) or .exe (for Windows operating systems) installer; in these cases, a platform-specific JDK is in the distribution and you do not need to install a JDK separately. However, you may need to upgrade this JDK to a more recent version, depending on the JDK versions that are certified.

Always verify the required JDK version by reviewing the certification information on the Oracle Fusion Middleware Supported System Configurations page.

To download the required JDK, navigate to the following URL and download the Java SE JDK:

http://www.oracle.com/technetwork/java/javase/downloads/index.html

1.2.5 Understanding Database Requirements for an Oracle Fusion Middleware Installation

Many Oracle Fusion Middleware products require database schemas prior to configuration. If you do not already have a database where you can install these schemas, you must install and configure a certified database.

To find a certified database for your operating system, see the certification document for your release on the Oracle Fusion Middleware Supported System Configurations page.

To make sure your database is properly configured for schema creation, see "Repository Creation Utility Requirements" in the Oracle Fusion Middleware System Requirements and Specifications document.

After your database is properly configured, you use the Repository Creation Utility (RCU) to create product schemas in your database. This tool is available in the Oracle home for your Oracle Fusion Middleware product. For more information about the RCU, see Understanding Repository Creation Utility in Creating Schemas with the Repository Creation Utility.

1.3 Obtaining the Product Distribution

You install Oracle GoldenGate Studio using the Oracle Fusion Middleware GoldenGate Studio distribution, which you can obtain from the Oracle Technology Network (OTN).

To install Oracle GoldenGate Studio, download and unzip the installer ZIP file to a directory on your system. You can then run the java —jar command from that directory to start the installer.

To locate and download Oracle Fusion Middleware products, see Oracle Fusion Middleware Download, Installation, and Configuration Readme Files on OTN.

You must have a certified JDK installed on your system to install this distribution.

Note:

For more information about distributions, see Understanding and Obtaining Product Distributions in Planning an Installation of Oracle Fusion Middleware.

2 Installing the Oracle GoldenGate Studio Software

Follow these step to install the Oracle GoldenGate Studio software and verify that it is installed properly.

Before beginning the installation, ensure that you have verified your system environment (Roadmap for Verifying Your System Environment).

By the end of this section, you will have installed Oracle GoldenGate Studio.

- Verifying the Installation Checklist
The installation process requires specific information from you.

- Starting the Installation Program
Before running the installation program, you must verify the JDK and prerequisite software is installed.

- Navigating the Installation Screens
The installer shows a series of screens where you verify or enter information about your installation.

- Verifying the Installation
After you complete the installation, verify it was successful by completing a series of tasks.

2.1 Verifying the Installation Checklist

The installation process requires specific information from you.

Table 2-1 lists important items that you must know before, or decide during, Oracle GoldenGate Studio installation.

Table 2-1 Installation Checklist

Information

Example Value

Description

JAVA_HOME

/home/Oracle/Java/jdk1.8.0_77

Environment variable that points to the Java JDK home directory.

Database host name

examplehost.exampledomain

Name and domain of the host where the database is running.

Database port

1521

Port number that the database listens on. The default Oracle database listen port is 1521.

Database service name

orcl

Oracle databases require a unique service name. The default service name is orcl.

DBA user name

SYS

Name of user with database administration privileges. The default DBA user on Oracle databases is SYS.

DBA password

ExamplePassword1

Password of the user with database administration privileges.

ORACLE_HOME

/home/Oracle/product/Oracle_Home

Directory you will install your software in.

This directory will include Oracle GoldenGate Studio.

RCU utility

ORACLE_HOME/oracle_common/bin

Path to the Repository Creation Utility (RCU).

RCU schema prefix

DEV

Prefix for names of database schema used by Oracle GoldenGate Studio.

RCU schema password

ExamplePassword1

Password for the database schema used by Oracle GoldenGate Studio.

2.2 Starting the Installation Program

Before running the installation program, you must verify the JDK and prerequisite software is installed.

To start the installation program:

1. Sign in to the host system.

2. If you have not already done so, verify that a certified JDK is installed on your system: enter java -version on the command line. For 12c (12.2.1.1), the certified JDK is 1.8.0_77 and later.

For more information, see Understanding JDK Requirements for an Oracle Fusion Middleware Installation.

3. Verify that you have installed all prerequisite software, such as Oracle Fusion Middleware Infrastructure.

4. Go to the directory where you downloaded the installation program.

5. Unzip the installer fmw_12.2.1.1.0_odi_Disk1_1of2.zip and fmw_12.2.1.1.0_odi_Disk1_2of2.zip files.

6. Start the installation program by running the java executable from the JDK directory. For example:

- (UNIX) /home/Oracle/Java/jdk1.8.0_77/bin/java —jar fmw_12.2.1.1.0_oggstudio_generic.jar

- (Windows) C:\home\Oracle\Java\jdk1.8.0_77\bin\java -jar fmw_12.2.1.1.0_oggstudio_generic.jar

Note:

You can also start the installer in silent mode using a saved response file instead of launching the installer screens. For more about silent or command line installation, see Using the Oracle Universal Installer in Silent Mode in Installing Software with the Oracle Universal Installer.

When the installation program appears, you are ready to begin the installation.

2.3 Navigating the Installation Screens

The installer shows a series of screens where you verify or enter information about your installation.

The following table lists the order in which installer screens appear. If you need additional help with an installation screen, click the screen name. You can also click Help on the installation screens for additional instructions.

Table 2-2 Oracle GoldenGate Studio Install Screens

Screen

Description

Installation Inventory Setup

On UNIX operating systems, this screen opens if this is the first time you are installing any Oracle product on this host. Specify the location where you want to create your central inventory. Make sure that the operating system group name selected on this screen has write permissions to the central inventory location.

For more about the central inventory, see Understanding the Oracle Central Inventory in Installing Software with the Oracle Universal Installer.

This screen does not appear on Windows operating systems.

Welcome

This screen introduces you to the product installer.

Auto Updates

Use this screen to search for the latest software updates, including important security updates, via your My Oracle Support account.

Installation Location

Use this screen to specify your Oracle home directory location. The Oracle home location you specify on this screen should be a new, empty directory.

You can click View to verify and ensure that you are installing Oracle GoldenGate Studio in the correct Oracle home.

For more about Oracle Fusion Middleware directory structure, see Understanding Directories for Installation and Configuration in Planning an Installation of Oracle Fusion Middleware.

Installation Type

Use this screen to select the installation type and consequently, the products and feature sets you want to install. Complete Install is the only installation type for Oracle GoldenGate Studio. This option is already selected by default.

Prerequisite Checks

Verify that your system meets the minimum necessary requirements.

To view the list of tasks that get verified, select View Successful Tasks. To view log details, select View Log.

If there are warning or error messages, see one of the documents in Roadmap for Verifying Your System Environment.

Installation Summary

Use this screen to verify the installation options you selected. If you want to save these options to a response file, click Save Response File and enter the response file location and name. You can use response files later if you perform a silent installation.

All feature sets that are installed after installation is complete are listed here.

For more about silent or command line installation, see Using the Oracle Universal Installer in Silent Mode in Installing Software with the Oracle Universal Installer.

Click Install to begin the installation.

Installation Progress

This screen shows the installation progress.

When the progress bar reaches 100% complete, click Finish to dismiss the installer or click Next to see a summary.

Installation Complete

Review the summary information on this screen, then click Finish to dismiss the installer.

After installing the software, you should be able to start Oracle GoldenGate Studio from the ORACLE_HOME/oggstudio/bin directory. However, at this point, you will not be able to use the product. You must first create the repository using the Repository Creation Utility (RCU).

For more information on how to start Oracle GoldenGate Studio, see Starting Oracle GoldenGate Studio.

2.4 Verifying the Installation

After you complete the installation, verify it was successful by completing a series of tasks.

- Reviewing the Installation Log Files
Review the contents of the installation log files to make sure that the installer did not encounter any problems.

- Checking the Directory Structure
The contents of your installation vary based on the options you selected during the installation.

- Viewing the Contents of the Oracle Home
You can view the contents of the Oracle home using the viewInventory script.

2.4.1 Reviewing the Installation Log Files

Review the contents of the installation log files to make sure that the installer did not encounter any problems.

By default, the installer writes logs files to the Oracle_Inventory_Location/logs (on UNIX operating systems) or Oracle_Inventory_Location\logs (on Windows operating systems) directory.

For a description of the log files and where to find them, see Installation Log Files in Installing Software with the Oracle Universal Installer.

2.4.2 Checking the Directory Structure

The contents of your installation vary based on the options you selected during the installation.

For more information about the directory structure after installation, see What Are the Key Oracle Fusion Middleware Directories? in Understanding Oracle Fusion Middleware.

2.4.3 Viewing the Contents of the Oracle Home

You can view the contents of the Oracle home using the viewInventory script.

For more information, see Viewing the Contents of an Oracle Home in Installing Software with the Oracle Universal Installer.

3 Creating the Oracle GoldenGate Studio Repository Schema

The repository for Oracle GoldenGate Studio contains all of the replication design and deployment details. Therefore, you must install the repository schema on a certified database before using Oracle GoldenGate Studio. You create the repository using the Oracle Repository Creation Utility (RCU).

Before you begin creating the schema, ensure that you have completed installing the Oracle GoldenGate Studio software in a new, empty Oracle home. For more information, see Installing the Oracle GoldenGate Studio Software.

Follow the instructions in this section to install the schema:

- Installing and Configuring a Certified Database
Before creating the database schemas, you must install and configure a certified database, and verify that the database is up and running.

- Starting the Repository Creation Utility
Start the Repository Creation Utility (RCU) after verifying that a certified JDK is installed on your system.

- Navigating the Repository Creation Utility Screens to Create the Schemas
Enter required information in the RCU screens to create the database schemas.

- Verifying the Installation
After completing the installation steps, you should verify that Oracle GoldenGate Studio is properly installed.

3.1 Installing and Configuring a Certified Database

Before creating the database schemas, you must install and configure a certified database, and verify that the database is up and running.

For more information, see Understanding Database Requirements for an Oracle Fusion Middleware Installation.

3.2 Starting the Repository Creation Utility

Start the Repository Creation Utility (RCU) after verifying that a certified JDK is installed on your system.

To start the RCU:

1. Verify that a certified JDK already exists on your system by running java -version from the command line. For 12c (12.2.1.1), the certified JDK is 1.8.0_77 and later.

For more information, see Understanding JDK Requirements for an Oracle Fusion Middleware Installation.

2. Ensure that the JAVA_HOME environment variable is set to the location of the certified JDK. For example:

- (UNIX) setenv JAVA_HOME/home/Oracle/Java/jdk1.8.0_77

- (Windows) set JAVA_HOME=C:\home\Oracle\Java\jdk1.8.0_77

3. Go to the /oracle_common/bin directory:

- (UNIX) ORACLE_HOME/oracle_common/bin

- (Windows) ORACLE_HOME\oracle_common\bin

4. Enter the following command:

- (UNIX) ./rcu

- (Windows) rcu.bat

3.3 Navigating the Repository Creation Utility Screens to Create the Schemas

Enter required information in the RCU screens to create the database schemas.

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

- Selecting a Method of Schema Creation
Use the Create Repository screen to select a method to create and load component schemas into the database.

- Providing Database Connection Details
On the Database Connection Details screen, provide the database connection details for the RCU to connect to your database.

- Specifying a Custom Prefix and Selecting the Oracle GoldenGate Repository Schema
On the Select Components screen, select Create new prefix, specify a custom prefix, then select the Oracle GoldenGate - Repository schema.

- Specifying Schema Passwords
Use the Schema Passwords screen to specify how you want to set the schema passwords on your database, then specify and confirm your passwords.

- Specifying Custom Variables
Use the Custom Variables screen to specify a password for the supervisor user and to select the encryption algorithm for the Oracle GoldenGate Studio Repository schema.

- Completing Schema Creation
Navigate through the remaining RCU screens to complete schema creation.

3.3.1 Introducing the RCU

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

Click Next.

3.3.2 Selecting a Method of Schema Creation

Use the Create Repository screen to select a method to create and load component schemas into the database.

On the Create Repository screen:

- If you have the necessary permission and privileges to perform DBA activities on your database, select System Load and Product Load. This procedure assumes that you have SYSDBA privileges.

- If you do not have the necessary permission or privileges to perform DBA activities in the database, you must select Prepare Scripts for System Load on this screen. This option generates a SQL script that you can give to your database administrator. See About System Load and Product Load in Creating Schemas with the Repository Creation Utility.

- If the DBA has already run the SQL script for System Load, select Perform Product Load.

3.3.3 Providing Database Connection Details

On the Database Connection Details screen, provide the database connection details for the RCU to connect to your database.

Note:

If you are unsure of the service name for your database, you can obtain it from the SERVICE_NAMES parameter in the initialization parameter file of the database. If the initialization parameter file does not contain the SERVICE_NAMES parameter, then the service name is the same as the global database name, which is specified in the DB_NAME and DB_DOMAIN parameters.

For example:

- Database Type: Oracle Database

- Name: examplehost.exampledomain.com

- Port: 1521

- Service Name: Orcl.exampledomain.com

- User Name: sys

- Password: ******

- Role: SYSDBA

Click Next to proceed, then click OK in the dialog window that confirms a successful database connections.

3.3.4 Specifying a Custom Prefix and Selecting the Oracle GoldenGate Repository Schema

On the Select Components screen, select Create new prefix, specify a custom prefix, then select the Oracle GoldenGate - Repository schema.

The schema Common Infrastructure Services is also automatically created. This schema is dimmed; you cannot select or deselect it. For more information, see Understanding the Service Table Schema in Creating Schemas with the Repository Creation Utility.

The custom prefix is used to logically group schemas together. Note that a prefix is required.

Tip:

For more information about custom prefixes, see Understanding Custom Prefixes in Creating Schemas with the Repository Creation Utility.

For more information about how schemas can be organized, see Planning Your Schema Creation in Creating Schemas with the Repository Creation Utility.

Tip:

You must make a note of the custom prefix you choose to enter here; you will need this later on.

Click Next to proceed, then click OK on the dialog window confirming that prerequisite checking for schema creation was successful.

3.3.5 Specifying Schema Passwords

Use the Schema Passwords screen to specify how you want to set the schema passwords on your database, then specify and confirm your passwords.

Tip:

You must make a note of the passwords you set on this screen; you will need them later on when providing your database connection information to connect to the repository after you start Oracle GoldenGate Studio.

3.3.6 Specifying Custom Variables

Use the Custom Variables screen to specify a password for the supervisor user and to select the encryption algorithm for the Oracle GoldenGate Studio Repository schema.

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

Variable

Description

Supervisor Password

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

You must enter a password for the Supervisor Password and Confirm Supervisor Password fields. These fields are required before you can continue. The password should be between 6 and 12 characters.

Make a note of the password you set on this screen; you will need it later on when providing your Oracle GoldenGate Studio connection information to connect to the repository after you start Oracle GoldenGate Studio.

Encryption Algorithm

Select the encryption algorithm, AES-128.

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

3.3.7 Completing Schema Creation

Navigate through the remaining RCU screens to complete schema creation.

On the Map Tablespaces screen, the Encrypt Tablespace check box appears only if you enabled TDE (Transparent Data Encryption) in the database (Oracle or Oracle EBR) when you start the RCU. Select the Encrypt Tablespace check box if you want to encrypt all new tablespaces that the RCU will create.

When you reach the Completion Summary screen, click Close to dismiss the RCU.

3.4 Verifying the Installation

After completing the installation steps, you should verify that Oracle GoldenGate Studio is properly installed.

To verify that Oracle GoldenGate Studio is installed properly, see Performing Oracle GoldenGate Studio Tasks. You should familiarize yourself with the tasks that this section describes and perform them to verify that Oracle GoldenGate Studio is properly installed.

4 Next Steps After Installing Oracle GoldenGate Studio

After installing the software and creating the Repository schema, there are additional tasks you might want to perform to get started working with Oracle GoldenGate Studio.

- Starting Oracle GoldenGate Studio
After you install the software and create your Oracle home, you can start and access Oracle GoldenGate Studio from the ORACLE_HOME/oggstudio/bin directory.

- Performing Oracle GoldenGate Studio Tasks
To get started, review these common tasks you will likely want to perform after installing Oracle GoldenGate Studio.

4.1 Starting Oracle GoldenGate Studio

After you install the software and create your Oracle home, you can start and access Oracle GoldenGate Studio from the ORACLE_HOME/oggstudio/bin directory.

To start Oracle GoldenGate Studio:

1. Change directory to the ORACLE_HOME/oggstudio/bin directory.

For example:

cd ORACLE_HOME/oggstudio/bin

2. Run the following command:

On Linux or UNIX:

./oggstudio

On Windows:

oggstudioW.exe

4.2 Performing Oracle GoldenGate Studio Tasks

To get started, review these common tasks you will likely want to perform after installing Oracle GoldenGate Studio.

Table 4-1 Basic Tasks for Oracle GoldenGate Studio

Task

More Information

Use wizards that provide pre-configured solution and deployment templates.

See Understanding Solutions in Using Oracle GoldenGate Studio.

Evolve solutions by dragging and dropping data servers and replication paths to the solution diagram.

See Working with Solutions and Deployment Profiles in Using Oracle GoldenGate Studio.

Define physical resources and assign them to your deployment profiles.

See Understanding Deployment Profiles in Using Oracle GoldenGate Studio.

Create multiple deployment profiles (for example, separate profiles for testing and production team) for a single solution.

See Understanding Deployment Profiles in Using Oracle GoldenGate Studio.

Use Automap or manually map, schema, table, and column mappings and assign to replication paths.

See Understanding Mapping Groups in Using Oracle GoldenGate Studio.

Reuse mappings in multiple replication paths and across different projects.

See Understanding Mapping Groups in Using Oracle GoldenGate Studio.

Add, remove, and fine tune any Oracle GoldenGate option or parameter.

See Using the Properties Inspector in Using Oracle GoldenGate Studio.

Generate parameter files and Oracle GoldenGate commands. Deploy them online to live Oracle GoldenGate instances or save them locally for manual deployment.

See Understanding Deployment Profiles in Using Oracle GoldenGate Studio.

Start, stop, and monitor all physical processes.

See Monitoring in Using Oracle GoldenGate Studio.

Monitor your solutions and view deployment history information.

See Understanding Deployment Profiles in Using Oracle GoldenGate Studio.

Export solutions and mappings to XML files that can be imported by other Oracle GoldenGate Studio users.

See Using the Projects Navigator in Using Oracle GoldenGate Studio.

5 Deinstalling or Reinstalling Oracle GoldenGate Studio

Follow the instructions in this section to deinstall or reinstall Oracle GoldenGate Studio.

Note:
This task applies only to standalone Oracle GoldenGate Studio. You cannot deinstall Oracle GoldenGate Studio when it is collocated in a WebLogic Server domain, as partial deconfiguration of a configured domain is not supported.

Oracle recommends that you always use the instructions in this section to remove the software. If you try to remove the software manually, you may encounter problems when you try to reinstall the software again at a later time. Following the procedures in this section ensures that the software is properly removed.

- About Product Deinstallation
The Oracle Fusion Middleware deinstaller removes the software from the Oracle home directory that it starts from.

- Stopping Oracle Fusion Middleware
Before running the deinstaller, Oracle recommends that you stop all servers and processes associated with the Oracle home you are going to remove.

- Removing Your Database Schemas
Before you remove the Oracle home, Oracle recommends that you run Repository Creation Utility to remove the GoldenGate Studio Repository schema associated with this installation.

- Deinstalling the Software
Follow the instructions in this section to start the product deinstaller and remove the software.

- Removing the Oracle Home Directory Manually
After deinstalling the software, you must manually remove your Oracle home directory and any existing subdirectories that the deinstaller did not remove.

- Removing the Program Shortcuts on Windows Operating Systems
On Windows operating systems, you must also manually remove the program shortcuts; the deinstaller does not remove them for you.

- Removing the Oracle GoldenGate Studio Cache Directory
Oracle GoldenGate Studio cache information should be manually removed; the deinstaller does not remove this information.

- Reinstalling the Software
You can reinstall your software into the same Oracle home as a previous installation only if you deinstalled the software by following the instructions in this section, including manually removing the Oracle home directory.

5.1 About Product Deinstallation

The Oracle Fusion Middleware deinstaller removes the software from the Oracle home directory that it starts from.

Table 5-1 summarizes the deinstallation procedure and links to supporting documentation.

Table 5-1 Roadmap for Product Deinstallation

Task

Description

Documentation

Stop Oracle Fusion Middleware

All servers and processes associated with the Oracle home should be stopped before running the deinstaller.

Note that you should disconnect from the repository and close Oracle GoldenGate Studio.

See Stopping Oracle Fusion Middleware.

Remove your database schemas

Run Repository Creation Utility to remove the GoldenGate Studio Repository schema.

See Removing Your Database Schemas.

Remove the software

Run the product deinstaller to remove Oracle GoldenGate Studio.

Note that if your Oracle home contains multiple products, you must run the deinstaller multiple times, once for each product.

See Deinstalling the Software.

Remove the Oracle home directory

The deinstaller does not remove all files and folders from the Oracle home directory. After the deinstaller is finished, you must manually remove the Oracle home to complete your product removal.

See Removing the Oracle Home Directory Manually.

5.2 Stopping Oracle Fusion Middleware

Before running the deinstaller, Oracle recommends that you stop all servers and processes associated with the Oracle home you are going to remove.

For more information, see Stopping an Oracle Fusion Middleware Environment in Administering Oracle Fusion Middleware.

5.3 Removing Your Database Schemas

Before you remove the Oracle home, Oracle recommends that you run Repository Creation Utility to remove the GoldenGate Studio Repository schema associated with this installation.

If there are multiple sets of schemas on your database, be sure to identify the schema prefix associated with the schema you are removing.

For schema removal steps, see Dropping Schemas in Creating Schemas with the Repository Creation Utility.

5.4 Deinstalling the Software

Follow the instructions in this section to start the product deinstaller and remove the software.

Note:
This task applies only to standalone Oracle GoldenGate Studio. You cannot deinstall Oracle GoldenGate Studio when it is collocated in a WebLogic Server domain, as partial deconfiguration of a configured domain is not supported.

If you want to perform a silent (command-line) deinstallation, see Running the Oracle Universal Installer for Silent Deinstallation in Installing Software with the Oracle Universal Installer.

- Starting the Deinstallation Program

- Selecting the Product to Deinstall
Because multiple products might exist in the Oracle home, ensure that you are deinstalling the correct distribution.

- Navigating the Deinstallation Screens

5.4.1 Starting the Deinstallation Program

To start the deinstaller:

- On UNIX
On the command line, enter the following commands:

cd $ORACLE_HOME/oui/bin
./deinstall.sh

- On Windows
Do one of the following:

- Use a file manager window to navigate to the ORACLE_HOME\oui\bin directory and double-click on deinstall.cmd.

- Open a command prompt and enter the following commands:

cd %ORACLE_HOME%\oui\bin
deinstall.cmd

- From the Start menu, select All Programs, then Oracle, then OracleHome, and then Uninstall Oracle Software.

5.4.2 Selecting the Product to Deinstall

Because multiple products might exist in the Oracle home, ensure that you are deinstalling the correct distribution.

After you start the deinstaller, the Distribution to Uninstall screen appears only if more than one distribution is detected in the Oracle home from where the program is started. From the drop-down list, select GG Studio 12.2.1.1.0 and click Uninstall. The deinstallation program shows the screens listed in Navigating the Deinstallation Screens.

Note:

You will not encounter the Distribution to Uninstall screen if no other software is detected in the Oracle home.

5.4.3 Navigating the Deinstallation Screens

The deinstaller shows a series of screens to confirm the deinstallation of the software.

If you need help on screen listed in Table 5-2, click Help on the screen.

Table 5-2 Deinstallation Screens and Descriptions

Screen

Description

Welcome

Introduces you to the product deinstaller.

Deinstallation Summary

Shows the Oracle home directory and its contents that will be deinstalled. Verify that this is the correct directory.

If you want to save these options to a response file, click Save Response File and enter the response file location and name. You can use response file later during a silent deinstallation. For more on silent or command line deinstallation, see Running the Oracle Universal Installer for Silent Deinstallation in Installing Software with the Oracle Universal Installer.

Click Deinstall to begin removing the software.

Deinstallation Progress

Shows the deinstallation progress.

Deinstallation Complete

Appears when the deinstallation is complete. Review the information on this screen, then click Finish to dismiss the deinstaller.

5.5 Removing the Oracle Home Directory Manually

After deinstalling the software, you must manually remove your Oracle home directory and any existing subdirectories that the deinstaller did not remove.

For example, if your Oracle home directory is /home/Oracle/product/ORACLE_HOME on a UNIX operating system, enter the following commands:

cd /home/Oracle/product
rm -rf ORACLE_HOME

On a Windows operating system, if your Oracle home directory is C:\Oracle\Product\ORACLE_HOME, use a file manager window and navigate to the C:\Oracle\Product directory, then right-click on the ORACLE_HOME folder and select Delete.

5.6 Removing the Program Shortcuts on Windows Operating Systems

On Windows operating systems, you must also manually remove the program shortcuts; the deinstaller does not remove them for you.

To remove the program shortcuts on Windows:

1. Go to the C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Oracle\ORACLE_HOME\Product directory.

2. If you only have one product installed in your Oracle home, delete the ORACLE_HOME directory. If you have multiple products installed in your Oracle home, delete all products before deleting the ORACLE_HOME directory.

5.7 Removing the Oracle GoldenGate Studio Cache Directory

Oracle GoldenGate Studio cache information should be manually removed; the deinstaller does not remove this information.

By default, the Oracle GoldenGate Studio cache is stored in a directory inside the user’s home directory. For example:

On Linux or UNIX:

/home/exampleuser/.oggstudio

On Windows:

C:\Users\exampleuser\AppData\Roaming\oggstudio

The binaries and user preferences are stored in this directory. As a result, if Oracle GoldenGate Studio is reinstalled on the same system by the same user, the binaries from a previous installation will be used unless this directory is manually removed.

5.8 Reinstalling the Software

You can reinstall your software into the same Oracle home as a previous installation only if you deinstalled the software by following the instructions in this section, including manually removing the Oracle home directory.

When you reinstall, you can then specify the same Oracle home as your previous installation.

Consider the following cases where the Oracle home is not empty:

- Installing in an existing Oracle home that contains the same feature sets.
The installer warns you that the Oracle home you specified during installation already contains the same software you are trying to install.

Your options are:

- Select a different installation type. In this case, only the feature sets that do not exist in the Oracle home directory are installed.

- Select a different Oracle home directory.

- Installing in an existing, non-empty Oracle home.
For example, suppose that you chose to create your Domain home or Application home somewhere inside your existing Oracle home. This data is not removed during the deinstallation process, so if you try to reinstall into the same Oracle home, the installer does not allow it. Your options are:

1. Deinstall your software from the Oracle home (as this section describes) and then remove the Oracle home directory. After you deinstall the software and remove the Oracle home directory, you can reinstall and reuse the same Oracle home location. Any domain or application data that was in the Oracle home must be re-created.

2. Select a different Oracle home directory.

Oracle Legal Notices

Copyright Notice

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

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, then the following notice is applicable:

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

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.

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.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Pre-General Availability Draft Documentation Notice

If this document is in public or private pre-General Availability status:

This documentation is in pre-General Availability 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.

Private Pre-General Availability Draft Documentation Notice

If this document is in private pre-General Availability status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your pre-General Availability trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

Documentation Accessibility

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

Access to Oracle Support

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