Chapter 2 Message List

An error occurred during execution of the application or command.

Processing will be aborted.

Check the message text and confirm that the application is written correctly and the command is being used correctly.

By default, checksums are verified and checksum failures are reported for any possible page corruptions

Continues processing.

Check the message text and confirm that the event indicated in supplementary information reported by the system is a planned event.

The input parameter in invalid.

Processing will be aborted.

Check the message text and confirm that the application is written correctly and the command is being used correctly.

can only be called in a sql_drop event trigger function

Processing will be aborted.

To investigate the cause of the occurrence from the message, and remove cause.

The function pg_event_trigger_table_rewrite_oid() can only be called in a table_rewrite event trigger function

Processing aborts

To investigate the cause of the occurrence from the message, and remove cause.

The function pg_event_trigger_ddl_commands() can only be called in a event trigger function

Processing aborts

To investigate the cause of the occurrence from the message, and remove cause.

SQL row locking clause such as "FOR UPDATE" cannot be applied to a function

Processing aborts

To investigate the cause of the occurrence from the message, and remove cause.

SQL row locking clause such as "FOR UPDATE" cannot be applied to a join

Processing aborts

To investigate the cause of the occurrence from the message, and remove cause.

SQL row locking clause such as "FOR UPDATE" cannot be applied to a WITH query

Processing aborts

To investigate the cause of the occurrence from the message, and remove cause.

SQL row locking clause cannot be applied to the nullable side of an outer join

Processing aborts

To investigate the cause of the occurrence from the message, and remove cause.

SQL row locking cannot be applied to VALUES

Processing aborts

To investigate the cause of the occurrence from the message, and remove cause.

commands VACUUM or ANALYZE cannot be executed from VACUUM or ANALYZE

Processing aborts

To investigate the cause of the occurrence from the message, and remove cause.

Reserved name cannot be used as a role name here

Processing aborts

To investigate the cause of the occurrence from the message, and remove cause.

Cause an error in heartbeat.

Processing aborts.

Check log of Operating System.

Causes an error at application connection.

Processing aborts.

Check log of Operating System.

An error occurred, when specified column of the function is different than the available column

Continues processing.

Investigate the cause of the error from the message body, and then remove the cause.

The return type of function LCS_asString is not allowed with aggregate functions.In this error case,the return type of LCS_asString is "FOR some"

Processing will be aborted.

To investigate the cause of the occurrence from the message, and remove cause

SQL row locking clause such as "FOR UPDATE" is not allowed with DISTINCT clause

Processing aborts

To investigate the cause of the occurrence from the message, and remove cause.

SQL row locking clause such as "FOR UPDATE" is not allowed with GROUP BY clause

Processing aborts

To investigate the cause of the occurrence from the message, and remove cause.

SQL row locking clause such as "FOR UPDATE" is not allowed with HAVING clause

Processing aborts

To investigate the cause of the occurrence from the message, and remove cause.

SQL row locking clause such as "FOR UPDATE" is not allowed with set-returning functions in the target list

Processing aborts

To investigate the cause of the occurrence from the message, and remove cause.

Locking clause is not allowed with UNION/INTERSECT/EXCEPT

Processing aborts

To investigate the cause of the occurrence from the message, and remove cause.

SQL row locking clause such as "FOR UPDATE" is not allowed with window functions

Processing aborts

To investigate the cause of the occurrence from the message, and remove cause.

The function is not an ordered-set aggregate, so it cannot have WITHIN GROUP

Processing aborts

To investigate the cause of the occurrence from the message, and remove cause.

An error occurred during execution of the application or command.

Processing will be aborted.

Check the message text and confirm that the application is written correctly and the command is being used correctly.

When creating a new replication slot, we must put CREATE_REPLICATION_SLOT and USE_SNAPSHOT in REPEATABLE READ isolation mode transAction.

Processing will be aborted.

Check the message text and confirm that the application is written correctly and the command is being used correctly.

When creating a new replication slot, we must put CREATE_REPLICATION_SLOT and USE_SNAPSHOT in a transAction.

Processing will be aborted.

Check the message text and confirm that the application is written correctly and the command is being used correctly.

When creating a new replication slot, we must not put CREATE_REPLICATION_SLOT and USE_SNAPSHOT in a subtransAction.

Processing will be aborted.

Check the message text and confirm that the application is written correctly and the command is being used correctly.

When creating a new replication slot, it is not allowed to put CREATE_REPLICATION_SLOT and EXPORT_SNAPSHOT in a transAction.

Processing will be aborted.

Check the message text and confirm that the application is written correctly and the command is being used correctly.

SQL row locking clause such as "FOR UPDATE" must specify unqualified relation names

Processing aborts

To investigate the cause of the occurrence from the message, and remove cause.

needs a slot to be specified using --slot

Processing aborts

To investigate the cause of the occurrence from the message, and remove cause.

The prepared transaction has been completed.

Continues processing.

No action required.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

There was insufficient free space in the server's memory during execution of the application.

Processing will be aborted.

Estimate memory usage and take the following action:

- If the number of simultaneous connections from client applications is high, reduce it.

- If the number of simultaneous SQL executions is high, reduce it.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

Not a directory.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

Not pid file: number of line is not enough.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

"root" execution of the conmgr is not permitted. The conmgr must be started under an unprivileged user ID to prevent possible system security compromise. See the documentation for more information on how to properly start the conmgr.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

Variables that have greather than 48 level have VARYING clause.

Precompling will be aborted.

Remove "VARYNING" clause or change the level number.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

A new encryption key has been set. The current number of save keys is the number on the left, and the maximum number of save keys is the number on the right.

