Ansicht
Dokumentation

ABAPEXEC_EXCEPTIONS - EXEC EXCEPTIONS

ABAPEXEC_EXCEPTIONS - EXEC EXCEPTIONS

General Data in Customer Master   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.
SAP E-Book

Exceptions

Catchable Exceptions

CX_SY_NATIVE_SQL_ERROR

  • Cause: Error when making a secondary connection.
    Runtime Error: DBIF_DSQL2_CONNECTERR
  • Cause: Illegal interruption of a database selection. The cursor was closed.
    Runtime Error: DBIF_DSQL2_INVALID_CURSOR:
  • Cause: There is insufficient memory available for a Native SQL statement.
    Runtime Error: DBIF_DSQL2_NO_MEMORY
  • Cause: Database object already exists in the database. An attempt was made to create a database object (for example, table, view, index) on the database, but this object already exists.
    Runtime Error: DBIF_DSQL2_OBJ_EXISTS
  • Cause: The name of a table or view that does not exist on the database was used.
    Runtime Error: DBIF_DSQL2_OBJ_UNKNOWN
  • Cause: An SQL error occurred while executing a native SQL statement.
    Runtime Error: DBIF_DSQL2_SQL_ERROR
  • Cause: The maximum number of secondary connections was exceeded.
    Runtime Error: EXSQL_CONNECTION_LIMIT
  • Cause: The maximum number of database cursors was exceeded.
    Runtime Error: EXSQL_DSQL_CURSOR_LIMIT

Non-Catchable Exceptions

  • Cause: The specified cursor does not exist. A CLOSE or SELECT statement in Native SQL has a specified cursor, but this cursor is unknown to cursor administration.
    Runtime Error: EXSQL_DSQL_CURSOR_NOT_FOUND
  • Cause: The specified cursor is already open. An OPEN statement in Native SQL has a specified cursor, which the cursor administration knows is already open.
    Runtime Error: EXSQL_DSQL_DUPLICATE_CURSOR
  • Cause: There is insufficient roll memory available. When a Native SQL statement is processed, the internal memory is needed for preparing the SQL Call.
    Runtime Error: EXSQL_DSQL_NOROLL
  • Cause: An indicator variable has an incorrect type. It must be the type INT2.
    Runtime Error: EXSQL_DSQL_WRONG_IVAR_TYPE
  • Cause: The connection name has already been used for another connection. A CONNECT statement in Native SQL has a specified connection name, which is already used for another connection.
    Runtime Error: EXSQL_ILLEGAL_CONNECTION
  • Cause: The connection "DEFAULT" was specified for a DISCONNECT statement in Native SQL. This connection cannot be terminated with DISCONNECT.
    Runtime Error: EXSQL_ILLEGAL_DISCONNECTION
  • Cause: A Native SQL statement contains too many variables. In this context, variables means all ABAP fields preceded by a colon (":"). If the INTO clause has the form INTO :wa for a work area wa, then all the fields of wa also count as variables.
    Runtime Error: EXSQL_TOO_MANY_VARS
  • Cause: A SET CONNECTION or DISCONNECT statement in Native SQL has a specified connection that is unknown to the connection administration.
    Runtime Error: EXSQL_UNKNOWN_CONNECTION
  • Cause: The target area specified in the INTO clause is not structured despite the assertion INTO STRUCTURE.
    Runtime Error: EXSQL_UNSTRUCTURED_INTO
  • Cause: 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





PERFORM Short Reference   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 5447 Date: 20240623 Time: 194008     sap01-206 ( 79 ms )