Previous Contents Index Next |
Sun Java System Application Server Standard and Enterprise Edition 7 2004Q2 Error Messages Reference

> ## Chapter 11
> High-Availability Database

> This chapter lists error messages that originate from the HADB.

> ##

> HADB

> ##### HADB00000

> Description | Operation completed successfully.
> Action | None.

> ##### HADB00208

> Description | An operation within the current transaction failed and the transaction was aborted.
> Action | Retry the transaction.

> ##### HADB00216

> Description | A request to abort transaction arrived. An error occurred on one of the processing nodes, that caused the transaction to abort.
> Action | Retry the transaction.

> ##### HADB00224

> Description | The operation timed out. The transaction controller did not receive a reply on time, from one or more of the participating nodes.
> Action | The possible reasons for this could be: Lock contention High load Node is inactive Lack of resources for executing the operation.

> ##### HADB00208

> Description | The transaction was aborted.
> Action | Look in the SQL Guide for your database to get an explanation, and retry the transaction.

> ##### HADB00216

> Description | An error occurred on one of the processing nodes, that caused the transaction to rollback.
> Action | Retry the transaction.

> ##### HADB00224

> Description | SQL operation timed out. .
> Action | Look in the SQL Guide for your database to get an explanation.

> ##### HADB00512

> Description | When starting or restarting a node, the Node Supervisor (NUSP) attempted to start a process, but there are indications that this process is already running. The most common occurrence of this is that the UDP port assigned to the process is occupied.
> Action | Check the offending computer for processes that own the UDP port. If the process that cannot be started is running, stop it manually.

> ##### HADB00560

> Description | Illegal internet address format. Error when connecting to the network address of a server process. This may be caused by an invalid network address or non-existing hostname.
> Action | Verify that the network addresses being used when creating a database exists.

> ##### HADB00582

> Description | Failed to free message information object. This is an internal consistency message. The process attempted to free a pool of objects for information about communication messages, but there are allocated objects in the pool.
> Action | If this message occurs during shutdown of a node or database, it can be ignored. Otherwise, Analyze the System, as described on (more...) .

> ##### HADB00583

> Description | Out of Message Descriptor objects for sending messages. This error may occur when a server process attempts to allocate more than 100000 message descriptors.
> Action | Analyze the System, as described on (more...) .. It is very unlikely that a process will allocate this many message descriptors during normal operation.

> ##### HADB00584

> Description | Failed to free Message Descriptor object. Internal consistency message. The process attempted to free a pool of descriptor objects for communication messages, but there are allocated objects in the pool.
> Action | If this message occurs during shutdown of a node or database, it can be ignored. Otherwise, Analyze the System, as described on (more...) ..

> ##### HADB00624

> Description | Too many ports used. Server process has exhausted its pool of network port objects. This is typically caused by the server process attempting to create too many network connections over a short period of time. This occurs when a large number of SQL client connections arrives almost simultaneously.
> Action | Try to decrease the arrival rate of SQL client connections, or distribute the load over more database nodes. If this is not possible, Analyze the System, as described on (more...) ..

> ##### HADB00832

> Description | Message out of sequence with respect to the current state has been received by a server or client process.
> Action | Spurious errors can be safely ignored. If numerous errors occur during a short interval, Analyze the System, as described on (more...) ..

> ##### HADB00848

> Description | This message is reported when you attempt to run server processes belonging to different versions of HADB software to support one database. Client programs running a software version different from the server versions is usually safe, unless specified in the release notes.
> Action | Upgrade all server software for a database to run the same software version.

> ##### HADB00916

> Description | This is an internal message that is used to synchronize internal processing of SQL commands. Due to some unresolved error, this error message will occasionally be sent to an application client, instead of a more specific user error. This problem will be resolved in future releases of HADB.
> Action | Retry the operation.

> ##### HADB01040

> Description | This error may occur when an application attempts to retrieve data from a table while the table is being refragmented.
> Action | Rollback the transaction and retry.

> ##### HADB01521

> Description | No space left on the device. The database was unable to allocate more space on a storage device.
> Action | Check the available device space on the offending database node and determine the device that lacks space. Reclaim free space on the device, if possible. If you determine that you need to upgrade the node with more storage space, follow the procedure documented in the Administrator’s Guide. Note that because most HADB instances are configured so that storage space is allocated evenly and distributed over the nodes, it is likely that other nodes will report the same error.

> ##### HADB01536

> Severity |
> Description | Unknown error during asynchronous operation. Attempting to read data from or write data to a file failed. An operating system specific error code is usually also displayed in an adjacent message. A normal reason is damaged storage devices.
> Action | Replace damaged storage devices, if any. Follow procedures in the Administrator’s Guide in order to reconstruct missing configurations and data.

> ##### HADB01552

> Description | Too many active transaction objects allocated at this node. Each active session may have an active transaction object. In addition, the transaction controller keeps a number of objects corresponding to transactions that have committed but not yet terminated due to incomplete slave cleanup work.
> Action | Increase the maximum number of sessions allowed per node. This will also cause a corresponding increase in the number of available transaction objects.

> ##### HADB01600

> Description | Log buffer full. This error may occur if the tuple log buffer or node-internal log buffer is too small for the applied load. When this occurs, the history files should contain information messages containing the text "HIGH LOAD" that gives a more precise description of the resource problem.
> Action | Refer to the Troubleshooting Guide for information on how to tune the system to avoid resource problems.

> ##### HADB01616

> Description | This error may occur during repair or refragmentation operation if the node has a regular node that fills the log faster than the repair/refragmentation operation can process. You are likely to see HIGH LOAD messages in the history files, meaning that the internal resource control attempts to reduce the regular node.
> Action | It this happens during a refragmentation operation, retry the operations, preferably at a time with less regular database load. If this happens during a repair, the repair is automatically retried. If the repair fails repeatedly, Analyze the System, as described on (more...) ..

> ##### HADB01664

> Description | No checkpoint log record found. The node recovery procedure failed because it was unable to find a valid checkpoint in either the node-internal log or the tuple log on that node. This may happen if the node fails very early after it started.
> Action | No action to be taken. The node supervisor catches this error and automatically initiates a repair from the mirror node.

> ##### HADB01696

> Description | Too many replicas. The pool of replica descriptors on the processing node has been exhausted. Generally, the maximum number of replicas can be calculated as the sum of replicas for each table in the database. For a table, the number of replicas is two multiplied by the number of nodes the table is fragmented over. The maximum number of replicas is currently fixed to 8800. Note that the required number of replicas increases when new nodes are added to a database.
> Action | Remove unused tables from the database. If the error occurs again, Analyze the System, as described on (more...) ..

> ##### HADB01920

> Description | Inconsistent B-tree. This error indicates an inconsistency in one of the table fragments stored at the node.
> Action | This error usually causes the node to abort, which eventually causes a repair of all data from the mirror node. Hence, no action is usually required.

> ##### HADB02000

> Description | Requested fragment not found. No replicas were found for some of the fragments of a table. This indicates a pair node failure, and disaster recovery is probably needed.
> Action | See the Administrator’s Guide for information on how to recover from session data corruption.

> ##### HADB02016

> Description | No replicas were found for one or more of the fragments of a table. This indicates a pair node failure, and disaster recovery is probably needed.
> Action | See the Administrator’s Guide for information on how to recover from session data corruption.

> ##### HADB02064

> Description | One fragment replica has changed the role during operation, probably from primary to hot-standby. This may occur when the mirror node is restarted during the operation, reclaiming the primary replica of the fragment. The transaction is rolled back.
> Action | Retry the transaction.

> ##### HADB02078

> Description | Wrong dictionary version number. The dictionary version that the client views is too old compared to the current global dictionary. This can be a problem for long transactions when other clients perform repeated dictionary-changing operations.
> Action | Rollback the current transaction and retry.

> ##### HADB02079

> Description | Version limit test failed. Version check performed on computing slave detected a transient mismatch between the global state of the dictionary and the state of a fragment at that particular slave. This may happen in rare circumstances when applying modifications to a table or creating or dropping indexes for a table.
> Action | Rollback the current transaction and retry.

> ##### HADB02080

> Description | Too many locks set, out of request objects.
> Action | Increase the maximum number of concurrent locks by modifying the hadbm variable, NumberOfLocks. Modify the application so that it sets fewer concurrent locks. For example, split a session into more transactions, or by reduce the transaction isolation level from Repeatable Read to Read Committed.

> ##### HADB02096

> Description | Too many locks held concurrently.
> Action | Increase the maximum number of concurrent locks by modifying the hadbm variable, NumberOfLocks. Modify the application so that it sets fewer concurrent locks. For example, split a session into more transactions, or by reduce the transaction isolation level from Repeatable Read to Read Committed.

> ##### HADB02097

> Description | Upgrade from shared to exclusive lock failed. An update to a record failed because the updating transaction was not the only transaction holding a shared lock on the record.
> Action | Rollback the transaction and retry. In severe cases, you may try to run conflicting applications at different times of day, or reprogram applications so that they access and lock data so that no lock upgrades are required.

> ##### HADB02168

