GoldenGate for MS SQL Server 2008 to Oracle Page 1 GoldenGate for MS SQL Server 2008 to Oracle Objective Upon completion of this lesson, you will be able to configure GoldenGate to provide MS SQL Server to Oracle synchronization. During this lesson, you will learn how to: Prepare your user environment. Configure and execute the initial data synchronization process. Configure and start the change capture process of database operations. Configure and start the change delivery process of database operations. MS SQL Server to Oracle configuration The following diagram illustrates a GoldenGate configuration for log-based replication from MS SQL Server source data to an Oracle target database on Windows or UNIX. Windows server <source> MS SQL Server <dsn> Source <schema> Extract Manager Log <target> server Oracle Target <owner/schema> Replicat Collector Trails Manager Network
29
Embed
GoldenGate for MS SQL Server 2008 to Oracle GoldenGate for MS SQL
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
GoldenGate for MS SQL Server 2008 to Oracle
Page 1
GoldenGate for MS SQL Server 2008 to Oracle
Objective
Upon completion of this lesson, you will be able to configure GoldenGate to provide MS SQL
Server to Oracle synchronization.
During this lesson, you will learn how to:
Prepare your user environment.
Configure and execute the initial data synchronization process.
Configure and start the change capture process of database operations.
Configure and start the change delivery process of database operations.
MS SQL Server to Oracle configuration
The following diagram illustrates a GoldenGate configuration for log-based replication from
MS SQL Server source data to an Oracle target database on Windows or UNIX.
Windows server <source>
MS SQL Server
<dsn>
Source
<schema>
Extract
Manager
Log
<target> server
Oracle
Target <owner/schema>
Replicat
Collector
Trails
Manager
Network
GoldenGate for MS SQL Server 2008 to Oracle
Page 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. And finally, source definitions are generated and
transfer to the target system.
Configure Initial Data Synchronization
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.
This lesson demonstrates using Extract to pull data from the source files and send it directly
to the Replicat component 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 Replicat process is configured to
deliver the captured change data into the target database.
<source> server <target> server
Initial
Replicat
MS SQL Server
<dsn>
Target
<schema>
Oracle
Source<owner/schema>
Initial
Extract
Network
Exercise Name
Page 3
Exercise 1.
Prepare the Environment
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 2008 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:
Exercise Name
Page 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.
Exercise Name
Page 5
The New Database dialog box appears. In the Name box, type the <database> from
the Lab Preparation worksheet.
Exercise Name
Page 6
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.
Exercise Name
Page 7
The New Login dialog box appears.
For Name, type the <login>.
Select Authentication,
Exercise Name
Page 8
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.
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:
Exercise Name
Page 9
create schema <schema_name>;
And press the Execute button from the toolbar.
Now you need to associate the new user with the login and the schema that you have created
with the new database.
In the SQL Query interface, type in:
create user <user_name>
for login <select login_name>
with default_schema=<schema_name>;
And press the Execute button from the toolbar.
Exercise Name
Page 10
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.
Exercise Name
Page 11
Select the SQL Server Native Client 10.0 driver and then click Finish. The Create a
New Data Source to SQL Server dialog box appears.
For Name, type <dsn>.
Exercise Name
Page 12
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.
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.
Exercise Name
Page 13
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.
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, 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.
Exercise Name
Page 14
Verify the results using the following commands in the input window:
sp_help tcustmer
go
sp_help tcustord
go
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.
Exercise Name
Page 15
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 2008).
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.
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