CHAPTER 1

Introduction to Oracle GoldenGate

第一章

Oracle GoldenGate簡介

Oracle GoldenGate supported processing methods and databases

Oracle GoldenGate支援的處理方法和資料庫

Oracle GoldenGate enables the exchange and manipulation of data at the transaction level

among multiple, heterogeneous platforms across the enterprise 1 . Its modular architecture

gives you the flexibility to extract and replicate selected data records, transactional

changes, and changes to DDL (data definition language 2 ) across a variety of topologies.

With this flexibility, and the filtering, transformation, and custom processing features of

Oracle GoldenGate, you can support numerous business requirements:

Oracle GoldenGate支援在事務級別交換和處理資料

跨企業的多個異構平臺。其模組化架構使您可以靈活地提取和複製事務性所選資料記錄

在多種拓撲之間進行更改以及對DDL（資料定義語言2）的更改。具有這種靈活性以及DDL（資料定義語言2）的過濾，轉換和自定義處理功能

使用Oracle GoldenGate，您可以支援眾多業務需求：

● Business continuance and high availability.

● 業務連續性和高可用

● Initial load and database migration.

● 初始化載入和資料遷移

● Data integration.

● 資料整合

● Decision support and data warehousing.

● 決策支援和資料倉儲

Figure 1 Oracle GoldenGate supported topologies

圖1 Oracle GoldenGate支援的拓撲

Support for replication across different database types and topologies varies by database type. See the Oracle GoldenGate Installation and Setup Guide for your database for detailed information about supported configurations.

對不同資料庫型別和拓撲之間的複製的支援因資料庫型別而異。有關支援的配置的詳細資訊，請參見資料庫的《 Oracle GoldenGate安裝和設定指南》

2. DDL is not supported for all databases

並非所有資料庫都支援DDL

For full information about processing methodology, supported topologies and functionality, and configuration requirements, see

the Oracle GoldenGate Installation and Setup Guide for your database.

有關處理方法，支援的拓撲和功能以及配置要求的完整資訊，請參見

適用於您的資料庫的《 Oracle GoldenGate安裝和設定指南》。

Supported only as a target database. Cannot be a source database for Oracle GoldenGate extraction.

** Uses a capture module that communicates with the Oracle GoldenGate API to send change data to Oracle GoldenGate.

*** Only like-to-like configuration is supported. Data manipulation, filtering, column mapping not supported.

僅支援作為目標資料庫。不能是Oracle GoldenGate提取的源資料庫。

**使用與Oracle GoldenGate API通訊的捕獲模組將更改資料傳送到Oracle GoldenGate。

***僅支援類似的配置。不支援資料操作，過濾，列對映。

Overview of the Oracle GoldenGate architecture

Oracle GoldenGate 體系結構概述

可以出於以下目的配置Oracle GoldenGate

● 從一個資料庫中靜態提取資料記錄並載入這些記錄到另一個資料庫

●連續提取和複製事務DML操作和DDL更改（對於受支援的資料庫）以保持源資料和目標資料的一致性。

●從資料庫中提取並複製到資料庫外部的檔案

Oracle GoldenGate由以下元件組成：

●Extract

● Data pump

● Replicat

● Trails or extract files

● Checkpoints

● Manager

● Collector

Figure 2 illustrates the logical architecture of Oracle GoldenGate for initial data loads and

for the synchronization of DML and DDL operations. This is the basic configuration.

Variations of this model are recommended depending on business needs.

圖2 演示了Oracle GoldenGate用於初始資料載入以及DML和DDL操作同步的邏輯體系結構。這是基本配置。建議根據業務需要更改此模型。

Figure 2 Oracle GoldenGate logical architecture

圖二 Oracle GoldenGate邏輯架構

Overview of Extract

The Extract process runs on the source system and is the extraction (capture) mechanism

of Oracle GoldenGate. You can configure Extract in one of the following ways:

● Initial loads: For initial data loads, Extract extracts (captures) a current, static set of

data directly from their source objects.

● Change synchronization: To keep source data synchronized with another set of data,