> Description | Execution terminated at slave involved in takeover. Transaction failed because a node takeover operation has occurred during transaction execution. A node takeover operation means that one or more replicas at one of the involved node changed role from primary to hot-standby, or vice versa. This error may also occur if a transaction is attempting to access a table that is being refragmented by another transaction. The transaction is automatically rolled back.
> Action | Retry the transaction.

> ##### HADB02272

> Description | Too many clients. Attempted to start too many database sessions at this transaction controller.
> Action | Try to connect to another transaction controller (you may have to replace the connect string), or increase the size of the hadbm variable, NumberOfSessions.

> ##### HADB02304

> Description | Session has been disconnected. The transaction controller has decided to assign the session object that was allocated to your session, to another client. A session object may be reused if there is no activity within 60 seconds, and another client requests a new database session.
> Action | The immediate action should be to reconnect with the database and retry the transaction. If this problem occurs often, you should increase the size of the hadbm variable, NumberOfSessions.

> ##### HADB02320

> Description | TCON does not accept clients.The database node has not completed initial start or restart.
> Action | Wait a short while and retry to connect to the database. If this situation persists, the offending database node has entered an invalid state. Manually restarting the node using hadbm restartnode may help to resolve the problem.

> ##### HADB02464

> Description | Amnesia. The process has run out of virtual or physical memory. This is similar to the error, HADB04096.
> Action | Increase the available memory by adding swap size or more physical memory to the computer. You may also decrease the memory consumption on the computer by moving services to another computer or decreasing the sizes of the memory buffers, for example, DataBufferPoolSize or LogbufferSize.

> ##### HADB03072

> Description | Bad or missing server address or key. This error indicates that a HADB utility program has failed when connecting to the database. The HADB utility programs use the hadbm configuration file when deciding the parameters used to connect to the database. If this file is inconsistent with respect to the configuration files stored at each database node.
> Action | Make sure that the configuration files used by hadbm and those stored at the database nodes are identical. In particular, make sure that the value for the variable clientkey are equal and that all the lines starting with node are equal.

> ##### HADB03104

> Description | Bad slave. This error means that one of the slave nodes involved in the transaction has failed during the transaction execution. The transaction is rolled back.
> Action | Retry the transaction.

> ##### HADB03504

> Description | Node involved in current operation failed. This error means that one of the slave nodes involved in the transaction has failed during the transaction execution. The transaction is rolled back.
> Action | Retry the transaction. You may have to investigate the cause of node failure, in case the node is not automatically restarted. This will probably involve reading history log files on the database node.

> ##### HADB03505

> Description | A relational algebra server process that was involved in the processing of a relational algebra query has failed. This error should be detected by the node supervisor, which will immediately restart a new relational algebra server.
> Action | Retry the operation. If the error persists, Analyze the System, as described on (more...) ..

> ##### HADB03508

> Description | All relational algebra server processes defined for the database have failed, and the request cannot be processed.
> Action | You may retry the operation at a later time, but a more likely action is to investigate why all relational algebra server processes have failed simultaneously. This will probably involve reading history log files on the database nodes, or Analyze the System, as described on (more...) ..

> ##### HADB03840

> Description | No replicas were found for one of the fragments of a table. This indicates a pair node failure, and disaster recovery is probably needed.
> Action | See the Administrator’s Guide for description of how to recover from session data corruption, for possible actions.

> ##### HADB04096

> Description | Out of space. The process has run out of virtual or physical memory. This is similar to error HADB02464.
> Action | Increase the available memory by adding swap size or more physical memory to the computer. You may also decrease the memory consumption on the computer by moving services to another computer or decreasing the sizes of the memory buffers. For example, DataBufferPoolSize or LogbufferSize.

> ##### HADB04362

> Description | Too many tables. The maximum number of tables that can be created in the database dictionary has been reached.
> Action | Increase the value of the hadbm variable, MaxTables, or remove unused existing tables, before retrying the create table operation.

> ##### HADB04576

> Description | Client held transaction open for too long. The transaction controller has rolled back the transaction because it was idle a too long time.
> Action | You can specify a longer transaction idle time from the client. In the JDBC, set the property maxtransidle. In the ODBC, set the ODBC ini string maxtransidle. In Clusql, use the SQL command SET TRANSACTION IDLETIME. A likely cause of this error may be that the previous transaction was not committed.

> ##### HADB04592

> Description | No free blocks on data devices. The data device(s) of one or more nodes involved in the operation has no more free blocks. This is a critical operational error that calls for immediate action.
> Action | You must always locate node(s) having no free blocks. Use the command hadbm deviceinfo and look for nodes that have a low number of free blocks. Note that because HADB tries to spread data evenly across all active nodes, it is likely that all nodes will reach critical storage space situation almost simultaneously. To resolve the problem, try one or more of the following procedures: Reclaim storage space by removing unused tables. Extend existing devices by increasing the value of the hadbm variable TotalDatadeviceSizePerNode. (You need to verify that the disk devices have sufficient free space before executing this procedure).

> ##### HADB04593

> Description | No unreserved blocks on data devices. The data device(s) of one or more nodes involved in the operation has no more unreserved blocks. To a user, this error is similar to error HADB04592. This is a critical operational error that calls for immediate action.
> Action | You must always locate node(s) having no free blocks. Use the command hadbm deviceinfo and look for nodes that have a low number of free blocks. Note that because HADB tries to spread data evenly across all active nodes, it is likely that all nodes will reach critical storage space situation almost simultaneously. To resolve the problem, try one or more of the following procedures: Reclaim storage space by removing unused tables. Extend existing devices by increasing the value of the hadbm variable TotalDatadeviceSizePerNode. (You need to verify that the disk devices have sufficient free space before executing this procedure).

> ##### HADB04640

> Description | Refrag table requires all nodes to be up and running. A refragmentation requires that all the nodes involved in the operation (both in the old and the new node group) are running.
> Action | Make sure that all nodes are active and retry the operation, or refragment to a set of nodes that are running.

> ##### HADB04656

> Description | A backup or restore operation, or a table creation, deletion or modification operation cannot be started when a backup operation is active inside the database.
> Action | Wait until the current backup operation is finished.

> ##### HADB04672

> Description | A backup or restore operation cannot be started when a restore operation is already active inside the database.
> Action | Wait until the current backup operation is finished.

> ##### HADB04688

> Description | Node-internal log buffer too small. The database node failed to start because the node-internal log buffer is too small.
> Action | Set the size of the node-internal log buffer (hadbm variable InternalLogBufferSize) as outlined in the Administrator’s Guide.

> ##### HADB04752

> Description | Too many fragment replicas at one node. When creating a table, you cannot specify more fragments than the number of nodes it is created over. It is not allowed to create more than one primary fragment per node.
> Action | Reduce the number of fragments in the create table statement so that it is not greater than the number of nodes in the nodegroup.

> ##### HADB04768

> Description | No backup service available at node. The backup or restore operation cannot be started because there is no backup service available at the specified node.
> Action | Start the operation where a backup service is active.

> ##### HADB05500

> Description | An attempt to open or create a file failed. The error message includes the name of the file and an operating system-specific error code. Normal reasons for this error are file not found or permission denied, and these reasons indicate misconfigurations or damaged storage devices.
> Action | A misconfiguration must be resolved by following procedures documented in the Administrator’s Guide, possibly by re-applying the offending command with the correct file name(s).

> ##### HADB05501

> Description | An attempt to close a file failed. The error message includes an operating system-specific error code.
> Action | Analyze the System, as described on (more...) ..

> ##### HADB05502

> Description | An attempt to read a file failed. The error message includes an operating system-specific error code. Normal reasons for this error are damaged storage devices.
> Action | You need to replace possible damaged storage devices. Follow procedures in the Administrator’s Guide to reconstruct missing configurations and data.

> ##### HADB05503

> Description | An attempt to write data to a file failed. The error message includes an operating system-specific error code. Normal reasons for this error are damaged storage devices.
> Action | You need to replace possible damaged storage devices. Follow procedures in the Administrator’s Guide to reconstruct missing configurations and data.

> ##### HADB05504

> Description | A control operation on an open file failed. The error message includes an operating system-specific error code. Possible reasons for this error are unavailable remote storage devices.
> Action | Try to resolve this problem using the operating system documentation. If you are unable to do so, Analyze the System, as described on (more...) .

> ##### HADB05505

> Description | An attempt to execute a file failed. The Node Supervisor (NSUP) attempted to create a new server process, but failed to execute a new program image. The error message includes the name of the file and an operating system-specific error code. The most likely causes for this error are lack of physical or virtual memory or an incorrect path to the executable program.
> Action | Install more physical memory on the computer. Increase the swap space available for the computer. Reduce the load on the computer,such as by moving HADB nodes or other computing services to other computers. Check that the path to the executable program that NSUP tries to start is valid.

> ##### HADB05506

> Description | An attempt to perform an asynchronous operation on a file failed. The error message includes an operating system-specific error code. Normal reasons for this error are damaged storage devices.
> Action | You need to replace possible damaged storage devices. Follow procedures in the Administrator’s Guide to reconstruct missing configurations and data.

> ##### HADB05510