This is an information messaage when TDE_h is loaded.

Provides notification of the current number of saved keys. If the maximum number is reached, the oldest key is deleted first. Check that the operation is as expected, and if it is not as expected, consider modifying postgresql.conf.

Rollback any active transactions because the database system is being requested to shut down.

Continues processing.

Retry any necessary applications or commands after restarting the database system.

An error occurred due to unexpected directory entry found at specific path

Cancels processing.

Remove those unexpected directories, or set allow_in_place_tablespaces to ON transiently to let recovery complete.

Another conmgr process is running.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

Another conmgr process is shutting down.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

Another conmgr process is starting up.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

Another conmgr process is running.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

Application connection is closed by remote.

Processing continues.

Check log of remote system.

An error occurred during execution of the application or command.

Processing will be aborted.

When assigning to a slice of an empty array value, slice boundaries must be fully specified.

The operating environment such as the status of the connection definition file and the connection method specification is abnormal.

Processing will be aborted.

Confirm that the operating environment such as the status of the connection definition file and the connection method specification is normal.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

Timeout occurred during execution of the application.

Processing will be aborted.

Check the following:

- If executing SQL that outputs a large volume of search results, add a conditional expression to filter the results further.

- If numerous SQLs are being simultaneously executed, reduce the number of simultaneously executed SQLs.

- If a large volume of data is to be updated in a single transaction, modify the SQL to reduce the volume of data to be updated in a single transaction.

- If executing a complex SQL, modify it to a simple SQL.

- Check if there are any problems in the network.

- Before conducting maintenance that involves the processing of a large volume of data, use the SET statement to temporarily increase the value of maintenance_work_mem.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

Timeout occurred during execution of the application.

Processing will be aborted.

Check the following:

- If executing SQL that outputs a large volume of search results, add a conditional expression to filter the results further.

- If numerous SQLs are being simultaneously executed, reduce the number of simultaneously executed SQLs.

- If a large volume of data is to be updated in a single transaction, modify the SQL to reduce the volume of data to be updated in a single transaction.

- If executing a complex SQL, modify it to a simple SQL.

- Check if there are any problems in the network.

- Before conducting maintenance that involves the processing of a large volume of data, use the SET statement to temporarily increase the value of maintenance_work_mem.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

This error occurs if a function wants to set client_encoding and is invoked by the parallel query.

Processing will be aborted.

Check the message text and confirm that client_encoding is not set by the parallel query operation.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred during execution of the application or command.

Processing will be aborted.

Try using the function jsonb_set to replace the key value.

Could not uniquely identify the id.

Processing will be aborted.

Please refer to the server log, and determine the cause of the error.

The operating environment such as the status of the connection definition file and the connection method specification is abnormal.

Processing will be aborted.

Confirm that the operating environment such as the status of the connection definition file and the connection method specification is normal.

Checkpoints are occurring too frequently.

Continues processing.

Consider increasing the value of configuration parameter max_wal_size.

Closing all application connections.

Processing continues.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

Cmdata directory does not exist.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

Conmgr process is ready.

Continues processing.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

Conmgr process is starting.

Processing continues.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

Conmgr process shutting down.

Continues processing.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

Conmgr process stopped.

Processing continues.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

Connection manager directory does not exist.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

COPY statement cannot be null.

Processing will be aborted.

Please specify COPY FROM statement.

Could not accept application connection.

Processing aborts.

Check log of Operating System.

Could not accept heartbeat connection.

Processing aborts.

Check log of Operating System.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

Could not access to cmdata directory.

Processing aborts.

Check log of Operating System.

Could not access to connection manager directory.

Processing aborts.

Check log of Operating System.

Could not add node.

Processing aborts.

Check messages near this message.

Could not be ready for next command.

Processing aborts.

Check log of Operating System.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

Could not bind port with following causes.

Processing aborts.

Check messages near this message.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

Could not change directory.

Processing aborts.

Check log of Operating System.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

Could not connect due to the following errors.

Processing aborts.

Check messages near this message.

Could not connect to conmgr process.

Processing aborts.

Check log of Operating System.

There was insufficient free space in the server's memory during execution of the application.

Processing will be aborted.

Estimate memory usage and take the following action:

- If the number of simultaneous connections from client applications is high, reduce it.

- If the number of simultaneous SQL executions is high, reduce it.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

Could not create an additional interval event.

Processing aborts.

Check log of Operating System.

There was insufficient free space in the disk of the database server during execution of the application.

Processing will be aborted.

Delete user data stored in the database server to free up space on the disk.

Could not create bufferevent.

Processing aborts.

Check log of Operating System.

Could not create conmgr process.

Processing aborts.

Check log of Operating System.

There was insufficient free space in the disk of the database server during execution of the application.

Processing will be aborted.

Delete user data stored in the database server to free up space on the disk.

There was insufficient free space in the disk of the database server during execution of the application.

Processing will be aborted.

Delete user data stored in the database server to free up space on the disk.

There was insufficient free space in the disk of the database server during execution of the application.

Processing will be aborted.

Delete user data stored in the database server to free up space on the disk.

There was insufficient free space in the disk of the database server during execution of the application.

Processing will be aborted.

Delete user data stored in the database server to free up space on the disk.

Could not create pid file.

Processing aborts.

Check log of Operating System.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

There was insufficient free space in the database server's shared memory during execution of the application.

Processing will be aborted.

Estimate memory usage and take the following action:

- If the number of simultaneous connections from client applications is high, reduce it.

- If the number of simultaneous SQL executions is high, reduce it.

There was insufficient free space in the database server's shared memory during execution of the application.

