Capabilities for Aurora MySQL

Last updated on Jul 23, 2020

Contents

This section lists the Capabilities of HVR when using 'Aurora MySQL'. For more information about the pre-requisites, access privileges, and other configuration requirements, see Requirements for MySQL and MariaDB.

Capture

HVR supports the following capabilities on Aurora MySQL:

  • Capture changes from location (Aurora MySQL from 1.0 to 2.0, since HVR 5.3.1/25).
  • Log-based capture (capture from DBMS logging system) (Aurora MySQL from 1.0 to 2.0).
  • Log-based capture of tables without a primary key (Aurora MySQL from 1.0 to 2.0).
  • Access to logs using SQL interface (Aurora MySQL from 1.0 to 2.0).
  • Log-based capture of tables with LOB column (Aurora MySQL from 1.0 to 2.0).
  • Rewind log-based capture to specific time (Hvrinit option -i) (Aurora MySQL from 1.0 to 2.0).
  • Online refresh using accurate LSN/SCN (Aurora MySQL from 1.0 to 2.0).
  • Log-based capture of truncate table statements (Aurora MySQL from 1.0 to 2.0).
  • Multiple log-based capture jobs can capture from same database (Aurora MySQL from 1.0 to 2.0).
  • Capture from tables with any compression (Aurora MySQL from 1.0 to 2.0).

HVR does not support the following capabilities on Aurora MySQL:

  • Capture from Archive log files only.
  • Direct access to logs on a file system.
  • Log-based capture from hidden rowid column (ColumnProperties /CaptureFromRowId).
  • Rewind log-based capture to the beginning of currently active oldest transaction.
  • Populates column hvr_cap_user for use in ColumnProperties {hvr_cap_user} substitutions.
  • Log-based capture checkpointing (action Capture /CheckpointingFrequency).
  • Hvrlogrelease to preserve journal/archives.
  • Read archives from an alternative directory (Capture /ArchiveLogPath).
  • Trigger-based capture (action Capture /TriggerBased).

Hub Database

HVR supports Hub database on Aurora MySQL.

Integrate

HVR supports the following capabilities on Aurora MySQL:

  • Integrate changes into location (Aurora MySQL from 1.0 to 2.0, since HVR 5.3.1/25).
  • Integrate with /Burst (Aurora MySQL from 1.0 to 2.0).
  • Integrate with /BurstCommitFrequency (Aurora MySQL from 1.0 to 2.0).
  • Continuous integration (Integrate without /Burst) (Aurora MySQL from 1.0 to 2.0).
  • Action TableProperties with /DuplicateRows for continuous integration (Aurora MySQL from 1.0 to 2.0).
  • Continuous Integrate with /OnErrorSaveFailed (without /Burst) (Aurora MySQL from 1.0 to 2.0).
  • Action Transform /SoftDelete (Aurora MySQL from 1.0 to 2.0).
  • Bulk load requires a staging area (LocationProperties /StagingDirectoryHvr) (Aurora MySQL from 1.0 to 2.0).
  • Creation and update of HVR state tables (Aurora MySQL from 1.0 to 2.0).

HVR does not support the following capabilities on Aurora MySQL:

  • Disable/enable database triggers during Integrate (/NoTriggerFiring).
  • Integrate with /DbProc.

Bi-directional Replication

HVR supports the following capabilities on Aurora MySQL:

  • Detection of changes made by HVR in a bidirectional channel to prevent loop-back (Aurora MySQL from 1.0 to 2.0, since HVR 5.3.1/25).
  • CollisionDetect with /TimestampColumn (Aurora MySQL from 1.0 to 2.0, since HVR 5.3.1/25).

HVR does not support the following capabilities on Aurora MySQL:

Refresh and Compare

HVR supports the following capabilities on Aurora MySQL:

  • Hvrrefresh or Hvrcompare from source location (Aurora MySQL from 1.0 to 2.0, since HVR 5.3.1/25).
  • Hvrrefresh into target location (Aurora MySQL from 1.0 to 2.0).
  • Row-wise Hvrrefresh into target location (option -g) (Aurora MySQL from 1.0 to 2.0).

Other Capabilities

HVR supports the following capabilities on Aurora MySQL:

  • Call database procedure dbproc during replication jobs (action AgentPlugin /DbProc) (Aurora MySQL from 1.0 to 2.0, since HVR 5.3.1/25).
  • International table and column names where DBMS is not configured with UTF-8 encoding (Aurora MySQL from 1.0 to 2.0).
  • Treat DBMS table names and columns case sensitive (action LocationProperties /CaseSensitiveNames) (Aurora MySQL from 1.0 to 2.0, since HVR 5.3.1/25).
  • Always treat DBMS table names and column names case sensitive (Aurora MySQL from 1.0 to 2.0).

HVR does not support the following capabilities on Aurora MySQL:

  • Use distribution key for parallelizing changes within a table (ColumnProperties /DistributionKey).
  • Lossless binary float datatypes. No data loss when transporting float values (because base 2 fractions are never converted to base 10).