Hvrtestlistener, hvrtestlocation, hvrtestscheduler

From HVR
Jump to: navigation, search
Previous: hvrswitchtable
Next: None
Command Reference


hvrtestlistener – Test listening on TCP/IP port for HVR remote connection
hvrtestlocation – Test connection to HVR location
hvrtestscheduler – Test (ping) that the HVR Scheduler is running.


hvrtestlistener [–Cpubcert] [–Kpair] [–Llogin/pwd] [–tN] node port
hvrtestlocation [–hclass] [–lloc]... [–tN] [–uuser] hubdb chn
hvrtestscheduler [–nnode][–tN] hubdb


Command hvrtestlistener tests that an HVR process is listening on a TCP/IP port for a HVR remote connection. If option –L is supplied then it also tests the authentication for that login and password.

Command hvrtestlocation tests a connection to an HVR location.

Command hvrtestscheduler checks if the HVR scheduler is running.


Parameter Description
–Cpubcert Remote public certificate for testing encrypted SSL connection.
–hclass Specify hub database. Valid values are oracle, ingres, sqlserver, db2, db2i, postgresql, and teradata. See also section Using HVR for Replication Transformations.
–Kpair SSL public certificate and private key of local machine. If pair is relative, then it is found in directory $HVR_HOME/lib/cert. Value pair specifies two files; the names of these files are calculated by removing any extension from pair and then adding extensions .pub_cert and .priv_key. For example, option –Khvr refers to files $HVR_HOME/lib/cert/hvr.pub_cert and $HVR_HOME/lib/cert/hvr.priv_key.
–lx Test locations specified by x. If this option is not supplied, then hvrtestlocation will test all locations within the channel. Values of x may be one of the following:
loc Only test location loc.
l1l2 Test all locations that fall alphabetically between l1 and l2 inclusive.
!loc Test all locations except loc.
!l1l2 Test all locations except for those that fall alphabetically between l1 and l2 inclusive.

Several –lx instructions can be supplied together to hvrtestlocation.

–Llogin/pwd Test authentication of login/password on remote machine.
–nnode Connect to HVR Scheduler running on node.
–Rnode:port Connect to node as a proxy. This option can be supplied multiple time for a chain of proxies. For more information, see section hvrproxy.
–tN Time–out after N seconds if network is hanging or HVR Scheduler takes too long to reply.
–uuser [/pwd] Connect to hub database using DBMS account user. For some databases (e.g. SQL Server) a password must also be supplied.