GoldenGate for SQL Server to UNIX DB2 - Oracle

GoldenGate for SQL Server to UNIX DB2

� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �


Objective

Upon completion of this lesson, you will be able to keep an MS SQL Server database

synchronized with a DB2 database on UNIX using GoldenGate.

During this lesson, you will learn how to:

�� Prepare your user environment.

�� Configure and execute the initial data load process.

�� Configure and start the change capture process of database operations.

�� Configure and start the change delivery process of database operations.

Oracle to DB2 configuration

The following diagram illustrates GoldenGate a configuration with MS SQL Server source

data being replicated to a DB2 target databaseO.

Windows server <source>

MS SQL Server

<dsn>

Source

<schema>

Extract

Manager

Log

<target> server

DB2 <database>

Target<owner.schema>

Replicat

Collector

Trails

Manager

Network

Overview of Tasks

Prepare the Environment

In order to execute this lesson, the GoldenGate application must be installed on both the

source and target systems. The installation includes a sample database and scripts to generate

initial data as well as subsequent update operations. The source and target tables are created

and loaded with initial data. The GoldenGate Manager processes are also started so that other

processes may be configured and started.


� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �

Configure Initial Data Load

Initial database synchronization is almost always required. To initially load data across

heterogeneous databases, you have limited choices. GoldenGate provides the ability to

perform initial data synchronization while your application remains active. The capture

process also provides flexible output options, including the capability to format the data to be

loaded with bulk load utilities, such as DB2 Load.

This lesson demonstrates using the direct load method to capture data directly from the

source tables and send the data directly to the delivery process on the target system.

Configure Change Capture

The Extract process is configured to capture change data directly from the SQL Server

recovery logs (transaction logs) and distribute the changes to a series of files known as a

GoldenGate trails.

This lesson demonstrates extracting the data with Extract and sending the data directly to the

Replicat process. This is known as the direct load method.

Configure Change Delivery

Once the tables have been initially loaded with data, the delivery process is configured to

synchronize the captured change data into the target database.

<source> server

Initial

Extract

MS SQL Server

<dsn>

Source

<schema>

<target> server

DB2 <database>

Target <owner/schema>

Initial

Replicat

Network


� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 3

Exercise 1.


� � � � � � � � � � � � � � �

Objective

The goals of this exercise are to:

�� Create the database

�� Create SQL Server logins and users

�� Create ODBC data source.

�� Set up transaction logging.

�� Create tables and populate source data.

Prerequisites

This lab assumes that the GLOBALS parameters have been created with a <mgr service> name

and that the Manager service has been added. This should have been done when installing

GoldenGate for Windows.

Prepare the SQL Server 2005 source environment

Install Manager

1. Configure Manager process on the source

Execute the following commands on the <source> system.

Note! The port numbers must be unique if you are installing GoldenGate more than once on

the same server.

Shell> ggsci GGSCI> EDIT PARAMS MGR

� In the parameter file, enter the following parameter, then save and close the file.

PORT <port>

� Start Manager.

GGSCI> START MANAGER

� Verify the results:


� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 4

GGSCI> INFO MANAGER

Create the database

2. Create the database

From Start>Programs, run SQL Server Management Studio.

� Enter the name of the local SQL Server instance, then click connect.

Note: These instructions assume SQL Server Authentication which requires the

more complex, double layer, of authentication. SQL Server Authentication is an

option only if it is permitted at the server level, and only Windows Authentication is

enabled by default. If you are using Windows Authentication, you can leave out

most of the login and password entries.

� This displays the main SQL Server Management Studio dialog box. Right, right-click Database and select the New Database option.


� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 5

� The New Database dialog box appears. In the Name box, type the <database> from

the Lab Preparation worksheet.

� Click OK to add the database.

� The main SQL Server Management Studio dialog box reappears.

3. Create SQL Server logins and users

� Right click Security and select the New > Login.

� The New Login dialog box appears.


� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 6

� For Name, type the <login>.

