Professional Documents
Culture Documents
May 2016
Contains instructions for installing and performing initial
setup of Oracle GoldenGate for the DB2 z/OS database.
Oracle Fusion Middleware Installing and Configuring Oracle GoldenGate for DB2 z/OS, 12c (12.2.0.1)
E67824-01
Copyright © 2013, 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, 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 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 ................................................................................................................................................................. v
Audience....................................................................................................................................................... v
Documentation Accessibility ..................................................................................................................... v
Related Documents ..................................................................................................................................... v
Conventions ................................................................................................................................................. vi
iii
3 Preparing the System for Oracle GoldenGate
3.1 Preparing Tables for Processing ............................................................................................... 3-1
3.1.1 Disabling Triggers and Cascade Constraints................................................................... 3-1
3.1.2 Assigning Row Identifiers .................................................................................................. 3-2
3.1.2.1 How Oracle GoldenGate Determines the Kind of Row Identifier to Use ............ 3-2
3.1.2.2 Using KEYCOLS to Specify a Custom Key................................................................... 3-2
3.1.3 Handling ROWID Columns................................................................................................... 3-2
3.2 Configuring Database Connections ......................................................................................... 3-3
3.2.1 Setting Initialization Parameters ....................................................................................... 3-3
3.2.2 Specifying the Path to the Initialization File .................................................................... 3-4
3.2.3 Ensuring ODBC Connection Compatibility..................................................................... 3-4
3.2.4 Specifying the Number of Connection Threads.............................................................. 3-4
3.3 Accessing Load Modules ........................................................................................................... 3-5
3.4 Specifying Job Names and Owners.......................................................................................... 3-5
3.5 Assigning WLM Velocity Goals................................................................................................ 3-5
3.6 Monitoring Processes ................................................................................................................. 3-6
3.6.1 Viewing Oracle GoldenGate Messages ............................................................................ 3-6
3.6.2 Identifying Oracle GoldenGate Processes........................................................................ 3-7
3.6.3 Interpreting Statistics for Update Operations ................................................................. 3-7
3.7 Supporting Globalization Functions ........................................................................................ 3-7
3.7.1 Replicating From a Source that Contains Both ASCII and EBCDIC ............................ 3-7
3.7.2 Specifying Multi-Byte Characters in Object Names ....................................................... 3-8
4 Preparing the DB2 for z/OS Transaction Logs for Oracle GoldenGate
4.1 Specifying a Bootstrap Data Set ................................................................................................ 4-1
4.2 Making Transaction Data Available......................................................................................... 4-1
4.2.1 Enabling Change Capture .................................................................................................. 4-1
4.2.2 Enabling Access to Log Records........................................................................................ 4-2
4.2.3 Sizing and Retaining the Logs ........................................................................................... 4-2
4.2.4 Using Archive Logs on Tape.............................................................................................. 4-3
4.2.5 Controlling Log Flushes...................................................................................................... 4-3
iv
Preface
On the IBM z/OS platform, Oracle GoldenGate for DB2 runs natively on UNIX System
Services (USS), also known as Open MVS (OMVS). With Oracle GoldenGate, you can
move data between similar or dissimilar supported DB2 for z/OS versions, or you can
move data between a DB2 for z/OS database and a database of another type, such as
Oracle or DB2 for LUW. Oracle GoldenGate for DB2 on the z/OS platform supports
the filtering, mapping, and transformation of data, unless otherwise noted in this
documentation.
This guide helps you get started with installing Oracle GoldenGate on a DB2 z/OS
database system and performing initial setup. Refer to the other Oracle GoldenGate
documentation listed in this Preface for additional information to configure, run, and
manage your Oracle GoldenGate environment.
Audience
This guide is intended for installers, database administrators, and system
administrators who are installing, configuring and running Oracle GoldenGate.
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.
Related Documents
The Oracle GoldenGate documentation set includes the following components:
v
■ Installing and Configuring Oracle GoldenGate for Informix
■ Installing and Configuring Oracle GoldenGate for MySQL
■ Installing and Configuring Oracle GoldenGate for NonStop SQL/MX
■ Installing and Configuring Oracle GoldenGate for SQL Server
■ Installing and Configuring Oracle GoldenGate for Oracle TimesTen
■ Installing and Configuring Oracle GoldenGate for Oracle Database
■ Installing and Configuring Oracle GoldenGate for Sybase
■ Installing and Configuring Oracle GoldenGate for Teradata
■ Administering Oracle GoldenGate for Windows and UNIX
■ Reference for Oracle GoldenGate for Windows and UNIX
■ Logdump Reference for Oracle GoldenGate
■ Upgrading Oracle GoldenGate for Windows and UNIX
■ Error Messages Reference for Oracle GoldenGate for Windows and UNIX
Conventions
The following text conventions are used in this document:
Convention Meaning
boldface Boldface type indicates graphical user interface elements associated
with an action, such as "From the File menu, select Save." Boldface also
is used for terms defined in text or in the glossary.
italic Italic type indicates placeholder variables for which you supply
particular values, such as in the parameter statement: TABLE table_
italic
name. Italic type also is used for book titles and emphasis.
monospace Monospace type indicates code components such as user exits and
scripts; the names of files and database objects; URL paths; and input
MONOSPACE
and output text that appears on the screen. Uppercase monospace type
is generally used to represent the names of Oracle GoldenGate
parameters, commands, and user-configurable functions, as well as
SQL commands and keywords.
UPPERCASE Uppercase in the regular text font indicates the name of a utility unless
the name is intended to be a specific case.
{} Braces within syntax enclose a set of options that are separated by pipe
symbols, one of which must be selected, for example: {option1 |
option2 | option3}.
[] Brackets within syntax indicate an optional element. For example in
this syntax, the SAVE clause is optional: CLEANUP REPLICAT group_name
[, SAVE count]. Multiple options within an optional element are
separated by a pipe symbol, for example: [option1 | option2].
vi
1
System Requirements and Preinstallation
1
Instructions
This chapter contains the requirements for the system and database resources that
[2]
support Oracle GoldenGate.
This chapter contains the following topics:
■ Section 1.1, "Verifying Certification and System Requirements"
■ Section 1.2, "Operating System Requirements"
■ Section 1.3, "Database Requirements"
■ Section 1.4, "Supported DB2 on z/OS Data Types"
■ Section 1.5, "Non-Supported DB2 on z/OS Data Types"
■ Section 1.6, "Supported Objects and Operations for DB2 on z/OS"
■ Section 1.7, "Non-Supported Objects and Operations for DB2 on z/OS"
1-2 Oracle GoldenGate Installing and Configuring Oracle GoldenGate for DB2 z/OS
Operating System Requirements
before downloading your selected build from Oracle Software Delivery Cloud.
The value shown is the size of the files in compressed form. The size of the
expanded Oracle GoldenGate installation directory will be significantly larger on
disk. For more information, see Section 2.3, "Understanding and Obtaining the
Oracle GoldenGate Distribution."
■ To install Oracle GoldenGate into a cluster environment, install the Oracle
GoldenGate binaries and files on a shared file system that is available to all cluster
nodes.
■ DSN=[hfs dsn]
■ DISP=(NEW,CATLG,DELETE)
■ SPACE =
■ DCB=DSORG=PO,DSNTYPE=HFS
Automatically mount the new file at IPL with an update to the BPXPRM UNIX
PARMLIB member. Make certain that the MOUNT FILESYSTEM parameter for HFS
in the BPXPRM PARMLIB member is not set to NOSETUID . To mount the files:
MOUNT FILESYSTEM([hfs dsn]') TYPE(HFS) MODE(RDWR)
MOUNTPOINT('[/u/ggs]')
1-4 Oracle GoldenGate Installing and Configuring Oracle GoldenGate for DB2 z/OS
Database Requirements
■ Grant Oracle GoldenGate EXECUTE privilege on the plan that is specified in the
ODBC initialization file (the default is DSNACLI).
■ You might need to insert the name of the local DB2 subsystem into the
SYSIBM.LOCATIONS table, which contains the remote DB2 server locations. Use a
statement similar to the following (the example uses the name DB2A).
INSERT INTO SYSIBM.LOCATIONS (LOCATION, PORT) VALUES ('DB2A', '446');
CREATE TABLE2 X
Table 1–2 (Cont.) Privileges Needed by Oracle GoldenGate for DB2 on z/OS
User privilege Extract Replicat
Privileges required by SQLEXEC procedures or queries that you X X
will be using.3
1
SELECT on source tables required only if tables contain LOB columns, or for an initial-load Extract, if used.
2
Required if using ADD CHECKPOINTTABLE in GGSCI to use the database checkpoint feature.
3
SQLEXEC enables stored procedures and queries to be executed by an Oracle GoldenGate process.
Limitations of Support
■ The support of range and precision for floating-point numbers depends on the
host machine. In general, the precision is accurate to 16 significant digits, but you
should review the database documentation to determine the expected
approximations. Oracle GoldenGate rounds or truncates values that exceed the
supported precision.
■ Oracle GoldenGate does not support the filtering, column mapping, or
manipulation of large objects greater than 4K in size. Full Oracle GoldenGate
functionality can be used for objects that are 4K or smaller.
■ DECFLOAT is fully supported by Replicat. Extract does not capture DECFLOAT from
the transaction log, but supports capture of it by fetching from the database.
1-6 Oracle GoldenGate Installing and Configuring Oracle GoldenGate for DB2 z/OS
Non-Supported Objects and Operations for DB2 on z/OS
1-8 Oracle GoldenGate Installing and Configuring Oracle GoldenGate for DB2 z/OS
2
Installing Oracle GoldenGate
2
[3This
] chapter shows you how to install Oracle GoldenGate for DB2 z/OS databases.
The installation procedure described here installs all of the components that are
required to run and manage the processing (excluding any components required from
other vendors, such as drivers or libraries). It also installs the Oracle GoldenGate
utilities.
This chapter contains the following sections:
■ Section 2.1, "Installation Overview"
■ Section 2.2, "Choosing an Installation System for DB2"
■ Section 2.3, "Understanding and Obtaining the Oracle GoldenGate Distribution"
■ Section 2.4, "Installing Oracle GoldenGate in USS on z/OS"
■ Section 2.5, "Installing Oracle GoldenGate on Linux and UNIX"
■ Section 2.6, "Installing Oracle GoldenGate on Windows"
These instructions are for installing Oracle GoldenGate for the first time. Additionally,
they are for downloading the base release of a new version of Oracle GoldenGate.
To download and install subsequent patches to the base release, go to the Patches and
Updates tab of My Oracle Support at:
http://support.oracle.com
To upgrade Oracle GoldenGate from one version to another, follow the upgrade
instructions in Upgrading Oracle GoldenGate for Windows and UNIX.
4. Add the target DB2 database to the DB2 for LUW catalog on the intermediary
system by using the following DB2 command:
catalog db database_name as database_alias at node db_node_name
5. Follow the instructions in Section 2.3, "Understanding and Obtaining the Oracle
GoldenGate Distribution" to download the appropriate build for the selected
remote Windows, Linux, or UNIX platform. Select the build that is labeled for
DB2Remote. Then, follow the appropriate instructions to install Oracle GoldenGate
on the intermediary system:
■ Section 2.5, "Installing Oracle GoldenGate on Linux and UNIX"
■ Section 2.6, "Installing Oracle GoldenGate on Windows"
6. Specify the DB2 target database name with the Replicat parameter TARGETDB when
you configure the Oracle GoldenGate processes.
2-2 Oracle GoldenGate Installing and Configuring Oracle GoldenGate for DB2 z/OS
Installing Oracle GoldenGate in USS on z/OS
5. In the UNIX shell, check for the "a" authorization for Extract and the DLL files by
issuing the following command.
ls -E extract *.dll
In the output, look for the "a" attribute, indicating the authorization in Authorized
Program Facility (APF) as shown in the following example.
6. If the "a" attribute is not set for both Extract and its DLL files (it may be built into
one but not the other, depending on the build configuration), issue the following
commands to add the authorization for Extract and the DLL files.
extattr +a extract
extattr +a *.dll
7. Run the command shell and change directories to the new Oracle GoldenGate
directory.
8. Set the LIBPATH environment variable to include the path to the Oracle
GoldenGate installation directory.
export LIBPATH=".:$(LIBPATH)"
The "." indicates the current directory. This change must be performed before
starting any Oracle GoldenGate processes and can be made in one of the following
ways:
■ system-wide
■ for a specific user at login time
■ manually each time that Oracle GoldenGate is executed
9. From the Oracle GoldenGate directory, run the GGSCI program.
GGSCI
10. In GGSCI, issue the following command to create the Oracle GoldenGate working
directories.
CREATE SUBDIRS
5. In GGSCI, issue the following command to create the Oracle GoldenGate working
directories.
CREATE SUBDIRS
2-4 Oracle GoldenGate Installing and Configuring Oracle GoldenGate for DB2 z/OS
Installing Oracle GoldenGate on Windows
3. In the file, add the following line, where name is a one-word name for the Manager
service.
MGRSERVNAME name
4. Save the file. The file is saved automatically with the name GLOBALS, but without a
file extension. Do not move this file. It is used during installation of the Windows
service and during data processing.
2-6 Oracle GoldenGate Installing and Configuring Oracle GoldenGate for DB2 z/OS
Installing Oracle GoldenGate on Windows
1
A user account can be changed by selecting the Properties action from the Services applet of the Windows
Control Panel.
4. If Windows User Account Control (UAC) is enabled, you are prompted to allow or
deny the program access to the computer. Select Allow to enable the INSTALL
utility to run.
The INSTALL utility installs the Manager service with a local system account
running with administrator privileges. No further UAC prompts will be
encountered when running Manager if installed as a service.
2-8 Oracle GoldenGate Installing and Configuring Oracle GoldenGate for DB2 z/OS
3
Preparing the System for Oracle GoldenGate
3
[4This
] chapter contains guidelines for preparing the database and the system to support
Oracle GoldenGate.
This chapter contains the following sections:
■ Preparing Tables for Processing
■ Configuring Database Connections
■ Accessing Load Modules
■ Specifying Job Names and Owners
■ Assigning WLM Velocity Goals
■ Monitoring Processes
■ Supporting Globalization Functions
3.1.2.1 How Oracle GoldenGate Determines the Kind of Row Identifier to Use
Unless a KEYCOLS clause is used in the TABLE or MAP statement, Oracle GoldenGate
selects a row identifier to use in the following order of priority:
1. Primary key
2. First unique key alphanumerically that does not contain a timestamp or
non-materialized computed column.
3. If none of the preceding key types exist (even though there might be other types of
keys defined on the table) Oracle GoldenGate constructs a pseudo key of all
columns that the database allows to be used in a unique key, excluding those that
are not supported by Oracle GoldenGate in a key or those that are excluded from
the Oracle GoldenGate configuration.
You can do one of the following to prepare tables with ROWID columns to be processed
by Oracle GoldenGate:
■ Ensure that any ROWID columns in target tables are defined as GENERATED BY
DEFAULT.
■ If it is not possible to change the table definition, you can work around it with the
following procedure.
3-2 Oracle GoldenGate Installing and Configuring Oracle GoldenGate for DB2 z/OS
Configuring Database Connections
The COLSEXCEPT clause excludes the ROWID column from being captured and
replicated to the target table.
2. For the target table, ensure that Replicat does not attempt to use the ROWID column
as the key. This can be done in one of the following ways:
■ Specify a primary key in the target table definition.
■ If a key cannot be created, create a Replicat MAP parameter for the table, and
use a KEYCOLS clause in that statement that contains any unique columns
except for the ROWID column. Replicat will use those columns as a key. For
example:
MAP tab1, TARGET tab1, KEYCOLS (num, ckey);
For more information about KEYCOLS, see Section 3.1.2, "Assigning Row Identifiers".
Note: When using the CAF attachment type, you must use the Oracle
GoldenGate DBOPTIONS parameter with the NOCATALOGCONNECT option
in the parameter file of any Extract or Replicat process that connects to
DB2. This parameter disables the usual attempt by Oracle GoldenGate
to obtain a second thread for the DB2 catalog. Otherwise, you will
receive error messages, such as: ODBC operation failed: Couldn't
connect to data source for catalog queries.
3-4 Oracle GoldenGate Installing and Configuring Oracle GoldenGate for DB2 z/OS
Assigning WLM Velocity Goals
If using CAF, there can be only one thread per Oracle GoldenGate process.
The preceding command will cause USS to allocate the equivalent of a STEPLIB DD
statement whenever it executes a shell command or Oracle GoldenGate process. If
using APF, all libraries in the STEPLIB concatenation must be APF-authorized.
priority, but the z/OS system executes them under the priority of a stored
procedure as defined by the DB2 and z/OS system programmers.
■ If you run Oracle GoldenGate under the TSO/E OMVS command, the Oracle
GoldenGate processes are subject to the system and WLM limits of the TSO/E
user account, rather than those of the UNIX kernel. Very long TSO/E response
times (up to 20 seconds), often with little service consumption, can be recorded for
an OMVS user because of the way that OMVS polls for terminal input. This can
affect those WLM goals that are based on response time.
You can use multiple WLM service classes for the Oracle GoldenGate processes. The
following is an example of how to maintain relative priorities for Oracle GoldenGate
and other work, from highest priority to the lowest:
1. z/OS system processes, including the UNIX kernel and IRLM.
2. DB2 for z/OS address spaces for the primary Extract group.
3. Primary Extract group configured for online or batch change synchronization, and
any DB2 stored procedures that it calls.
4. z/OS transaction managers, such as CICS and IMS.
5. Collector (Server) for local Extract data pump, if used.
6. Local Extract data pump (reading from trail), if used.
7. Collector for remote trails (files received from a remote site). Such files include the
QSAM file created with the Extract RMTBATCH parameter on a NonStop system.
8. Online Replicat groups and any DB2 stored procedures that they call.
9. Manager process (required only for startup of Oracle GoldenGate processes and
trail cleanup).
10. GGSCI and other user UNIX and TSO/E terminal work.
11. Initial-load Extract and any DB2 stored procedures that it calls.
12. Initial-load Replicat and any DB2 stored procedures that it calls.
3-6 Oracle GoldenGate Installing and Configuring Oracle GoldenGate for DB2 z/OS
Supporting Globalization Functions
messages to the Oracle GoldenGate USS session and to the Oracle GoldenGate report
files by using the following UNIX command:
export _BPXK_JOBLOG=STDERR
3.7.1 Replicating From a Source that Contains Both ASCII and EBCDIC
When replicating to or from a DB2 source system to a target that has a different
character set, some consideration must be given to the encoding of the character data
on the DB2 source if it contains a mix of ASCII and EBCDIC data. Character set
conversion by any given Replicat requires source data to be in a single character set.
The source character set is specified in the trail header. Thus, the Oracle GoldenGate
trail can contain either ASCII or EBCDIC data, but not both. Unicode tables are
processed without any special configuration and are exempt from the one-character set
requirement.
With respect to a source that contains both character encoding types, you have the
following options:
■ You can use one Extract for all of your tables, and have it write the character data
to the trail as either ASCII or as EBCDIC.
■ You can use different Extracts: one Extract to write the ASCII character data to a
trail, and another Extract to write the EBCDIC character data to a different trail.
You then associate each trail with its own data pump process and Replicat process,
so that the two data streams are processed separately.
To output the correct character set in either of those scenarios, use the
TRAILCHARSETASCII and TRAILCHARSETEBCDIC parameters. The default is
TRAILCHARSETEBCDIC. Without these parameters, ASCII and EBCDIC data are written
to the trail as-is. When using these parameters, note the following:
■ If used on a single-byte DB2 subsystem, these parameters cause Extract to convert
all of the character data to either the ASCII or EBCDIC single-byte CCSID of the
subsystem to which Extract is connected, depending on which parameter is used
(except for Unicode, which is processed as-is).
■ If used on a multi-byte DB2 subsystem, these parameters cause Extract to capture
only ASCII or EBCDIC tables (and Unicode). Character data is written in either the
ASCII or EBCDIC mixed CCSID (depending on the parameter used) of the DB2
z/OS subsystem to which Extract is connected.
3-8 Oracle GoldenGate Installing and Configuring Oracle GoldenGate for DB2 z/OS
4
Preparing the DB2 for z/OS Transaction Logs
4
[5This
] chapter contains information that you need to configure the DB2 transaction
logging to support data capture by Oracle GoldenGate Extract.
■ Section 4.1, "Specifying a Bootstrap Data Set"
■ Section 4.2, "Making Transaction Data Available"
Preparing the DB2 for z/OS Transaction Logs for Oracle GoldenGate 4-1
Making Transaction Data Available
3. Issue the following command. where table is the fully qualified name of the table.
You can use a wildcard to specify multiple table names but not owner names.
ADD TRANDATA table
4-2 Oracle GoldenGate Installing and Configuring Oracle GoldenGate for DB2 z/OS
Making Transaction Data Available
■ Alter Extract to capture from a later point in time for which log data is available
(and accept possible data loss on the target).
■ Resynchronize the source and target tables, and then start the Oracle GoldenGate
environment over again.
Preparing the DB2 for z/OS Transaction Logs for Oracle GoldenGate 4-3
Making Transaction Data Available
4-4 Oracle GoldenGate Installing and Configuring Oracle GoldenGate for DB2 z/OS
5
Uninstalling Oracle GoldenGate
5
from a system.
It contains the following sections:
■ Section 5.1, "Uninstalling Oracle GoldenGate from Linux or UNIX (includes USS)"
■ Section 5.2, "Removing Oracle GoldenGate from Windows Cluster"
■ Section 5.3, "Uninstalling Oracle GoldenGate from Windows (Non-Cluster)"
Warning: These procedures assume that you no longer need the data
in the Oracle GoldenGate trails, and that you no longer need to
preserve the current Oracle GoldenGate environment. To preserve
your current environment and data, make a backup of the Oracle
GoldenGate directory and all subdirectories before starting this
procedure.
On all Systems:
1. Run the command shell.
2. (Suggested) Log on as the system administrator or as a user with permission to
issue Oracle GoldenGate commands and delete files and directories from the
operating system.
3. Change directories to the Oracle GoldenGate installation directory.
4. Run GGSCI.
5. Stop all Oracle GoldenGate processes.
6. Stop the Manager process.
On a Source System:
Log into the database with the DBLOGIN command, and then run the DELETE TRANDATA
command to alter the tables to DATA CAPTURE NONE.
On all systems:
1. Make certain all processes are stopped (including GGSCI).
7. Move the cluster group to the next node in the cluster, and repeat from step 4.
8. Follow the instructions in Section 5.3, "Uninstalling Oracle GoldenGate from
Windows (Non-Cluster)".
On all Systems:
1. (Recommended) Log on as the system administrator or as a user with permission
to issue Oracle GoldenGate commands and to delete files and directories from the
operating system.
2. From the Oracle GoldenGate installation folder, run GGSCI.
3. Stop all Oracle GoldenGate processes.
4. Stop the Manager program or service.
5. Click Start then Run and type cmd in the Run dialog box to open the command
console.
6. Change directories to the Oracle GoldenGate installation directory.
5-2 Oracle GoldenGate Installing and Configuring Oracle GoldenGate for DB2 z/OS
Uninstalling Oracle GoldenGate from Windows (Non-Cluster)
7. Run the INSTALL utility with the following syntax to stop Oracle GoldenGate
events from being reported to the Windows Event Manager and to remove the
Manager service.
install deleteevents deleteservice
On a Source System:
Log into the database with the DBLOGIN command, and then run the DELETE TRANDATA
command to alter the tables to DATA CAPTURE NONE.
On all Systems:
Make certain all processes are stopped (including GGSCI) and then remove the Oracle
GoldenGate files by removing the installation directory.
5-4 Oracle GoldenGate Installing and Configuring Oracle GoldenGate for DB2 z/OS
A
AOracle GoldenGate Installed Components
This appendix describes the programs, directories, and other components created or
[7]
Note: Some programs may not exist in all installations. For example,
if only capture or delivery is supported by Oracle GoldenGate for
your platform, the extract or replicat program will not be installed,
respectively. Likewise, special files might be installed to support a
specific database.
A-2 Oracle GoldenGate Installing and Configuring Oracle GoldenGate for DB2 z/OS
Oracle GoldenGate Subdirectories
A-4 Oracle GoldenGate Installing and Configuring Oracle GoldenGate for DB2 z/OS
Other Oracle GoldenGate Files
A-6 Oracle GoldenGate Installing and Configuring Oracle GoldenGate for DB2 z/OS
Oracle GoldenGate Checkpoint Table
A-8 Oracle GoldenGate Installing and Configuring Oracle GoldenGate for DB2 z/OS