Dynamic Vnode Specification—Connect to Remote Node
When connecting to a remote node (using the vnode::dbname syntax), you can specify a dynamic vnode instead of a vnode name. The dynamic vnode specification includes the connection data, user authorization, and attributes that are associated with a remote node.
Note: A dynamic vnode can be used wherever a vnode is allowed, unless otherwise stated.
A dynamic vnode specification has the following format:
@host,protocol,port[;attribute=value{;attribute=value}][[user,password]]
@host
Identifies the network name or address of the node on which the remote database is located. The @ character is required because it identifies this specification as a dynamic vnode rather than a vnode name.
protocol
Identifies the network protocol to be used by the local node to connect to the remote node. For a list of protocols and their associated keywords, see
Network Protocol Keywords (see page
Network Protocol Keywords).
port
Identifies the listen address of the instance on the remote node.
attribute=value
(Optional) Is one or more additional connection, encryption, and authentication attributes for the connection. Vnode attributes are described in
Configure Vnode Attributes (see page
Configure Vnode Attributes).
[user,password]
(Optional) Identifies the user (login) name and password on the remote system.
Note: If used, the user name and password must be enclosed in brackets.
Examples of dynamic vnode specification:
This command runs the terminal monitor (sql) and connects to node hosta using protocol tcp_ip to remote Ingres symbolic port II. The login and password are Johnny and secretpwd. The remote database name is customerdb:
sql @hosta,tcp_ip,II;[Johnny,secretpwd]::customerdb
This command establishes a direct connection by using the connection_type attribute:
sql @hosta,tcp_ip,II;connection_type=direct[Johnny,secretpwd]::customerdb