Oracle GoldenGate 11.1.1.1 安装与设置指南

需积分: 10 139 浏览量更新于2024-07-18 收藏 583KB PDF 举报

"Oracle GoldenGate 是一款强大的数据复制软件，主要用于实现数据库间的实时数据同步。Oracle GoldenGate 支持多种操作系统平台，包括Windows和UNIX。在11g Release 1 Patch Set 1 (11.1.1.1) 版本中，提供了详细的安装和设置指南，帮助用户进行部署和配置。" Oracle GoldenGate 的安装和设置是确保数据复制服务顺利运行的关键步骤。以下是对这个过程的一些关键知识点的详细说明： 1. **环境准备**：在开始安装之前，需要确保目标系统满足Oracle GoldenGate的硬件和软件要求，包括操作系统版本、内存、磁盘空间等。同时，需要安装合适的JDK版本，因为Oracle GoldenGate依赖Java环境。 2. **下载和解压**：从Oracle官方网站获取适合操作系统的安装包，然后将其解压缩到指定目录。通常，安装包会包含多个组件，如Manager、Extract、Replicat、Trail Files等。 3. **配置Oracle GoldenGate参数**：在安装过程中，需要配置一系列参数，如 GGHOME（GoldenGate软件安装目录）、GGSCI（GoldenGate命令行接口）、USERID（数据库连接用户名）和 PASSWORD（对应的密码）等。 4. **创建GoldenGate进程**：Oracle GoldenGate的核心进程包括Extract（数据抽取）、Replicat（数据应用）和Trail Files（数据日志）。Extract从源数据库抽取数据，Replicat将这些数据应用到目标数据库，而Trail Files存储了这些数据变化的记录。 5. **数据库连接和权限**：在源和目标数据库上创建并配置GoldenGate所需的用户和角色，确保有足够的权限进行数据读取、写入和管理Trail Files。 6. **定义数据抽取和复制规则**：根据业务需求，通过DDL语句或GoldenGate的定制工具定义抽取和复制的表、列以及转换规则。 7. **启动和监控**：使用GGSCI启动各个进程，并通过其内置的监控工具检查数据复制的状态，包括数据延迟、错误报告和性能指标。 8. **故障排查和优化**：在遇到问题时，查阅Oracle GoldenGate的日志文件进行故障排除，同时可以通过调整参数和优化数据处理流程来提升性能。 9. **安全性**：确保数据在传输过程中的安全，可以采用加密技术保护Trail Files，以及通过限制网络访问来增强系统的安全性。 10. **维护和升级**：定期检查和更新Oracle GoldenGate以获取最新的补丁和功能，同时进行必要的备份和恢复策略以应对可能的系统故障。 Oracle GoldenGate的安装和设置涉及到多个环节，每个环节都需要仔细规划和实施，以确保数据复制的高效、稳定和安全。遵循官方文档和最佳实践，可以有效避免常见问题，实现高质量的数据同步。

System requirements and preinstallation instructions

Supported Oracle data types

9Oracle GoldenGate

Oracle Installation and Setup Guide

..............................................................................

● NCHAR

● NVARCHAR2

Multi-byte character types

● NCHAR and NVARCHAR2 multi-byte character data types

● Multi-byte data stored in CHAR and VARCHAR2 columns

Limitations of support

● For Oracle GoldenGate to support multi-byte character data, the source and target

databases must be identical. Transformation, filtering, and other manipulation are not

supported.

● Multi-byte characters can be used with limitations in MAP and TABLE parameter

statements such as string-based conversion functions and

WHERE clauses. The code

point for a multi-byte character must be represented within an escape sequence, for

example “

\u20ac.” For more information, see the Oracle GoldenGate Windows and

UNIX Administrator’s Guide and the Oracle GoldenGate Windows and UNIX

Reference Guide.

● Multi-byte data is supported whether the length semantics are in bytes or characters.

If the semantics setting of the source database is

BYTE and the setting of the target is

CHAR, use the Replicat parameter SOURCEDEFS in your configuration, and place a DEFGEN-

generated definitions file on the target. These steps are required to support the

difference in semantics, whether or not the source and target data definitions are

identical. Replicat refers to the definitions file to determine the upper size limit for

fixed-size character columns. For information about

SOURCEDEFS and DEFGEN, see the

Oracle GoldenGate Windows and UNIX Administrator’s Guide.

● If the database has an NLS_NCHAR_CHARACTERSET value other than AL16UTF16, use the

VARWIDTHNCHAR parameter to force NCHAR data to be written to the trail with 2-byte

