attunity replicate user and reference guide...editingendpointconfigurationinformation 136...

Attunity Replicate Setup andUser Guide

Version 6.4

October 30, 2019

Attunity Replicate Setup and User Guide, 6.4

Copyright © 2019 Qlik Analytics (ISR) Ltd. All rights reserved.

Primary Author: Charlton Book

The Programs (which include both the software and documentation) contain proprietary information;they are provided under a license agreement containing restrictions on use and disclosure and are alsoprotected by copyright, patent, and other intellectual and industrial property laws. Reverseengineering, disassembly, or decompilation of the Programs, except to the extent required to obtaininteroperability with other independently created software or as specified by law, is prohibited.

The information contained in this document is subject to change without notice. If you find anyproblems in the documentation, please report them to us in writing. This document is not warranted tobe error-free. Except as may be expressly permitted in your license agreement for these Programs, nopart of these Programsmay be reproduced or transmitted in any form or by any means, electronic ormechanical, for any purpose.

If the Programs are delivered to the United States Government or anyone licensing or using thePrograms on behalf of the United States Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, endpoints, and related documentation and technicaldata delivered to U.S. Government customers are "commercial computer software" or "commercialtechnical data" pursuant to the applicable Federal Acquisition Regulation and agency-specificsupplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of thePrograms, including documentation and technical data, shall be subject to the licensing restrictions setforth in the applicable Attunity license agreement, and, to the extent applicable, the additional rightsset forth in FAR 52.227-19, Commercial Computer Software—Restricted Rights (June 1987). QlikAnalytics (ISR) Ltd., 70 Blanchard Road, Burlington, MA 01803

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or otherinherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if thePrograms are used for such purposes, andwe disclaim liability for any damages caused by such use ofthe Programs.

Attunity is a registered trademark of Qlik Analytics (ISR) Ltd. and/or its affiliates. Other namesmay betrademarks of their respective owners.

The Programsmay provide links toWeb sites and access to content, products, and services from thirdparties. Qlik Analytics (ISR) Ltd. is not responsible for the availability of, or any content provided on,third-party Web sites. You bear all risks associated with the use of such content. If you choose topurchase any products or services from a third party, the relationship is directly between you and thethird party. Attunity is not responsible for: (a) the quality of third-party products or services; or (b)fulfilling any of the terms of the agreement with the third party, including delivery of products orservices andwarranty obligations related to purchased products or services. Qlik Analytics (ISR) Ltd. isnot responsible for any loss or damage of any sort that you may incur from dealing with any third party.

Contents1 | Introduction 47Replication Explained 47

Attunity Replicate 48

Limitations and Considerations 49

System Architecture 51

Replication Tasks 52Using Multiple Tasks 52

Full Load and CDC Processes 53

Replication Topologies 53One to One 54

Logical Independence 54

Hub and Spoke 54

2 | Installing Attunity Replicate 55Installation Prerequisites 55Software Requirements 55

Windows Software Requirements 56

Linux Software Requirements 56

Windows Permissions 56

Recommended Hardware Configuration 57

Supported Endpoints 59

Installing or Upgrading Attunity Replicate on Windows 59Installation Instructions 60

Upgrade Instructions 60

Starting and Stopping the Attunity Replicate Server on Windows 62

Silently Installing Attunity Replicate 62

Creating a Response File 62

Running the Silent Install 63

Silently Upgrading Attunity Replicate 63


Attunity Replicate Setup and User Guide | Page 3Qlik Analytics (ISR) Ltd.

Running a Silent Upgrade 63

Silently Uninstalling Attunity Replicate 64


Running a Silent Uninstall 65

Changing the Data Directory Location on Windows 65

Installing Attunity Replicate on Linux 67Replicate Instances and Services on Linux 68

Installation Prerequisites and Procedures 69

Prerequisites 69

Installing Attunity Replicate on Linux 69

Attunity Replicate Server Procedures 72

Verifying that an Attunity Replicate Instance is Running 72

Starting and Stopping an Attunity Replicate Instance 72

Upgrading Attunity Replicate 73

Resolving Configuration File Conflicts 74

Uninstalling Attunity Replicate 75

Working with Additional Replicate Instances 76

Installing an Instance of Replicate as a Service 77

Uninstalling an Instance of a Replicate Service 77

Changing the Data Directory Location on Linux 78

3 | Security Considerations 79Securing Access to the Attunity Replicate Web UI 79

Setting Up Replicate Console HTTPS Support 80Checking if an SSL Certificate is Installed 80

Using the Self-Signed Certificate 80

Setting Up Attunity Replicate Server HTTPS Support 81Replacing the Self-Signed SSL Certificates on Linux 81

Examples of the Scrambled Private Key Password 82

Replacing the Self-Signed Certificate on Windows 83

Changing the Server Password 84

Protecting Replicate Passwords 86


The Master Key File 87

Changing and Protecting the Master Key 87

Changing the Master Key Replacement 88

Protecting the Master Key File from Misuse 89

Master Key Considerations when Exporting and Importing Tasks 89

Encrypting the User Permissions File 90

Securing Connections to Endpoints 91

Application Security 92

Using External Credentials 92Limitations and Considerations 92

Changing the Default Addon Name 93

Step 1: Edit the MyPasswordProvider.c File 93

Step 2: Compile the Code 93

Step 3: Edit the addons_def.json.sample File 93

Step 4: Configure the Endpoints 94

4 | Overview of Attunity Replicate Endpoints 95Supported Replicate Endpoints 95

Using ARC CDC Agents as Endpoints 95

Replicate Data Types 96

Supported DDL Statements 98How Replicate Handles DDL Changes 98

Limitations when Capturing DDL Changes 98

Configuring Replicate to Automatically Replace the User-Entered Pass-word 99Defining Multiple Endpoints to use the same Automatically Changed Password 101

5 | Using the Attunity Replicate Console 102Accessing the Attunity Replicate Console 102Accessing Attunity Replicate from a Remote Computer 103

Attunity Replicate UI Server Configurations 104

Configuration 1: Replicate Server Running on Windows 104


Configuration 2: Replicate Server Running on Linux 104

Configuration 3: Replicate UI Console and Replicate Server Running on Linux 105

Multiple Users Connecting to a Single Console 106

Tasks View 106Viewing Specific Tasks 109

Designer Mode 109

Monitor Mode 111

Server View 112

List Actions 112

6 | Getting Started: An Attunity Replicate Tutorial 114What You Need 114

Open the Attunity Replicate Console 115

Add an Oracle Endpoint as a Source 115

Add a Microsoft SQL Server database as a Target 117

Add a Replication Task 119Add a Replication Task to the Attunity Replicate Console 119

Add the Source and Target Endpoints to the Task 121

Select Tables for the Replication Task 123

Run and Monitor the Replication Task 124

View the Replicated Tables in Microsoft SQL Server 125

7 | Defining Tasks 127Adding Tasks 128Bidirectional Replication 132

Limitations 132


Setting up Bidirectional Replication 133

Using Bidirectional Replication with the File Channel Endpoint 134

Editing and Viewing a Task Description 135

Working with Endpoints 135Adding an Endpoint 136


Editing Endpoint Configuration Information 136

Viewing Endpoint Configuration Information 137

Testing an Endpoint Connection 137

Duplicating Endpoints 138

Searching for Endpoints 138

Deleting Endpoints 138

