Comments
ABAP EXEC EXCEPTIONS Statement syntax, information and example SAP source code
INCLUDE
Runtime Exceptions
Catchable Exceptions
CX_SY_NATIVE_SQL_ERROR
Reason for error: Error when building up a secondary database connection.
Runtime error: DBIF_DSQL2_CONNECTERR
Reason for error: The specified secondary database connection is not
registered in table DBCON .
Runtime error: DBIF_DSQL2_CONNECTSTR_ERROR
Reason for error: Error at COMMIT or ROLLBACK on the
"DEFAULT" database connection.
Runtime error: DBIF_DSQL2_DEFAULT_CR_ERROR
Reason for error: Internal error when processing
Native SQL .
Runtime error: DBIF_DSQL2_INTERNAL_ERROR
Reason for error: Environment variables with errors in table DBCON
used for connection to SAP or another external database
(Multi-Connect). To build up a connection, the environment variables are
read from the table DBCON and analysed. The check resulted that
the values are longer than allowed, or that environment variables are
missing when building up a connection.
Runtime error: DBIF_DSQL2_INVALENV_ERROR
Reason for error: Illegal disruption of a database selection. The cursor
was closed.
Runtime error: DBIF_DSQL2_INVALID_CURSOR :
Reason for error: The DSQL interface was called using illegal
parameters. In Syslog (SM21) , you can find further comments
about the illegal parameters.
Runtime error: DBIF_DSQL2_INVALID_REQUEST
Reason for error: There is already a dataset with the specified key.
Runtime error: DBIF_DSQL2_KEY_ALREADY_EXISTS
Reason for error: The specified key was not found in the database.
Runtime error: DBIF_DSQL2_KEY_NOT_FOUND
Reason for error: Internal Error at COMMIT or
ROLLBACK .
Runtime error: DBIF_DSQL2_MIXED_CR_ERROR
Reason for error: Error at COMMIT or ROLLBACK
on a Native SQL database connection.
Runtime error: DBIF_DSQL2_NATIVE_CR_ERROR
Reason for error: No more memory available for a Native SQL
Statement.
Runtime error: DBIF_DSQL2_NO_MEMORY
Reason for error: The database object already exists in the database. You
tried to create a database object (table, View, Index, ...) in the
database. This object already existed.
Runtime error: DBIF_DSQL2_OBJ_EXISTS
Reason for error: You used the name of a table or a view that does not
exist in the database.
Runtime error: DBIF_DSQL2_OBJ_UNKNOWN
Reason for error: SQL Error at the execution of a Native SQL
command.
Runtime error: DBIF_DSQL2_SQL_ERROR
Reason for error: The database interface delivered an unexpected
return-code.
Runtime error: DBIF_DSQL2_UNEXPECTED_CODE
Reason for error: The maximum number of secondary database connections was
exceeded.
Runtime error: EXSQL_CONNECTION_LIMIT
Reason for error: The maximum number of cursors was exceeded.
Runtime error: EXSQL_DSQL_CURSOR_LIMIT
Non-catchable Exceptions
Reason for error: Internal Error: Statement-ID cannot be set.
Runtime error: EXSQL_CANT_SET_STATEMENT_ID
Reason for error: The specified cursor does not exist. At a CLOSE
or SELECT command in Native SQL , a cursor was specified
which is unknown to the cursor administration.
Runtime error: EXSQL_DSQL_CURSOR_NOT_FOUND
Reason for error: The specified cursor is already open. A cursor was
specified at a OPEN command in Native SQL which the cursor
administration knows as already opened.
Runtime error: EXSQL_DSQL_DUPLICATE_CURSOR
Reason for error: No more roll memory available. When processing a
Native SQL Statement, the internal memory is required to prepare the
SQL Call.
Runtime error: EXSQL_DSQL_NOROLL
Reason for error: An indicator variable has the wrong type. It must have
the type INT2 .
Runtime error: EXSQL_DSQL_WRONG_IVAR_TYPE
Reason for error: Internal error: No entry at EXEC SQL
PERFORMING in the stack.
Runtime error: EXSQL_FETCH_DSQL_STACK_EMPTY
Reason for error: The connection name has already been assigned. At an
CONNECT command in Native SQL , a connection name was
specified which is already used for another connection.
Runtime error: EXSQL_ILLEGAL_CONNECTION
Reason for error: At a DISCONNECT command in Native SQL , the
connection "DEFAULT" was specified. This connection cannot be
terminated with DISCONNECT .
Runtime error: EXSQL_ILLEGAL_DISCONNECTION
Reason for error: A Native SQL command contains too many variables.
As variables are considered all ABAP fields that are marked with
a preceding colon(":") . If the INTO clause has the form INTO
:wa for a work area wa , then all the fields of wa are
also considered variables.
Runtime error: EXSQL_TOO_MANY_VARS
Reason for error: At a SET CONNECTION or DISCONNECT command
in Native SQL , a connection was specified that is unknown to the
connection administration.
Runtime error: EXSQL_UNKNOWN_CONNECTION
Reason for error: Despite the assurance INTO STRUCTURE , the target
option, specified in the INTO- clause, is not structured.
Runtime error: EXSQL_UNSTRUCTURED_INTO
Reason for error: A locator-variable has the wrong type.
Locator-variables have to be of the type "I" haben.
Runtime error: EXSQL_WRONG_TYPE_FOR_LOCATOR
Reason for error: A LOB Variable has the wrong type. LOB
Variables must have the type string , xstring , c ,
x or n .
Runtime error: EXSQL_WRONG_TYPE_FOR_LOB
Documentation extract taken from SAP system, � Copyright SAP AG. All rights reserved
