Upgrading Oracle GoldenGate Adapters
Release 12c (12.2.0.1)
E65337-01
June 2016
This document provides information on how to upgrade an existing Oracle GoldenGate Adapter.
This document contains the following sections:
There are two types of upgrades for the Oracle GoldenGate Java Adapters:
An adapter that is receiving changes captured from a source database and written to an Oracle GoldenGate trail.
An adapter that is receiving changes from a JMS source
The upgrade steps are different for each of these.
These sections explain the steps you need to follow for each of the types of upgrades.
If the adapter is receiving trail data from a source database, use the following upgrade steps:
Create an installation directory that has no spaces in its name.
Extract the zip file into this new installation directory. This will download the files into several subdirectories.
Still on the installation directory, bring up GGSCI to create the remaining subdirectories in the installation location.
Shell> ggsci GGSCI> CREATE SUBDIRS
Copy all of the dirprm files from your existing installation into the dirprm directory in the new installation location.
Note:
All of your configuration files must be in the dirprm directory. If you have property files, Velocity templates, or other configuration files in a location other than dirprm in your old installation, copy them to the dirprm directory in the new installation.
Copy all of the dirdef files from your existing installation into the dirdef directory in the new installation location.
If you have additional jar files or other custom files in your old installation, copy them to the new installation directory.
Configure the Extract pump processes in the new installation directory by bringing up GGSCI and adding the Extracts and naming the trails.
GGSCI> ADD EXTRACT group_name, EXTTRAILSOURCE trail_name, . . .
Start the Extract processes and verify that they are running:
GGSCI> START EXTRACT group_name GGSCI> INFO EXTRACT group_name GGSCI> VIEW REPORT group_name
Modify the source system to write to the new Oracle GoldenGate Adapter installation directory:
(Optional) Upgrade the source database Oracle GoldenGate capture following the upgrade procedure for your database platform.
Configure the source database capture to write to the new Oracle GoldenGate Adapter installation location dirdat directory.
When the old Oracle GoldenGate Adapter installation has processed all its data, switch over to the process that will send data to the new location.
If your adapter is capturing changes from a JMS source, use the following steps to upgrade the installation.
Create an installation directory that has no spaces in its name.
Extract the zip file into this new installation directory. This will download the files into several subdirectories.
Still on the installation directory, bring up GGSCI to create the remaining subdirectories in the installation location.
Shell> ggsci GGSCI> CREATE SUBDIRS
Copy all of the dirprm files from your existing installation into the dirprm directory in the new installation location.
Copy all of the dirdef files from your existing installation into the dirdef directory in the new installation location.
If you have additional jar files or other custom files in your old installation, copy them to the new installation directory.
Configure the Extract processes in the new installation directory to write to a new trail by bringing up GGSCI and adding the Extracts and naming the trails.
GGSCI> ADD EXTRACT group_name, EXTTRAILSOURCE trail_name, . . .
Stop the old Extract from the previous version.
GGSCI> STOP EXTRACT old_name
Start the new Extract processes and verify that they are running:
GGSCI> START EXTRACT group_name GGSCI> INFO EXTRACT group_name GGSCI> VIEW REPORT group_name
When the old Oracle GoldenGate Adapter installation has processed all its data, configure the downstream processes to read from the new trails generated by the upgraded JMS capture process.
This section covers special instructions for upgrading to certain release numbers.
This section covers special instructions to be followed when upgrading to Oracle GoldenGate Adapters release 12.1.2.1.0.
When upgrading to Oracle GoldenGate Adapters release 12.1.2.1.0 from release 11.1.0 or later, the previous logging configuration will use files stored in the ggjava directory. For example, logging property files may be found in ggjava/resources/classes. In 12.1.2, these files may have changed, moved, or may no longer exist.
To upgrade the logging configuration:
Navigate to the newly installed AdapterExamples directory
Locate the example logging configuration file
Copy the example file to the dirprm directory
Customize the logging configuration as needed
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.
Oracle® GoldenGate Application Adapters Upgrading Oracle GoldenGate Adapters, Release 12c (12.2.0.1)
E65337-01
Copyright © , 2016, Oracle and/or its affiliates. All rights reserved.
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.