1/30

Contents

Title and Copyright Information

Preface

• Audience
• Documentation Accessibility
• Related Information
• Conventions

1 Oracle GoldenGate Administration Overview

2 Oracle GoldenGate Globalization Support

• 2.1 Preserving the Character Set
  • 2.1.1 Character Set of Database Structural Metadata
  • 2.1.2 Character Set of Character-type Data
  • 2.1.3 Character Set of Database Connection
  • 2.1.4 Character Set of Text Input and Output
• 2.2 Using Unicode and Native Characters

Part I Administering Oracle GoldenGate Classic Architecture

3 Configuring Manager and Network Communications

• 3.1 Overview of the Manager Process
• 3.2 Assigning Manager a Port for Local Communication
• 3.3 Maintaining Ports for Remote Connections through Firewalls
• 3.4 Choosing an Internet Protocol
• 3.5 Using the Recommended Manager Parameters
• 3.6 Creating the Manager Parameter File
• 3.7 Starting Manager
  • 3.7.1 Starting Manager from the Command Shell of the Operating System
  • 3.7.2 Starting Manager from GGSCI
• 3.8 Stopping Manager
  • 3.8.1 Stopping Manager on UNIX and Linux
  • 3.8.2 Stopping Manager on Windows

4 Getting Started with the Oracle GoldenGate Process Interfaces

• 4.1 Using the GGSCI Command-line Interface
  • 4.1.1 Using Wildcards in Command Arguments
  • 4.1.2 Globalization Support for the Command Interface
  • 4.1.3 Using Command History
  • 4.1.4 Storing and Calling Frequently Used Command Sequences
• 4.2 Controlling Oracle GoldenGate Processes
  • 4.2.1 Controlling Manager
  • 4.2.2 Controlling Extract and Replicat
  • 4.2.3 Deleting Extract and Replicat
• 4.3 Automating Commands
  • 4.3.1 Issuing Commands Through the IBM i CLI
• 4.4 Using Oracle GoldenGate Parameter Files
  • 4.4.1 Globalization Support for Parameter Files
  • 4.4.2 Working with the GLOBALS File
  • 4.4.3 Working with Runtime Parameters
  • 4.4.4 Creating a Parameter File
    • 4.4.4.1 Creating a Parameter File in GGSCI
    • 4.4.4.2 Creating a Parameter File with a Text Editor
  • 4.4.5 Validating a Parameter File
  • 4.4.6 Viewing a Parameter File
  • 4.4.7 Changing a Parameter File
  • 4.4.8 Simplifying the Creation of Parameter Files
    • 4.4.8.1 Using Wildcards
    • 4.4.8.2 Using OBEY
    • 4.4.8.3 Using Macros
    • 4.4.8.4 Using Parameter Substitution
  • 4.4.9 Getting Information about Oracle GoldenGate Parameters
• 4.5 Specifying Object Names in Oracle GoldenGate Input
  • 4.5.1 Specifying Filesystem Path Names in Parameter Files on Windows Systems
  • 4.5.2 Supported Database Object Names
    • 4.5.2.1 Supported Special Characters
    • 4.5.2.2 Non-supported Special Characters
  • 4.5.3 Specifying Names that Contain Slashes
  • 4.5.4 Qualifying Database Object Names
    • 4.5.4.1 Two-part Names
    • 4.5.4.2 Three-part Names
    • 4.5.4.3 Applying Data from Multiple Containers or Catalogs
    • 4.5.4.4 Specifying a Default Container or Catalog
  • 4.5.5 Specifying Case-Sensitive Database Object Names
  • 4.5.6 Using Wildcards in Database Object Names
    • 4.5.6.1 Rules for Using Wildcards for Source Objects
    • 4.5.6.2 Rules for Using Wildcards for Target Objects
    • 4.5.6.3 Fallback Name Mapping
    • 4.5.6.4 Wildcard Mapping from Pre-11.2.1 Trail Version
    • 4.5.6.5 Asterisks or Question Marks as Literals in Object Names
    • 4.5.6.6 How Wildcards are Resolved
    • 4.5.6.7 Excluding Objects from a Wildcard Specification
  • 4.5.7 Differentiating Case-Sensitive Column Names from Literals