� Select Authentication,

� If you selected SQL Server Authentication, type the <password> in the two Password fields.

� Under Defaults, select your <database> for Database, and leave Language set to the default.

� Do not click OK. Instead, from Select a page in the upper left-hand box, double click

Server Roles.


� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 7

� Under Server Role, check the box for the System Administrators role.

� Click OK to exit.

The next step creates a schema that you will associate with the new user.

� While you have the database selected, click on the New Query button in the main

menu.

� The right side of the dialog displays the SQL Query interface. Type in:

create schema <owner/schema>;

And press the Execute button from the toolbar.


� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 8

Now you need to associate the new user and the schema that you have created with the new

database.

� Right click on the Security option that is under the database and select New > User.

� The New Database User dialog box appears. Enter the name of your user and press

the browse button labeled with three dots (…).


� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 9

� The Select Login dialog displays. Press the Browse button.

� Select your new user <login> from the list. Then press OK.

� Your selected user now displays in the object names box. Press OK to exit from

Select Login.

� Back in the New Database User dialog, enter the <schema> you added as the default

schema and press OK.

4. Create the ODBC system data source name

The GoldenGate Extract process connects to a SQL Server database through an ODBC (Open

Database Connectivity) connection. Both the Extract and Replicat components of GoldenGate

require that a system data source name (DSN) be established, which stores the information

about how to connect to the SQL Server.

� Click Start > Settings > Control Panel.

� Double-click Administrative Tools.

� Double-click Data Sources (ODBC) to open the ODBC Data Source Administrator

dialog box.

� Click the System DSN tab, and then click the Add button. The Create New Data

Source dialog box appears.


� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 10

� Select the SQL Server driver and then click Finish. The Create a New Data Source to SQL Server dialog box appears.

� For Name, type <dsn>.

� Optionally type in a description, type for this source DSN.

� For Which SQL Server do you want to connect to, select local if SQL Server is on

the local system, or enter the server name at your SQL Server location.

� Click Next.

� Answer the question about how SQL Server should verify the login by selecting the option that you entered when creating the <login>. Then type <login> in Login ID and

<password> in Password.


� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 11

� Click Next.

� Make certain the default database is set to the database that you created; otherwise

select Change the default database to: and select it. Leave the other settings to their

defaults to use ANSI.

� Click Next.

� Leave the next dialog box set to the defaults, and click Finish.

� In the confirmation, click Test Data Source to test the connection.

� Close the confirmation dialog box and the Create a New Data Source box.


� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 12

� You can leave the SQL Server Management Studio running on the source system,

because you will be using it later.

5. Create the practice tables and insert source data

Execute the following commands on the <source> system only.

� Go to SQL Server Management Studio, select your database and select New Query

from the toolbar.

� If the correct database is not displayed in the drop down box (showing ggsdata above), click on the arrow and select it from the list.

� Click the File > Open and navigate to the demo_mss_create.sql script.

� Click Open to open the script in the New Query window.

� Execute the script by clicking the Execute Query button on the toolbar.

� Verify the results using the following commands in the input window:

sp_help tcustmer go sp_help tcustord go


� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 13

� Click the X button to close the input tab. Click New Query whenever you need to run another SQL command.

� Following the steps you used to execute the table create script, run the demo_mss_insert.sql script to insert source data into the source tcustmer and

tcustord tables.

Note! Run this on the source only.

� Verify the results as you did before.

� Leave the SQL Management Studio running on the source system.

Install replication components for SQL Server 2005

Installing replication components sets up the Microsoft SQL Server 2005 Distributor database

and Publisher. This is not needed if you meet the following conditions:

� You have installed MicroSoft’s Cumulative Update 6 (CU6) for SQL Server 2005.

� You are running GoldenGate version 9.5.1.15 or higher.

If you do not meet both of these conditions, replication components must be installed on your <source> system in order to capture changes generated by SQL Server 2005. Unless your

instructor indicates that these components have already been installed and configured,