Extract captures DML and DDL operations after the initial synchronization has taken

place.

Extract captures from a data source that can be one of the following:

● Source tables, if the run is an initial load.

● The database recovery logs or transaction logs (such as the Oracle redo logs or SQL/MX

audit trails). The actual method of capturing from the logs varies depending on the

database type.

● A third-party capture module. This method provides a communication layer that

passes data and metadata from an external API to the Extract API. The database

vendor or a third-party vendor provides the components that extract the data

operations and pass them to Extract.

When configured for change synchronization, Extract captures the DML and DDL

operations that are performed on objects in the Extract configuration. Extract stores these

operations until it receives commit records or rollbacks for the transactions that contain

them. When a rollback is received, Extract discards the operations for that transaction.

When a commit is received, Extract persists the transaction to disk in a series of files called

a trail, where it is queued for propagation to the target system. All of the operations in each

transaction are written to the trail as a sequentially organized transaction unit. This

design ensures both speed and data integrity.

NOTE Extract ignores operations on objects that are not in the Extract configuration, even

though the same transaction may also include operations on objects that are in the

Extract configuration.

Multiple Extract processes can operate on different objects at the same time. For example,

two Extract processes can extract and transmit in parallel to two Replicat processes (with

two persistence trails) to minimize target latency when the databases are large. To

differentiate among different Extract processes, you assign each one a group name (see

“Overview of groups” on page 16).

Extract概述

抽取程式在源系統上執行，是Oracle GoldenGate的抽取（捕獲）機制。可以透過以下方式之一配置提取：

● 初始載入：對於初始資料載入，直接從源物件中提取（捕獲）當前靜態資料集。

● 更改同步：為了使源資料與另一組資料同步，初始同步發生後，Extract捕獲DML和DDL操作。

從以下資料來源中抽取捕獲：

●源表（如果執行是初始載入）。

●資料庫恢復日誌或事務日誌（例如Oracle重做日誌或SQL / MX審計跟蹤）。從日誌中捕獲的實際方法取決於資料庫型別。

●第三方捕獲模組。此方法提供了一個通訊層，該通訊層將資料和後設資料從外部API傳遞到Extract API。資料庫供應商或第三方供應商提供提取資料操作並將其傳遞給Extract的元件。

為更改同步配置時，Extract捕獲對Extract配置中的物件執行的DML和DDL操作。Extract儲存這些操作，直到它接收到包含這些

操作的事務的提交記錄或回滾。當接收到回滾時，Extract將放棄該事務的操作。當接收到提交時，Extract將事務持久化到一系列

稱為trail的檔案中的磁碟，在這些檔案中，事務排隊等待傳播到目標系統。每個事務中的所有操作都作為順序組織的事務單元寫入

trail。這個設計確保速度和資料完整性。

注意即使同一事務可能還包括對在提取配置中的物件的操作，提取也將忽略不在提取配置中的物件的操作。

多個提取過程可以同時對不同的物件進行操作。例如，

兩個提取過程可以並行提取和傳輸兩個複製過程（兩個永續性跟蹤）當資料庫很大時，將目標延遲最小化。要區分不同的提取過程，請為每個過程分配一個組名（請參閱第16頁的“組概述”）。

Overview of data pumps

資料泵概述

A data pump is a secondary Extract group within the source Oracle GoldenGate

configuration. If a data pump is not used, Extract must send the captured data operations

to a remote trail on the target. In a typical configuration with a data pump, however, the

primary Extract group writes to a trail on the source system. The data pump reads this

trail and sends the data operations over the network to a remote trail on the target. The

data pump adds storage flexibility and also serves to isolate the primary Extract process

from TCP/IP activity.

資料泵是源端Oracle GoldenGate配置中的輔助抽取組

如果不使用資料泵，Extract必須將捕獲的資料操作傳送到目標上的遠端跟蹤，

然而，在典型的資料泵配置中 primary Extract group在源系統上寫入跟蹤。

資料泵讀取此跟蹤並將資料操作透過網路傳送到目標上的遠端跟蹤。

