Display Data Flow - Short Dump

Hi all,
When i select display data flow of any cube...it is going for a short dump.
I have searched for the answer in previous Forum questions. I could find only for previous BW versions but not for for BI7.
Could you please let me know the solution for this issue.
Thanks & Regards,
Eswari

Hi All,
Thank you very much for all of your responces.....
I am working on Support Package 10.
Here is the detailed description of the short dump.
Short text
    The current application triggered a termination with a short dump.
What happened?
    The current application program detected a situation which really
    should not occur. Therefore, a termination with a short dump was
    triggered on purpose by the key word MESSAGE (type X).
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.
Error analysis
    Short text of error message:
    GP: Control Framework returned an error; contact system administrator
    Long text of error message:
     Diagnosis
         The Graphical Framework is based on the basis technology known as
         the Control Framework. A method in the Control Framework returned
         an error.
     Procedure
         It probably involves a programming error. You should contact your
         system administrator.
     Procedure for System Administration
         Check the programming of the graphics proxy especially for the
         parameters that were sent and, if necessary, correct your program.
    Technical information about the message:
    Message class....... "APPLG"
    Number.............. 229
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    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:
    "MESSAGE_TYPE_X" " "
    "CL_AWB_OBJECT_NET_SAPGUI======CP" or "CL_AWB_OBJECT_NET_SAPGUI======CM005"
    "PBO"
    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.
Thanks,
Eswari.

