HP NonStop SQL/MX to SQL Server - Oracle | Integrated · PDF fileHP NonStop SQL/MX to SQL...

HP NonStop SQL/MX to SQL Server

1


Objective

Upon completion of this lesson, you will be able to keep two heterogeneous databases

synchronized, in this case NonStop SQL/MX to MS SQL Server.

During this lesson, you will learn how to:

Prepare your environment to configure the GoldenGate processes

Configure and execute the initial data load

Configure and start the change capture of database operations

Configure and start the change delivery of database operations

NonStop SQL/MX to SQL Server configuration

The following diagram illustrates a configuration with the source SQL/MX database on the

NonStop. GoldenGate processes running on the NSK OSS pick up changes from the TMF

audit trail using a VAM interface and apply them to an SQL Server database on a Windows

platform.

NonStop

NonStop OSS

<source>

TMF Audit

TrailVamserv

Source

database

Manager

Extract

Windows server <target>

MS SQL Server

<dsn>

Target

<schema>Replicat

Collector

Trails

Manager

Network


2

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.

Initial Data Load

To initially load data between heterogeneous databases, use the GoldenGate application to

perform your initial data synchronization while the application remains active. This lesson

demonstrates the direct method using Extract to pull data from the source files and sending

the data directly to Replicat on the target system.

Configure Change Capture

For audited tables, the Extract process is configured to capture change data directly from the

TMF audit trails via a VAM interface and store the changes in a data queue known as

GoldenGate remote trails.

Configure Change Delivery

Once the tables have been initially loaded with data and the Extract process is capturing all

operations, the Replicat process is configured to deliver the captured operations to the target

database.

NonStop <source>

NonStop OSS

ExtractSourcedatabase

<target> server

SQL Server

Target <owner/schema>

Initial

Replicat

Network


3

Exercise 1.


Objective

The goals of this exercise are to:

Configure and start the Manager processes.

Prepare the source and target sample databases.

Preparing your source HP NonStop environment

1. Configure and start the Manager process on the source system

The Manager provides a number of important functions, including monitoring critical system

components and starting GoldenGate processes.

Before running any other GoldenGate programs on the OSS, you must start Manager. Before starting Manager, you must edit Manger’s parameter file and add the PORT.

Execute the following commands on the <source> to start the vi program for editing

the parameters:

OSS> cd <install location>

OSS> ./ggsci

GGSCI> EDIT PARAMS MGR

Add the following parameters, then save the file and quit the editor.

-- GoldenGate Manager Parameter file

PORT <port>

Start the Manager on the <source> using the following commands.

GGSCI > START MANAGER

Verify the results:

GGSCI> INFO MANAGER

GGSCI> EXIT


4

2. Create and load source files

Execute the following commands on the <source> system to create and load the source

tables.

Create the catalog and schema


OSS> mxci

>> create catalog <catalog>;

>> set catalog <catalog>;

>> create schema <schema>;

>> set schema <schema>;

Create and populate the tables

>> obey demo_sqlmx_create.sql;

>> obey demo_sqlmx_insert.sql;

Verify the results:

>> select * from tcustmer;

>> select * from tcustord;

>> exit;

3. Create source definitions

Note: Source definitions are required even though the source and target databases have the

same structure because ASSUMETARGETDEFS is not supported for this ODBC connection.

Execute the following commands on the <source> system to create the source definitions

file.

Create the DEFGEN parameter file and add its parameters.


OSS> ./ggsci

GGSCI> edit param defgen

DEFSFILE dirdef/source.def, PURGE

SOURCEDB <catalog>

TABLE <schema>.TCUSTMER;

TABLE <schema>.TCUSTORD;

Save the file and exit from GGSCI.

Execute DEFGEN from the command line with the following command.

OSS> defgen paramfile dirprm/defgen.prm

Transfer the source definitions to the target system

Shell> ftp <target>

Name (<source>:): <login>

Password: password

ftp> ascii


5

ftp> cd <install location>/dirdef

ftp> lcd <install location>/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. SMX.def).