資料泵增加了儲存靈活性，還可以隔離主提取過程來自TCP / IP活動。

In general, a data pump can perform data filtering, mapping, and conversion, or it can be

configured in pass-through mode, where data is passively transferred as-is, without

manipulation. Pass-through mode increases the throughput of the data pump, because all

of the functionality that looks up object definitions is bypassed.

In most business cases, you should use a data pump. Some reasons for using a data pump

include the following:

通常，資料泵可以執行資料過濾，對映和轉換，也可以配置為直通模式，在這種模式下，資料按原樣被動傳輸，而無需進行操作。直通模式可提高資料泵的吞吐量，因為所有查詢物件定義的功能中的一部分被繞過了。在大多數業務情況下，應使用資料泵。使用資料泵的一些原因包括以下這些：

● Protection against network and target failures: In a basic Oracle GoldenGate

configuration, with only a trail on the target system, there is nowhere on the source

system to store the data operations that Extract continuously extracts into memory. If

the network or the target system becomes unavailable, Extract could run out of

memory and abend. However, with a trail and data pump on the source system,

captured data can be moved to disk, preventing the abend of the primary Extract.

When connectivity is restored, the data pump captures the data from the source trail

and sends it to the target system(s).

●防止網路和目標故障：在基本的Oracle GoldenGate配置中，只有目標系統上的一條線索，源系統上沒有任何地方可以儲存連續提取到記憶體中的資料操作。如果網路或目標系統不可用，提取可能會耗盡記憶體和異常終止。但是，透過源系統上的trail和data pump，捕獲的資料可以移動到磁碟，從而防止主提取的異常終止。當連線恢復時，data pump從源trail 捕獲資料並將其傳送到目標系統。

● You are implementing several phases of data filtering or transformation. When using

complex filtering or data transformation configurations, you can configure a data pump

to perform the first transformation either on the source system or on the target system,

or even on an intermediary system, and then use another data pump or the Replicat

group to perform the second transformation.

● 您正在實現資料過濾或轉換的幾個階段。當使用複雜的過濾或資料轉換配置時，可以配置資料泵

要在源系統或目標系統上執行第一個轉換，甚至在中間系統上，然後使用另一個資料泵或Replicat組執行第二次轉換。

● Consolidating data from many sources to a central target. When synchronizing multiple

source databases with a central target database, you can store extracted data

operations on each source system and use data pumps on each of those systems to send

the data to a trail on the target system. Dividing the storage load between the source

and target systems reduces the need for massive amounts of space on the target system

to accommodate data arriving from multiple sources.

● 將來自許多來源的資料整合到一箇中心目標。將多個源資料庫與中央目標資料庫同步時，可以在每個源系統上儲存提取的資料操作，並在每個系統上使用資料泵進行傳送資料到目標系統上的路徑。在源系統和目標系統之間分配儲存負載可以減少目標系統上需要大量空間來容納來自多個源的資料。

● Synchronizing one source with multiple targets. When sending data to multiple target

systems, you can configure data pumps on the source system for each target. If network

connectivity to any of the targets fails, data can still be sent to the other targets.

● 同步一個源和多個目標。向多個目標系統傳送資料時，可以在源系統上為每個目標配置資料泵。

如果到任何目標的網路連線失敗，資料仍可以傳送到其他目標

Overview of Replicat

複製概述

The Replicat process runs on the target system, reads the trail on that system, and then

reconstructs the DML or DDL operations and applies them to the target database. You can

configure Replicat in one of the following ways:

Replicat程式在目標系統上執行，讀取該系統上的佇列，然後重現DML或DDL操作並將其應用於目標資料庫。

您可以透過以下方式之一配置Replicat：

● Initial loads: For initial data loads, Replicat can apply a static data copy to target objects

or route it to a high-speed bulk-load utility.

●初始載入：對於初始資料載入，Replicat可以將靜態資料副本應用於目標物件或將其路由到高速大容量載入實用程式。

● Change synchronization: When configured for change synchronization, Replicat applies