5 Using Oracle GoldenGate for Live Reporting

• 5.1 Overview of the Reporting Configuration
  • 5.1.1 Filtering and Conversion
  • 5.1.2 Read-only vs. High Availability
  • 5.1.3 Additional Information
• 5.2 Creating a Standard Reporting Configuration
  • 5.2.1 Source System
  • 5.2.2 Target System
• 5.3 Creating a Reporting Configuration with a Data Pump on the Source System
  • 5.3.1 Source System
  • 5.3.2 Target System
• 5.4 Creating a Reporting Configuration with a Data Pump on an Intermediary System
  • 5.4.1 Source System
  • 5.4.2 Intermediary System
  • 5.4.3 Target System
• 5.5 Creating a Cascading Reporting Configuration
  • 5.5.1 Source System
  • 5.5.2 Second System in the Cascade
  • 5.5.3 Third System in the Cascade

6 Using Oracle GoldenGate for Real-time Data Distribution

• 6.1 Overview of the Data-distribution Configuration
• 6.2 Considerations for a Data-distribution Configuration
  • 6.2.1 Fault Tolerance
  • 6.2.2 Filtering and Conversion
  • 6.2.3 Read-only vs. High Availability
  • 6.2.4 Additional Information
• 6.3 Creating a Data Distribution Configuration
  • 6.3.1 Source System
  • 6.3.2 Target Systems

7 Configuring Oracle GoldenGate for Real-time Data Warehousing

• 7.1 Overview of the Data Warehousing Configuration
• 7.2 Considerations for a Data Warehousing Configuration
  • 7.2.1 Isolation of Data Records
  • 7.2.2 Data Storage
  • 7.2.3 Filtering and Conversion
  • 7.2.4 Additional Information
• 7.3 Creating a Data Warehousing Configuration
  • 7.3.1 Source Systems
  • 7.3.2 Target System

8 Configuring Oracle GoldenGate to Maintain a Live Standby Database

• 8.1 Overview of a Live Standby Configuration
• 8.2 Considerations for a Live Standby Configuration
  • 8.2.1 Trusted Source
  • 8.2.2 Duplicate Standby
  • 8.2.3 DML on the Standby System
  • 8.2.4 Oracle GoldenGate Processes
  • 8.2.5 Backup Files
  • 8.2.6 Failover Preparedness
  • 8.2.7 Sequential Values that are Generated by the Database
  • 8.2.8 Additional Information
• 8.3 Creating a Live Standby Configuration
  • 8.3.1 Prerequisites on Both Systems
  • 8.3.2 Configuration from Active Source to Standby
• 8.4 Configuration from Standby to Active Source
• 8.5 Moving User Activity in a Planned Switchover
  • 8.5.1 Moving User Activity to the Live Standby
  • 8.5.2 Moving User Activity Back to the Primary System
• 8.6 Moving User Activity in an Unplanned Failover
  • 8.6.1 Moving User Activity to the Live Standby
  • 8.6.2 Moving User Activity Back to the Primary System

9 Configuring Oracle GoldenGate for Active-Active High Availability

• 9.1 Overview of an Active-Active Configuration
• 9.2 Considerations for an Active-Active Configuration
  • 9.2.1 TRUNCATES
  • 9.2.2 Application Design
  • 9.2.3 Keys
  • 9.2.4 Triggers and Cascaded Deletes
  • 9.2.5 Database-Generated Values
  • 9.2.6 Database Configuration
• 9.3 Preventing Data Looping
  • 9.3.1 Preventing the Capture of Replicat Operations
    • 9.3.1.1 Preventing the Capture of Replicat Transactions (Oracle)
    • 9.3.1.2 Preventing Capture of Replicat Transactions (Other Databases)
  • 9.3.2 Identifying Replicat Transactions
    • 9.3.2.1 DB2 z/OS, DB2 LUW, and DB2 for i
    • 9.3.2.2 MySQL
    • 9.3.2.3 Oracle
    • 9.3.2.4 SQL Server
  • 9.3.3 Replicating DDL in a Bi-directional Configuration