Adding a Source and Target Endpoint to a Task 138

Adding Tables and/or Views to a Task 140Searching for Tables/Views to use in a Replication Task 142

Selecting Specific Tables/Views for Replication 143

Removing Specific Tables/Views from a Replication Task 144

Creating Table/View Selection Patterns 144

Setting Load Order 145

Editing a Replication Task 146

Searching for Tasks 147

Deleting a Replication Task 147

Exporting and Importing Tasks 147Exporting Tasks 148

Importing Tasks 150

Editing an Exported (json) File 151

Making Changes to the Endpoint Connection Information 152

8 | Adding and Managing Source Endpoints 154Using Amazon RDS for SQL Server as a Source 155Prerequisites 156

Limitations 158

Non-Supported Amazon RDS for SQL Server Security Features 160

Required Permissions 160

Supported Compression Methods 160

Amazon RDS for SQL Server Source Data Types 160

Non-Supported Data Types 164

Homogeneous Replication 164


Data Type Exceptions 164

Column and Table Collation 165

Preparing the Amazon RDS for SQL Server Database for Replication 166

Setting up Amazon RDS for SQL Server for CDC (Change Data Capture) 166

Preparing Amazon RDS for SQL Server Backup and Recovery 167

Defining Amazon RDS for SQL Server Database Settings 168

Working with Windows Authentication 168

Setting Connection Properties 168

Artifacts Created by Replicate in the Database 171

Using Amazon RDS for MySQL as a Source 172Prerequisites 172

Attunity Replicate Server for Windows 173

Attunity Replicate Server for Linux 173

Amazon RDS for MySQL Replication 173

Setting up Amazon RDS for MySQL for CDC (Change Data Capture) 174

Replicating 4-byte UTF8 Emojis 174

Limitations 174

Security Requirements 175

Data Types 175


Setting General Connection Properties 179

SSL Authentication Options 181

Selecting a Schema 181

Setting Advanced Connection Properties 182

Internal Parameters 182

Settings Summary 182

Using Amazon RDS for PostregSQL as a Source 183Source Prerequisites 183

Client Side 183


Setting up Amazon RDS for PostgreSQL for CDC (Change Data Capture) 185

Using an Account without the "rds_superuser" Role 185


Limitations 187

Amazon RDS for PostregSQL Source Data Types 188


Replication of Partitioned Tables 192

Data Type Considerations and Exceptions 192







Removing Replicate Artifacts from the Amazon RDS for PostregSQL Database 197

Using ARC CDC Solutions in Attunity Replicate 199Prerequisites for Using ARC CDC Solutions 199

Additional Prerequisites when Using ARC Non-Relational Sources 200

ARC CDC Solution Security Considerations 201

Encrypting Communications Between Replicate and ARC Data Sources 201

Limitations 203

ARC Source Data Type Mapping 203

Working with ARC CDC Solutions 205

Create an ARC CDC Solution in Attunity Replicate Connect Studio 205

Add the ARC Data Source to Attunity Replicate 205

Add the ARC CDC Solution Endpoint to a Task 209




Using a File as a Source 212General Overview 212

File Source Overview 213

Reference Files 213

Full Load Files 214

Change Files 215


Prerequisites 216

Limitations 216


Defining Tables and Full Load Data 223

Setting Advanced Options 225



Using Google Cloud SQL for MySQL as a Source 229Prerequisites 229



Google Cloud SQL for MySQL Replication 230

Verifying that Google Cloud SQL for MySQL is Set Up for CDC (Change Data Cap-ture) 231


Limitations 231


Data Types 232








Using Google Cloud SQL for PostgreSQL as a Source 240Prerequisites 240


Limitations 241

Supported Data Types 242










Using Hadoop as a Source 250Prerequisites 250

Limitations 251


Hadoop Endpoint Source Data Types 251

Unsupported Data Types 252





Using IBMDB2 for iSeries as a Source 261Prerequisites 261

Client 261

Change Processing 262


Limitations 264

IBM DB2 for iSeries Database Source Data Types 265



Overriding CCSID to Character Set Mapping 268

Adding the RRN Column to Target Tables 269

Replicating System Names 270

Skipping Journal Validation 270



Using IBMDB2 for LUW as a Source 272Prerequisites 272


Client Prerequisites 272

IBM DB2 for LUW Server Prerequisites 274


Limitations 275

IBM DB2 for LUW Database Source Data Types 276





Using IBMDB2 for z/OS as a Source 281Prerequisites 281

Install the R4Z Product on z/OS 282

ODBC Requirements 282


Change Data Capture Requirements 283

Limitations 283

Handling Actions Resulting in Subtype 83 284

Controlling the CDC Process 285

Control Program Invocation Syntax 286

Control Program Completion Codes 287

Sample Jobs (in the INSTALL library) 288

Enabling the CDC Process (auto-activation) 288

Establishing R4Z CDC Services 289

IBM DB2 for z/OS Database Source Data Types 290



Overriding CCSID to Character Set Mapping 294

Change Data Capture Properties 295

Setting Internal Parameters 297

R4Z Configuration Dependency on Host 298


Sample XMIT Files “Receive” Job 299


Using IBM Informix as a Source 300Prerequisites 300

Limitations 301


IBM Informix Database Source Data Types 302






Using IBM Netezza as a Source 307Prerequisites 307

IBM Netezza Data Types 307


Setting Internal Parameters 310


Setting Change Processing Parameters 310

Prerequisites 310

Limitations 311

Configuring Change Processing Settings 312

Using a Microsoft Azure SQL Managed Instance as a Source 313Prerequisites 314

Preparing the Microsoft Azure SQL Managed Instance Database for Replication 316

Limitations 319

Non-Supported Microsoft Azure SQL Managed Instance Security Features 320



Microsoft Azure SQL Managed Instance Source Data Types 321








Using Microsoft SQL Server as a Source 330Supported Editions 331

Prerequisites 331

Limitations 334

Non-Supported Microsoft SQL Server Security Features 336

Working with Microsoft SQL Server AlwaysOn Availability Groups 336

Prerequisites 336

Configuring Replicate to Access the AlwaysOn Listener 337

Limitations 337

Accessing Backup Logs in AlwaysOn Availability Groups 338

Setting up a Non-Sysadmin User when Working with AlwaysOn AvailabilityGroups 338


Setting up a Non-Sysadmin User 339


Microsoft SQL Server Source Data Types 340





Preparing the Microsoft SQL Server Database for Replication 346

Preparing Microsoft SQL Server Backup and Recovery 346

Setting up Microsoft SQL Server for Replication 347

Replicating Tables that do not have a Primary Key 347

Defining Microsoft SQL Server Database Settings 348

Working with Windows Authentication 349







Using a MySQL-Based Database as a Source 357Prerequisites 358

General Prerequisites 358



Enable Binary Logging 359

Cluster Prerequisites 360


Limitations 361


MySQL Database Source Data Types 363








Using ODBC to Connect to a Source 371Prerequisites 371



Limitations 373

ODBC Source Data Types 373





Using ODBC with CDC as a Source 382Prerequisites 382

Replicate Server for Windows 382

Replicate Server for Linux 383


Limitations 383

ODBC with CDC Source Data Types 384



Prerequisites 390

Limitations 392


Using Oracle as a Source 394Supported Oracle Database Editions 395

Prerequisites 395