Similar Messages

  • Data Load Short Dump (ABAP/4 processor: ASSIGN_TYPE_CONFLICT)

    Hi Experts,
      I made few changes to the exisisting data target and transported it to Test system...
    Today when i loaded test data i got Dump: ABAP/4 processor: ASSIGN_TYPE_CONFLICT error
    Now i need to reactivate the Transformations and DTP's that will fix the error
    What is the reason for this error
    Thanks

    Yes, you are correct, you need to activate your transformation and then DTP to get rid of this error.
    The reason for this error is inconsistency b/w transformation and DTP.If you have made any changes to trasforamtion and activated it, then you need to activate the DTP also. If you are loading the data without DTP activation, you will get this error. This is because the DTP is build on transformation.
    Thanks...
    Shambhu

  • Short dumps, tuning

    What are techniques used for tuning query performance? Please explain in detail?
    What are short dumps how can we check?
    What methodologies we follow for the PSA cleansing? Where exactly is the PSA change log where we can delete the request based on timestamp details am using BW 3.1c?
    plz help points assured....

    Hi,
    For query performance please check the following link
    http://help.sap.com/saphelp_nw2004s/helpdata/en/41/b987eb1443534ba78a793f4beed9d5/frameset.htm
    Short dumps:
    A short dump is an program error because of which the process terminates. It is notified and can be viewed in t-code ST22 on a particular usernaem where you can analyze the reason for short dump.
    and refer these links
    http://publib.boulder.ibm.com/tividd/td/ITMAN/SC32-9195-00/en_US/HTML/sap_add06.htm
    short dump
    Short dump while loading data?
    Update rules activation gives short dump?
    Delete of Master Data creates short dump?
    PSA:
    check the following link
    http://help.sap.com/saphelp_nw70/helpdata/EN/bd/c627c88f9e11d4b2c90050da4c74dc/frameset.htm
    Hope it help u.
    Assign Points if it helps.
    Regards,
    RKC
    Edited by: RKC on Mar 7, 2008 11:29 AM

  • Documentation of data flow and processes in BW

    Hi,
    Is anyone aware of the possibility to document data flow and job-flows from BW (source systems, datasources etc all the way to queries) and export it from BW.
    I am looking for a SAP certified tool like ie. Erwin that can collect this documentation from BW. I have not been able to find out if Erwin supports BW.
    My hope is that - now that these things are done in BW - I can extract/export this documentation and use it in our general documentation environment.
    The alternative is to manually document it.
    Regards,
    Mick
    Denmark

    Hi Mick,
    I don't think that there is a tool like the one you are talking about...
    however, if you select your infoprovider and then right-click->display data flow...in this way, you can obtain a picture of your data flow from the datasource to your provider with all the interdependencies !
    Hope it helps !
    Bye,
    Roberto

  • EWA on solution manager - short dumps

    Hi there
    I've setup EWA on solution manager for Remote System BWQ, all test etc went fine, but as soon as I start service processing on solman to retrieve the data, a short dump is create as follows:
    Short text
        Syntax error in program "RDSVASAEA_ROOT_____________049 ".
    Error in the ABAP Application Program
    The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "RDSVASAEA_ROOT_____________049
      " in include "RDSVASAEA_ROOT_____________049 " in
    line 87:
    "INCLUDE report "/1CAGTF/IF_LOGFUNC_000393" not found."
    The include has been created and last changed by:
    Created by: "SAP "
    Last changed by: "SAP "
    Error in the ABAP Application Program
    The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    could anyone please assist me with this.
    Regards,
    Stephan

    Hi
    So i tried to implement the above mentioned notes, but to update the solution manager stack, i have to use maintenance optimizer to approve the stack...
    I have added solution manager 7.0 to the solution overview, and can select it from 'Plan Maintenance' window.. but as soon as i try and go to the second step, another short dump is created.
    Runtime Errors         UNCAUGHT_EXCEPTION
    Exception              CX_SOCM_NOT_IMPLEMENTED
    Date and Time          13.06.2008 09:25:45
    |Short text                                                                                |
    |    An exception occurred that was not caught.                                                    |
    |What happened?                                                                                |
    |    The exception 'CX_SOCM_NOT_IMPLEMENTED' was raised, but it was not caught                     |
    |     anywhere along                                                                               |
    |    the call hierarchy.                                                                           |
    |                                                                                |
    |    Since exceptions represent error situations and this error was not                            |
    |    adequately responded to, the running ABAP program                                             |
    |     'CL_CHM1_CHANGE_REQU_INSTANCE==CP' has to be                                                 |
    |    terminated.                                                                                |
    i then looked at Notes:
    Note 851496 - Exception: CX_SOCM_NOT_IMPLEMENTED missing implementation
    Note 849690 - BC Set Change Management
    But none of them seem relevant to our SOLMAN.

  • BW Data flow-Upward and downward option

    Hi Experts,
    We are getting this error while doing a ZInfocube -display data flow - Option Upwards and downward
    The screen hangs and nothing happens. In SM50, there is nothin happening, all processes waiting status.
    Please suggest what could be the reason and how to resolve it.
    Regards,
    Sabita

    Hi,
    Thanks for your suggestions. We changed the GUI configuration to Enjoy Screen and the flow chart is appearing now.
    Regards,
    Sabita

  • Short dump while displaying cube data in production

    Hi Folks,
    I'm getting a short dump while displaying cube data in production, please suggest
    Thanks and Regards
    Santhosh

    Hi Santosh,
    I'd suggest to follow as per SAP Note: 568768 - Analysis of SQL Errors causing Shortdumps or Error messages. The Note contains precise steps to analyze such an ABAP dump.
    cheers
    m./

  • Short dump while displaying infocube data

    Hi Folks,
    I have created one infocube in BW 7.3  with 2 characteristics and one keyfigure for uploading flat file data.
    I have successfully uploaded the data into infocube.When i go for displaying data by right click on the infocube it is throwing some short dump.
    Pls find the short dump below.
    Category                         ABAP Programming Error
    Runtime Errors               RAISE_EXCEPTION
    ABAP Program               SAPLRRSI
    Application Component  BW-BEX-OT
    Error analysis                                                                                |
    A RAISE statement in the program "SAPLRRSI" raised the exception
    condition "X_MESSAGE".
    Since the exception was not intercepted by a superior
    program, processing was terminated.
    |                                          
    We are using BW 7.3. Pls help me ..Thanks in advance.
    Regards
    sri

    Hi,
    check following threads as well
    1. ST03N Raise Exception Shortdump when Access BI Workload
    2 See if you can activate the Infocube RSDG_CUBE_ACTIVATE
    3. CHECK if you have sufficient memory to work in case this is dev or test system
    4. check in RSRV in case there is any issue with design
    5. InfoCube Data not Visible in BI
    Go to Manage>Infocube content>Execute(you may not be able to see anything here)>in the menu (where DETAILS, SORTING)etc are available click on the 10th option> CHANGE LAYOUT--> You may not have anything selected at the left pane in this pop up window.
    Select all or your desired objects from COLUMN SET to DISPLAYED COLUMNS. Click on the tick mark & ow see.I think it'll help u...
    As suggested you may have some authorization issue.
    Thanks and regards
    Kiran

  • Short dump while executing info package in 3.5 data flow?

    Hi,
    i am getting short dump while executing info package while executing info package. it was working perfectly 2 days back suddenly it is giving this problem. it is a full load for info object text data and i have only 600 records. when i tried with " only info package" it is working perfectly n bringing the data into PSA. But when i use "PSA and the into data target" it is giving short dump.
    i replicated Data source and also i activated transfer rules, update rules still it is not working. When i check with another info objects it is working perfectly fine. i dont know what is wrong with only particular info object.
    Please find attached short dump.
    Thanks

    Hi,
    When you load transaction data I think there is a deadlock.
    Check in the process overview (transaction SM50) the waiting processes are in program SAPLSENA .
    The program SAPLSENA is the lock handler tool.
    Also check if  ACR is running on this target while your load is happening.
    Check in SM12 if there are any lock entries for the Infoobject to which you are loading data and on RSICCONT table .
    Try reloading after deleting the locks manually.
    Regards.

  • Short dump MESSAGE_TYPE_X in displaying data from BPC Virtualcube

    Hi Experts,
    I am experiencing an error when try to display data from a BPC VirtualProvider Infocube (both from Workbench and with LISTCUBE transaction).
    This kind of virtualcube is auto generated by BPC.
    When I do some kind of selection I obtain this error: MESSAGE_TYPE_X
    Short text of error message:
    System error in program SAPLRRK0 and form CHECK_KHANDLE (see long text)
    Technical information about the message:
    Message class....... "BRAIN"
    Number.............. 299
    Variable 1.......... "SAPLRRK0"
    Variable 2.......... "CHECK_KHANDLE"
    I have another BPC vitualprovider and this doesnu2019t happen.
    I would use this cube inside a multiprovider, that has a BI cube too, and get the data through a BEx query. But the query throws the error and stopped.
    I know that there could be problems with BPC structures (i.e. changes in tech name when transporting it), but at the moment I donu2019t see other solution to compare BI to BPC data.
    I went through other posts in sdn forum for this issue, but I am not able to get the exact solution,
    please help
    Thanks,
    Marco
    System version:
    BW:     701 level 0007
    BPC:     750 level 0005

    Hi Lokesh,
    I read the note you have indicated.
    For the first note 1479393: I donu2019t have hierarchies and the error appears in a different program to what is indicated in the note. This is where terminated:
    Termination occurred in the ABAP program "SAPLRRK0" - in "CHECK_KHANDLE".
    The main program was "GP4LQ7N6RS4RUB6HA69UREYGPKB ".
    In the source code you have the termination point in line 34
    of the (Include) program "LRRK0F05".
    Furthermore, there are no calculated measures nor members in the MDX statement, because I just try to display the data from the virtualcube.
    For the second 1448691: yes, it could be a performance related problem. Indeed, when I apply stronger filters, the error doesnu2019t occur and I got the data. But the system is already patched to SAPKW70107.
    So, do you have any other ideas?
    Thanks,
    Marco

  • Getting short dumps while reading bulky data from excel sheet

    Hi all,
    We have converted our non-unicode based sap system (R/3 4.7, Windows 2003,
    SQL 2000) into a unicode based system recently. We are facing two peculiar
    problems for last few days.
    *Problem 1 - *Whenever we want to upload the data from excel sheet, the
    system throws a dump after reading about 400 entries, while last week the
    same system used to read about 8000 entries in a single go.
    *Problem 2 - *Also, whenever we realease a transport requst from development
    containing a lot of changes, the request will reach the quality system but
    without the changes. but if i ll try to import the changes into quality
    system after generating more than one request containing small small
    changes, they get reflected in QAS immediately. Is there any size
    constraint in transporting a request fro DEV->QAS->PRD.
    Please suggest some ways.
    I am pasting the dump (that I am getting while data uploading from Excel).
    ~~~~~~~~~~~~~~~~~~
    Runtime errors
    MESSAGE_TYPE_X*
    Occurred on
    22.02.2008 at
    13:21:02*
    The current application triggered a termination with a short dump.
    What happened?
    The current application program detected a situation which really
    should not occur. Therefore, a termination with a short dump was
    triggered on purpose by the key word MESSAGE (type X).
    What can you do?
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    Error analysis
    Short text of error message:
    Control Framework : Error processing control
    Technical information about the message:
    Diagnosis
    An error occurred when the system tried to process the commands
    from the Automation Queue on the presentation server.
    There are several possible reasons for this:
    - The installation of the SAP GUI on the presentation server is
    faulty or obsolete.
    - There is an error in the application program
    - There is an error in the SAPGUI or an integrated control
    Procedure
    1. Make sure that you have imported the appropriate Support
    Package, the current kernel, and GUI patch for the release of your
    System
    2. Check whether the error occurs locally on one or a few PCs, or
    generally on all PCs. Note whether the error only occurs for some
    users, for example because of a specific Customizing setting.
    If it only occurs locally, this suggests an installation problem
    with the PC. Check the installation; if necessary, reinstall the
    software. In the dump, search for the SY-MSGLI field, since it may
    point to the cause of the error.
    3. Activate the Automation Trace (in accordance with SAP Note
    158985).
    4.Start the transaction and continue until the screen immediately
    before the dump.
    5. From the System -> Utilities menu, choose Autom. Queue,
    Synchronous Processing.
    The status bar of the GUI displays the text:
    "Automation synchron flush mode on"
    6. If you now proceed with the application, the short dump will
    display the ABAP call that caused the error; the Automation Trace
    will contain the error on the presentation server.
    7. If necessary, load the short dump and trace files on to
    sapservX, so that SAP can analyze them.
    Message classe...... "CNDP"
    Number.............. 006
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    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,
    use the following search criteria:
    "MESSAGE_TYPE_X" C
    "SAPLOLEA" or "LOLEAU02"
    "AC_SYSTEM_FLUSH"
    If you cannot solve the problem yourself, please send the
    following documents to SAP:
    1. A hard copy print describing the problem.
    To obtain this, select the "Print" function on the current screen.
    2. A suitable hardcopy prinout of the system log.
    To obtain this, call the system log with Transaction SM21
    and select the "Print" function to print out the relevant
    part.
    3. If the programs are your own programs or modified SAP programs,
    supply the source code.
    To do this, you can either use the "PRINT" command in the editor or
    print the programs using the report RSINCL00.
    4. Details regarding the conditions under which the error occurred
    or which actions and input led to the error.
    System environment
    SAP Release.............. "620"
    Application server....... "nhbho930"
    Network address.......... "192.168.0.30"
    Operating system......... "Windows NT"
    Release.................. "5.2"
    Hardware type............ "4x Intel 801586"
    Character length......... 16 Bits
    Pointer length........... 32 Bits
    Work process number...... 0
    Short dump setting....... "full"
    Database server.......... "NHBHO930"
    Database type............ "MSSQL"
    Database name............ "DEV"
    Database owner........... "dev"
    Character set............ "C"
    SAP kernel............... "640"
    Created on............... "Aug 17 2007 00:18:58"
    Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version......... "SQL_Server_8.00 "
    Patch level.............. "196"
    Patch text............... " "
    Supported environment....
    Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
    SAP database version..... "640"
    Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,
    Windows NT 6.0"
    User, transaction...
    Client.............. 300
    User................ "NHBABAP"
    Language key........ "E"
    Transaction......... "SE38 "
    Program............. "SAPLOLEA"
    Screen.............. "SAPMSDYP 0010"
    Screen line......... 0
    Information on where terminated
    The termination occurred in the ABAP program "SAPLOLEA" in
    "AC_SYSTEM_FLUSH".
    The main program was "ZBDC_CONTRACT ".
    The termination occurred in line 29 of the source code of the (Include)
    program "LOLEAU02"
    of the source code of program "LOLEAU02" (when calling the editor 290).
    ~~~~~~~~~~~~~~~~~~~~~
    Thank you all.
    Cheers.
    Mitra __.____._

    for the 50 millionth time: Excel spreadsheets are NOT databases, you should NOT try to use them as such and NEVER access them using JDBC.
    You should also under NO condition use the JDBC-ODBC bridge driver (that was actually the 78 millionth time that was told someone).

  • Getting short dump at the time of loading data from R/3 to ODS

    Hi BW Grurus,
    I am trying to load data from R/3 to ODS, but after running for a few minutes it is getting into the short dump and displays the following run time error. So please give me solution how I can load data without getting short dump. I tried thrice but it is giving the same and failed.
    Run time error : TSV_TNEW_PAGE_ALLOC_FAILED

    Hi,
    Check, is start routine or individual routine in present in update/transfer rule?
    May be read large amount data (select * from) another ODS and put into internal table cause these type of error.
    Regards,
    Saran

  • DBIF_REPO_SQL_ERROR short dumps while activating data in ODS

    Hi All,
    We are using BW3.5 with Oracle 9.2 on AIX 5.3 box, from the past few days we are getting DBIF_REPO_SQL_ERROR short dumps frequently while activating data in ODS.
    Runtime Error          DBIF_REPO_SQL_ERROR
    Date and Time          08.01.2008 13:01:08
         1. A printout of the problem description (short dump)
            To obtain this, select in the current display "System->List->
            Save->Local File (unconverted)".
         2. A suitable printout of the system log
            To obtain this, call the system log through transaction SM21.
            Limit the time interval to 10 minutes before and 5 minutes
            after the short dump. In the display, then select the function
            "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, select the Editor function "Further Utilities->
            Upload/Download->Download".
         4. Details regarding the conditions under which the error occurred
            or which actions and input led to the error.
         Internal call code.........: "[REPO/*/43/LOAD/CX_SY_OPEN_SQL_DB=============CP
         Please check the entries in the system log (Transaction SM21).
         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,
         use the following search criteria:
         "DBIF_REPO_SQL_ERROR" C
         "SAPLRSSM_PROCESS" or "LRSSM_PROCESSF04"
         "CHECK_IF_ANALYZE_IS_NESSESSARY"
    System environment
        SAP Release.............. "640"
        Application server....... "psapdb"
        Network address.......... "158.58.65.11"
        Operating system......... "AIX"
        Release.................. "5.3"
        Hardware type............ "00CD615C4C00"
        Character length......... 16 Bits
        Pointer length........... 64 Bits
        Work process number...... 22
        Short dump setting....... "full"
        Database server.......... "psapdb"
        Database type............ "ORACLE"
        Database name............ "BWP"
        Database owner........... "SAPBWP"
        Character set............ "C"
        SAP kernel............... "640"
        Created on............... "Oct 29 2006 20:49:57"
        Created in............... "AIX 1 5 00538A4A4C00"
        Database version......... "OCI_920 "
        Patch level.............. "155"
        Patch text............... " "
        Supported environment....
        Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
         10.2.0.."
        SAP database version..... "640"
    Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
    Memory usage.............
    Roll..................... 16192
    EM....................... 16759424
    Heap..................... 0
    Page..................... 24576
    MM Used.................. 6604384
    MM Free.................. 1772536
    SAP Release.............. "640"
    User and Transaction
        Client.............. 200
        User................ "R3REMOTE"
        Language key........ "E"
        Transaction......... " "
        Program............. "SAPLRSSM_PROCESS"
        Screen.............. "SAPMSSY0 1000"
        Screen line......... 6
    Information on where terminated
        The termination occurred in the ABAP program "SAPLRSSM_PROCESS" in
         "CHECK_IF_ANALYZE_IS_NESSESSARY".
        The main program was "RSPROCESS ".
        The termination occurred in line 1143 of the source code of the (Include)
         program "LRSSM_PROCESSF04"
        of the source code of program "LRSSM_PROCESSF04" (when calling the editor
         11430).
        The program "SAPLRSSM_PROCESS" was started as a background job.
        Job name........ "BI_PROCESS_ODSACTIVAT"
        Job initiator... "RPRIYANKA"
        Job number...... 02010102
    Also we have a failed job here. Here is the job log.
    Job log overview for job:    BI_PROCESS_ODSACTIVAT / 02010102
    Date       Time     Message text
    08.01.2008 13:01:00 Job started
    08.01.2008 13:01:00 Step 001 started (program RSPROCESS, variant &0000000000188, user ID R3REMOTE)
    08.01.2008 13:01:02 Activation is running: Data target HBCS_O25, from 1,758 to 1,767
    08.01.2008 13:01:02 Data to be activated successfully checked against archiving objects
    08.01.2008 13:01:02 SQL: 01/08/2008 13:01:02 R3REMOTE
    08.01.2008 13:01:02 ANALYZE TABLE "/BIC/AHBCS_O2540" DELETE
    08.01.2008 13:01:02 STATISTICS
    08.01.2008 13:01:02 SQL-END: 01/08/2008 13:01:02 00:00:00
    08.01.2008 13:01:02 SQL: 01/08/2008 13:01:02 R3REMOTE
    08.01.2008 13:01:02 BEGIN DBMS_STATS.GATHER_TABLE_STATS ( OWNNAME =>
    08.01.2008 13:01:02 'SAPBWP', TABNAME => '"/BIC/AHBCS_O2540"',
    08.01.2008 13:01:02 ESTIMATE_PERCENT => 1 , METHOD_OPT => 'FOR ALL
    08.01.2008 13:01:02 INDEXED COLUMNS SIZE 75', DEGREE => 1 ,
    08.01.2008 13:01:02 GRANULARITY => 'ALL', CASCADE => TRUE ); END;
    08.01.2008 13:01:05 SQL-END: 01/08/2008 13:01:05 00:00:03
    08.01.2008 13:01:05     SQL-ERROR: 603 ORA-00603: ORACLE server session terminated by fat al error
    08.01.2008 13:01:05 System error: RSDU_ANALYZE_TABLE_ORA/ ORACLE
    08.01.2008 13:01:08 ABAP/4 processor: DBIF_REPO_SQL_ERROR
    08.01.2008 13:01:08 Job cancelled
    Listener is working fine, Checked the RFC connections, Tried restarting the system, tried adding space to the TEMP tablespace as well as PSAPBWP, but they didn't work.
    Please help.

    The problem got solved as there were DB errors like ORA-01114: IO error writing block to file 256 (block # 126218).
    Here the point to be notes is file 256. The number greater than 255 indicates a temp datafile. This indicates an issue with PSAPTEMP tablespace. When checked on PSAPTEMP tablespace, one of the filesystems where one temp data file sitting was full. The filesystem was 100% full. This will prevent the temp datafile to grow and shrink as and when required.
    So, adding more space to the filesystem solved the problem.
    Thanks to everyone who have shown interest in solving my problem.

  • Short Dump in SAP BW Sys while extracting data from R/3

    HI All,
    I am getting short dump problem in sap bw while extracting the data from r/3 to bw info cube.
    the error message is like this,
    Runtime Error          DBIF_RSQL_SQL_ERROR
    Except.                CX_SY_OPEN_SQL_DB
    Date and Time          11.05.2011 09:36:51
    ShrtText
    An SQL error occurred when accessing a table.
    What can you do?
    Make a note of the actions and input which caused the error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    How to correct the error
    Database error text........: "ORA-14400: inserted partition key does not map to
    any partition"
    Internal call code.........: "[RSQL/INSR//BIC/B0000115000 ]"
    Please check the entries in the system log (Transaction SM21).
    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,
    use the following search criteria:
    "DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC
    "GPCX2UNC5JG556R7DPSFJUGJS1Z" or "GPCX2UNC5JG556R7DPSFJUGJS1Z"
    |    "INSERT_ODS"                
    If you cannot solve the problem yourself and you wish to send
    an error message to SAP, include the following documents:
    1. A printout of the problem description (short dump)
    To obtain this, select in the current display "System->List->
    Save->Local File (unconverted)".
    2. A suitable printout of the system log
    To obtain this, call the system log through transaction SM21.
    Limit the time interval to 10 minutes before and 5 minutes
    after the short dump. In the display, then select the function
    "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, select the Editor function "Further Utilities->
    Upload/Download->Download".
    4. Details regarding the conditions under which the error occurred
    or which actions and input led to the error.
    The exception must either be prevented, caught within the procedure
    "INSERT_ODS"
    "(FORM)", or declared in the procedure's RAISING clause.
    To prevent the exception, note the following:
    System environment
    SAP Release.............. "640"
    Application server....... "bwdev"
    Network address.......... "10.10.100.36"
    Operating system......... "Windows NT"
    Release.................. "5.2"
    Hardware type............ "8x AMD64 Level"
    Character length......... 8 Bits
    Pointer length........... 64 Bits
    Work process number...... 0
    Short dump setting....... "full"
    Database server.......... "BWDEV"
    Database type............ "ORACLE"
    Database name............ "BWD"
    Database owner........... "SAPR3"
    Character set............ "English_United State"
    SAP kernel............... "640"
    Created on............... "Aug 17 2008 20:56:58"
    Created in............... "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
    Database version......... "OCI_10201_SHARE "
    Patch level.............. "247"
    Patch text............... " "
    Supported environment....
    Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
    10.2.0.."
    SAP database version..... "640"
    Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,
    Windows NT 6.0"
    Memory usage.............
    Roll..................... 16128
    EM....................... 6265200
    Heap..................... 0
    Page..................... 0
    MM Used.................. 5972296
    MM Free.................. 289384
    SAP Release.............. "640"
    User and Transaction
    Information on where terminated
    The termination occurred in the ABAP program "GPCX2UNC5JG556R7DPSFJUGJS1Z" in
    "INSERT_ODS".
    The main program was "SAPMSSY1 ".
    The termination occurred in line 41 of the source code of the (Include)
    program "GPCX2UNC5JG556R7DPSFJUGJS1Z"
    of the source code of program "GPCX2UNC5JG556R7DPSFJUGJS1Z" (when calling the
    editor 410).
    Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
    the
    procedure "INSERT_ODS" "(FORM)" but was not handled locally, not declared in
    the
    RAISING clause of the procedure.
    The procedure is in the program "GPCX2UNC5JG556R7DPSFJUGJS1Z ". Its source code
    starts in line 21
    |    of the (Include) program "GPCX2UNC5JG556R7DPSFJUGJS1Z ".

    Hi,
    This error  occurs if you want to insert an entry in the table that does not match the value range of any partition. In such a case, you must compare the value of the entry with the definitions of the partitions to determine the cause of the error.
    please run the following test/repair in transaction RSRV ,
    RSRV -> All Elementary Test -> PSA Tables -> Consistency Between PSA Partitions and SAP Administration  Information
    -> include the PSA table
        /BIC/B0000115000
    Check OSS note 339896 which explains  the repair procedure.
    Regards,
    Lokesh

  • Short dump error for delta load to 0CFM_C10 via 0CFM_DELTA_POSITIONS flow

    hi all,
    i am getting short dump error for delta load to 0CFM_C10 via 0CFM_DELTA_POSITIONS flow.
    not able to figure out the actual issue and how to solve it.
    can anyone suggest?
    below is the details of the short dump
    Short text
        Exception condition "UNKNOWN_TRANSCAT" raised.
    What happened?
        The current ABAP/4 program encountered an unexpected
        situation.
    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.
    Error analysis
        A RAISE statement in the program "CL_SERVICE_TRG================CP" raised the
         exception
        condition "UNKNOWN_TRANSCAT".
        Since the exception was not intercepted by a superior
        program, processing was terminated.
        Short description of exception condition:
        For detailed documentation of the exception condition, use
        Transaction SE37 (Function Library). You can take the called
        function module from the display of active calls.
    How to correct the error
        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:
        "RAISE_EXCEPTION" " "
        "CL_SERVICE_TRG================CP" or "CL_SERVICE_TRG================CM003"
        "SORT_TRANSACTIONS"
        or
        "CL_SERVICE_TRG================CP" "UNKNOWN_TRANSCAT"
        or
        "SBIE0001 " "UNKNOWN_TRANSCAT"
        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.

    Hi,
    It seems like some routine are there and check your rotines , transformation etc.
    Regards
    sivaraju

Maybe you are looking for