• 9.4 Managing Conflicts
• 9.5 Additional Information
• 9.6 Creating an Active-Active Configuration
  • 9.6.1 Prerequisites on Both Systems
  • 9.6.2 Configuration from Primary System to Secondary System
  • 9.6.3 Configuration from Secondary System to Primary System

10 Configuring Conflict Detection and Resolution

• 10.1 Overview of the Oracle GoldenGate CDR Feature
• 10.2 Configuring Oracle GoldenGate CDR
  • 10.2.1 Making the Required Column Values Available to Extract
  • 10.2.2 Configuring the Oracle GoldenGate Parameter Files for Conflict Resolution
  • 10.2.3 Configuring the Oracle GoldenGate Parameter Files for Error Handling
    • 10.2.3.1 Tools for Mapping Extra Data to the Exceptions Table
    • 10.2.3.2 Sample Exceptions Mapping with Source and Target Columns Only
    • 10.2.3.3 Sample Exceptions Mapping with Additional Columns in the Exceptions Table
  • 10.2.4 Viewing CDR Statistics
    • 10.2.4.1 Report File
    • 10.2.4.2 GGSCI
    • 10.2.4.3 Column-conversion Functions
• 10.3 CDR Example 1: All Conflict Types with USEMAX, OVERWRITE, DISCARD
  • 10.3.1 Table Used in this Example
  • 10.3.2 MAP Statement with Conflict Resolution Specifications
  • 10.3.3 Description of MAP Statement
  • 10.3.4 Error Handling
  • 10.3.5 INSERTROWEXISTS with the USEMAX Resolution
  • 10.3.6 UPDATEROWEXISTS with the USEMAX Resolution
  • 10.3.7 UPDATEROWMISSING with OVERWRITE Resolution
  • 10.3.8 DELETEROWMISSING with DISCARD Resolution
  • 10.3.9 DELETEROWEXISTS with OVERWRITE Resolution
• 10.4 CDR Example 2: UPDATEROWEXISTS with USEDELTA and USEMAX
  • 10.4.1 Table Used in this Example
  • 10.4.2 MAP Statement
  • 10.4.3 Description of MAP Statement
  • 10.4.4 Error Handling
• 10.5 CDR Example 3: UPDATEROWEXISTS with USEDELTA, USEMAX, and IGNORE
  • 10.5.1 Table Used in this Example
  • 10.5.2 MAP Statement
  • 10.5.3 Description of MAP Statement
  • 10.5.4 Error Handling

11 Mapping and Manipulating Data

• 11.1 Limitations of Support
• 11.2 Parameters that Control Mapping and Data Integration
• 11.3 Mapping between Dissimilar Databases
• 11.4 Deciding Where Data Mapping and Conversion Will Take Place
  • 11.4.1 Mapping and Conversion on Windows and UNIX Systems
  • 11.4.2 Mapping and Conversion on NonStop Systems
• 11.5 Globalization Considerations when Mapping Data
  • 11.5.1 Conversion between Character Sets
    • 11.5.1.1 Database Object Names
    • 11.5.1.2 Column Data
  • 11.5.2 Preservation of Locale
  • 11.5.3 Support for Escape Sequences
• 11.6 Mapping Columns
  • 11.6.1 Supporting Case and Special Characters in Column Names
  • 11.6.2 Configuring Table-level Column Mapping with COLMAP
    • 11.6.2.1 Specifying the Columns to be Mapped in the COLMAP Clause
    • 11.6.2.2 Using USEDEFAULTS to Enable Default Column Mapping
    • 11.6.2.3 Determining Whether COLMAP Requires a Data-definitions File
  • 11.6.3 Configuring Global Column Mapping with COLMATCH
  • 11.6.4 Understanding Default Column Mapping
  • 11.6.5 Mapping Data Types from Column to Column
    • 11.6.5.1 Numeric Columns
    • 11.6.5.2 Character-type Columns
    • 11.6.5.3 Datetime Columns