Processing will be aborted.

Estimate memory usage and take the following action:

- If the number of simultaneous connections from client applications is high, reduce it.

- If the number of simultaneous SQL executions is high, reduce it.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

There was insufficient free space in the server's memory during execution of the application.

Processing will be aborted.

Estimate memory usage and take the following action:

- If the number of simultaneous connections from client applications is high, reduce it.

- If the number of simultaneous SQL executions is high, reduce it.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

Could not establish heartbeat connection.

Processing aborts.

Check messages near this message.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

There was insufficient free space in the disk of the database server during execution of the application.

Processing will be aborted.

Delete user data stored in the database server to free up space on the disk.

There was insufficient free space in the disk of the database server during execution of the application.

Processing will be aborted.

Delete user data stored in the database server to free up space on the disk.

Could not get a result from conmgr process.

Processing aborts.

Check log of Operating System.

Failed to load a function in the PKCS11 library.

Processing will be aborted.

Check that the PKCS11 library version and/or path are correct and take action.

The operating environment such as the status of the connection definition file and the connection method specification is abnormal.

Processing will be aborted.

Confirm that the operating environment such as the status of the connection definition file and the connection method specification is normal.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

Could not get string format address.

Processing continues.

Check log of Operating System.

There was insufficient free space in the database server's shared memory during execution of the application.

Processing will be aborted.

Estimate memory usage and take the following action:

- If the number of simultaneous connections from client applications is high, reduce it.

- If the number of simultaneous SQL executions is high, reduce it.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

Could not listen for socket.

Processing aborts.

Check log of Operating System.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

The operating environment such as the status of the connection definition file and the connection method specification is abnormal.

Processing will be aborted.

Confirm that the operating environment such as the status of the connection definition file and the connection method specification is normal.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

Could not notify application.

Processing aborts.

Check log of Operating System.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

The operating environment such as the status of the connection definition file and the connection method specification is abnormal.

Processing will be aborted.

Confirm that the operating environment such as the status of the connection definition file and the connection method specification is normal.

Could not open file.

Processing aborts.

Check log of Operating System.

Could not open pid file.

Processing aborts.

Check log of Operating System.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

Could not prepare for heartbeat.

Processing aborts.

Check log of Operating System.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

The operating environment such as the status of the connection definition file and the connection method specification is abnormal.

Processing will be aborted.

Confirm that the operating environment such as the status of the connection definition file and the connection method specification is normal.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

Could not read from pid file.

Processing aborts.

Check log of Operating System.

There was insufficient free space in the disk of the database server during execution of the application.

Processing will be aborted.

Delete user data stored in the database server to free up space on the disk.

The operating environment such as the status of the connection definition file and the connection method specification is abnormal.

Processing will be aborted.

Confirm that the operating environment such as the status of the connection definition file and the connection method specification is normal.

There was insufficient free space in the disk of the database server during execution of the application.

Processing will be aborted.

Delete user data stored in the database server to free up space on the disk.

Could not receive a heartbeat packet.

Processing aborts.

Check log of Operating System.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

Could not remove pid file.

Processing aborts.

Check log of Operating System.

Could not reply all application info.

Processing aborts.

Check log of Operating System.

Could not reply all node info.

Processing aborts.

Check log of Operating System.

Could not reply for startup.

Processing aborts.

Check log of Operating System.

Could not reply target node info.

Processing aborts.

Check log of Operating System.

Could not resolve address.

Processing aborts.

Check log of Operating System.

Supplementary information was output.

None.

Refer to this message together with the message that was output immediately beforehand.

Could not seek pid file.

Processing aborts.

Check log of Operating System.

Could not send.

Processing aborts.

Check log of Operating System.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

Could not send signal to conmgr process

Processing aborts.

Check log of Operating System.

Could not send signal to conmgr process.

Processing aborts.

Check log of Operating System.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

Could not start conmgr process due to setsid() failure.

Processing aborts.

Check log of Operating System.

Could not start conmgr process in time.

Processing aborts.

Check log of conmgr process.

Could not start conmgr process.

Processing aborts.

Check log of Operating System.

Could not start conmgr process.

Processing aborts.

Check log of conmgr process.

There was insufficient free space in the disk of the database server during execution of the application.

Processing will be aborted.

Delete user data stored in the database server to free up space on the disk.

Could not stop conmgr process in time.

Processing aborts.

Check log of conmgr process.

Could not sync to pid file.

Processing aborts.

Check log of Operating System.

Supplementary information was output.

None.

Refer to this message together with the message that was output immediately beforehand.

An error occurred while translating domain name to Kerberos realm name in SSL.

Processing will be aborted.

Check the message text and confirm that the domain name is written correctly.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

There was insufficient free space in the disk of the database server during execution of the application.

Processing will be aborted.

Delete user data stored in the database server to free up space on the disk.

There was insufficient free space in the disk of the database server during execution of the application.

Processing will be aborted.

Delete user data stored in the database server to free up space on the disk.

There was insufficient free space in the disk of the database server during execution of the application.

Processing will be aborted.

Delete user data stored in the database server to free up space on the disk.

There was insufficient free space in the disk of the database server during execution of the application.

Processing will be aborted.

Delete user data stored in the database server to free up space on the disk.

There was insufficient free space in the disk of the database server during execution of the application.

Processing will be aborted.

Delete user data stored in the database server to free up space on the disk.

There was insufficient free space in the disk of the database server during execution of the application.

Processing will be aborted.

Delete user data stored in the database server to free up space on the disk.

Could not write pid file.

Processing aborts.

Check log of Operating System.

There was insufficient free space in the disk of the database server during execution of the application.

