Naming of HVR Objects Inside Database Locations

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.

Name	Description
tbl_ _c0 tbl_ _c1	Capture tables (trigger–based capture only).
tbl_ _ci tbl_ _cd tbl_ _cu	Capture database rules or triggers.
tbl_ _c tbl_ _c0 tbl_ _c1	Capture database procedures (trigger–based capture only).
tbl_ _l tbl_ _li tbl_ _ld tbl_ _lu	Database procedures, rules and triggers for capture of dynamic lookup table. Created for action Restrict /DynamicHorizLookup.
hvr_sys_table	Temp table used for faster set-wise queries of DBMS catalogs (Oracle only)
hvr_togchn	Capture toggle state table (trigger–based capture only).
hvr_qtogchn	Capture quick toggle state table (trigger–based capture only).
hvr_lktogchn	Capture toggle lock table (Ingres trigger–based capture only).
hvr_seqchn	Capture sequence number (Oracle trigger–based capture only).
tbl_ _ii tbl_ _id tbl_ _iu	Integrate database procedures. Created for action Integrate /DbProc.
tbl_ _b	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.
tbl_ _h	Collision history table. Created if action CollisionDetect is defined.
tbl_ _x	External table. Used for external loading into Greenplum.
hvr_stbuchn_loc	Integrate burst state table. Created if action Integrate /Burst is defined.
hvr_stinchn_loc	Integrate receive timestamp table.
hvr_stischn_loc	Integrate commit frequency table.
hvr_strrchn_loc	Bulk refresh recovery state table.
hvr_strschn_loc	State table created by Hvrrefresh so that HVR capture can detect the session name.
hvr_integrate	Integrate role (Ingres only).
hvr_refresh	Refresh role (Ingres only).
hvr_scheduler	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.