hvrinit – Load a replication channel.
hvrinit [–options] hubdb chn
hvrinit encapsulates all steps required to generate and load the various objects needed to enable replication of channel chn. These objects include replication jobs and scripts as well as database triggers/rules for trigger–based capture and table enrollment information for log–based capture.
The first argument hubdb specifies the connection to the hub database. This can be an Oracle, Ingres, SQL Server, DB2, DB2 for i, PosgreSQL, or Teradata database depending on its form. See further section Calling HVR on the Command Line.
|–d||Drop objects only. If this option is not supplied, then hvrinit will drop and recreate the objects associated with the channel such as HVR scripts, internal tables and any transaction files containing data in the replication pipeline. Only a few objects are preserved such as job groups in the scheduler catalogs; these can be removed using hvrinit –d.|
|–E||Recreates enroll file. Using hvrinit –E is same as hvrinit –osctprEljf (in HVRGUI it is same as selecting all options under Object Types).|
|–hclass||Specify hub database. Valid values are oracle, ingres, sqlserver, db2, db2i,postgresql, or teradata. For more information, see section Calling HVR on the Command Line.|
|–ix||Capture rewind. Initialize channel to start capturing changes from a specific time in the past, rather than only changes made from the moment the hvrinit command is run. Capture rewind is only supported for database log–based capture (not for trigger–based capture i.e. /TriggerBased parameter) and for capture from file locations when parameter /DeleteAfterCapture is not defined.
|–Ix||Defines start emitting time.
|–lx||Only affect objects for locations specified by x. Values of x may be one of the following:
Several –lx instructions can be supplied together to hvrinit.
|–oS||Operations limited to objects indicated by S. |
Values of S may be one of the following:
Several –oS instructions can be supplied together (e.g. –octp) which causes hvrinit to effect all object types indicated. Not specifying a –o option implies all objects are affected (equivalent to –osctpreljf).
|–pN||Indicates that SQL for database locations should be performed using N sub–processes running in parallel. Output lines from each subprocess are preceded by a symbol indicating the corresponding location. This option cannot be used with option –S.|
|–S||Write SQL to stdout instead of applying it to database locations. This can either be used for debugging or as a way of generating a first version of an SQL include file (see action DbObjectGeneration /IncludeSqlFile), which can later be customized. This option is often used with options –lloc –otp.|
|–ty||Only affect objects referring to tables specified by y. Values of y may be one of the following:
Several –ty instructions can be supplied together to hvrinit.
|–uuser [/pwd]||Connect to hub database using DBMS account user. For some databases (e.g. SQL Server) a password must also be supplied.|
|│||└─||*.logrelease||Which log–based capture journals or archive files have been released by the capture job.|
|│||└─||YYYYMMDD||Journal files created by action Integrate /JournalRouterFiles.|
|├─||job||Directory containing generated job scripts. Some jobs use static scripts instead.|
|├─||router||Directory containing replication state.|
|└─||sqlgen||Directory containing temporary files used during generation of SQL.|