Capabilities

From HVR
Jump to: navigation, search

This section describes the capabilities supported by HVR on each location class.

Capture

This section lists the capabilities related to Capture.

HVR Capability Support Status
Capture changes from location Only supported on:
  • MariaDB version 10.0 and above, since HVR 5.3.1/13
  • MySQL version 5.6 and above, since HVR 5.3.1/13
Log-based capture (capture from DBMS logging system) Only supported on:
  • MariaDB version 10.0 and above, since HVR 5.3.1/13
  • MySQL version 5.6 and above, since HVR 5.3.1/13
Log-based capture of DDL statements using action AdaptDDL Only supported on:
  • DB2 for i version 7.1 and above, since HVR 5.3.1/12
  • MariaDB version 10.0 and above, since HVR 5.3.1/21
  • MySQL version 5.6 and above, since HVR 5.3.1/21
Log-based capture of tables without a primary key Supported on all classes where Log-based capture is supported, except for:
Direct access to logs on a file system Supported on all classes where Log-based capture is supported, except for:
Access to logs using SQL interface Only supported on:
  • MariaDB version 10.0 and above, since HVR 5.3.1/13
  • MySQL version 5.6 and above, since HVR 5.3.1/13
  • Oracle version 9.2 and above, since HVR 5.3.1/12
Log-based capture with /LogReadMethod param Only supported on:
  • MariaDB version 10.0 and above, since HVR 5.3.1/13
  • MySQL version 5.6 and above, since HVR 5.3.1/13
  • Oracle version 9.2 and above, since HVR 5.3.1/12
Log-based capture of tables with LOB column Only supported on:
  • MariaDB version 10.0 and above, since HVR 5.3.1/13
  • MySQL version 5.6 and above, since HVR 5.3.1/13
Log-based capture from hidden rowid column (ColumnProperties /CaptureFromRowId) Only supported on:
Rewind log-based capture to specific time (hvrinit option -i) Only supported on:
  • MariaDB version 10.0 and above, since HVR 5.3.1/15
  • MySQL version 5.6 and above, since HVR 5.3.1/15
Rewind log-based capture to the beginning of currently active oldest transaction Only supported on:
Rewind log-based capture to the beginning of currently active oldest transaction for a specific list of tables Only supported on:
Online refresh using accurate LSN/SCN Only supported on:
  • DB2 for i version 7.1 and above, since HVR 5.3.1/12
  • MariaDB version 10.0 and above, since HVR 5.3.1/13
  • MySQL version 5.6 and above, since HVR 5.3.1/13
Online refresh skips capture log records early in scanner Only supported on:
Populates column hvr_cap_user for use in ColumnProperties {hvr_cap_user} substitutions Only supported on:
Log-based capture of truncate table statements Only supported on:
  • DB2 for i version 7.1 and above, support depends on system setting
  • MariaDB version 10.0 and above, since HVR 5.3.1/21
  • MySQL version 5.6 and above, since HVR 5.3.1/21
Multiple log-based capture jobs can capture from same database Only supported on:
  • MariaDB version 10.0 and above, since HVR 5.3.1/13
  • MySQL version 5.6 and above, since HVR 5.3.1/13
  • SQL Server 2005 and above, only FN mechanism, not SP
Capture from tables with basic compression Only supported on:
  • MariaDB version 10.0 and above, since HVR 5.3.1/13
  • MySQL version 5.6 and above, since HVR 5.3.1/13
  • Oracle version 11.2.0.4 and above
Capture from tables with advanced compression Only supported on:
  • Oracle version 11.2.0.4 and above
Capture from tables with BLOB compression Only supported on:
  • Oracle version 11.2.0.4 and above
Log-based capture checkpointing (action Capture /CheckpointingFrequency) Only supported on:
hvrlogrelease to preserve journal/archives Only supported on:
Read archives from an alternative directory (Capture /ArchiveLogPath) Only supported on:
Trigger-based capture (action Capture /TriggerBased) Only supported on:
Capture /QuickToggle Only supported on:
Boundaries between transactions preserved by trigger-based capture Only supported on:
Trigger-based capture jobs can be woken by db-event when change happens Only supported on:

HVR Hub

This section lists the capabilities related to HVR Hub.

HVR Capability Support Status
Hub database Only supported on:
  • MySQL version 5.6 and above

Integrate

This section lists the capabilities related to Integrate.