Processing will be aborted.

Delete user data stored in the database server to free up space on the disk.

There was insufficient free space in the disk of the database server during execution of the application.

Processing will be aborted.

Delete user data stored in the database server to free up space on the disk.

There was insufficient free space in the disk of the database server during execution of the application.

Processing will be aborted.

Delete user data stored in the database server to free up space on the disk.

There was insufficient free space in the disk of the database server during execution of the application.

Processing will be aborted.

Delete user data stored in the database server to free up space on the disk.

There are the following cases:

- failed to write transaction log file

- failed to write transaction log file on backup data storage destination

Processing will be aborted.

Lack of storage space or malfunction of storage allocating the file shown in this message is considered.

If it's ture, recover the database system accoring to "Actions when an Error Occurs" of "Operation Guide" or "Cluster Operation Guide (Database Multiplexing)".

If it's not true, identify the cause according to the informations in this message such as errno, and work around.

The following major causes are considered.

- the file has no permission or the permission has been changed

- power of the storage allocating the file has been turned off

- unmounted the storage allocating the file

- another process or human operated the file

- the storage allocating the file has crashed

Could not write to pid file.

Processing aborts.

Check log of Operating System.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

Either backend_host or backend_hostaddr is needed for instance.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

Ending log output to stderr.

Continues processing.

Future log output will be output to the log destination.

Error is occured for completion of asynchronous connect for heartbeat.

Processing aborts.

Check log of Operating System.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

Execution of conmgr by a user with administrative permissions is not permitted. The conmgr must be started under an unprivileged user ID to prevent possible system security compromises. See the documentation for more information on how to properly start the conmgr.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

Failed to add new prepared transaction.

Processing will be aborted.

Please refer to the server log, and determine the cause of the error.

Could not delete the row in pgx_loader_state table.

Processing will be aborted.

Please refer to the server log, and determine the cause of the error.

Could not execute SPI.

Processing will be aborted.

Please refer to the server log, and determine the cause of the error.

Failed to fetch the id column.

Processing will be aborted.

Please refer to the server log, and determine the cause of the error.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

Failed to update the state column.

Processing will be aborted.

Please refer to the server log, and determine the cause of the error.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

Heartbeat connect is refused.

Processing aborts.

Check log of remote system.

Heartbeat connect is timed out.

Processing aborts.

Check log of remote system.

Heartbeat connection is established.

Processing continues.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

Heartbeat is timed out.

Processing aborts.

Check log of remote system.

The operating environment such as the status of the connection definition file and the connection method specification is abnormal.

Processing will be aborted.

Confirm that the operating environment such as the status of the connection definition file and the connection method specification is normal.

The operating environment such as the status of the connection definition file and the connection method specification is abnormal.

Processing will be aborted.

Confirm that the operating environment such as the status of the connection definition file and the connection method specification is normal.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

Increase watchdog.max_hb_connections.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

The operating environment such as the status of the connection definition file and the connection method specification is abnormal.

Processing will be aborted.

Confirm that the operating environment such as the status of the connection definition file and the connection method specification is normal.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

Invalid parameter in configuration file.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

Invalid pid file.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

invalid record length was found on archive log or transaction log data.

The following causes could be considered.

- if the log level is information(INFO, NOTICE, LOG, DEBUG)

Continue processing.

- if the log level is error(ERROR, FATAL, PANIC)

Processing will be aborted.

If the log level is information(INFO, NOTICE, LOG, DEBUG), no action is required.

When the log level is error(ERROR, FATAL, PANIC), take either of the following actions.

- if this message is output during starting instance

Please restore according to "Deal at the time of abnormality" of "Operation Guide" or "Cluster Operation Guide (Database Multiplexing)".

- if this message is output during recovering

Cannot continue to recover with the current backup data because an archive log in the backup has an error.

Recover from the other backup data.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

Invalid timeout specified.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

Invalid value for integer parameter in configuration file.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

Invalid value for parameter.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

Invalid value for parameter in configuration file.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

Invalid value for parameter of instance.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

keystore-passphrase command line option and PGX_KEYSTORE_PASSPHRASE environment variable should not be set when using TDE_z extension.

Processing will be aborted.

Remove keystore-passphrase from command line option or unset PGX_KEYSTORE_PASSPHRASE environment variable before starting the server with TDE_z extension loaded.

Lack of max_prepared_transactions.

Processing will be aborted.

Please increase max_prepared_transactions.

A group data item contains the 77 level variable.

Precompling will be aborted.

Remove the variable from the group data item.

77 level variable is used in the TYPEDEF statement.

Precompling will be aborted.

Change the level number.

There was insufficient free space in the disk of the database server during execution of the application.

Processing will be aborted.

Delete user data stored in the database server to free up space on the disk.

The operating environment such as the status of the connection definition file and the connection method specification is abnormal.

Processing will be aborted.

Confirm that the operating environment such as the status of the connection definition file and the connection method specification is normal.

Listening on port.

Processing continues.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

Logical replication target relation uses some of the system columns to identify rows which are updated or deleted.

Processing will be aborted.

Usage of system columns for REPLICA IDENTITY should be avoided as these data vary across databases.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

Materialize mode required, but it is not allowed in this context.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

Lack of max_prepared_transactions.

Processing will be aborted.

Please increase max_prepared_transactions.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

The operating environment such as the status of the connection definition file and the connection method specification is abnormal.

Processing will be aborted.

Confirm that the operating environment such as the status of the connection definition file and the connection method specification is normal.

The operating environment such as the status of the connection definition file and the connection method specification is abnormal.

Processing will be aborted.

