Root cause of "SQL error in the database when accessing a table. "

Question

Dear experts,
I meet this dump "SQL error in the database when accessing a table" when executing a sql.
Sql:
    SELECT sesssessno poscrm_serplan_id poscrm_ser_h_id poscrm_ser_i_id
           possolution_id sessbundle_id sessdbid sessinstno pos~crm_ordered_prod
           sessdbid sessinstno
      INTO CORRESPONDING FIELDS OF TABLE et_sess_list
      FROM dsvassessadmin AS sess JOIN service_posn_sm AS pos
        ON possession_id     = sesssessno
      FOR ALL ENTRIES IN lt_contractno
      WHERE sess~contractno = lt_contractno-contract_no
       AND sess~status IN lt_status_range
       AND bundle_id IN lt_bundle_id
       AND pos~solution_id GT 0
This sql works well in dev system SD7, however, it causes dump in another dev system "SMV".
Can anyone give me any ideas?
Thanks

Answer 1

Hi Jovito,
This is info from ST22
Short text
    SQL error in the database when accessing a table.
What can you do?
    Note which actions and input led to the error.
    For further help in handling the problem, contact your SAP administrator
    You can use the ABAP dump analysis transaction ST22 to view and manage
    termination messages, in particular for long term reference.
How to correct the error
    Database error text........: "SQL0101N The statement is too long or too
     complex. SQLSTATE=54001"    Internal call code.........: "[RSQL/OPEN/DSVASSESSADMIN ]"
    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_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
    "CL_AGS_SERVICE_SERV===========CP" or "CL_AGS_SERVICE_SERV===========CM018"
    "GET_OVS_SESSION_LIST"
    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 SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    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 error occurred or which
    actions and input led to the error.
    The exception must either be prevented, caught within proedure
    "GET_OVS_SESSION_LIST" "(METHOD)", or its possible occurrence must be declared
     in the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
It seems that after translation the native sql is too long. But I think this can be solved.