00000 SUCCESS
Explanation:
The SQL statement was successfully executed.
User Action:
No user action is required.
01003 NULL VALUE IN SET FUNCTION ELIMINATED
Explanation:
The SQL statement was successfully executed. At least one NULL value was eliminated from a <set function spec>.
User Action:
No user action is required.
01004 VARIABLE MAY BE TRUNCATED
Explanation:
The SQL statement was successfully executed. The value in the parameter or in the database column was too long to be stored completely in the corresponding database column or parameter. It was truncated.
User Action:
No user action is required. If this is not desired, modify either the format of the database column or the format of the parameter.
02000 ROW NOT FOUND
Explanation:
There is no (further) table row which meets the qualification.
User Action:
No user action is required.
07008 TOO MANY PARAMETERS FOR DESCRIPTOR
Explanation:
Too many parameters are specified for the descriptor variable.
User Action:
Reduce the number of parameters in the SQL statement. The maximum number is 300.
08001 SERVERDB NOT ACCESSIBLE
Explanation:
The attempt was made to start a session using an ADABAS component. This is not possible, because
1. the SERVERDB name was incorrectly specified or
2. the database server was not started.
User Action:
1. Check the specified SERVERDB name.
2. Start the database server.
08002 SESSION ALREADY CONNECTED
Explanation:
A database session has already been opened with this number.
User Action:
Either close the database session beforehand or remove the CONNECT from the application program.
08003
USER MUST BE CONNECTED
Explanation:
An ADABAS session can only be opened with a <connect statement>.
User Action:
Specify a <connect statement>.
CONNECT FAILED, CHECK SERVERDB
Explanation:
An error was detected while processing the CONNECT statement.
User Action:
1. Check the name of the database and correct it, if necessary.
2. A check must be made as to whether the database is running. If need be, the DBA must perform a RESTART.
3. Data communication with the database must be re-established.
SERVERDB SYSTEM NOT YET AVAILABLE
Explanation:
The database exists, but it is in the startup or shutdown phase, with the result that a connection cannot be established at the moment.
User Action:
Repeat the CONNECT at a later point in time.
08004
USER ALREADY CONNECTED TO THIS USER TASK
Explanation:
A user already connected to the database entered another <connect statement>.
User Action:
If the user wants to continue working under another user name, he must specify first the <release statement> and then a <connect statement>.
USER ALREADY CONNECTED
Explanation:
A user attempts to connect to ADABAS under a user name which was defined with EXCLUSIVE in a <create user statement>, <create usergroup statement>, <alter user statement>, or <alter usergroup statement>. Another user has connected to ADABAS using this name.
User Action:
The user must wait until the other user has disconnected from ADABAS using a <release statement>.
To enable a user to have several simultaneous connects, the owner of the user or usergroup must specify NOT EXCLUSIVE for this user using the <alter user statement> or <alter usergroup statement>.
CONNECT STATEMENT SYNTAX WRONG
Explanation:
There is an error in the CONNECT statement syntax.
User Action:
For the exact description of the syntax, refer to the chapter <connect statement>. Correct the statement accordingly.
IMPLICIT CONNECT: MISSING USER OR SERVERDB
Explanation:
During the execution of an implicit CONNECT, the user entries or the database name could not be found.
User Action:
Open an XUSER file, or enter the CONNECT parameters using runtime options.
MISSING USERNAME FOR CONNECT
Explanation:
No user/password combination could be found for an implicit CONNECT enabled by the CHECK option.
User Action:
Write the CONNECT statement as the first parameter into the program, or specify the option USER, or create an XUSER file for an implicit CONNECT.
MISSING USERNAME OR PASSWORD FOR CONNECT
Explanation:
A username or password specification is missing in a CONNECT statement, or there is no XUSER file for an implicit CONNECT.
User Action:
Specify username and password for the CONNECT statement using options, or open an XUSER file.
SERVERDB MUST BE RESTARTED
Explanation:
It is not possible to work on the SERVERDB because it was shut down.
User Action:
The SERVERDB must be started with the Operating / Restart / Warm menu function in the ADABAS component CONTROL.
UNKNOWN USER NAME/PASSWORD COMBINATION
Explanation:
The specified combination of user name and password is unknown. ADABAS can only be accessed by a combination that is known to the database.
User Action:
Change the user or password specification in the SQL statement.
0A000 SYSTEM ERROR: NOT YET IMPLEMENTED
Explanation:
This SQL statement is not yet implemented. It will be available in future versions.
User Action:
A user action is not possible.
21000 MORE THAN ONE RESULT ROW NOT ALLOWED
Explanation:
1. This error may occur when a <single select statement> is executed and more than one row complies with the <search condition>.
2. The error can also occur when a <subquery> specified in a <comparison predicate> or a <set update clause> of an <update statement> is executed and more than one row complies with the <search condition>.
User Action:
1. The <single select statement> can be replaced with a <query statement> and a sequence of <fetch statement>s, or it can be ensured that at most one row complies with the conditions by expanding the <search condition>.
2. The <comparison predicate> can be replaced with a <quantified predicate>. The attempt can be made to change the <subquery> in such a way that the <subquery> contains at most one row as the result by specifying DISTINCT or by expanding the <search condition>.
22001
INPUT VARIABLE HAS BEEN TRUNCATED
Explanation:
The contents of a character string is longer than the database is capable of storing, or a floating point number was truncated.
User Action:
Set the input variable to a string which corresponds to the length of the database variable or adapt the input variable to the format used in the database.
CONSTANT MUST BE COMPATIBLE WITH COLUMN TYPE AND LENGTH
Explanation:
The specified constant does not match the data type for this column.
User Action:
Use a <query statement> issued on the system table DOMAIN.COLUMNS to find out the definition of the affected column. Specify a constant with the correct data type.
ASSIGNMENT IMPOSSIBLE, CHAR VALUE TOO LONG
Explanation:
In an <insert statement> with <query expression> or in an <update statement>, the attempt was made to assign a character string to a column of data type CHAR. This character string was too long. The error message is returned for the first occurring value with an exceeding length, not while analyzing the maximum column lengths.
User Action:
Use SELECT ... WHERE LENGTH (<column name>) > <unsigned integer> in SQLMODE ADABAS to find out the rows containing a value with an exceeding length.
The length of the corresponding column can be increased in SQLMODE ADABAS by an <alter table statement>.
22002 MISSING INDICATOR VARIABLE,
OUTPUT PARAMETER WITH NULL VALUE
Explanation:
The indicator variable required for returning the NULL value to the SQL variable is missing.
User Action:
Specify an indicator variable with the parameter.
22003
INVALID EXPONENT
Explanation:
There is one of two possible causes.
1. A numeric final or temporary result is greater or less than the values which can be represented by a floating point number.
2. A numeric value is greater or less than permitted by the data type of a specified column.
User Action:
1. If a numeric temporary result is too large or too small, the attempt can be made to prevent an overflow or underflow by rearranging the arithmetic operations.
2. Use a <query statement> issued on the system table DOMAIN.COLUMNS to find out the data type of the column. The values must be corrected accordingly.
NUMERIC INPUT PARAMETER OVERFLOW
Explanation:
The numeric input value is too large for the database.
User Action:
Check the size of the input value and of the range of values valid for the database and modify them, if necessary.
NUMERIC OUTPUT PARAMETER OVERFLOW
Explanation:
An ADABAS database value is too large for the SQL variable or the parameter.
User Action:
Enlarge the value range for the SQL variable or parameter.
22005 INCOMPATIBLE DATA TYPES
Explanation:
The data type of the SQL variable or parameter is not compatible with the ADABAS data type.
User Action:
Change the data type of the SQL variable or parameter to match the ADABAS data type for the table column.
If this message is returned during precompilation and the data types do be compatible, precompile with NOCHECK option (see the chapter 'General Rules' of the Precompiler manuals).
22007
INVALID DATE FORMAT
Explanation:
The specified value is not a valid date value.
User Action:
Correct the date value.
INVALID TIME FORMAT
Explanation:
The specified value is not a valid time value.
User Action:
Correct the time value.
INVALID TIMESTAMP FORMAT
Explanation:
The specified value is not a valid timestamp value.
User Action:
Correct the timestamp value.
22012 INVALID NUMERIC EXPRESSION
Explanation:
It was intended to perform a division by 0.
User Action:
Check whether this error can be prevented by using appropriate <predicate>s.
22019 INVALID ESCAPE VALUE
Explanation:
The input host variable is longer than 1 byte.
User Action:
Use a correct host variable.
INVALID ESCAPE VALUE
Explanation:
Exactly one character is valid for an escape value.
User Action:
Reduce the escape value to one character.
22023 INVALID NUMERIC INPUT PARAMETER VALUE
Explanation:
The input value cannot be converted.
User Action:
Specify the value in a valid notation (see SQL variable types in the chapter 'General SQL Variable Conventions' of the Precompiler manuals).
22024 UNTERMINATED C STRING
Explanation:
The zero byte delimiter is missing.
User Action:
Insert a zero byte.
22025 INVALID ESCAPE SEQUENCE
Explanation:
The escape character may only be placed before a <match char> which is identical to the escape character, before a <match string>, or before a <match set> which is not a <match char>.
User Action:
Remove the exceeding escape character. Afterwards, the SQL statement can be reissued.
23000
INTEGRITY VIOLATION
Explanation:
Insertions or updates would violate integrity constraints specified in the base or view table definition.
User Action:
The error message specifies the column which would violate the integrity constraints.
Correct the input value for the corresponding column.
DUPLICATE KEY
Explanation:
There is already a table row with the key to be inserted.
User Action:
Check whether the existing table row contains the desired values. If this is not the case, check whether values in the existing table row can be replaced with the desired values. If a new table row must be inserted, change the value of the key to be inserted in order to prevent key collisions.
REFERENTIAL INTEGRITY VIOLATED
Explanation:
There is one of three possible causes.
1. An <insert statement> or <update statement> issued on a table that is the referencing table of a <referential constraint definition> produces a row that is not a matching row of the <referential constraint definition>.
2. When deleting rows from a <referenced table> of a <referential constraint definition> with <action> RESTRICT in the <delete rule>, a matching row exists.
3. When executing a <referential constraing definition>, the <referenced table> or referencing table contains rows which conflict with the <referential constraint definition>.
User Action:
1. Display the definition of the <referential constraint definition> using a <query statement> issued on the system table DOMAIN.COL_REFS_COL. Correct the <insert statement> or <update statement> according to this definition.
2. Use an appropriate <query statement> to determine which row of the referencing table prevents the desired <referenced table> rows from being deleted.
3. Use an appropriate <query statement> to determine which row of the <referenced table> or referencing table conflicts with the <referential constraint definition> to be created. Modify or delete the row concerned, or correct the <referential constraint definition> to be created.
DUPLICATE KEY IN INDEX
Explanation:
There is already a table row with the specified secondary key. UNIQUE was specified for the secondary key.
User Action:
Correct the value of the secondary key to be inserted in the SQL statement in order to avoid a key value collision.
The error message specifies the column or multiple-column index already containing the specified values.
24000
DUPLICATE RESULT TABLE NAME
Explanation:
A result table generated by DECLARE CURSOR must be closed using a <close statement>, before the result table name can be used to open a new result table within the transaction.
User Action:
Insert a <close statement> into the ADABAS application.
SQL STATEMENT NOT ALLOWED WITHOUT PREVIOUS FETCH
Explanation:
The attempt was made to issue an SQL statement with CURRENT OF <result table name>, without having previously issued a successful <fetch statement> on the specified result table.
ADABAS Action
Repeat the SQL statement, once you have issued a successful <fetch statement> for the result table.
UNKNOWN RESULT TABLE
Explanation:
There is no result table (any more) with the specified name.
User Action:
Use a <query statement> issued on the system table DOMAIN.TABLES to find out the names of the existing result tables. Correct the name of the result table or check why the result table with the specified name was deleted.
A <commit statement> and <rollback statement> implicitly close all result tables.
26000 UNKNOWN STATEMENT NAME
Explanation:
The statement name is unknown.
User Action:
Issue the PREPARE statement or correct it.
40001
LOCK REQUEST TIMEOUT
Explanation:
The lock request or an implicit lock conflicts with the locks of another user. The maximum waiting time for granting the lock has elapsed (installation parameter REQUEST TIMEOUT).
User Action:
In some cases, the error message contains a more detailed description of the error.
The lock request can be reissued. To avoid possible deadlock situations, it is advisable to roll back the transaction by using a <rollback statement>.
WORK ROLLED BACK
Explanation:
Your transaction was implicitly cancelled and rolled back by an implicit <rollback statement>, because
1. you failed to carry out any ADABAS operations within a certain period of time (installation parameter LOCK TIMEOUT), but held locks which other users were waiting for, or because
2. the SERVERDB was in a deadlock situation. A deadlock situation is a situation in which two or more users hold locks and request further locks that are held by the respective other users. In the simplest case of two users, one user holds one lock at least and requests another lock. But this lock is held by another user who, on the other hand, waits for the lock held by the first user. This situation can only be resolved if one of the users releases the lock already obtained.
User Action:
In some cases, the error message contains a more detailed description of the error.
In both cases, the lock requests must be checked and modified, if necessary. The last transaction must be repeated.
It may also be necessary to check and modify the value of the installation parameter LOCK TIMEOUT.
40003 SESSION INACTIVITY TIMEOUT (WORK ROLLED BACK)
Explanation:
Your transaction was implicitly cancelled and rolled back by an implicit <rollback statement>. The ADABAS session was implicitly terminated, since you failed to carry out any ADABAS operations within a certain period of time (installation parameter SESSION TIMEOUT or TIMEOUT value specified with the <connect statement>).
User Action:
Repeat the <connect statement> and specify a larger TIMEOUT value, if necessary.
It may also be necessary to check and modify the value of the installation parameter SESSION TIMEOUT.
42000
MISSING IDENTIFIER
Explanation:
An <identifier> is missing.
User Action:
The error position indicates the location of the missing <identifier>. Insert an <identifier> into the SQL statement.
IDENTIFIER TOO LONG
Explanation:
The specified identifier is longer than 18 characters.
User Action:
Specify an identifier that does not exceed 18 characters.
MISSING INTEGER
Explanation:
An integer is missing.
User Action:
Insert an integer into the SQL statement.
MISSING CONSTANT
Explanation:
A constant is missing in the SQL statement.
User Action:
Insert a constant into the SQL statement.
PARAMETER SPEC NOT ALLOWED IN THIS CONTEXT
Explanation:
1. The attempt was made to specify a parameter in a <select column>.
2. The error message can also be returned if a <comparison predicate> of the format '<parameter spec> <comp op> <parameter spec>' occurs within the <search condition>.
3. The error message can also occur if a <comparison predicate>, <in predicate>, or <quantified predicate> specifies a comparison between a parameter and a <subquery>.
User Action:
1. Replace the parameter with a constant.
2. It is useful to check such a condition within the ADABAS application, not in ADABAS. If this is not possible, replace one of the two parameters with a constant, a column name, or an <expression> which does not only contain parameters.
3. Replace the parameter with a constant, so that the data type of the parameter becomes unique.
RESERVED IDENTIFIER NOT ALLOWED
Explanation:
The specified name is a reserved keyword and must not be used to identify database objects.
User Action:
Correct the SQL statement using another <identifier>.
INVALID KEYWORD OR MISSING DELIMITER
Explanation:
The SQL statement contains an incorrect keyword or a keyword that is unknown, or a keyword or delimiter is missing.
User Action:
Correct the SQL statement according to the syntax description.
COLUMN MUST BE GROUP COLUMN
Explanation:
A column which is not a group column was specified in a <select column> or <having clause>. Columns which are not group columns may only occur in arguments of the functions COUNT, SUM, AVG, MAX, or MIN.
User Action:
Insert the specified column into the <group clause> as further group column or remove it from the <select column> or <having clause>.
UNKNOWN COLUMN NAME
Explanation:
There is no column with the specified name in any of the specified tables.
User Action:
Use <query statement>s issued on the system table DOMAIN.COLUMNS to find out the names of the columns existing in the tables. Correct the column name.
UNKNOWN TABLE NAME
Explanation:
A table with the specified name is not known to you. This table may not exist; or this table exists but you have no privileges for it.
User Action:
Use a <query statement> issued on the system table DOMAIN.TABLES to find out the names of the tables for which you have privileges. Then correct the table name. It may be sufficient to place the missing <owner> in front of it. Otherwise, create a table with the desired name or check why you have no privileges for the existing table.
UNION COLUMNS MUST BE COMPATIBLE
Explanation:
In a <query expression> with at least a UNION specification, all sequences of <select column>s must designate the same number of <select column> s. The data types amd lengths of the corresponding columns must be identical. It is also necessary that only <column spec>s or '*' may be specified in the sequences of <select column>s of the <query spec>s connected by UNION. The specification of <literal>s is not allowed.
User Action:
This request cannot be made.
INVALID SQL STATEMENT
Explanation:
The SQL statement either contains a typing error within the first two keywords, or is unknown, or is not permitted in this ADABAS version.
User Action:
Correct the typing errors, or specify another SQL statement.
INVALID UNSIGNED INTEGER
Explanation:
No valid number was specified.
User Action:
Correct the SQL statement.
INVALID DATATYPE
Explanation:
The specified data type is unknown.
User Action:
The valid data types are described in the chapter '<column definition>' in this manual. Use one of the data types specified there.
INVALID TABLE NAME
Explanation:
The specified table name does not comply with the syntax for <identifier>s.
User Action:
Correct the table name specified in the SQL statement.
INVALID END OF SQL STATEMENT
Explanation:
According to the syntax, the specified SQL statement is not allowed.
User Action:
The error position shows the location where the specified SQL statement deviates from the permitted syntax.
Correct the SQL statement accordingly.
VARIABLE IN VIEW DEFINITION NOT ALLOWED IN VIEW
Explanation:
Parameters must not be specified in the <create view statement>.
User Action:
Use constants instead of variables.
MISSING VALUE SPECIFICATION
Explanation:
A value is missing, or the specified value is not allowed.
User Action:
Correct the value specified in the SQL statement, or insert a value into the SQL statement.
MISSING NUMERIC CONSTANT
Explanation:
A number is missing.
User Action:
The error position indicates the location of the missing number. Insert a number into the SQL statement.
NUMERIC CONSTANT TOO LONG
Explanation:
A number was entered which
1. contains more than 18 digits or
2. does not comply with the definition of the range of values.
User Action:
The number which was incorrectly entered may be found out from the position specification in the error message.
1. The number must be reduced to 18 significant digits and be specified as <floating point literal>, if necessary.
2. The definition of the range of values must be checked and the specification of the number must be corrected accordingly.
MISSING STRING CONSTANT
Explanation:
A string constant is missing in the issued SQL statement.
User Action:
Insert a <string literal> into the SQL statement.
TOO FEW COLUMNS
Explanation:
For a <referential constraint definition>, less <referencing column>s than <referenced column>s were specified. The number of columns specified for the referencing table must correspond to the number of the <referenced column>s or the <referenced table> specified implicitly or explicitly.
User Action:
Use a <query statement> issued on the system table DOMAIN.COLUMNS to determine the definition of the key columns of the <referenced table>. Use a <query statement> issued on the system table DOMAIN.IND_USES_COL to find out the indexes of the <referenced table>. The specification of the referencing table columns must be adapted accordingly.
TOO FEW VALUES
Explanation:
In case of an <insert statement> or <update statement>, the number of specified values is less than the number of column names (possibly implicitly specified).
User Action:
Adapt the number of specified values in the SQL statement to the number of specified column names.
Use a <query statement> issued on the system table DOMAIN.COLUMNS for an <insert statement> without column name specification to determine the definition of the used table.
TOO MANY VARIABLES
Explanation:
A maximum of 300 variables may be specified per SQL statement.
User Action:
Decrease the number of variables in the SQL statement. Some variables must be replaced with constant values. If this is not possible, split the SQL statement into several SQL statements.
TOO MANY VALUES
Explanation:
In case of an <insert statement> or <update statement>, the number of specified values exceeds the number of column names (possibly implicitly specified).
User Action:
Adapt the number of specified values in the SQL statement to the number of specified column names.
Use a <query statement> issued on the system table DOMAIN.COLUMNS for an <insert statement> without column name specification to find out the definition of the used table.
MISSING PRIVILEGE
Explanation:
You are not authorized to execute the SQL statement.
User Action:
Use a <show privileges statement> to find out the privileges you have received for the specified table. It is not possible to execute the desired SQL statement.
44000 VIEW VIOLATION
Explanation:
An <insert statement> or <update statement> was issued for a view table. At least one of the rows specified in the SQL statement does not satisfy the <search condition>s of all underlying view tables defined 'WITH CHECK OPTION'.
User Action:
Display the definition of the view table using a <query statement> issued on the system table DOMAIN.VIEWDEFS. Correct the <insert statement> or <update statement> according to this definition.
Ixxxx
Explanation:
SQLSTATEs starting with 'I' are SQLSTATEs which are not predefined by the standard. For the Explanation and User Actions, see the manual Messages and Codes. To find out the pertinent description, replace the 'I' of the SQLSTATE with a '-'. Leading '0's are omitted.
User Action:
See the manual Messages and Codes.
Sxxxx SYSTEM ERROR
Explanation:
These error messages should not occur during normal operation on a consistent database.
With some errors, an implicit SHUTDOWN is issued.
User Action:
As a rule, the database should be shut down and the ADABAS Support be informed. It is possible to create a trace of the last database activities. Write this trace to magnetic tape and send it to the ADABAS Support for error tracing and correction.