Confirm that the operating environment such as the status of the connection definition file and the connection method specification is normal.

No cmdata directory specified and environment variable CMDATA unset.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

No connection manager directory is specified and environment variable CMDATA is unset.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

There was insufficient free space in the disk of the database server during execution of the application.

Processing will be aborted.

Delete user data stored in the database server to free up space on the disk.

No operation mode is specified.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

The operating environment such as the status of the connection definition file and the connection method specification is abnormal.

Processing will be aborted.

Confirm that the operating environment such as the status of the connection definition file and the connection method specification is normal.

The operating environment such as the status of the connection definition file and the connection method specification is abnormal.

Processing will be aborted.

Confirm that the operating environment such as the status of the connection definition file and the connection method specification is normal.

There was insufficient free space in the server's memory during execution of the application.

Processing will be aborted.

Estimate memory usage and take the following action:

- If the number of simultaneous connections from client applications is high, reduce it.

- If the number of simultaneous SQL executions is high, reduce it.

There was insufficient free space in the server's memory during execution of the application.

Processing will be aborted.

Estimate memory usage and take the following action:

- If the number of simultaneous connections from client applications is high, reduce it.

- If the number of simultaneous SQL executions is high, reduce it.

There was insufficient free space in the database server's shared memory during execution of the application.

Processing will be aborted.

Estimate memory usage and take the following action:

- If the number of simultaneous connections from client applications is high, reduce it.

- If the number of simultaneous SQL executions is high, reduce it.

The number of workers must not be negative.

Processing will be aborted.

Please specify more than one.

Terminated normally but a warning was output.

Continues processing.

Close open transactions with multixacts soon to avoid wraparound problems.

one of -d/--dbname and -f/--file must be specified

Processing will be aborted.

Check the command-line, and re-execute the command with correct options.

There was insufficient free space in the server's memory during execution of the application.

Processing will be aborted.

Estimate memory usage and take the following action:

- If the number of simultaneous connections from client applications is high, reduce it.

- If the number of simultaneous SQL executions is high, reduce it.

There was insufficient free space in the client's memory during execution of the application.

Processing will be aborted.

Estimate memory usage and take the following action:

- Modify the application to reduce memory usage.

There was insufficient free space in the client's memory during execution of the application.

Processing will be aborted.

Estimate memory usage and take the following action:

- Modify the application to reduce memory usage.

There was insufficient free space in the server's memory during execution of the application.

Processing will be aborted.

Estimate memory usage and take the following action:

- If the number of simultaneous connections from client applications is high, reduce it.

- If the number of simultaneous SQL executions is high, reduce it.

There was insufficient free space in the database server's shared memory during execution of the application.

Processing will be aborted.

Estimate memory usage and take the following action:

- If the number of simultaneous connections from client applications is high, reduce it.

- If the number of simultaneous SQL executions is high, reduce it.

pgx_global_metacache must be set to at least 10MB when enabled.

Processing will be aborted.

Set the pgx_global_metacache parameter to at least 10MB and restart the database.

pgx_loader can be available only COPY FROM command.

Processing will be aborted.

Please specify COPY FROM statement.

Pid file does not exist.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

An error occurred during execution of the application or command.

Processing will be aborted.

Reduce the value of maintenance_work_mem.

postmaster exited during a parallel loading.

Processing will be aborted.

Please refer to the server log, and determine the cause of the error.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

The operating environment such as the status of the connection definition file and the connection method specification is abnormal.

Processing will be aborted.

Confirm that the operating environment such as the status of the connection definition file and the connection method specification is normal.

The operating environment such as the status of the connection definition file and the connection method specification is abnormal.

Processing will be aborted.

Confirm that the operating environment such as the status of the connection definition file and the connection method specification is normal.

The operating environment such as the status of the connection definition file and the connection method specification is abnormal.

Processing will be aborted.

Confirm that the operating environment such as the status of the connection definition file and the connection method specification is normal.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred during execution of the application or command.

Processing will be aborted.

To disable the policy for the table owner, use ALTER TABLE NO FORCE ROW LEVEL SECURITY.

Real and effective user IDs must match.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

An error occurred while translating domain name to Kerberos realm name in SSL.

Processing will be aborted.

Check the message text and confirm that the domain name is written correctly.

Received fast shutdown request.

Processing continues.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

Received immediate shutdown request.

Processing continues.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

Received invalid startup packet.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

Received smart shutdown request.

Processing continues.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

Rejected a connection from application due to going shutdown.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

Remote node closes heartbeat connection.

Processing aborts.

Check log of remote system.

Remote node shuts down heartbeat connection.

Processing aborts.

Check log of remote system.

An error occurred due to unexpected directory entry found at specific path

Cancels processing.

Remove those unexpected directories, or set allow_in_place_tablespaces to ON transiently to let recovery complete.

The backup data may be corrupted.

Processing will be aborted.

Copy the backup data to the backup storage directory from backup media.

Supplementary information was output.

None.

Refer to this message together with the message that was output immediately beforehand.

An error occurred during DB Server processing in the database.

Processing will be aborted.

Refer to this message together with the message that was output immediately beforehand.

The operating environment such as the status of the connection definition file and the connection method specification is abnormal.

Processing will be aborted.

Confirm that the operating environment such as the status of the connection definition file and the connection method specification is normal.

Supplementary information was output.

None.

Refer to this message together with the message that was output immediately beforehand.

Supplementary information was output.

None.

Refer to this message together with the message that was output immediately beforehand.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

The operating environment such as the status of the connection definition file and the connection method specification is abnormal.

Processing will be aborted.

Confirm that the operating environment such as the status of the connection definition file and the connection method specification is normal.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

