Message_type_x short dump while deleting request from infocube

Hi,
While deleting one of the erroneous requests from some infocubes,
system is resulting in short dump "MESSAGE_TYPE_X".
This is happening only with respect to some infocubes.
Description of short dump:
Short text of error message:                                            
System error in program RSMDATASTATE and form RSM_DATASTATE_CHECK-5- (see long text)  
Can any one of you please help with this?
Regards,
Nilima Rodrigues

Hi NILIMA,
I got same problem with my InfoPackage  last month with same error msg.
that error come due to data inconstancy in data base table.
in my case i am unable to open my InfoPackage  and after double clicking it was giving dump with same error.
If u know abap then just change the sy-subrc value from 4 to 0 before dump line code it will resolve your problem.
for this on dump screen click on debugger button then it opens your code and shows line on which u getting dump with table name check your entry in table ok
if u unable u find table then do one thing just put break point before dump line and open fresh rsa1 and go to same cube and double click it will stop on your debugger point just press f5 button it shos sy-subrc 4 convert it to 0 and press edit button and press f8 .
Regards
Ankit

Similar Messages

  • Error while deleting request from DSO: S:RSODSO_ROLLBACK:259

    Hi,
    While deleting request from DSO, we face following errors:
    S:RSODSO_ROLLBACK:259                129 transaction rolled back by an internal error: fail
    Message no. RSODSO_ROLLBACK259
    Job is getting completed with message:
    Deletion of request REQU_3HHPSMIMMVRF87FI0EGC5CS4B from data target ZPR_ODS failed
    Deletion of request REQU_3T80EDOBQR7CWSC8QKKHAMH5N from data target ZPR_ODS failed
    Deletion of request REQU_8JIMF8SRDOG0T3QG6AGRA63Q3 from data target ZPR_ODS failed
    Deletion of request REQU_CMCCHOZGOF3KXNMVXB94ZHMCB from data target ZPR_ODS failed
    Deletion of request REQU_BPCAB8LY6V4CMC3XQ12AWN7MJ from data target ZPR_ODS failed
    <Message short text RSODSO_ROLLBACK 259 does not exist>
    Parallel processes (for Rollback); 000003
    Timeout for parallel process (for Rollback): 000600
    Package size (for Rollback): Dependent on Activation
    Task handling (for Rollback): Backgr Process
    Server group (for Rollback): No Server Group Configured
    Job finished
    FYI:
    Kindly help us to resolve the error.
    Regards,
    Antony Jerald.

    Hi Dinesh,
    Thanks for your reply.
    We have Netweaver 7.30 with BW on hana on SP 9.
    First 3 SAP notes doesn't meets the need.
    Shall I use 1007717 note? 
    Which says:
         use transaction SE16 to delete all entries for this request and for this Operational Data Store (ODS) object from the RSICCONT, RSMONICDP, RSODSACTUPDTYPE and RSODSACTREQ tables. Then set the 'from-date' in the administration of the data target to a value older than the oldest request loaded in this ODS object. Choose 'Refresh'. This corrects the administration.
    Will it resolves the problem?
    Kindly suggest.
    Regards,
    Antony Jerald.

  • Regarding Short Dump While loading data from DB Connect

    Dear All,
    We are having an issue of getting short dump while loading data from DB Connect to BW. We were able to load the data into BW Dev using the same data source without any problem. Whereas in Production, I am getting the following error:
    Runtime Error          PERFORM_CONFLICT_TAB_TYPE  
    Except.                   CX_SY_DYN_CALL_ILLEGAL_TYPE
    What could be the reason for the error that I am getting

    hi,
    Refer Note 707986 - Writing in trans. InfoCubes: PERFORM_CONFLICT_TAB_TYPE
    Summary
    Symptom
    When data is written to a transactional InfoCube, the termination PERFORM_CONFLICT_TAB_TYPE occurs. The short dump lists the following reasons for the termination:
    ("X") The row types of the two tables are incompatible.
    ("X") The table keys of the two tables do not correspond.
    Other terms
    transactional InfoCube, SEM, BPS, BPS0, APO
    Reason and Prerequisites
    The error is caused by an intensified type check in the ABAP runtime environment.
    Solution
    Workaround for BW 3.0B (SP16-19), BW 3.1 (SP10-13)
    Apply the attached correction instructions.
    BW 3.0B
    Import Support Package 20 for 3.0B (BW3.0B Patch20 or SAPKW30B20) into your BW system. The Support Package is available oncenote 0647752 with the short text "SAPBWNews BW3.0B Support Package 20", which describes this Support Package in more detail, has been released for customers.
    BW 3.10 Content
    Import Support Package 14 for 3.10 (BW3. 10 Patch14 or SAPKW31014) into your BW system. The Support Package is available once note 0601051 with the short text "SAPBWNews BW 3.1 Content Support Package 14" has been released for customers.
    BW3.50
    Import Support Package 03 for 3.5 (BW3.50 Patch03 or SAPKW35003) into your BW system. The Support Package is available once note 0693363 with the short text "SAPBWNews BW 3.5 Support Package 03", which describes this Support Package in more detail, has been released for customers.
    The notes specified may already be available to provide advance information before the Support Package is released. However, in this case, the short text still contains the term "Preliminary version" in this case.
    Header Data
    Release Status: Released for Customer
    Released on: 18.02.2004 08:11:39
    Priority: Correction with medium priority
    Category: Program error
    Primary Component: BW-BEX-OT-DBIF Interface to Database
    Secondary Components: FIN-SEM-BPS Business Planning and Simulation
    Releases
    Software
    Component Release From
    Release To
    Release And
    subsequent
    SAP_BW 30 30B 30B
    SAP_BW 310 310 310
    SAP_BW 35 350 350
    Support Packages
    Support
    Packages Release Package
    Name
    SAP_BW_VIRTUAL_COMP 30B SAPK-30B20INVCBWTECH
    Related Notes
    693363 - SAPBWNews BW SP03 NW'04 Stack 03 RIN
    647752 - SAPBWNews BW 3.0B Support Package 20
    601051 - SAPBWNews BW 3.1 Content Support Package 14
    Corrections Instructions
    Correction
    Instruction Valid
    from Valid
    to Software
    Component Ref.
    Correction Last
    Modifcation
    301776 30B 350 SAP_BW J19K013852 18.02.2004 08:03:33
    Attributes
    Attribute Value
    weitere Komponenten 0000031199
    Thanks
    (Activate ODS/Cube and Transfer rules again..)

  • Short dump while reconstructing request in ODS

    Hi
    I had loaded a request into a few ODS, but later found i had to do some changes to the PSA manually, so i deleted the request from all the ODS and modified the records in the PSA.
    Now when i try reconstruction it gives a short dump in one of the ODS with message  "Exception condition "NOT_EXIST" raised. ".
    Data from this ODS was further loaded to a few other targets as delta and while deleting the request it gave a message saying the delta will be deactivated, I said Ok and the request was deleted.
    I was able to reconstruct the request in all the other ODS and cubes without any issues. 
    what could be the problem???
    Regards
    Sujai

    Hi
    I am doing PSA to ODS. The data is available in PSA. the reconstruction went thru fine in the other targets. but when i try it in the ODS that i want it goes for a dump. This is where the error occurs.. shown in the dump..
    select * from rsreqicods into table l_t_rsreqicods where   
            tabname = i_dta and                                 
            typ     = 'I' and                                   
            odssid  = i_odssid.                                 
    if sy-subrc <> 0.                                          
       raise not_exist. -----> Error in this line                                    
       exit.                                                    
    endif.     
    Regards
    Sujai

  • Short Dump while loading Delta from ODS to ODS

    Hi Experts,
    I have run into a short dump error while loading delta from one ODS to another via a process chain.
    Following is the error message:
    Error analysis                                                                               
    Short text of error message:                                                                 
        Request 0000259294 is not completely activated. Please activate it again                     
    Technical information about the message:                                                     
         Diagnosis                                                                               
    Activation of request 0000259294 has terminated, or is not yet                          
             complete.                                                                               
    System response                                                                               
    Procedure                                                                               
    If the process has terminated, all of the requests that the system                      
             was unabe to activate in the most recent activation process have to                     
             be reactivated before the new requests can be activated.                                
             If you are not able to carry out this activation step, delete the                       
             relevant requests from the administration of the ODS object (on the                     
             Requests tabstrip).                                                                     
         Procedure for System Administration                                                         
        Message classe...... "RSM1"                                                                  
        Number.............. 180                                                                     
        Variable 1.......... 0000259294                                                              
        Variable 2.......... " "                                                                     
        Variable 3.......... " "                                                                     
        Variable 4.......... " "                                                                     
        Variable 3.......... " "                                                                     
        Variable 4.......... " "                                                                     
    Can someone help me resolve this?
    Thank you

    Check the status of request SID 259294  in ODS, whether the Activation got completed or not. If not wait till the activation completes.
    If there is any problem in the activation process, correct that complete the activation process and load the ne request that you want to load..
    Regards
    VJ

  • Short Dump while fetching values from a Database view

    Hi ALL,
    Here is the code that is giving short dump
    SELECT * FROM ZVMATLMOVE INTO TABLE I_MATLMOVE
        WHERE BUDAT >= V_LASTRUN_DATE
        AND   WERKS IN S_WERKS
        AND   LIFNR IN S_LIFNR
        AND   EBELN IN S_EBELN
        AND   MATNR IN S_MATNR
        AND   BWART IN S_BWART
    (Please don't say that I am using * in the select query,
    I knew that it is not a good way of fetching values)
    Declaration of the internal table is:
    DATA  I_MATLMOVE LIKE ZVMATLMOVE OCCURS 0 WITH HEADER LINE.
    The variable V_LASTRUN_DATE is:
    DATA  V_LASTRUN_DATE LIKE SY-DATUM.
    We will be getting the lastrundate value from another table. And it is passing correct value (ex. 20060731)
    ZVMATLMOVE is a database view created for MKPF and MSEG table. And I checked both table were consistent.
    Dump Analysis:
    Runtime errors         DBIF_RSQL_SQL_ERROR          
    Exception              CX_SY_OPEN_SQL_DB
    Every thing is fine. But I don't know how it is going to dump. Any suggestions?

    Hi !
    It seams that your table is not correct / fully activated.
    To check it out you should try the following:
    - Go to the SE11
    - Give it your table name and go to "Display"
    - Check if the table is "active"
    - Choose "Utilities->Database Object->Check" and see
      if there are any errors
    - go back and choose "Utilities->Runtime Object->Check"
      and see if there are any errors
    If there are any errors - try to activate the table again. You may need the "Utilities->Database Utiliy" for that.
    After there are no more errors by checking all these your program should work.
    Regards
    Rainer
    Some points would be nice if thate helped a bit.

  • Error  While  Deleting Data  From ODS

    Hi all,
    We are getting short dump while deleting data from a perticular ODS.
    Part of short dump is--
    trigger Location of Runtime Error
       Program                                 SAPLRSAC
       Include                                 LRSACU75
       Row                                     535
       Module type                             (FUNCTION)
       Module Name                             RSAR_TRANSTRUCTURE_ACTIVATE
    help is desperately required
    Regards
    Srini--

    try to activate InfoSource and later delete data.
    Check if all ODS related objects are consistent and active.
    also pls attached the whole dump for more clarity if this does not work.

  • Short dump while loading master data (0material_attr).

    Hi,
    I am experiencing a short dump while loading 0matrial_attr from R/3.
    Name of the runtime error :
    DBIF_RSQL_SQL_ERROR
    program is generating exception at this point.
    ***Try to insert the records into the ODS table
    INSERT /BIC/B0002905000 FROM TABLE L_T_DATA.
    pls help me.

    Hi,
    I am sure I am looking at the proper dump.
    the code I have pasted is the standard code.. which I get to see in the dump analysis.
    ******************************dump analysis*********************************
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
    neither
    caught nor passed along using a RAISING clause, in the procedure "INSERT_ODS"
    "(FORM)"
    Since the caller of the procedure could not have expected this exception
    to occur, the running program was terminated.
    The reason for the exception is:
    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:
    Database error text........: "ORA-14400: inserted partition key does not map to
    any partition"
    Internal call code.........: "[RSQL/INSR//BIC/B0002905000 ]"
    Please check the entries in the system log (Transaction SM21).
    system log in SM 21 is below**************
    After the attempt to access a database table the database system has
    returned an error code which indicates that the operation concerned
    could not be performed successfully.

  • Delete Overlapping Request from InfoCube.

    Hello,
    I am using process Type "Delete Overlapping Request from infocube" in this I am selecting object type as a "DTP"
    Under "Delete Selection" I am selecting following
    1. Only Delete Requests from same DTP
    2. Only Delete Full DTP request
    3. Only Delete DTP Requests from Same Source
    I am using "Full Load" in my DTP.
    My requirements are like  I need to delete old data and load new data every day in to  a cube for that I am using this process type.
    If anybody have better solution please let me know.
    Thanks,

    Also
    I am not deleting Index  OR  Not creating Indexs while using process type "Deleting overlapping request InfoCube"
    what will be the impact on the cube?
    How many index will have infocube?
    If the cube having more than one index if i delete index, which index will be deleted?
    Thanks,

  • Delete Overlapping Requests from InfoCube: Before or After the Generate Ind

    Hi,
    Delete Overlapping Requests from InfoCube Before or After the Generate Index of the Infocube? Why?
    I think "After", but the system (transaction RSPC)suggest 1.Generate Index 2.Overlapping Requests from InfoCube ...
    Thanks
    Alessandro

    Hi Alessandro,
       Bottom Line Index will speed up the Process. While loading the Data you need to delete the Index.
    Index will degrade the performence while updating or modifying DB Entries(Loading). Index will improve the performence while reading the DB(Reporting).
    It's not with BW. all RDBMS need this.
    Regards,
    Nagesh.

  • Unable to automate deletion of old data (requests) from InfoCube using a PC

    Each week I copy open Notifications into a 'SnapShot' cube, from the Transaction Cube, using the current date to make it a unique copy/snapshot for that week.  This is then reported on showing, amongst other things, the trend of open Notifications throughout the year.
    In an effort to ensure this doesn't grow too big, I will only keep a rolling 52 weeks of data.  I thought I could use a feature available when creating Process Chains called 'Delete Overlapping Requests from InfoCube' to manage the amount of data held (52 weeks only).
    The variant used to delete the requests has been created linked to object type 'Data Transfer Process' (DTP) and the actual DTP used to load the  'SnapShot' cube ... I then click the 'delete selections' button.  On the next window I select 'Request Selection Through Routine', then click 'Change Routine'.  I entered the following code, which I borrowed from another thread:
    data: datum(16) type c,
    date type sy-datum.
    date = sy-datum.
    date = date - 365.
    break-point.
    concatenate date sy-uzeit into datum.
    loop at l_t_request_to_delete.
    delete l_t_request_to_delete where timestamp gt datum.
    endloop.
    append l_t_request_to_delete.
    p_subrc = 0.
    I get a message saying "No Requests for deletion were found'.  Any ideas?

    HI Tony,
    Please check whether the timestamp value you are popolating i filed datum with the following statement:
    concatenate date sy-uzeit into datum.
    has same data format and type as the timestamp for the request.
    If this is not same then you will not be able to find any request corresponding to timestamp.
    - Geetanjali

  • Duplicate records: Process : Delete Overlapping Requests from InfoCube

    Hi Experts,
    We are loading data in standard costing cube with standard available option Full upload. In our process chain we have included process type "Delete Overlapping Requests from InfoCube". In our scenario we always load yesterday and today's data. In this case after loading yesterday's data, we need to check and delete the overlapping requests and then upload todays data.
    Many a times this deletion process is failing due to message "Couldn't lock cube" because it is already locked by user "ALEREMOTE". This cause system to duplicate the records in cube.
    How we can avoid this?
    Alok

    I tried running again and it again failed. Checked in SM12 and found this entry
    800     ALEREMOTE     08/14/2007     E     RSENQ_PROT_ENQ     CREA_INDX      ZCCA_C11                      DATATARGET     CREA_INDX                     ######################################     0     1
    This locked is not released since 14th. Is there way to remove the lock using some process.

  • Process Maintenance: Delete Overlapping Requests from InfoCube

    Hi Experts,
    How can I open Process Maintenance: Delete Overlapping Requests from InfoCube Screen? What's T-code? Is that in Process Chain? Please tell me that....
    Thanks in advance,

    Hi
    'Delete overlapping request' is an option(its a process type) in the process chains..
    RSPC>Process types>Load Process and post process folder--->Delete overlapping request from the infocube..
    here you can have more options like 'source systems are same',and infosources are same etc...
    How to delete most recent request in a Cube by using process chain
    Hope it helps
    Thanks,
    Teja
    Edited by: Teja badugu on Apr 28, 2008 11:35 AM

  • Problems with delete overlapping requests from InfoCube in PC

    Hi guys,
    Iu2019m using delete overlapping requests from InfoCube in Process Chains, but Iu2019m not being able to adjust it to my specific requirement.
    For example:
    I execute DTP to load InfoCube XPTO with Fiscal Year 2008 and 2009. After this I have to load again, but only for 2009.
    In this specific example I want my process chain to delete the 2009 data from my first load, because it is overlapped, and leave 2008 data.
    Is this possible? If yes how?
    Thanks in advance
    Jão Arvanas

    It will not work that way.
    It will look if the selections are same then it wil delete if not then it will not do that activity.
    Overlapping settings which you might chosen is based on the delete overlapping for the same selections..
    So in this case the selections are different and hence its not possible.
    Thanks
    Murali

  • "Delete Overlapping Requests from InfoCube" in a Process Chain

    Dear all,
    I encountered a problem when I building the process chain in BW 3.0.
    In a process chain, I schedule daily an InfoPackage to load data to an InfoCube and then delete the previously loaded data by the same InfoPacckage from the InfoCube.
    For example, I have 2 InfoPacakge, A and B, and schedule to load data to InfoCube C. In the process chain, I scheduled daily the following tasks in sequence:
    - Delete index in InfoCube C
    - Load data through InfoPackage A to InfoCube C
    - Delete duplicated request previously loaded through InfoPackage A in InfoCube C
    - Load data through InfoPackage B to InfoCube C
    - Delete duplicated request previously loaded through InfoPackage B in InfoCube C
    - Create index in InfoCube C
    However, when I activate the process chain, a warning message is prompted: No type "Delete Overlapping Requests from InfoCube" process allowed infront of process "Execute InfoPackage" variable ZPAK_4GMFI
    Would anyone tell me why such warning message is prompted?
    Many thanks!
    Best regards,
    Marcus

    Hi all,
    Re Ranjan:
    I previously config the process chain like that:
    (1)   Delete index in InfoCube C
    (2)   Load data through InfoPackage A to InfoCube C
    (3a) Delete duplicated request previously loaded through InfoPackage A in InfoCube C
    (3b) Load data through InfoPackage B to InfoCube C
    (4)   Delete duplicated request previously loaded through InfoPackage B in InfoCube C
    (5)   Create index in InfoCube C
    where (3a) and (3b) is executed simultaneously.
    However, (3b) often reports error. I guess it may be due to the parallel run of (3a) and (3b). So that's why I set the process chain to be executed in serial.
    Re Jacob:
    I found that the process chain can be run even a warning message is prompted when activating the process chain!.
    Thanks you all for your kind support!!
    Best regards,
    Marcus

Maybe you are looking for