the replicated source operations to the target objects using a native database interface

or ODBC, depending on the database type. To preserve data integrity, Replicat applies

the replicated operations in the same order as they were committed to the source

database.

●更改同步：當配置為更改同步時，Replicat使用本機資料庫介面或ODBC將複製的源操作應用於目標物件，具體取決於資料庫型別。為了保持資料完整性，Replicat按照提交給源資料庫的相同順序應用複製的操作。

You can use multiple Replicat processes with multiple Extract processes in parallel to

increase throughput. To preserve data integrity, each set of processes handles a different

set of objects. To differentiate among Replicat processes, you assign each one a group name

(see “Overview of groups” on page 16).

您可以將多個複製程式與多個提取程式並行使用，以提高吞吐量。為了保持資料完整性，每個程式集處理不同的物件集。為了區分複製程式，您為每個程式分配一個組名（參見第16頁的“組概述”）。

You can delay Replicat so that it waits a specific amount of time before applying the

replicated operations to the target database. A delay may be desirable, for example, to

prevent the propagation of errant SQL, to control data arrival across different time zones,

or to allow time for other planned events to occur. The length of the delay is controlled by

the DEFERAPPLYINTERVAL parameter.

您可以延遲Replicat，以便它在將複製操作應用於目標資料庫之前等待特定的時間量。延遲可能是可取的，例如，為了防止

錯誤的SQL的傳播，為了控制跨不同時區的資料到達，或者留出時間讓其他計劃的事件發生。延遲的長度由DEFERAPPLYINTERVAL

引數控制。

Overview of trails

佇列概述

To support the continuous extraction and replication of database changes, Oracle

GoldenGate stores records of the captured changes temporarily on disk in a series of files

called a trail. A trail can exist on the source system, an intermediary system, the target

system, or any combination of those systems, depending on how you configure Oracle

GoldenGate. On the local system it is known as an extract trail (or local trail). On a remote

system it is known as a remote trail.

為了支援連續提取和複製資料庫更改，Oracle GoldenGate將捕獲的更改的記錄臨時儲存在磁碟上稱為trail的一系列檔案中。路徑可以存在於源系統，中間系統，目標系統或這些系統的任意組合，具體取決於您配置Oracle GoldenGate的方式。在本地系統上，它稱為抽取路徑（或本地路徑）。在遠端系統上，它稱為遠端路徑。

By using a trail for storage, Oracle GoldenGate supports data accuracy and fault tolerance

(see “Overview of checkpoints” on page 14). The use of a trail also allows extraction and

replication activities to occur independently of each other. With these processes separated,

you have more choices for how data is processed and delivered. For example, instead of

extracting and replicating changes continuously, you could extract changes continuously

but store them in the trail for replication to the target later, whenever the target

application needs them.

透過使用trail佇列進行儲存，Oracle GoldenGate支援資料準確性和容錯性（見第14頁“檢查點概述”）。trail的使用

還允許提取和複製活動彼此獨立地進行。有了這些分離的程式，對於如何處理和傳遞資料，您有更多的選擇。例如，您可

以連續抽取變化而將它們儲存在trail中，而不是連續抽取和複製，以便以後在目標應用程式需要時複製到目標

Processes that write to, and read, a trail

寫入和讀取佇列的程式

The primary Extract and the data-pump Extract write to a trail. Only one Extract process

can write to a trail, and each Extract must be linked to a trail.

主抽取和資料泵抽取寫入佇列。只有一個提取過程可以寫入佇列，並且每個提取必須連結到一個佇列。

Processes that read the trail are:

讀取佇列的程式包括：

● Data-pump Extract: Extracts DML and DDL operations from a local trail that is linked

to a previous Extract (typically the primary Extract), performs further processing if

needed, and transfers the data to a trail that is read by the next Oracle GoldenGate

process downstream (typically Replicat, but could be another data pump if required).

●資料泵提取：從連結到上一個抽取（通常是主抽取）的本地佇列中提取DML和DDL操作，如果需要，執行進一步的處理，並將資料傳輸到下一個Oracle GoldenGate程式下游讀取的佇列（通常是複製，但如果需要，可以是另一個資料泵）。

