Teradata to Teradata: Max Protection - · PDF fileTeradata to Teradata: Max Protection Page 1...

of 20/20
Teradata to Teradata: Max Protection Page 1 Teradata to Teradata: Max Protection Objective Upon completion of this lesson, you will be able to keep two Teradata databases synchronized using the maximum protection method. During this lesson, you will learn how to: Prepare your user environment. Configure the change capture process to create a transaction log of Teradata changes in Max Protection mode. Execute the table copy process for the initial data synchronization process. Configure and start the change delivery process of database operations. Teradata to Teradata max protection configuration The diagram illustrates GoldenGate for Teradata in maximum protection mode. Teradata<server> Teradata <server> <dsn> database Windows/Unix Server <target> database Target <database> Network Replicat Collector Trails Manager <dsn> database database Source <database> Network Windows/Unix Server <source> Manager Network Network RSG TAM/VAM Extract
  • date post

    30-Jan-2018
  • Category

    Documents

  • view

    241
  • download

    2

Embed Size (px)

Transcript of Teradata to Teradata: Max Protection - · PDF fileTeradata to Teradata: Max Protection Page 1...

  • Teradata to Teradata: Max Protection

    Page 1

    Teradata to Teradata: Max Protection

    Objective

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

    synchronized using the maximum protection method.

    During this lesson, you will learn how to:

    Prepare your user environment.

    Configure the change capture process to create a transaction log of Teradata changes in Max Protection mode.

    Execute the table copy process for the initial data synchronization process.

    Configure and start the change delivery process of database operations.

    Teradata to Teradata max protection configuration

    The diagram illustrates GoldenGate for Teradata in maximum protection mode.

    Teradata

    Teradata

    database

    Windows/Unix Server

    databaseTarget

    Network

    Replicat

    Collector

    Trails

    Manager

    databasedatabase

    Source

    Network

    Windows/Unix Server

    Manager

    Network

    NetworkRSG TAM/VAM

    Extract

  • Teradata to Teradata: Max Protection

    Page 2

    GoldenGate is installed on a separate Windows or UNIX server for the source and target

    systems. Source and target both communicate with a Teradata server.

    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, you have a few strategies to select from, including Teradatas FastLoad

    utility or GoldenGates TableCopy feature, both of which have their pros and cons.

    This lesson demonstrates using the Teradata FastLoad utility to load the data at high speed to

    the target system.

    Configure Change Capture

    For VAM-based Teradata capture in Max Protection mode, the Extract process is configured

    to capture change data directly from the Teradata Access Module (TAM) and store the

    changes in data queues known as GoldenGate Trails.

    In Max Protection mode, the capture stores uncommitted transactional detail to a VAM trail.

    Once the transaction is committed, GoldenGate persists the data and sends a message back to

    Teradata indicating that the transaction has been successfully saved. Teradata will then

    release the transaction. If the data cannot be persisted, Teradata will rollback the transaction.

    A VAM trail must then be processed by another Extract capture process to sort all of the

    transactional details in commit order.

    In summary, two capture processes are configured. The first Extract creates a VAM log of all

    operations and the second Extract sorts them into commit order and creates a GoldenGate

    trail.

    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.

    Prerequisites

    The prerequisites for this lab include the following.

    GoldenGate installed in both the source and the target .

    Teradata ODBC installed in the Windows environment.

  • Teradata to Teradata: Max Protection

    Page 3

    Teradata Change Data Capture facility of the Teradata Database must be installed and configured.

    Teradata Access Module library, TAM.dll, copied to the GoldenGate installation location.

    Students should have been granted the security necessary to create replication groups.

    The Teradata ODBC, Change Data Capture facility, and the Teradata Access Module library

    are provided by NCR Corporation.

  • Prepare the Environment

    Page 4

    Exercise 1.

    Prepare the Environment

    Objective

    The goals of this exercise are to:

    Configure and start the Manager processes.

    Prepare source and target sample Teradata databases.

    Create ODBC data source name.

    Set up Teradata replication services.

    Configure the TAM initialization file.

    Configure the Manager processes

    1. Configure the Manager process on the source

    Execute the following commands on the system.

    Start the command interface

    shell> cd shell> ggsci

    Specify the port that the Manager should use.

    GGSCI> EDIT PARAMS MGR

    -- GoldenGate Manager Parameter file PORT

    Start Manager

    GGSCI> START MANAGER

    Verify the results:

    GGSCI> INFO MANAGER

  • Prepare the Environment

    Page 5

    Prepare the database

    2. Create ODBC data source name

    An ODBC system data source stores information about how to connect to the Teradata . Execute the following commands for a Teradata system.

    Create your system DSN for Teradata with a name of to connect to your source

    name. These examples show a DSN named GGSTera and a server named Tribble,

    but these should be changed to match your names.

    Click on the Options button. Select ANSI for the Session Mode and AAA for the DateTime

    Format.

    3. Create source files and load with initial data

    Execute the following commands on the system.

    Edit the script, demo_tera_ create.sql and demo_tera_insert.sql and change the

    to the identifier for your source database.

  • Prepare the Environment

    Page 6

    create table .tcustmer; create table .tcustord;

    For the script demo_tera_insert.sql enter the correct /,.

    Using the Teradata command interface, BTEQ, login and execute the scripts.

    Shell> bteq BTEQ> .logon /

    This will prompt you to enter the . Then you can run the script.

    BTEQ> .run file = /demo_tera_create.sql; BTEQ> .run file = /demo_tera_insert.sql;

    Verify the results:

    BTEQ> select * from .tcustmer; BTEQ> select * from .tcustord;

    4. Create the obey file to configure the Teradata replication group

    On the system, create the sql obey file RepGroupPro.sql with the following

    statement. Change the and to your values.

    Create Replication Group REPGROUP (.tcustmer, .tcustord, .statecode);

    5. Configure the Teradata Access Module initialization file VAMPRO.ini

    The initialization (.ini) file contains information to be passed to the TAM. These details

    include the replication mode, ODBC connection strings, the security token for the replication

    group, and other TAM variables.

    On your system, use an editor, such as WordPad, to create a text file named \VAMPRO.ini. This should contain the following information set to your

    values.

    Note: As of Teradata 12.0, the following rules apply:

    The RepliationGroupName parameter is no longer required. It is replaced by GroupID.

    If the replication group already exists, both the SecurityToken and GroupID must be entered.

    Multiple RSG connections may be supplied as shown in the example below.

    ; Sets the mode for this extract process ("Replication" or "TableCopy") Mode=Replication

    ; ODBC connection string used to access metadata from ; the data dictionary of the primary Teradata system

    DictOdbcConnString=DSN=;uid=;pwd=

  • Prepare the Environment

    Page 7

    ; ODBC connection string used to execute management functions ; (such as CREATE REPLICATION GROUP) on the primary Teradata system

    MgmtOdbcConnString=DSN=;uid=;pwd=

    ; Name of the replication group is not needed when using ; CreateGroupStmtFile ; Otherwise for Teradata v2r6 enter (must be uppercase):

    ; ReplicationGroupName=REPGROUP ; For Teradata v12 enter: ; GroupID= (enter the group ID number)

    ; If the group already exists, enter Security token ; SecurityToken= (enter the security token) ; OR enter the name of the file containing CREATE REPLICATION GROUP ; statement for a new group (set up in step 4) CreateGroupStmtFile=./RepGroupPro.sql

    ; Character set (ASCII, UTF16) CharacterSet=ASCII

    ; RSG Node addresses - specify name or IP, with optional port

    ControlRSG=:5298

    DataRSG1=:5298 ; As of Teradata 12.0 multiple RSG connections may be included

    ; DataRSG2=:

    ; DataRSG3=:

    ; Specifies which types of messages are encrypted (None, Control, Data, ; or All) Encryption=None

    Prepare the Teradata target environment

    6. Configure the Manager process

    Execute the following command on the Teradata system.

    Start the command interface

    shell> cd shell> ggsci

    Specify the port that the Manager should use.

    GGSCI> EDIT PARAMS MGR

    -- GoldenGate Manager Parameter file PORT

    Start Manager

  • Prepare the Environment

    Page 8

    GGSCI> START MANAGER

    Verify the results:

    GGSCI> INFO MANAGER

    7. Create ODBC data source name

    An ODBC system data source stores information about how to connect to the Teradata . Execute the following commands on the Teradata system.

    Create your system DSN for Teradata with a name of to connect