perform the workshop SQL Server 2005 Replication Components before proceeding to the

next section.


� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 14

Prepare for transaction logging

To support GoldenGate extraction, the following are required. Execute these steps on the <source> system only.

�� Log truncation and non-logged bulk copy must be turned off.

�� The SQL Server database must be set to the full recovery model (this is the default for

SQL Server 2005).

�� At least one full database backup must be done before GoldenGate processes are

started for the first time.

�� Additional log data must be enabled so GoldenGate can reconstruct update

operations.

� Microsoft SQL Server 2005 replication components must be installed (previous step).

6. Turn off log truncation and bulk copy

In SQL Management Studio on the source system perform the following steps to turn off log

truncation and bulk copy.

� Clear the input window and then use the following command to check the status of

the log truncation option. Type the command in the input window (upper window),

then click the F5 key to execute it.

exec sp_dboption '<database>', 'trunc. log on chkpt.'

� The following response appears in the results (lower) window with a status of either ON or OFF.

If log truncation is ON, turn it off by executing the following command.

exec sp_dboption '<database>', 'trunc. log on chkpt.', false

The output should now show a CurrentSetting of OFF’.

� Check the status of the non-logged bulk copy option by executing the following command:

exec sp_dboption '<database>', 'select into/bulkcopy'

If non-logged bulk copy is on, disable it with the following command:

exec sp_dboption '<database>', ' select into/bulkcopy ', false


� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 15

7. Execute backup

Still in SQL Server Management Studio:

� In the console tree, right-click the database name and select Tasks > Backup

.

� The Back Up Database dialog box displays. If the back up destination is correct, skip the next two bulleted steps and initiate the backup as explained in the last step. If it is not correct, change the backup destination and click ADD.


� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 16

� The Select Backup Destination appears, where you can select File Name and then

click the navigation (...) button to navigate to a directory and specify the backup file

name.

� Click OK to close the Select Backup Destination dialog box. The backup file is added to the Destination list box in the SQL Server Backup dialog box.

� Click OK to start the backup. This procedure ensures that no transaction log information is lost when GoldenGate starts up.


� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 17

8. Set up capture of additional log data

Perform the following steps on the source system to configure the database to log full before

and after images for each update operation.

� From the source operating system's command shell, run GGSCI.

� Log into the database with the following command:

GGSCI > DBLOGIN SOURCEDB <dsn>, USERID <login>, PASSWORD <password>

� Issue the following commands to force the logging of the full before and after image

for updates.

GGSCI > ADD TRANDATA <owner/schema>.tcustmer GGSCI > ADD TRANDATA <owner/schema>.tcustord

� Verify that supplemental logging has been turned on for these tables.

GGSCI> INFO TRANDATA <owner/schema>.tcust*

Note: With SQL Server 2005 you cannot drop tables that have TRANDATA set. First

you must delete the TRANDATA setting.

Create source definitions

9. Configure source definition generator


� Bring up the DEFGEN parameter file in the editor.

GGSCI> EDIT PARAM DEFGEN

� Type in the parameters shown below.

DEFSFILE ./dirdef/source.def, PURGE SOURCEDB <dsn>, USERID <login>, PASSWORD <password> TABLE <owner/schema>.TCUSTMER; TABLE <owner/schema>.TCUSTORD;

� Exit from GGSCI.

GGSCI> EXIT

10. Execute the source definition generator

Execute the source definition generator from the Windows command prompt.

Shell> defgen paramfile .\dirprm\defgen.prm


� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 18

11. Transfer the source definition file to the target system

Execute the following commands on the <source> system to transfer the definition file to the

<target> system.

The cd command should be set to the <target> location and the lcd to the <source> location.

Shell> ftp <target> Name (<target>:<login>): <login> Password: <password> ftp> ascii ftp> cd <install loc>/dirdef ftp> lcd <install loc>/dirdef ftp> put source.def ftp> bye

Note: To avoid overlaying existing definition files, always put the file as <db type>.def

