Requirements for Ingres and Vector

From HVR
Jump to: navigation, search

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

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

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

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

Location Connection

This section lists and describes the connection details required for creating Ingres/Vector location in HVR.

SC-Hvr-Location Ingres db1.png
Field Description
Database Connection
II_SYSTEM The directory path where the Ingres/Vector database is installed.
  Example: /ingres/921
Database The name of the Ingres/Vector database.
  Example: mytestdb
User The username to connect HVR to Ingres/Vector Database.
  Example: hvruser

Access Privileges


For an Ingres or Vector hub database or database location, each account used by HVR must have permission to use Ingres.

The HVR user should be the owner of the hub database.

Typically HVR connects to database locations as the owner of that database. This means that either HVR is already running as the owner of the database, or that it is running as a user with Ingres Security Privilege. HVR can also connect to a database location as a user who is not the database's owner, although row wise refresh into such a database is not supported if database rules are defined on the target tables.

Accessdb permission screen:


DBA permission screen:

SC-Ingres-VisualDba privs.png

CBF screen. For trigger based capture from Ingres databases, the isolation level (parameter system_isolation) must be set to serializable. Other parameters (e.g. system_readlocks) can be anything.


For HVR to integrate changes into an Ingres installation on a remote machine, a special database role must be created in that Ingres installation. Execute the following script to create this role.

In UNIX or Linux,

 $ sql iidbdb < $HVR_HOME/sql/ingres/hvrrolecreate.sql

In Windows,

 C:\>sql iidbdb < %HVR_HOME%\sql\ingres\hvrrolecreate.sql
UNIX & Linux

Log-based capture from Ingres requires that HVR has permission to read the internal DBMS logging files. Installing this requires a special step to create a trusted executable, which must be performed while logged in as ingres. See step 4 of section New Installation on Unix or Linux. This installation step is not needed if HVR runs under login ingres, and is also not needed if trigger based capture is used or on Microsoft Windows.

Checkpointing an Ingres Capture Database

  • Trigger–based Capture
    If trigger–based capture is defined for an Ingres database, HVR uses SQL DDL statement modify to truncated to empty the capture tables. The locks taken by this statement conflicts with locks taken by an on–line checkpoint. This can lead to HVR jobs hanging or deadlocking. These problems can be solved by creating file $HVR_CONFIG/files/dbname.avoidddl just before checkpointing database dbname and deleting it afterwards. HVR will check for this file, and will avoid DDL when it sees it.
    Under Unix, do this as follows:
    $ touch $HVR_CONFIG/files/mydb.avoidddl
    $ sleep 5
    $ ckpdb mydb
    $ rm $HVR_CONFIG/files/mydb.avoidddl
  • Log–based Capture
    If log–based capture is defined for an Ingres database (action Capture) then HVR may need to go back to reading the Ingres journal files. But each site has an existing backup/recovery regime that periodically deletes these Ingres checkpoint and journal files. Command hvrlogrelease can make cloned copies of these files so that HVR's capture is not affected when these files are purged by the site's backup/recovery regime. When the capture job no longer needs these cloned files, then hvrlogrelease will delete them again.