• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer navigation

The Geek Diary

  • OS
    • Linux
    • CentOS/RHEL
    • Solaris
    • Oracle Linux
    • VCS
  • Interview Questions
  • Database
    • oracle
    • oracle 12c
    • ASM
    • mysql
    • MariaDB
  • DevOps
    • Docker
    • Shell Scripting
  • Big Data
    • Hadoop
    • Cloudera
    • Hortonworks HDP

Oracle GoldenGate: Pump (Extract) Sample Parameter File

by admin

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.

Pump (Extract) Process

The data pump group is a secondary extract group that is used to help ship data across network. Although a data pump is another extract group similar to the capture process, don’t confuse the two. The main purpose of the data pump process is to ship trail files across the network to the remote target system.

Process name: Pump (Extract)

Extract parameter file (Sample)

-- Runcmd: ADD EXTRACT [pump name], EXTTRAILSOURCE [extract trail
-- Path/two character trail id]
-- Runcmd: ADD RMTTRAIL [pump trail path/two character trail id] ,
-- EXTRACT [pump name], Megabytes [n]
-- Name of the Pump process. Limited to 8 charecters.

EXTRACT [Pump name]

-- Oracle environment settings
SETENV (ORACLE_HOME = "[Oracle home path]" )
SETENV (ORACLE_SID="[Oracle sid]")

-- In passthru mode GoldenGate pump process cascades captured data from 
-- source to target without logging in to the source database 
Passthru

-- Remote host and remort manager port to write trail
RMTHOST [Remote hostname], MGRPORT [Target manager port number]

-- Remote trail info
RMTTRAIL [extract trail path/two character trail id]

--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

-- List of tables
Table [source schema name].[table name];
Oracle GoldenGate: GLOBALS Sample Parameter File
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

Filed Under: GoldenGate, oracle

Some more articles you might also be interested in …

  1. Database Crashed With ORA-19815, ORA-19809, ORA-16038
  2. How To Cancel A SQL Query In Oracle Database 18c
  3. Troubleshooting Common ORA-1157 Errors (cannot identify/lock data file)
  4. Script To Find Redolog Switch History And Find Archivelog Size For Each Instances In Oracle RAC
  5. ORA-354 ORA-353 and ORA-312: Possible corruption in Online Redo Log File Members in a Redo Log Group
  6. Oracle Database Server Architecture: Overview
  7. How to Clear a Redo Log file in Oracle Database
  8. Example of PDB Level Duplication in Oracle Database 18c
  9. Oracle Interview Questions – Flash Recovery Area
  10. Oracle SQL Script to Detect Tablespace Fragmentation

You May Also Like

Primary Sidebar

Recent Posts

  • pw-cat Command Examples in Linux
  • pvs: command not found
  • pulseaudio: command not found
  • pulseaudio Command Examples in Linux

© 2023 · The Geek Diary

  • Archives
  • Contact Us
  • Copyright