instead of source.def (e.g. MSSQL.def).

Disable SQL Server Log Reader Agent job

12. Stop and disable the job

The Log Reader Agent job cannot run concurrently with the GoldenGate Extract process.

Perform the following steps to stop and disable this job.

� In SQL Server Management Studio, connect to the SQL Server 2005 instance.

� Start SQL Server Agent, if not running.

� Expand the SQL Server Agent folder.

� Expand the Jobs folder.

� Find the job that was created by the ADD TRANDATA command. The name is based

on the server, instance, and database name, plus the iteration of the publication.It will look similar to the following: KTANCO\SQL2005-SQLLBE_SRC-1

� Right click the job and select Stop Job.

� Right click the job again and select Disable.

Prepare your DB2 target environment

1. Configure the Manager process on the target system

Execute the following commands on the <target> system.

� Start the command interface

Shell> cd <install location>


� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 19

Shell> ggsci

� Specify the port that the Manager should use.

GGSCI> EDIT PARAMS MGR

-- GoldenGate Manager Parameter file PORT <port>

� Start Manager

GGSCI> START MANAGER

Verify the results:

GGSCI> INFO MANAGER

2. Create target DB2 tables


You are advised to edit the table create scripts, tcust.sql, and update the database connection

information to match your system. For example, on the first line add:

CONNECT TO <database>

Shell> cd <install location> Shell> db2 –tf <install location>/dirsql/tcust.sql

Additional table create scripts for the sample database can be found in the GoldenGate for

DB2 installation directory named demo_db2_create.sql.

Verify the results:

Shell> db2 db2 => connect to <database> db2 => describe table tcustmer db2 => describe table tcustord db2 => quit

Initial Data Load

� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �

Exercise 2.

Initial Data Load using Direct Load Method

Objective

These steps configure initial load groups that copy source data and apply it to the target

tables.

Configure initial load capture

1. Add the initial data load extract batch task group

Execute the following commands on the <source> system to add an Extract process called

EINI<unique id>1.

� Execute the following command in GGSCI to create the batch task.

Shell> cd <install location> Shell> ggsci GGSCI> ADD EXTRACT EINI<unique id>, SOURCEISTABLE

� Verify the results:

GGSCI> INFO EXTRACT *, TASKS

2. Configure the initial data load Extract parameter file

� Execute the following command in GGSCI to open the editor.

GGSCI> EDIT PARAMS EINI<unique id>

� Add the following lines to the parameter file

-- -- GoldenGate Initial Data Capture -- for TCUSTMER and TCUSTORD -- EXTRACT EINI<unique id> SOURCEDB <dsn>, USERID <login>, PASSWORD <password> RMTHOST <target>, MGRPORT <port> RMTTASK REPLICAT, GROUP RINI<unique id> TABLE <owner/schema>.TCUSTMER; TABLE <owner/schema>.TCUSTORD;

1 The process names used in lab exercises, for example EINIBD, are made up of 1) one character for the

GoldenGate process (E for Extract, R for Replicat); 2) three or four to describe the process type (INI for initial data load, ORA for capture from or delivery to an Oracle database, etc.) and 3) two characters to

create a unique identifier (usually your initials).

Initial Data Load

� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �

Configure initial load delivery

3. Add the initial load delivery batch task group

Execute the following command in GGSCI to create the batch task on the <target> system.

GGSCI> ADD REPLICAT RINI<unique id>, SPECIALRUN

Verify the results:

GGSCI> INFO REPLICAT *, TASKS

4. Configure the initial load delivery parameter file

Execute the following command in GGSCI to open the editor on the <target> system.

GGSCI> EDIT PARAMS RINI<unique id>

Add the following lines to the parameter file.