Limitations 396


General Permissions 398

Access Privileges when using Oracle LogMiner to Access the Redo Logs 399

Access Privileges when using Attunity Log Reader to Access the Redo Logs 400

Required ASM Privileges 401

Supported Encryption Methods 402


Supported Standby Configurations 403

Redo Log Files - Access Method Guidelines 405

Handling Shrink Space Operations 405

Replicating Nested Tables 406

Prerequisites 406

Supported Nested Table Types 406

Limitations 407

How Nested Tables are Replicated 407

JOIN Statement Example 407

Oracle Source Data Types 408



Preparing the Oracle Database for Replication 412

Provide Oracle Account Access 412

Ensure that ARCHIVELOG Mode is On 412


Setting up Supplemental Logging 412

Working with Oracle on Amazon RDS 415



Setting Advanced Connection Properties Using Oracle LogMiner 418

Setting Advanced Connection Properties Using Attunity Log Reader 421

Finding the Wallet Entries used for TDE Encryption 429

Using PostgreSQL as a Source 431Source Prerequisites 431

Client Side 431

Server Side 433


Using an Account without the "superuser" Role 434

Limitations 435

PostgreSQL Source Data Types 436











Using SAP Application as a Source 446Prerequisites 446

Supported SAP Packages 446

Set up a Source Endpoint for your SAP Application 447

Install the SAP NetWeaver RFC Client 447

Install the Attunity Replicate for SAP Client on the SAP Machine 447

The Installation Procedure 448


SAP Users for Replicate 448

Authorizations for Replicate 449

Importing the Data-file 450

Importing the Co-file 450

Managing Business Groups and Tables 453

Target Collation 455

Limitations 455

SAP Application Source Data Types 455


Setting Advanced Properties 459



Using SAP Application (DB) as a Source 461Prerequisites 461

Set up a Source Endpoint for your SAP Application (DB) 461

Install the Attunity Replicate for SAP Client on the SAP Machine 462

The Installation Procedure 462

SAP Users for Replicate 463

Authorizations for Replicate 463

Importing the Data-file 464

Importing the Co-file 465

Managing Business Groups and Tables 468

Target Collation 470

Limitations 470

SAP Application (DB) Source Data Types 470





Using SAP HANA as a Source 474Prerequisites 475

Port 475


Required Clients 475


Limitations 476

Permissions 477





Trigger-based CDC 480

Log-based CDC 480



Using SAP Sybase ASE as a Source 482Prerequisites 482


Replicate on Windows 483

Replicate on Linux 483

Limitations 483


SAP Sybase ASE database Source Data Types 484






Handling the Secondary Truncation Point 489

Using Teradata Database as a Source 490Prerequisites 490




Teradata Source Data Types 492




Prerequisites 495

Limitations 496


9 | Adding and Managing Target Endpoints 499Using Actian Vector as a Target 501Prerequisites 501

Actian Vector Windows Environment Prerequisites 502

Actian Vector Linux Environment Prerequisites 502

Limitations 502

Permissions 503

Actian Vector Data Types 503





Using Amazon EMR as a Target 507Prerequisites 508

Limitations 509

Change Data Partitioning on Amazon EMR 509

Amazon EMR Endpoint Target Data Types 510





Using Amazon Kinesis Data Streams as a Target 517Prerequisites 517

Transaction Processing by the Consumer 519

How it Works 520

Transaction Consistency from a Consumer Perspective 520

Limitations 521



Mapping from Attunity Replicate Data types to Avro 523


Overriding the Default Settings 526




The Attunity Envelope 528

Decoding a Self-Describing Message 530

Decoding a Message by Referenced Schema ID 530

Typical Consumer Logic 531

Metadata and Data Messages 531

Metadata Message 531

Data Message 532

Using Amazon Redshift as a Target 536Introducing the Amazon Redshift Target Endpoint for Attunity Replicate 536

Limitations 537

Amazon Redshift Database Prerequisites 537

Get Started with Amazon Redshift 537

Sign up for an Amazon S3 Bucket 538

Security 538

Amazon Redshift Data Types 539

Setting General Connection Parameters 541




Using Amazon S3 as a Target 546Prerequisites 546

Amazon S3 Target Overview 548

DDL Handling 549

Limitations 549

Change Data Partitioning 549


Amazon S3 Target Data Types 550





Generating Reference Files 561

Content-Type and Content-Encoding Properties 562

Using a File as a Target 563File Target Overview 563

DDL Handling 565

Limitations 565


File Target Data Types 566

Setting General Properties 567





Using Google Cloud SQL for MySQL as a Target 577Prerequisites 577




Limitations 579







Using Google Cloud SQL for PostgreSQL as a Target 585Prerequisites 585



Google Cloud SQL for PostgreSQL Database Target Data Types 586

Data Types when Replicating from a PostgreSQL Source 588






Using Google Cloud Storage as a Target 592Prerequisites 592

Google Cloud Storage Target Overview 592

DDL Handling 593

Limitations 593

Data Types 593






Using Google Dataproc as a Target 605Prerequisites 605

Limitations 606

Change Data Partitioning on Google Dataproc 606

Google Dataproc Endpoint Target Data Types 607





Using Hadoop as a Target 614Prerequisites 614

Prerequisites for using the Cloudera Distribution as a Hadoop Target 615

Prerequisites for using a Linux ODBC Driver 615


Limitations 616

Change Data Partitioning on Hadoop 617

Prerequisites 617


Hadoop Endpoint Target Data Types 617



Preventing ODBC Connection Timeouts 634



Using Kerberos Authentication 635

Using Kerberos Authentication on Linux 635

Using Kerberos Authentication on Windows 636

Using Hortonworks Data Platform (HDP) as a Target 640Prerequisites 640

Prerequisites for using a Linux ODBC Driver 641

Limitations 641


Prerequisites 642


HDP Endpoint Target Data Types 642





Using Kerberos Authentication 655

Using Kerberos Authentication on Linux 655


Using HP Vertica as a Target 660Prerequisites 660




Limitations 661


HP Vertica Target Data Types 662





Using IBM Netezza as a Target 666Prerequisites 666

Limitations 667


Database Privileges 667

Table Privileges 667

Schema Privileges 667

View Privileges 667

IBM Netezza Target Data Types 668





Using Kafka as a Target 672Transaction Processing by the Consumer 672

How it Works 673


Prerequisites 674

Limitations 674

Kafka Target Data Types 675















Data Message 693

Using a Log Stream Target 697

Using MapR Streams as a Target 698Transaction Processing by the Consumer 698

How it Works 699


Prerequisites 700

Limitations 701














Data Message 712

Using MemSQL as a Target 716Prerequisites 716




Limitations 717







Using Microsoft APS PDW as a Target 723Prerequisites 723

Limitations 723


Microsoft APS PDW Target Data Types 724





Using Microsoft Azure ADLS as a Target 728Prerequisites 728

Microsoft Azure ADLS Target Overview 729

DDL Handling 729

Limitations 729


Data Types 730






Using Microsoft Azure Database for MySQL as a Target 744Prerequisites 744





Limitations 746







Using Microsoft Azure Database for PostgreSQL as a Target 753Prerequisites 753


Microsoft Azure Database for PostgreSQL Target Data Types 755







Using Microsoft Azure Databricks as a Target 760Prerequisites 760

Limitations 761