Prepare the SQL Server 2005 target system

Install Manager

1. Configure Manager process on the target

Execute the following commands on the <target> system.

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

the same server.

Shell> cd <install location>

Shell> ggsci

GGSCI> EDIT PARAMS MGR

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

-- GoldenGate Manager Parameter file

PORT <port>

Start Manager.

GGSCI> START MANAGER

Verify the results:

GGSCI> INFO MANAGER

Steps to 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.


6

Note: These instructions assume SQL Server Authentication which requires the

more complex, double layer, of authentication. For only 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.

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

the Lab Preparation worksheet.


7

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.


8

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 User Mapping.


9

In the upper Users mapped to this login area, activate the checkmark next to your

database.

In the lower Database role membership for <database> area,, check the box for the

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


10

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 (…).


11

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.

Note: For SQL Server 2000, you may use any ODBC driver supported by the

database. For SQL Server 2005, however, you must use the ODBC driver that is

included with Microsoft Data Access Components (MDAC). Both Extract and

Replicat will abend if the SQL Native Client ODBC driver that is provided with SQL

Server 2005 is used.


12

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

For a description, type "GG Training Data source" when creating this source DSN.

This field is optional.

For Which SQL Server do you want to connect to, select the server name.

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.


13

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.


14

5. Create the practice tables


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


15

Initial Data Load: NSK SQL/MX to SQL Server

16

Exercise 2.


Objective


Configure and execute the initial data load capture

Configure and execute the initial data delivery

Configure initial load

1. Add the initial load capture batch task group

Execute the following commands on the <source> system to add an Extract group named EINI<unique id>1.

Start the command interface.

OSS> ./GGSCI

Add the Extract batch task.

GGSCI> ADD EXTRACT EINI<unique id>, SOURCEISTABLE

Verify the results:

GGSCI> INFO EXTRACT *, TASKS

2. Configure the initial load capture parameter file

Execute the following commands on the <source> system.

GGSCI> EDIT PARAMS EINI<unique id>

--

-- GoldenGate Initial Data Capture

-- for tables as listed below

--

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

identify the type of process (E for Extract, R for Replicat); 2) three characters to describe the type of

process (INI for initial data load, ORA for capture from or delivery to an Oracle database, etc.) and 3) three

characters usually made up of the student’s initials plus a sequential number to uniquely identify multiple

occurrences of that type of process.


17

EXTRACT EINI<unique id>

SOURCEDB <catalog>

RMTHOST <target>, MGRPORT 7809

RMTTASK REPLICAT, GROUP RINI<unique id>



3. Configure the initial data load Replicat parameter file


Execute the following command in GGSCI to open the editor.

GGSCI> EDIT PARAMS RINI<unique id>

Add the following lines to the parameter file

-- GoldenGate Initial Data Load Delivery

--

REPLICAT RINI<unique id>

TARGETDB <dsn>, USERID <login>, PASSWORD <password>

DISCARDFILE ./dirrpt/RINI<unique id>.txt, PURGE

SOURCEDEFS ./dirdef/source.def

MAP <schema>.TCUSTMER, TARGET <owner/schema>.TCUSTMER;

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

4. Add the initial load delivery batch task group


GGSCI> ADD REPLICAT RINI<unique id>, SPECIALRUN

Verify the results:

GGSCI> INFO REPLICAT *, TASKS

5. Execute the initial load process


GGSCI> START EXTRACT EINI<unique id>

Verify the results:


GGSCI> VIEW REPORT EINI<unique id>


18

Exercise 3.


Objective


Configure and add the Extract process that will capture changes for SQL/MX tables.

Add the trail that will store the changes.

Start the Extract process.

Configure change capture

1. Create the Extract parameter file

Execute the following commands on the <source> system to define an Extract named

ESMX<unique id> that will work with VAMSERV to capture changes to GoldenGate trails.

Note: SQL/MX transactions are logged in the NonStop Guardian TMF audit trails. The VAMSERV program communicates between the OSS Extract and the TMF audit trails.