• 11.7 Selecting and Filtering Rows
  • 11.7.1 Selecting Rows with a FILTER Clause
  • 11.7.2 Selecting Rows with a WHERE Clause
  • 11.7.3 Considerations for Selecting Rows with FILTER and WHERE
    • 11.7.3.1 Ensuring Data Availability for Filters
    • 11.7.3.2 Comparing Column Values
    • 11.7.3.3 Testing for NULL Values
• 11.8 Retrieving Before and After Values
• 11.9 Selecting Columns
• 11.10 Selecting and Converting SQL Operations
• 11.11 Using Transaction History
• 11.12 Testing and Transforming Data
  • 11.12.1 Handling Column Names and Literals in Functions
  • 11.12.2 Using the Appropriate Function
  • 11.12.3 Transforming Dates
  • 11.12.4 Performing Arithmetic Operations
    • 11.12.4.1 Omitting @COMPUTE
  • 11.12.5 Manipulating Numbers and Character Strings
  • 11.12.6 Handling Null, Invalid, and Missing Data
    • 11.12.6.1 Using @COLSTAT
    • 11.12.6.2 Using @COLTEST
    • 11.12.6.3 Using @IF
  • 11.12.7 Performing Tests
    • 11.12.7.1 Using @CASE
    • 11.12.7.2 Using @VALONEOF
    • 11.12.7.3 Using @EVAL
• 11.13 Using Tokens
  • 11.13.1 Defining Tokens
  • 11.13.2 Using Token Data in Target Tables

12 Associating Replicated Data with Metadata

• 12.1 Overview
• 12.2 Understanding Data Definition Files
  • 12.2.1 Contents of the Definitions File
  • 12.2.2 Which Definitions File Type to Use, and Where
  • 12.2.3 Understanding the Effect of Character Sets on Definitions Files
    • 12.2.3.1 Confining Data Mapping and Conversion to the Replicat Process
    • 12.2.3.2 Avoiding File Corruptions Due to Operating System Character Sets
    • 12.2.3.3 Changing the Character Set of Existing Definitions Files
    • 12.2.3.4 Downloading from a z/OS system to another platform
  • 12.2.4 Using a Definitions Template
  • 12.2.5 Configuring Oracle GoldenGate to Capture Data-definitions
    • 12.2.5.1 Configure DEFGEN
    • 12.2.5.2 Run DEFGEN
    • 12.2.5.3 Transfer the Definitions File to the Remote System
    • 12.2.5.4 Specify the Definitions File
  • 12.2.6 Adding Tables that Satisfy a Definitions Template
  • 12.2.7 Examples of Using a Definitions File
    • 12.2.7.1 Creating a Source-definitions file for Use on a Target System
    • 12.2.7.2 Creating Target-definitions Files for Use on a Source System
    • 12.2.7.3 Creating Multiple Source Definition Files for Use on a Target System
• 12.3 Using Automatic Trail File Recovery
• 12.4 Configuring Oracle GoldenGate to Use Self-Describing Trail Files
  • 12.4.1 Support Considerations
  • 12.4.2 Using Self-Describing Trail Files
  • 12.4.3 Examples of Parameter Files
• 12.5 Configuring Oracle GoldenGate to Assume Identical Metadata
  • 12.5.1 Rules for Tables to be Considered Identical
• 12.6 Configuring Oracle GoldenGate to Assume Dissimilar Metadata
• 12.7 Configuring Oracle GoldenGate to Use a Combination of Similar and Dissimilar Definitions

13 Configuring Online Change Synchronization

• 13.1 Overview of Online Change Synchronization
  • 13.1.1 Initial Synchronization
• 13.2 Choosing Names for Processes and Files
  • 13.2.1 Naming Conventions for Processes
  • 13.2.2 Choosing File Names
• 13.3 Creating a Checkpoint Table
  • 13.3.1 Options for Creating the Checkpoint Table
  • 13.3.2 Adjusting for Coordinated Replicat in Oracle RAC
• 13.4 Creating an Online Extract Group
• 13.5 Creating a Trail
  • 13.5.1 Assigning Storage for Oracle GoldenGate Trails
  • 13.5.2 Estimating Space for the Trails
  • 13.5.3 Adding a Trail