Change Data Partitioning on Microsoft Azure Databricks 762






Using Microsoft Azure Event Hubs as a Target 768Prerequisites 768

Transaction Processing by the Consumer 769


How it Works 770


Limitations 771

Supported Target Data Types 771













Data Message 782

Using Microsoft Azure HDInsight as a Target 786Prerequisites 786

Limitations 787

Change Data Partitioning on Microsoft Azure HDInsight 788

Microsoft Azure HDInsight Endpoint Target Data Types 789





Using Microsoft Azure SQL Data Warehouse as a Target 797Overview 797

799

Limitations 799

Microsoft Azure SQL Data Warehouse Endpoint Prerequisites 799

Sign up for Microsoft Azure Blob Storage 799


Sign up for Microsoft Azure SQL Data Warehouse 800

Open the Required Firewall Port(s) 800

Install the Required Client 801

Microsoft Azure SQL Data Warehouse Data Types 801





Using Microsoft Azure SQL Database as a Target 807Prerequisites 807

Limitations 809

Permissions 810

Microsoft Azure SQL Database Target Data Types 810





Using Microsoft SQL Server as a Target 816Supported Editions 816

Prerequisites 817

Limitations 819

Permissions 819

Microsoft SQL Server Target Data Types 819





Using a MySQL-Based Database as a Target 827Prerequisites 827





Limitations 829







Using ODBC to Connect to a Target 835ODBC Target Data Types 835





Using Oracle as a Target 841Prerequisites 841

Limitations 842


Oracle Target Data Types 844





Using Pivotal Greenplum as a Target 851An Overview of the Pivotal Greenplum Target 851

Attunity Replicate Pivotal Greenplum Endpoint Architecture Overview 853

Full Load 853

CDC 853

Full Load 854

Applying Changes to the Pivotal Greenplum Target 854

Transactional Apply Mode 854

Batch-Optimized Apply Mode 855

Required Pivotal Greenplum Software, Environments 855


Windows Pivotal Greenplum Required Software 855

Linux Pivotal Greenplum Required Software 855

Required Pivotal Greenplum Configuration and Environment 856

Provide Pivotal Greenplum Account Access 856


Limitations 857

Pivotal Greenplum Data Types 857

Setting up the gpfdist Program as a Service 859

Using Multiple gpfdist Programs 861





Using a PostgreSQL-Based Database as a Target 865Prerequisites 865


PostgreSQL Database Target Data Types 867







Using SAP HANA as a Target 872Prerequisites 872

Permissions 872






Using SAP Sybase ASE as a Target 876


Prerequisites 876

Limitations 877


SAP Sybase ASE Database Target Data Types 877






Using SAP Sybase IQ as a Target 882Prerequisites 882

Limitations 882


SAP Sybase IQ Target Data Types 883





Using Snowflake on AWS as a Target 887Prerequisites 888

Amazon Web Services Account Prerequisites 888

Amazon S3 Staging Prerequisites 888



Firewall Prerequisites 889

Snowflake on AWS Data Types 889





Using Snowflake on Azure as a Target 896Prerequisites 896


Microsoft Azure Blob Storage Account 897


Permissions 897

Firewall Prerequisites 897

Snowflake on Azure Data Types 897





Using Teradata Database as a Target 903An Overview of the Teradata Database Target 903

Teradata Database Target Load Options 904

TPT Stream Mode 904

TPT Load Mode 904

Database Availability 904

Required Teradata Database Software, Environments 904



Providing Access to the Teradata Database 906

Editing the Hosts File 907


Teradata Database Data Types 908





10 | Using the Attunity Replicate File Channel 915Setting Up Attunity Replicate File Channel Tasks 915Local Task 915

Remote Task 916

Replicating to Multiple Targets (Distribution) 916

Adding Tables to a Running Remote Task 917


Working with the File Channel Data Files 918File-Channel Directory Structure 918

Attunity Replicate Installation Requirements for the File Channel 920

Security 920

Limitations 921

Using the File Channel as a Source 921Setting General Connection Properties 921

Using Advanced Properties for a File-Channel Source 923



Using the File Channel as a Target 924Setting General Connection Properties 924




11 | Using the Log Stream 928Terminology 928

Overview 928The Flow 930

Step 1: Create a Log Stream Target Endpoint 930

Step 2: Create and Run a Log Stream Staging Task 932Log Stream Staging Limitations and Considerations 934

Step 3: Create a Replication Task to Transfer the Staged Data to theTarget 935Duplicate the Source Endpoint and Add it to the Log Stream Staging Task 936

Create the Replication Task using the Duplicated Source Endpoint 937

Replication Task Limitations and Considerations 939

12 | Customizing Tasks 940Table Settings 940Performing General Tasks for a Single Table/View 941


Defining Transformations for a Single Table/View 943

Limitations 943

Using the Transform Tab 945

Creating an Expression for Transformations 951

Using SQLite Syntax with Transformations 952

Using Filters 953

Filter Limitations 953

Opening the Filter Tab 954

Creating a Filter Condition for a Specified Column 955

Creating a Record Selection Condition for One or More Columns 956

Adding or Removing Filter Ranges 958

Using SQLite Syntax with Filtering 960

Parallel Load 961


Setting Up Parallel Load 962

Usage Example 963

Adjusting the Number of Segments that can be Loaded in Parallel 965

Handling LOB Columns 966

Message Format 970

Defining Global Transformations 971Limitations for Global Transformations 972

Starting the New Transformation Rule Wizard 972

Selecting the Transformation Type 972

Under what Conditions to Transform 975

Defining the Transformation Rule 978

Limitations for Transformation Rules 979

Rename Schema 979

Rename schema to (string) 979

Add a Prefix or Suffix 980

Remove a Prefix or Suffix 980

Replace a Prefix or Suffix with Different Characters 981

Convert Schema Name to Uppercase 982

Convert Schema Name to Lowercase 982


Rename Schema (Expression) 983

Change Table Tablespace 984

Change Index Tablespace 984

Rename Table 984

Rename table to (string) 984




Convert table name to uppercase 986

Convert table name to lowercase 987

Rename table (expression) 987

Rename Column 988

Rename column to (string) 988




Convert column name to uppercase 990

Convert column name to lowercase 990

Rename Column (expression) 990

Add Column 991

Drop Column 992

Convert Data Type 992

Rename Change Table 992

Rename Change Table to (string) 993




Convert Change Table Name to Uppercase 995

Convert Change Table Name to Lowercase 995

Rename Change Table (expression) 995

Rename Change Table Schema 996

Rename Change Table Schema to (string) 996





Convert Change Table Schema Name to Uppercase 998

Convert Change Table Schema Name to Lowercase 999

Rename Change Table schema (expression) 999

Viewing all Global Transformation Rules 1000

Edit a Global Transformation Rule 1000

Delete a Global transformation Rule 1000

Using the Expression Builder (for Filters, Transformations, and GlobalTransformations) 1001Overview of the Expression Builder 1001

Build an Expression 1003

Operator toolbar 1004

Parse an Expression 1004

Test an Expression 1005

Using Elements in the Expression Builder 1007

Columns (Transformations and Filters only) 1007

Metadata (Global Transformations Only) 1007

Headers 1008

Variables 1009

Operators 1009

Functions 1015

Data Enrichment Functions 1020

Data Enrichment Example 1023

User-Defined Transformations 1027

