After the machine name is changed, the DB2 instance cannot be started and the sql6031n error is reported?

After the machine name is changed, the DB2 instance cannot be started and the sql6031n error is reported?

DB2Version8Start, the originalDB2The Enterprise Edition and enterprise extended edition are merged into the Enterprise Server Edition. For partitioned and non-partitioned databasesDb2nodes. cfgFile, which records the server node information.

ToWindowsFor exampleTsstest1A single-partition database instance onDB2, In"Sqllib" DB2DirectoryDb2nodes. cfgThe following line is recorded in the file:

0 tsstest1 tsstest1 0

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

0 test 0

Otherwise, an error will be reported when the database instance is started.Sql6031nError. cause code:10.

Cause code10To ensure thatDb2nodes. cfgThe"<Line>"The host name defined in the row is defined on the system and can be operated.

InWindowsPlatform. Pay special attention to this issue if you define an instance to be automatically started or are used to starting an instance in a service.