• 13.6 Creating a Parameter File for Online Extraction
• 13.7 Creating an Online Replicat Group
  • 13.7.1 About Classic Replicat Mode
  • 13.7.2 About Coordinated Replicat Mode
    • 13.7.2.1 About Barrier Transactions
    • 13.7.2.2 How Barrier Transactions are Processed
    • 13.7.2.3 About the Global Watermark
  • 13.7.3 About Integrated Replicat Mode
  • 13.7.4 Understanding Replicat Processing in Relation to Parameter Changes
  • 13.7.5 Creating the Replicat Group
• 13.8 Creating a Parameter File for Online Replication

14 Handling Processing Errors

• 14.1 Overview of Oracle GoldenGate Error Handling
• 14.2 Handling Extract Errors
• 14.3 Handling Replicat Errors during DML Operations
  • 14.3.1 Handling Errors as Exceptions
    • 14.3.1.1 Using EXCEPTIONSONLY
    • 14.3.1.2 Using MAPEXCEPTION
    • 14.3.1.3 About the Exceptions Table
• 14.4 Handling Replicat errors during DDL Operations
• 14.5 Handling TCP/IP Errors
• 14.6 Maintaining Updated Error Messages
• 14.7 Resolving Oracle GoldenGate Errors

15 Instantiating Oracle GoldenGate with an Initial Load

• 15.1 Overview of the Initial-Load Procedure
  • 15.1.1 Improving the Performance of an Initial Load
  • 15.1.2 Prerequisites for Initial Load
    • 15.1.2.1 Disable DDL Processing
    • 15.1.2.2 Prepare the Target Tables
    • 15.1.2.3 Configure the Manager Process
    • 15.1.2.4 Create a Data-definitions File
    • 15.1.2.5 Create Change-synchronization Groups
    • 15.1.2.6 Sharing Parameters between Process Groups
• 15.2 Initial Load in Classic Architecture
  • 15.2.1 Loading Data with a Database Utility
  • 15.2.2 Loading Data with Oracle Data Pump
    • 15.2.2.1 Using Automatic Per Table Instantiation
    • 15.2.2.2 Using Oracle Data Pump Table Instantiation
  • 15.2.3 Loading Data from File to Replicat
  • 15.2.4 Loading Data with an Oracle GoldenGate Direct Load
  • 15.2.5 Loading Data with a Direct Bulk Load to SQL*Loader
  • 15.2.6 Loading Data with Teradata Load Utilities

16 Customizing Oracle GoldenGate Processing

• 16.1 Executing Commands, Stored Procedures, and Queries with SQLEXEC
  • 16.1.1 Performing Processing with SQLEXEC
  • 16.1.2 Using SQLEXEC
  • 16.1.3 Executing SQLEXEC within a TABLE or MAP Statement
  • 16.1.4 Executing SQLEXEC as a Standalone Statement
  • 16.1.5 Using Input and Output Parameters
    • 16.1.5.1 Passing Values to Input Parameters
    • 16.1.5.2 Passing Values to Output Parameters
    • 16.1.5.3 SQLEXEC Examples Using Parameters
  • 16.1.6 Handling SQLEXEC Errors
    • 16.1.6.1 Handling Missing Column Values
    • 16.1.6.2 Handling Database Errors
  • 16.1.7 Additional SQLEXEC Guidelines
• 16.2 Using Oracle GoldenGate Macros to Simplify and Automate Work
  • 16.2.1 Defining a Macro
  • 16.2.2 Calling a Macro
    • 16.2.2.1 Calling a Macro that Contains Parameters
    • 16.2.2.2 Calling a Macro without Input Parameters
  • 16.2.3 Calling Other Macros from a Macro
  • 16.2.4 Creating Macro Libraries
  • 16.2.5 Tracing Macro Expansion