> Description | Creating or getting access to an existing shared memory segment failed. The error message includes an operating system-specific error code. Possible problems include: the segment already exists (if a previous instance was not completely cleaned up, or another application uses the same shared memory key), access problems (also if the segment already exists), lack of memory (that is, there is not sufficient virtual or physical memory to create the segment), or maximum shared memory segment size is configured too small for the requested segment size.
> Action | Make sure that old instances have been properly cleaned up. Make sure that other applications does not use the same shared memory key. Use the command ipcs(1) to list the existing shared memory segments. You may have to define a different shared memory segment key for HADB nodes (see Administrator’s Guide). You may have to add physical or virtual memory to the computer, or move HADB instances to other computers. You may have to increase the maximum shared memory size for the computer (see the Installation Guide).

> ##### HADB05511

> Description | A control operation on a shared memory segment, such as retrieving the size of the segment or removing the segment, failed. The error message includes an operating system-specific error code.
> Action | Consult the operating system documentation for information on how to resolve this problem.

> ##### HADB05512

> Description | Attaching a process to a shared memory segment failed. The error message includes an operating system-specific error code. This error may indicate that there is not enough physical or virtual memory to map the memory segment.
> Action | Consult the operating system documentation for information on how to resolve this problem. You may have to increase the physical memory on the computer, or increase the swap space. You may also work around the problem by reducing the HADB data or log buffer sizes.

> ##### HADB05513

> Description | Detaching a process from a shared memory segment failed. The error message includes an operating system-specific error code. There are no common reasons for this error.
> Action | Consult the operating system documentation for information on how to resolve this problem.

> ##### HADB05514

> Description | A control operation on a shared memory segment failed. The error message includes an operating system-specific error code. There are no common reasons for this error.
> Action | Consult the operating system documentation for information on how to resolve this problem.

> ##### HADB05520

> Description | Creating a semaphore failed. The error message includes an operating system-specific error code. The error code may indicate a lack of semaphore resources or that you tried to create a semaphore that already exists.
> Action | You may have to increase the number of semaphore resources on your computer. Instructions are provided in the Installation Guide. Otherwise, consult the operating system documentation for information on how to resolve this problem.

> ##### HADB05521

> Description | An operation on a semaphore, such as obtaining the status of a semaphore or acquiring or releasing a semaphore, failed. The error message includes an operating system-specific error code. This error code may indicate a lack of semaphore resources.
> Action | You may have to increase the number of semaphore resources on your computer. Instructions are provided in the Installation Guide. Otherwise, consult the operating system documentation for information on how to resolve this problem.

> ##### HADB05522

> Description | Removing a semaphore failed. The error message includes an operating system-specific error code.
> Action | Consult the operating system documentation for information on how to resolve this problem.

> ##### HADB05530

> Description | Creating a socket failed. The operating system error code associated with this error indicates the problem. Most likely this is a resource problem, such as the pool of socket descriptors is full.
> Action | The operating system error code determines the action to take.

> ##### HADB05531

> Description | A control operation on a socket failed. The operating system error code associated with this error indicates the problem.
> Action | The operating system error code determines the action to take.

> ##### HADB05532

> Description | Removing a socket failed. The operating system error code associated with this error indicates the problem.
> Action | The operating system error code determines the action to take.

> ##### HADB05533

> Description | An attempt to receive data on a UDP port failed. The error message displays an operating system-specific error code.
> Action | Check the operating system-specific error code for information about the error.

> ##### HADB05534

> Description | An attempt to send data on a UDP port failed. The error message displays an operating system-specific error code.
> Action | Check the operating system-specific error code for specific information about the error.

> ##### HADB05540

> Description | Creating a message queue failed. The error message displays an operating system-specific error code, which may indicate insufficient message queue resources or you tried to create a message queue with a key that already in use.
> Action | You may have to increase the number of message queue resources on your computer. Instructions are provided in the Installation Guide. Otherwise, consult the operating system documentation for information on how to resolve this problem.

> ##### HADB05541

> Description | Removing a message queue failed. The error message displays an operating system-specific error code.
> Action | Consult the operating system documentation for information on how to resolve this problem.

> ##### HADB05542

> Description | Sending a message to a message queue failed. The error message displays an operating system-specific error code.
> Action | Consult the operating system documentation for information on how to resolve this problem.

> ##### HADB05543

> Description | Receiving a message from a message queue failed. The error message displays an operating system-specific error code.
> Action | Consult the operating system documentation for information on how to resolve this problem.

> ##### HADB05544

> Description | A control operation on a message queue failed. The error message displays an operating system-specific error code.
> Action | Consult the operating system documentation for information on how to resolve this problem.

> ##### HADB05550

> Description | A call to an operating system routine failed. The error message displays the name of the routine as well as the operating system error code.
> Action | Consult the operating system documentation for information on how to resolve this problem.

> ##### HADB05551

> Description | Creating a process failed. The Node Supervisor (NUSP) attempted to create a new server process, but failed to fork a new process. The most likely errors are lack of process slots and lack of physical or virtual memory.
> Action | Increase the number of processes and reboot the system. Install more physical memory on the computer. Increase the swap space available for the computer. Reduce the load on the computer, such as by moving HADB nodes or other computing services to other computers.

> ##### HADB05552

> Description | Looking up the address of an Internet resource specified with Internet address and port number failed. The error message displays an operating system-specific error code.
> Action | Consult the operating system documentation for information on how to resolve this problem.

> ##### HADB05570

> Description | Creating a thread inside a multi-threaded process failed. The error message displays an operating system-specific error code.
> Action | Consult the operating system documentation for information on how to resolve this problem.

> ##### HADB05571

> Description | Destroying a thread inside a multi-threaded process failed. The error message displays an operating system-specific error code.
> Action | Consult the operating system documentation for information on how to resolve this problem.

> ##### HADB05572

> Description | A synchronization operation on a thread inside a multi-threaded process failed. The error message displays an operating system-specific error code.
> Action | Consult the operating system documentation for information on how to resolve this problem.

> ##### HADB05573

> Description | Sending a continuation signal to a thread inside a multi-threaded process failed. The error message displays an operating system-specific error code.
> Action | Consult the operating system documentation for information on how to resolve this problem.

> ##### HADB05580

> Description | Allocating a segment of memory failed. The error message displays an operating system-specific error code.
> Action | You may have to increase the physical memory or swap space associated with the computer.

> ##### HADB11110

> Description | Sequential file is damaged. The sequential file being read is unreadable. This may occur if the file being read is assumed to be a text file but is actually a binary file, if the file has been truncated in the middle of a logical record, and so on.
> Action | The file that you are trying to read is not usable. You need to find the appropriate file or reconstruct the file from other sources.

> ##### HADB11112

> Description | The file or file system containing the relational algebra temporary storage device is full, and no more blocks can be allocated from it. You may move the storage device to a larger disk.
> Action | You must create a larger file for the relational algebra temporary storage device. You may need to allocate a larger storage device, if the currently allocated space is insufficient.

> ##### HADB11304

> Description | Key is too large. The row to be inserted or updated is greater than 8080 bytes.
> Action | If you have control over the database schema, consider to split the offending table in two, or convert some large character or binary columns into CLOB or BLOB columns. If you do not have control over the database schema, consider truncating some of the variable-sized fields in the row, or inform the application provider of this problem.

> ##### HADB11309

> Description | Too many statement handles allocated. The database session attempted to allocate more than 8000 statement handles.
> Action | Make sure that you close the statement handles when they are no longer used.

> ##### HADB11311

> Description | Unique index could not be created. There are duplicate values in columns specified in a CREATE UNIQUE INDEX statement. The index could not be created.
> Action | Remove duplicate values from the table. Create a non-unique index instead of a unique index.

> ##### HADB11320

> Description | Key is too large. The row to be inserted or updated has a primary key that is greater than 1024 bytes, or the secondary key fields of the row (for any secondary index), are greater than 1024 bytes.
> Action | If you have control over the database schema, consider to use a different primary key definition, or remove secondary indexes created over very large columns. If you do not have control over the database schema, consider truncating some of the variable-sized fields in the row, or inform the application provider of this problem.

> ##### HADB11402

> Description | String not terminated. A string must be enclosed in single quotes. A delimited identifier must be enclosed in double quotes. The last quote is missing in the current statement.
> Action | Make sure that the string is terminated with a single quote or double quote character.

> ##### HADB11403

> Description | Illegal special character. The specified character cannot be used in this context. Apart from alphabetic and numeric characters, the following characters are allowed outside of character strings in the SQL syntax: ‘_’, ‘#’, ‘<’, ‘>’, ‘=’, ‘.’, ‘,’, ‘;’, ‘:’, ‘’’, ‘”’, ‘!’, ‘?’, ‘+’, ‘-‘, ‘*’,‘/’, ‘%’, ‘|’, ‘\’, ‘(‘, ‘)’, ‘[‘, ‘]’, space character.
> Action | Make sure that your SQL string contains only valid special characters.

> ##### HADB11404

> Description | Specified string argument is too long. The string argument supplied is longer than 32000 characters.
> Action | Make sure that the string argument is not longer than the limit.

> ##### HADB11405

> Description | String is too long.
> Action | A string specified in the statement is longer than the allowed maximum size. Filenames can be maximum 256 characters wide.

> ##### HADB11406

> Description | Syntax error in symbol specification. A syntactical error was found in the supplied text argument. A hexadecimal constant value was not terminated with a quote character.
> Action | Make sure that the symbol has proper syntax.

