TRY ... CATCH doesn't work with EXEC SQL?

Question

When I created a native SQL statement, I knew before, that it would take a few tries to get it working. I decided to use exception classes to avoid short dumps, but it didn't work.
Following code causes a short dump because of the dot after :xp_stras in the native SQL SELECT statement:
   try.
       EXEC SQL                     PERFORMING  list.
         SELECT LIFNR, NAME1, STRAS
                                INTO  :xsl
                                FROM  LFA1
         WHERE  UPPER( NAME1 )  LIKE  :xp_name1
         AND    UPPER( STRAS )  LIKE  :xp_stras.
       ENDEXEC.
                                                                                catch CX_SY_NATIVE_SQL_ERROR.
       write: /1 'CX_SY_NATIVE_SQL_ERROR'.
   catch CX_SY_SQL_ERROR.
       write: /1 'CX_SY_SQL_ERROR'.
   catch CX_DYNAMIC_CHECK.
       write: /1 'CX_DYNAMIC_CHECK'.
   catch CX_ROOT.
       write: /1 'CX_SY_ROOT'.
   endtry.
In ST22 you can see
Name of runtime error: DBIF_DSQL2_SQL_ERROR
Exception:
The name of the exception is empty, in other short dumps you can find there the name of the exception class. Maybe that's the reason for CATCH does'nt work, but I don't understand it.
Online help for EXEC SQL says:
Catchable Exceptions
CXSY_NATIVE_SQL_ERROR_
Cause: SQL-Error at the execution of a Native SQL-command.
Runtime Error: DBIF_DSQL2_SQL_ERROR
We have SAP ECC 6.0 with SAP_BASIS rel. 700 lvl. 0013.
If You have an idea why CATCH doesn't work, please tell me!
Regards,
Klaus

Answer 1

Hi Rob,
I tried out Your original code as program ZTEST5 and got a short dump (sorry, some of the short dump symbols are formatting this post in a wrong way ...):
Short text
    An SQL error occurred when executing Native SQL.
What happened?
    The error 919 occurred in the current database connection "DEFAULT".
What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
How to correct the error
    Database error text........: "ORA-00919: invalid function"
    Database error code........: 919
    Triggering SQL statement...: "FETCH NEXT "
    Internal call code.........: "[DBDS/NEW DSQL]"
    Please check the entries in the system log (Transaction SM21).
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "DBIF_DSQL2_SQL_ERROR" " "
    "ZTEST5" or "ZTEST5"
    "START-OF-SELECTION"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction
       Restrict the time interval to 10 minutes befor
    after the short dump. Then choose "System->List->
    (Unconverted)".
    3. If the problem occurs in a problem of your own
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the e
    actions and input led to the error.
System environment
    SAP-Release 700
    Application server... "lux01617"
    Network address...... "195.217.80.104"
    Operating system..... "Linux"
    Release.............. "2.6.5-7.283-smp"
    Hardware type........ "x86_64"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 5
    Shortdump setting.... "full"
    Database server... "lux09208"
    Database type..... "ORACLE"
    Database name..... "D10"
    Database user ID.. "SAPDAT"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Dec 2 2007 20:18:08"
    create on........ "Linux GNU SLES-9 x86_64 cc3.3.3"
    Database version. "OCI_102 (10.2.0.2.0) "
    Patch level. 138
    Patch text.. " "
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 1
    SAP database version. 700
    Operating system..... "Linux 2.6"
    Memory consumption
    Roll.... 16192
    EM...... 16759392
    Heap.... 0
    Page.... 98304
    MM Used. 694160
    MM Free. 3493088
User and Transaction
    Client.............. 500
    User................ "Z0000D2P"
    Language key........ "E"
    Transaction......... "SE38 "
    Transactions ID..... "48FE92EB921F51C3E1000000C3D95068"
    Program............. "ZTEST5"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
Information on where terminated
    Termination occurred in the ABAP program "ZTEST5" - in "START-OF-SELECTION".
    The main program was "ZTEST5 ".
    In the source code you have the termination point in line 16
    of the (Include) program "ZTEST5".
Source Code Extract
Line  SourceCde
    1 REPORT ztest LINE-SIZE 80 MESSAGE-ID 00.
    2
    3 TABLES: lfa1.
    4
    5 DATA: BEGIN OF xsl,
    6         lifnr TYPE lfa1-lifnr,
    7         name1 TYPE lfa1-name1,
    8         stras TYPE lfa1-stras,
    9       END   OF xsl.
   10
   11 DATA: xp_name1 TYPE lfa1-name1,
   12       xp_stras TYPE lfa1-stras.
   13
   14 TRY.
   15     EXEC SQL PERFORMING list.
>>>>>       SELECT LIFNR, NAME1, STRAS
   17       INTO :xsl
   18       FROM LFA1
   19       WHERE UPPER( NAME1 ) LIKE :xp_name1
   20       AND UPPER( STRAS ) LIKE :xp_stras.
   21     ENDEXEC.
   22
   23   CATCH cx_sy_native_sql_error.
   24     WRITE: /1 'CX_SY_NATIVE_SQL_ERROR'.
   25   CATCH cx_sy_sql_error.
   26     WRITE: /1 'CX_SY_SQL_ERROR'.
   27   CATCH cx_dynamic_check.
   28     WRITE: /1 'CX_DYNAMIC_CHECK'.
   29   CATCH cx_root.
   30     WRITE: /1 'CX_SY_ROOT'.
   31 ENDTRY.
   32
   33 &----
   34 *&      Form  LIST
   35 &----
Edited by: Klaus Babl on Oct 22, 2008 6:42 AM