HVR Capability Support Status
Integrate changes into location Only supported on:
  • Kafka version 0.8 and above
  • MySQL version 5.6 and above
Integrate with /Burst Supported on all classes where Integrate changes into location is supported, except for:
Integrate with /BurstCommitFrequency Supported on all classes where Integrate changes into location is supported, except for:
Continuous integration (Integrate without /Burst) Supported on all classes where Integrate changes into location is supported, except for:
Action TableProperties with /DuplicateRows for continuous integration Supported on all classes where Integrate changes into location is supported, except for:
Continuous integrate with /OnErrorSaveFailed (without /Burst) Only supported on:
  • MySQL version 5.6 and above
Disable/enable database triggers during integrate (/NoTriggerFiring) Only supported on:
Action Transform /SoftDelete Supported on all classes where Integrate changes into location is supported
Bulk load requires a staging area (LocationProperties /StagingDirectoryHvr) Only supported on:
  • MySQL version 5.6 and above
Creation and update of HVR state tables Supported on all classes, except for:
Integrate with /DbProc Only supported on:

Bi-directional Replication

This section lists the capabilities related to Bi-directional Replication.

HVR Capability Support Status
Detection of changes made by HVR in a bidirectional channel to prevent loop-back Only supported on:
  • HANA, state table needs to be created before replication starts
  • MariaDB version 10.0 and above, since HVR 5.3.1/13
  • MySQL version 5.6 and above, since HVR 5.3.1/13
  • PostgreSQL version 8.0 and above, state table needs to be created before replication starts
Collision Detect with Log-based Capture (without /TimestampColumn) Only supported on:
Collision Detect with Trigger-based Capture (with Capture /TriggerBased and without Collision Detect /TimestampColumn) Supported on all classes where Trigger-based capture is supported, except for:
Collision Detect with /TimestampColumn Only supported on:
  • MariaDB version 10.0 and above, since HVR 5.3.1/13
  • MySQL version 5.6 and above, since HVR 5.3.1/13

Refresh and Compare

This section lists the capabilities related to Refresh and Compare.

HVR Capability Support Status
Refresh or Compare from source location Only supported on:
Select more than 4 billion rows during Refresh or Compare Supported on all classes, except for:
Refresh into target location Supported on all classes
Row-wise refresh into target location (option -g) Supported on all classes, except for:
Disable/enable foreign keys and secondary indices during refresh (option -F) Only supported on:
Disable/enable constraints check during refresh Only supported on:
Disable/enable foreign keys from table to others during refresh (option -F) Only supported on:
Defer foreign keys during refresh (option -F) Only supported on:
For a table: disable/enable journaling, disable/enable unique/primary constraints, disable/enable volatile secondary indices, support main storage structure during refresh Only supported on:
Disable/enable triggers during refresh (option -f) Only supported on:
Replicate database sequences (using action DbSequence) Only supported on:
Suggestions in GUI for Slice Boundaries using DBMS statistics (refresh option -S) Only supported on:
  • Oracle version 11.0 and above, since HVR 5.3.1/21
Select data from each table from same consistent moment in time (refresh options -Mnow, -Mscn=val, -Mhvr_tx_seq=val, -Mtime) Only supported on:
Select data from each table from same consistent moment in time using a single transaction (and session) with 'serializable' SQL isolation level (refresh option -Mserializable) Only supported on:
Select data from each table from same consistent moment in time using a single transaction (and session) with 'snapshot' SQL isolation level (refresh option -Msnapshot) Only supported on:
Enable foreign keys immediately after refresh option -Mserializable as done on -Msnapshot and -Mnow Only supported on:

Other Capabilities

This section lists the capabilities related to Other Capabilities.

HVR Capability Support Status
Use distribution key for parallelizing changes within a table (ColumnProperties /DistributionKey) Only supported on:
Call database procedure dbproc during replication jobs (action AgentPlugin /DbProc) Only supported on:
DbObjectGeneration with /IncludeSQLFile Only supported on:
International table and column names where DBMS is not configured with UTF-8 encoding Supported on all classes, except for:
Lossless binary float datatypes. No dataloss when transporting float values (because base 2 fractions are never converted to base 10) Only supported on:
Treat DBMS table names and columns case sensitive (action LocationProperties /CaseSensitiveNames) Only supported on:
Reduce width of datatype when selecting or capturing changes (action ColumnProperties /TrimDatatype) Only supported on: