KFAA31898-E

aa....aa cannot be performed for reason bb....bb.

               aa....aa: Process in which an error occurred

                        The definition SQL cannot be executed: Execution of a definition SQL statement

                        The retrieval SQL cannot be executed: Execution of a retrieval SQL statement

                        The update SQL cannot be executed: Execution of an update SQL statement

                        The CONNECT statement cannot be executed: Execution of a CONNECT statement

                        The command cannot be executed: Execution of a command

                        The transaction cannot be started: Start of transaction

               bb....bb:

                  Cause of the error

               cc....cc:

                  Connection ID

               S:

                  Ignores this SQL statement.

               Action:

                  Take one of the following corrective actions based on the cause of the error that is output:

                                 Cause of the error (bb....bb)

                                 Error description

                                 Corrective action

                                 SQLSTATE

                                 A command that cannot be executed at the same time as other commands or applications is currently being executed

                                 A command is running that cannot be executed concurrently with another command or application.

                                 After the executing command has terminated, re-execute this command.

                                 08608

                                 The HADB server operation mode is "OFFLINE"

                                 The CONNECT statement cannot be executed because the HADB server is in offline mode.

                                 Change the HADB server operation mode to normal, and then re-execute the SQL statement.

                                 08609

                                 A connection is being established directly on a slave node

                                 The CONNECT statement cannot be executed because a direct connection is being established to the HADB server for the slave node.

                                 Change the application's connection target to the alias IP address that indicates the master node, and then re-execute the SQL statement.

                                 0860A

                                 An attempt to connect to the port for communication between HADB servers is in progress

                                 The CONNECT statement cannot be executed because an attempt to establish a connection to an HADB server-dedicated communication port is in progress.

                                 In adb_clt_rpc_srv_port in the client definition, specify the port number specified by the server definition's adb_rpc_port operand, and then re-execute the SQL statement.

                                 0860B

                                 The HADB client or command belongs to a client group whose maximum number of concurrent connections is zero

                                 A connection to the HADB server cannot be established because the client or command belongs to a client group or command group whose maximum number of concurrent connections is zero.

                                 Take one of the following corrective actions. Then, re-execute the SQL statement or command.

                                       Action 1

                                          For the adb_clt_group_name operand in the client definition, specify a group name for which a value other than 0 is specified for the -m option of the adbcltgrp operand in the server definition.

                                       Action 2

                                          In the server definition, revise the value of the adbcltgrp operand's -m option corresponding to the group name specified for the adb_clt_group_name operand in the client definition.

                                 This error also occurs if, in the server definition, the sum of the values specified for -u options of the adbcltgrp operands equals the value of the adb_sys_max_users operand. In this case, revise the value specified for each -u option of the adbcltgrp operand.

                                 0860D

                                 The HADB server operation mode is "MAINTENANCE"

                                 The CONNECT statement cannot be executed because the HADB server operation mode is maintenance mode.

                                 Change the HADB server operation mode to normal, and then re-execute the CONNECT statement.

                                 0860E

                                 A command cannot be executed because the HADB server operation mode is maintenance mode.

                                 Change the HADB server operation mode to normal, and then re-execute the command.

                                 None

                                 The HADB client execution environment is invalid

                                 The CONNECT statement cannot be executed because the HADB client execution environment is invalid.

                                 Take the corrective action given for the error message that was output preceding this message.

                                 08623

                                 SQL is already being executed on the same connection

                                 An SQL statement is already executing on the connection.

                                 Wait for the SQL statement executing on the connection to finish, and then re-execute this SQL statement.

                                 54013

                                 The read-only transaction is already being executed on the HADB server in the multi-node configuration

                                 Transactions cannot be started because a read-only transaction is being executed on an HADB server in a multi-node configuration.

                                 Execute the SQL statement or command again after all read-only transactions being performed are completed on an HADB server in a multi-node configuration.

                                 54014 or None

                                 The read/write transaction or the command is already being executed on the HADB server in the multi-node configuration

                                 Transactions cannot be started because a read/write transaction or command is being executed on an HADB server in a multi-node configuration.

                                 Execute the SQL statement again after all read/write transactions and commands being performed are completed on an HADB server in a multi-node configuration.

                                 54016

                                 The HADB server operation mode is "QUIESCENCE"

                                 An update SQL statement or definition SQL statement cannot be executed because the HADB server operation mode is quiescence mode.

                                 Change the HADB server operation mode to normal, and then re-execute the SQL statement.

                                 54018

                                 A command cannot be executed because the HADB server operation mode is quiescence mode.

                                 Change the HADB server operation mode to normal, and then re-execute the command.

                                 None

                                 An attempt to access a DB area that is being accessed by an update SQL statement in a different transaction while another retrieval SQL statement is being executed in the same transaction

                                 If the multi-node function is used, the retrieval SQL statements that satisfy all the following conditions cannot be executed:

                                       An attempt is made to concurrently execute retrieval SQL statements by using multiple statement handles in the same transaction.

                                       A retrieval SQL statement is accessing the data DB area.

                                       Another retrieval SQL statement attempts to access the data DB area being accessed by an update SQL statement (this retrieval SQL statement results in an error).

                                 For details about the conditions in which an error occurs, see Nodes on which SQL statements are executed in Nodes on which transactions and commands are executed in the HADB Setup and Operation Guide.

                                 Take one of the following corrective actions:

                                       Action 1

                                          Wait for termination of the running retrieval SQL statement in condition 2 on the left.

                                       Action 2

                                          Wait for termination of the transaction that uses the update SQL statement in condition 3 on the left.

                                 Then, re-execute the SQL statement that resulted in an error.

                                 54020

                                 The command was executed on a slave node

                                 This command cannot be executed on a slave node.

                                 Re-execute the command on a master node.

                                 None