Task Settings 1030Metadata 1031

Target Metadata 1031

Control Tables 1035

Bidirectional 1037

Full Load 1037

Full Load Settings 1037

Full Load Tuning 1040



Apply Changes Settings 1041

Store Changes Settings 1042

Change Processing Tuning 1047

Error Handling 1051

Error Handling Settings 1052

Environmental Errors 1052

Data Errors 1053

Table Errors 1054

Apply Conflicts 1055

Logging 1057

Storing Trace and Verbose Logging in Memory 1057

Character Substitution 1058

File Uploads 1060

Message Format 1062

General Rules and Usage Guidelines 1062

Defining a Custom Message Format 1064

13 | Working with Tasks at Runtime 1067Running a Task 1067How to Run a Task 1067

Using the Run Button Options 1068

Start Processing 1069

Reload Target 1069

Using Advanced Run Options 1070

Recovering from Data Folder Loss or Corruption 1074

Setting Up and Initiating Task Recovery 1074

Viewing the Task Status 1075

Reading Messages about a Task 1076Viewing Notifications 1077

Using the Notifications List 1077

View Log Messages for a Task 1078

Using the Log Messages List 1078


Viewing the Log file in the Log Viewer 1079

14 | Monitoring and Controlling Replication Tasks 1080Viewing Information in the Monitor 1080

Monitoring Full-Load Operations 1080General Information for a Full Load 1081

Detailed Information for the Full Load 1082

General Information for a Completed Task 1082

Information for Each Table in the Task 1083

Information for Tables that have Completed Loading 1084

Information for Tables that are Currently Loading 1085

Information for Tables that are in the Loading Queue 1087

Information for Tables with Errors 1087

Monitoring Throughput in a Full Load Operation 1088

Monitoring Change Processing Operations 1089General Change Processing Information 1089

Detailed Change Processing Information 1091

Information about Incoming Changes 1092

Information about Applied Changes 1093

Information about Change Processing Throughput 1095

Information about Apply Latency 1097

Viewing Messages 1099

Using the Monitor Tools 1099Viewing History Information 1100

Setting the Task Logging Level 1101


Viewing the Task Log Files and Manually Rolling them Over 1102

Viewing and Downloading the Task Log Files 1102

Manually Rolling Over Task Log Files 1103

Deleting Log Files 1104

Downloading a Memory Report 1104

Downloading a Diagnostics Package 1105


15 | Attunity Replicate Server Settings 1106Notifications Settings 1106Defining Notifications 1107

Creating a New Notification 1108

Define the Recipients 1122

Define the Notification Message 1123

The Notifications List 1127

Editing a Notification 1128

Deleting a Notification 1129

Setting up Mail Parameters 1129

Creating a Default Recipient List 1130

Replicate Event IDs in Windows Event Log 1130

License Settings 1131Requesting a License 1132

Using the Advanced License Request Option 1134

Registering a License 1135

Viewing a License 1137

Global Error Handling 1138

Logging 1138Setting Logging Levels for the Server and File Transfer Service 1139


Setting Automatic Roll Over and Cleanup 1140

Automatic Rollover 1140

Automatic Cleanup 1141

Viewing and Downloading Log Files 1142

Manually Rolling Over the Log Files 1142

Deleting Server, Task and FTS Log Files 1142

File Transfer Service 1143How it Works 1143

Compression 1144

Encryption 1144

Defining a File Transfer Service 1144


Editing a File Transfer Service 1145

Deleting a File Transfer Service 1145

Scheduling Jobs 1146

User Permissions 1148Managing User Permissions 1150

Resource Control 1151Disk Space 1152

System Memory 1152

A | Using Change Tables 1154Working with Change Tables 1154

Reading the Change Tables 1156Change Tables 1156

Use Example 1160

B | Using an Audit Table 1162

C | Creating Dump Files 1166

D | Pivotal Greenplum Prerequisites for Attunity Replicate 1167Required Pivotal Greenplum Software Environments 1167Windows Pivotal Greenplum Required Software 1167

Linux Pivotal Greenplum Required Software 1167

Required Pivotal Greenplum Configuration and Environment 1168Collect Connection Information 1168

Create a Test Input File 1169

Create an SQL Script File 1169

Start gpfdist 1169

Run the SQL Script 1170

Troubleshooting gpfdist Issues 1171Did gpfdist start on the correct port or protocol? 1171

Can Pivotal Greenplum reach gpfdist? 1171


E | Setting up Attunity Replicate in a Cluster Environment 1173Setting up Attunity Replicate in a Windows Server Cluster (HA) 1173Step 1: Install Attunity Replicate in the Cluster 1173

Step 2: Add the Attunity Replicate Services 1175

Step 3: Define the Dependencies for Each Service 1175

Step 4: Enable Different Console Configurations in a High Availability Environment1176

Setting up Attunity Replicate in a Linux Cluster 1177

F | Control Tables 1178Apply Exceptions 1178

Replication Status 1179

Suspended Tables 1181

Replication History 1181

Change Data Partitions 1182

DDL History 1183

G | Using HP NonStop SQL/MP as an ODBC Target 1187Prerequisites 1187

Table Settings 1189

Task Setting Limitations 1190

H | Impact of DST Change on Attunity Replicate 1191

I | Metadata File Description 1194

J | Supported Platforms and Endpoints 1198Supported Platforms 1198

Supported Windows Platforms 1198

Supported Linux Platforms 1198

Supported Source Endpoints 1200

Supported Target Endpoints 1205

Endpoints Supported in Bidirectional Replication 1209


Supported Browsers 1209

K | Best Practices when Working with Oracle ASM 1211The "Copy redo logs to temporary folder" Method 1211

Oracle Permissions Required for the Attunity Log Reader and the"Copy redo logs to temporary folder" Options 1212

Permissions for Deleting the Processed Redo logs from the Tem-porary Folder 1213

Oracle ASM Access Permissions 1213

Setting up the File Share if the "Direct Access" option was chosen 1214

Configuring the "Copy to Temp Folder" Option in Replicate 1214

Additional Considerations 1215Security and Folder Location 1215

Multiple Tasks Using the Same Temporary Folder 1215

Temporary Folder Disk Usage 1216

L | Replicate Loggers 1217ADDONS 1218

ASSERTION 1218

COMMON 1218

COMMUNICATION 1218

DATA_RECORD 1218

Example 16 - Example 1218

DATA_STRUCTURE 1220

FILE_FACTORY 1220

FILE_TRANSFER (AKA CIFTA) 1220

INFRASTRUCTURE 1220

IO 1220

Example 17 - Example: 1220

METADATA_CHANGES 1220

METADATA_MANAGER 1221

PERFORMANCE 1221

REST_SERVER 1221


SERVER 1221

SORTER 1221

SORTER_STORAGE 1221

SOURCE_CAPTURE 1222

SOURCE_LOG_DUMP 1222

SOURCE_UNLOAD 1222

STREAM 1222

STREAM_COMPONENT 1223

Example 18 - Example 1223

TABLES_MANAGER 1223

TARGET_APPLY 1223

TARGET_LOAD 1223

TASK_MANAGER 1223

TRANSFORMATION 1224

Example 19 - Example: 1224

UTILITIES 1224

M | Replicate Add-ons API 1225Memory Management Methods 1226create_pool 1226

destroy_pool 1226

clear_pool 1227

