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

• The retrieval SQL applying SQL parallel execution cannot be executed: Execution of a retrieval SQL statement with SQL parallel execution function applied

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 command cannot be executed because the HADB server operation mode is offline mode.	Change the HADB server operation mode to normal, and then re-execute the command. However, for the adbupddmk command, change the HADB server operation mode to maintenance mode, and then re-execute the command.	None
A connection is being established directly on a secondary node	The CONNECT statement cannot be executed because a direct connection is being established to the HADB server for the secondary node.	Change the application's connection target to the alias IP address that indicates the primary node, and then re-execute the SQL statement.	0860A
A connection is being established directly on a worker node	The CONNECT statement cannot be executed because a direct connection is being established to the HADB server for the worker node.	Take one of the following corrective actions. Then, re-execute the SQL statement. Multi-node configuration with HA Monitor Change the application program's connection target to the alias IP address that indicates the primary node. Multi-node configuration without HA Monitor Change the application program's connection target to the IP address of the primary node.	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
		Wait for the SQL statement executing on the connection to finish, and then re-execute this retrieval SQL statement with SQL parallel execution function applied.	54025
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. However, for the adbupddmk command, change the HADB server operation mode to maintenance mode, 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 number of concurrent SQL parallel executions exceeded the maximum number	Because the number of concurrent executions of the SQL parallel execution function applied to the retrieval SQL statement has exceeded the maximum number of concurrent executions specified in the server definition adb_sys_max_parallel_exec_num operand, no more SQL parallel execution function applied to the retrieval SQL statement can be executed.	Re-execute the retrieval SQL statement with the SQL parallel execution function after the other retrieval SQL statements with the SQL parallel execution function have been completed.	54024
The retrieval SQL is already being executed as part of SQL parallel execution on the same connection	The SQL statement cannot be executed because a retrieval SQL statement that has already applied the SQL parallel execution function is being executed on the same connection.	Wait for the SQL statement executing on the connection to finish, and then re-execute this retrieval SQL statement with SQL parallel execution function applied.	54025
No SQL sub node could be allocated	Because none of the SQL sub nodes could be allocated, the SQL parallel execution function cannot be applied to the retrieval SQL statement.	The following describes the causes of why not a single SQL sub node could be allocated and the corrective action to take. The specified values of the operands in the server definition do not match When using the SQL parallel execution function, there are server definition operands whose specified values must match at each node. Check that the specified values of the operands in the server definitions for each node match. If there are nodes with different specified values for the server definition operands, terminate the HADB server and set the specified values for the server definition operands to be the same. After that, start the HADB server and then re-execute the retrieval SQL statement with the SQL parallel execution function applied. For details about the server definition operands that require the specification value at each node to match, see Preparatory Work When Using the SQL Parallel Execution Function in Specifying the Server Definition in the HADB Setup and Operation Guide. There is no node in the multi-node configuration that can become an SQL sub node Check for deleted worker nodes or disconnected secondary nodes. Add a worker node that can become a SQL sub node or return the secondary node and then re-execute the retrieval SQL statement with the SQL parallel execution function applied. There is no room in the processing thread to execute SQL statements on each node After the execution of the SQL statement or command being executed on each node is completed, re-execute the retrieval SQL statement with the SQL parallel execution function applied. Alternatively, you can terminate the multi-node configuration HADB server and specify a value for the server definition adb_sys_rthd_num operand that is greater than or equal to "adb_sys_max_users-operand-specified-value × adb_sql_exe_max_rthd_num-operand-specified-value". After that, start the multi-node configuration HADB server and re-execute the retrieval SQL statement with the SQL parallel execution function applied.	54026
A read/write transaction or specific command is being executed on the primary node	Cannot execute the retrieval SQL statement that uses the SQL parallel execution function because a read/write transaction or a specific command is being executed on the primary node.	Re-execute the retrieval SQL statement with the SQL parallel execution function applied after the read/write transaction or command that is running on the primary node has completed.	54027
The command was executed on a secondary node	This command cannot be executed on a secondary node.	Re-execute the command on a primary node.	None
The command was executed on a worker node	This command cannot be executed on a worker node.	Re-execute the command on a primary node.	None
A node other than the primary node is running	The command cannot be executed because a node other than the primary node is activated.	Terminate the HADB server on the secondary node and worker node, and then re-execute the command.	None
The HADB server operation mode is "NORMAL"	A command cannot be executed because the HADB server operation mode is normal mode.	Change the HADB server operation mode to maintenance mode, and then re-execute the command.	None
Other command or AP is currently being executed	Reorganization of the dictionary table by using the adbreorgsystemdata command cannot be executed because other commands or applications are running.	Re-execute the reorganization of the dictionary table by using the adbreorgsystemdata command after other commands or applications have finished.	None