1
Oracle® Fusion Middleware
Oracle GoldenGate Release Notes for Windows and UNIX
12c (12.2.0.1)
E64454-03
January 2016
This document describes the new features, major changes, and the known issues for
the 12c (12.2.0.1) release of Oracle GoldenGate for the Windows and UNIX platforms.
It includes the following sections:
■ Section 1, "New Features in 12c (12.2.0.1)"
■ Section 2, "Command Changes and Additions"
■ Section 3, "Parameter Changes and Additions"
■ Section 4, "Default Behavior Changes"
■ Section 5, "Installation"
■ Section 8, "Corrected Problems"
■ Section 9, "Known Issues"
■ Section 10, "Related Documents"
■ Section 11, "Getting Help with My Oracle Support"
■ Section 12, "Documentation Accessibility"
1 New Features in 12c (12.2.0.1)
This section outlines the new features that are being introduced in this release. It is
divided according to each database that this release supports, followed by new
features that apply to all supported databases.
■ Section 1.1, "New Core Features for Oracle GoldenGate"
■ Section 1.2, "New Features for Oracle Database"
■ Section 1.3, "New Features for SQL Server"
■ Section 1.4, "New Features for DB2 LUW"
■ Section 1.5, "New Features for Informix, MySQL, SQL/MX, Sybase, TimesTen, and
PostgreSQL"
1.1 New Core Features for Oracle GoldenGate
This section describes core infrastructure changes that allow the features to span
multiple databases in the Oracle GoldenGate 12.2.0.1:
2
Metadata Encapsulation
This feature stores and forwards metadata from the source to the target and
encapsulates it in each of the trail files to provide you the following benefits:
■ Extract embeds metadata records into each trail file before the first
SEQUENCE
or
first DML of each table. The following two metadata records are added to the trail
file:
■ Database Definition Record (DDR) — database character sets, time zone, and
object name case-sensitivity information.
■ Table Definition Record (TDR) — table and column definition.
■ With Oracle GoldenGate the Metadata associated with each table in the replication
process no longer requires the use of the
SOURCEDEFS
and
ASSUMETARGETDEFS
parameters. You can now configure replication without the need to define either of
these parameters.
■ You can now replicate Oracle DDL between two non-like Oracle schemas. For
example, the target may have more columns than the source, such as a timestamp
column.
■ You can now replicate table with different column ordering without the need of
SOURCEDEFS
.
■ Use of the Metadata Encapsulation feature is the default with the Oracle
GoldenGate 12.2.0.1 release.
■ You can easily switch between the old and new ways of resolving the table
metadata by:
-Using the new
USE_TRAILDEFS
GLOBALS parameter to control all pumps and
Replicats.
-Use the
OVERRIDE
option for individual
SOURCEDEFS
and
ASSUMETARGETDEFS
parameters in the pump or Replicat parameter files.
End to End Replication Lag
New built-in feature that provides end-to-end replication lag views without having to
manually implement the heartbeat tables as described in article Doc ID 965415.1 How
to setup GoldenGate to Maintain a Heartbeat With the Database. New commands were
added to simplify this replication configuration and provide extra features including:
■ Unidirectional lag from source to target.
■ Automatically discovers replication flows for all replication topologies.
■ Bidirectional lag when you setup in an Active-Active replication that provides
both incoming and outgoing lag.
■ The new Oracle GoldenGate Software Command Interface (GGSCI) command,
ADD
HEARTBEATTABLE
, enables this feature. There is no need to update the parameter
files of the replication processes to enable heartbeats.
■ The new
GG_LAG
Database View allows you to view the end-to-end lag
information.
Parameter Simplification
The use of Oracle GoldenGate parameters was simplified such that you can now:
3
■ Get detailed help on a parameter using the
INFO PARAM
command, which gives
you in depth details about the parameter and where it can be used.
■ View all of the active parameters associated with the running process using the
SEND … GETPARAMINFO
command.
■ Use the new
checkprm
utility to validate your parameter files. You can use
checkprm
to ensure the validity of your parameter files before you deploy the
replication to avoid syntax errors.
Trail File Extension Increase
Extending the maximum number of trail files by 1000x by extending it from a 6 digits
trail file to a 9 digit trail file. This 9 digits trail file format is the default.
Automated Remote Trail File Recovery by Pump
As of version 12.1.2.1.8, Oracle GoldenGate extends its high availability capabilities by
automatically handling when a target system is restored to a previous point in time.
This feature also handles most cases where target trail files have been inadvertently
deleted or corrupted. This is done by automatically regenerating the missing target
trail data when the source trail data is available and by intelligently skipping any
duplicate transactions when applying the change data.
The trail recovery process has the ability to, in some cases, automatically rebuild trail
files that are corrupt or missing by Oracle GoldenGate. When an Extract, pump
restarts, if the trail it is writing to is missing, the Extract pump will attempt to rebuild
the missing trail file on the target system. This is done automatically using the
checkpoint information for the process and the last valid trail file. The Replicat process
automatically skips over any duplicate data in the trail files that have been rebuilt by
the new trail recovery feature. This recovery will occur as long as there is at least 1
target trail from this sequence and that the trail files still exist on the source where the
Extract pump is reading them.
This process can also be used to rebuild corrupt or invalid trail files on the target.
Simply delete the corrupt trail file, and any trail files after that, and then restart the
Extract pump. With this new behavior, Ora we recommends that
PURGEOLDEXTRACTS
MINKEEP
rules are properly configured to ensure that there are trail files from the
source that can be used to rebuild the target environment. This feature requires that
Oracle GoldenGate release 12.1.2.1.8 or greater is used on both the source and target
servers. Do not attempt to start the Replicat with
NOFILTERDUPTRANSACTIONS
because it
will override this default behavior and may cause transactions that have already been
applied to the target database to be applied again.
Performance Toolkit Monitor
The Performance Toolkit Monitor is introduced and provides new metrics for
diagnostics and tuning including the following:
■ CPU
■ I/O
■ Transactions in flight
■ Cache memory usage and statistics
■ Improved capture and apply performance
4
These metrics are recorded in a RESTful API for use in diagnosing issues by Oracle
GoldenGate Support and Development. These metrics can be used to improve CPU
efficiency thus reducing load on source and target databases.
You can obtain the free corresponding Java program to configure your own
monitor
ing system at:
https://java.net/projects/oracledi/downloads/download/GoldenGate/OGGPTK.ja
r
Note: Use of the Performance Toolkit Monitor requires an Oracle
GoldenGate Management Pack license.
1.2 New Features for Oracle Database
In addition to the core features, there are multiple features specific to Oracle Databases
and are described in this section.
XAG Integration
Oracle GoldenGate can be configured to be mor
e aware of Oracle Grid Infrastructure
Bundled Agents (XAG) to provide a high availability environment in a cluster
configuration using the
XAGENABLE
parameter in the
GLOBALS
file. Not valid for HP
NonStop platforms.
Instantiation SCN Support
Simplified the online migration with the integration with Oracle data pump. It will
r
etain the SCN for each table and manage the point of apply for each table to better the
instantiation process.
Invisible Column Support
Replication of invisible columns is now supported in Integrated Capture mode. Trail
format
release 12.2 is required.
Fetch from Oracle Active Data Guard Support
Integrated Extract now has the capability to fetch data from an Oracle Active Data
Guar
d (ADG) Standby database eliminating any impact on the source database after
Extract has reached steady state.
1.3 New Features for SQL Server
The following are the new features that support SQL Server specifically.
Column Character Set Encoding Support
This allows replication between databases like SQL Server to an Oracle Database when
ther
e are multiple character set encodings per table.
Capture Support for Standard Edition
Capturing DML from SQL Server Standard Edition is introduced. In the previous
Gold
enGate 12.1.0 release, Oracle GoldenGate only supported capture of DML from
SQL Server Enterprise Edition, due to the method of enabling Supplemental Logging,
which is done using a feature only available to Enterprise Editions of SQL Server.
Oracle GoldenGate now enables Supplemental Logging for Standard Edition instances
5
using a different mechanism that is a feature of that edition. For more information, see
Installing and Configuring Oracle GoldenGate for SQL Server.
Archived Log Mode Only
Capturing DML from only the SQL Server transaction log backups is introduced.
Oracle GoldenGate can run on the database server in an Archived Log Mode (ALO)
only configuration (includes Remote ALO Mode). Optionally, Oracle GoldenGate can
be installed and run on a middle tier Windows server, which is the main advantage to
this feature. For more information, see Installing and Configuring Oracle GoldenGate
for SQL Server
Compressed Log Backups
Support for SQL Server 2014 Compressed Log Backups was added.
1.4 New Features for DB2 LUW
The following is the new feature that supports DB2 LUW specifically.
Temporal tables are now supported.
1.5 New Features for Informix, MySQL, SQL/MX, Sybase, TimesTen, and
PostgreSQL
There are no specific features related to the MySQL, Sybase, TimesTen, and
PostgreSQL databases and all core features are available with these databases.
2 Command Changes and Additions
This section contains information about new and updated Oracle GoldenGate
commands as the result of new features or functionality changes in the product for this
release.
■ Section 2.2, "Automatic Heartbeat Table"
■ Section 2.3, "Metadata Extract Trail"
■ Section 2.4, "GGSCI"
2.1 Enhanced Remote Trail Security
There is a new requirement if the target directory for incoming trails received from a
remote site will not be residing in the GoldenGate installation
dirdat
directory or a
dirdat
subdirectory. You must use the
ALLOWOUTPUTDIR
parameter in the
GLOBALS
file
to specify the target directory in these situations.
2.2 Automatic Heartbeat Table
These additions are the result of the new automatically generated heartbeat table.
■
[ENABLE | DISABLE]_HEARTBEAT_TABLE
— Specifies whether the Oracle
GoldenGate process will be handling records from
GG_HEARTBEAT
table or not.
When specified as a
GLOBALS
, it is true for the entire installation unless overridden
by a specific process.
评论0