calloc 1227

get_ctx_pool 1228

get_ctx 1228

set_ctx 1229

Log Management Methods 1230log_error 1230

log_warning 1230

log_trace 1231


Glossary 1232

Index 1233


1 | IntroductionThis section describes the main concepts of data replication and the major components ofAttunity Replicate.

Note The term "endpoint" is used generically throughout this guide to refer to a datarepository that can be used as a source and/or target in an Attunity Replicate task.Examples of such repositories include relational databases (such as Oracle) and files.

In this chapter:

▶ Replication Explained

▶ Attunity Replicate

▶ Limitations and Considerations

▶ System Architecture

▶ Replication Tasks

▶ Full Load and CDC Processes

▶ Replication Topologies

Replication ExplainedReplication is a process that keeps two or more collections of computerized informationidentically synchronized. It facilitates:

Load reduction: Keeping a complete or partial copy of a collection on a differentserver reduces the load on the main server.

Improved service: Accessing a copy of the data can provide better service to usersthan having them access the original data..

Restricted data access: If some users should only have access to a subset of data,replicating only part of a collection makes it easy to enforce security restrictions.

Geographic distribution: Making only a subset of data relevant to a specific node(or location) available is beneficial in widely distributed enterprises (such as a chain ofretail stores or warehouses). You can still make all data available at a central locationfor less frequent use.

Attunity Replicate 6.4 Setup and User Guide

Chapter 1 | Introduction | Page 47Qlik Analytics (ISR) Ltd.

Disaster Recovery: Keeping a copy of the main data available allows for setting uprapid fail-over clusters (the capability to switch over to a redundant or standbycomputer server in case the main system fails).

"Cloud" computing: Replicating data allows for implementing what is commonlyknown as cloud computing (the on-demand storage, management, and processing ofInternet-based data).

The information replicated is stored as files or in a database. In the case of files, thestructure and content of a file are known only to the specialized programs that use the file.Databases are managed by database management systems (DBMS) that make use ofstandardized descriptions of the structure of the information (such as tables, columns,rows, and data types). These descriptions are known collectively as metadata and allow ageneral-purpose replicator to carry out relevant operations (for example filtering and datatransformations) without the need to know anything about the contents or “meaning” of thedata. Because file systems do not contain metadata, operations available for replicationare more limited.

During replication, a collection of data is copied from system A to system B, where A isknown as the source (for this collection) and B is known as the target. A system can be asource, a target, or both (with certain restrictions). A complex replication topology has anumber of sources, targets, and data collections defined.

The replication process must account for the fact that source data may be changing whilebeing copied. It is not possible to make or maintain copies instantaneously and to stop thesource computer to “freeze” the information. Therefore, replication must account for:

Integrity: The target data must reflect the complete result of all changes made to thesource data during the replication process.

Consistency: If a change affects different tables, rows, or files, the copy must reflectthese changes consistently across all affected tables, rows, or files.

Latency: The replication process must aim at keeping latency at a minimum. Ideally,it should not exceed a few seconds.

Attunity ReplicateAttunity Replicate is a simple, powerful, easy-to-implement solution that providesreplication between various endpoints. Replicate lets you:

Load data efficiently and quickly to operational data stores/warehouses.

Create copies of production endpoints.

Distribute data across endpoints.



Replicate has high throughput, speed, and scale. It is designed to scale and support largescale enterprise data replication scenarios with a multi-server, multi-task, and multi-threaded architecture.

Replicate consists of a Web-based console and a replication server to replicate data acrossheterogeneous data sources. It provides users with instant visibility into current andhistorical exceptions, status, performance, and resource usage information.

Replicate can execute replication tasks between enterprise endpoints including Oracle,Microsoft SQL Server, and IBM DB2. It uses a "Click-2-Replicate" design that simplifies thereplication process by automating the steps required to build a replication solution.

When you run a task in Replicate, you can select between:

Full Load Replication: Creates files or tables at the target endpoint, automaticallydefines the metadata that is required at the target, and populates the tables with datafrom the source

Change Processing, also called Change Data Capture (CDC): Captures changes in thesource data or metadata as they occur and applies them to the target endpoint as soonas possible in near-real time

Replication is log based, which means that it reads only the changes. This reduces theimpact on the source endpoints.

Limitations and ConsiderationsWhen working with Attunity Replicate, the following limitations apply:

Replicate does not support replication of Primary Keys that are LOB data types.

When replicating a table which has no Primary Key on the source endpoint, LOBcolumns are removed from the table at the target endpoint as no Unique Index columnis created in the source table.

When the Limit LOB size to option is enabled, replication of structured data LOBs (e.g.XML, JSON, IMAGE, etc.) may truncate (and thereby invalidate) the structured data inthe target LOB.

In Batch Optimized Apply mode, if the target table has more columns than the sourcetable, any values in the extra columns will be replaced with NULL.

The workaround is to create two tasks. One task for the target table(s) with extracolumns and the other task for the source table(s) which have the same number ofcolumns as the target tables. Then, run the task for the target table(s) with extracolumns in Transactional Apply mode and run the other task (where the target tables



do not have extra columns) in Batch Optimized Apply mode. Note, however, thatupdating large tables in Transactional Apply mode may impact performance.

When Replicate creates a new table in the target endpoint, it defines only one index onthe table. The index will either be the Primary Key or the first Unique Key (accordingto alphabetical order) of the table. No other indexes will be defined in the target. Ifadditional indexes are required, these will need to be defined manually.

If a Unique Index/Primary Key in any of the source tables contains NULL values inmultiple rows, UPDATE and DELETE operations on one of the rows will UPDATE/DELETE all of the target rows (in the Unique Index/Primary Key) that have a NULLvalue.

LOB columns are always created as nullable on the target database. If you create thetarget table(s) manually, then you must set all LOB columns to nullable.

If you stop a task after Full Load completes, perform some changes on the sourcetables, and later resume the task from timestamp (by selecting the Start processingchanges from run option), some changes may not be replicated to the target. Thisusually only happens if the transaction logs in the source database have been deleteddue to a log purge policy. In this case, Replicate will resume the task from the lastchange in the current transaction log.

When replicating tables without a Primary Key, there is no way to verify whether arecord already exists on the target. This may result in data inconsistency whenUPDATE and DELETE operations are performed on the target database.

Replication of calculated values is not supported during Change Processing.

If a task fails with a recoverable error on the target while it is starting, it will not readchanges from the source.

Cached changes may be duplicated in a target table that does not have a UniqueIndex.

A unique index consisting of several ascending and descending columns will always bereplicated to the target as ascending columns. In other words, the descending columnswill become ascending columns.

When the source table contains an identity column, Replicate does not create theidentity column on the target table. In this case, the table will need to be createdmanually on the target endpoint.

Replication of tables with the same name as any of the Replicate Control tables is notsupported. For a list of the Control Table names, see Control Tables.



CREATE TABLE operations performed on the source while a task is stopped will beapplied to the target when the task is resumed, but will not be recorded as a DDL inthe attrep_ddl_history Control Table.

System ArchitectureThe following diagram shows the basic architecture of Attunity Replicate.

Figure 1.1 | Attunity Replicate System Architecture

In this diagram, the source data and metadata are part of the source server. Thetransaction log reader can be on the source server (for efficiency) or on the AttunityReplicate server (for zero footprint on the source). Filtering and compression of the sourcerows/logs can occur on the source or Attunity Replicate servers.