● Replicat: Reads the trail and applies replicated DML and DDL operations to the target

database.

● Replicat：讀取佇列並將複製的DML和DDL操作應用於目標資料庫

Trail creation and maintenance

佇列建立和維護

The trail files themselves are created as needed during processing, but you specify a two-

character name for the trail when you add it to the Oracle GoldenGate configuration with

the ADD RMTTRAIL or ADD EXTTRAIL command. By default, trails are stored in the dirdat sub-

directory of the Oracle GoldenGate directory.

佇列檔案本身是在程式中根據需要建立的，但是當使用以下方式將其新增到Oracle GoldenGate配置中時，可以為該佇列指定一個兩個字元的名稱：ADD RMTTRAIL或ADD EXTTRAIL命令。預設情況下，佇列儲存在Oracle GoldenGate目錄的dirdat子目錄中。

Full trail files are aged automatically to allow processing to continue without interruption

for file maintenance. As each new file is created, it inherits the two-character trail name

appended with a unique, six-digit sequence number from 000000 through 999999 (for

example c: \ggs\dirdat\tr000001 ). When the sequence number reaches 999999, the numbering

starts over at 000000.

完整的佇列檔案會自動老化，以便在不中斷檔案維護中程式持續。在建立每個新檔案時，它將繼承兩個字元的trail名稱，

並附加一個從000000到999999的唯一六位序列號（例如c:\ ggs\dirdat\tr000001）。當序列號達到999999時從000000

重新開始。

You can create more than one trail to separate the data from different objects or

applications. You link the objects that are specified in a TABLE or SEQUENCE parameter to a

trail that is specified with an EXTTRAIL or RMTTRAIL parameter in the Extract parameter file.

Aged trail files can be purged by using the Manager parameter PURGEOLDEXTRACTS .

To maximize throughput, and to minimize I/O load on the system, extracted data is sent

into and out of a trail in large blocks. Transactional order is preserved. By default, Oracle

GoldenGate writes data to the trail in canonical format, a proprietary format which allows

it to be exchanged rapidly and accurately among heterogeneous databases. However, data

can be written in other formats that are compatible with different applications.

For additional information about the trail and the records it contains, see Appendix 2 on

page 562.

您可以建立多條佇列以將資料從不同的物件或應用程式中分離出來。將表或序列引數中指定的物件連結到提取引數檔案中

使用EXTTRAIL或RMTTRAIL引數指定的軌跡。可以使用管理器引數PURGEOLDEXTRACTS清除過時的佇列檔案。

為了最大化吞吐量和最小化系統上的I/O負載，提取的資料以大資料塊的形式傳送到和傳送出一條路徑。事務順序被保留。

預設情況下， Oracle GoldenGate以規範格式將資料寫入trail，這是一種專有格式，允許在異構資料庫之間快速、準確地交

換資料。但是，資料可以用與不同應用程式相容的其他格式編寫。有關跟蹤及其包含的記錄的更多資訊，請參閱第562頁的

附錄2。

Overview of extract files

抽取檔案概述

In some configurations, Oracle GoldenGate stores extracted data in an extract file instead

of a trail. The extract file can be a single file, or it can be configured to roll over into

multiple files in anticipation of limitations on file size that are imposed by the operating

system. In this sense, it is similar to a trail, except that checkpoints are not recorded. The

file or files are created automatically during the run. The same versioning features that

apply to trails also apply to extract files.

在某些配置中，Oracle GoldenGate將提取的資料儲存在抽取檔案中而不是佇列中。提取檔案可以是單個檔案，也可以

配置為在預期作業系統會限制檔案大小的情況下滾動成多個檔案。從這個意義上講，它類似於佇列，不同之處在於不記錄

檢查點。一個或多個檔案在執行期間自動建立。適用於佇列的相同版本控制功能也適用於提取檔案。

Overview of checkpoints

檢查點概述

Checkpoints store the current read and write positions of a process to disk for recovery

