This post provides sample example of Oracle GoldenGate parameter files that can be used to configure Oracle GoldenGate replication setup inline with recommended best practices. The example is generic and can serve as a starting point for a more customized Oracle GoldenGate implementation.
Extract Process
The extract process of Oracle GoldenGate is used to perform change data capture from the source database. The extract is used to synchronize data that is read from the online transaction log (in Oracle the online redo logs) or the associated archive logs. The data that is extracted, when configured for change synchronization, from the source database is then stored until it receives either a commit or rollback. On a commit, the extract persists the transaction to disk where it is stored in a series of files known as a trail file. Committed transactions will be stored in a trail file in sequentially organized transaction units. Once transactions are persisted to disk in a trail file, the transaction can be shipped using standard TCP/IP protocols.
Process name: Extract
Description: The Extract process captures either full data records or transactional data changes, depending on configuration parameters, and then sends the data to a target system to be applied to target tables or processed further by another process, such as a load utility.
Extract parameter file (Sample)
-- ################################################################### -- Runcmd: ADD EXTRACT [extract name], TRANLOG, BEGIN NOW -- Runcmd: ADD EXTTRAIL [extract trail path/two character trail id] , -- EXTRACT [extract name], Megabytes [n] -- Name of the extract process. Limited to 8 charecters. EXTRACT [Extract name] -- DB environment settings SETENV (ORACLE_HOME = "[Oracle home path]" ) SETENV (ORACLE_SID="[Oracle sid]") -- OGG database user login USERID [username] password [encrypted password], encryptkey default -- Local trail info EXTTRAIL [extract trail path/two character trail id] -- Prevent data looping. This is generally used in bi-directional -- configuration TRANLOGOPTIONS EXCLUDEUSER [Replicat username] -- ASM login info (Oracle only. If db is using ASM) TRANLOGOPTIONS ASMUSER sys@[connect string], ASMPASSWORD [encrypted password], encryptkey default --DBLOGREADER enables Extract to use a read buffer size of up to 4 MB --- in size. A larger buffer may improve the performance of Extract when -- redo rate is high. The db has to be 10.2.0.5 or higher to use -- this feature. If DBLOGREADER parameter is in place then the above -- ASMUSER parameter should not be used. TRANLOGOPTIONS DBLOGREADER, DBLOGREADER BUFSIZE [x], BUFSIZE [y] --DDL replication parameters DDL INCLUDE ALL, EXCLUDE OBJNAME "[schema name].[object name] " DDLOPTIONS ADDTRANDATA --Discard file location. DISCARDFILE [diacard file path/[discard file name.dsc], APPEND Megabytes [n] -- Use the DISCARDROLLOVER parameter to set a schedule for aging discard --files. DISCARDROLLOVER AT [hh:mi] on [day of the week] -- Use the REPORTROLLOVER parameter to force report files to age on a -- regular schedule, instead of when a process starts REPORTROLLOVER AT [hh:mi] on [day of the week] -- Use the REPORTCOUNT parameter to report a count of transaction -- records that Extract or Replicat processed since startup REPORTCOUNT EVERY [n] HOURS, RATE -- Use the FETCHOPTIONS parameter to control certain aspects of the way -- that GoldenGate fetches data FETCHOPTIONS, USESNAPSHOT, NOUSELATESTVERSION, MISSINGROW REPORT STATOPTIONS REPORTFETCH -- Warn for long running txns WARNLONGTRANS [n]H, CHECKINTERVAL [n]m -- List of tables Table [source schema name].[table name]; ..
Oracle GoldenGate: Manager Sample Parameter File
Oracle GoldenGate: Extract Sample Parameter File
Oracle GoldenGate: Pump (Extract) Sample Parameter File
Oracle GoldenGate: Replicat Sample Parameter File