KFAA30723-E

An error occurred during communication with the HADB server. Another possibility is that the HADB server terminated abnormally.

aa....aa:

Cause of the failure

Value of aa....aa	Meaning	SQLSTATE
SERVER NOT UP	The HADB server is not running.	08004
HOST NAME	The address of the target host cannot be acquired.	52322
NETWORK	One of the following failures was detected: A failure occurred on the network. The connection was blocked by the local firewall rules. The HADB server terminated abnormally and the connection was closed. The connection was closed because the HADB client version differs from the HADB server version.	52324
SecurityException	A security violation occurred in the JDBC driver.	52325
TIMEOUT	A timeout occurred during connection to the HADB server or data transmission.	52326
SYSTEM CALL ERROR	A system call error occurred during communication processing.	52328
DESCRIPTOR	A descriptor shortage occurred.	53040
INSUFFICIENT NETWORK PORT	Allocation of communication port numbers failed.	53041
CLIENT MEMORY	A memory shortage occurred in a client library.	53201

S:

Terminates processing.

Action:

Re-execute the application program. If this message is output, it means that the connection to the HADB server has been closed; you must restore the connection before re-executing.

If CLIENT MEMORY is indicated as the cause of the failure, use the following procedure to resolve the memory shortage:

1. Check for any unnecessary processes. If any unnecessary processes are running, shut them down. Then, re-execute the command or SQL statement.

2. If there is not enough memory after performing step 1, restart the OS. Then, re-execute the command or SQL statement.

3. If there is not enough memory after performing step 2, change the kernel parameter setting to increase the amount of memory that processes can use. Restart the OS, and then re-execute the command or SQL statement.

If HOST NAME is displayed as the cause of the failure, carefully review the values specified in the client definition's adb_clt_rpc_srv_host operand, the hosts file, the settings of the DNS server, and so on.

If SERVER NOT UP is displayed even though the HADB server is running, check whether either of the following applies:

• Has the host name specified in the client definition's adb_clt_rpc_srv_host operand correctly resolved to the IP address of the host on which the HADB server is running?

• Is the same port number specified in the client definition's adb_clt_rpc_srv_port operand and the server definition's adb_rpc_port operand?

If neither of these resolves the problem, check the network settings, such as the firewall settings.

If SecurityException is displayed as the cause of the failure, enable a connect to the server host with java.net.SocketPermission, or disable the security manager. Also make sure that the server host name can be resolved.