KFPA11723-E

An error occurred during communication with the embedded database system or embedded database server. Alternatively, the embedded database system or embedded database server has gone down.

aa....aa: Character string indicating the details of the error

CLIENT MEMORY: A memory shortage occurred in the client library.

FES (SDS) CLOSE: The server is being terminated.

FES (SDS) NOT UP: The server is not running or is being started.

HiRDB BUSY: The embedded database (server) cannot be connected because it is busy.

HiRDB DATA ERROR: Communication data from the embedded database system or embedded database server is invalid.

HiRDB INITIALIZE: The embedded database system or embedded database server is being initialized.

HiRDB NOT UP: The embedded database system or embedded database server is not running. Alternatively, Listen queues on the embedded database server are insufficient.

HiRDB SYSTEM ERROR: A system error was detected in the embedded database system or embedded database server.

HiRDB MEMORY: A memory shortage occurred in the embedded database system or on the embedded database server.

INIT ERROR: An error occurred during initialization for communication.

INVALID SERVER TYPE: The server type of the embedded database (server) differs from PDSRVTYPE (client environment definition).

NETWORK: A network failure occurred. Alternatively, the connection was released due to abnormal termination of the embedded database server.

(S)

Terminates processing.

(P)

When aa....aa is HiRDB BUSY:

Wait a while, and then retry. If this message reappears, contact the embedded database system administrator.

When aa....aa is not HiRDB BUSY:

Report the details of the error to the embedded database system administrator, and then correct the error and retry.

Action

Determine the cause of the error from the error log file output by the embedded database client, correct the cause of the error, and then retry.

If this message (aa....aa is HiRDB NOT UP) still appears during connection even after the embedded database has started, recheck the JP1/AJS3 environment setting parameters. In addition, use a syslog (or Windows event log in Windows) to check for errors on the embedded database server.

If the values of JP1/AJS3 environment setting parameters are correct and the message KFPZ02444-E (func=connect and errno indicating ETIMEDOUT or ECONNREFUSED) is output to the error log file, it is possible that too many requests have been made to the embedded database server. In this case, wait a while and then retry. Alternatively, increase the value specified for the Listen queues.

Note that when this message appears, connection with the embedded database server has been released. Therefore, you must retry starting from the CONNECT statement.