The operating environment such as the status of the connection definition file and the connection method specification is abnormal.

Processing will be aborted.

Confirm that the operating environment such as the status of the connection definition file and the connection method specification is normal.

Set-valued function called in context that cannot accept a set.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

Sleep until another process releases global meta cache because global meta cache cannot be swept away yet. Please increase pgx_global_metacache.

Processing continues.

If this message occurs frequently, increase the pgx_global_metacache parameter setting and restart the database.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

The depth of the execution stack exceeded the allowable value during execution of the application.

Processing will be aborted.

If executing a complex SQL, modify it to a simple SQL.

An error occurred during DB Server processing in the database.

Processing will be aborted.

Refer to this message together with the message that was output immediately beforehand.

Started conmgr process successfully.

Continues processing.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

Starting conmgr process.

Continues processing.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

Stopped conmgr process successfully.

Continues processing.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

Supplementary information was output.

None.

Refer to this message together with the message that was output immediately beforehand.

An error occurred during execution of the application or command.

Processing will be aborted.

The string may have unclosed double quotation marks.

An error occurred during execution of the application or command.

Processing will be aborted.

Check the value of synchronous_standby_names, which may come from postgresql.conf or the SQL command line.

The operating environment such as the status of the connection definition file and the connection method specification is abnormal.

Processing will be aborted.

Confirm that the operating environment such as the status of the connection definition file and the connection method specification is normal.

Syntax error in configuration file.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

The operating environment such as the status of the connection definition file and the connection method specification is abnormal.

Processing will be aborted.

Confirm that the operating environment such as the status of the connection definition file and the connection method specification is normal.

The TDE_h extension cannot be dynamically loaded by the user.

Processing will be aborted.

In postgresql.conf specify shared_preload_libraries = 'tde_h'

The PKCS11 function call failed.

Processing will be aborted.

The specified value in the PKCS11 configuration file (grep11client.yaml) or the TDE_h execution environment is incorrect, or the HPCS is detecting an error. Check the message and take appropriate action according to the reported PKCS11 error code. Also, if you have specified a log in the PKCS11 configuration file, check the output log and take action.

The call to the C_OpenSession function of PKCS11 has failed.

Processing will be aborted.

Check the message text and take appropriate action based on the reported PKCS11 error code.

During encryption or decryption processing TDE_h was not able to find an expected PKCS11 key.

Processing will be aborted.

The keystore and the PKCS11 token key objects are not consistent with each other. This may happen if the keystore and/or PKCS11 token directory have been incorrectly copied (or not copied at all). Check all files have been copied correctly.

The TDE_h extension cannot be dynamically loaded by the user.

Processing will be aborted.

In postgresql.conf specify shared_preload_libraries = 'tde_h'

The PKCS11 API key associated with the token of Slot ID was not defined at load time.

This is only a warning message when TDE_h is loaded.

The token API key must be known to tde_h before secure keys can be used. Specify the API key at load time with --api-key option, or by GUC tde_h.API_KEY in postgresql.conf. Or, specify the API key at run-time using SELECT pgx_open_keystore(API Key); or SELECT pgx_set_master_key(API Key);

The PKCS11 Slot ID for transparent data encryption is not defined.

Processing will be aborted.

In postgresql.conf set the GUC tded_h.SLOT_ID to the PKCS11 Slot ID configured for transparent data encryption.

The specified Slot ID does not support a mechanism required by TDE_h.

Processing will be aborted.

Specify a different token which supports the necessary mechanism.

The specified Slot ID does not support a mechanism required by TDE_h.

Processing will be aborted.

Specify a different token which supports the necessary mechanism.

The call to the C_OpenSession function of PKCS11 has failed.

Processing will be aborted.

Check the message text and take appropriate action based on the reported PKCS11 error code.

The specified Slot ID does not support a mechanism required by TDE_h.

Processing will be aborted.

Specify a different token which supports the necessary mechanism.

The specified Slot ID does not support a mechanism required by TDE_h.

Processing will be aborted.

Specify a different token which supports the necessary mechanism.

The specified Slot ID does not support a mechanism required by TDE_h.

Processing will be aborted.

Specify a different token which supports the necessary mechanism.

The PKCS11 token model at the specified Slot ID is not suported by TDE_h.

Processing will be aborted.

Only "EP11" and "CCA" tokens are supported.

Logs the PKCS11 Slot ID and token model that TDE_h will be using.

This is an information messaage when TDE_h is loaded.

No action is required. Confirm the Slot and token type are as expected.

Failed to initialize execution environment for TDE_h.

Processing will be aborted.

The specified value in the PKCS11 configuration file (grep11client.yaml) or the TDE_h execution environment is incorrect, or the HPCS is detecting an error. Check the message and take appropriate action according to the reported PKCS11 error code. Also, if you have specified a log in the PKCS11 configuration file, check the output log and take action.

The call to the C_Initalize function of PKCS11 has failed.

Processing will be aborted.

The specified value in the PKCS11 configuration file (grep11client.yaml) or the TDE_h execution environment is incorrect, or the HPCS is detecting an error. Check the message and take appropriate action according to the reported PKCS11 error code. Also, if you have specified a log in the PKCS11 configuration file, check the output log and take action.

The TDE_z extension cannot be dynamically loaded by the user.

Processing will be aborted.

In postgresql.conf specify shared_preload_libraries = 'TDE_z'

The TDE_z extension cannot be dynamically loaded by the user.

Processing will be aborted.

In postgresql.conf specify shared_preload_libraries = 'TDE_z'

The call to the C_OpenSession function of PKCS#11 has failed.

Processing will be aborted.

Check the message text and take appropriate action based on the reported PKCS#11 error code.

During encryption or decryption processing TDE_z was not able to find an expected opencryptoki key.

Processing will be aborted.

The keystore and the opencryptoki token key objects are not consistent with each other. This may happen if the keystore and/or opencryptoki token directory have been incorrectly copied (or not copied at all). Check all files have been copied correctly.

The opencryptoki Slot ID for transparent data encryption is not defined.

Processing will be aborted.

In postgresql.conf set the GUC TDE_z.SLOT_ID to the opencryptoki Slot ID configured for transparent data encryption.

The opencryptoki User PIN associated with the token of Slot ID was not defined at load time.

This is only a warning message when TDE_z is loaded.

The token User PIN must be known to TDE_z before secure keys can be used. Specify the User PIN at load time with --user-pin option, or by GUC TDE_z.USER_PIN in postgresql.conf. Or, specify the User PIN at run-time using SELECT pgx_open_keystore(user pin); or SELECT pgx_set_master_key(user pin);

The specified Slot ID does not support a mechanism required by TDE_z.

Processing will be aborted.

Specify a different token which supports the necessary mechanism.

The specified Slot ID does not support a mechanism required by TDE_z.

Processing will be aborted.

Specify a different token which supports the necessary mechanism.

The call to the C_OpenSession function of PKCS#11 has failed.

Processing will be aborted.

Check the message text and take appropriate action based on the reported PKCS#11 error code.

The specified Slot ID does not support a mechanism required by TDE_z.

Processing will be aborted.

Specify a different token which supports the necessary mechanism.

The specified Slot ID does not support a mechanism required by TDE_z.

Processing will be aborted.

Specify a different token which supports the necessary mechanism.

The specified Slot ID does not support a mechanism required by TDE_z.

Processing will be aborted.

Specify a different token which supports the necessary mechanism.

The opencryptoki token model at the specified Slot ID is not supported by TDE_z.

Processing will be aborted.

Only "EP11" and "CCA" tokens are supported.

Logs the opencryptoki Slot ID and token model that TDE_z will be using.

This is an information messaage when TDE_z is loaded.

No action is required. Confirm the Slot and token type are as expected.

The call to the C_Initalize function of PKCS#11 has failed.

Processing will be aborted.

Check the message text and take appropriate action based on the reported PKCS#11 error code.

The TDE type specified in shared_preload_libraries in postgresql.conf does not match the keystore format of the execution environment.

Processing will be aborted.

Inconsistent value specified for shared_preload_libraries in keystore and postgresql.conf. Determine which is correct and take appropriate action.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

Timeout occurred during execution of the application.

Processing will be aborted.

Check the following:

- If executing SQL that outputs a large volume of search results, add a conditional expression to filter the results further.

- If numerous SQLs are being simultaneously executed, reduce the number of simultaneously executed SQLs.

- If a large volume of data is to be updated in a single transaction, modify the SQL to reduce the volume of data to be updated in a single transaction.

- If executing a complex SQL, modify it to a simple SQL.

- Check if there are any problems in the network.

- Before conducting maintenance that involves the processing of a large volume of data, use the SET statement to temporarily increase the value of maintenance_work_mem.

An error occurred during execution of the application or command.

Processing will be aborted.

Check the message text and confirm that the server is still running.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

Could not prepare statement.

Processing aborts.

Check messages near this message.

Terminated connections.

Processing continues.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

The database system is shutting down.

Processing will be aborted.

This message is output when the stopping process is operating normally. Retry any necessary applications or commands after restarting the database system.

The database system is starting up.

Processing will be aborted.

This message is output when the startup process or recovery process is operating normally. Restart any necessary the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

A required program was not found. Check your installation.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

The program was not the same version.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

value of sslservercertcn is different from common name in the server certificate.

Processing is aborted.

Set SSL certificate's common name to sslservercertcn.

Timeout occurred during execution of the application.

Processing will be aborted.

Check the following:

- If executing SQL that outputs a large volume of search results, add a conditional expression to filter the results further.

- If numerous SQLs are being simultaneously executed, reduce the number of simultaneously executed SQLs.

- If a large volume of data is to be updated in a single transaction, modify the SQL to reduce the volume of data to be updated in a single transaction.

- If executing a complex SQL, modify it to a simple SQL.

- Check if there are any problems in the network.

- Before conducting maintenance that involves the processing of a large volume of data, use the SET statement to temporarily increase the value of maintenance_work_mem.

Too long literal in configuration file.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

Up to max_worker_processes background worker can be registered with the current settings.

Processing will be aborted.

Consider increasing the value of configuration parameter max_worker_processes.

Too many command-line arguments.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

An error occurred during execution of the application or command.

Processing will be aborted.

Check the message text and confirm that the items in the GROUPING SET are less than the maximum allowable value.

An error occurred while translating account name to Kerberos user name in SSL.

Processing will be aborted.

Check the message text and confirm that the account name is written correctly.

Trigger created with DO block cannot be replaced by EXECUTE PROCEDURE.

Processing is aborted.

Please redefine it after deleting the trigger.

Trigger created with EXECUTE PROCEDURE cannot be replaced by DO block.

Processing is aborted.

Please redefine it after deleting the trigger.

An error occurred during execution of the application or command.

Continues processing.

Check the message text and confirm that functions are not marked as volatile.

An error occurred during execution of the application or command.

Continues processing.

Check the message text and confirm that functions are not marked as volatile.

An error occurred during execution of the application or command.

Continues processing.

Check the message text and confirm that functions are not marked as volatile.

An error occurred during execution of the application or command.

Continues processing.

Check the message text and confirm that functions are not marked as volatile.

An error occurred during execution of the application or command.

Continues processing.

Check the message text and confirm that functions are not marked as volatile.

An error occurred during execution of the application or command.

Continues processing.

Check the message text and confirm that functions are not marked as volatile.

Unexpected directory entry found at specific path while recovery.

Cancels processing.

Remove those unexpected directories, or set allow_in_place_tablespaces to ON transiently to let recovery complete.

An error occurred because execution is temporarily impossible.

Processing will be aborted.

Restart the application. If the same error occurs when you restart the application, to check if there are any problems in the database server.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

Supplementary information was output.

None.

Refer to this message together with the message that was output immediately beforehand.

Unrecognized operation mode was specified.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

Unrecognized stop mode was specified.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

Unrecognized value specified for option '-i'.

Processing aborts.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

The operating environment such as the status of the connection definition file and the connection method specification is abnormal.

Processing will be aborted.

Confirm that the operating environment such as the status of the connection definition file and the connection method specification is normal.

Supplementary information was output.

None.

Refer to this message together with the message that was output immediately beforehand.

Supplementary information was output.

None.

Refer to this message together with the message that was output immediately beforehand.

Supplementary information was output.

None.

Refer to this message together with the message that was output immediately beforehand.

Supplementary information was output.

None.

Refer to this message together with the message that was output immediately beforehand.

Waiting conmgr process to connect to watchdog.

Continues processing.

Recheck command line, configuration file, or logic of your application. Hint message may follow with this message.

Could not accept heartbeat connection.

Processing aborts.

Check messages near this message.

Could not send attribute.

Processing aborts.

Check messages near this message.

You might need to increase max_worker_processes.

Processing will be aborted.

You might need to increase max_worker_processes

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during execution of the application or command.

Processing will be aborted.

Check the message text and confirm that the application is written correctly and the command is being used correctly.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

Timeout occurred during execution of the application.

Processing will be aborted.

Check the following:

- If executing SQL that outputs a large volume of search results, add a conditional expression to filter the results further.

- If numerous SQLs are being simultaneously executed, reduce the number of simultaneously executed SQLs.

- If a large volume of data is to be updated in a single transaction, modify the SQL to reduce the volume of data to be updated in a single transaction.

- If executing a complex SQL, modify it to a simple SQL.

- Check if there are any problems in the network.

- Before conducting maintenance that involves the processing of a large volume of data, use the SET statement to temporarily increase the value of maintenance_work_mem.

The operating environment such as the status of the connection definition file and the connection method specification is abnormal.

Processing will be aborted.

Confirm that the operating environment such as the status of the connection definition file and the connection method specification is normal.

Could not find a suitable target server.

Processing is aborted.

Check following settings (host, IP address, port number,or targetServer):

- Connection string

- Connection service file

- Data source of JDBC or ODBC

- Environment variables for default connection parameter values(ex. PGHOST)

- Arguments of functions of libpq

- Options of command

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

An error occurred during execution of the application or command.

Processing will be aborted.

Check the message text and confirm that the application is written correctly and the command is being used correctly.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

The operating environment such as the status of the connection definition file and the connection method specification is abnormal.

Processing will be aborted.

Confirm that the operating environment such as the status of the connection definition file and the connection method specification is normal.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

The operating environment such as the status of the connection definition file and the connection method specification is abnormal.

Processing will be aborted.

Confirm that the operating environment such as the status of the connection definition file and the connection method specification is normal.

value of targetserver is invalid.

Processing is aborted.

Set one of the following:

- primary

- standby

- prefer_standby

- any(can be specified only JDBC)

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

The operating environment such as the status of the connection definition file and the connection method specification is abnormal.

Processing will be aborted.

Confirm that the operating environment such as the status of the connection definition file and the connection method specification is normal.

An error occurred during execution of the application or command.

Processing will be aborted.

Check the message text and confirm that the application is written correctly and the command is being used correctly.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

There was insufficient free space in the server's memory during execution of the application.

Processing will be aborted.

Estimate memory usage and take the following action:

- If the number of simultaneous connections from client applications is high, reduce it.

- If the number of simultaneous SQL executions is high, reduce it.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

value of sslservercertcn is different from common name in the server certificate.

Processing is aborted.

- Set SSL certificate's common name to sslservercertcn.

- Check the program of class specified by hostnameverifier.

The operating environment such as the status of the connection definition file and the connection method specification is abnormal.

Processing will be aborted.

Confirm that the operating environment such as the status of the connection definition file and the connection method specification is normal.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

An error occurred during communication between the application and the database server.

Processing will be aborted.

Check if there are any problems in the network, eliminate the cause of any error and re-execute the command.

The database server was disconnected during execution of the application.

Processing will be aborted.

Communication may have been disconnected for the following reasons:

- An error occurred in the communication line (TCP/IP etc.)

- The database server terminated abnormally.

Take the following actions:

- Eliminate the cause of the communication disconnection.

Examine the application and check whether the transaction for implementing update is a long transaction. Judge whether it is a long transaction from the following viewpoints and modify the application.

a) If the COMMIT process is not executed after update, add the COMMIT process.

b) If the total number of update records in a single transaction is high, split it into short transactions.

c) If search was conducted for a long period of time after update, execute COMMIT after update or review the search SQL statement.

- If none of the above situations applies, perform the following:

a) Confirm that the database server has not stopped.

b) If the database server is starting or stopping, re-execute the command after the database server starts.

An error occurred during execution of the application or command.

Processing will be aborted.

Check the message text and confirm that the application is written correctly and the command is being used correctly.