-- -- GoldenGate Initial Load Delivery REPLICAT RINI<unique id> TARGETDB <database>, USERID <userid>, PASSWORD <password> DISCARDFILE ./dirrpt/RINI<unique id>.dsc, PURGE SOURCEDEFS ./dirdef/source.def MAP <owner/schema>.TCUSMTER, TARGET <owner/schema>.TCUSTMER; MAP <owner/schema>.TCUSTORD, TARGET <owner/schema>.TCUSTORD;

Note: Remember to use <db type>.def if you renamed the source.def when you transferred it

to the <target>.

Execute the initial load

5. Execute the initial load task


GGSCI> START EXTRACT EINI<unique id>

Verify the results:

GGSCI> VIEW REPORT EINI<unique id>


GGSCI> VIEW REPORT RINI<unique id>


� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �

Exercise 3.


Objective


�� Add the Extract process that will capture changes.

�� Add the trail that will store the changes.

�� Start the Extract process.

Steps to configure change

1. Add the Extract checkpoint group

Execute the following commands on the <source> system to create the Extract group.

GGSCI> ADD EXTRACT EMSS<unique id>, TRANLOG, BEGIN NOW

Verify the results:

GGSCI> INFO EXTRACT EMSS<unique id>

2. Create the Extract parameter file


� Execute the following command in GGSCI to open the editor.

GGSCI> EDIT PARAM EMSS<unique id>

� Add the following lines to the parameter file.

Note: MANAGESECONDARYTRUNCATIONPOINT is valid only for SQL Server 2005,

so should not be included for SQL Server 2000.

-- -- Parameter file to capture -- TCUSTMER and TCUSTORD Changes -- EXTRACT EMSS<unique id> --Include the following only for SQL Server 2005 TRANLOGOPTIONS MANAGESECONDARYTRUNCATIONPOINT -- If SQL Server Replication is also running, choose -- the NOMANAGESECONDARYTRUNCATIONPOINT option SOURCEDB <dsn>, USERID <login>, PASSWORD <password> RMTHOST <target>, MGRPORT <port> RMTTRAIL ./dirdat/<trail id>


� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �

TABLE <owner/schema>.TCUSTMER; TABLE <owner/schema>.TCUSTORD;

Note: Record the two characters selected for your <trail id>: ______. You will need this in

the next step and when you set up the Replicat.

3. Define the GoldenGate extract trails

Execute the following commands on the <source> system to create a trail.

GGSCI> ADD RMTTRAIL ./dirdat/<trail id>, EXTRACT EMSS<unique id>, MEGABYTES 50

Verify the results:

GGSCI> INFO RMTTRAIL *

4. Start the Extract process

On the <source> system, issue the following command in GGSCI to start the Extract process.

GGSCI> START EXTRACT EMSS<unique id>

Verify the results:

GGSCI> INFO EXTRACT EMSS<unique id>, DETAIL


� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �

Exercise 4.


� � � � � � � � � � � � � � �

Objective


�� Set up the checkpoint table on the target system.

�� Create a named group that includes the Replicat process and the checkpoint tables.

�� Configure the Replicat group by adding parameters.

�� Start the Replicat group.

Set up the checkpoint table

1. Create a GLOBALS file on the target system


� Create and edit the GLOBALS parameter file to add the checkpoint table.

Shell> cd <install location> Shell> ggsci GGSCI> EDIT PARAMS ./GLOBALS

In the text editor, type:

CHECKPOINTTABLE <owner/schema>.ggschkpt

� Record the checkpoint table owner and name, then save and close the file.

Table owner ____________________ name ___________________

Note: You could name the table anything you want, but for training purposes we are

using ggschkpt.

� Verify that the GLOBALS file was created in the root GoldenGate directory, and remove any file extension that was added.

2. Activate the GLOBALS parameters

For the GLOBALS configuration to take effect, you must exit the session in which the changes

were made. Execute the following command to exit GGSCI.

GGSCI> EXIT


� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �

3. Add a Replicat checkpoint table

On the <target> system, execute the following commands in GGSCI:

Shell> cd <install location> Shell> ggsci GGSCI> DBLOGIN SOURCEDB <database>, USERID <login>, PASSWORD <password> GGSCI> ADD CHECKPOINTTABLE