Cause of the error (bb....bb)	Error description	Corrective action	SQLSTATE
`A` `command` `that` `cannot` `be` `executed` `at` `the` `same` `time` `as` `other` `commands` `or` `applications` `is` `currently` `being` `executed`	A command is running that cannot be executed concurrently with another command or application.	After the executing command has terminated, re-execute this command.	`08608`
`The` `HADB` `server` `operation` `mode` `is` `"OFFLINE"`	The `CONNECT` statement cannot be executed because the HADB server is in offline mode.	Change the HADB server operation mode to normal, and then re-execute the SQL statement.	`08609`
`A` `connection` `is` `being` `established` `directly` `on` `a` `slave` `node`	The `CONNECT` statement cannot be executed because a direct connection is being established to the HADB server for the slave node.	Change the application's connection target to the alias IP address that indicates the master node, and then re-execute the SQL statement.	`0860A`
`An` `attempt` `to` `connect` `to` `the` `port` `for` `communication` `between` `HADB` `servers` `is` `in` `progress`	The `CONNECT` statement cannot be executed because an attempt to establish a connection to an HADB server-dedicated communication port is in progress.	In `adb_clt_rpc_srv_port` in the client definition, specify the port number specified by the server definition's `adb_rpc_port` operand, and then re-execute the SQL statement.	`0860B`
`The` `HADB` `client` `or` `command` `belongs` `to` `a` `client` `group` `whose` `maximum` `number` `of` `concurrent` `connections` `is` `zero`	A connection to the HADB server cannot be established because the client or command belongs to a client group or command group whose maximum number of concurrent connections is zero.	Take one of the following corrective actions. Then, re-execute the SQL statement or command. Action 1 For the `adb_clt_group_name` operand in the client definition, specify a group name for which a value other than `0` is specified for the `-m` option of the `adbcltgrp` operand in the server definition. Action 2 In the server definition, revise the value of the `adbcltgrp` operand's `-m` option corresponding to the group name specified for the `adb_clt_group_name` operand in the client definition. This error also occurs if, in the server definition, the sum of the values specified for `-u` options of the `adbcltgrp` operands equals the value of the `adb_sys_max_users` operand. In this case, revise the value specified for each `-u` option of the `adbcltgrp` operand.	`0860D`
`The` `HADB` `server` `operation` `mode` `is` `"MAINTENANCE"`	The `CONNECT` statement cannot be executed because the HADB server operation mode is maintenance mode.	Change the HADB server operation mode to normal, and then re-execute the `CONNECT` statement.	`0860E`
	A command cannot be executed because the HADB server operation mode is maintenance mode.	Change the HADB server operation mode to normal, and then re-execute the command.	`None`
`The` `HADB` `client` `execution` `environment` `is` `invalid`	The `CONNECT` statement cannot be executed because the HADB client execution environment is invalid.	Take the corrective action given for the error message that was output preceding this message.	`08623`
`SQL` `is` `already` `being` `executed` `on` `the` `same` `connection`	An SQL statement is already executing on the connection.	Wait for the SQL statement executing on the connection to finish, and then re-execute this SQL statement.	`54013`
`The read-only transaction is already being executed on the HADB server in the multi-node configuration`	Transactions cannot be started because a read-only transaction is being executed on an HADB server in a multi-node configuration.	Execute the SQL statement or command again after all read-only transactions being performed are completed on an HADB server in a multi-node configuration.	`54014` or `None`
`The read/write transaction or the command is already being executed on the HADB server in the multi-node configuration`	Transactions cannot be started because a read/write transaction or command is being executed on an HADB server in a multi-node configuration.	Execute the SQL statement again after all read/write transactions and commands being performed are completed on an HADB server in a multi-node configuration.	`54016`
`The` `HADB` `server` `operation` `mode` `is` `"QUIESCENCE"`	An update SQL statement or definition SQL statement cannot be executed because the HADB server operation mode is quiescence mode.	Change the HADB server operation mode to normal, and then re-execute the SQL statement.	`54018`
	A command cannot be executed because the HADB server operation mode is quiescence mode.	Change the HADB server operation mode to normal, and then re-execute the command.	`None`
`An` `attempt` `to` `access` `a` `DB` `area` `that` `is` `being` `accessed` `by` `an` `update` `SQL` `statement` `in` `a` `different` `transaction` `while` `another` `retrieval` `SQL` `statement` `is` `being` `executed` `in` `the` `same` `transaction`	If the multi-node function is used, the retrieval SQL statements that satisfy all the following conditions cannot be executed: An attempt is made to concurrently execute retrieval SQL statements by using multiple statement handles in the same transaction. A retrieval SQL statement is accessing the data DB area. Another retrieval SQL statement attempts to access the data DB area being accessed by an update SQL statement (this retrieval SQL statement results in an error). For details about the conditions in which an error occurs, see Nodes on which SQL statements are executed in Nodes on which transactions and commands are executed in the HADB Setup and Operation Guide.	Take one of the following corrective actions: Action 1 Wait for termination of the running retrieval SQL statement in condition 2 on the left. Action 2 Wait for termination of the transaction that uses the update SQL statement in condition 3 on the left. Then, re-execute the SQL statement that resulted in an error.	`54020`
`The` `command` `was` `executed` `on` `a` `slave` `node`	This command cannot be executed on a slave node.	Re-execute the command on a master node.	`None`