In the initial load process, Attunity Replicate reads a filtered stream of rows (with relevantcolumns only) and passes them to the transformation process for further filtering andsubsequent writing to the target endpoint (in the expected output format).

The CDC process obtains a stream of filtered events or changes in data or metadata fromthe transaction log file. It then buffers all changes for a given transaction into a single unitbefore forwarding them to the target when the transaction commits. During the initial loadprocess, CDC also buffers all changes that occur within a transaction until all affectedtables have been loaded.



The Designer/Console server, which is part of the Replication server, is a Web-basedapplication that serves as the user interface for dealing with designing or modifying thereplication system and displaying and controlling its operation.

Replication TasksEach instance of a table synchronization activity comprises a task in Attunity Replicate. Youdefine a task using the browser-based Attunity Replicate Console. When defining a task,you specify:

The source and target endpoints

The source and target tables to be kept in sync

The relevant source table columns

The filtering conditions (if any) for each source table as Boolean predicates (in SQLitesyntax) on the values of one or more source columns

The target table columns (optionally), including their data types and values (asexpressions or functions over the values of one or more source or target columns,using SQL syntax). If not specified, Replicate uses the same column names and valuesas the source tables, with default mapping of the source DBMS data types onto thetarget DBMS data types. Replicate automatically takes care of the required filtering,transformations, and computations during the Load or CDC execution.

When a task is defined, you can activate it immediately. Replicate automatically createsand loads the target tables with the necessary metadata definitions and activates the CDC.Using the Attunity Replicate Console, you can then monitor, stop, or restart the replicationprocess.

Using Multiple TasksYou can define and activate several replication tasks at once. This is best if the tasks:

Have different source tables

Share some source tables but have different filtering conditions on the source rows

Update different target tables

Updating the same target table and row by two different replication tasks would not begood practice and may cause unpredictable results.

The different replication tasks work independently and run concurrently. Each has its ownInitial Load, CDC, and Log Reader processes.



Full Load and CDC ProcessesThe full load process creates files or tables at the target endpoint, automatically definesthe metadata that is required at the target, and populates the tables with data from thesource. Unlike the CDC process, the full load process loads the data one entire table or fileat a time, for maximum efficiency.

The source tables may be subject to update activity during the Load process. However,there is no need to stop processing in the source. Replicate automatically starts the CDCprocess as soon as the load process starts. It does not apply the changes to the target untilafter the load of a table completes because the data on the target might not be consistentwhile the load process is active. At the conclusion of the load process, however, Replicateguarantees consistency and integrity of the target data.

If the load process is interrupted, it continues from wherever it stopped when restarted.

You can add new tables to an existing target without reloading the existing tables.Similarly, you can add or drop columns in previously populated target tables withoutreloading.

The CDC process captures changes in the source data or metadata as they occur andapplies them to the target endpoint as soon as possible in near real time. It captures andapplies the changes as units of single committed transactions and can update severaldifferent target tables as the result of a single source commit. This guaranteestransactional integrity in the target endpoint. The CDC process for any file or table starts assoon as the data load process for the file or table begins.

CDC operates by reading the recovery log file of the source endpoint management systemand grouping together the entries for each transaction. The process employs techniquesthat ensure efficiency without seriously impacting the latency of the target data. If the CDCprocess cannot apply the changes to the target within a reasonable amount of time (forexample when the target is not accessible), it buffers the changes on the Replication serverfor as long as necessary. There is no need to re-read the source DBMS logs, which maytake a long time.

Replication TopologiesAttunity Replicate supports the following topologies for replication tasks:

One to One

Logical Independence

Hub and Spoke



One to OneIn a one-one topology, there is one source and one target endpoint. When the source andtarget endpoints are distinct, Attunity Replicate guarantees transactional integrity andconsistency. If you use two different replication tasks, the endpoints may switch roles,allowing two-way synchronization.

Caution: If the same row in a table is updated by two different replication tasks, theresult of two-way synchronization may be unpredictable. A problem can occur even iftwo different rows are referentially related, that is if some application updates a rowbased on reading a value in a different row. If the rows are updated concurrently on thesource and the target, the result may be unpredictable1 . Such occurrences are rare,but they can occur.

Logical IndependenceTwo-way replication works best when updates of a row on a source and on a target areentirely autonomous and do not affect each other. There is an assumption that any table ora horizontal or vertical segment of a partitioned table can only be updated in one source.Attunity Replicate allows updating the same row in several places, but in this case, thecolumns being updated must be distinct. Another assumption is that if a data value in onerow depends on or is derived from a value in another row, the values can be changed onlyon the same server but nowhere else (except by the Replicator). This is called logicalindependence. With logical independence, concurrent update conflicts cannot occur duringreplication.

Hub and SpokeMany-to-one and one-to-many relationships can be combined into a hub-and-spoketopology, which allows the merging of data into multiple targets and then distributing toother targets. It does not allow cycles or multiple paths for propagating changes. The hub-and-spoke topology is that of an acyclic directed graph.

1CDC has no way of knowing exactly when a row was read by an application on one system relative to its havingbeen changed on another system. Read operations are typically not logged.



2 | Installing Attunity ReplicateThis section describes how to prepare your system for Attunity Replicate, how to installAttunity Replicate, and how to access the Attunity Replicate Console.

Important: To work, Attunity Replicate needs to be set up with the proper securityconfiguration. It is therefore strongly recommended to review Security Considerationsbefore using the product for the first time.

In this chapter:

▶ Installation Prerequisites

▶ Installing or Upgrading Attunity Replicate on Windows

▶ Installing Attunity Replicate on Linux

Installation PrerequisitesThis section describes how to prepare your system to use Attunity Replicate. Therequirements differ according to the platform on which you want to install AttunityReplicate and according to the desired Attunity Replicate UI Server configuration. For moreinformation on the available UI Server configurations, see Attunity Replicate UI ServerConfigurations.

Software Requirements

Supported Endpoints

Software RequirementsThis section describes what software is required to work with Attunity Replicate.

Windows Software Requirements

Linux Software Requirements


Chapter 2 | Installing Attunity Replicate | Page 55Qlik Analytics (ISR) Ltd.

Windows Software RequirementsTo install the Attunity Replicate Server and Console on a Windows computer, you musthave the following installed on your system:

.NET Framework 4.5.2 or above

Visual C++ Redistributable for Visual Studio 2015. If it is not installed or if an olderversion is installed, it will be installed automatically during installation.

TLS v1.2 needs to be fully installed and configured prior to installing Replicate on aWindows 2016 Server.

For a list of supported browsers, see Supported Browsers.

For a list of supported operating systems, see Supported Platforms.

Linux Software RequirementsFor a list of supported Linux operating systems, see Supported Linux Platforms.

Windows PermissionsAttunity Replicate needs to be installed as an Administrator.

The following privileges are required to start the Attunity Replicate UI Server service(which is run as a local system service), but are dropped as soon as the service is started:

SE_CREATE_GLOBAL_NAME

SE_CREATE_PAGEFILE_NAME

SE_CREATE_PERMANENT_NAME

SE_CREATE_SYMBOLIC_LINK_NAME

SE_CREATE_TOKEN_NAME

SE_DEBUG_NAME

SE_ENABLE_DELEGATION_NAME