length information. For more information, see the Oracle GoldenGate Windows and

UNIX Reference Guide.

Binary data types

● RAW

● LONG RAW

Date and timestamp data types

● DATE

● TIMESTAMP (see Limitations of support)

Limitations of support

● By default, only TIMESTAMP WITH TIME ZONE specified as a UTC offset is supported. To

support

TIMESTAMP WITH TIME ZONE specified as TZR (Region ID), you must use the Extract

parameter

TRANLOGOPTIONS with either the INCLUDEREGIONID or

INCLUDEREGIONIDWITHOFFSET option. Without TRANLOGOPTIONS, Extract abends on this

data type. See also Non-supported data types.

System requirements and preinstallation instructions

Supported Oracle data types

10Oracle GoldenGate

Oracle Installation and Setup Guide

..............................................................................

● TIMESTAMP WITH TIME ZONE as TZR is not supported by Oracle GoldenGate for initial loads,

for use with the

SQLEXEC feature, or for operations where the column must be fetched

from the database. In these cases, the region ID is converted to a time offset by the

Oracle database engine when the column is selected. Replicat will replicate the column

data as date and time data with a time offset value.

● Because of the way that the Oracle database normalizes TIMESTAMP WITH LOCAL TIME ZONE

to the local time zone of the database, the timestamps do not transfer correctly between

databases that are in different time zones. Timestamps will transfer correctly between

databases in the same time zone if you set the time zone of the Replicat session to the

timezone of the database. Include the following parameter statement in the Replicat

parameter file, placing it after the

USERID parameter, but before the first MAP statement:

SQLEXEC "ALTER SESSION SET TIME_ZONE = <value of dbtimezone>"

● Oracle GoldenGate does not support negative dates.

Large object data types

● CLOB

● NCLOB

● BLOB

Limitations of support

● SECUREFILE and BASICFILE are both supported.

● Store large objects out of row if possible.

● LOB capture differs between earlier and later versions of Oracle:

❍ Oracle versions earlier than 10g: In-row LOBs are captured from the redo log, but out-

of-row LOBs are fetched from the database. If a value gets deleted before a fetch

occurs, Extract writes a null to the trail. If a value gets updated before the fetch

occurs, Extract writes the updated value. To prevent these inaccuracies, try to keep

Extract latency low. The Oracle GoldenGate documentation provides guidelines for

tuning process performance.

❍ Oracle 10g and later, BASICFILE LOBs:

All BASICFILE LOBs are captured from the redo log, whether stored in-row or out-of-

row. However, Extract will continue to fetch LOBs under the following conditions,

for which it will issue a warning:

◗ Extract determines that a LOB instance is invalid.

◗ The LOB data is missing from the redo log. This can occur if the BASICFILE LOB

is created with the

no_logging option.

◗ The LOB is created with the CACHE attribute.

◗ A LOB is only partially updated. Oracle GoldenGate does not support partial

column data

. Extract assumes LOB data to be incomplete if the LOB data does

not start with a LOB reset record or does not start at the first byte and does not

end at the last byte, according to the new LOB length. Partial updates can be

generated by the following OCI calls:

OCILOBWrite(), OCILobAppend(), OCiLobCopy(),

OCILobLoadFromFile()

, OCILobTrim(), and by updated made through procedures in the

dbms_lob package.

System requirements and preinstallation instructions

Supported Oracle data types

11Oracle GoldenGate

Oracle Installation and Setup Guide

..............................................................................

◗ Extract detects an anomaly in the LOB data, such as a missing page number,

missing

END MARKER, or a mismatch between the size that was captured and the

expected size.

❍ Oracle 10g and later, SECUREFILE LOBs:

Oracle introduced SECUREFILE LOBs in 11g Release 1. SECUREFILE LOBs are captured

from the redo logs only when the update is complete and the LOB is not

transformed (the column is not compressed or encrypted or deduplicated) and

stored out-of-row. Extract will fetch

SECUREFILE LOBs under the following

circumstances:

◗ The LOB is stored in-row.

◗ The LOB is transformed either with compression or encryption.

◗ The LOB is created with the CACHE attribute.

◗ Extract determines that a LOB instance is invalid.

◗ LOB data is missing from the redo log. This can occur if the LOB is created with

any of following options:

deduplicate, no_logging, filesystem_like_logging.

◗ The LOB is updated using OCILOBWrite(), OCILobAppend(), OCiLobCopy(),

OCILobLoadFromFile(), OCILobTrim(), or through procedures in the dbms_lob package.

◗ Any other anomalies as detected by Extract in terms of a missing page number,

a missing

END MARKER, or a mismatch between the size that was captured and

the expected size.

● When changing a SECUREFILE LOB from one storage to another (such as from ENCRYPT to

DECRYPT), Oracle updates the whole table, and Extract captures those updates from the

log. Therefore, it will appear as though Oracle updated all of the data blocks that are

associated with the table. This also can happen when an

ALTER TABLE command sets a

DEFAULT value to a column that has null values.

● If CLOB columns can store binary data, set the NLS_LANG system environment variable

and the

NLS_LANGUAGE database parameter to the same value.

● When the size of a large object exceeds 4K, Oracle GoldenGate stores the data in

segments within the Oracle GoldenGate trail. The first 4K is stored in the base

segment, and the rest is stored in a series of 2K segments. Oracle GoldenGate does not

support the filtering, column mapping, or manipulation of large objects of this size. Full

Oracle GoldenGate functionality can be used for objects that are 4K or smaller.

XML data types

● XMLType is supported.

Limitations of support

● The source and target objects that contain the XML must be identical. Filtering and

manipulation are not supported. However, you can map the

XML representation of an

object to a character column by means of a

COLMAP clause in a TABLE or MAP statement.

● Oracle GoldenGate treats XMLType data as a LOB. There is no size limitation, but see

“Large object data types” on page 10 for additional support and limitations.

● A table that contains XMLType columns must have one of the following: a primary key,

column(s) with a unique constraint, or a unique index.

System requirements and preinstallation instructions

Supported Oracle data types

12Oracle GoldenGate

Oracle Installation and Setup Guide

..............................................................................

User defined types

Oracle GoldenGate supports user defined types (UDT) when the source and target objects

have the same structure. The schema names can be different.

General limitations of support

● Extract must fetch UDTs (except for object tables) from the database, so you should

configure and use a snapshot for data consistency.

● Because a UDT must be fetched, a table that contains one must have one of the

following: a primary key, column(s) with a unique constraint, or a unique index.

● Oracle GoldenGate does not support UDTs with the following embedded scalar types:

CLOB, CFILE, BFILE, or INTERVAL_YM, INTERVAL_DS, and OPAQUE (with the exception of XMLType,

which is supported).

● Object or relational tables where the key contains a UDT, or where a UDT is the only

column, are not supported.

● The RMTTASK parameter does not support user-defined types (UDT).

● CHAR and VARCHAR attributes that contain binary or unprintable characters are not

supported.

● UDTs, including values inside object columns or rows, cannot be used within filtering

criteria in

TABLE or MAP statements, or as input or output for the Oracle GoldenGate

column-conversion functions,

SQLEXEC, or other built-in data-manipulation tools.

Support is only provided for like-to-like Oracle source and targets.

● Oracle GoldenGate does not support REF types.

Limitations for collection types

● When data in a nested table is updated, the row that contains the nested table must be

updated at the same time.

● When VARRAYS and nested tables are fetched, the entire contents of the column are

fetched each time, not just the changes.

Limitations for object tables

● Oracle GoldenGate supports object tables in uni-directional and active-active

configurations for Oracle 10g and later. Object tables are captured from the redo log,

but certain data types that are fetched from the database when in regular relational

tables, such as LOBs and collection types, will also be fetched when in object tables.

Similarly, current limitations that apply to collection types when in regular tables also

apply to these types when in object tables.

● An Oracle object table can be mapped to a non-Oracle object table in a supported target

database.

● A primary key must be defined on the root-level object attributes of the object table,

and cannot include leaf-level attributes. If no key is defined, Oracle GoldenGate will

use all viable columns as a pseudo-key.

● Oracle GoldenGate does not support the replication of DDL operations for an object

table. This limitation includes the database object versioning that is associated with

ALTERs of object tables.

● Synonyms are not supported for object tables or relational tables that contain object

tables.

剩余90页未读，继续阅读

Jiangyide

粉丝: 1
资源: 9

Oracle GoldenGate 11.1.1.1 安装与设置指南

Oracle GoldenGate深入解析

Oracle GoldenGate for Sybase 安装与设置指南

Oracle GoldenGate深度解析与实战指南

Step by Step Oracle GoldenGate Installation and Configure Guide

GoldenGate Pre-installation

Oracle® GoldenGate - Oracle Installation and Setup Guide (11.1.1.1).pdf

Oracle_GoldenGate_Sybase_Installation_and_Setup_Guide

Expert Oracle GoldenGate.pdf

Oracle GoldenGate 11.1.1 patch set

goldengate的安装与配置

最新资源