The following table shows the database objects which HVR can create to support replication. The name of each database object either begins with an hvr_ prefix or consists of a replicated table name followed by two underscores and a suffix.
Capture tables (trigger–based capture only).
Capture database rules or triggers.
Capture database procedures (trigger–based capture only).
Database procedures, rules and triggers for capture of dynamic lookup table. Created for action Restrict /DynamicHorizLookup.
Temp table used for faster set-wise queries of DBMS catalogs (Oracle only)
Capture toggle state table (trigger–based capture only).
Capture quick toggle state table (trigger–based capture only).
Capture toggle lock table (Ingres trigger–based capture only).
Capture sequence number (Oracle trigger–based capture only).
tbl*_ _ii *
Integrate database procedures. Created for action Integrate /DbProc.
Burst tables. Used for staging if Integrate /Burst is defined.
tbl* _ _f*
Integrate fail table. Created when needed, i.e. when an integrate error occurs.
Collision history table. Created if action CollisionDetect is defined.
External table. Used for external loading into Greenplum.
Integrate burst state table. Created if action Integrate /Burst is defined.
Integrate receive timestamp table.
Integrate commit frequency table.
Bulk refresh recovery state table.
State table created by Hvrrefresh so that HVR capture can detect the session name.
Integrate role (Ingres only).
Refresh role (Ingres only).
Scheduler role (Ingres only).
- If a table has no non–key columns (i.e. the replication key consists of all columns) then some update objects (e.g. tbl__iu) may not exist.
- Capture objects are only created for trigger–based capture; log–based capture does not use any database objects.
- Action DbObjectGeneration can be used to inhibit or modify generation of these database objects.