purposes. Checkpoints ensure that data changes that are marked for synchronization

actually are captured by Extract and applied to the target by Replicat, and they prevent

redundant processing. They provide fault tolerance by preventing the loss of data should

the system, the network, or an Oracle GoldenGate process need to be restarted. For

complex synchronization configurations, checkpoints enable multiple Extract or Replicat

processes to read from the same set of trails.

Checkpoints work with inter-process acknowledgments to prevent messages from being

lost in the network. Oracle GoldenGate has a proprietary guaranteed-message delivery

technology.

檢查點將程式的當前讀寫位置儲存到磁碟以進行恢復目的。檢查點確保標記為同步的資料更改

實際上是由Extract捕獲的，並由Replicat應用於目標的，它們可以防止冗餘處理。它們透過防

止資料丟失來提供容錯能力。系統，網路或Oracle GoldenGate程式需要重新啟動。對於

複雜的同步配置，檢查點可啟用多個取抽或複製從同一組記錄讀取的過程。檢查點與程式間確認

一起使用，以防止訊息被髮送迷失在網路中。 Oracle GoldenGate具有專有的保證訊息交付技術。

Extract creates checkpoints for its positions in the data source and in the trail. Because

Extract only captures committed transactions, it must keep track of operations in all open

transactions, in the event that any of them are committed. This requires Extract to record

a checkpoint where it is currently reading in a transaction log, plus the position of the start

of the oldest open transaction, which can be in the current or any preceding log.

Extract為其在資料來源和佇列中的位置建立檢查點。因為 Extract只捕獲提交的事務，它必須跟蹤所有開啟的操作

事務，如果其中任何一個已提交。這需要摘錄來記錄當前在事務日誌中讀取的檢查點，加上開始位置最早的開啟

事務，可以在當前日誌或任何前面的日誌中。

To control the amount of transaction log that must be re-processed after an outage, Extract

persists the current state and data of processing to disk at specific intervals, including the

state and data (if any) of long-running transactions. If Extract stops after one of these

intervals, it can recover from a position within the previous interval or at the last

checkpoint, instead of having to return to the log position where the oldest open long-

running transaction first appeared. For more information, see the BR parameter in the

Oracle GoldenGate Windows and UNIX Reference Guide.

要控制中斷後必須重新處理的事務日誌量，請抽取以特定的間隔將當前處理狀態和資料持久化到磁碟，包括

長期執行事務的狀態和資料（如果有）。如果提取在其中一個之後停止間隔，它可以從上一個間隔或最後一個

間隔內的位置恢復檢查點，而不必返回到最早開啟long的日誌位置- 首次出現執行事務。有關詳細資訊，請參見

《Oracle GoldenGate Windows和UNIX參考指南》。

Replicat creates checkpoints for its position in the trail. Replicat stores its checkpoints in

a checkpoint table in the target database to couple the commit of its transaction with its

position in the trail file. The checkpoint table guarantees consistency after a database

recovery by ensuring that a transaction will only be applied once, even if there is a failure

of the Replicat process or the database process. For reporting purposes, Replicat also has

a checkpoint file on disk in the dirchk sub-directory of the Oracle GoldenGate directory.

Replicat為它在trail中的位置建立檢查點。Replicat將其檢查點儲存在目標資料庫中的檢查點表，用於將其

事務的提交與在軌跡檔案中的位置。檢查點表保證資料庫之後的一致性透過確保事務只應用一次（即使出現

故障）來恢復複製程式或資料庫程式的。出於報告的目的，Replicat還有磁碟上Oracle GoldenGate目錄的

dirchk子目錄中的檢查點檔案。

Checkpoints are not required for non-continuous types of configurations that can be re-run

from a start point if needed, such as initial loads.

對於可以重新執行的非連續型別的配置，不需要檢查點如果需要，從起點開始，例如初始負載。

Overview of Manager

manager概述

Manager is the control process of Oracle GoldenGate. Manager must be running on each

system in the Oracle GoldenGate configuration before Extract or Replicat can be started,

and Manager must remain running while those processes are running so that resource