GGSCI> EDIT PARAMS ESMX<unique id>

--

-- Change Capture parameter file to capture

-- TCUSTMER and TCUSTORD Changes

--

EXTRACT ESMX<unique id>

SOURCEDB <catalog>

RMTHOST <target>, MGRPORT <port>

RMTTRAIL ./dirdat/<trail id>



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

step 3 and later when you set up the Replicat.

2. Add the Extract group


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


19

Verify results:

GGSCI> INFO EXTRACT ESMX<unique id>

3. Define the GoldenGate trail

Execute the following commands on the <source> system to add the trail declared in the

ESMX<unique id> Extract parameters.

GGSCI> ADD RMTTRAIL ./dirdat/<trail id>, EXTRACT ESMX<unique id>,

MEGABYTES 5

4. Start the Extract process


GGSCI> START EXTRACT ESMX<unique id>

Verify the results:

GGSCI> INFO ESMX<unique id>

Discussion points

1. Identifying a remote system

What parameters are used to identify the remote target system?

___________________________________________________________________

___________________________________________________________________

2. Sizing the GoldenGate trail

Where do you set how large a GoldenGate trail file may get before it rolls to the next file?

What option do you use?

___________________________________________________________________

___________________________________________________________________


20

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 checkpoints

1. Edit a GLOBALS file on the target system


Edit the GLOBALS parameter file to add the checkpoint table.


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.

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


21

3. Add a Replicat checkpoint table


This step adds the checkpoint table that you specified when you created the GLOBALS

parameter file. It will be created in the <dsn> database.

Run GGSCI on the target.


Shell> ggsci

Execute the following commands in GGSCI.

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

<password>

GGSCI> ADD CHECKPOINTTABLE

Configure delivery

4. Add the Replicat checkpoint group

Execute the following commands on the <target> system to create the Replicat group named

RMSS<unique id>.

GGSCI> ADD REPLICAT RMSS<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 command on the <target> system to edit the Replicat

parameter file.

GGSCI> EDIT PARAM RMSS<unique id>

Add the following lines to the parameter file.

REPLICAT RMSS<unique id>

TARGETDB <dsn>, USERID <login>, PASSWORD <password>

HANDLECOLLISIONS

SOURCEDEFS ./dirdef/source.def

DISCARDFILE ./dirrpt/RMSS<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 the <target>.


22

4. Start the Replicat process


Execute the following command in GGSCI to start the Replicat process.

GGSCI> START REPLICAT RMSS<unique id>

Verify the results:

GGSCI> INFO REPLICAT RMSS<unique id>

Generate Activity and Verify Results

23

Exercise 5.


Objective


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 the initial load.

Generate database operations

1. Execute miscellaneous update, insert, and delete operations

Execute the following commands on the <source> system to run a script that will generate

activity in the source SQL/MX database.

OSS> mxci

>> SET CATALOG <catalog>;

>> SET SCHEMA <schema>;

>> obey demo_sqlmx_misc.sql;

Verify change capture and delivery

2. Verify your results on the source system


>> SELECT * FROM <schema>.TCUSTMER;

>> SELECT * FROM <schema>.TCUSTORD;

>> EXIT;

Verify your target SQL Server 2005 results

3. Verify your results on the SQL Server 2005 target

Verify and record processing statistics on the <target> with the following command

in GGSCI.


24

GGSCI> SEND REPLICAT RMSS<unique id>, REPORT

GGSCI> VIEW REPORT RMSS<unique id>

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;

Turn off error handling

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


GGSCI> SEND REPLICAT RMSS<unique id>, NOHANDLECOLLISIONS

5. Remove initial load error handling from the parameter file

GGSCI> EDIT PARAMS RMSS<unique id>

Remove the HANDLECOLLISIONS parameter.

HP NonStop SQL/MX to SQL Server - Oracle | Integrated · PDF fileHP NonStop SQL/MX to SQL...

Documents

Transcript of HP NonStop SQL/MX to SQL Server - Oracle | Integrated · PDF fileHP NonStop SQL/MX to SQL...