• 16.3 Using User Exits to Extend Oracle GoldenGate Capabilities
  • 16.3.1 When to Implement User Exits
  • 16.3.2 Making Oracle GoldenGate Record Information Available to the Routine
  • 16.3.3 Creating User Exits
  • 16.3.4 Supporting Character-set Conversion in User Exits
  • 16.3.5 Using Macros to Check Name Metadata
  • 16.3.6 Describing the Character Format
  • 16.3.7 Upgrading User Exits
  • 16.3.8 Viewing Examples of How to Use the User Exit Functions
• 16.4 Using the Oracle GoldenGate Event Marker System to Raise Database Events
  • 16.4.1 Case Studies in the Usage of the Event Marker System
    • 16.4.1.1 Trigger End-of-day Processing
    • 16.4.1.2 Simplify Transition from Initial Load to Change Synchronization
    • 16.4.1.3 Stop Processing When Data Anomalies are Encountered
    • 16.4.1.4 Trace a Specific Order Number
    • 16.4.1.5 Execute a Batch Process
    • 16.4.1.6 Propagate Only a SQL Statement without the Resultant Operations
    • 16.4.1.7 Committing Other Transactions Before Starting a Long-running Transaction
    • 16.4.1.8 Execute a Shell Script to Validate Data

17 Monitoring Oracle GoldenGate Processing

• 17.1 Using the Information Commands in GGSCI
• 17.2 Monitoring an Extract Recovery
• 17.3 Monitoring Lag
  • 17.3.1 About Lag
  • 17.3.2 Controlling How Lag is Reported
• 17.4 Using Automatic Heartbeat Tables to Monitor
  • 17.4.1 Understanding Heartbeat Table End-To-End Replication Flow
  • 17.4.2 Updating Heartbeat Tables
  • 17.4.3 Purging the Heartbeat History Tables
  • 17.4.4 Best Practice
  • 17.4.5 Using the Automatic Heartbeat Commands
• 17.5 Monitoring Processing Volume
• 17.6 Using the Error Log
• 17.7 Using the Process Report
  • 17.7.1 Scheduling Runtime Statistics in the Process Report
  • 17.7.2 Viewing Record Counts in the Process Report
  • 17.7.3 Preventing SQL Errors from Filling the Replicat Report File
• 17.8 Using the Discard File
• 17.9 Maintaining the Discard and Report Files
• 17.10 Reconciling Time Differences
• 17.11 Getting Help with Performance Tuning

18 Tuning the Performance of Oracle GoldenGate

• 18.1 Using Multiple Process Groups
  • 18.1.1 Considerations for Using Multiple Process Groups
    • 18.1.1.1 Maintaining Data Integrity
    • 18.1.1.2 Number of Groups
    • 18.1.1.3 Memory
    • 18.1.1.4 Isolating Processing-Intensive Tables
  • 18.1.2 Using Parallel Replicat Groups on a Target System
    • 18.1.2.1 To Create the Extract Group
    • 18.1.2.2 To Create the Replicat Groups
  • 18.1.3 Using Multiple Extract Groups with Multiple Replicat Groups
    • 18.1.3.1 To Create the Extract Groups
    • 18.1.3.2 To Create the Replicat Groups
• 18.2 Splitting Large Tables Into Row Ranges Across Process Groups
• 18.3 Configuring Oracle GoldenGate to Use the Network Efficiently
  • 18.3.1 Detecting a Network Bottleneck that is Affecting Oracle GoldenGate
  • 18.3.2 Working Around Bandwidth Limitations by Using Data Pumps
  • 18.3.3 Reducing the Bandwidth Requirements of Oracle GoldenGate
  • 18.3.4 Increasing the TCP/IP Packet Size
• 18.4 Eliminating Disk I/O Bottlenecks
  • 18.4.1 Improving I/O performance Within the System Configuration
  • 18.4.2 Improving I/O Performance Within the Oracle GoldenGate Configuration
• 18.5 Managing Virtual Memory and Paging
• 18.6 Optimizing Data Filtering and Conversion
• 18.7 Tuning Replicat Transactions
  • 18.7.1 Tuning Coordination Performance Against Barrier Transactions
  • 18.7.2 Applying Similar SQL Statements in Arrays
  • 18.7.3 Preventing Full Table Scans in the Absence of Keys
  • 18.7.4 Splitting Large Transactions
  • 18.7.5 Adjusting Open Cursors
  • 18.7.6 Improving Update Speed
  • 18.7.7 Set a Replicat Transaction Timeout