4. Add the Replicat group

Execute the following command on the <target> system to add a delivery group named

RDB2<unique id>.

GGSCI> ADD REPLICAT RDB2<unique id>, EXTTRAIL ./dirdat/<trail id>

Note: Refer to your Extract set up for the correct two-character <trail id>.

5. Create Replicat parameter file

Execute the following commands on the <target> system to bring up the parameter file in the

editor.

GGSCI> EDIT PARAM RDB2<unique id>

Type in the following parameters

-- -- Change Delivery parameter file to apply -- TCUSTMER and TCUSTORD Changes -- REPLICAT RDB2<unique id> TARGETDB <database>, USERID <login>, PASSWORD <password> HANDLECOLLISIONS SOURCEDEFS ./dirdef/source.def DISCARDFILE ./dirrpt/RDB2<unique id>.DSC, PURGE MAP <owner/schema>.TCUSTMER, TARGET <owner/schema>.TCUSTMER; MAP <owner/schema>.TCUSTORD, TARGET <owner/schema>.TCUSTORD;

Note: Remember to use <db type>.def if you renamed the source.def when you transferred it

to the <target>.

6. Start the Replicat process

GGSCI> START REPLICAT RDB2<unique id>

Verify the results:


� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �

GGSCI> INFO REPLICAT RDB2<unique id>

Discussion points

Search in the Windows/UNIX Reference Guide for the information on the following

questions.

1. When to use HANDLECOLLISIONS

When would you use HANDLECOLLISIONS? What does it do?

_________________________________________________________________________

_________________________________________________________________________

2. What information is supplied by SOURCEDEFS?

_________________________________________________________________________

_________________________________________________________________________

3. What is the purpose of the DISCARDFILE?

_________________________________________________________________________

________________________________________________________________________

Generate Activity and Verify Results

� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �

Exercise 5.

Generate Activity & Verify Results


�� Execute miscellaneous update, insert, and delete operations on the source system.

�� Verify the delivery of the changes to the target

�� Turn off the error handling used for initial load.

Verify your source SQL Server 2005 results

Steps to generate database operations

1. Generate inserts, updates, and deletes


� Go to SQL Server Management Studio, select your database and press New Query.

� If the correct database is not displayed in the drop down box (showing ggsdata above), click on the arrow and select it from the list.

� Click the File > Open and navigate to the demo_mss_misc.sql script and click Open

to open it in the input window.

� Execute the script by clicking the Execute Query button on the toolbar.

� Verify and record processing statistics with the following command in GGSCI.

GGSCI> SEND EXTRACT EMSS<unique id>, REPORT GGSCI> VIEW REPORT EMSS<unique id>

___________________________________________________________________

___________________________________________________________________

___________________________________________________________________

___________________________________________________________________

Generate Activity and Verify Results

� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �

� Verify the data by executing the following commands in the New Query window of

SQL Server Management Studio on the source:

select * from TCUSTMER; select * from TCUSTORD;

3. Verify your results on the target system

Execute the following commands on the <target> system to verify the target data.

Shell> cd <install location> Shell> db2 db2 => connect to <database> db2 => select * from TCUSTMER db2 => select * from TCUSTORD db2 => quit

Shell> ggsci GGSCI> SEND REPLICAT RDB2<unique id>, REPORT GGSCI> VIEW REPORT RDB2<unique id>

Turn off error handling

4. Turn off initial load error handling for the running delivery process

GGSCI> SEND REPLICAT RDB2<unique id>, NOHANDLECOLLISIONS

5. Remove initial load error handling from the parameter file

GGSCI> EDIT PARAMS RDB2<unique id>

Remove the HANDLECOLLISIONS parameter.

Exercise Name

� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �

GoldenGate for SQL Server to UNIX DB2 - Oracle

Documents

Transcript of GoldenGate for SQL Server to UNIX DB2 - Oracle