Why the DB2 instance will fail to start after you modify the machine name

Question: Why did the instance fail to start after modifying the machine name and reported sql6031n error.

Environment:

Product DB2

Platform Cross Platform

Version 8.1

Answer:

DB2 version 8, the original DB2 Enterprise and Enterprise Extensions merged into the Enterprise Server Edition, regardless of the partitioned database and the non-partitioned database, there will be db2nodes.cfg files in the instance directory, which records the server node information.

Take the Windows platform for example, for a single partitioned database instance on the machine named TSSTEST1, DB2. The following line is recorded in the Db2nodes.cfg file in the SQLLIB\DB2 directory:

0 TSSTEST1 TSSTEST1 0

If you modify the machine name of the machine, you need to modify the file. For example, if you modify the machine name TSCTEST1, the above file needs to be modified to

0 TSCTEST1 TSCTEST1 0

Otherwise, the sql6031n error is reported when the evidence library instance is started, with the reason code 10.

The explanation for reason code 10 is:

(10) To ensure that the Db2nodes.cfg "< line designtimesp=29798>"

The host name values defined in the row are defined on the system and can be manipulated.

In the Windows platform, you need to pay special attention to this problem if you define an instance to start automatically, or if you are accustomed to starting an instance in a service.