SE_IMPERSONATE_NAME

SE_INC_BASE_PRIORITY_NAME

SE_INCREASE_QUOTA_NAME

SE_INC_WORKING_SET_NAME

SE_LOAD_DRIVER_NAME

SE_LOCK_MEMORY_NAME

SE_MACHINE_ACCOUNT_NAME

SE_MANAGE_VOLUME_NAME

SE_PROF_SINGLE_PROCESS_NAME



SE_RELABEL_NAME

SE_REMOTE_SHUTDOWN_NAME

SE_RESTORE_NAME

SE_SECURITY_NAME

SE_SHUTDOWN_NAME

SE_SYNC_AGENT_NAME

SE_SYSTEM_ENVIRONMENT_NAME

SE_SYSTEM_PROFILE_NAME

SE_SYSTEMTIME_NAME

SE_TAKE_OWNERSHIP_NAME

SE_TCB_NAME

SE_TIME_ZONE_NAME

SE_TRUSTED_CREDMAN_ACCESS_NAME

SE_UNDOCK_NAME

In addition, the account that runs Replicate needs to be granted access to the Datadirectory (~\Attunity\Replicate\Data) as well as any directory containing files (such as CSVfiles) that need to be used in a replication task.

Recommended Hardware ConfigurationThis section describes the recommended hardware configurations for using AttunityReplicate. For information on the software requirements for using Attunity Replicate, seeSoftware Requirements.

The following table describes the recommended hardware configuration for installingAttunity Replicate on Windows and Linux operating systems. Note that therecommendations apply to mid-scale systems (i.e. hundreds of tasks) rather than large-scale systems (i.e. thousands of tasks).



BasicSystem

LargeSystem

Extra-LargeSystem

Notes:

Processor Quadcore

Quadcorebase

Dual-core pertask

8-corebase

Quadcore pertask

Additional cores are useful in any of thefollowing situations:

Many tasks running in parallel

Full-load performance priority

Multiple full-load processes running inparallel

Memory 8 GB 32 GB 64 GB More memory is useful in any of thefollowing situations:

Many tasks running in parallel

Long-running transactions on thesource endpoint (for example,monthly batch processing)

Many active users on the sourcesystem

Table 2.1 | Recommended Hardware Configuration



BasicSystem

LargeSystem

Extra-LargeSystem

Notes:

Diskrequirements

320 GB

7200RPM

500 GB

10,000RPM

RAID

500 GB

15,000RPM

RAID

A faster disk is useful in any of thefollowing situations:

Using a file-based target, such asGreenplum or Actian Vector

Long-running source transactions thatmay not fit into memory

Using tasks that are set up to continueprocessing during target outage

A larger disk is required in any of thefollowing situations:

Using tasks that are set up to continueprocessing during target outage

Very large source transactions that donot fit into memory

RAID is recommended for systemrecoverability in case of disk failure for allconfigurations.

Network 1 Gb 10 Gb Two 10Gb

Table 2.1 | Recommended Hardware Configuration (Cont.)

Supported EndpointsTo replicate data using Attunity Replicate, you must be sure to have a supported version ofthe endpoint you are working with available. For information about the endpoints you canuse with Attunity Replicate, see Supported Platforms and Endpoints.

Installing or Upgrading Attunity Replicate on WindowsThe following topic describes how to install and upgrade Replicate on Windows using thesetup wizard.



Installation InstructionsInstall Attunity Replicate using the AttunityReplicate__X64.exeinstallation kit. This kit runs on Windows 64-bit (x64) environments. For a list of theWindows versions supported by Attunity Replicate, see Windows Software Requirements.

Follow the instructions in the Setup wizard to install Attunity Replicate.

Later, if you need to start or stop the Attunity Replicate Server, see the following section:Starting and Stopping the Attunity Replicate Server on Windows

Note In the setup wizard’s Replication Server Location screen, one of the optionsis Connect to a remote Linux Attunity Replicate Server. You should only selectthis option if you have already installed Attunity Replicate Server on a Linux machine. Ifyou select this option, you will be prompted for the IP address and port number of theLinux machine in the following screen.

For more information on installing Attunity Replicate Server on Linux, see Installing

Attunity Replicate on Linux.

For information on the possible deployment configurations, see Attunity Replicate UI

Server Configurations.

All of the data that is created when you use Attunity Replicate is stored in a directory calleddata. By default, this directory is located in the installation directory where you installAttunity Replicate. If you want to create the data directory in a different location, selectthis option in the installation wizard.

If you elect to create the data directory in a different location, all command line actionsmust include the -d your_data_directory_path parameter where your_data_directory_path is the location of the "data" directory.

Upgrade Instructions

1. Choose one of the backup methods below.

Method 1:

Stop all Replicate tasks and services.

Back up the Replicate "data" directory to a location outside the product folder. Thismethod is recommended in most cases. However, if your "data" folder is very largeand there is not enough space to back it up, then use Method 2 below.



Method 2:

Open a Windows command prompt and change the path to \bin. Thenissue the following command:

repctl [-d alternate_data_directory_path] exportrepository

where [-d alternate_data_directory_path] is required when the Replicate "data"directory is in a non-default location.

2. Run the Attunity Replicate setup wizard (AttunityReplicate__X64.exe).

3. If you notice an issue with the upgrade, you can either revert to the previous versionas described below or do one of the following depending on which backup method youchose above.

If you chose Method 1:

a. Stop all Replicate services.

b. Overwrite the "data" directory with the "data" directory that you backed upearlier.

c. Start all Replicate services.

If you chose Method 2:

Issue the following command:

repctl [-d data-directory] importrepository json_file=Full path to the

exported *.json file

where [-d data-directory] is only required if you installed the Replicate "data"directory to a non-default location.

Example:

repctl -d f:/data importrepository json_file=C:\Temp\many_tables.json

To revert to a previous version:

1. Back up the Replicate "data" directory to a location outside the product folder.

2. Uninstall the product and then reinstall to the same directory.

3. Once the installation is complete, stop all Replicate services.

4. Overwrite the "data" directory with the "data" directory that you backed up earlier.

5. Start all Replicate services.



Starting and Stopping the Attunity Replicate Server onWindowsIn some cases you may need to stop and start the Attunity Replicate Server. You must dothis from the Windows computer where Attunity Replicate is installed.

To stop and start the Attunity Replicate Server on Windows

From the Start menu on the Windows computer where Attunity Replicate is installed,find Attunity Replicate; then select either Stop Attunity Replicate Server orStart Attunity Replicate Server.

Silently Installing Attunity ReplicateAttunity Replicate can be installed silently (i.e. without requiring user interaction). Thisoption is useful, for example, if you need to install Attunity Replicate on several machinesthroughout your organization.

Note Before commencing the installation, make sure that the prerequisites have beenmet.

The installation process consists of two stages:

1. Creating a Response File

2. Running the Silent Install

Creating a Response FileBefore starting the installation, you need to create a response file.

To create the response file

1. From the directory containing the Attunity Replicate setup file, run the followingcommand (note that this will also install Attunity Replicate):

AttunityReplicate__X64.exe /r /f1

where:

is the full path to the generated response file.

Example:

AttunityReplicate__X64.exe /r /f1C:\Replicate_

install.iss

Chapter 2 | Installing Attunit

attunity replicate user and reference guide...editingendpointconfigurationinformation 136...

Documents