OracleGoldenGate11g官方文檔Administrator’sGuide續(xù)一
CHAPTER 1
尉氏網(wǎng)站制作公司哪家好，找成都創(chuàng)新互聯(lián)公司！從網(wǎng)頁設(shè)計、網(wǎng)站建設(shè)、微信開發(fā)、APP開發(fā)、成都響應(yīng)式網(wǎng)站建設(shè)等網(wǎng)站項目制作，到程序開發(fā)，運營維護(hù)。成都創(chuàng)新互聯(lián)公司于2013年創(chuàng)立到現(xiàn)在10年的時間，我們擁有了豐富的建站經(jīng)驗和運維經(jīng)驗，來保證我們的工作的順利進(jìn)行。專注于網(wǎng)站建設(shè)就選成都創(chuàng)新互聯(lián)公司。
Introduction to Oracle GoldenGate
第一章
Oracle GoldenGate簡介
Oracle GoldenGate supported processing methods and databases
Oracle GoldenGate支持的處理方法和數(shù)據(jù)庫
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支持在事務(wù)級別交換和處理數(shù)據(jù)
跨企業(yè)的多個異構(gòu)平臺。其模塊化架構(gòu)使您可以靈活地提取和復(fù)制事務(wù)性所選數(shù)據(jù)記錄
在多種拓?fù)渲g進(jìn)行更改以及對DDL（數(shù)據(jù)定義語言2）的更改。具有這種靈活性以及DDL（數(shù)據(jù)定義語言2）的過濾，轉(zhuǎn)換和自定義處理功能
使用Oracle GoldenGate，您可以支持眾多業(yè)務(wù)需求：
● Business continuance and high availability.
● 業(yè)務(wù)連續(xù)性和高可用
● Initial load and database migration.
● 初始化加載和數(shù)據(jù)遷移
● Data integration.
● 數(shù)據(jù)集成
● Decision support and data warehousing.
● 決策支持和數(shù)據(jù)倉庫
Figure 1 Oracle GoldenGate supported topologies
圖1 Oracle GoldenGate支持的拓?fù)?/p>
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.
對不同數(shù)據(jù)庫類型和拓?fù)渲g的復(fù)制的支持因數(shù)據(jù)庫類型而異。有關(guān)支持的配置的詳細(xì)信息，請參見數(shù)據(jù)庫的《 Oracle GoldenGate安裝和設(shè)置指南》
2. DDL is not supported for all databases
并非所有數(shù)據(jù)庫都支持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.
有關(guān)處理方法，支持的拓?fù)浜凸δ芤约芭渲靡蟮耐暾畔ⅲ垍⒁?/p>
適用于您的數(shù)據(jù)庫的《 Oracle GoldenGate安裝和設(shè)置指南》。
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.
僅支持作為目標(biāo)數(shù)據(jù)庫。不能是Oracle GoldenGate提取的源數(shù)據(jù)庫。
**使用與Oracle GoldenGate API通信的捕獲模塊將更改數(shù)據(jù)發(fā)送到Oracle GoldenGate。
***僅支持類似的配置。不支持?jǐn)?shù)據(jù)操作，過濾，列映射。
Overview of the Oracle GoldenGate architecture
Oracle GoldenGate 體系結(jié)構(gòu)概述
可以出于以下目的配置Oracle GoldenGate
● 從一個數(shù)據(jù)庫中靜態(tài)提取數(shù)據(jù)記錄并加載這些記錄到另一個數(shù)據(jù)庫
●連續(xù)提取和復(fù)制事務(wù)DML操作和DDL更改（對于受支持的數(shù)據(jù)庫）以保持源數(shù)據(jù)和目標(biāo)數(shù)據(jù)的一致性。
●從數(shù)據(jù)庫中提取并復(fù)制到數(shù)據(jù)庫外部的文件
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用于初始數(shù)據(jù)加載以及DML和DDL操作同步的邏輯體系結(jié)構(gòu)。這是基本配置。建議根據(jù)業(yè)務(wù)需要更改此模型。
Figure 2 Oracle GoldenGate logical architecture
圖二 Oracle GoldenGate邏輯架構(gòu)
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概述
抽取進(jìn)程在源系統(tǒng)上運行，是Oracle GoldenGate的抽取（捕獲）機(jī)制?？梢酝ㄟ^以下方式之一配置提?。?/p>
● 初始加載：對于初始數(shù)據(jù)加載，直接從源對象中提?。ú东@）當(dāng)前靜態(tài)數(shù)據(jù)集。
● 更改同步：為了使源數(shù)據(jù)與另一組數(shù)據(jù)同步，初始同步發(fā)生后，Extract捕獲DML和DDL操作。
從以下數(shù)據(jù)源中抽取捕獲：
●源表（如果運行是初始加載）。
●數(shù)據(jù)庫恢復(fù)日志或事務(wù)日志（例如Oracle重做日志或SQL / MX審計跟蹤）。從日志中捕獲的實際方法取決于數(shù)據(jù)庫類型。
●第三方捕獲模塊。此方法提供了一個通信層，該通信層將數(shù)據(jù)和元數(shù)據(jù)從外部API傳遞到Extract API。數(shù)據(jù)庫供應(yīng)商或第三方供應(yīng)商提供提取數(shù)據(jù)操作并將其傳遞給Extract的組件。
為更改同步配置時，Extract捕獲對Extract配置中的對象執(zhí)行的DML和DDL操作。Extract存儲這些操作，直到它接收到包含這些
操作的事務(wù)的提交記錄或回滾。當(dāng)接收到回滾時，Extract將放棄該事務(wù)的操作。 當(dāng)接收到提交時，Extract將事務(wù)持久化到一系列
稱為trail的文件中的磁盤，在這些文件中，事務(wù)排隊等待傳播到目標(biāo)系統(tǒng)。每個事務(wù)中的所有操作都作為順序組織的事務(wù)單元寫入
trail。這個 設(shè)計確保速度和數(shù)據(jù)完整性。
注意即使同一事務(wù)可能還包括對在提取配置中的對象的操作，提取也將忽略不在提取配置中的對象的操作。
多個提取過程可以同時對不同的對象進(jìn)行操作。例如，
兩個提取過程可以并行提取和傳輸兩個復(fù)制過程（兩個持久性跟蹤）當(dāng)數(shù)據(jù)庫很大時，將目標(biāo)延遲最小化。要區(qū)分不同的提取過程，請為每個過程分配一個組名（請參閱第16頁的“組概述”）。
Overview of data pumps
數(shù)據(jù)泵概述
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.
數(shù)據(jù)泵是源端Oracle GoldenGate配置中的輔助抽取組
如果不使用數(shù)據(jù)泵，Extract必須將捕獲的數(shù)據(jù)操作發(fā)送到目標(biāo)上的遠(yuǎn)程跟蹤，
然而，在典型的數(shù)據(jù)泵配置中 primary Extract group在源系統(tǒng)上寫入跟蹤。
數(shù)據(jù)泵讀取此跟蹤并將數(shù)據(jù)操作通過網(wǎng)絡(luò)發(fā)送到目標(biāo)上的遠(yuǎn)程跟蹤。
數(shù)據(jù)泵增加了存儲靈活性，還可以隔離主提取過程來自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:
通常，數(shù)據(jù)泵可以執(zhí)行數(shù)據(jù)過濾，映射和轉(zhuǎn)換，也可以配置為直通模式，在這種模式下，數(shù)據(jù)按原樣被動傳輸，而無需進(jìn)行操作。直通模式可提高數(shù)據(jù)泵的吞吐量，因為所有查找對象定義的功能中的一部分被繞過了。在大多數(shù)業(yè)務(wù)情況下，應(yīng)使用數(shù)據(jù)泵。使用數(shù)據(jù)泵的一些原因包括以下這些：
● 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).
●防止網(wǎng)絡(luò)和目標(biāo)故障：在基本的Oracle GoldenGate配置中，只有目標(biāo)系統(tǒng)上的一條線索，源系統(tǒng)上沒有任何地方可以存儲連續(xù)提取到內(nèi)存中的數(shù)據(jù)操作。如果網(wǎng)絡(luò)或目標(biāo)系統(tǒng)不可用，提取可能會耗盡內(nèi)存和異常終止。但是，通過源系統(tǒng)上的trail和data pump，捕獲的數(shù)據(jù)可以移動到磁盤，從而防止主提取的異常終止。當(dāng)連接恢復(fù)時，data pump從源trail 捕獲數(shù)據(jù)并將其發(fā)送到目標(biāo)系統(tǒng)。
● 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.
● 您正在實現(xiàn)數(shù)據(jù)過濾或轉(zhuǎn)換的幾個階段。當(dāng)使用復(fù)雜的過濾或數(shù)據(jù)轉(zhuǎn)換配置時，可以配置數(shù)據(jù)泵
要在源系統(tǒng)或目標(biāo)系統(tǒng)上執(zhí)行第一個轉(zhuǎn)換， 甚至在中間系統(tǒng)上，然后使用另一個數(shù)據(jù)泵或Replicat組執(zhí)行第二次轉(zhuǎn)換。
● 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.
● 將來自許多來源的數(shù)據(jù)整合到一個中心目標(biāo)。將多個源數(shù)據(jù)庫與中央目標(biāo)數(shù)據(jù)庫同步時，可以在每個源系統(tǒng)上存儲提取的數(shù)據(jù)操作，并在每個系統(tǒng)上使用數(shù)據(jù)泵進(jìn)行發(fā)送數(shù)據(jù)到目標(biāo)系統(tǒng)上的路徑。在源系統(tǒng)和目標(biāo)系統(tǒng)之間分配存儲負(fù)載可以減少目標(biāo)系統(tǒng)上需要大量空間來容納來自多個源的數(shù)據(jù)。
● 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.
● 同步一個源和多個目標(biāo)。向多個目標(biāo)系統(tǒng)發(fā)送數(shù)據(jù)時，可以在源系統(tǒng)上為每個目標(biāo)配置數(shù)據(jù)泵。
如果到任何目標(biāo)的網(wǎng)絡(luò)連接失敗，數(shù)據(jù)仍可以發(fā)送到其他目標(biāo)
Overview of Replicat
復(fù)制概述
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進(jìn)程在目標(biāo)系統(tǒng)上運行，讀取該系統(tǒng)上的隊列，然后重現(xiàn)DML或DDL操作并將其應(yīng)用于目標(biāo)數(shù)據(jù)庫。
您可以通過以下方式之一配置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.
●初始加載：對于初始數(shù)據(jù)加載，Replicat可以將靜態(tài)數(shù)據(jù)副本應(yīng)用于目標(biāo)對象或?qū)⑵渎酚傻礁咚俅笕萘考虞d實用程序。
● 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.
●更改同步：當(dāng)配置為更改同步時，Replicat使用本機(jī)數(shù)據(jù)庫接口或ODBC將復(fù)制的源操作應(yīng)用于目標(biāo)對象，具體取決于數(shù)據(jù)庫類型。為了保持?jǐn)?shù)據(jù)完整性，Replicat按照提交給源數(shù)據(jù)庫的相同順序應(yīng)用復(fù)制的操作。
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).
您可以將多個復(fù)制進(jìn)程與多個提取進(jìn)程并行使用，以提高吞吐量。為了保持?jǐn)?shù)據(jù)完整性，每個進(jìn)程集處理不同的對象集。為了區(qū)分復(fù)制進(jìn)程，您為每個進(jìn)程分配一個組名（參見第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，以便它在將復(fù)制操作應(yīng)用于目標(biāo)數(shù)據(jù)庫之前等待特定的時間量。延遲可能是可取的，例如，為了防止
錯誤的SQL的傳播，為了控制跨不同時區(qū)的數(shù)據(jù)到達(dá)， 或者留出時間讓其他計劃的事件發(fā)生。延遲的長度由DEFERAPPLYINTERVAL
參數(shù)控制。
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.
為了支持連續(xù)提取和復(fù)制數(shù)據(jù)庫更改，Oracle GoldenGate將捕獲的更改的記錄臨時存儲在磁盤上稱為trail的一系列文件中。路徑可以存在于源系統(tǒng)，中間系統(tǒng)，目標(biāo)系統(tǒng)或這些系統(tǒng)的任意組合，具體取決于您配置Oracle GoldenGate的方式。在本地系統(tǒng)上，它稱為抽取路徑（或本地路徑）。在遠(yuǎn)程系統(tǒng)上，它稱為遠(yuǎn)程路徑。
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隊列進(jìn)行存儲，Oracle GoldenGate支持?jǐn)?shù)據(jù)準(zhǔn)確性和容錯性 （見第14頁“檢查點概述”）。trail的使用
還允許提取和復(fù)制活動彼此獨立地進(jìn)行。有了這些分離的進(jìn)程， 對于如何處理和傳遞數(shù)據(jù)，您有更多的選擇。例如，您可
以連續(xù)抽取變化而將它們存儲在trail中，而不是連續(xù)抽取和復(fù)制 ，以便以后在目標(biāo)應(yīng)用程序需要時復(fù)制到目標(biāo)
Processes that write to, and read, a trail
寫入和讀取隊列的進(jìn)程
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.
主抽取和數(shù)據(jù)泵抽取寫入隊列。只有一個提取過程可以寫入隊列，并且每個提取必須鏈接到一個隊列。
Processes that read the trail are:
讀取隊列的進(jìn)程包括：
● 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).
●數(shù)據(jù)泵提取：從鏈接到上一個抽?。ㄍǔＪ侵鞒槿。┑谋镜仃犃兄刑崛ML和DDL操作，如果需要，執(zhí)行進(jìn)一步的處理，并將數(shù)據(jù)傳輸?shù)较乱粋€Oracle GoldenGate進(jìn)程下游讀取的隊列（通常是復(fù)制，但如果需要，可以是另一個數(shù)據(jù)泵）。
● Replicat: Reads the trail and applies replicated DML and DDL operations to the target
database.
● Replicat：讀取隊列并將復(fù)制的DML和DDL操作應(yīng)用于目標(biāo)數(shù)據(jù)庫
Trail creation and maintenance
隊列創(chuàng)建和維護(hù)
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.
隊列文件本身是在進(jìn)程中根據(jù)需要創(chuàng)建的，但是當(dāng)使用以下方式將其添加到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.
完整的隊列文件會自動老化，以便在不中斷 文件維護(hù)中進(jìn)程持續(xù)。在創(chuàng)建每個新文件時，它將繼承兩個字符的trail名稱，
并附加一個從000000到999999的唯一六位序列號（例如c:\ ggs\dirdat\tr000001）。當(dāng)序列號達(dá)到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.
您可以創(chuàng)建多條隊列以將數(shù)據(jù)從不同的對象或應(yīng)用程序中分離出來。將表或序列參數(shù)中指定的對象鏈接到提取參數(shù)文件中
使用EXTTRAIL或RMTTRAIL參數(shù)指定的軌跡。 可以使用管理器參數(shù)PURGEOLDEXTRACTS清除過時的隊列文件。
為了最大化吞吐量和最小化系統(tǒng)上的I/O負(fù)載，提取的數(shù)據(jù)以大數(shù)據(jù)塊的形式發(fā)送到和發(fā)送出一條路徑。事務(wù)順序被保留。
默認(rèn)情況下， Oracle GoldenGate以規(guī)范格式將數(shù)據(jù)寫入trail，這是一種專有格式，允許在異構(gòu)數(shù)據(jù)庫之間快速、準(zhǔn)確地交
換數(shù)據(jù)。但是，數(shù)據(jù) 可以用與不同應(yīng)用程序兼容的其他格式編寫。 有關(guān)跟蹤及其包含的記錄的更多信息，請參閱第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將提取的數(shù)據(jù)存儲在抽取文件中而不是隊列中。提取文件可以是單個文件，也可以
配置為在預(yù)期操作系統(tǒng)會限制文件大小的情況下滾動成多個文件。從這個意義上講，它類似于隊列，不同之處在于不記錄
檢查點。一個或多個文件在運行期間自動創(chuàng)建。適用于隊列的相同版本控制功能也適用于提取文件。
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.
檢查點將進(jìn)程的當(dāng)前讀寫位置存儲到磁盤以進(jìn)行恢復(fù)目的。檢查點確保標(biāo)記為同步的數(shù)據(jù)更改
實際上是由Extract捕獲的，并由Replicat應(yīng)用于目標(biāo)的，它們可以防止冗余處理。它們通過防
止數(shù)據(jù)丟失來提供容錯能力。系統(tǒng)，網(wǎng)絡(luò)或Oracle GoldenGate進(jìn)程需要重新啟動。對于
復(fù)雜的同步配置，檢查點可啟用多個取抽或復(fù)制從同一組記錄讀取的過程。檢查點與進(jìn)程間確認(rèn)
一起使用，以防止消息被發(fā)送迷失在網(wǎng)絡(luò)中。 Oracle GoldenGate具有專有的保證消息交付技術(shù)。
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為其在數(shù)據(jù)源和隊列中的位置創(chuàng)建檢查點。因為 Extract只捕獲提交的事務(wù)，它必須跟蹤所有打開的操作
事務(wù)，如果其中任何一個已提交。這需要摘錄來記錄 當(dāng)前在事務(wù)日志中讀取的檢查點，加上開始位置 最早的打開
事務(wù)，可以在當(dāng)前日志或任何前面的日志中。
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.
要控制中斷后必須重新處理的事務(wù)日志量，請抽取 以特定的間隔將當(dāng)前處理狀態(tài)和數(shù)據(jù)持久化到磁盤，包括
長期運行事務(wù)的狀態(tài)和數(shù)據(jù)（如果有）。如果提取在其中一個之后停止 間隔，它可以從上一個間隔或最后一個
間隔內(nèi)的位置恢復(fù) 檢查點，而不必返回到最早打開long的日志位置- 首次出現(xiàn)運行事務(wù)。有關(guān)詳細(xì)信息，請參見
《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中的位置創(chuàng)建檢查點。Replicat將其檢查點存儲在 目標(biāo)數(shù)據(jù)庫中的檢查點表，用于將其
事務(wù)的提交與 在軌跡文件中的位置。檢查點表保證數(shù)據(jù)庫之后的一致性 通過確保事務(wù)只應(yīng)用一次（即使出現(xiàn)
故障）來恢復(fù) 復(fù)制進(jìn)程或數(shù)據(jù)庫進(jìn)程的。出于報告的目的，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.
對于可以重新運行的非連續(xù)類型的配置，不需要檢查點 如果需要，從起點開始，例如初始負(fù)載。
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配置中的每個系統(tǒng)上運行管理器，然后才能
啟動提取或復(fù)制， 當(dāng)這些進(jìn)程運行時，管理器必須保持運行，以便 執(zhí)行管理功能。管理器執(zhí)行以下功能：
● 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.
一個管理器進(jìn)程可以控制多個提取或復(fù)制進(jìn)程。在Windows系統(tǒng)上，Manager可以作為服務(wù)運行。有關(guān)管理器進(jìn)程和配置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:
收集器是一個進(jìn)程，當(dāng)連續(xù)的聯(lián)機(jī)更改同步處于活動狀態(tài)時，該進(jìn)程在目標(biāo)系統(tǒng)的后臺運行。收集器執(zhí)行以下操作：
● 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.
●從遠(yuǎn)程提取到管理器的連接請求后，掃描并綁定到可用端口，然后將端口號發(fā)送給管理器，以便分配到請求提取過程。
● 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.
接收通過提取發(fā)送的提取數(shù)據(jù)庫更改，并將其寫入跟蹤文件。當(dāng)需要網(wǎng)絡(luò)連接時，Manager會自動啟動收集器，因此
Oracle GoldenGate用戶不會與其交互。收集器可以從僅 一個抽取過程進(jìn)程接收信息，因此您使用的每個提取都有一個
收集器。 當(dāng)關(guān)聯(lián)的提取進(jìn)程終止時，收集器終止。
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.
如果需要，可以手動運行便箋收集器。這稱為靜態(tài)收集器（與常規(guī)的動態(tài)收集器相反）。
多個提取進(jìn)程可以共享一個靜態(tài)收集器；但是，一對一的比率是最佳的。靜電收集器
用于確保進(jìn)程在特定端口上運行。有關(guān)靜態(tài)收集器的詳細(xì)信息，請參閱《Oracle GoldenGate Windows和UNIX參考指南》。有關(guān)Manager如何分配端口的詳細(xì)信息，請參閱
第三章。
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.
默認(rèn)情況下，“提取”會啟動從源系統(tǒng)到目標(biāo)上收集器的TCP/IP連接，但可以配置Oracle GoldenGate，以便收集器從
目標(biāo)啟動連接?？赡苄枰獜哪繕?biāo)啟動連接，例如， 目標(biāo)位于受信任的網(wǎng)絡(luò)區(qū)域，但源位于不受信任的區(qū)域。為了 有關(guān)此
配置的信息，請參閱第136頁。
Overview of process types
進(jìn)程類型概述
Depending on the requirement, Oracle GoldenGate can be configured with the following processing types.
根據(jù)需要，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.
●在線提取或復(fù)制過程一直運行到用戶停止為止。聯(lián)機(jī)進(jìn)程在跟蹤中維護(hù)恢復(fù)檢查點，以便在中斷后恢復(fù)處理。您可以使用聯(lián)機(jī)過程連續(xù)提取和復(fù)制DML和
DDL操作（如果支持）以保持源對象和目標(biāo)對象同步。EXTRACT和REPLICAT參數(shù)應(yīng)用于此進(jìn)程類型。
●source-is-table提取過程直接從源對象中提取一組當(dāng)前靜態(tài)數(shù)據(jù)，以準(zhǔn)備初始加載到另一個數(shù)據(jù)庫。此進(jìn)程類型不使用檢查點。SOURCEISTABLE參數(shù)應(yīng)用于此進(jìn)程類型。
●特殊運行復(fù)制過程在已知起點和終點內(nèi)應(yīng)用數(shù)據(jù)。您可以使用一個特殊的Replicat run來加載初始數(shù)據(jù)，它還可以與一個聯(lián)機(jī)提取一起使用，以成批應(yīng)用來自trail的數(shù)據(jù)更改，
例如每天一次，而不是 連續(xù)不斷地。此進(jìn)程類型不維護(hù)檢查點，因為可以使用相同的起點和終點重新開始運行。SPECIALRUN參數(shù)適用于此進(jìn)程類型。
●遠(yuǎn)程任務(wù)是一種特殊類型的初始加載過程，其中Extract與 直接通過TCP/IP復(fù)制。不使用收集器進(jìn)程或跟蹤或文件中的臨時磁盤存儲。任務(wù)在提取參數(shù)文件中用RMTTASK參數(shù)定義。
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.
要區(qū)分系統(tǒng)上的多個提取或復(fù)制進(jìn)程，請定義處理組。例如，要并行復(fù)制不同的數(shù)據(jù)集，可以創(chuàng)建兩個復(fù)制組。
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.
一個進(jìn)程組由進(jìn)程（Extract或Replicat）、其參數(shù)文件、檢查點文件和與該進(jìn)程關(guān)聯(lián)的任何其他文件組成。對于Replicat，組還包含關(guān)聯(lián)的檢查點表。
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命令來定義組。有關(guān)允許的組名，請參閱《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.
與組相關(guān)的所有文件和檢查點共享分配給組本身的名稱。在發(fā)出控制或查看處理的命令時，可以通過通配符提供組名或多個組名
Overview of the Commit Sequence Number (CSN)
提交序列號（CSN）概述
使用Oracle GoldenGate時，可能需要引用提交序列號或CSN。CSN是Oracle GoldenGate為維護(hù)事務(wù)一致性和數(shù)據(jù)完整性而
構(gòu)造的用于標(biāo)識事務(wù)的標(biāo)識符。 它 唯 一標(biāo)識事務(wù)提交到數(shù)據(jù)庫的時間點。 可以要求CSN在事務(wù)日志中定位Extract，以重新定位
Replicat 在隊列上，或為了其他目的。它由一些轉(zhuǎn)換函數(shù)返回，并且 包括在報告和某些GGSCI輸出中。 有關(guān)CSN和每個數(shù)據(jù)庫的
CSN值列表的更多信息，請參見附錄 第559頁。
文章名稱：OracleGoldenGate11g官方文檔Administrator’sGuide續(xù)一
URL地址：http://m.jiaotiyi.com/article/jipjdh.html