management functions are performed. Manager performs the following functions:

Manager是Oracle GoldenGate的控制過程。必須在Oracle GoldenGate配置中的每個系統上執行管理器，然後才能

啟動提取或複製，當這些程式執行時，管理器必須保持執行，以便執行管理功能。管理器執行以下功能：

● Start Oracle GoldenGate processes

● Start dynamic processes

● Maintain port numbers for processes

● Perform trail management

● Create event, error, and threshold reports

One Manager process can control many Extract or Replicat processes. On Windows

systems, Manager can run as a service. For more information about the Manager process

and configuring TCP/IP connections, see Chapter 3.

一個管理器程式可以控制多個提取或複製程式。在Windows系統上，Manager可以作為服務執行。有關管理器程式和配置TCP/IP連線的更多資訊，請參閱第3章。

Overview of Collector

Collector概述

Collector is a process that runs in the background on the target system when continuous,

online change synchronization is active. Collector does the following:

收集器是一個程式，當連續的聯機更改同步處於活動狀態時，該程式在目標系統的後臺執行。收集器執行以下操作：

● Upon a connection request from a remote Extract to Manger, scan and bind to an

available port and then send the port number to Manager for assignment to the requesting Extract process.

●從遠端提取到管理器的連線請求後，掃描並繫結到可用埠，然後將埠號傳送給管理器，以便分配到請求提取過程。

● Receive extracted database changes that are sent by Extract and write them to a trail

file. Manager starts Collector automatically when a network connection is required, so

Oracle GoldenGate users do not interact with it. Collector can receive information from

only one Extract process, so there is one Collector for each Extract that you use.

Collector terminates when the associated Extract process terminates.

接收透過提取傳送的提取資料庫更改，並將其寫入跟蹤檔案。當需要網路連線時，Manager會自動啟動收集器，因此

Oracle GoldenGate使用者不會與其互動。收集器可以從僅一個抽取過程程式接收資訊，因此您使用的每個提取都有一個

收集器。當關聯的提取程式終止時，收集器終止。

NOTE Collector can be run manually, if needed. This is known as a static Collector (as

opposed to the regular, dynamic Collector). Several Extract processes can share

one static Collector; however, a one-to-one ratio is optimal. A static Collector can

be used to ensure that the process runs on a specific port. For more information

about the static Collector, see the Oracle GoldenGate Windows and UNIX

Reference Guide. For more information about how Manager assigns ports, see

Chapter 3.

如果需要，可以手動執行便箋收集器。這稱為靜態收集器（與常規的動態收集器相反）。

多個提取程式可以共享一個靜態收集器；但是，一對一的比率是最佳的。靜電收集器

用於確保程式在特定埠上執行。有關靜態收集器的詳細資訊，請參閱《Oracle GoldenGate Windows和UNIX參考指南》。有關Manager如何分配埠的詳細資訊，請參閱

第三章。

By default, Extract initiates TCP/IP connections from the source system to Collector on the

target, but Oracle GoldenGate can be configured so that Collector initiates connections

from the target. Initiating connections from the target might be required if, for example,

the target is in a trusted network zone, but the source is in a less trusted zone. For

information about this configuration, see page 136.

預設情況下，“提取”會啟動從源系統到目標上收集器的TCP/IP連線，但可以配置Oracle GoldenGate，以便收集器從

目標啟動連線。可能需要從目標啟動連線，例如，目標位於受信任的網路區域，但源位於不受信任的區域。為了有關此

配置的資訊，請參閱第136頁。

Overview of process types

程式型別概述

Depending on the requirement, Oracle GoldenGate can be configured with the following processing types.

根據需要，Oracle GoldenGate可以配置以下處理型別。

● An online Extract or Replicat process runs until stopped by a user. Online processes

maintain recovery checkpoints in the trail so that processing can resume after

interruptions. You use online processes to continuously extract and replicate DML and

DDL operations (where supported) to keep source and target objects synchronized. The

EXTRACT and REPLICAT parameters apply to this process type.

