Requirements for Greenplum

From HVR
Jump to: navigation, search

This section describes the requirements, access privileges, and other features of HVR when using Greenplum for replication. For information about the capabilities supported by HVR on Greenplum, see Capabilities for Greenplum.

For information about compatibility and supported versions of Greenplum with HVR platforms, see Platform Compatibility Matrix.

Capture Hub Integrate
Icon-No.png Icon-No.png Icon-Yes.png

ODBC Connection

HVR does not need to be installed on any of the nodes of the Greenplum cluster. It can be installed on a machine outside the cluster from which it uses ODBC to connect to the Greenplum cluster. HVR requires the DataDirect Connect XE ODBC driver for Greenplum installed (on the machine from which HVR connects to Greenplum server). HVR only supports ODBC driver version from to 7.1.6.

Location Connection

This section lists and describes the connection details required for creating Greenplum location in HVR.

SC-Hvr-Location Greenplum.png
Field Description
Database Connection
Node The hostname or ip-address of the machine on which the Greenplum server is running.
  Example: gp430
Port The port on which the Greenplum server is expecting connections.
  Example: 5432
Database The name of the Greenplum database.
  Example: sfdec02
User The username to connect HVR to the Greenplum Database.
  Example: hvruser
Password The password of the User to connect HVR to the Greenplum Database.
Linux / Unix
Driver Manager Library The directory path where the Unix ODBC Driver Manager Library is installed.
  Example: /opt/Progress/DataDirect/Connect64_for_ODBC_71/lib
ODBCINST The directory path where odbcinst.ini file is located.
  Example: /opt/Progress/DataDirect/Connect64_for_ODBC_71/odbcinst.ini
ODBC Driver The user defined (installed) ODBC driver to connect HVR to the Greenplum server.

Integrate and Refresh Target

HVR supports integrating changes into Greenplum location. This section describes the configuration requirements for integrating changes (using integrate and refresh) into Greenplum location.

Burst Integrate and Bulk Refresh

HVR allows you to perform Integrate with Burst and Bulk Refresh on Greenplum (it uses the Greenplum Parallel File Distribution (gpfdist) server for maximum performance).

To use the Greenplum Parallel File Distribution (gpfdist) server for bulk loading operations (Integrate with Burst and Bulk Refresh) ensure that gpfdist is configured on the machine from which HVR will connect to Greenplum.

To perform Integrate with Burst and Bulk Refresh, define action LocationProperties on Greenplum location with the following parameters:

  • /StagingDirectoryHvr: the location where HVR will create the temporary staging files. This should be the -d (directory) option of the gpfdist server command.
  • /StagingDirectoryDb: the location from where Greenplum will access the temporary staging files. This should be set to gpfdist://<hostname>:<port> where hostname is the name of the machine used to connect to Greenplum and port is the -p (http port) option of the gpfdist server command.

Example of a gpfdist command line in Linux & Unix:

/opt/gpfdist-4.3.0/gpfdist -p 33333 -d /home/hvr/tsuite_staging -l /home/hvr/staging/gpfdist.log -m 10485760

On Windows, the gpfdist is a service and the values can be retrieved from the "Path to Executable" on the properties dialog of the service.

Grants for Compare, Refresh and Integrate

The hvr user requires the following privileges:

grant connect and create table on the database
grant select, insert, update, delete on replicated tables

If the HVR user needs to change tables which are in another schema (using action TableProperties /Schema=myschema) then the following grants are needed:

grant usage on myschema to hvr_user;

When HVR Refresh is used to create the target tables, the following is also needed:

grant create on myschema to hvr_user;

HVR's internal tables, like burst and state-tables, will be created in schema public unless the search_path is set for this connection. This can be done using action: Environment /Name=HVR_SQL_INIT /Value="set search_path=hvrschema;". In this case the following grants are also needed:

grant usage on hvrschema to hvr_user;
grant create on hvrschema to hvr_user;