19 Performing Administrative Operations

• 19.1 Performing Application Patches
• 19.2 Initializing the Transaction Logs
• 19.3 Shutting Down the System
• 19.4 Changing Database Attributes
  • 19.4.1 Changing Database Metadata
  • 19.4.2 Adding Tables to the Oracle GoldenGate Configuration
  • 19.4.3 Coordinating Table Attributes between Source and Target
  • 19.4.4 Performing an ALTER TABLE to Add a Column on DB2 z/OS Tables
  • 19.4.5 Dropping and Recreating a Source Table
  • 19.4.6 Changing the Number of Oracle RAC Threads when Using Classic Capture
  • 19.4.7 Changing the ORACLE_SID
  • 19.4.8 Purging Archive Logs
  • 19.4.9 Reorganizing a DB2 Table (z/OS Platform)
• 19.5 Adding Process Groups to an Active Configuration
  • 19.5.1 Before You Start
  • 19.5.2 Adding Another Extract Group to an Active Configuration
  • 19.5.3 Adding Another Data Pump to an Active Configuration
  • 19.5.4 Adding Another Replicat Group to an Active Configuration
• 19.6 Changing the Size of Trail Files
• 19.7 Switching Extract from Classic Mode to Integrated Mode
• 19.8 Switching Extract from Integrated Mode to Classic Mode
• 19.9 Switching Replicat from Nonintegrated Mode to Integrated Mode
• 19.10 Switching Replicat from Integrated Mode to Nonintegrated Mode
• 19.11 Switching Replicat to Coordinated Mode
  • 19.11.1 Procedure Overview
  • 19.11.2 Performing the Switch to Coordinated Replicat
• 19.12 Administering a Coordinated Replicat Configuration
  • 19.12.1 Performing a Planned Re-partitioning of the Workload
  • 19.12.2 Recovering Replicat After an Unplanned Re-partitioning
    • 19.12.2.1 Reprocessing From the Low Watermark with HANDLECOLLISIONS
    • 19.12.2.2 Using the Auto-Saved Parameter File
  • 19.12.3 Synchronizing Threads After an Unclean Stop
• 19.13 Restarting a Primary Extract after System Failure or Corruption
  • 19.13.1 Details of This Procedure
  • 19.13.2 Performing the Recovery

Part II Administering Oracle GoldenGate Microservices Architecture

20 Loading Data from File to Replicat in Microservices Architecture

A Supported Character Sets

• A.1 Supported Character Sets - Oracle
• A.2 Supported Character Sets - Non-Oracle

B Supported Locales

C About the Oracle GoldenGate Trail

• C.1 Trail Recovery Mode
• C.2 Trail File Header Record
• C.3 Trail Record Format
• C.4 Example of an Oracle GoldenGate Record
• C.5 Record Header Area
  • C.5.1 Description of Header Fields
  • C.5.2 Using Header Data
• C.6 Record Data Area
  • C.6.1 Full Record Image Format (NonStop Sources)
  • C.6.2 Compressed Record Image Format (Windows, UNIX, Linux Sources)
• C.7 Tokens Area
• C.8 Oracle GoldenGate Operation Types
• C.9 Oracle GoldenGate Trail Header Record

D Using the Commit Sequence Number

E About Checkpoints

• E.1 Extract Checkpoints
  • E.1.1 About Extract read checkpoints
    • E.1.1.1 Startup Checkpoint
    • E.1.1.2 Recovery Checkpoint
    • E.1.1.3 Current Checkpoint
  • E.1.2 About Extract Write Checkpoints
• E.2 Replicat Checkpoints
  • E.2.1 About Replicat Checkpoints
    • E.2.1.1 Startup Checkpoint
    • E.2.1.2 Current Checkpoint
• E.3 Internal Checkpoint Information
• E.4 Oracle GoldenGate Checkpoint Tables