Oracle GoldenGate官檔知識
Oracle GoldenGate 下載：
官網安裝文件：
Oracle GoldenGate 12c (12.2.0.1)：
Fusion Middleware Installing and Configuring Oracle GoldenGate for Oracle Database：
Fusion Middleware Oracle GoldenGate Release Notes for Windows and UNIX
：
=================================
Oracle Fusion Middleware Installing and Configuring Oracle GoldenGate for Oracle Database
Preface
System Requirements and Preinstallation Instructions
Installing Oracle GoldenGate
Preparing the Database for Oracle GoldenGate
Establishing Oracle GoldenGate Credentials
Choosing Capture and Apply Modes
Configuring Oracle GoldenGate in a Multitenant Container Database
Configuring Capture in Integrated Mode
Configuring Capture in Classic Mode
Configuring Oracle GoldenGate Apply
Additional Oracle GoldenGate Configuration Considerations
Additional Configuration Steps for Using Classic Capture
Additional Configuration Steps For Using Nonintegrated Replicat
Configuring DDL Support
Creating Process Groups
Instantiating Oracle GoldenGate Replication
Managing the DDL Replication Environment
Uninstalling Oracle GoldenGate
Optional Parameters for Integrated Modes
Configuring a Downstream Mining Database
Example Downstream Mining Configuration
Installing Trigger-Based DDL Capture
Supporting Changes to XML Schemas
Preparing DBFS for an Active-Active Configuration
Oracle GoldenGate Installed Components
=======================================================================
1 System Requirements and Preinstallation Instructions
本章包含支援Oracle GoldenGate的系統和資料庫資源的要求。本章包括以下部分
Verifying Certification and System Requirements
Operating System Requirements
Oracle Universal Installer Requirements for Oracle GoldenGate
Database Configuration
Summary of Supported Oracle Data Types and Objects Per Capture Mode
Details of Support for Oracle Data Types
Details of Support for Objects and Operations in Oracle DML
Details of Support for Objects and Operations in Oracle DDL
Supported and Non-supported Object Names
1.1 Verifying Certification and System Requirements
確保您在支援的硬體或軟體配置上安裝產品。 有關更多資訊，請參閱Oracle Fusion Middleware Supported System Configurations（"Oracle融合中介軟體支援的系統配置"）頁面上的發行證照文件。
1.2 Operating System Requirements作業系統檢查
1.2.1 Memory Requirements
For more information about evaluating Oracle GoldenGate memory requirements, see the CACHEMGR parameter in Reference for Oracle GoldenGate for Windows and UNIX.
有關評估Oracle GoldenGate記憶體需求的更多資訊，請參閱Oracle GoldenGate for Windows和UNIX的參考中的CACHEMGR引數。
1.2.2 Disk Requirements
1.2.2.1 Disk Requirements for Oracle GoldenGate Installation Files
This section shows the disk requirements for a manual installation and for an installation through OUI.
本部分顯示手動安裝和透過OUI安裝的磁碟要求。
Table 1-1 shows the disk space that is consumed by the files of one Oracle GoldenGate installation in a manual build. A manual build does not use OUI. The person installing Oracle GoldenGate uncompresses the files and creates the working directories.
表1-1顯示了手動構建中一個Oracle GoldenGate安裝檔案所消耗的磁碟空間。 手動構建不使用OUI。 安裝Oracle GoldenGate的人員解壓縮檔案並建立工作目錄。
Disk Requirements for an OUI Build
Platform Oracle Version Compressed Size (MB) Installed Size (MB)
Linux 12c 325 zip file 521
329 OUI installer
1.2.2.2 Other Disk Space Considerations
除了由GoldenGate安裝的檔案和二進位制檔案所需的磁碟空間之外，還可以在承載Oracle GoldenGate跟蹤（或小節）的任何系統上額外增加1 GB的磁碟空間。
1.2.2.3 Installing in a Cluster
要將Oracle GoldenGate安裝到叢集環境中，請將Oracle GoldenGate二進位制檔案和檔案作為Oracle使用者安裝到所有叢集節點可用的共享檔案系統上。 有關詳細資訊，請參閱準備在群集中安裝Oracle GoldenGate。
1.2.2.4 Temporary Disk Requirements
預設情況下，Oracle GoldenGate會將資料寫入Oracle GoldenGate安裝目錄的dirtmp子目錄中。 當總快取事務資料超過CACHEMGR引數的CACHESIZE設定時，Extract將開始將快取資料寫入臨時檔案。 快取管理器假定檔案系統上的所有可用空間都可用。 如果存在大型事務大小的事務卷，則該目錄可以快速填滿。 為了防止I / O爭用和與磁碟相關的Extract故障，請將磁碟專用於此目錄。 您可以使用CACHEMGR引數的CACHEDIRECTORY選項為此目錄指定名稱。
作業系統交換磁碟通常比使用Extract寫入臨時檔案更有效。 預設的CACHESIZE設定假定為。 因此，應該有足夠的磁碟空間來解決這個問題，因為只有在超過CACHESIZE的值之後才能將檔案系統名稱空間中的寫事務快取資料提取到臨時檔案。 如果在系統上執行多個"提取"程式，則磁碟需求可能會增加。 當沒有足夠的記憶體來儲存開啟的事務時，Oracle GoldenGate會寫入磁碟。 一旦提交或回滾事務，就將寫入的資料寫入跟蹤檔案，並從記憶體中釋放資料，並且Oracle GoldenGate不再跟蹤該事務。 沒有最低的磁碟要求，因為在每次操作之後提交事務時，這些事務永遠不會寫入磁碟。
1.2.3 Network
記錄您分配給Oracle GoldenGate的埠。 在配置Manager程式時，您將使用引數指定它們。
1.2.4 Operating System Privileges
以下是安裝Oracle GoldenGate並執行程式所需的作業系統中的許可權：
要在UNIX上安裝，安裝Oracle GoldenGate的人員必須具有對Oracle GoldenGate安裝目錄的讀寫許可權。
Oracle GoldenGate Extract，Replicat和Manager程式必須作為具有讀取，寫入和刪除Oracle GoldenGate目錄中的檔案和子目錄的許可權的作業系統使用者。 此外，Manager程式需要許可權來控制其他Oracle GoldenGate程式。
（經典捕捉模式）在經典捕捉模式下，"提取"（Extract）程式將直接讀取重做日誌，並且必須作為具有對線上和存檔的日誌檔案的讀取訪問許可權的作業系統使用者進行操作。 在UNIX系統上，該使用者必須是擁有Oracle例項的組的成員。 如果在本文件中的安裝步驟中將Manager程式作為Windows服務安裝，則必須以管理員身份安裝以分配正確的許可權。 如果無法安裝Manager作為服務，請手動分配對Extract程式的讀訪問許可權，然後始終以管理員身份執行管理器和提取。
將Extract，Replicat和Manager作業系統使用者專用於Oracle GoldenGate。 任何執行Oracle GoldenGate程式的人都可以使用敏感資訊，這取決於資料庫身份驗證的配置方式。
1.2.5 Console Character Sets
您可以使用以下DOS命令在開啟GGSCI會話之前設定控制檯的字符集：
chcp OS character set
1.3 Oracle Universal Installer Requirements for Oracle GoldenGate
1.4 Database Configuration資料庫配置
本節包含特定於Oracle資料庫的Oracle GoldenGate要求。 除非明確指出，否則這兩種捕獲模式都適用。
If you are using the DBMS_LOB.LOADFROMFILE procedure to update a LOB column only and your supplemental log is on all the columns, Integrated Extract captures the key columns and LOB improving performance. Classic Extract captures the all the columns by default. These behaviors do not effect like to like replications. However, with a replication to data warehouse, you may want all the columns for update. If you are converting from Classic Extract to Integrated Extract, you must use one of the following parameters to ensure that the Extract operates correctly:
如果您正在使用DBMS_LOB.LOADFROMFILE過程來更新LOB列，並且您的補充日誌位於所有列上，Integrated Extract將捕獲關鍵列和LOB以提高效能。 Classic Extract預設捕獲所有列。 這些行為並不像喜歡複製一樣。 但是，透過複製到資料倉儲，您可能希望更新所有列。 如果要從Classic Extract轉換為Integrated Extract，則必須使用以下引數之一來確保提取操作正確：
Use KEYCOLS to add all columns (except LOB).
Use LOGALLSUPCOLS to control the writing of supplementally logged columns.
Database user privileges and configuration requirements are explained in “Establishing Oracle GoldenGate Credentials”.
資料庫使用者許可權和配置要求在建立Oracle GoldenGate憑據中有所描述。
If the database is configured to use a bequeath connection, the sqlnet.ora file must contain the bequeath_detach=true setting.
如果資料庫配置為使用bequeath連線，則sqlnet.ora檔案必須包含bequeath_detach = true設定。
To install Oracle GoldenGate in an Oracle Real Application Cluster (RAC) environment, install Oracle GoldenGate on the shared drive(s) that are accessed by the RAC nodes. For more information, see Preparing to Install Oracle GoldenGate Within a Cluster.
要在Oracle Real Application Cluster（RAC）環境中安裝Oracle GoldenGate，請在由RAC節點訪問的共享驅動器上安裝Oracle GoldenGate。 有關詳細資訊，請參閱準備在群集中安裝Oracle GoldenGate。
(Integrated capture mode) Integrated Capture mode makes use of a logmining server on the source system or in a downstream Oracle Database. Refer to My Oracle Support article 1557031.1 for all Oracle Database release bundled patches for Oracle GoldenGate.
（整合捕獲模式）整合捕獲模式使用源系統或下游Oracle資料庫中的登入伺服器。 有關Oracle GoldenGate的所有Oracle資料庫版本捆綁補丁，請參閱我的Oracle支援文章1557031.1。
To use integrated capture with an Oracle 11.2.0.3 source database, download and install the 11.2.0.3 database specific bundled patch required for Integrated Extract.
For more information, see Choosing Capture and Apply Modes.
要使用整合捕獲與Oracle 11.2.0.3源資料庫，請下載並安裝Integrated Extract所需的11.2.0.3資料庫特定的捆綁補丁。有關詳細資訊，請參閱選擇捕獲和應用模式。
Oracle Databases must be in ARCHIVELOG mode so that Extract can process the log files.
Oracle資料庫必須處於ARCHIVELOG模式，以便Extract可以處理日誌檔案。
1.5 Summary of Supported Oracle Data Types and Objects Per Capture Mode 每種捕獲模式支援的Oracle資料型別和物件摘要
table 1-3 summarizes the way that Oracle GoldenGate supports the Oracle data types according to the capture mode that you choose. For more information about capture modes, see Deciding Which Capture Method to Use.
表1-3總結了Oracle GoldenGate根據您選擇的捕獲模式支援Oracle資料型別的方式。 有關捕獲模式的更多資訊，請參閱確定要使用的捕獲方法。
Detailed support information for Oracle data types, objects, and operations starts with Details of Support for Oracle Data Types.
有關Oracle資料型別，物件和操作的詳細支援資訊，請參閱Oracle資料型別支援詳細資訊。
見：
1.6 Details of Support for Oracle Data Types Oracle資料型別支援的詳細資訊
The following outlines details of Oracle data type support by Oracle GoldenGate. Unless otherwise noted, the support applies to both classic and integrated capture mode. For more information about these modes, see Choosing “Capture and Apply Modes”.
以下概述了Oracle GoldenGate支援的Oracle資料型別的詳細資訊。 除非另有說明，否則支援適用於經典和整合捕獲模式。 有關這些模式的更多資訊，請參閱選擇捕獲和應用模式。
1.6.1 ANYDATA Data Types
1.6.1.1 Limitations of Support
Your source database compatibility must be set to 11.2.0.0.0 or higher. Support for named collections and VARRAYs embedded within those data types.
您的源資料庫相容性必須設定為11.2.0.0.0或更高版本。 支援嵌入在這些資料型別中的命名集合和VARRAY。
1.6.2 Numeric Data Types
1.6.2.1 Limitations of Support
The support of the 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.
浮點數的範圍和精度的支援取決於主機。 一般來說，精確度精確到16位有效數字，但您應該檢視資料庫文件以確定預期的近似值。 Oracle GoldenGate可以舍入或截斷超出支援的精度的值。
1.6.3 Character Data Types
1.6.3.1 Limitations of Support
If an extended VARCHAR column is part of unique index or constraint, then direct path inserts to this table may cause Replicat to abend with a warning. Verify that the extended VARCHAR caused the abend by checking all_indexes/all_ind_columns for a unique index or all_cons_columns/all_constraints for a unique constraint. Once you determine that an extended VARCHAR, you can temporarily drop the index or disable the constraint:
如果擴充套件的VARCHAR列是唯一索引或約束的一部分，則直接路徑插入此表可能會導致Replicat退出警告。 透過檢查唯一索引的all_indexes / all_ind_columns來檢查擴充套件VARCHAR是否導致了異常，或者唯一約束的all_cons_columns / all_constraints。 確定擴充套件的VARCHAR後，您可以臨時刪除索引或禁用約束：
For Unique Index:
drop index t2u;
For Unique Constraint:
alter table v32ind modify constraint sys_c0010125 disable;
Extended (32K) VARCHAR2 and NVARCHAR2 columns are supported when Extract is in integrated capture mode. All modes of Replicat support 32K VARCHAR2 and NVARCHAR2 columns. The following limitations apply:
Extract處於整合捕獲模式時，支援擴充套件（32K）VARCHAR2和NVARCHAR2列。 Replicat的所有模式都支援32K VARCHAR2和NVARCHAR2列。 以下限制適用：
Oracle GoldenGate does not support 32K VARCHAR2 and NVARCHAR2 columns as part of a key or unique index, nor as a column in a KEYCOLS clause of the TABLE or MAP parameter. 32K columns cannot be used as row identifiers because they are not supplementally logged even when part of a primary key.
32K columns are not supported as resolution columns in a CDR (conflict resolution and detection) configuration nor as the basis for any other work that requires a column value to be present in the transaction log.
Oracle GoldenGate does not limit the number of 32K columns, but each trail record has a length limit of 4MB for inline records. The number of 32K columns that reaches this limit is approximately 160 columns, but the number of columns also depends on the actual size of the extended VARCHAR2 column.
1.6.4 Multi-byte Character Types 多位元組字元型別
1.6.5 Binary Data Types二進位制資料型別
1.6.6 Date and Timestamp Data Types 日期和時間戳資料型別
1.6.7 Large Object Data Types
1.6.8 XML Data Types
1.6.9 User Defined or Abstract Types 使用者定義或抽象型別
1.6.10 Non-Supported Oracle Data Types 不支援的Oracle資料型別
1.7 Details of Support for Objects and Operations in Oracle DML： Oracle DML中物件和操作的支援細節
This section outlines the Oracle objects and operations that Oracle GoldenGate supports for the capture and replication of DML operations.
本節概述Oracle GoldenGate支援捕獲和複製DML操作的Oracle物件和操作。
1.7.1 Multitenant Container Databases多租戶集裝箱資料庫
Oracle GoldenGate captures from, and delivers to, a multitenant container database. See Configuring Oracle GoldenGate in a Multitenant Container Database for more information about how Oracle GoldenGate supports multitenant container databases.
Oracle GoldenGate從多租戶容器資料庫捕獲並傳遞給多租戶集裝箱資料庫。 有關Oracle GoldenGate如何支援多租戶容器資料庫的更多資訊，請參閱在多租戶容器資料庫中配置Oracle GoldenGate。
1.7.2 Tables, Views, and Materialized Views
Oracle GoldenGate supports the following DML operations made to regular tables, index-organized tables, clustered tables, and materialized views.
Oracle GoldenGate支援對常規表，索引組織表，聚簇表和物化檢視進行的以下DML操作：
INSERT
UPDATE
DELETE
Associated transaction control operations
您可以使用DBA_GOLDENGATE_SUPPORT_MODE資料字典檢視顯示有關Oracle GoldenGate捕獲程式對資料庫中表的支援級別的資訊。 有關更多資訊，請參閱"Oracle資料庫參考"。
1.7.3 Sequences
1.7.4 Non-supported Objects and Operations in Oracle DML
1.8 Details of Support for Objects and Operations in Oracle DDL ：Oracle DDL中物件和操作支援的詳細資訊
This section outlines the Oracle objects and operation types that Oracle GoldenGate supports for the capture and replication of DDL operations. For more information about DDL support, see the following:
本節概述了Oracle GoldenGate支援捕獲和複製DDL操作的Oracle物件和操作型別。 有關DDL支援的更多資訊，請參閱以下內容：
Configuring DDL Support 配置DDL支援
Installing Trigger-Based DDL Capture (Trigger-based capture is required for Oracle releases that are earlier than version 11.2.0.4. If Extract will run in integrated mode against a version 11.2.0.4 or later Oracle Database, the DDL trigger and supporting objects are not required.)
安裝基於觸發器的DDL捕獲（低於版本11.2.0.4的Oracle版本需要基於觸發器的捕獲）。如果Extract將針對11.2.0.4或更高
1.8.1 Supported Objects and Operations in Oracle DDL：Oracle DDL中支援的物件和操作
When the source database is Oracle 11.2.0.4 or later and Extract operates in integrated mode, DDL capture support is integrated into the database logmining server and does not require the use of a DDL trigger. You must set the database parameter compatibility to 11.2.0.4.0. In integrated capture mode, Extract supports DDL that includes password-based column encryption
當源資料庫是Oracle 11.2.0.4或更高版本，Extract以整合模式執行時，DDL捕獲支援整合到資料庫登入伺服器中，不需要使用DDL觸發器。 您必須將資料庫引數相容性設定為11.2.0.4.0。 在整合捕獲模式下，Extract支援包含基於密碼的列加密的DDL
注意：Password-based column encryption in DDL is not supported in classic capture mode.
The following additional statements apply to both integrated and classic capture modes with respect to DDL support.以下附加說明適用於DDL支援的整合和經典捕獲模式。
Oracle DDL複製支援所有Oracle GoldenGate拓撲配置。在包含相同後設資料的兩個（而且只有兩個）資料庫之間支援Oracle DDL的主動（雙向）複製。Oracle GoldenGate支援以下物件上的DDL：
對於以下Oracle資料庫物件，整合的Extract支援Oracle DDL的基於Oracle版本的重新定義（EBR）資料庫複製
Oracle GoldenGate支援高達4 MB的DDL操作。 Oracle GoldenGate以位元組為單位測量DDL語句的大小，而不是字元。 此大小限制包括包，過程和功能。 DDL支援的實際大小限制是近似值，因為大小不僅包括語句文字，還包括Oracle GoldenGate維護開銷，這取決於物件名稱的長度，DDL型別以及內部保留DDL記錄的其他特性 。
Oracle GoldenGate支援全域性臨時表（GTT）DDL操作對Extract可見，以便它們可以被複制。 您必須將DDLOPTIONS引數設定為啟用此操作，因為它未被預設設定。
Oracle GoldenGate支援用於NOUSERID和TRANLOGOPTIONS GETCTASDML的整合字典。 這意味著Extract將從LogMiner字典而不是DDL觸發器獲取物件後設資料，而不查詢字典物件。 當源資料庫相容性引數大於或等於11.2.0.4時，Oracle GoldenGate將自動使用整合字典，並使用整合提取。
Classic Extract不支援整合字典功能。
當在Oracle GoldenGate版本12.2.x中使用整合字典和跟蹤格式時，如果Oracle資料庫版本早於12.1.0.2，則Integrated Capture需要將Logminer補丁應用於挖掘資料庫。
1.8.2 Non-supported Objects and Operations in Oracle DDL：Oracle DDL中不支援的物件和操作
These statements apply to integrated and classic capture modes.
1.8.2.1 Excluded Objects
1.8.2.2 Other Non-supported DDL
1.9 Supported and Non-supported Object Names 支援的和不支援的物件名稱
Oracle object names are case insensitive by default, but can be made case-sensitive with the use of double quotes. Oracle GoldenGate supports Oracle case-sensitivity. For information about Oracle GoldenGate support for object names and case, see Administering Oracle GoldenGate for Windows and UNIX.
Oracle物件名稱預設情況下不區分大小寫，但可以使用雙引號使其區分大小寫。 Oracle GoldenGate支援Oracle區分大小寫。 有關Oracle GoldenGate對物件名稱和大小寫的支援的資訊，請參閱管理Oracle GoldenGate for Windows和UNIX。
2 Installing Oracle GoldenGate安裝Oracle GoldenGate
本章包括首次安裝Oracle GoldenGate的說明。 安裝Oracle GoldenGate安裝執行和管理處理所需的所有元件（不包括其他供應商所需的任何元件，如驅動程式或庫），並安裝Oracle GoldenGate實用程式。 本章包括以下部分：
Understanding and Obtaining the Oracle GoldenGate Distribution
Setting ORACLE_HOME and ORACLE_SID
Setting Library Paths for Dynamic Builds on UNIX
Preparing to Install Oracle GoldenGate Within a Cluster
Installing Oracle GoldenGate
Integrating Oracle GoldenGate into a Cluster
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.這些說明首次用於安裝Oracle GoldenGate。 此外，它們用於下載新版本的Oracle GoldenGate的基本版本。
To download and install subsequent patches to the base release, go to the Patches and Updates tab of My Oracle Support at:
To upgrade Oracle GoldenGate from one version to another, follow the upgrade instructions at:
2.1 Understanding and Obtaining the Oracle GoldenGate Distribution 瞭解和獲取Oracle GoldenGate發行版
For complete information about how to obtain Oracle Fusion Middleware software, see "Understanding and Obtaining Product Distributions" in Planning an Installation of Oracle Fusion Middleware.
To download the Oracle WebLogic Server and Coherence software for development or evaluation, see the following location on the Oracle Technology Network (OTN):
For more information about locating and downloading Oracle Fusion Middleware products, see the Oracle Fusion Middleware Download, Installation, and Configuration Readme Files on OTN.
To obtain Oracle GoldenGate follow these steps:
1.Go to Oracle Technology Network.
2.Find the Oracle GoldenGate 12c (12.2.0.1) release and download the ZIP file onto your system.
2.2 Setting ORACLE_HOME and ORACLE_SID 設定ORACLE_HOME和ORACLE_SID
確保將ORACLE_HOME和ORACLE_SID系統環境變數設定為正確的Oracle例項。 連線到資料庫時，Oracle GoldenGate程式引用它們。
If there is one instance of Oracle Database on the system, set the ORACLE_HOME and ORACLE_SID environment variables at the system level. If you cannot set them that way, use the following SETENV statements in the parameter file of every Extract and Replicat group that will be connecting to the instance. The SETENV parameters override the system settings and allow the Oracle GoldenGate process to set the variables at the session level when it connects to the database.
如果系統上有一個Oracle資料庫例項，請在系統級別設定ORACLE_HOME和ORACLE_SID環境變數。 如果不能以這種方式設定，請在將連線到例項的每個"提取"和"複製"組的引數檔案中使用以下SETENV語句。 SETENV引數覆蓋系統設定，並允許Oracle GoldenGate程式在連線到資料庫時將變數設定為會話級別。
SETENV (ORACLE_HOME = "path to Oracle home location")
SETENV (ORACLE_SID = "SID")
If there are multiple Oracle instances on the system with Extract and Replicat processes connecting to them, you will need to use a SETENV statement in the parameter file of each process group. As input to the SETENV parameter, use the ORACLE_HOME and ORACLE_SID environment variables to point Oracle GoldenGate to the correct Oracle instance. For example, the following shows parameter files for two Extract groups, each capturing from a different Oracle instance.
如果系統上有多個連線了Extract和Replicat程式的Oracle例項，則需要在每個程式組的引數檔案中使用SETENV語句。 作為SETENV引數的輸入，使用ORACLE_HOME和ORACLE_SID環境變數將Oracle GoldenGate指向正確的Oracle例項。 例如，以下顯示兩個"提取"組的引數檔案，每個從不同的Oracle例項捕獲。
Group 1:
EXTRACT ora9a
SETENV (ORACLE_HOME = "/home/oracle/ora/product")
SETENV (ORACLE_SID = "oraa")
USERIDALIAS tiger1
RMTHOST sysb
RMTTRAIL /home/ggs/dirdat/rt
TABLE hr.emp;
TABLE hr.salary;
Group 2:
EXTRACT orab
SETENV (ORACLE_HOME = "/home/oracle/ora/product")
SETENV (ORACLE_SID = "orab")
USERIDALIAS tiger1
RMTHOST sysb
RMTTRAIL /home/ggs/dirdat/st
TABLE fin.sales;
TABLE fin.cust;
2.3 Setting Library Paths for Dynamic Builds on UNIX：在UNIX上設定動態構建的庫路徑
Oracle GoldenGate使用共享庫。 在UNIX系統上安裝Oracle GoldenGate時，在執行GGSCI或任何其他Oracle GoldenGate程式之前，以下內容必須為真：
1.確保將資料庫庫新增到系統的共享庫環境變數中。 此過程通常在資料庫安裝時執行。 如果您有任何問題，請諮詢資料庫管理員。
當Oracle GoldenGate在與資料庫相同的伺服器上執行時，以下所有內容必須為64位：Oracle library versions；Oracle GoldenGate version；Database versions；
當Oracle GoldenGate透過SQL * Net遠端連線到資料庫伺服器時，需要以下內容：
Replicat: The Oracle client library and the Oracle GoldenGate build must have the same Oracle version, bit type (64-bit or IA64), and operating system version.
Extract: The Oracle client library and the Oracle GoldenGate build must have the same Oracle version, bit type (64-bit or IA64), and operating system version. In addition, both operating systems must be the same endian.
2.如果您將在UNIX系統上從Oracle GoldenGate安裝目錄外部執行Oracle GoldenGate程式
(Optional) Add the Oracle GoldenGate installation directory to the PATH environment variable.
(可選)將Oracle GoldenGate安裝目錄新增到PATH環境變數中。
(Required) Add the Oracle GoldenGate installation directory to the shared-libraries environment variable.
(必需)將Oracle GoldenGate安裝目錄新增到共享庫環境變數中。
Example 2-2 To Set the Variables in Bourne Shell:
export PATH=installation_directory:$PATH
export shared_libraries_variable=absolute_path_of_installation_directory:$shared_libraries_variable
Where shared libraries variable is one of the variables shown in Table 2-1:共享庫變數是表2-1中顯示的變數之一
Platform Environment variable
LINUX LD_LIBRARY_PATH
注意：
To view the libraries that are required by an Oracle Oracle GoldenGate process, use the ldd goldengate_process shell command before starting the process. This command also shows an error message for any that are missing.
要檢視Oracle Oracle GoldenGate程式所需的庫，請在啟動該程式之前使用ldd goldengate_process shell命令。 此命令還顯示任何缺少的錯誤訊息。
2.4 Preparing to Install Oracle GoldenGate Within a Cluster 在叢集中安裝Oracle GoldenGate
本主題介紹了在叢集環境中安裝Oracle GoldenGate時的安裝要求。 Oracle GoldenGate可以與任何能夠自動進行故障切換的叢集管理解決方案配合使用。 Oracle Clusterware解決方案提供了能夠與或不與Oracle RAC資料庫一起使用的優點，從而可以包括執行Oracle GoldenGate的任何非資料庫伺服器。
2.4.1 Deciding Where to Install Oracle GoldenGate Binaries and Files in the Cluster
2.4.2 Example Oracle Cluster Storage
2.5 Installing Oracle GoldenGate 安裝Oracle GoldenGate
2.5.1 Performing an Interactive Installation with OUI 使用OUI執行互動式安裝
OUI安裝在資料庫版本在11g及以上才支援
The interactive installation provides a graphical user interface that prompts for the required installation information. These instructions apply to new installations as well as upgrades. However, to perform an upgrade to Oracle GoldenGate, follow the instructions in Upgrading Oracle GoldenGate for Windows and UNIX, which includes a prompt to run OUI at the appropriate time.
互動式安裝提供了一個圖形使用者介面，提示所需的安裝資訊。 這些說明適用於新的安裝和升級。 但是，要執行升級到Oracle GoldenGate，請按照升級Oracle GoldenGate for Windows和UNIX的說明進行操作，其中包括在適當時間執行OUI的提示。
2.5.2 Performing a Silent Installation with OUI 使用OUI執行靜默安裝
You perform a silent installation by running a response file. You can create a response file by selecting the Save Response File option during an interactive OUI session or by editing a template, as shown in Example 2-4. To run a response file, issue the following command.
您可以透過執行響應檔案執行靜默安裝。 您可以透過在互動式OUI會話期間選擇儲存響應檔案選項或透過編輯模板來建立響應檔案，如示例2-4所示。 要執行響應檔案，請發出以下命令。
./runIntailler -silent -nowait -responseFile path_to_file
2.6 Integrating Oracle GoldenGate into a Cluster
If you installed Oracle GoldenGate in a cluster, take the following steps to integrate Oracle GoldenGate within the cluster solution.
For more information about installing and using Oracle GoldenGate in a cluster, see the Oracle GoldenGate with Oracle Real Application Clusters Configuration white paper
2.6.1 General Requirements in a Cluster
2.6.2 Adding Oracle GoldenGate as a Windows Cluster Resource
3 Preparing the Database for Oracle GoldenGate 準備Oracle GoldenGate資料庫
This chapter contains steps to take so that the source Oracle Database is configured properly to support the capture of transactional changes.
本章包含採取的步驟，以便正確配置源Oracle資料庫以支援事務性更改的捕獲。
This chapter includes the following sections:本章包括以下部分
Configuring Connections for Integrated Processes
Configuring Logging Properties
Enabling Oracle GoldenGate in the Database
Setting Flashback Query
Managing Server Resources
3.1 Configuring Connections for Integrated Processes 組態整合過程的連線
If you will be using integrated capture and integrated Replicat, each requires a dedicated server connection in the tnsnames.ora file. You direct the processes to use these connections with the USERID or USERIDALIAS parameter in the Extract and Replicat parameter files when you configure those processes.
如果您將使用整合捕獲和整合的Replicat，則每個都需要tnsnames.ora檔案中的專用伺服器連線。 在配置這些程式時，您可以使用"提取和複製"引數檔案中的USERID或USERIDALIAS引數來指導程式使用這些連線。
示例：
The following is an example of the dedicated connection required for integrated capture (Extract) and integrated Replicat.
TEST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = test2)(PORT = 1521))
)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = test)
)
)
The following are the security options for specifying the connection string in the Extract or Replicat parameter file.
Password encryption method:
USERID intext@test, PASSWORD mypassword
Credential store method:
USERIDALIAS ext
In the case of USERIDALIAS, the alias ext is stored in the Oracle GoldenGate credential store with the actual connection string, as in the following example:
GGSCI> INFO CREDENTIALSTORE DOMAIN support
Domain: Support
Alias: ext
Userid: intext@test
For more information about specifying database connection information in the parameter file, see "Administering Oracle GoldenGate for Windows and UNIX".
3.2 Configuring Logging Properties 配置日誌記錄屬性
Oracle GoldenGate依賴重做日誌來捕獲複製源事務所需的資料。 在啟動Oracle GoldenGate處理之前，必須正確配置源系統上的Oracle重做日誌。
本節介紹適用於Oracle GoldenGate的以下日誌記錄級別。 您使用的日誌記錄級別取決於您使用的Oracle GoldenGate功能或功能。
3.2.1 Enabling Minimum Database-level Supplemental Logging 啟用最低資料庫級補充日誌記錄
Oracle strongly recommends putting the Oracle source database into forced logging mode. Forced logging mode forces the logging of all transactions and loads, overriding any user or storage settings to the contrary. This ensures that no source data in the Extract configuration gets missed.
Oracle強烈建議將Oracle源資料庫置於強制登入模式。 強制日誌記錄模式強制記錄所有事務和載入，覆蓋任何使用者或儲存設定相反。 這樣可以確保"提取"配置中的源資料不會丟失。
In addition, minimal supplemental logging, a database-level option, is required for an Oracle source database when using Oracle GoldenGate. This adds row chaining information, if any exists, to the redo log for update operations.
此外，使用Oracle GoldenGate時，Oracle資料庫需要最少的補充日誌記錄（資料庫級別選項）。 這將新增行連結資訊（如果有的話）到重做日誌以進行更新操作。
Database-level primary key (PK) and unique index (UI) logging is strongly discouraged because of the excessive additional overhead it creates on tables outside of replication. Unless those logging options are required for business purposes, you only need to enable minimal supplemental logging at the database level and force logging for Oracle GoldenGate.
強烈不鼓勵資料庫級主鍵（PK）和唯一索引（UI）日誌記錄，因為它在複製之外的表上建立了額外的額外開銷。 除非這些日誌選項是商業目的需要的，否則您只需要在資料庫級別啟用最少的補充日誌記錄，並強制Oracle GoldenGate的日誌記錄。
檢查是否開啟最小補充日誌和force logging：
SELECT supplemental_log_data_min, force_logging FROM v$database;
開啟最小補充日誌和force logging：
ALTER DATABASE ADD SUPPLEMENTAL LOG DATA;
ALTER DATABASE FORCE LOGGING;
3.2.2 Enabling Schema-level Supplemental Logging 啟用schema級補充日誌記錄
Oracle GoldenGate supports schema-level supplemental logging. Schema-level logging is required for an Oracle source database when using the Oracle GoldenGate DDL replication feature. In all other use cases, it is optional, but then you must use table-level logging instead (see Enabling Table-level Supplemental Logging).
Oracle GoldenGate支援Schema級補充日誌記錄.使用Oracle GoldenGate DDL複製功能時，Oracle源資料庫需要Schema級日誌記錄。在所有其他用例中,它是可選的,但是您必須使用表級日誌記錄（請參閱啟用表級補充日誌記錄）。
注意：Oracle強烈建議使用模式級日誌記錄而不是表級日誌記錄，因為它可以確保新增到模式中的任何新表符合萬用字元規範。
perform the following steps on the source system to enable schema-level supplemental logging.
1.Apply Oracle Patch 13794550 to the source Oracle Database if the version is earlier than 11.2.0.2.
2.Run GGSCI on the source system.
3.Issue the DBLOGIN command with the alias of a user in the credential store who has privilege to enable schema-level supplemental logging.
DBLOGIN USERIDALIAS alias
See Reference for Oracle GoldenGate for Windows and UNIX for more information about DBLOGIN and additional options.
4.Issue the ADD SCHEMATRANDATA command for each schema for which you want to capture data changes with Oracle GoldenGate.
ADD SCHEMATRANDATA schema [ALLCOLS | NOSCHEDULINGCOLS]
Where:
Without options, ADD SCHEMATRANDATA schema enables the unconditional supplemental logging on the source system of the primary key and the conditional supplemental logging of all unique key(s) and foreign key(s) of all current and future tables in the given schema. Unconditional logging forces the primary key values to the log whether or not the key was changed in the current operation. Conditional logging logs all of the column values of a foreign or unique key if at least one of them was changed in the current operation. The default is optional to support nonintegrated Replicat but is required to support integrated Replicat because primary key, unique keys, and foreign keys must all be available to the inbound server to compute dependencies. For more information about integrated Replicat, see Deciding Which Apply Method to Use.
ALLCOLS can be used to enable the unconditional supplemental logging of all of the columns of a table and applies to all current and future tables in the given schema. Use to support integrated Replicat when the source and target tables have different scheduling columns. (Scheduling columns are the primary key, the unique key, and the foreign key.)
NOSCHEDULINGCOLS logs only the values of the primary key and all valid unique indexes for existing tables in the schema and new tables added later. This is the minimal required level of schema-level logging and is valid only for Replicat in nonintegrated mode.
In the following example, the command enables default supplemental logging for the finance schema.
ADD SCHEMATRANDATA finance
In the following example, the command enables the supplemental logging only for the primary key and valid unique indexes for the hr schema.
ADD SCHEMATRANDATA hr NOSCHEDULINGCOLS
See Reference for Oracle GoldenGate for Windows and UNIX for more information about ADD SCHEMATRANDATA.
3.2.3 Enabling Table-level Supplemental Logging 啟用表級補充日誌
在以下情況下，在源系統上啟用表級補充日誌記錄：在不使用schema級日誌記錄時啟用所需級別的日誌記錄（請參閱啟用schema級補充日誌記錄）;防止為任何給定的表記錄主鍵; 在表級別記錄非關鍵列值，以支援特定的Oracle GoldenGate功能，例如過濾和衝突檢測和解析邏輯。
Perform the following steps on the source system to enable table-level supplemental logging or use the optional features of the command.
1.Run GGSCI on the source system.
2.Issue the DBLOGIN command using the alias of a user in the credential store who has privilege to enable table-level supplemental logging.
DBLOGIN USERIDALIAS alias
See Reference for Oracle GoldenGate for Windows and UNIX for more information about DBLOGIN and additional options.
3.Issue the ADD TRANDATA command.
ADD TRANDATA [container.]schema.table [, COLS (columns)] [, NOKEY] [, ALLCOLS | NOSCHEDULINGCOLS]
Where:
container is the name of the root container or pluggable database if the table is in a multitenant container database.
schema is the source schema that contains the table.
table is the name of the table. See Administering Oracle GoldenGate for Windows and UNIX for instructions for specifying object names.
ADD TRANDATA without other options automatically enables unconditional supplemental logging of the primary key and conditional supplemental logging of unique key(s) and foreign key(s) of the table. Unconditional logging forces the primary key values to the log whether or not the key was changed in the current operation. Conditional logging logs all of the column values of a foreign or unique key if at least one of them was changed in the current operation. The default is optional to support nonintegrated Replicat (see also NOSCHEDULINGCOLS) but is required to support integrated Replicat because primary key, unique keys, and foreign keys must all be available to the inbound server to compute dependencies. For more information about integrated Replicat, see Deciding Which Apply Method to Use.
沒有其他選項的ADD TRANDATA可以自動啟用主鍵的無條件補充日誌記錄和條件補充日誌記錄表的唯一鍵和外來鍵。 無條件日誌記錄會將主鍵值強制到日誌，無論在當前操作中鍵是否更改。 條件記錄記錄外部或唯一鍵的所有列值，如果當前操作中至少有一個值被更改。 預設值是可選的，以支援非整合的Replicat（另見NOSCHEDULINGCOLS），但是需要支援整合的Replicat，因為主鍵，唯一鍵和外來鍵都必須可用於入站伺服器以計算依賴關係。 有關整合的Replicat的更多資訊，請參閱確定使用哪種應用方法。
ALLCOLS enables the unconditional supplemental logging of all of the columns of the table. Use to support integrated Replicat when the source and target tables have different scheduling columns. (Scheduling columns are the primary key, the unique key, and the foreign key.)
ALLCOLS可以對錶的所有列進行無條件的補充記錄。 當源表和目標表具有不同的排程列時，用於支援整合的Replicat。 （排程列是主鍵，唯一鍵和外來鍵）。
NOSCHEDULINGCOLS is valid for Replicat in nonintegrated mode only. It issues an ALTER TABLE command with an ADD SUPPLEMENTAL LOG DATA ALWAYS clause that is appropriate for the type of unique constraint that is defined for the table, or all columns in the absence of a unique constraint. This command satisfies the basic table-level logging requirements of Oracle GoldenGate when schema-level logging will not be used. See Ensuring Row Uniqueness in Source and Target Tables for how Oracle GoldenGate selects a key or index.
NOSCHEDULINGCOLS僅在非整合模式下對Replicat有效。 它使用ADD SUPPLEMENTAL LOG DATA ALWAYS子句發出一個ALTER TABLE命令，該子句適用於為表定義的唯一約束型別，或不存在唯一約束的所有列。 當不使用模式級日誌記錄時，此命令滿足Oracle GoldenGate的基本表級日誌記錄要求。 請參閱確定源和目標表中的行唯一性，以瞭解Oracle GoldenGate如何選擇金鑰或索引。
COLS columns logs non-key columns that are required for a KEYCOLS clause or for filtering and manipulation. The parentheses are required. These columns will be logged in addition to the primary key unless the NOKEY option is also present.
COLS列記錄KEYCOLS子句所需的非鍵列或過濾和操作。 括號是必需的。 這些列除了主鍵之外還將被記錄，除非NOKEY選項也存在。
NOKEY prevents the logging of the primary key or unique key. Requires a KEYCOLS clause in the TABLE and MAP parameters and a COLS clause in the ADD TRANDATA command to log the alternate KEYCOLS columns.
NOKEY防止記錄主鍵或唯一鍵。 需要TABLE和MAP引數中的KEYCOLS子句以及ADD TRANDATA命令中的COLS子句才能記錄備用KEYCOLS列。
4.If using ADD TRANDATA with the COLS option, create a unique index for those columns on the target to optimize row retrieval. If you are logging those columns as a substitute key for a KEYCOLS clause, make a note to add the KEYCOLS clause to the TABLE and MAP statements when you configure the Oracle GoldenGate processes.
如果使用帶有COLS選項的ADD TRANDATA，則為目標上的那些列建立唯一的索引，以最佳化行檢索。 如果您正在將這些列作為KEYCOLS子句的替代鍵進行記錄，請在配置Oracle GoldenGate程式時，記下將KEYCOLS子句新增到TABLE和MAP語句。
See Reference for Oracle GoldenGate for Windows and UNIX for more information about ADD TRANDATA.
3.3 Enabling Oracle GoldenGate in the Database 在資料庫中啟用Oracle GoldenGate
必須為Oracle 11.2.0.4或更高版本的資料庫顯式啟用支援Oracle GoldenGate捕獲和應用所需的資料庫服務。 這是Extract和Replicat的所有模式所必需的。
要啟用Oracle GoldenGate，請設定以下資料庫初始化引數。 Oracle RAC中的所有例項必須具有相同的設定。
ENABLE_GOLDENGATE_REPLICATION =true
For more information about this parameter, see Oracle Database Reference.
3.4 Setting Flashback Query 設定閃回查詢
To process certain update records, Extract fetches additional row data from the source database. Oracle GoldenGate fetches data for the following:
User-defined types
Nested tables
XMLType objects
By default, Oracle GoldenGate uses Flashback Query to fetch the values from the undo (rollback) tablespaces. That way, Oracle GoldenGate can reconstruct a read-consistent row image as of a specific time or SCN to match the redo record.
預設情況下，Oracle GoldenGate使用Flashback Query從undo（rollback）表空間中獲取值。 這樣，Oracle GoldenGate可以根據特定時間或SCN重建一個讀取一致的行影像，以匹配重做記錄。
For best fetch results, configure the source database as follows:為獲得最佳提取結果，請按如下方式配置源資料庫
1.透過設定Oracle初始化引數UNDO_MANAGEMENT和UNDO_RETENTION來設定足夠的重做保留次數
2.使用以下公式計算undo表空間中所需的空間。
undo_space = UNDO_RETENTION * UPS + overhead
Use the system view V$UNDOSTAT to estimate UPS and overhead.
3.對於包含LOB的表，請執行以下操作之一：
Set the LOB storage clause to RETENTION. This is the default for tables that are created when UNDO_MANAGEMENT is set to AUTO；
If using PCTVERSION instead of RETENTION, set PCTVERSION to an initial value of 25. You can adjust it based on the fetch statistics that are reported with the STATS EXTRACT command (see Table 3-2). If the value of the STAT_OPER_ROWFETCH CURRENTBYROWID or STAT_OPER_ROWFETCH_CURRENTBYKEY field in these statistics is high, increase PCTVERSION in increments of 10 until the statistics show low values.
4.Grant either of the following privileges to the Oracle GoldenGate Extract user:
GRANT FLASHBACK ANY TABLE TO db_user：
GRANT FLASHBACK ON schema.table TO db_user
3.5 Managing Server Resources 管理伺服器資源
在整合模式下，Extract與源資料庫中的底層日誌伺服器進行互動，Replicat與目標資料庫中的入站伺服器進行互動。 本節提供管理這些伺服器所使用的共享記憶體的指導。
伺服器使用的共享記憶體來自資料庫中系統全域性區域（SGA）的Streams池部分。 因此，您必須將資料庫初始化引數STREAMS_POOL_SIZE設定得足夠高，以保持足夠的記憶體可用於您希望以整合模式執行的Extract和Replicat程式數。 請注意，Streams池也被資料庫的其他元件（如Oracle Streams，Advanced Queuing和Datapump匯出/匯入）使用，因此在確定Oracle GoldenGate的Streams池時，請務必考慮它們。
預設情況下，一個整合捕獲提取請求登入伺服器以MAX_SGA_SIZE為1GB的行數執行，並且PARALLELISM為2.因此，如果在同一資料庫例項中以整合捕獲模式執行三個提取，則至少需要3 GB的記憶體 到Streams池。 作為最佳做法，可以保留25％的Streams池。 例如，如果整合捕獲模式中有三個提取，請將STREAMS_POOL_SIZE設定為以下：
3 GB + (3 GB * 0.25) = 3.75 GB
4. Establishing Oracle GoldenGate Credentials 建立Oracle GoldenGate證照
This chapter provides guidelines for creating database users for the processes that will interact with the database, assigning the correct privileges, and securing the credentials from unauthorized use.
本章提供了為與資料庫進行互動的過程建立資料庫使用者的準則，分配正確的許可權以及保護憑據以防止未經授權的使用。
This chapter includes the following sections:本章包括以下部分：
Assigning Credentials to Oracle GoldenGate
Securing the Oracle GoldenGate Credentials
4.1 Assigning Credentials to Oracle GoldenGate
The Oracle GoldenGate processes require one or more database credentials with the correct database privileges for the database version, database configuration, and Oracle GoldenGate features that you are using. Create a source database user and a target database user, each one dedicated to Oracle GoldenGate on the source and target systems. The assigned user can be the same user for all of the Oracle GoldenGate processes that must connect to a source or target Oracle Database.
Oracle GoldenGate程式需要一個或多個資料庫憑據，以及正在使用的資料庫版本，資料庫配置和Oracle GoldenGate功能的正確資料庫許可權。 建立源資料庫使用者和目標資料庫使用者，每個使用者都在源和目標系統上專用於Oracle GoldenGate。 對於必須連線到源或目標Oracle資料庫的所有Oracle GoldenGate程式，分配的使用者可以是相同的使用者。
The following sections outline the Oracle GoldenGate processes that require user credentials:
Extract User
Replicat User
Other Oracle GoldenGate Users
4.1.1 Extract User
The Extract user performs metadata queries on the source database and fetches data from the source tables when needed. In a local mining deployment of integrated capture, this user also creates, alters, and connects to the logmining server and receives logical change records (LCR) from it. (See Deciding Which Capture Method to Use for more information about capture modes.)
If the source database is a multitenant container database, the Extract user must be a common user and must log into the root container. See Configuring Oracle GoldenGate in a Multitenant Container Database for more information.
You need to assign an additional user if Extract will be operating in integrated capture mode and you are using a downstream mining database. This user will be the mining user and is created in the downstream database. The mining user creates, alters, and connects to the logmining server on the mining database, and it receives logical change records (LCR) from it. This user can be the same as the source Extract user or different. Choose the name of the mining user carefully. Once created by this user, the database logmining server cannot be altered or used by another user. See Configuring a Downstream Mining Database for more information about configuring downstream mining.
4.1.2 Replicat User
The Replicat user creates the Replicat checkpoint table (if used) and applies DML and DDL operations through Oracle Call Interface or through a database inbound server, depending on the Replicat mode. (See Deciding Which Apply Method to Use for more information about Replicat modes.)
Replicat使用者建立Replicat檢查點表（如果使用），並根據Replicat模式透過Oracle呼叫介面或資料庫入站伺服器應用DML和DDL操作。 （有關複製模式的更多資訊，請參閱確定使用哪種應用方法。）
4.1.3 Other Oracle GoldenGate Users
A user is required in the source database for the Manager process if you are using Oracle GoldenGate DDL support. This user performs maintenance on the Oracle GoldenGate database objects that support DDL capture.
如果您正在使用Oracle GoldenGate DDL支援，則需要在源資料庫中為Manager程式使用使用者。 此使用者對支援DDL捕獲的Oracle GoldenGate資料庫物件執行維護。
4.1.4 Granting the Appropriate User Privileges 授予適當的使用者許可權
The user privileges that are required for Oracle GoldenGate depend on the database version and the Extract or Replicat process mode. For more information about process modes, see Choosing Capture and Apply Modes.
4.1.4.1 Oracle 11.2.0.4 or Later Database Privileges
4.1.4.2 Oracle 11.2.0.3 or Earlier Database Privileges
4.1.4.3 About the dbms_goldengate_auth.grant_admin_privilege Package
Most of the privileges that are needed for Extract and Replicat to operate in classic and integrated mode are granted through the dbms_goldengate_auth.grant_admin_privilege package.
Extract和Replicat以經典和整合模式執行所需的大部分許可權透過dbms_goldengate_auth.grant_admin_privilege包進行授予。
4.1.4.4 Optional Grants for dbms_goldengate_auth.grant_admin_privilege
Additional grants can be added to dbms_goldengate_auth.grant_admin_privilege to support the optional features shown in Table 4-3.
4.2 Securing the Oracle GoldenGate Credentials
To preserve the security of your data, and to monitor Oracle GoldenGate processing accurately, do not permit other users, applications, or processes to log on as, or operate as, an Oracle GoldenGate database user.
為了保持資料的安全性，並準確監控Oracle GoldenGate處理，不允許其他使用者，應用程式或程式以Oracle GoldenGate資料庫使用者身份登入或操作。
Oracle GoldenGate provides different options for securing the login credentials assigned to Oracle GoldenGate processes. The recommended option is to use a credential store. You can create one credential store and store it in a shared location where all installations of Oracle GoldenGate can access it, or you can create a separate one on each system where Oracle GoldenGate is installed.
Oracle GoldenGate提供了不同的選項來保護分配給Oracle GoldenGate程式的登入憑據。 推薦的選項是使用憑證儲存。 您可以建立一個憑據儲存，並將其儲存在Oracle GoldenGate的所有安裝可以訪問的共享位置，也可以在安裝了Oracle GoldenGate的每個系統上建立一個單獨的憑據儲存。
The credential store stores the user name and password for each of the assigned Oracle GoldenGate users. A user ID is associated with one or more aliases, and it is the alias that is supplied in commands and parameter files, not the actual user name or password. The credential file can be partitioned into domains, allowing a standard set of aliases to be used for the processes, while allowing the administrator on each system to manage credentials locally.
憑據儲存儲存每個分配的Oracle GoldenGate使用者的使用者名稱和密碼。 使用者ID與一個或多個別名相關聯，它是在命令和引數檔案中提供的別名，而不是實際的使用者名稱或密碼。 可以將憑據檔案分割槽為域，允許將一組標準的別名用於程式，同時允許每個系統上的管理員在本地管理憑據。
See “Administering Oracle GoldenGate for Windows and UNIX” for more information about creating a credential store and adding user credentials.
有關建立憑據儲存和新增使用者憑據的更多資訊，請參閱管理適用於Windows和UNIX的Oracle GoldenGate。
官網安裝文件：
Oracle GoldenGate 12c (12.2.0.1)：
Fusion Middleware Installing and Configuring Oracle GoldenGate for Oracle Database：
Fusion Middleware Oracle GoldenGate Release Notes for Windows and UNIX
：
=================================
Oracle Fusion Middleware Installing and Configuring Oracle GoldenGate for Oracle Database
Preface
System Requirements and Preinstallation Instructions
Installing Oracle GoldenGate
Preparing the Database for Oracle GoldenGate
Establishing Oracle GoldenGate Credentials
Choosing Capture and Apply Modes
Configuring Oracle GoldenGate in a Multitenant Container Database
Configuring Capture in Integrated Mode
Configuring Capture in Classic Mode
Configuring Oracle GoldenGate Apply
Additional Oracle GoldenGate Configuration Considerations
Additional Configuration Steps for Using Classic Capture
Additional Configuration Steps For Using Nonintegrated Replicat
Configuring DDL Support
Creating Process Groups
Instantiating Oracle GoldenGate Replication
Managing the DDL Replication Environment
Uninstalling Oracle GoldenGate
Optional Parameters for Integrated Modes
Configuring a Downstream Mining Database
Example Downstream Mining Configuration
Installing Trigger-Based DDL Capture
Supporting Changes to XML Schemas
Preparing DBFS for an Active-Active Configuration
Oracle GoldenGate Installed Components
=======================================================================
1 System Requirements and Preinstallation Instructions
本章包含支援Oracle GoldenGate的系統和資料庫資源的要求。本章包括以下部分
Verifying Certification and System Requirements
Operating System Requirements
Oracle Universal Installer Requirements for Oracle GoldenGate
Database Configuration
Summary of Supported Oracle Data Types and Objects Per Capture Mode
Details of Support for Oracle Data Types
Details of Support for Objects and Operations in Oracle DML
Details of Support for Objects and Operations in Oracle DDL
Supported and Non-supported Object Names
1.1 Verifying Certification and System Requirements
確保您在支援的硬體或軟體配置上安裝產品。 有關更多資訊，請參閱Oracle Fusion Middleware Supported System Configurations（"Oracle融合中介軟體支援的系統配置"）頁面上的發行證照文件。
1.2 Operating System Requirements作業系統檢查
1.2.1 Memory Requirements
For more information about evaluating Oracle GoldenGate memory requirements, see the CACHEMGR parameter in Reference for Oracle GoldenGate for Windows and UNIX.
有關評估Oracle GoldenGate記憶體需求的更多資訊，請參閱Oracle GoldenGate for Windows和UNIX的參考中的CACHEMGR引數。
1.2.2 Disk Requirements
1.2.2.1 Disk Requirements for Oracle GoldenGate Installation Files
This section shows the disk requirements for a manual installation and for an installation through OUI.
本部分顯示手動安裝和透過OUI安裝的磁碟要求。
Table 1-1 shows the disk space that is consumed by the files of one Oracle GoldenGate installation in a manual build. A manual build does not use OUI. The person installing Oracle GoldenGate uncompresses the files and creates the working directories.
表1-1顯示了手動構建中一個Oracle GoldenGate安裝檔案所消耗的磁碟空間。 手動構建不使用OUI。 安裝Oracle GoldenGate的人員解壓縮檔案並建立工作目錄。
Disk Requirements for an OUI Build
Platform Oracle Version Compressed Size (MB) Installed Size (MB)
Linux 12c 325 zip file 521
329 OUI installer
1.2.2.2 Other Disk Space Considerations
除了由GoldenGate安裝的檔案和二進位制檔案所需的磁碟空間之外，還可以在承載Oracle GoldenGate跟蹤（或小節）的任何系統上額外增加1 GB的磁碟空間。
1.2.2.3 Installing in a Cluster
要將Oracle GoldenGate安裝到叢集環境中，請將Oracle GoldenGate二進位制檔案和檔案作為Oracle使用者安裝到所有叢集節點可用的共享檔案系統上。 有關詳細資訊，請參閱準備在群集中安裝Oracle GoldenGate。
1.2.2.4 Temporary Disk Requirements
預設情況下，Oracle GoldenGate會將資料寫入Oracle GoldenGate安裝目錄的dirtmp子目錄中。 當總快取事務資料超過CACHEMGR引數的CACHESIZE設定時，Extract將開始將快取資料寫入臨時檔案。 快取管理器假定檔案系統上的所有可用空間都可用。 如果存在大型事務大小的事務卷，則該目錄可以快速填滿。 為了防止I / O爭用和與磁碟相關的Extract故障，請將磁碟專用於此目錄。 您可以使用CACHEMGR引數的CACHEDIRECTORY選項為此目錄指定名稱。
作業系統交換磁碟通常比使用Extract寫入臨時檔案更有效。 預設的CACHESIZE設定假定為。 因此，應該有足夠的磁碟空間來解決這個問題，因為只有在超過CACHESIZE的值之後才能將檔案系統名稱空間中的寫事務快取資料提取到臨時檔案。 如果在系統上執行多個"提取"程式，則磁碟需求可能會增加。 當沒有足夠的記憶體來儲存開啟的事務時，Oracle GoldenGate會寫入磁碟。 一旦提交或回滾事務，就將寫入的資料寫入跟蹤檔案，並從記憶體中釋放資料，並且Oracle GoldenGate不再跟蹤該事務。 沒有最低的磁碟要求，因為在每次操作之後提交事務時，這些事務永遠不會寫入磁碟。
1.2.3 Network
記錄您分配給Oracle GoldenGate的埠。 在配置Manager程式時，您將使用引數指定它們。
1.2.4 Operating System Privileges
以下是安裝Oracle GoldenGate並執行程式所需的作業系統中的許可權：
要在UNIX上安裝，安裝Oracle GoldenGate的人員必須具有對Oracle GoldenGate安裝目錄的讀寫許可權。
Oracle GoldenGate Extract，Replicat和Manager程式必須作為具有讀取，寫入和刪除Oracle GoldenGate目錄中的檔案和子目錄的許可權的作業系統使用者。 此外，Manager程式需要許可權來控制其他Oracle GoldenGate程式。
（經典捕捉模式）在經典捕捉模式下，"提取"（Extract）程式將直接讀取重做日誌，並且必須作為具有對線上和存檔的日誌檔案的讀取訪問許可權的作業系統使用者進行操作。 在UNIX系統上，該使用者必須是擁有Oracle例項的組的成員。 如果在本文件中的安裝步驟中將Manager程式作為Windows服務安裝，則必須以管理員身份安裝以分配正確的許可權。 如果無法安裝Manager作為服務，請手動分配對Extract程式的讀訪問許可權，然後始終以管理員身份執行管理器和提取。
將Extract，Replicat和Manager作業系統使用者專用於Oracle GoldenGate。 任何執行Oracle GoldenGate程式的人都可以使用敏感資訊，這取決於資料庫身份驗證的配置方式。
1.2.5 Console Character Sets
您可以使用以下DOS命令在開啟GGSCI會話之前設定控制檯的字符集：
chcp OS character set
1.3 Oracle Universal Installer Requirements for Oracle GoldenGate
1.4 Database Configuration資料庫配置
本節包含特定於Oracle資料庫的Oracle GoldenGate要求。 除非明確指出，否則這兩種捕獲模式都適用。
If you are using the DBMS_LOB.LOADFROMFILE procedure to update a LOB column only and your supplemental log is on all the columns, Integrated Extract captures the key columns and LOB improving performance. Classic Extract captures the all the columns by default. These behaviors do not effect like to like replications. However, with a replication to data warehouse, you may want all the columns for update. If you are converting from Classic Extract to Integrated Extract, you must use one of the following parameters to ensure that the Extract operates correctly:
如果您正在使用DBMS_LOB.LOADFROMFILE過程來更新LOB列，並且您的補充日誌位於所有列上，Integrated Extract將捕獲關鍵列和LOB以提高效能。 Classic Extract預設捕獲所有列。 這些行為並不像喜歡複製一樣。 但是，透過複製到資料倉儲，您可能希望更新所有列。 如果要從Classic Extract轉換為Integrated Extract，則必須使用以下引數之一來確保提取操作正確：
Use KEYCOLS to add all columns (except LOB).
Use LOGALLSUPCOLS to control the writing of supplementally logged columns.
Database user privileges and configuration requirements are explained in “Establishing Oracle GoldenGate Credentials”.
資料庫使用者許可權和配置要求在建立Oracle GoldenGate憑據中有所描述。
If the database is configured to use a bequeath connection, the sqlnet.ora file must contain the bequeath_detach=true setting.
如果資料庫配置為使用bequeath連線，則sqlnet.ora檔案必須包含bequeath_detach = true設定。
To install Oracle GoldenGate in an Oracle Real Application Cluster (RAC) environment, install Oracle GoldenGate on the shared drive(s) that are accessed by the RAC nodes. For more information, see Preparing to Install Oracle GoldenGate Within a Cluster.
要在Oracle Real Application Cluster（RAC）環境中安裝Oracle GoldenGate，請在由RAC節點訪問的共享驅動器上安裝Oracle GoldenGate。 有關詳細資訊，請參閱準備在群集中安裝Oracle GoldenGate。
(Integrated capture mode) Integrated Capture mode makes use of a logmining server on the source system or in a downstream Oracle Database. Refer to My Oracle Support article 1557031.1 for all Oracle Database release bundled patches for Oracle GoldenGate.
（整合捕獲模式）整合捕獲模式使用源系統或下游Oracle資料庫中的登入伺服器。 有關Oracle GoldenGate的所有Oracle資料庫版本捆綁補丁，請參閱我的Oracle支援文章1557031.1。
To use integrated capture with an Oracle 11.2.0.3 source database, download and install the 11.2.0.3 database specific bundled patch required for Integrated Extract.
For more information, see Choosing Capture and Apply Modes.
要使用整合捕獲與Oracle 11.2.0.3源資料庫，請下載並安裝Integrated Extract所需的11.2.0.3資料庫特定的捆綁補丁。有關詳細資訊，請參閱選擇捕獲和應用模式。
Oracle Databases must be in ARCHIVELOG mode so that Extract can process the log files.
Oracle資料庫必須處於ARCHIVELOG模式，以便Extract可以處理日誌檔案。
1.5 Summary of Supported Oracle Data Types and Objects Per Capture Mode 每種捕獲模式支援的Oracle資料型別和物件摘要
table 1-3 summarizes the way that Oracle GoldenGate supports the Oracle data types according to the capture mode that you choose. For more information about capture modes, see Deciding Which Capture Method to Use.
表1-3總結了Oracle GoldenGate根據您選擇的捕獲模式支援Oracle資料型別的方式。 有關捕獲模式的更多資訊，請參閱確定要使用的捕獲方法。
Detailed support information for Oracle data types, objects, and operations starts with Details of Support for Oracle Data Types.
有關Oracle資料型別，物件和操作的詳細支援資訊，請參閱Oracle資料型別支援詳細資訊。
見：
1.6 Details of Support for Oracle Data Types Oracle資料型別支援的詳細資訊
The following outlines details of Oracle data type support by Oracle GoldenGate. Unless otherwise noted, the support applies to both classic and integrated capture mode. For more information about these modes, see Choosing “Capture and Apply Modes”.
以下概述了Oracle GoldenGate支援的Oracle資料型別的詳細資訊。 除非另有說明，否則支援適用於經典和整合捕獲模式。 有關這些模式的更多資訊，請參閱選擇捕獲和應用模式。
1.6.1 ANYDATA Data Types
1.6.1.1 Limitations of Support
Your source database compatibility must be set to 11.2.0.0.0 or higher. Support for named collections and VARRAYs embedded within those data types.
您的源資料庫相容性必須設定為11.2.0.0.0或更高版本。 支援嵌入在這些資料型別中的命名集合和VARRAY。
1.6.2 Numeric Data Types
1.6.2.1 Limitations of Support
The support of the 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.
浮點數的範圍和精度的支援取決於主機。 一般來說，精確度精確到16位有效數字，但您應該檢視資料庫文件以確定預期的近似值。 Oracle GoldenGate可以舍入或截斷超出支援的精度的值。
1.6.3 Character Data Types
1.6.3.1 Limitations of Support
If an extended VARCHAR column is part of unique index or constraint, then direct path inserts to this table may cause Replicat to abend with a warning. Verify that the extended VARCHAR caused the abend by checking all_indexes/all_ind_columns for a unique index or all_cons_columns/all_constraints for a unique constraint. Once you determine that an extended VARCHAR, you can temporarily drop the index or disable the constraint:
如果擴充套件的VARCHAR列是唯一索引或約束的一部分，則直接路徑插入此表可能會導致Replicat退出警告。 透過檢查唯一索引的all_indexes / all_ind_columns來檢查擴充套件VARCHAR是否導致了異常，或者唯一約束的all_cons_columns / all_constraints。 確定擴充套件的VARCHAR後，您可以臨時刪除索引或禁用約束：
For Unique Index:
drop index t2u;
For Unique Constraint:
alter table v32ind modify constraint sys_c0010125 disable;
Extended (32K) VARCHAR2 and NVARCHAR2 columns are supported when Extract is in integrated capture mode. All modes of Replicat support 32K VARCHAR2 and NVARCHAR2 columns. The following limitations apply:
Extract處於整合捕獲模式時，支援擴充套件（32K）VARCHAR2和NVARCHAR2列。 Replicat的所有模式都支援32K VARCHAR2和NVARCHAR2列。 以下限制適用：
Oracle GoldenGate does not support 32K VARCHAR2 and NVARCHAR2 columns as part of a key or unique index, nor as a column in a KEYCOLS clause of the TABLE or MAP parameter. 32K columns cannot be used as row identifiers because they are not supplementally logged even when part of a primary key.
32K columns are not supported as resolution columns in a CDR (conflict resolution and detection) configuration nor as the basis for any other work that requires a column value to be present in the transaction log.
Oracle GoldenGate does not limit the number of 32K columns, but each trail record has a length limit of 4MB for inline records. The number of 32K columns that reaches this limit is approximately 160 columns, but the number of columns also depends on the actual size of the extended VARCHAR2 column.
1.6.4 Multi-byte Character Types 多位元組字元型別
1.6.5 Binary Data Types二進位制資料型別
1.6.6 Date and Timestamp Data Types 日期和時間戳資料型別
1.6.7 Large Object Data Types
1.6.8 XML Data Types
1.6.9 User Defined or Abstract Types 使用者定義或抽象型別
1.6.10 Non-Supported Oracle Data Types 不支援的Oracle資料型別
1.7 Details of Support for Objects and Operations in Oracle DML： Oracle DML中物件和操作的支援細節
This section outlines the Oracle objects and operations that Oracle GoldenGate supports for the capture and replication of DML operations.
本節概述Oracle GoldenGate支援捕獲和複製DML操作的Oracle物件和操作。
1.7.1 Multitenant Container Databases多租戶集裝箱資料庫
Oracle GoldenGate captures from, and delivers to, a multitenant container database. See Configuring Oracle GoldenGate in a Multitenant Container Database for more information about how Oracle GoldenGate supports multitenant container databases.
Oracle GoldenGate從多租戶容器資料庫捕獲並傳遞給多租戶集裝箱資料庫。 有關Oracle GoldenGate如何支援多租戶容器資料庫的更多資訊，請參閱在多租戶容器資料庫中配置Oracle GoldenGate。
1.7.2 Tables, Views, and Materialized Views
Oracle GoldenGate supports the following DML operations made to regular tables, index-organized tables, clustered tables, and materialized views.
Oracle GoldenGate支援對常規表，索引組織表，聚簇表和物化檢視進行的以下DML操作：
INSERT
UPDATE
DELETE
Associated transaction control operations
您可以使用DBA_GOLDENGATE_SUPPORT_MODE資料字典檢視顯示有關Oracle GoldenGate捕獲程式對資料庫中表的支援級別的資訊。 有關更多資訊，請參閱"Oracle資料庫參考"。
1.7.3 Sequences
1.7.4 Non-supported Objects and Operations in Oracle DML
1.8 Details of Support for Objects and Operations in Oracle DDL ：Oracle DDL中物件和操作支援的詳細資訊
This section outlines the Oracle objects and operation types that Oracle GoldenGate supports for the capture and replication of DDL operations. For more information about DDL support, see the following:
本節概述了Oracle GoldenGate支援捕獲和複製DDL操作的Oracle物件和操作型別。 有關DDL支援的更多資訊，請參閱以下內容：
Configuring DDL Support 配置DDL支援
Installing Trigger-Based DDL Capture (Trigger-based capture is required for Oracle releases that are earlier than version 11.2.0.4. If Extract will run in integrated mode against a version 11.2.0.4 or later Oracle Database, the DDL trigger and supporting objects are not required.)
安裝基於觸發器的DDL捕獲（低於版本11.2.0.4的Oracle版本需要基於觸發器的捕獲）。如果Extract將針對11.2.0.4或更高
1.8.1 Supported Objects and Operations in Oracle DDL：Oracle DDL中支援的物件和操作
When the source database is Oracle 11.2.0.4 or later and Extract operates in integrated mode, DDL capture support is integrated into the database logmining server and does not require the use of a DDL trigger. You must set the database parameter compatibility to 11.2.0.4.0. In integrated capture mode, Extract supports DDL that includes password-based column encryption
當源資料庫是Oracle 11.2.0.4或更高版本，Extract以整合模式執行時，DDL捕獲支援整合到資料庫登入伺服器中，不需要使用DDL觸發器。 您必須將資料庫引數相容性設定為11.2.0.4.0。 在整合捕獲模式下，Extract支援包含基於密碼的列加密的DDL
注意：Password-based column encryption in DDL is not supported in classic capture mode.
The following additional statements apply to both integrated and classic capture modes with respect to DDL support.以下附加說明適用於DDL支援的整合和經典捕獲模式。
Oracle DDL複製支援所有Oracle GoldenGate拓撲配置。在包含相同後設資料的兩個（而且只有兩個）資料庫之間支援Oracle DDL的主動（雙向）複製。Oracle GoldenGate支援以下物件上的DDL：
對於以下Oracle資料庫物件，整合的Extract支援Oracle DDL的基於Oracle版本的重新定義（EBR）資料庫複製
Oracle GoldenGate支援高達4 MB的DDL操作。 Oracle GoldenGate以位元組為單位測量DDL語句的大小，而不是字元。 此大小限制包括包，過程和功能。 DDL支援的實際大小限制是近似值，因為大小不僅包括語句文字，還包括Oracle GoldenGate維護開銷，這取決於物件名稱的長度，DDL型別以及內部保留DDL記錄的其他特性 。
Oracle GoldenGate支援全域性臨時表（GTT）DDL操作對Extract可見，以便它們可以被複制。 您必須將DDLOPTIONS引數設定為啟用此操作，因為它未被預設設定。
Oracle GoldenGate支援用於NOUSERID和TRANLOGOPTIONS GETCTASDML的整合字典。 這意味著Extract將從LogMiner字典而不是DDL觸發器獲取物件後設資料，而不查詢字典物件。 當源資料庫相容性引數大於或等於11.2.0.4時，Oracle GoldenGate將自動使用整合字典，並使用整合提取。
Classic Extract不支援整合字典功能。
當在Oracle GoldenGate版本12.2.x中使用整合字典和跟蹤格式時，如果Oracle資料庫版本早於12.1.0.2，則Integrated Capture需要將Logminer補丁應用於挖掘資料庫。
1.8.2 Non-supported Objects and Operations in Oracle DDL：Oracle DDL中不支援的物件和操作
These statements apply to integrated and classic capture modes.
1.8.2.1 Excluded Objects
1.8.2.2 Other Non-supported DDL
1.9 Supported and Non-supported Object Names 支援的和不支援的物件名稱
Oracle object names are case insensitive by default, but can be made case-sensitive with the use of double quotes. Oracle GoldenGate supports Oracle case-sensitivity. For information about Oracle GoldenGate support for object names and case, see Administering Oracle GoldenGate for Windows and UNIX.
Oracle物件名稱預設情況下不區分大小寫，但可以使用雙引號使其區分大小寫。 Oracle GoldenGate支援Oracle區分大小寫。 有關Oracle GoldenGate對物件名稱和大小寫的支援的資訊，請參閱管理Oracle GoldenGate for Windows和UNIX。
2 Installing Oracle GoldenGate安裝Oracle GoldenGate
本章包括首次安裝Oracle GoldenGate的說明。 安裝Oracle GoldenGate安裝執行和管理處理所需的所有元件（不包括其他供應商所需的任何元件，如驅動程式或庫），並安裝Oracle GoldenGate實用程式。 本章包括以下部分：
Understanding and Obtaining the Oracle GoldenGate Distribution
Setting ORACLE_HOME and ORACLE_SID
Setting Library Paths for Dynamic Builds on UNIX
Preparing to Install Oracle GoldenGate Within a Cluster
Installing Oracle GoldenGate
Integrating Oracle GoldenGate into a Cluster
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.這些說明首次用於安裝Oracle GoldenGate。 此外，它們用於下載新版本的Oracle GoldenGate的基本版本。
To download and install subsequent patches to the base release, go to the Patches and Updates tab of My Oracle Support at:
To upgrade Oracle GoldenGate from one version to another, follow the upgrade instructions at:
2.1 Understanding and Obtaining the Oracle GoldenGate Distribution 瞭解和獲取Oracle GoldenGate發行版
For complete information about how to obtain Oracle Fusion Middleware software, see "Understanding and Obtaining Product Distributions" in Planning an Installation of Oracle Fusion Middleware.
To download the Oracle WebLogic Server and Coherence software for development or evaluation, see the following location on the Oracle Technology Network (OTN):
For more information about locating and downloading Oracle Fusion Middleware products, see the Oracle Fusion Middleware Download, Installation, and Configuration Readme Files on OTN.
To obtain Oracle GoldenGate follow these steps:
1.Go to Oracle Technology Network.
2.Find the Oracle GoldenGate 12c (12.2.0.1) release and download the ZIP file onto your system.
2.2 Setting ORACLE_HOME and ORACLE_SID 設定ORACLE_HOME和ORACLE_SID
確保將ORACLE_HOME和ORACLE_SID系統環境變數設定為正確的Oracle例項。 連線到資料庫時，Oracle GoldenGate程式引用它們。
If there is one instance of Oracle Database on the system, set the ORACLE_HOME and ORACLE_SID environment variables at the system level. If you cannot set them that way, use the following SETENV statements in the parameter file of every Extract and Replicat group that will be connecting to the instance. The SETENV parameters override the system settings and allow the Oracle GoldenGate process to set the variables at the session level when it connects to the database.
如果系統上有一個Oracle資料庫例項，請在系統級別設定ORACLE_HOME和ORACLE_SID環境變數。 如果不能以這種方式設定，請在將連線到例項的每個"提取"和"複製"組的引數檔案中使用以下SETENV語句。 SETENV引數覆蓋系統設定，並允許Oracle GoldenGate程式在連線到資料庫時將變數設定為會話級別。
SETENV (ORACLE_HOME = "path to Oracle home location")
SETENV (ORACLE_SID = "SID")
If there are multiple Oracle instances on the system with Extract and Replicat processes connecting to them, you will need to use a SETENV statement in the parameter file of each process group. As input to the SETENV parameter, use the ORACLE_HOME and ORACLE_SID environment variables to point Oracle GoldenGate to the correct Oracle instance. For example, the following shows parameter files for two Extract groups, each capturing from a different Oracle instance.
如果系統上有多個連線了Extract和Replicat程式的Oracle例項，則需要在每個程式組的引數檔案中使用SETENV語句。 作為SETENV引數的輸入，使用ORACLE_HOME和ORACLE_SID環境變數將Oracle GoldenGate指向正確的Oracle例項。 例如，以下顯示兩個"提取"組的引數檔案，每個從不同的Oracle例項捕獲。
Group 1:
EXTRACT ora9a
SETENV (ORACLE_HOME = "/home/oracle/ora/product")
SETENV (ORACLE_SID = "oraa")
USERIDALIAS tiger1
RMTHOST sysb
RMTTRAIL /home/ggs/dirdat/rt
TABLE hr.emp;
TABLE hr.salary;
Group 2:
EXTRACT orab
SETENV (ORACLE_HOME = "/home/oracle/ora/product")
SETENV (ORACLE_SID = "orab")
USERIDALIAS tiger1
RMTHOST sysb
RMTTRAIL /home/ggs/dirdat/st
TABLE fin.sales;
TABLE fin.cust;
2.3 Setting Library Paths for Dynamic Builds on UNIX：在UNIX上設定動態構建的庫路徑
Oracle GoldenGate使用共享庫。 在UNIX系統上安裝Oracle GoldenGate時，在執行GGSCI或任何其他Oracle GoldenGate程式之前，以下內容必須為真：
1.確保將資料庫庫新增到系統的共享庫環境變數中。 此過程通常在資料庫安裝時執行。 如果您有任何問題，請諮詢資料庫管理員。
當Oracle GoldenGate在與資料庫相同的伺服器上執行時，以下所有內容必須為64位：Oracle library versions；Oracle GoldenGate version；Database versions；
當Oracle GoldenGate透過SQL * Net遠端連線到資料庫伺服器時，需要以下內容：
Replicat: The Oracle client library and the Oracle GoldenGate build must have the same Oracle version, bit type (64-bit or IA64), and operating system version.
Extract: The Oracle client library and the Oracle GoldenGate build must have the same Oracle version, bit type (64-bit or IA64), and operating system version. In addition, both operating systems must be the same endian.
2.如果您將在UNIX系統上從Oracle GoldenGate安裝目錄外部執行Oracle GoldenGate程式
(Optional) Add the Oracle GoldenGate installation directory to the PATH environment variable.
(可選)將Oracle GoldenGate安裝目錄新增到PATH環境變數中。
(Required) Add the Oracle GoldenGate installation directory to the shared-libraries environment variable.
(必需)將Oracle GoldenGate安裝目錄新增到共享庫環境變數中。
Example 2-2 To Set the Variables in Bourne Shell:
export PATH=installation_directory:$PATH
export shared_libraries_variable=absolute_path_of_installation_directory:$shared_libraries_variable
Where shared libraries variable is one of the variables shown in Table 2-1:共享庫變數是表2-1中顯示的變數之一
Platform Environment variable
LINUX LD_LIBRARY_PATH
注意：
To view the libraries that are required by an Oracle Oracle GoldenGate process, use the ldd goldengate_process shell command before starting the process. This command also shows an error message for any that are missing.
要檢視Oracle Oracle GoldenGate程式所需的庫，請在啟動該程式之前使用ldd goldengate_process shell命令。 此命令還顯示任何缺少的錯誤訊息。
2.4 Preparing to Install Oracle GoldenGate Within a Cluster 在叢集中安裝Oracle GoldenGate
本主題介紹了在叢集環境中安裝Oracle GoldenGate時的安裝要求。 Oracle GoldenGate可以與任何能夠自動進行故障切換的叢集管理解決方案配合使用。 Oracle Clusterware解決方案提供了能夠與或不與Oracle RAC資料庫一起使用的優點，從而可以包括執行Oracle GoldenGate的任何非資料庫伺服器。
2.4.1 Deciding Where to Install Oracle GoldenGate Binaries and Files in the Cluster
2.4.2 Example Oracle Cluster Storage
2.5 Installing Oracle GoldenGate 安裝Oracle GoldenGate
2.5.1 Performing an Interactive Installation with OUI 使用OUI執行互動式安裝
OUI安裝在資料庫版本在11g及以上才支援
The interactive installation provides a graphical user interface that prompts for the required installation information. These instructions apply to new installations as well as upgrades. However, to perform an upgrade to Oracle GoldenGate, follow the instructions in Upgrading Oracle GoldenGate for Windows and UNIX, which includes a prompt to run OUI at the appropriate time.
互動式安裝提供了一個圖形使用者介面，提示所需的安裝資訊。 這些說明適用於新的安裝和升級。 但是，要執行升級到Oracle GoldenGate，請按照升級Oracle GoldenGate for Windows和UNIX的說明進行操作，其中包括在適當時間執行OUI的提示。
2.5.2 Performing a Silent Installation with OUI 使用OUI執行靜默安裝
You perform a silent installation by running a response file. You can create a response file by selecting the Save Response File option during an interactive OUI session or by editing a template, as shown in Example 2-4. To run a response file, issue the following command.
您可以透過執行響應檔案執行靜默安裝。 您可以透過在互動式OUI會話期間選擇儲存響應檔案選項或透過編輯模板來建立響應檔案，如示例2-4所示。 要執行響應檔案，請發出以下命令。
./runIntailler -silent -nowait -responseFile path_to_file
2.6 Integrating Oracle GoldenGate into a Cluster
If you installed Oracle GoldenGate in a cluster, take the following steps to integrate Oracle GoldenGate within the cluster solution.
For more information about installing and using Oracle GoldenGate in a cluster, see the Oracle GoldenGate with Oracle Real Application Clusters Configuration white paper
2.6.1 General Requirements in a Cluster
2.6.2 Adding Oracle GoldenGate as a Windows Cluster Resource
3 Preparing the Database for Oracle GoldenGate 準備Oracle GoldenGate資料庫
This chapter contains steps to take so that the source Oracle Database is configured properly to support the capture of transactional changes.
本章包含採取的步驟，以便正確配置源Oracle資料庫以支援事務性更改的捕獲。
This chapter includes the following sections:本章包括以下部分
Configuring Connections for Integrated Processes
Configuring Logging Properties
Enabling Oracle GoldenGate in the Database
Setting Flashback Query
Managing Server Resources
3.1 Configuring Connections for Integrated Processes 組態整合過程的連線
If you will be using integrated capture and integrated Replicat, each requires a dedicated server connection in the tnsnames.ora file. You direct the processes to use these connections with the USERID or USERIDALIAS parameter in the Extract and Replicat parameter files when you configure those processes.
如果您將使用整合捕獲和整合的Replicat，則每個都需要tnsnames.ora檔案中的專用伺服器連線。 在配置這些程式時，您可以使用"提取和複製"引數檔案中的USERID或USERIDALIAS引數來指導程式使用這些連線。
示例：
The following is an example of the dedicated connection required for integrated capture (Extract) and integrated Replicat.
TEST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = test2)(PORT = 1521))
)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = test)
)
)
The following are the security options for specifying the connection string in the Extract or Replicat parameter file.
Password encryption method:
USERID intext@test, PASSWORD mypassword
Credential store method:
USERIDALIAS ext
In the case of USERIDALIAS, the alias ext is stored in the Oracle GoldenGate credential store with the actual connection string, as in the following example:
GGSCI> INFO CREDENTIALSTORE DOMAIN support
Domain: Support
Alias: ext
Userid: intext@test
For more information about specifying database connection information in the parameter file, see "Administering Oracle GoldenGate for Windows and UNIX".
3.2 Configuring Logging Properties 配置日誌記錄屬性
Oracle GoldenGate依賴重做日誌來捕獲複製源事務所需的資料。 在啟動Oracle GoldenGate處理之前，必須正確配置源系統上的Oracle重做日誌。
本節介紹適用於Oracle GoldenGate的以下日誌記錄級別。 您使用的日誌記錄級別取決於您使用的Oracle GoldenGate功能或功能。
3.2.1 Enabling Minimum Database-level Supplemental Logging 啟用最低資料庫級補充日誌記錄
Oracle strongly recommends putting the Oracle source database into forced logging mode. Forced logging mode forces the logging of all transactions and loads, overriding any user or storage settings to the contrary. This ensures that no source data in the Extract configuration gets missed.
Oracle強烈建議將Oracle源資料庫置於強制登入模式。 強制日誌記錄模式強制記錄所有事務和載入，覆蓋任何使用者或儲存設定相反。 這樣可以確保"提取"配置中的源資料不會丟失。
In addition, minimal supplemental logging, a database-level option, is required for an Oracle source database when using Oracle GoldenGate. This adds row chaining information, if any exists, to the redo log for update operations.
此外，使用Oracle GoldenGate時，Oracle資料庫需要最少的補充日誌記錄（資料庫級別選項）。 這將新增行連結資訊（如果有的話）到重做日誌以進行更新操作。
Database-level primary key (PK) and unique index (UI) logging is strongly discouraged because of the excessive additional overhead it creates on tables outside of replication. Unless those logging options are required for business purposes, you only need to enable minimal supplemental logging at the database level and force logging for Oracle GoldenGate.
強烈不鼓勵資料庫級主鍵（PK）和唯一索引（UI）日誌記錄，因為它在複製之外的表上建立了額外的額外開銷。 除非這些日誌選項是商業目的需要的，否則您只需要在資料庫級別啟用最少的補充日誌記錄，並強制Oracle GoldenGate的日誌記錄。
檢查是否開啟最小補充日誌和force logging：
SELECT supplemental_log_data_min, force_logging FROM v$database;
開啟最小補充日誌和force logging：
ALTER DATABASE ADD SUPPLEMENTAL LOG DATA;
ALTER DATABASE FORCE LOGGING;
3.2.2 Enabling Schema-level Supplemental Logging 啟用schema級補充日誌記錄
Oracle GoldenGate supports schema-level supplemental logging. Schema-level logging is required for an Oracle source database when using the Oracle GoldenGate DDL replication feature. In all other use cases, it is optional, but then you must use table-level logging instead (see Enabling Table-level Supplemental Logging).
Oracle GoldenGate支援Schema級補充日誌記錄.使用Oracle GoldenGate DDL複製功能時，Oracle源資料庫需要Schema級日誌記錄。在所有其他用例中,它是可選的,但是您必須使用表級日誌記錄（請參閱啟用表級補充日誌記錄）。
注意：Oracle強烈建議使用模式級日誌記錄而不是表級日誌記錄，因為它可以確保新增到模式中的任何新表符合萬用字元規範。
perform the following steps on the source system to enable schema-level supplemental logging.
1.Apply Oracle Patch 13794550 to the source Oracle Database if the version is earlier than 11.2.0.2.
2.Run GGSCI on the source system.
3.Issue the DBLOGIN command with the alias of a user in the credential store who has privilege to enable schema-level supplemental logging.
DBLOGIN USERIDALIAS alias
See Reference for Oracle GoldenGate for Windows and UNIX for more information about DBLOGIN and additional options.
4.Issue the ADD SCHEMATRANDATA command for each schema for which you want to capture data changes with Oracle GoldenGate.
ADD SCHEMATRANDATA schema [ALLCOLS | NOSCHEDULINGCOLS]
Where:
Without options, ADD SCHEMATRANDATA schema enables the unconditional supplemental logging on the source system of the primary key and the conditional supplemental logging of all unique key(s) and foreign key(s) of all current and future tables in the given schema. Unconditional logging forces the primary key values to the log whether or not the key was changed in the current operation. Conditional logging logs all of the column values of a foreign or unique key if at least one of them was changed in the current operation. The default is optional to support nonintegrated Replicat but is required to support integrated Replicat because primary key, unique keys, and foreign keys must all be available to the inbound server to compute dependencies. For more information about integrated Replicat, see Deciding Which Apply Method to Use.
ALLCOLS can be used to enable the unconditional supplemental logging of all of the columns of a table and applies to all current and future tables in the given schema. Use to support integrated Replicat when the source and target tables have different scheduling columns. (Scheduling columns are the primary key, the unique key, and the foreign key.)
NOSCHEDULINGCOLS logs only the values of the primary key and all valid unique indexes for existing tables in the schema and new tables added later. This is the minimal required level of schema-level logging and is valid only for Replicat in nonintegrated mode.
In the following example, the command enables default supplemental logging for the finance schema.
ADD SCHEMATRANDATA finance
In the following example, the command enables the supplemental logging only for the primary key and valid unique indexes for the hr schema.
ADD SCHEMATRANDATA hr NOSCHEDULINGCOLS
See Reference for Oracle GoldenGate for Windows and UNIX for more information about ADD SCHEMATRANDATA.
3.2.3 Enabling Table-level Supplemental Logging 啟用表級補充日誌
在以下情況下，在源系統上啟用表級補充日誌記錄：在不使用schema級日誌記錄時啟用所需級別的日誌記錄（請參閱啟用schema級補充日誌記錄）;防止為任何給定的表記錄主鍵; 在表級別記錄非關鍵列值，以支援特定的Oracle GoldenGate功能，例如過濾和衝突檢測和解析邏輯。
Perform the following steps on the source system to enable table-level supplemental logging or use the optional features of the command.
1.Run GGSCI on the source system.
2.Issue the DBLOGIN command using the alias of a user in the credential store who has privilege to enable table-level supplemental logging.
DBLOGIN USERIDALIAS alias
See Reference for Oracle GoldenGate for Windows and UNIX for more information about DBLOGIN and additional options.
3.Issue the ADD TRANDATA command.
ADD TRANDATA [container.]schema.table [, COLS (columns)] [, NOKEY] [, ALLCOLS | NOSCHEDULINGCOLS]
Where:
container is the name of the root container or pluggable database if the table is in a multitenant container database.
schema is the source schema that contains the table.
table is the name of the table. See Administering Oracle GoldenGate for Windows and UNIX for instructions for specifying object names.
ADD TRANDATA without other options automatically enables unconditional supplemental logging of the primary key and conditional supplemental logging of unique key(s) and foreign key(s) of the table. Unconditional logging forces the primary key values to the log whether or not the key was changed in the current operation. Conditional logging logs all of the column values of a foreign or unique key if at least one of them was changed in the current operation. The default is optional to support nonintegrated Replicat (see also NOSCHEDULINGCOLS) but is required to support integrated Replicat because primary key, unique keys, and foreign keys must all be available to the inbound server to compute dependencies. For more information about integrated Replicat, see Deciding Which Apply Method to Use.
沒有其他選項的ADD TRANDATA可以自動啟用主鍵的無條件補充日誌記錄和條件補充日誌記錄表的唯一鍵和外來鍵。 無條件日誌記錄會將主鍵值強制到日誌，無論在當前操作中鍵是否更改。 條件記錄記錄外部或唯一鍵的所有列值，如果當前操作中至少有一個值被更改。 預設值是可選的，以支援非整合的Replicat（另見NOSCHEDULINGCOLS），但是需要支援整合的Replicat，因為主鍵，唯一鍵和外來鍵都必須可用於入站伺服器以計算依賴關係。 有關整合的Replicat的更多資訊，請參閱確定使用哪種應用方法。
ALLCOLS enables the unconditional supplemental logging of all of the columns of the table. Use to support integrated Replicat when the source and target tables have different scheduling columns. (Scheduling columns are the primary key, the unique key, and the foreign key.)
ALLCOLS可以對錶的所有列進行無條件的補充記錄。 當源表和目標表具有不同的排程列時，用於支援整合的Replicat。 （排程列是主鍵，唯一鍵和外來鍵）。
NOSCHEDULINGCOLS is valid for Replicat in nonintegrated mode only. It issues an ALTER TABLE command with an ADD SUPPLEMENTAL LOG DATA ALWAYS clause that is appropriate for the type of unique constraint that is defined for the table, or all columns in the absence of a unique constraint. This command satisfies the basic table-level logging requirements of Oracle GoldenGate when schema-level logging will not be used. See Ensuring Row Uniqueness in Source and Target Tables for how Oracle GoldenGate selects a key or index.
NOSCHEDULINGCOLS僅在非整合模式下對Replicat有效。 它使用ADD SUPPLEMENTAL LOG DATA ALWAYS子句發出一個ALTER TABLE命令，該子句適用於為表定義的唯一約束型別，或不存在唯一約束的所有列。 當不使用模式級日誌記錄時，此命令滿足Oracle GoldenGate的基本表級日誌記錄要求。 請參閱確定源和目標表中的行唯一性，以瞭解Oracle GoldenGate如何選擇金鑰或索引。
COLS columns logs non-key columns that are required for a KEYCOLS clause or for filtering and manipulation. The parentheses are required. These columns will be logged in addition to the primary key unless the NOKEY option is also present.
COLS列記錄KEYCOLS子句所需的非鍵列或過濾和操作。 括號是必需的。 這些列除了主鍵之外還將被記錄，除非NOKEY選項也存在。
NOKEY prevents the logging of the primary key or unique key. Requires a KEYCOLS clause in the TABLE and MAP parameters and a COLS clause in the ADD TRANDATA command to log the alternate KEYCOLS columns.
NOKEY防止記錄主鍵或唯一鍵。 需要TABLE和MAP引數中的KEYCOLS子句以及ADD TRANDATA命令中的COLS子句才能記錄備用KEYCOLS列。
4.If using ADD TRANDATA with the COLS option, create a unique index for those columns on the target to optimize row retrieval. If you are logging those columns as a substitute key for a KEYCOLS clause, make a note to add the KEYCOLS clause to the TABLE and MAP statements when you configure the Oracle GoldenGate processes.
如果使用帶有COLS選項的ADD TRANDATA，則為目標上的那些列建立唯一的索引，以最佳化行檢索。 如果您正在將這些列作為KEYCOLS子句的替代鍵進行記錄，請在配置Oracle GoldenGate程式時，記下將KEYCOLS子句新增到TABLE和MAP語句。
See Reference for Oracle GoldenGate for Windows and UNIX for more information about ADD TRANDATA.
3.3 Enabling Oracle GoldenGate in the Database 在資料庫中啟用Oracle GoldenGate
必須為Oracle 11.2.0.4或更高版本的資料庫顯式啟用支援Oracle GoldenGate捕獲和應用所需的資料庫服務。 這是Extract和Replicat的所有模式所必需的。
要啟用Oracle GoldenGate，請設定以下資料庫初始化引數。 Oracle RAC中的所有例項必須具有相同的設定。
ENABLE_GOLDENGATE_REPLICATION =true
For more information about this parameter, see Oracle Database Reference.
3.4 Setting Flashback Query 設定閃回查詢
To process certain update records, Extract fetches additional row data from the source database. Oracle GoldenGate fetches data for the following:
User-defined types
Nested tables
XMLType objects
By default, Oracle GoldenGate uses Flashback Query to fetch the values from the undo (rollback) tablespaces. That way, Oracle GoldenGate can reconstruct a read-consistent row image as of a specific time or SCN to match the redo record.
預設情況下，Oracle GoldenGate使用Flashback Query從undo（rollback）表空間中獲取值。 這樣，Oracle GoldenGate可以根據特定時間或SCN重建一個讀取一致的行影像，以匹配重做記錄。
For best fetch results, configure the source database as follows:為獲得最佳提取結果，請按如下方式配置源資料庫
1.透過設定Oracle初始化引數UNDO_MANAGEMENT和UNDO_RETENTION來設定足夠的重做保留次數
2.使用以下公式計算undo表空間中所需的空間。
undo_space = UNDO_RETENTION * UPS + overhead
Use the system view V$UNDOSTAT to estimate UPS and overhead.
3.對於包含LOB的表，請執行以下操作之一：
Set the LOB storage clause to RETENTION. This is the default for tables that are created when UNDO_MANAGEMENT is set to AUTO；
If using PCTVERSION instead of RETENTION, set PCTVERSION to an initial value of 25. You can adjust it based on the fetch statistics that are reported with the STATS EXTRACT command (see Table 3-2). If the value of the STAT_OPER_ROWFETCH CURRENTBYROWID or STAT_OPER_ROWFETCH_CURRENTBYKEY field in these statistics is high, increase PCTVERSION in increments of 10 until the statistics show low values.
4.Grant either of the following privileges to the Oracle GoldenGate Extract user:
GRANT FLASHBACK ANY TABLE TO db_user：
GRANT FLASHBACK ON schema.table TO db_user
3.5 Managing Server Resources 管理伺服器資源
在整合模式下，Extract與源資料庫中的底層日誌伺服器進行互動，Replicat與目標資料庫中的入站伺服器進行互動。 本節提供管理這些伺服器所使用的共享記憶體的指導。
伺服器使用的共享記憶體來自資料庫中系統全域性區域（SGA）的Streams池部分。 因此，您必須將資料庫初始化引數STREAMS_POOL_SIZE設定得足夠高，以保持足夠的記憶體可用於您希望以整合模式執行的Extract和Replicat程式數。 請注意，Streams池也被資料庫的其他元件（如Oracle Streams，Advanced Queuing和Datapump匯出/匯入）使用，因此在確定Oracle GoldenGate的Streams池時，請務必考慮它們。
預設情況下，一個整合捕獲提取請求登入伺服器以MAX_SGA_SIZE為1GB的行數執行，並且PARALLELISM為2.因此，如果在同一資料庫例項中以整合捕獲模式執行三個提取，則至少需要3 GB的記憶體 到Streams池。 作為最佳做法，可以保留25％的Streams池。 例如，如果整合捕獲模式中有三個提取，請將STREAMS_POOL_SIZE設定為以下：
3 GB + (3 GB * 0.25) = 3.75 GB
4. Establishing Oracle GoldenGate Credentials 建立Oracle GoldenGate證照
This chapter provides guidelines for creating database users for the processes that will interact with the database, assigning the correct privileges, and securing the credentials from unauthorized use.
本章提供了為與資料庫進行互動的過程建立資料庫使用者的準則，分配正確的許可權以及保護憑據以防止未經授權的使用。
This chapter includes the following sections:本章包括以下部分：
Assigning Credentials to Oracle GoldenGate
Securing the Oracle GoldenGate Credentials
4.1 Assigning Credentials to Oracle GoldenGate
The Oracle GoldenGate processes require one or more database credentials with the correct database privileges for the database version, database configuration, and Oracle GoldenGate features that you are using. Create a source database user and a target database user, each one dedicated to Oracle GoldenGate on the source and target systems. The assigned user can be the same user for all of the Oracle GoldenGate processes that must connect to a source or target Oracle Database.
Oracle GoldenGate程式需要一個或多個資料庫憑據，以及正在使用的資料庫版本，資料庫配置和Oracle GoldenGate功能的正確資料庫許可權。 建立源資料庫使用者和目標資料庫使用者，每個使用者都在源和目標系統上專用於Oracle GoldenGate。 對於必須連線到源或目標Oracle資料庫的所有Oracle GoldenGate程式，分配的使用者可以是相同的使用者。
The following sections outline the Oracle GoldenGate processes that require user credentials:
Extract User
Replicat User
Other Oracle GoldenGate Users
4.1.1 Extract User
The Extract user performs metadata queries on the source database and fetches data from the source tables when needed. In a local mining deployment of integrated capture, this user also creates, alters, and connects to the logmining server and receives logical change records (LCR) from it. (See Deciding Which Capture Method to Use for more information about capture modes.)
If the source database is a multitenant container database, the Extract user must be a common user and must log into the root container. See Configuring Oracle GoldenGate in a Multitenant Container Database for more information.
You need to assign an additional user if Extract will be operating in integrated capture mode and you are using a downstream mining database. This user will be the mining user and is created in the downstream database. The mining user creates, alters, and connects to the logmining server on the mining database, and it receives logical change records (LCR) from it. This user can be the same as the source Extract user or different. Choose the name of the mining user carefully. Once created by this user, the database logmining server cannot be altered or used by another user. See Configuring a Downstream Mining Database for more information about configuring downstream mining.
4.1.2 Replicat User
The Replicat user creates the Replicat checkpoint table (if used) and applies DML and DDL operations through Oracle Call Interface or through a database inbound server, depending on the Replicat mode. (See Deciding Which Apply Method to Use for more information about Replicat modes.)
Replicat使用者建立Replicat檢查點表（如果使用），並根據Replicat模式透過Oracle呼叫介面或資料庫入站伺服器應用DML和DDL操作。 （有關複製模式的更多資訊，請參閱確定使用哪種應用方法。）
4.1.3 Other Oracle GoldenGate Users
A user is required in the source database for the Manager process if you are using Oracle GoldenGate DDL support. This user performs maintenance on the Oracle GoldenGate database objects that support DDL capture.
如果您正在使用Oracle GoldenGate DDL支援，則需要在源資料庫中為Manager程式使用使用者。 此使用者對支援DDL捕獲的Oracle GoldenGate資料庫物件執行維護。
4.1.4 Granting the Appropriate User Privileges 授予適當的使用者許可權
The user privileges that are required for Oracle GoldenGate depend on the database version and the Extract or Replicat process mode. For more information about process modes, see Choosing Capture and Apply Modes.
4.1.4.1 Oracle 11.2.0.4 or Later Database Privileges
4.1.4.2 Oracle 11.2.0.3 or Earlier Database Privileges
4.1.4.3 About the dbms_goldengate_auth.grant_admin_privilege Package
Most of the privileges that are needed for Extract and Replicat to operate in classic and integrated mode are granted through the dbms_goldengate_auth.grant_admin_privilege package.
Extract和Replicat以經典和整合模式執行所需的大部分許可權透過dbms_goldengate_auth.grant_admin_privilege包進行授予。
4.1.4.4 Optional Grants for dbms_goldengate_auth.grant_admin_privilege
Additional grants can be added to dbms_goldengate_auth.grant_admin_privilege to support the optional features shown in Table 4-3.
4.2 Securing the Oracle GoldenGate Credentials
To preserve the security of your data, and to monitor Oracle GoldenGate processing accurately, do not permit other users, applications, or processes to log on as, or operate as, an Oracle GoldenGate database user.
為了保持資料的安全性，並準確監控Oracle GoldenGate處理，不允許其他使用者，應用程式或程式以Oracle GoldenGate資料庫使用者身份登入或操作。
Oracle GoldenGate provides different options for securing the login credentials assigned to Oracle GoldenGate processes. The recommended option is to use a credential store. You can create one credential store and store it in a shared location where all installations of Oracle GoldenGate can access it, or you can create a separate one on each system where Oracle GoldenGate is installed.
Oracle GoldenGate提供了不同的選項來保護分配給Oracle GoldenGate程式的登入憑據。 推薦的選項是使用憑證儲存。 您可以建立一個憑據儲存，並將其儲存在Oracle GoldenGate的所有安裝可以訪問的共享位置，也可以在安裝了Oracle GoldenGate的每個系統上建立一個單獨的憑據儲存。
The credential store stores the user name and password for each of the assigned Oracle GoldenGate users. A user ID is associated with one or more aliases, and it is the alias that is supplied in commands and parameter files, not the actual user name or password. The credential file can be partitioned into domains, allowing a standard set of aliases to be used for the processes, while allowing the administrator on each system to manage credentials locally.
憑據儲存儲存每個分配的Oracle GoldenGate使用者的使用者名稱和密碼。 使用者ID與一個或多個別名相關聯，它是在命令和引數檔案中提供的別名，而不是實際的使用者名稱或密碼。 可以將憑據檔案分割槽為域，允許將一組標準的別名用於程式，同時允許每個系統上的管理員在本地管理憑據。
See “Administering Oracle GoldenGate for Windows and UNIX” for more information about creating a credential store and adding user credentials.
有關建立憑據儲存和新增使用者憑據的更多資訊，請參閱管理適用於Windows和UNIX的Oracle GoldenGate。
來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/31397003/viewspace-2146461/，如需轉載，請註明出處，否則將追究法律責任。
相關文章
- oracle 歸檔日誌的小知識點Oracle
- ORACLE基本知識Oracle
- 面試官: 我必問的容器知識點!面試
- oracle listener工具知識Oracle
- oracle知識碎記Oracle
- Oracle知識小記Oracle
- Oracle 基本知識（轉）Oracle
- oracle 基礎知識Oracle
- JAVA檔案操作知識Java
- Oracle 相關知識點Oracle
- oracle awr相關知識Oracle
- [轉] Oracle RAC知識索引Oracle索引
- Oracle鎖基礎知識Oracle
- 面試官：你瞭解es6的知識嗎？面試
- 【ORACLE】Oracle繫結變數知識梳理Oracle變數
- Oracle相關基礎知識Oracle
- Oracle臨時表相關知識Oracle
- Oracle LOB儲存知識(zt)Oracle
- Oracle表空間小知識Oracle
- Oracle知識拾漏兩則Oracle
- oracle rba一些小知識Oracle
- Oracle Directory目錄的知識Oracle
- Oracle Data Guard 理論知識Oracle
- Oracle GoldenGate DirectorOracleGo
- oracle goldengate 配置OracleGo
- 【GoldenGate】Oracle GoldenGate(三) DDL同步配置GoOracle
- 用python生成oracle goldengate複製配置檔案PythonOracleGo
- Oracle GoldenGate同步服務歸檔空間維護OracleGo
- [基礎知識] Redis 配置檔案Redis
- oracle dba需要哪些非oracle專業知識Oracle
- 【GoldenGate】Oracle GoldenGate(二) 雙向同步配置GoOracle
- Oracle 選擇題知識點整理Oracle
- 【CURSOR】Oracle 遊標 （cursor）知識梳理Oracle
- 【INDEX】Oracle 索引常見知識梳理IndexOracle索引
- Oracle-SQL知識詳解（一）OracleSQL
- Oracle database 補丁知識介紹OracleDatabase
- oracle事務知識點小結Oracle
- ORACLE字符集基礎知識Oracle