DB2 Version 9.7 for Linux, UNIX, and Windows

Recataloging nodes and databases using TCP/IP protocol

Recataloging nodes using the TCP/IP protocol is required when the communication protocol that you used to catalog these nodes is no longer supported or when you want to use a feature that supports only TCP/IP protocol. If you change the node name, you must recatalog the databases as well to use the new node name.

The NetBIOS and SNA protocols are discontinued since DB2® Version 9.1. You must recatalog, using a valid protocol, any nodes that you cataloged with the NetBIOS and SNA protocols. If you try to connect to any databases cataloged on a node that uses the NetBIOS or SNA protocol, your connection request returns an error because these protocols are invalid.

If you have a Version 8 client installed on the same system as a DB2 Version 9.7 server or a Version 9.7 client installed on the same system as a DB2 Version 8 server, connections to the databases on the DB2 server from the DB2 client cataloged using a local node are not supported. If you do not upgrade the Version 8 client or DB2 Version 8 server to DB2 Version 9.7, recatalog local nodes as TCP/IP nodes.

If you want to use the trusted context capability on upgraded databases that are cataloged using a local node, recatalog the nodes using the TCP/IP protocol.

About this task

Restrictions

The only protocols available in DB2 Version 9.7 are TCP/IP, Named Pipes, and SSL.

Before you begin

Ensure that you have SYSADM or SYSCTRL authority.
Ensure that you have network connectivity from the client to the DB2 server.

Procedure

To recatalog nodes and databases specifying the TCP/IP protocol:

Determine which are the local nodes that you want to recatalog or the nodes use the NetBIOS or SNA protocol by issuing the LIST NODE DIRECTORY command:
```
   db2 LIST NODE DIRECTORY show detail > node_list.log
```
Redirect the output of this command to a file and keep it, because the information is useful to recatalog your nodes.
Remove the local nodes that you want to recatalog and all nodes that use NetBIOS or SNA protocol from the node directory by issuing the UNCATALOG NODE command:
```
   db2 UNCATALOG NODE node-name
```
Determine which databases use the nodes that you uncataloged in the previous step by issuing the LIST DATABASE DIRECTORY command:
```
   db2 LIST DATABASE DIRECTORY show detail > database_list.log
```
If you are going recatalog your nodes using a different node name, remove all databases using those nodes by issuing the UNCATALOG DATABASE command:
```
   db2 UNCATALOG DATABASE database-name
```
Recatalog your nodes specifying TCP/IP as the protocol by issuing the CATALOG TCPIP NODE command. If you use the original node name, you do not have to recatalog your databases.
```
  db2 CATALOG TCPIP NODE new-node REMOTE host-name 
        SERVER instance-svcename REMOTE_INSTANCE instance-name
```
You can determine the value of instance-svcename by looking at the value of the svcename database manager configuration parameter for that instance.
If you did not recatalog your nodes using the original node names, recatalog your databases using the new node name by issuing the CATALOG DATABASE command.
```
   db2 CATALOG DATABASE db-name [AS alias-db-name] 
         AT NODE new-node
```