Environment Description:
Today, the Linux system installed on the virtual machine, and loaded with DB2, but in the connection encountered a problem, baffled. Here are the specific questions and solutions
Problem Description:
Workaround:
1. Ping the server first to ping.
If the server ping fails, then is the network problem, need to modify the corresponding connection and IP, this does not describe
2. Check that the server firewall is close enough
Note: We need to shut down two types of firewalls in Linux
2.1 Shutdown of Iptables firewall
2.2 Hardware Firewall
Log in as root user:
(1) View firewall status.
Systemctl Status Firewalld
(2) Temporarily shut down the firewall command. After restarting your computer, the firewall is automatically up.
Systemctl Stop Firewalld
(3) Permanently shut down the firewall command. After rebooting, the firewall does not start automatically.
Systemctl Disable FIREWALLD
Open the Firewall command.
Systemctl Enable Firewalld
3. Check the Local Catalog
Check the Local Node Catalog: DB2 list node Directory
Check Database catalog: DB2 List DB directory
4. Check the port
Check the port to telnet directly.
When the above 4 conditions are met, it is generally possible to connect to the remote database.
SQL30081N detected a communication error. Communication protocol in use: "TCP/IP"