Chapter 4. Configuring Oracle GoldenGate

Having installed Oracle GoldenGate 12c, it must be configured in order to meet all of your data replication, data migration, or upgrade requirements. After initially discussing the main GoldenGate parameters, this chapter will provide a methodical approach to the configuration process, stepping through each task to give the depth of information necessary to successfully implement GoldenGate on Oracle 11g and 12c environments. You will learn the basic steps necessary to configure one-way replication in a GoldenGate environment, including data synchronization between the source and target.

This includes the following discussion topics:

  • Choosing the most appropriate instantiation method to synchronize the source database with the target prior to replication
  • Preparing and configuring the data capture for the initial load on the source system
  • Configuring change synchronization on the source system
  • Configuring change synchronization on the target system
  • Configuring classic and integrated modes

We also look at some new parameters and features, including configuring replication to and from multitenant and downstream mining databases. Helping to provide the building blocks, this chapter forms the basis for more complex configurations.

GoldenGate parameters

Parameters play a very important role in the configuration of GoldenGate. Every configurable process is driven from an associated parameter file, which are stored by default in the dirprm subdirectory under the GoldenGate Home with the following naming convention:

<process_group>.prm

Following a successful software installation as described in Chapter 2, Installing and Preparing GoldenGate, we have already used a handful of parameters for a basic configuration. Although parameter files can be edited using a text editor, it is strongly recommended to edit process group parameter files from GGSCI using the EDIT PARAMS <process_group> command.

Let's now take a look at the scope and application of the GoldenGate parameters used in this chapter.

The following table lists the parameters and their description grouped by their process type. This is by no means an exhaustive list; we will become familiar with these parameters as we continue our journey through the book.

Note SOURCECATALOG, USERIDALIAS, LOGALLSUPCOLS, and UPDATERECORDFORMAT are new GoldenGate 12c parameters, which are used in the configuration examples implemented and tested in Oracle 11g Release 2 and the Oracle 12c multitenant container database environment:

Process

Parameter name

Parameter description

Mgr

PORT

This specifies the TCP/IP port number that the Manager process uses for communication with other processes. The default is PORT 7809.

Mgr

PURGEOLDEXTRACTS

This enables purging of Extract and Replicat trail files from associated trail locations. The default is to purge the trail file when moving to the next file in the sequence.

Mgr

AUTOSTART

This directs the Manager process to automatically start Extract and Replicat processes.

Mgr

AUTORESTART

This directs the Manager process to automatically restart Extract and Replicat processes after failure.

Extract

EXTRACT

This defines the name of the Extract process.

Extract

SOURCEISTABLE

This defines the source as the database table and is used in initial load only.

Extract

SOURCECATALOG

This defines a default source Oracle container in a multitenant container database. It enables the traditional use of schema.object in TABLE or MAP statements.

Extract

LOGALLSUPCOLS

This enables the logging of ALL supplementary columns on the source database when using integrated Replicat on the target. The default is LOGALLSUPCOLS.

Extract

UPDATERECORDFORMAT

When set with the COMPACT option forces the Extract process to combine the before and after images of an UPDATE operation into a single record in the trail. The default uses the FULL option.

Extract

RMTTASK

This configures Extract to communicate directly with the Replicat over TCP/IP for Direct Load methods during the initial load.

Extract

RMTFILE

This defines the location and filename on the remote system where the Extract process writes its data. It is used in initial load and batch processing operations.

Extract

RMTTRAIL

This configures Extract to write data to a remote trail and is used in the data pump Extract parameter file.

Extract

RMTHOST

This defines the remote system's hostname. If a hostname is used, it must resolve to an IP address.

Extract

EXTFILE

This defines the name and location for a file used to temporarily store the data changes written to by the Extract process. It is used in conjunction with SPECIALRUN for initial load and batch processing operations.

Extract

MGRPORT

This defines the Manager port number.

Extract/Replicat

USERIDALIAS

This specifies an OGG user ID and optional group for database logon credentials held in the credential store.

Extract/Replicat

USERID

This is the Oracle database OGG admin user ID.

Extract/Replicat

PASSWORD

This is the Oracle database OGG admin user password.

Extract/Replicat

TABLE

This defines the source (Extract) or target (Replicat) table name.

Extract/Replicat

DISCARDFILE

This defines the name and location of the process discarded data file. The maximum file size is 50MB.

Replicat

REPLICAT

This defines the name of the Replicat process.

Replicat

SPECIALRUN

This indicates that Replicat is a one-off process, typically an initial load. It supports the END RUNTIME parameter.

Replicat

RUNTIME

All unprocessed records with timestamps up to the current point in time are processed; otherwise, the Replicat process is terminated.

Replicat

SOURCEDEFS

This is declared in association with a source definitions file to provide mapping between tables having a different data structure to the target tables.

Replicat

ASSUMETARGETDEFS

This declares that the source tables are identical in structure as the target tables.

Replicat

HANDLECOLLISIONS

This directs automatic resolution of duplicate and missing record errors when applying data on the target database. This parameter is generally used only for the initial load. The default is NOHANDLECOLLISIONS.

Replicat

MAP

This defines the mapping between source and target tables. It can be used for column mapping and transformations.

Replicat

BULKLOAD

This directs the Replicat to use the bulk load method of initial load, writing data directly to the SQL*Loader interface.

Armed with the most common configuration parameters, let's now choose and create our GoldenGate instantiation method.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
18.117.182.179