+ All Categories
Home > Documents > DB2 LUW WHY HVR?

DB2 LUW WHY HVR?

Date post: 29-Nov-2021
Category:
Upload: others
View: 17 times
Download: 0 times
Share this document with a friend
2
hvr-software.com | [email protected] | 135 Main Street, Suite 850, San Francisco, CA 94105 © Copyright 2020. All Rights Reserved. HVR Software. The DB2 LUW is a very commonly used database, often running very demanding and mission-critical workloads, including the SAP ERP suite. DB2 is a common data source for analytical environments and data lakes. This datasheet describes HVR’s support for the DB2 Database as a source for change data capture, and as a target for data delivery. Version Compatibility HVR supports DB2 LUW versions 9.7 through 11.1 as a source and target, with most major operating system supported. Connectivity to the DB2 LUW is established through the native drivers. HVR uses the db2readlog API to read the DB2 database recovery logs to capture CDC in real time. One-Time Load – Refresh – and Compare and Repair One-time load, in HVR’s terms, Refresh, as well as Compare and Repair, starts with a select from the DB2 LUW Database. HVR’s powerful Compare and Repair tool allows individual row compares between sources and targets even if the databases are heterogeneous. If the data is not in sync the Repair feature allows individual rows to be placed in sync. DB2 LUW To support CDC from busy, mission- critical workloads running on IBM’s LUW database you need an efficient, robust, and flexible solution. HVR is that solution. HVR provides CDC capabilities for your heterogeneous replication scenarios. In addition, HVR is equipped with: • Table Creation: Target table creation automatically maps data to compatible data types • Initial Load: One-time data load, integrated with CDC to simplify initial load scenarios, granular down to the table level • Data Validation: Compare your replicated data and fix data that is out-of-sync • Data Statistics: Visual representation of data flows so that you can manage and optimize data movement • Automatic monitoring: Set latency thresholds and get alerts if data movement is slowed • Graphical User Interface: Simple set up and design of your data flows WHY HVR? +
Transcript
Page 1: DB2 LUW WHY HVR?

hvr-software.com | [email protected] | 135 Main Street, Suite 850, San Francisco, CA 94105

© Copyright 2020. All Rights Reserved. HVR Software.

The DB2 LUW is a very commonly used database, often running very demanding and mission-critical workloads, including the SAP ERP suite. DB2 is a common data source for analytical environments and data lakes. This datasheet describes HVR’s support for the DB2 Database as a source for change data capture, and as a target for data delivery.

Version Compatibility HVR supports DB2 LUW versions 9.7 through 11.1 as a source and target, with most major operating system supported. Connectivity to the DB2 LUW is established through the native drivers. HVR uses the db2readlog API to read the DB2 database recovery logs to capture CDC in real time.

One-Time Load – Refresh – and Compare and RepairOne-time load, in HVR’s terms, Refresh, as well as Compare and Repair, starts with a select from the DB2 LUW Database. HVR’s powerful Compare and Repair tool allows individual row compares between sources and targets even if the databases are heterogeneous. If the data is not in sync the Repair feature allows individual rows to be placed in sync.

DB2 LUWTo support CDC from busy, mission-

critical workloads running on IBM’s

LUW database you need an efficient,

robust, and flexible solution. HVR

is that solution. HVR provides CDC

capabilities for your heterogeneous

replication scenarios. In addition, HVR

is equipped with:

• Table Creation: Target table

creation automatically maps

data to compatible data types

• Initial Load: One-time data load,

integrated with CDC to simplify

initial load scenarios, granular

down to the table level

• Data Validation: Compare your

replicated data and fix data that

is out-of-sync

• Data Statistics: Visual

representation of data flows

so that you can manage and

optimize data movement

• Automatic monitoring: Set

latency thresholds and get alerts

if data movement is slowed

• Graphical User Interface: Simple

set up and design of your data

flows

WHY HVR?

+

Page 2: DB2 LUW WHY HVR?

hvr-software.com | [email protected] | 135 Main Street, Suite 850, San Francisco, CA 94105

© Copyright 2020. All Rights Reserved. HVR Software.

CONTINUED. ONE-TIME LOAD – REFRESH – AND COMPARE AND REPAIR Parallelism can be specified across tables or using slicing for parallelism within a table, and data is pulled out through a native DB2 connection. For optimum performance and efficiency, HVR recommends an architecture using an agent close to if not on the database server(s) to densely compress/decompress the data, and optionally encrypt/decrypt it. The native connection, combined with optimized network utilization, supports efficient and fast data retrieval.

Log-Based CDC from DB2 DB2 database recovery logs record database changes to ensure that a failure does not leave the database in an inconsistent state and serve as a history of all transactions performed on the database. The database recovery log is also the source for data replication products like HVR to know what operations were submitted to the database. HVR uses DB2’s native db2ReadLog API to gather transactions from the transaction logs to support CDC logical replication. The DB2 source database must be running in full recovery mode to support replication. HVR reads the online logs by default, there may be occasions where HVR may have to read archive logs. If that is the case, then archiving should be enabled on the source database. HVR requires some form of unique row identifier on the source and target tables to locate the correct target rows for replicated updates and deletes. Supplemental logging is required in order to obtain that unique row identifier.

Target DB2HVR uses IBM’s native connectivity protocol to connect to the database. Bulk data refreshes, including the initial data load, as well as loads into staging tables for burst integration, use IBM DB2’s bulk loading interface for optimum performance.

ABOUT HVR

We accelerate data movement so that you can revolutionize your business. HVR is designed to move large volumes of data FAST and efficiently in hybrid environments for real-time updates.


Recommended