Adds a Transmission Control Protocol/Internet Protocol (TCP/IP) database partition server entry to the node directory. The TCP/IP communications protocol is used to access the remote database partition server. The CATALOG TCPIP/TCPIP4/TCPIP6 NODE command is run on a client.
None. Directory operations affect the local directory only.
>>-CATALOG--+-------+--+-TCPIP NODE--+--nodename----------------> '-ADMIN-' +-TCPIP4 NODE-+ '-TCPIP6 NODE-' >--REMOTE--+-hostname-----+--SERVER--+-service-name-+-----------> +-IPv4 address-+ '-port number--' '-IPv6 address-' >--+----------------+--+--------------------------------+-------> +-SECURITY SOCKS-+ '-REMOTE_INSTANCE--instance-name-' '-SECURITY SSL---' >--+---------------------+--+-------------------------------+---> '-SYSTEM--system-name-' '-OSTYPE--operating-system-type-' >--+------------------------+---------------------------------->< '-WITH--"comment-string"-'
If a service name is specified, the services file on the client is used to map the service name to a port number. A service name is specified in the server's database manager configuration file, and the services file on the server is used to map this service name to a port number. The port number on the client and the server must match.
A port number, instead of a service name, can be specified in the database manager configuration file on the server, but this is not recommended. If a port number is specified, no service name needs to be specified in the local services file.
This parameter must not be specified for ADMIN nodes, but is mandatory for non-ADMIN nodes. The value on ADMIN nodes is always 523.
If this command is issued after a db2start, it is necessary to issue a TERMINATE command to have the command take effect.
db2 catalog tcpip node db2tcp1 remote hostname server db2inst1
with "Look up IPv4 or IPv6 address from hostname"
db2 catalog tcpip4 node db2tcp2 remote 192.0.32.67 server db2inst1
with "Look up IPv4 address from 192.0.32.67"
This example specifies an IPv4 address. You should not specify an IPv6 address in the CATALOG TCPIP4 NODE command. The catalog will not fail if you do, but a subsequent attach or connect will fail because an invalid address was specified during cataloging.
db2 catalog tcpip6 node db2tcp3 1080:0:0:0:8:800:200C:417A server 50000
with "Look up IPv6 address from 1080:0:0:0:8:800:200C:417A"
This example specifies an IPv6 address and a port number for SERVER. You should not specify an IPv6 address in the CATALOG TCPIP4 NODE command. The catalog will not fail if you do, but a subsequent attach or connect will fail because an invalid address was specified during cataloging.
db2 catalog tcpip node db2tcp4 remote hostname server ssl_port
The database manager creates the node directory when the first node is cataloged (that is, when the first CATALOG...NODE command is issued). On a Windows client, it stores and maintains the node directory in the instance subdirectory where the client is installed. On an AIX client, it creates the node directory in the DB2 installation directory.
List the contents of the local node directory using the LIST NODE DIRECTORY command.
If directory caching is enabled, database, node, and DCS directory files are cached in memory. An application's directory cache is created during its first directory lookup. Since the cache is only refreshed when the application modifies any of the directory files, directory changes made by other applications might not be effective until the application has restarted.
To refresh the CLP's directory cache, use the TERMINATE command. To refresh DB2's shared cache, stop (db2stop) and then restart (db2start) the database manager. To refresh the directory cache for another application, stop and then restart that application.
To get the DB2 database manager to listen on IPv6, the operating system and server must first be configured for IPv6. Speak to your system administrator to ensure this configuration has been done before cataloging an IPv6 TCPIP node. Follow Upgrading to IPv6 with IPv4 configured to see how this can be done on AIX 6.1.