• Click Yes in the prompt dialog asking to create catalog tables in HVR hub database.

On connecting successfully to the hub database, the navigation tree pane displays the hub machine and the hub database. Location Configuration, Channel Definitions, and Scheduler are displayed under the hub database.

CREATE LOCATION

Location is a storage place (for example, database or file storage) from where HVR captures (source location) or integrates (target location) changes.

Create one source location (src) connected to source schema (sourcedb) and one target location (tgt) connected to target schema (targetdb).

1. In navigation tree pane, right–click Location Configuration ->New Location
   

2. Enter Location name and Description for the location.
3. Select Oracle in Class.
4. Provide Database Connection details
   • • Enter directory path for ORACLE_HOME. You can also click browse to select directory path.
     • Enter Oracle System ID in ORACLE_SID or TNS credential or RAC credential
     • Enter user name of schema in User
     • Enter password for schema in Password
5. Click Test Connection to verify the connection to location database.
6. Click Ok

6. Target location for kafka will be defined in later chapter (Create kafka location).

CREATE CHANNEL

A CHANNEL is an object in HVR that groups together the locations that should be connected together and the tables that should be replicated.

1. In navigation tree pane, right–click Channel Definitions -> New Channel.

2. Enter Channel name and Description for the channel in New Channel dialog.
3. Click OK.
   

   CREATE LOCATION GROUPS

   The location groups are used for
   defining action on the location. Typically a channel contains two location groups – one for the source location and one for the target location. Each location group can contain multiple locations.In this example,
   create one source location group (SRCGRP) and one target location group
   (TGTGRP).

1. In navigation tree pane, click+next to the
   channel (test).
2. Create source location group (SRCGRP):
   • Right–click Location Groups -> New Group.
   • Enter Group Name and Description for the location group.

1. • Select source location (src1) from Group Membership.
   • Click OK.
3. Create target location group (TGTGRP):
   • Right–click Location Groups -> New Group.
   • Enter Group Name and Description for the location group.
   • Select target location (tgt1) from Group Membership

• Click OK.

SELECT TABLES

This section describes how to select the tables from source location for replication.Table Explore allows you to select schema(s) and/or table(s) for replication.

• Right–click Tables -> Table Explore

• Select source location (src1) from the list.

1. Click Connect.
   
2. Select tables from Table Explore dialog. Press Shift key to select multiple tables or Ctrl+Ato select all tables.
3. Click Add to add the selected tables.

4. Click OK in HVR Table Name dialog
5. Click Close in Table Explore dialog

Define Actions

This section describes how to define Actions on the location groups (SRCGRP and TGTGRP). Actions define the behavior of a replication activity.

1. Define action Capture to capture changes from all tables in the source location group.
   
   • Right–click source location group SRCGRP -> New Action -> Capture

• Click OK.

1. Define action Integrate.
   • Right–click target location group TGTGRP -> New Action -> Integrate.

• Click OK.

INITIALIZE

This section describes how to initialize the replication. HVR Initialize first checks the channel and creates replication jobs in the HVR Scheduler.

In this example, HVR Initialize creates one capture job and one integrate job.

1. Right–click channel test ->HVR Initialize.
2. Select Create or Replace Objects in HVR Initialize dialog and check all the boxes.
3. Click Initialize.

4. Click OK.
5. Click Close.

Click Scheduler node in navigation tree pane to view the capture and integrate jobs in Job stab.

START SCHEDULER AND CREATE WINDOWS SERVICE

This section describes how to start the HVR Scheduler and create Windows service.

1. Start Scheduler. In the navigation tree pane, right-click Scheduler -> Start.

2. Click Create… in the prompt asking to create the service hvrscheduler_hvrhub.
3. Select Local System Account (‘SYSTEM’) in Create Windows Service dialog.
4. Click Create…

START CAPTURE JOB

This section describes how to start the job for capturing changes from source location (src1). By starting the Capture job in HVR Scheduler, HVR begins capturing all changes since the moment HVR Initialize was executed. This ‘capture begin moment’ can be modified using the option Capture Rewind available in the Advanced Options tab of HVR Initialize dialog.

1. In the navigation tree pane, click Scheduler.
   
2. Start capture job. In the Jobs pane, right-click capture job test-cap-src1 -> Start.

3. Click Yes in Start dialog.

REFRESH

This section describes how to perform initial load into the target database. HVR Refresh copies all existing data from source location (src1) to the target location (tgt1) and optionally creates new tables and keys in target location.

1. In the navigation tree pane, right–click channel test -> HVR Refresh.

2. Click Refresh.
3. Click Yes to begin HVR Refresh. When the refresh is completed, the Refresh Result dialog displays the total number of rows replicated from the selected tables
4. Click Close in Refresh Result dialog
5. Click Close in HVR Refresh dialog

START INTEGRATE JOB

This section describes how to start the job to integrate changes into the target location (tgt).

1. In the navigation tree pane, click Scheduler.
2. Start integrate job. In the Jobs pane, right-click integrate job test-integ-tgt1 -> Start.

3. Click Yes in Start dialog.

VERIFY REPLICATION

This section describes the two methods for verifying HVR’s replication activity.

• Log file: HVR creates separate log file for the hub, channel (hvrdemo), and for each replication jobs (test-cap-src1 and test-integ-tgt1). This log file contains the details of the changes captured and integrated. To view the replication activity log:

1. In navigation tree pane, click + next to the Scheduler.

2. Click test-> View Log to view the output of the jobs.
3. Update the value(s) in source location database.
4. HVR Compare(can’t be done with kafka): Verify the replication activity by comparing the data in source and target locations.

PREREQUISITES AND USING HVR WITH KAFKA

This section describes the requirements, access privileges, and other features of HVR when using Kafka for replication.

Installation Dependencies

On Linux, to use the Kafka authentication Mechanism (User Name and Password or Kerberos), HVR requires the library libsasl2.so.2 to be installed. This library is part of Cyrus SASL and can be installed as follows:

yum install cyrus-sasl

If you have libsasl2.so.3.0.0 then make the symbolic link libsasl2.so.2 that points to libsasl2.so.3.0.0.

Grants

grant create session to targetdb;
grant create table to targetdb;

Create kafka location

To create a Kafka location, right–click on Location Configuration ->New Location.

• HVR creates a Kafka location that sends messages in JSON format by default.

• To create a Kafka location that sends messages in (micro) AVRO format, select Schema Registry (Avro) and provide the URL for Schema Registry

Now you need to try and use above instructions to replicate data from oracle database to kafka using HVR. If you follow steps carefully you won’t have many problems and you will see that HVR is a powerful tool for the job. Enjoy! 🙂

Please visit the first part of the blog series:

PART 1/2