+00050

Warning message

The request was successfully completed, but a warning was issued.

+00100

No more data

A request for data was processed, but either no data or no more data fitting the requested characteristics was found.

00000

Successful completion

The request completed normally with no errors or unexpected conditions occurring.

-30100

Table not found

A table referenced in a statement doesn’t exist or is owned by another user. This error can also be returned concerning an index or a view.

-30110

Column not known or not in table

A column referenced in a statement is not found.

-30120

Unknown cursor

An invalid or unopened cursor name or identifier was specified or referenced in a statement.

-30130

Other database object not found

A database object other than a table, view, index, column or cursor was specified or referenced in a statement, but is not identified or located. This applies to a database procedure, a grant or permission, a rule, or other object.

-30140

Other unknown or unavailable resource

A resource, of a type other than one mentioned above, is either not known or unavailable for the request.

-30200

Duplicate resource definition

An attempt to define a database object (such as a table) was made, but the object already exists.

-30210

Invalid attempt to insert duplicate row

A request to insert a row was refused; the table does not accept duplicates, or there is a unique index defined on the table.

-31000

Statement syntax error

The statement just processed had a syntax error.

-31100

Invalid identifier

An identifier, such as a table name, cursor name or identifier, procedure name, was invalid because it contained incorrect characters or been too long.

-31200

Unsupported query language

A request to use an unrecognized or unsupported query language was made.

-32000

Inconsistent or incorrect query specification

A query, while syntactically correct, was logically inconsistent, conflicting or otherwise incorrect.

-33000

Runtime logical error

An error occurred at runtime. An incorrect specification was made, an incorrect host variable value or type was specified or some other error not detected until runtime was found.

-34000

Not privileged/ restricted operation

An operation was rejected because the user did not have appropriate permission or privileges to perform the operation, or the operation was restricted (for example, to a certain time of day) and the operation was requested at the wrong time or in the wrong mode.

-36000

System limit exceeded

A system limit was exceeded during query processing, for example, number of columns, size of a table, row length, or number of tables in a query.

-36100

Out of needed resource

The system exhausted, or did not have enough of, a resource such as memory or temporary disk space required to complete the query.

-36200

System configuration error

An error in the configuration of the system was detected.

-37000

Communication/ transmission error

The connection between the DBMS and the client failed.

-38000

Error within an Enterprise Access product

An error occurred in an Enterprise Access product or DBMS interface.

-38100

Host system error

An error occurred in the host system.

-39000

Fatal error - session terminated

A severe error occurred which has terminated the session with the DBMS or the client.

-39100

Unmappable error

An error occurred which is not mapped to a generic error.

-40100

Cardinality violation

A request tried to return more or fewer rows than allowed. This usually occurs when a singleton select request returns more than one row, or when a nested subquery returns an incorrect number of rows.

-402dd

Data exception

A data handling error occurred. The subcode dd defines the type of error.

-40300

Constraint violation

A DBMS constraint, such as a referential integrity or the check option on a view was violated. The request was rejected.

-40400

Invalid cursor state

An invalid cursor operation was requested; for example, an update request was issued for a read-only cursor.

-40500

Invalid transaction state

A request was made that was invalid in the current transaction state. For example, an update request was issued in a read-only transaction, or a request was issued improperly in or out of a transaction.

-40600

Invalid SQL statement identifier

An identifier for an SQL statement, such as a repeat query name, was invalid.

-40700

Triggered data change violation

A change requested by a cascaded referential integrity change was invalid.

-41000

Invalid user authorization identifier

An authorization identifier, usually a user name, was invalid.

-41200

Invalid SQL statement

Unlike generic error -31000 (statement syntax error), this was a recognized statement that is either currently invalid or unsupported.

-41500

Duplicate SQL statement identifier

An identifier for an SQL statement, such as a repeat query name, was already active or known.

-49900

Serialization failure (Deadlock)

An error occurred (for example, deadlock, timeout, forced abort, log file full) that caused the query to be rejected. If the transaction is rejected, it is rolled back except in the case of a timeout. (Check SQLWARN6 in the SQLCA structure.) The query or transaction can be resubmitted.