> ##### HADB11407

> Description | Non-delimiter token must be followed by a delimiter token or separator. The statement contains two consecutive non-delimiter tokens which must have an intermittent separator, such as a space character or a line break.
> Action | Insert appropriate separators between non-delimiter tokens.

> ##### HADB11521

> Description | Table definition has changed, prepared statement invalid. The SQL server was not able to automatically re-prepare a statement. The layout of one or more tables that are part of the statement has changed, and, when preparing the statement, it was found that the types of columns selected from the tables had changed.
> Action | You must terminate and restart the application.

> ##### HADB11601

> Description | Invalid user password. Login not accepted because user name or password is incorrect.
> Action | Add the missing user name and password to the database, or use the correct user name and password combination.

> ##### HADB11602

> Description | An operation that requires auto commit mode was attempted in the manual commit mode. Operations that require auto commit mode are: create/drop index table refragmentation
> Action | Set the connection to autocommit mode, and retry the operation.

> ##### HADB11608

> Description | Too many users, login rejected The defined maximum number of users are already logged in to the database. Wait some time before trying a new login. Contact the database administrator (DBA) if this situation persists. You may need to increase the configuration file parameter nsessions.
> Action | Reconfigure the HADB to allow more user connections. Ensure that all clients disconnect from the HADB properly before terminating. A client which exits without closing the connection to HADB occupies resources until HADB decides to time-out the connection. The default timeout is 30 minutes of idle time.

> ##### HADB11619

> Description | Too many global table descriptors. Space is exhausted in the shared memory segment used for SQL dictionary cache. The SQL query cannot be prepared or executed. Note that this memory segment is shared between all connections on a given HADB node.
> Action | Change the application(s) to use fewer tables, or increase the size of the dictionary cache.

> ##### HADB11646

> Description | The maximum total line length has been exceeded. The maximum length is 32000 characters. Note that in order to have lines longer than 255 characters, you need to split them up into several lines no longer than 255 characters and terminate the last line with a semicolon.
> Action | Rewrite the SQL query.

> ##### HADB11657

> Description | Reported by clusql if it reaches end-of-file before reading the SQL query termination token “;”. Query will not be prepared or executed.
> Action | Terminate all queries with “;”.

> ##### HADB11662

> Description | Invalid transaction state. An attempt was made to perform an INSERT, UPDATE or DELETE operation on a permanent table, and the current transaction is in read only mode. Also a transaction may be active when the SET TRANSACTION command is executed.
> Action | Set the connection in read-write mode if transactions need to modify the database.

> ##### HADB11666

> Description | This error is reported by clusql if control-c is entered at the SQL: prompt. The application is terminated. Note that queries that have been submitted, cannot be canceled (by control-c or by other means).
> Action | Use quit or exit to terminate clusql.

> ##### HADB11701

> Description | Table not found. No table or view with the given name exists in the database.
> Action | Ensure that current schema is correct, and that the table name is correct.

> ##### HADB11703

> Description | Table type not found. The table type with the specified name does not exist in the database.
> Action | If you have used the create tabletype ... and create table <table name> tabletype <table type>, then verify that the names used are correct. If the problem persists, Analyze the System, as described on (more...) ..

> ##### HADB11704

> Description | Column not found. Column does not exist within the tables, views, or table types specified in the current command.
> Action | Check the spelling of the column names.

> ##### HADB11707

> Description | A table type cannot be altered or dropped because at least one table is using the type.
> Action | Drop tables using the table type.

> ##### HADB11708

> Description | Table name is not recognized as a schema.
> Action | Check the table name. Create the missing schema.

> ##### HADB11709

> Description | Schema is not empty. The schema cannot be dropped because there is at least one table or view in it.
> Action | Drop the contents of the schema before dropping the schema.

> ##### HADB11711

> Description | Table exists already A table or view with the supplied name exists already. Supply a unique name when creating or modifying a table.
> Action | Supply a unique name when creating or modifying a table.

> ##### HADB11713

> Description | Insufficient privilege for attempted operation. Operation cannot be performed with existing user privilege and access rights.
> Action | Grant access rights to the current user, or connect as a different user with appropriate rights.

> ##### HADB11714

> Description | Double declaration in dictionary definition. The definition portion of a Data Dictionary creation or modification command contains a double declaration.
> Action | Each declaration in a dictionary command (such as OWNER) can be specified only once.

> ##### HADB11715

> Description | No table type was specified in a CREATE TABLE command and the table specification does not include a column definition list. A table type name and a column definition list must be specified when creating a table.
> Action | Create the table type first, or create the table with a column definition list.

> ##### HADB11716

> Description | Illegal organization of table. Table must be organized as INDEXED or SEQUENTIAL.
> Action | Table organization must be specified as indexed or sequential. Only indexed tables are supported. Although sequential is accepted it is ignored.

> ##### HADB11717

> Description | Illegal fill level specified. Fill level must be greater than 0% and less than or equal to 100%.
> Action | Fill level must be greater than 0% and less than or equal to 100%.

> ##### HADB11718

> Description | User cannot be owner of resource. A user needs System or Total privilege to become the owner of an index, a table, view, table type, application or nodegroup.
> Action | Grant appropriate access rights, or connect as a different user.

> ##### HADB11721

> Description | Table type exists already. The table type name cannot be used because a table type with this name already exists in the database.
> Action | Supply a unique name when creating or modifying a table type.

> ##### HADB11723

> Description | No primary key specified. A table created with INDEXED organization (implicitly or explicitly) must contain a primary key.
> Action | All tables stored in HADB must have a primary key.

> ##### HADB11725

> Description | Sequence, column, or group cannot be a key. A column of this type cannot be a primary or secondary key column.
> Action | Columns of type decimal or real cannot be indexed. Use other columns as primary or secondary keys.

> ##### HADB11726

> Description | Illegal to add, change or remove key column. A column which is part of the primary key of a table cannot be altered or dropped. It is also illegal to add new columns to the primary key definition. It is, however, legal to rename a key column.
> Action | Drop and recreate the table with the new column definitions.

> ##### HADB11727

> Description | It is illegal to change a column’s basic type, for example, a numeric column cannot be changed into a character column. It is, however legal to change between any data type and the data type byte of the same size, for example, from integer to byte (4) and vice versa. In this case, no actual data conversion is performed.
> Action | The cast function can be used for data conversion in many cases.

> ##### HADB11733

> Description | Column and field names cannot be used twice when declaring the column list of a table type.
> Action | Supply a unique name when creating or modifying a table.

> ##### HADB11734

> Description | Illegal length, precision or scale. The length of CHAR, VARCHAR, BINARY and VARBINARY columns must be greater than 0 and less or equal to 8000 characters (bytes). The precision of a DECIMAL column must be greater than 0 and less than or equal to 31 digits. The scale of a DECIMAL column cannot be greater than the precision. The binary precision of a real column cannot be greater than the implementation-defined maximum precision of a 64 bit floating point datum. (The IEEE standard specifies this as 52). The seconds precision of a TIME or TIMESTAMP column cannot be greater than six. The leading precision and seconds precision of an INTERVAL column cannot be greater than six.
> Action | Rewrite your table definition to comply with the rules described.

> ##### HADB11735

> Description | Illegal data type specified in column definition.
> Action | Use only supported data types in table definitions and in cast/convert queries.

> ##### HADB11736

> Description | Too many columns in key. A primary or secondary key consisting of more than 16 columns cannot be defined.
> Action | Rewrite your table definition.

> ##### HADB11738

> Description | Too many columns. Number of columns within the table type exceeds 255.
> Action | Re-write your table definition.

> ##### HADB11740

> Description | A system table (a table with a table ID less than 1000) cannot be deleted.
> Action | No action to be taken.

> ##### HADB11742

> Description | The specified user name is already defined in the database.
> Action | Supply a unique name when creating or modifying users.

> ##### HADB11743

> Description | The specified user name does not exist in the database.
> Action | Make sure you enter the correct user name.

> ##### HADB11744

> Description | During an attempt to create or modify a user, the user definition contained a syntax error.
> Action | No action to be taken.

> ##### HADB11745

> Description | Attempt to drop system defined user. The system defined user created with the name SYSTEM when a database is initialized cannot be removed from the database.
> Action | No action to be taken.

> ##### HADB11747

> Description | Nodegroup exists already.
> Action | Supply a unique name when creating new node groups.

> ##### HADB11748

> Description | The nodegroup name given cannot be found.
> Action | Ensure that the supplied node group name is correct.

> ##### HADB11751

> Description | The schema could not be created because a schema with the same name exists already.
> Action | Supply a unique name when creating a new schema.

> ##### HADB11755

> Description | No schema with the given name exists in the database.
> Action | Ensure that the schema name is correct.

> ##### HADB11757

> Description | An attempt was made to delete a schema which is essential for operation of the database.
> Action | No action to be taken.

> ##### HADB11759

> Description | When attempting to change the layout of a table, and the change is not cosmetic (for example, rename a column), the table type must be used by this table.
> Action | If several tables use the same table type, you must create a new table type and then convert the table to the new table type with the statement. ALTER TABLE t type = new_type.

> ##### HADB11761

