1.DB2COMM=TCPIP

2. Database failure

3. The port number is disabled

Solution:

1. Check whether the port number is configured correctly and whether the configuration parameter svcename is consistent with the db2 port number configured in the service file. Windows generally uses 50000, and unix/linux generally uses 60000.

2. Connection error First check whether the server ip and port are written correctly.

If the ip is correct, it depends on whether the db2 service port of the server is correct. In addition, you should also pay attention to the following aspects of the server.

Check the configuration of the server as follows:

Verify that the DB2 database exists.

Db2 list database directory

Db2 listdb directory shows details.

Verify the communication protocol used by the instance and look at the DB2COMM variable.

db2set -all

Check the configuration of the database manager, and check the SVCENAME (especially the tcpip protocol).

db2 get dbm cfg

Check /etc/services to see if there is a SVCENAME port corresponding to the above, for example:

db2cDB2 50000/tcp

To confirm whether the server is listening, netstat -an can be used to check whether the port is in listening state.