Error While Running KE5T

Question

Short text
    Error in module RSQL of the database interface.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "GP$GLX$GLPCT" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
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.
    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.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
     in
    procedure "FETCH" "(FORM)", nor was it propagated by a RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    In a SELECT access, the read file could not be placed in the target
    field provided.
    Either the conversion is not supported for the type of the target field,
    the target field is too small to include the value, or the data does not
    have the format required for the target field.
Information on where terminated
    Termination occurred in the ABAP program "GP$GLX$GLPCT" - in "FETCH".
    The main program was "RGUCOMP4 ".
    In the source code you have the termination point in line 517
    of the (Include) program "GP$GLX$GLPCT".
    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
    procedure "FETCH" "(FORM)", but it was neither handled locally nor declared
    in the RAISING clause of its signature.
    The procedure is in program "GP$GLX$GLPCT "; its source code begins in line
    448 of the (Include program "GP$GLX$GLPCT ".
Source Code Extract
Line  SourceCde
  487
  488   IF I_APPENDING_TABLE EQ GUSL_C_TRUE.
  489     L_CLEAR = GUSL_C_FALSE.
  490   ELSE.
  491     L_CLEAR = GUSL_C_TRUE.
  492   ENDIF.
  493
  494 *     Post processing is necessary if
  495 *     cumulated balances are requested or
  496 *     full aggregation upon period is requested
  497   IF C_S_CURSOR-X_CUMULATED EQ GUSL_C_TRUE         OR
  498      C_S_CURSOR-PERIOD_AGGR EQ GUSL_C_PERAGGR_FULL.
  499     L_POST_PROC = GUSL_C_TRUE.
  500   ELSE.
  501     L_POST_PROC = GUSL_C_FALSE.
  502   ENDIF.
  503
  504   IF L_POST_PROC         EQ GUSL_C_TRUE AND
  505      C_S_CURSOR-PACKAGE  GT 0.
  506     PERFORM RESTORE_FETCHSTATE USING    C_S_CURSOR-SX_FETCHSTATE
  507                                CHANGING L_SX_FETCHSTATE.
  508   ENDIF.
  509
  510   L_COUNTER = 0.
  511   C_S_CURSOR-SUBRC = 0.
  512   WHILE I_PACKAGE_SIZE EQ 0              OR
  513         L_COUNTER      LT I_PACKAGE_SIZE.
  514     FETCH NEXT CURSOR C_S_CURSOR-CURSOR
  515           INTO CORRESPONDING FIELDS OF TABLE G_T_RECORDS
  516           PACKAGE SIZE L_PSIZE.
>>>>>     IF SY-SUBRC EQ 0.
  518       IF L_CLEAR EQ GUSL_C_TRUE.
  519         CLEAR: C_T_GLU1, C_T_DATA.
  520         L_CLEAR = GUSL_C_FALSE.
  521       ENDIF.
  522       DESCRIBE TABLE G_T_RECORDS LINES L_TFILL.
  523       ADD L_TFILL TO L_COUNTER.
  524     ELSE.
  525       IF L_COUNTER EQ 0.
  526         C_S_CURSOR-SUBRC = 8.
  527       ELSE.
  528         C_S_CURSOR-SUBRC = 4.
  529       ENDIF.
  530       FREE G_T_RECORDS.
  531       L_CURSOR = C_S_CURSOR-CURSOR.
  532       CLOSE CURSOR L_CURSOR.
  533       EXIT.
  534     ENDIF.
  535
  536     IF NOT I_S_REQTB-GLU1        IS INITIAL     OR

Answer 1

Hi,
We are facing the same problem, after the patch upgrdae.
Please let me know, if anyone got solution for the dump?
Regards,
Suresh