> Description | The specified index does not exist.
> Action | Ensure that current schema is correct, and that the index name is correct.

> ##### HADB11762

> Description | An attempt was made to create an index with a name that already exists.
> Action | Supply a unique name when creating an index.

> ##### HADB11763

> Description | The name of an index is required in this operation. The specified name does not refer to an index.
> Action | Ensure that current schema is correct, and that the index name is correct.

> ##### HADB11768

> Description | An attempt was made to revoke several privileges from a user, but some or all of the privileges could not be revoked. This is probably because not all of the revoked privileges were granted to the user originally.
> Action | Privileges defined for a user can be obtained from DatabaseMetaData.getColumnPrivileges() and DatabaseMetaData.getTablePrivileges() in the JDBC.

> ##### HADB11770

> Description | You do not have the privileges necessary to grant some or all of the specified privileges. Only those privileges that you are granted 'with grant option' have been granted.
> Action | Privileges defined for a user can be obtained from DatabaseMetaData.getColumnPrivileges() and DatabaseMetaData.getTablePrivileges() in the JDBC.

> ##### HADB11773

> Description | The user to whom you granted the privilege(s) has passed them on to another user.
> Action | Use revoke with the cascade clause to revoke the whole chain of privileges that has resulted from your original grant statement.

> ##### HADB11775

> Description | You can specify with check option only when creating a view that can be updated.
> Action | Views involving more than one table cannot be updated in HADB. Note that the with check option is not currently enforced.

> ##### HADB11776

> Description | The specified table, view or column cannot be dropped because there are other views or restrictions that depend on the specified resource.
> Action | Use the cascade option to drop the table, view or column and all dependent views and restrictions.

> ##### HADB11778

> Description | Only one primary key constraint is allowed.
> Action | You can specify the primary key option for only one column, or once with a list of columns specified within parentheses.

> ##### HADB11779

> Description | The specified revoke statement would cause some privileges implicitly granted by a 'create view' statement to be revoked.
> Action | Using revoke with the cascade option will force the privileges to be revoked, and may cause the views to be dropped because they are no longer visible.

> ##### HADB11782

> Description | No view with the given name exists in the database (in the current schema).
> Action | Ensure that current schema is correct, and that the view name is correct.

> ##### HADB11783

> Description | A view with the supplied name exists already.
> Action | Supply a unique name when creating a view.

> ##### HADB11784

> Description | You specified an operation that required a table, but the name that you specified refers to a view or a schema.
> Action | Ensure that the current schema is correct, and that the table name is correct.

> ##### HADB11787

> Description | It is not legal to drop a user who owns schemas, tables or table types.
> Action | Drop the entities owned by the user before dropping the user.

> ##### HADB11790

> Description | Columns of 'interval' data type cannot have default values.
> Action | Rewrite your table definition.

> ##### HADB11796

> Description | An illegal access priority was specified for create table or alter table.
> Action | Use one of the legal values.

> ##### HADB11798

> Description | Too many nodes specified in a create nodegroup statement.
> Action | Do not specify more than the actual number of running nodes.

> ##### HADB11901

> Description | Table is too large for operation. The result of a 'group by' operation is too large to fit in main memory buffers.
> Action | Increase the value of the config variable relalg_workspace_size, and restart clu_relalg_srv on all nodes.

> ##### HADB11903

> Description | Trim character must be a single character. The trim() function was called with a <trim character> string with length different from 1.
> Action | Use a string with a single character.

> ##### HADB11905

> Description | Substring length is negative. The substring() function was called with a <start position> value that was less than 1.
> Action | Rewrite your SQL query.

> ##### HADB11907

> Description | Overflow in string field. A string concatenation, conversion or assignment caused a result string that exceeded the maximum length expected for the target string.
> Action | Rewrite your SQL query, or alter the table(s) involved.

> ##### HADB11908

> Description | Numeric value out of range. An arithmetic operation or a conversion into a numeric data type created a value that was outside the range of the data type of the result of the operation.
> Action | Rewrite your SQL query, or alter the table(s) involved.

> ##### HADB11909

> Description | An attempt to divide a number by zero was made.
> Action | Check your data or rewrite your query so that division by zero cannot occur.

> ##### HADB11910

> Description | Invalid character value for cast. Conversion from a character field to a numeric field failed because an invalid character was found in the character field.
> Action | Check your data.

> ##### HADB11914

> Description | The specified date and time field (date, time or timestamp) was not valid. Possible reason may be because a date field specified a month value greater than 12.
> Action | Check your data.

> ##### HADB11915

> Description | The specified interval field was not valid. Possible reason may be because an interval hour to second field specified a minute or second value greater than 59.
> Action | Check your data.

> ##### HADB11916

> Description | A time zone interval value expression specified in a datetime expression with the at time zone construct, or in a set time zone command, must be greater than or equal to -12:59 and less than or equal to +13:00.
> Action | Check your data or command.

> ##### HADB11917

> Description | A null value was attempted to be assigned to a column that was defined with a Not Null constraint.
> Action | Check your data.

> ##### HADB11918

> Description | A dynamic parameter that was required for the execution of this query was not supplied.
> Action | Check your client application.

> ##### HADB11919

> Description | A conversion to a date, time or timestamp field from a string expression failed because the string expression was not in the correct datetime format. This may occur in a cast expression or when converting from a user-defined character field to a data time field.
> Action | Check your data.

> ##### HADB11920

> Description | A source string was retrieved into a target string that was smaller than the size of the source string. The source string was right truncated so that it fit into the size of the target string.
> Action | Check your data.

> ##### HADB11921

> Description | A set function (count, min, max, sum, avg) was executed and one or more value expressions contained in the set function specification evaluated to NULL and was eliminated before applying the set function.
> Action | Check your data.

> ##### HADB11924

> Description | An SQL query containing a scalar subquery was performed, but the scalar subquery returned more than one row.
> Action | Check your data and/or client application. You need to specify a scalar subquery that returns a maximum of one row.

> ##### HADB11927

> Description | A conversion to an interval field from a string expression failed because the string expression was not in the correct interval format. This may occur in a cast expression or when converting from a user-defined character field to an interval field.
> Action | Check your data.

> ##### HADB11939

> Description | An attempt was made to insert a row with a primary key which already was in use by another row.
> Action | Use unique values for primary keys.

> ##### HADB12001

> Description | HADB was unable to allocate more virtual memory from the operating system.
> Action | Decrease the load on the host(s) where HADB is running. Extend physical and/or virtual memory on the host(s). Use unique values for primary keys.

> ##### HADB12002

> Description | Expressions can be nested up to 256 levels.
> Action | Rewrite your SQL query.

> ##### HADB12003

> Description | Space is exhausted in the shared memory segment used for SQL dictionary cache. The SQL query cannot be prepared or executed. Note that this memory segment is shared between all connections at a given HADB node.
> Action | Change the application(s) to use fewer tables, or increase the size of the dictionary cache.

> ##### HADB12004

> Description | An internal error has occurred while allocating memory.
> Action | Analyze the System, as described on (more...) .

> ##### HADB12005

> Description | An error has occurred while trying to allocate memory from the operating system. An operating system specific error code is usually also displayed in an adjacent message.
> Action | Analyze the System, as described on (more...) .

> ##### HADB12006

> Description | An internal error has occurred while allocating memory.
> Action | Analyze the System, as described on (more...) .

> ##### HADB12301

> Description | Import of table contents from file (bulk load) failed because of inconsistent input data.
> Action | Verify the contents of the input file.

> ##### HADB12302

> Description | Import of table contents from file (bulk load) failed because of inconsistent input data.
> Action | Verify the contents of the input file.

> ##### HADB12303

> Description | Import of table contents from file (bulk load) failed because of inconsistent input data.
> Action | Verify the contents of the input file.

> ##### HADB12304

> Description | Import of table contents from file (bulk load) failed because of inconsistent input data.
> Action | Verify the contents of the input file.

> ##### HADB12305

> Description | Import of table contents from file (bulk load) failed because of inconsistent input data.
> Action | Verify the contents of the input file.

> ##### HADB12306

> Description | Import of table contents from file (bulk load) failed because of inconsistent input data.
> Action | Verify the contents of the input file.

> ##### HADB12307

> Description | Import of table contents from file (bulk load) failed because of inconsistent input data. The bulk load operation was terminated.
> Action | Verify the contents of the input file.

> ##### HADB12317

> Description | The table import/export was successfully completed, with some warnings about data conversion errors.
> Action | Verify the contents of the input/output file.

> ##### HADB12319

> Description | Invalid import or export specification.
> Action | Verify your import/export command.

> ##### HADB12320

> Description | Import of table contents from file (bulk load) failed because of inconsistent input data.
> Action | Verify the contents of the input file.

> ##### HADB12321

> Description | Import of table contents from file (bulk load) failed because of inconsistent input data.
> Action | Verify the contents of the input file.

> ##### HADB12322

> Description | Invalid import or export specification.
> Action | Verify your import/export command.

> ##### HADB12323

> Description | Invalid import or export specification.
> Action | Verify your import/export command.

> ##### HADB12324

> Description | The parameters supplied for a prepared query occupies more than 32000 bytes.
> Action | Rewrite the client application.

> ##### HADB12401

