KFAA50300-E

An error has occurred in system call aa....aa.

aa....aa:

Name of system call in which the error occurred

bb....bb:

Error number

S:

Terminates processing. However, in the case of temporary errors, the system might retry the operation.

Action:

Check in the OS documentation for the system call name and error number that are displayed, and then eliminate the cause of the error. If you cannot determine the corrective action to take based on the system call name and error number that are displayed, execute an adbinfoget command to collect troubleshooting information, and then contact the customer support center.

The following table describes the major system call errors and corrective actions to take.

No.	Error details			Possible causes	Corrective actions to take
	System call name	Error number
		In Linux	In Windows
1	accept	23 24	--	Too many files are opened or too many connections have been established to the HADB server. The maximum number of descriptors is too small.	Terminate unnecessary processes. Reduce the number of connections to the HADB server. Use the kernel parameters nofile and file-max to increase the maximum number of descriptors.# 1 Reduce the number of DB areas.
2	bind	98	--	The port number used for accepting a connection is being used by another process.	Change the specified port number. Terminate the other process that is using the same port number.
3	connect	99	10055	The local ports are busy.	Wait for a local port to be available. Terminate another process that is performing communication. Use the kernel parameter ip_local_port_range or the Windows command netsh to expand the range of temporary ports assigned by the OS.# 1
4		101 110 113	10049 10051 10060 10065	An invalid connection destination is specified. The destination host does not exist. The specified host name has been resolved to an incorrect IP address. A communication path failure occurred.# 2	Make sure that the connection destination is specified correctly. Connect the destination host to the network. Check the DNS or hosts file settings. Alternatively, specify the IP address for the host name. Check whether a communication path failure occurred.
5	readv recv	101 110 113	10060	A communication path failure occurred.# 2 The network configuration or network settings are changed.	Check whether a communication path failure occurred. Check the physical configuration and settings of the network.
6		104	10054	The remote party process terminated forcibly. The remote party detected a problem such as a communication timeout or error, and explicitly and forcibly disconnected communications. The application program has not explicitly disconnected the connection with the HADB server before termination of the process. Communications were blocked as a result of a communication path failure or similar failure.# 2 After that, attempts to transfer the same transmission packet were made several times. However, no response was received from the other side of communication, so the OS has reset this communication. At this time, the connection might remain at the communication destination. However, this connection will be terminated after some time has passed.	If an HADB server terminated forcibly, restart it. If an HADB server in a multi-node configuration terminated forcibly, restart that HADB server. If the remote party is an HADB server in a multi-node configuration in which another HADB server is running, wait a while, and then reconnect to the HADB server in the multi-node configuration. If the remote party is an HADB client, re-establish a connection from the HADB client to the HADB server. Revise the values of timer monitoring operands specified on the remote party. For example, revise the values of the adb_rpc_wait_time operand in the server definition and adb_clt_rpc_sql_wait_time operand in the client definition. Check the message log file on the remote party. Take corrective action for the output error message. Revise the contents of application program processing. If the processing to disconnect the HADB server is not specified, add that processing. To immediately disconnect the remaining connection on the HADB server, use the command adbls to investigate the connection status. After that, disconnect the unnecessary connection by using the command adbcancel. If communications are frequently reset as a result of the communication path being blocked, identify the location of the blockage in the communication path, and eliminate the cause of the failure.
7	socket	23 24	10024	Too many files are open or too many connections have been established with the HADB server. The maximum number of descriptors is too small.	Terminate unnecessary processes. Reduce the number of connections to the HADB server. Use the kernel parameters nofile and file-max to increase the maximum number of descriptors.# 1
8	writev send	32 104	10054	The remote party process terminated forcibly. The remote party detected a problem such as a communication timeout or error, and explicitly and forcibly disconnected communications. Communications were blocked as a result of a communication path failure or similar failure.# 2 After that, attempts to transfer the same transmission packet were made several times. However, no response was received from the other side of communication, so the OS has reset this communication. At this time, the connection might remain at the communication destination. However, this connection will be terminated after some time has passed.	If an HADB server terminated forcibly, restart it. If an HADB server in a multi-node configuration terminated forcibly, restart that HADB server. If the remote party is an HADB server in a multi-node configuration in which another HADB server is running, wait a while, and then reconnect to the HADB server in the multi-node configuration. If the remote party is an HADB client, re-establish a connection from the HADB client to the HADB server. Revise the values of timer monitoring operands specified on the remote party. For example, revise the values of the adb_rpc_wait_time operand in the server definition and adb_clt_rpc_sql_wait_time operand in the client definition. Check the message log file on the remote party. Take corrective action for the output error message. To immediately disconnect the remaining connection on the HADB server, use the command adbls to investigate the connection status. After that, disconnect the unnecessary connection by using the command adbcancel. If communications are frequently reset as a result of the communication path being blocked, identify the location of the blockage in the communication path, and eliminate the cause of the failure.
9		101 110 113	10060 10065	A communication path failure occurred.# 2 The network configuration or network settings are changed.	Check whether a communication path failure occurred. Check the physical configuration and settings of the network.

#1

For details, see the OS documentation.

#2

The following shows examples of communication path failures.

- A cable is removed or disconnected.

- A stop or error of the network interface (NIC) is detected.

- A firewall blocks communications (including a case in which packets are discarded without notice).

- Power supply to the communication equipment is turned off.

- The communication equipment failed.

- Packets delayed or disappeared due to concentration of traffic or for other reasons.

- The destination host cannot respond because it is busy.