DB2 10.5 for Linux, UNIX, and Windows

Changing database partitions (Windows)

On Windows, use the db2nchg command to change database partitions.

About this task

Move the database partition from one computer to another.
Change the TCP/IP host name of the computer.
If you are planning to use multiple network adapters, you must use this command to specify the TCP/IP address for the "netname" field in the db2nodes.cfg file.
Use a different logical port number.
Use a different name for the database partition server.

The command has the following required parameter:

   db2nchg /n:node_number

The parameter /n: is the number of the database partition server that you want to change. This parameter is required.

Optional parameters include:

/i:instance_name: Specifies the instance that this database partition server participates in. If you do not specify this parameter, the default is the current instance.
/u:username,password: Changes the logon account name and password for the DB2® database service. If you do not specify this parameter, the logon account and password remain the same.
/p:logical_port: Changes the logical port for the database partition server. This parameter must be specified if you move the database partition server to a different computer. If you do not specify this parameter, the logical port number remains unchanged.
/h:host_name: Changes the TCP/IP host name used by FCM for internal communications. If you do not specify this parameter, the host name is unchanged.
/m:computer_name: Moves the database partition server to another computer. The database partition server can be moved only if there are no existing databases in the instance.
/g:network_name: Changes the network name for the database partition server.
Use this parameter if you have multiple IP addresses on a computer and you want to use a specific IP address for the database partition server. You can enter the network_name using the network name or the IP address.

For example, to change the logical port assigned to database partition 2, which participates in the instance TESTMPP, to use the logical port 3, enter the following command:

   db2nchg /n:2 /i:TESTMPP /p:3

The DB2 database manager provides the capability of accessing DB2 database system registry variables at the instance level on a remote computer. Currently, DB2 database system registry variables are stored in three different levels: computer or global level, instance level, and database partition level. The registry variables stored at the instance level (including the database partition level) can be redirected to another computer by using DB2REMOTEPREG. When DB2REMOTEPREG is set, the DB2 database manager accesses the DB2 database system registry variables from the computer pointed to by DB2REMOTEPREG. The db2set command would appear as:

   db2set DB2REMOTEPREG=remote_workstation

where remote_workstation is the remote workstation name.

Note:

Care must be taken in setting this option since all DB2 database instance profiles and instance listings will be located on the specified remote computer name.
If your environment includes users from domains, ensure that the logon account associated with the DB2 instance service is a domain account. This ensures that the DB2 instance has the appropriate privileges to enumerate groups at the domain level.

This feature might be used in combination with setting DBINSTPROF to point to a remote LAN drive on the same computer that contains the registry.