> Description | The operands in this expression do not have compatible data types. Integers cannot be compared with character strings, and so on.
> Action | Sometimes you can get around this problem by using the cast or convert function. For example, a character string that contains all numeric characters can be cast into an integer.

> ##### HADB12402

> Description | The current SQL statement contains a syntax error.
> Action | Verify your SQL statement.

> ##### HADB12403

> Description | The number of values specified in an insert into statement must conform to the number of columns of the table to insert into.
> Action | Verify your SQL statement.

> ##### HADB12404

> Description | An SQL query was submitted in an illegal context, for example in JDBC: statement.executeUpdate("select * from t").
> Action | Verify your client application.

> ##### HADB12406

> Description | The specified column was found in more than one table.
> Action | Prefix the column name with the name of the correct table and a period (.).

> ##### HADB12407

> Description | An expression in an order by list must be a number greater than 0 and less or equal to the number of columns selected, or a valid expression containing columns present in the select list.
> Action | Verify your client application.

> ##### HADB12408

> Description | An aggregate expression is used in the wrong context. For example, select sum(i) from t where sum(i)>0.
> Action | Verify your client application.

> ##### HADB12411

> Description | A subquery is contained in one of the branches of an or clause, or inside the <join specification> of a joined table clause.
> Action | Rewrite your SQL query.

> ##### HADB12412

> Description | The expression is too complex to be evaluated, due to limitations in HADB SQL.
> Action | Rewrite your SQL query.

> ##### HADB12413

> Description | When aggregated expressions are specified in a select statement, the grouping columns are the only individual columns that can be retrieved in the result, in addition to the aggregated expressions.
> Action | Verify your client application.

> ##### HADB12416

> Description | An attempt was made to exceed an implementation defined limit. HADB cannot handle more than 100 users in a single GRANT or REVOKE statement.
> Action | Rewrite your SQL grant/revoke command.

> ##### HADB12422

> Description | The same column name was used more than once when a unique name was required. This can occur inside a view definition, update clause or column alias list.
> Action | Verify your SQL statement.

> ##### HADB12423

> Description | The number of column aliases in an alias list does not match the number of columns in the corresponding table expression.
> Action | Verify your SQL statement.

> ##### HADB12424

> Description | A column that is found in both tables specified in a join expression and is used as a join column cannot be referenced with a table alias prefix. Such a column must be referenced with column name alone, without any table alias.
> Action | Verify your SQL statement.

> ##### HADB12427

> Description | When specifying a table set operation (UNION, INTERSECT or EXCEPT), the select list of both select statements must contain the same number of expressions.
> Action | Verify your SQL statement.

> ##### HADB12428

> Description | When using the CORRESPONDING BY clause in a table set operation, the corresponding column(s) must be part of the select list from both SELECT statements participating in the set operation.
> Action | Verify your SQL statement.

> ##### HADB12430

> Description | When using the CORRESPONDING BY clause in a table set operation, the select lists of the two SELECT statements involved must contain at least one column with the same name.
> Action | Verify your SQL statement.

> ##### HADB12432

> Description | You are attempting to grant or revoke table privileges on a non-table entity, or you are attempting to grant or revoke USAGE privileges on a table entity.
> Action | Verify your SQL statement.

> ##### HADB12433

> Description | You can delete, insert or update rows in a view only if the view can be updated.
> Action | Views involving more than one table cannot be updated in HADB. Verify your SQL statement.

> ##### HADB12434

> Description | When creating a view, a view column list is required if referenced columns have system-generated names. This occurs if referenced column is an expression or if two or more referenced columns have equal names.
> Action | Verify your SQL statement.

> ##### HADB12435

> Description | When using a table subquery as part of a comparison clause, the table subquery must contain the same number of expressions in its select list as there are expressions in the list being compared with.
> Action | Verify your SQL statement.

> ##### HADB12437

> Description | Aggregate functions cannot be nested. For example, it is illegal to specify sum(sum(column)). Aggregate functions cannot contain subqueries or grouped columns.
> Action | Verify your SQL statement.

> ##### HADB12440

> Description | The internal definition of the view that was referenced in your query is corrupt.
> Action | The view must be dropped and recreated.

> ##### HADB12442

> Description | The specified dynamic SQL statement contains an expression involving a dynamic parameter marker whose data type cannot be determined. You are not allowed to specify an expression consisting of a single parameter marker, parameter markers on both sides of a dyadic operator, a parameter marker in a set function argument, and so on.
> Action | Verify your SQL statement.

> ##### HADB12443

> Description | You cannot specify a parameter marker in the SELECT statement part of a CREATE VIEW statement.
> Action | Verify your SQL statement.

> ##### HADB12444

> Description | You cannot create a view that references a temporary table. Only permanent tables and other views can be referenced.
> Action | Verify your SQL statement.

> ##### HADB12445

> Description | Subtracting two DATE, TIME or TIMESTAMP expressions to form an INTERVAL requires the interval type for the result to be specified.
> Action | Verify your SQL statement.

> ##### HADB12446

> Description | System maintained columns (for example, log sequence number: LSN) cannot be updated.
> Action | Verify your SQL statement.

> ##### HADB12447

> Description | DEFAULT values cannot be used inside general expressions.
> Action | Verify your SQL statement.

> ##### HADB12448

> Description | A dynamic SQL statement contains an invalid usage of a parameter. For example, select ? from t.
> Action | Verify your SQL statement.

> ##### HADB12449

> Description | An INSERT INTO may contain a list of values representing rows to be inserted. The rows must be of the same degree, that is have the same number of fields. An example of an illegal statement is, insert into t values (1),(1,2);
> Action | Verify your SQL statement.

> ##### HADB12450

> Description | An 'INSERT INTO' may contain a list of values representing rows to be inserted. The values to be inserted must have the correct number of elements. For example, if table t has a single column, the following statement is illegal. insert into t values(1,2);
> Action | Verify your SQL statement.

> ##### HADB12451

> Description | A NULL value is used in an incorrect way. For example, select NULL from t;
> Action | Verify your SQL statement. A correct example is as follows: select cast(NULL as int) from t;

> ##### HADB12452

> Description | A NULL value is used in an ill-defined manner. For example, insert into temporary.t values(NULL);
> Action | Verify your SQL statement. You can use the cast() construct to specify correct type.

> ##### HADB12454

> Description | An SQL query can reference a maximum of 32 tables, including tables which are included when expanding views.
> Action | Rewrite the SQL query.

> ##### HADB12455

> Description | The expression is too complex to be evaluated, due to limitations in HADB SQL.
> Action | Rewrite the SQL query.

> ##### HADB12456

> Description | The expression is too complex to be evaluated, due to limitations in HADB SQL.
> Action | Rewrite your SQL query.

> ##### HADB12457

> Description | The number of parameters for a dynamic SQL query exceeds 255.
> Action | Rewrite the client application.

> ##### HADB12458

> Description | Due to limitations in HADB SQL, the expression is too complex to be evaluated. The number of statements is limited to 1023. This is relevant for batched SQL statements.
> Action | Rewrite your SQL query.

> ##### HADB12459

> Description | Row value lists are not supported in all expression contexts. An example of an illegal query is as follows: select * from t2 where (i,j) > (0,0)
> Action | Rewrite your SQL query.

> ##### HADB12460

> Description | If columns have been renamed by an alias in a query, the alias names must be used in the select list.
> Action | Rewrite your SQL query.

> ##### HADB12461

> Description | When performing a natural join with the using() construct, the select list cannot qualify the (common) join columns with a table name. This is according to the SQL standard.
> Action | Rewrite your SQL query.

> ##### HADB12522

> Description | You tried to send one receive statement through the client/server interface without establishing a network connection.
> Action | Try to reconnect to the server.

> ##### HADB12523

> Description | The HADB node to which your client tries to connect does not have the necessary capabilities to handle client requests.
> Action | Connect to a different HADB node, or re-try the connection at a later time.

> ##### HADB12528

> Description | The connection has been aborted by HADB. The HADB node to which you were connected has most likely stopped, or has crashed.
> Action | Re-connect to HADB.

> ##### HADB12530

> Description | The client and servers has initiated a connection, but lose contact before a proper connection has been established.
> Action | Re-connect to HADB on a different node.

> ##### HADB12539

> Description | There is a mismatch in the client/server protocol. You are possibly using a new ODBC/JDBC driver to connect to an old version of HADB, or vice versa.
> Action | Change to the driver appropriate for your HADB version.

> ##### HADB20001

> Description | A internal error occurred in the JDBC driver.
> Action | Analyze the System, as described on (more...) .

> ##### HADB20002

> Description | The feature used is optional in the JDBC standard, and is not supported by the HADB.
> Action | User code should be rewritten not to use this feature.

> ##### HADB20003

> Description | The specified transaction isolation level is not supported.
> Action | Use either TRANSACTION_READ_COMMITED, TRANSACTION_READ_UNCOMMITTED or TRANSACTION_REPEATABLE_READ.

> ##### HADB20004

> Description | The JDBC Connection is closed, so no more operations are allowed on it.
> Action | Re-connect to the database.

> ##### HADB20005

> Description | An invalid data type conversion. One typical cause is to use setString(colno, value) on an integer column.
> Action | Check data type and use the correct accessor procedure.

