Why DB2 instance cannot be started after machine name Modification

The following article describes the reasons why the DB2 instance cannot be started after the machine name is modified, if you are interested in the reason why the DB2 instance cannot be started, you can click the following article to view it.

Starting from DB2 version 8, the original DB2 Enterprise Edition and the Extended Enterprise Edition are merged into the Enterprise Server Edition. For partitioned and non-partitioned databases, db2nodes is available in the instance directory. cfg file, which records the server node information.

Question: Why does the instance fail to start after the machine name is modified and the SQL6031N error is reported.

Environment:

Product DB2

Cross-platform

Release 8.1

Answer:

Since DB2 version 8, the original DB2 Enterprise Edition and enterprise extended edition are merged into the Enterprise Server Edition. For partitioned and non-partitioned databases, there will be db2nodes under the instance directory. cfg file, which records the server node information.

Take Windows as an example. For a single-partition database instance DB2 named TSSTEST1, the following row is recorded in the db2nodes. cfg file under the .. SQLLIB \ DB2 Directory:

0 TSSTEST1 TSSTEST1 0

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

0 TSCTEST1 TSCTEST1 0

Otherwise, the SQL6031N error is reported when the real-time database instance is started. The cause code is 10.

The reason 10 is:

(10) Make sure the "<row>" in db2nodes. cfg"

The host name defined in the row is defined on the system and can be operated.

On Windows, pay special attention to this issue if you define an instance to be automatically started or used to start an instance in a service.

The above content is a description of why the DB2 instance cannot be started after the machine name is modified. I hope it will help you in this regard.