UNCAUGHT_EXCEPTION - CX_SY_NO_HANDLER in CL_RSBK_CMD_X=================CP ABAP Program

When I am loading data from PSA to DSO, this kind of exception is generated. Generally, this error occurs when we load huge volumes of data.

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------


Category               ABAP Programming Error
Runtime Errors         UNCAUGHT_EXCEPTION
Except.                CX_SY_NO_HANDLER
ABAP Program           CL_RSBK_CMD_X=================CP
Application Component  BW-WHM-DST
Date and Time          15.07.2012 23:33:24




 What can you do?
     Take note of the actions and inputs that lead to the error.


     Contact your SAP administrator for further processing of the problem.


     Using transaction ST22 for ABAP short dump analysis you can see and
     administrate termination messages and retain them for a longer period.






 Error analysis
     An exception occurred which is explained in detail below.
     The exception, which is assigned to class 'CX_SY_NO_HANDLER', was not caught
      and
     therefore caused a runtime error.
     The reason for the exception is:
     An exception with the type CX_SY_OPEN_SQL_DB occurred, but was neither handled
     locally, nor declared in a RAISING clause


     The occurrence of the exception is closely related to the occurrence of
     a previous exception "CX_SY_OPEN_SQL_DB", which was raised in the program
      "CL_RSODSO_SEMANTIC_PACKETIZER=CP",
     specifically in line 79 of the (include) program
      "CL_RSODSO_SEMANTIC_PACKETIZER=CM002".
     The cause of the exception was:


     The database returned a value containing an error

How to correct the error

    You may able to find an interim solution to the problem

    in the SAP note system. If you have access to the note system yourself,

    please use the following search criteria:

        "UNCAUGHT_EXCEPTION" "CX_SY_NO_HANDLER"

        "CL_RSBK_CMD_X=================CP" bzw.

     "CL_RSBK_CMD_X=================CM00R"

        "IF_RSBK_CMD_X~GET_DATAPACKAGE_GENERAL"

    If you cannot solve the problem yourself, please send the

    following documents to SAP:

    1. A hard copy print describing the problem (short dump).

       To obtain this, select "System->List->Save->Local File (unconverted)"

       on the current screen.

    2. A suitable hardcopy printout of the system log.

       To obtain this, call the system log with Transaction SM21

       and set the time interval to 10 minutes before and 5 minutes after

       the short dump. In the display choose "System->List->Save->

       Local File (unconverted)"

    3. If the programs are your own programs or modified SAP programs,

       supply the source code.

       To do this, choose "More Utilities->Upload/Download->Download" in the

       Editor.

    4. Details regarding the conditions under which the error occurred

       or which actions and input led to the error.

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Error Analysis:

So, after digging on search engine and SAP Notes. The problem or challenge in this ABAP dump analysis is that the process has lack of storage, lack of PSATEMP storage. PSAPTEMP is an ORACLE temporary tablespace using by the SAP BW. Like temp table on Microsoft SQL Server.

You can use ST14 to perform a Business Warehouse Application analysis, finding the large(largest) table so you can determine the suitable(minimum) size for PSAPTEMP. eventhough the exact size might be hard to figure, at least we can figure out the minimum storage size.

The process that took the significant ammount of storage is caused by ‘Semantic Groups’ technique. The ‘Semantic Groups’ feature will first gather all the information based on primary key / groups primary key to sort all the records across the packet.

2.Turn Off the ‘Semantic Groups’ feature in DTP. This will do the work also without extend the PSAPTEMP.
The consequence of turning off the ‘Semantic Groups’ is that you might be end up with fixing a lot of unqualified data despite those records have same key(primer key) or group key.

Option for solution, workaround:

1.Extend  PSAPTEMP

2.Turn Off the ‘Semantic Groups’ feature in DTP. This will do the work also without extend the PSAPTEMP.
The consequence of turning off the ‘Semantic Groups’ is that you might be end up with fixing a lot of unqualified data despite those records have same key(primer key) or group key.