> ##### HADB20006

> Description | Invalid characters were detected in the string.
> Action | Correct the input string.

> ##### HADB20008

> Description | A numeric conversion resulting in an overflow was attempted.
> Action | Check value range and data types.

> ##### HADB20009

> Description | Cursor positioning is not allowed on forward-only cursors.
> Action | Do not use cursor positioning methods.

> ##### HADB20010

> Description | An attempt was made to set a column to a NULL value when the column cannot be set to NULL in the database.
> Action | Either change the database schema to allow null values, or set a non-null value on the column.

> ##### HADB20011

> Description | An attempt was made to retrieve data from a ResultSet and the ResultSet is not positioned on a row.
> Action | When a result set is retrieved for a query, it is positioned before the first row. Use ResultSet.next() to position on the first row.

> ##### HADB20012

> Description | It is not permissible to retrieve values from the result set after it is closed.
> Action | Close the result set after reading from it.

> ##### HADB20013

> Description | An attempt was made to retrieve a column that does not exist in the result set.
> Action | Check column index value.

> ##### HADB20014

> Description | An attempt was made to set a query parameter that does not exist.
> Action | Check query parameter index value.

> ##### HADB20015

> Description | The query returned values with a data type not known to the JDBC driver.
> Action | Analyze the System, as described on (more...) .

> ##### HADB20016

> Description | The column name does not exist in the result set.
> Action | Check the column name.

> ##### HADB20020

> Description | The requested result set type is not supported.
> Action | The result set type may only be TYPE_FORWARD_ONLY: TYPE_SCROLL_INSENSITIVE or TYPE_SCROLL_SENSITIVE.

> ##### HADB20021

> Description | The executeQuery() and executeUpdate() on a PreparedStatement may not accept any parameters.
> Action |

> ##### HADB20022

> Description | The requested result set concurrency level is not supported
> Action | Only CONCUR_READ_ONLY is supported.

> ##### HADB20024

> Description | The executeUpdate() method was used to execute a SELECT-type query.
> Action | Use either the executeQuery() or the execute() method when executing SELECT-type queries.

> ##### HADB20025

> Description | The executeQuery() method was used to execute an INSERT/UPDATE/DELETE-type query.
> Action | Use either executeUpdate() or execute() to execute an INSERT/UPDATE/DELETE-type query.

> ##### HADB20026

> Description | A statement may not include variable parameters.
> Action | Use PreparedStatement when using variable parameters.

> ##### HADB20027

> Description | The parameter to setMaxFieldSize() can not be negative.
> Action | Use a positive value.

> ##### HADB20028

> Description | The parameter to setMaxRows() can not be negative.
> Action | Use a positive value.

> ##### HADB20029

> Description | The time-out value cannot be negative.
> Action | Use a positive value.

> ##### HADB20030

> Description | The statement is closed. No further operations are allowed.
> Action | Do not close the statement until completing it.

> ##### HADB20033

> Description | The date-time format is incorrect, or out of range.
> Action | Check the JDBC documentation for the correct format.

> ##### HADB20034

> Description | The interval value was out of range.
> Action | See the JDBC documentation for information on legal ranges of interval columns.

> ##### HADB20035

> Description | A character used is not allowed in the current character code set.
> Action | Use valid characters.

> ##### HADB20036

> Description | Only FETCH_FORWARD is allowed as fetch direction on a TYPE_FORWARD_ONLY result set.
> Action | Use FETCH_FORWARD as the fetch direction.

> ##### HADB20037

> Description | The fetch size value may not be a negative value.
> Action | Use a positive value for the fetch size.

> ##### HADB20038

> Description | The suggested fetch direction is not allowed.
> Action | See the JDBC documentation for information on allowed values.

> ##### HADB20039

> Description | The fetch size must be less or equal to the value set using setMaxRows().
> Action | Use a lower value.

> ##### HADB20040

> Description | The PreparedStatement does not have any parameters, so any call to setXXX() fails.
> Action | Do not call setXXX() methods in a PreparedStatement with no parameters.

> ##### HADB20041

> Description | The PreparedStatement has one or more parameters that need to be set before calling executeQuery/executeUpdate, since they access columns that may not be NULL.
> Action | Set all parameters that access non-NULL columns.

> ##### HADB20043

> Description | The requested server information item array was not found.
> Action | Analyze the System, as described on (more...) .

> ##### HADB20044

> Description | A user name is required to log on to the database.
> Action | Provide a user name

> ##### HADB20045

> Description | A user password is required to log on to the database.
> Action | Provide a password.

> ##### HADB20046

> Description | None of the hosts in the connection URL could be found. This is usually due to misspelling or problems with the Domain Name Service (DNS).
> Action | Check host names and the DNS setup.

> ##### HADB20050

> Description | The executeUpdate() or executeQuery() was used to execute batched statements.
> Action | Use executeBatch() to execute batched statements.

> ##### HADB20051

> Description | None of the hosts in the connection URL could be found. This is usually due to misspelling or problems with the Domain Name Service (DNS).
> Action | Check host names and the DNS setup.

> ##### HADB20052

> Description | The requested hold is not supported.
> Action | Only CLOSE_CURSORS_AT_COMMIT is supported.

> ##### HADB20053

> Description | SQL save points are not supported in this version of HADB.
> Action | Rewrite code so that use of savepoints are not required.

> ##### HADB20054

> Description | The LOB table specified in the LOB descriptor does not exist in this schema.
> Action | Check if the right database schema is used.

> ##### HADB20055

> Description | Batched statements are not allowed in LOB queries.
> Action | Execute each query by itself.

> ##### HADB20056

> Description | The requested data type conversion is not allowed on a BLOB/CLOB column.
> Action | See the conversion table in the JDBC documentation for conversions that are allowed.

> ##### HADB20057

> Description | The requested operation is not supported when operating on LOBs.
> Action | See the Administrator’s Guide for information on operations that are allowed.

> ##### HADB20059

> Description | An internal inconsistency has occurred.
> Action | Analyze the System, as described on (more...) .

> ##### HADB20060

> Description | The connection is in an invalid state for executing LOB operations.
> Action | The transaction isolation level must be REPEATABLE_READ or higher, and the auto commit mode must be set to OFF.

> ##### HADB20061

> Description | Only SELECT-type queries are allowed when using executeQuery().
> Action | Use executeUpdate to execute INSERT/UPDATE/DELETE-type queries and DML updates.

> ##### HADB20062

> Description | The executeUpdate may not be used for SELECT-type operations.
> Action | Use executeQuery() to execute SELECT-type queries.

> ##### HADB22002

> Description | Database specified does not exist.
> Action | Retry the command with appropriate parameters

> ##### HADB22003

> Description | Node number specified does not exist.
> Action | Retry the command with appropriate parameters.

> ##### HADB22005

> Description | Invalid password.
> Action | Retry the command with appropriate parameters

> ##### HADB22125

> Description | An exception propagated from mgt API or cladm.
> Action | Check the exception code mapped in the message. Example 1: "Internal Error: [ Cladm command failed : CLADM-E-27:failed to start database". In this case, the history files must be analyzed to find the reason the system could not start the database. Example 2: Internal Error: [ "localhost" not allowed in the host list (21042) ] Do not use localhost in the hostlist

> ##### HADB22021

> Description | This error message was generated by the create command. A database with the specified name already exists.
> Action | Create a database with another name.

> ##### HADB22022

> Description | This error message was generated by the create/add nodes command. Specified path does not exist on a host.
> Action | Create the path on the host, or specify another path.

> ##### HADB22023

> Description | This error message was generated by the create/addnodes command. Specified path on a host does not have Write permissions.
> Action | Provide Write permission to the path, or specify another path.

> ##### HADB22024

> Description | This error message was generated by the create/addnodes command. Specified hosts are not reachable.
> Action | Verify that the host can be reached by pinging the host. Verify the ssh/rsh setup.

> ##### HADB22025

> Description | This error message was generated by the create/addnodes command. Length of host list must be greater than one and should be even.
> Action | Retry the command with appropriate parameters.

> ##### HADB22026

> Description | This error message was generated by the create command. Specified database name is not valid.
> Action | Retry the command with appropriate parameters.

> ##### HADB22027

> Description | This error message was generated by the create command. Port base number is not valid or is already in use.
> Action | Make sure no other HADB instance/program uses the port. Retry the command with appropriate parameters

> ##### HADB22028

> Description | This error message was generated by the create command. Specified number of data devices cannot be supported.
> Action | Retry the command with appropriate parameters

> ##### HADB22029

> Description | This error message was generated by the create command. Specified device size cannot be supported.
> Action | Retry the command with appropriate parameters

> ##### HADB22030

> Description | This error message was generated by the create/addnodes command. Specified number of spares could not be allocated.
> Action | Retry the command with appropriate parameters

> ##### HADB22031

> Description | This error message was generated by the create/set command. Attributes that are to be set are not recognized: [ {0} ].
> Action | Retry the command with appropriate parameters.

> ##### HADB22032

> Description | This error message was generated by the create/clear command. Password string is invalid. It should have a minimum length of eight.
> Action | Retry the command with appropriate parameters.

> ##### HADB22033