● A source-is-table Extract process extracts a current set of static data directly from the

source objects in preparation for an initial load to another database. This process type

does not use checkpoints. The SOURCEISTABLE parameter applies to this process type.

● A special-run Replicat process applies data within known begin and end points. You

use a special Replicat run for initial data loads, and it also can be used with an online

Extract to apply data changes from the trail in batches, such as once a day rather than

continuously. This process type does not maintain checkpoints, because the run can be

started over with the same begin and end points. The SPECIALRUN parameter applies to

this process type.

● A remote task is a special type of initial-load process in which Extract communicates

directly with Replicat over TCP/IP. Neither a Collector process nor temporary disk

storage in a trail or file is used. The task is defined in the Extract parameter file with

the RMTTASK parameter.

●線上提取或複製過程一直執行到使用者停止為止。聯機程式在跟蹤中維護恢復檢查點，以便在中斷後恢復處理。您可以使用聯機過程連續提取和複製DML和

DDL操作（如果支援）以保持源物件和目標物件同步。EXTRACT和REPLICAT引數應用於此程式型別。

●source-is-table提取過程直接從源物件中提取一組當前靜態資料，以準備初始載入到另一個資料庫。此程式型別不使用檢查點。SOURCEISTABLE引數應用於此程式型別。

●特殊執行復制過程在已知起點和終點內應用資料。您可以使用一個特殊的Replicat run來載入初始資料，它還可以與一個聯機提取一起使用，以成批應用來自trail的資料更改，

例如每天一次，而不是連續不斷地。此程式型別不維護檢查點，因為可以使用相同的起點和終點重新開始執行。SPECIALRUN引數適用於此程式型別。

●遠端任務是一種特殊型別的初始載入過程，其中Extract與直接透過TCP/IP複製。不使用收集器程式或跟蹤或檔案中的臨時磁碟儲存。任務在提取引數檔案中用RMTTASK引數定義。

Overview of groups

groups概述

To differentiate among multiple Extract or Replicat processes on a system, you define

processing groups. For example, to replicate different sets of data in parallel, you would

create two Replicat groups.

要區分系統上的多個提取或複製程式，請定義處理組。例如，要並行複製不同的資料集，可以建立兩個複製組。

A processing group consists of a process (either Extract or Replicat), its parameter file, its

checkpoint file, and any other files associated with the process. For Replicat, a group also

includes the associated checkpoint table.

一個程式組由程式（Extract或Replicat）、其引數檔案、檢查點檔案和與該程式關聯的任何其他檔案組成。對於Replicat，組還包含關聯的檢查點表。

You define groups by using the ADD EXTRACT and ADD REPLICAT commands in the Oracle

GoldenGate command interface, GGSCI. For permissible group names, see those

commands in the Oracle GoldenGate Windows and UNIX Reference Guide.

您可以使用OracleGoldenGate命令介面中的ADD EXTRACT和ADD REPLICAT命令來定義組。有關允許的組名，請參閱《Oracle GoldenGate Windows和UNIX參考指南》中的這些命令。

All files and checkpoints relating to a group share the name that is assigned to the group

itself. Any time that you issue a command to control or view processing, you supply a group

name or multiple group names by means of a wildcard.

與組相關的所有檔案和檢查點共享分配給組本身的名稱。在發出控制或檢視處理的命令時，可以透過萬用字元提供組名或多個組名

Overview of the Commit Sequence Number (CSN)

提交序列號（CSN）概述

使用Oracle GoldenGate時，可能需要引用提交序列號或CSN。CSN是Oracle GoldenGate為維護事務一致性和資料完整性而

構造的用於標識事務的識別符號。它唯一標識事務提交到資料庫的時間點。可以要求CSN在事務日誌中定位Extract，以重新定位

Replicat 在佇列上，或為了其他目的。它由一些轉換函式返回，並且包括在報告和某些GGSCI輸出中。有關CSN和每個資料庫的

CSN值列表的更多資訊，請參見附錄第559頁。

Oracle GoldenGate 11g官方文件Administrator’s Guide續一

相關文章