> Description | This error message was generated by the create command. Invalid values have been set for attributes. Following are the attributes which have been specified with invalid values: [ {0} ]
> Action | Retry the command with appropriate parameters.

> ##### HADB22034

> Description | This error message was generated by the create/addnodes command. Invalid directory specified for inetd setup files.
> Action | Retry the command with appropriate parameters.

> ##### HADB22041

> Description | This error message was generated by the addnodes command. Database has to be in HAFaultTolerant or FaultTolerant states.
> Action | Start the database, or start the nodes which are not running before running the addnodes command. In case of double node failure (mirror nodes), stop and delete the hadb instance and recreate it after including the new nodes.

> ##### HADB22201

> Description | This error message was generated by the addnodes command. Database was not refragmented.
> Action | Refragment the database with the refragment command.

> ##### HADB22042

> Description | This error message was generated by the addnodes/refragment command. Database could not be refragmented.
> Action | Make sure there is enough disk space for refragment. If there is not enough space, increment the TotalDatadeviceSizePerNode attribute. If this fails, delete and recreate the hadb instance, and retry the command.

> ##### HADB22043

> Description | This error message was generated by the addnodes/create command. Specified number of spares could not be allocated. Number of spares should be a positive number less than or equal to length of host list.
> Action | Retry the command with appropriate parameters.

> ##### HADB22044

> Description | This error message was generated by the addnodes command. Path configured for the original database is not existing on the new hosts: [ {0} {1} ].
> Action | Create the path on the new hosts.

> ##### HADB22045

> Description | This error message was generated by the addnodes command. Path configured for the original database does not have write permissions on the new host.
> Action | Set write permissions for the path on the new host.

> ##### HADB22046

> Description | This error message was generated by the addnodes command. Database state has deteriorated. Original and current states of the database are: [ {0} {1} ]
> Action | Check the nodes that have failed with the hadbm status --nodes command. Then check the history files for the nodes for error messages/warning messages. If some nodes have stopped, try to start them one by one with the hadbm startnodes command.

> ##### HADB22047

> Description | This error message was generated by the refragment command. Refragmentation cannot be done in this operation as the database is running under inetd. Use -r | --no-refragment option and re-run the command to turn off refragmentation.
> Action | Retry the command with appropriate parameters.

> ##### HADB22203

> Description | Info message from the addnodes command. Nodes successfully added to the database without refragmenting data. Use the inetd setup files to configure and restart inetd and then run refragment command.
> Action | No action to be taken.

> ##### HADB22061

> Description | This error message was generated by the clear command.
> Action | Check the history files for error messages. Retry the clear command, or delete and recreate the HADB instance.

> ##### HADB22065

> Description | This error message was generated by the delete command. Database is not in the stop state.
> Action | Stop the database by using the stop command and rerun the command.

> ##### HADB22066

> Description | Database could not be deleted: [ {0} ]
> Action | None

> ##### HADB22071

> Description | This error message was generated by the get/set command. Attributes are not recognized.
> Action | Retry the command with appropriate parameters.

> ##### HADB22072

> Description | This error message was generated by the set command. Some or all of the attributes cannot be set on an existing database.
> Action | The attributes are static for the HADB instance. Change, delete and recreate the HADB instance with the new attribute values.

> ##### HADB22073

> Description | This error message was generated by the get command. The get command failed to get the attributes from the database.
> Action | Retry the operation.

> ##### HADB22081

> Description | This error message was generated by the startnode command. Expected node state of stopped, but node state is running.
> Action | The node is already running, so do not run the startnode command. Check the status of the node by using the hadbm status --nodes command.

> ##### HADB22082

> Description | This error message was generated by the startnode command.
> Action | Retry the command with appropriate parameters.

> ##### HADB22083

> Description | This error message was generated by the startnode command. Node could not be started.
> Action | Check the history files for HADB.

> ##### HADB22085

> Description | This error message was generated by the stopnode command. Database has to be in HAFaultTolerant state for repair. No spare node is available. Node has not been stopped. Node number: [ {0} ].
> Action | The node can be stopped with the --no-repair option.

> ##### HADB22086

> Description | This error message was generated by the stopnode command. Node could not be stopped. Node number: [ {0} ]
> Action | Retry the command. Check hadb history files for error and warning messages.

> ##### HADB22087

> Description | This error message was generated by the stopnode command. Mirror node is not up. Node is not stopped. Node number and its mirror node number are: [ {0} {1} ]
> Action | None. Do not try to stop a node and a mirror node, the database will become non-operational. To stop all nodes, use the stop command for the database (hadbm stop).

> ##### HADB22088

> Description | This error message was generated by the stopnode command. Node should not be in stop state. Node state found is stopped. Node could not be stopped. Node number: [ {0} ]
> Action | None. The node is already stopped.

> ##### HADB22091

> Description | This error message was generated by the restartnode command. Node could not be restarted. Node number: [ {0} ]
> Action | Retry the command. Check the hadb history files for error and warning messages.

> ##### HADB22095

> Description | This error message was generated by the start command. Database could not be started: [ {0} ]
> Action | Check the HADB history files for error and warning messages. If the history files are not available, check for error and warning messages in syslog. The messages are prefixed with HADB, by default.

> ##### HADB22096

> Description | This error message was generated by the start command. Database is already running: [ {0} ]
> Action | None. The database is already running, so there is no need to run the start command.

> ##### HADB22097

> Description | This error message was generated by the start command. Database only partially started.
> Action | Retry the command, check hadb history files for error messages and warning messages.

> ##### HADB22101

> Description | This error message was generated by the stop command. Database could not be stopped.
> Action | Retry the command. Check hadb history files for error and warning messages.

> ##### HADB22102

> Description | This error message was generated by the stop command. Database is already in a stopped state.
> Action | None

> ##### HADB22105

> Description | This error message was generated by the restart command. Database is not running. Database name: [ {0} ]
> Action | Start the database with the hadbm start command.

> ##### HADB22106

> Description | This error message was generated by the restart command. Database could not be restarted. Database name: [ {0} ]
> Action | Retry the command. Check HADB history files for error and warning messages.

> ##### HADB22107

> Description | This error message was generated by the restart command. Restart failed to return the database to original state or better.
> Action | Check HADB history files for error and warning messages. Start nodes which are not running.

> ##### HADB22108

> Description | This error message was generated by the restart command. Database has to be in HAFaultTolerant or FaultTolerant states for rolling restart.
> Action | Use no-rolling option to restart the database

> ##### HADB22111

> Description | This error message was generated by the clearhistory command. Directory to which history files are to be saved does not exist.
> Action | Retry the command with appropriate parameters.

> ##### HADB22112

> Description | This error message was generated by the clearhistory command. Specified location to save the history files is not a directory.
> Action | Retry the command with appropriate parameters.

> ##### HADB22113

> Description | This error message was generated by the clearhistory command. Directory to which history files are to be saved does not have write permissions.
> Action | Retry the command with appropriate parameters.

> ##### HADB22114

> Description | This error message was generated by the clearhistory command. History files could not be cleared and saved.
> Action | Enable logging in the CLI by modifying the hadbmlogging.properties file in the lib directory. Retry the command. If it fails, Analyze the System, as described on (more...) .

> ##### HADB21006

> Description | The value for a configuration attribute is invalid.
> Action | Retry command with appropriate parameters.

> ##### HADB21022

> Description | The cladm command failed. There will be a linked message from cladm with error code and description as part of this error message.
> Action | Analyze the message from cladm.

> ##### HADB21024

> Description | No reply received in response to the dialog message for one of the server processes.
> Action | Verify that the nodes are running, retry the command.

> ##### HADB21042

> Description | Prevents the user from adding nodes with localhost as hostname.
> Action | You must supply the qualified hostname, preferably the IP address.

> ##### HADB21035

> Description | Device size is too small for logstore and data. A part of the data device is reserved for logstore. Totally 4*logbuffersize is reserved for logstore per node. This exception (4*logbuffersize+16) occurs if the data devices can not hold the log store.
> Action | Increase the size of the data devices, or decrease the size of the logbuffersize.

> ##### HADB21023

> Description | The cladm command could not be invoked.
> Action | Check permissions for the cladm script, located in the bin directory.

> ##### HADB25005

> Description | The communication RPC layer is closed.
> Action | Reconnect to the database.

> ##### HADB25010

> Description | The query string is too large.
> Action | Shorten the query, and if possible execute the query using multiple queries.

> ##### HADB25012

> Description | The connection to the database failed.
> Action | Check if the database is running, and that the correct host name and port numbers are used. Reconnect to the database.

> ##### HADB25017

> Description | The database server node serving the query is not currently available. The database connection is still valid, but the transaction must be retried.
> Action | Retry the transaction.

> ##### HADB25018

> Description | There has been a time-out in the call to the database server. The connection is still valid, but the transaction must be retried.
> Action | Retry the transaction.

> ##### HADB25020

> Description | The JDBC driver and the database server is not compatible. This is usually due to using a JDBC driver that is either too old or too new compared to the database server.
> Action | Use the correct JDBC driver version.

> ##### HADB25022

> Description | The transaction was rolled back due to an error in the commit cycle. The transaction must be retried.
> Action | Retry the transaction.

> Previous Contents Index Next

> Copyright 2004 Sun Microsystems, Inc. All rights reserved.