DSO Activation Time - "TIME_OUT"

Hello,
i've added a new InfoObject to an existing DSO.
Then, i saved the DSO and wanted to activate it.
Now to the problem:
The activation time is so long, that the process terminate.
So that we get the runtime error "TIME_OUT".
I ask for your help.
Regards
Marco

Hi Marco,
As you are trying to activate the DSO in front end and it is ending with time out error(This may be your DSO taking long time to activate).
activate using program  RSDG_ODSO_ACTIVATE
goto SE38-->give the program name and execute -->give the DSO name -->before you click on execute, in menu bar under execute click on execute in background.
in the next screen give the local printer name and enter.
In the next screen make the job condition as immediate and remove the periodic option and enter.
Now you can see the job in SM37, monitor this job until it's get finished.
Regards,
Venkatesh

Similar Messages

  • How to reduce dso activation time

    hi
    can any body explain  me how to reduce dso activation time.I am having a dso with 5 crore records and it is taking 7 to 8 hrs for activation.

    Hi,
    Try this.
    T.code RSCUSTA2 . Here you can change the no.of records and no.of processes to use for activation job with this you can increase your ODS activation process, here the no.of processes can be increased based on no.of processes available in your server, check in SM50 or SM51.
    ODS Query Performance  
    Thanks,
    JituK

  • How to reduce Time taken by DSO Activation.

    Hi
    My Inventory Transaction DSO taking nearly 18min for 180,000 records to activate. It means it takes 1 min for every 10,000 records to activate. I think its too much.
    Is there any way i can reduce DSO activation time... what are factors that increases the DSO activation Time.
    Pls let me know if u have some idea  this issue.
    Thanks.....

    Hi,
      Some of the factors which affect DSO activation are
    1) Data volume and size of DSO (if the volume and no of fields are more then it takes long time)
    2) SID generation(uncheck this if the DSO is not used for reporting)
    3) Secondary index (remove unwanted secondary index)
    4) No of background jobs and packages siz allocated for activation (check the settings for ur DSO in tcode RSODSO_SETTINGS)
    Apart from this it also depends on database performance and other factors
    Regards,
    Raghavendra.

  • DSO activation in Process Chains - takes long time

    Dear All,
    We have included DSO activation in Process Chains. This process takes a long time to execute. We manually cancel the corresponding process in Process Overview and repeat it from chain. The chain runs daily and this issue also occurs on a daily basis.
    Does anyone one of you have an idea of how to deal with this performance issue?
    Regards.

    Figure out in which class does your process fall in:
    Class A- High Priority
    Class B- Medium Priority
    Class C- Least Priority
    Background processes
    Class A jobs
    The number of work processes reserved for job class A is a subset of the number of background processes.
    You should only reserve work processes for job class A if it makes sense within your system organization. Work processes reserved for class A jobs are no longer available for job classes B or C.
    Set parallel processing for a specific BW process in the (variant) maintenance of the process
    Call the function for setting the parallel processes.
    You can call the function in the process variant maintenance of a process chain or in the process maintenance. The function call varies for the different BW processes.
    For example, in the data transfer process you call the function with Goto-->  Background Manager Settings.
    The Settings for Parallel Processing dialog box appears
      Under Number of Processes, define the maximum number of work processes that should be used to process the BW process.
    If you enter 1, the BW process is processed serially.
    If you enter a number greater than 1, the BW process is processed in parallel
    In the Parallel Processing group frame, make the relevant settings for parallel processing in the background:
    Enter a job class for defining the job priority.
    The job priority defines how the jobs are distributed among the available background work processes
      In the group frame Parallel Processing, you can define whether parallel processing should take place in dialog work processes or in background work processes for the processes ODSACTIVAT, ODSSID and ODSREQUDEL for the DataStore object
    Transport:
    The entries in tables RSBATCHPARALLEL and RSBATCHSERVER are written on a transport request of the Change and Transport System.
    Edited by: ram.pch on Oct 7, 2011 9:55 PM

  • How to improve the activation time for a standard DSO

    Hi all,
    I'm facing an issue related to the activation of a DSO. The SM37 log is as follows....
    12:03:16 Job started
    12:03:16 Step 001 started (program RSPROCESS, variant &0000000006946, user ID BWREMOTE)
    12:03:20 Attivazione is running: Data target ZFIZIASA, from 93,627 to 93,627
    12:18:00 Overlapping check with archived data areas for InfoProvider ZFIZIASA
    12:18:00 Data to be activated successfully checked against archiving objects
    12:18:02 Status transition 2 / 2 to 7 / 7 completed successfully
    12:18:13 Program RSBATCH_EXECUTE_PROZESS successfully scheduled as job BIBCTL_4IC45QJA588GKZ0M7JEJ3HCAR with ID 1218130
    12:18:19 Program RSBATCH_EXECUTE_PROZESS successfully scheduled as job BIBCTL_4IC45QJA588GKZ0M7JEJ3HCAR with ID 1218190
    12:18:20 Parallel processes (for Attivazione); 000003
    12:18:20 Timeout for parallel process (for Attivazione): 000300
    12:18:20 Package size (for Attivazione): 020000
    12:18:20 Task handling (for Attivazione): Processi batch
    12:18:20 Server group (for Attivazione): Nessun gruppo di server config
    12:18:20 Activation started (process is running under user BWREMOTE)
    12:18:20 Not all data fields were updated in mode "overwrite"
    12:18:20 Process started
    12:18:20 Process completed
    12:18:20 Activation ended
    Please have a look into the bold 3rd & 4th line. I couldnt able to analyse where the issue is and what to do to minimize the time for activation.
    It is very challenging, please reply!
    Please help.
    Thanks in adv.
    Ajay

    Hi Kundan,
    Thanks for the response!
    Actually, I have two identical DSO, having all the char & KF same and feeding the data from same DS at the same time but the issue is...
    1) For 1st DSO, Activation log....
    01.07.2010 02:02:41 Job started
    01.07.2010 02:02:41 Step 001 started (program RSPROCESS, variant &0000000006946, user ID BWREMOTE)
    01.07.2010 02:02:46 Attivazione is running: Data target ZFIZIASA, from 93,751 to 93,751
    01.07.2010 02:19:27 Overlapping check with archived data areas for InfoProvider ZFIZIASA
    01.07.2010 02:19:27 Data to be activated successfully checked against archiving objects
    01.07.2010 02:19:27 Status transition 2 / 2 to 7 / 7 completed successfully
    01.07.2010 02:19:28 Program RSBATCH_EXECUTE_PROZESS successfully scheduled as job BIBCTL_4ICC6UMXYT00Z2DYOQV8QL8CJ with ID 021
    01.07.2010 02:19:30 Parallel processes (for Attivazione); 000003
    01.07.2010 02:19:30 Timeout for parallel process (for Attivazione): 000600
    01.07.2010 02:19:30 Package size (for Attivazione): 020000
    01.07.2010 02:19:30 Task handling (for Attivazione): Processi batch
    01.07.2010 02:19:30 Server group (for Attivazione): Nessun gruppo di server config
    01.07.2010 02:19:30 Activation started (process is running under user BWREMOTE)
    01.07.2010 02:19:30 Not all data fields were updated in mode "overwrite"
    01.07.2010 02:19:30 Activation ended
    2) For 2nd DSO, the activation log is..
    01.07.2010 02:01:13 Job started
    01.07.2010 02:01:13 Step 001 started (program RSPROCESS, variant &0000000006947, user ID BWREMOTE)
    01.07.2010 02:01:35 Attivazione is running: Data target ZFIGL_02, from 93,749 to 93,749
    01.07.2010 02:01:43 Overlapping check with archived data areas for InfoProvider ZFIGL_02
    01.07.2010 02:01:43 Data to be activated successfully checked against archiving objects
    01.07.2010 02:01:53 Program RSBATCH_EXECUTE_PROZESS successfully scheduled as job BIBCTL_4ICCAR91ALHE1VHSB6GV9PAPV with ID 02015300
    01.07.2010 02:01:54 Program RSBATCH_EXECUTE_PROZESS successfully scheduled as job BIBCTL_4ICCAR91ALHE1VHSB6GV9PAPV with ID 02015400
    01.07.2010 02:01:56 Program RSBATCH_EXECUTE_PROZESS successfully scheduled as job BIBCTL_4ICCAR91ALHE1VHSB6GV9PAPV with ID 02015600
    Now my client is asking to lower the activation time for 1st one as it is taking for 2nd one.
    I'm toatally blank now that what & how to do it!
    The volume of data ...
    ZFIZIASA
    Active table - Number of entries: 13.960.508
    Change Log Table - Number of entries: 13.976.530
    ZFIGL_02
    Active Table - Number of entries: 21.923.947
    Change Log table - Number of entries: 21.938.657
    Thanks,
    ajay
    Edited by: sap.ajaykumar on Jul 6, 2010 1:47 PM

  • How to improve performance of DSO activation

    Hi all,
    We have created a DSO which is updated daily from another DSO. The extraction is from the Active table of the source DSO, so all records are extracted, in this case roughly 1,000,000 records. (we cannot use delta update for this particular DSO)
    Because of the large number of records, the activation of the data in the target DSO is quite slow (ca 20 minutes).
    My question: Is there any way that we can analize where exactly the time is lost during the activation and how we can improve the performance? Is it for example possible to deactivate the Change log?
    Note that I am already familiar with RSODSO_SETTINGS, and also, we do not want to switch to write-optimized DSO.
    Thank you in advance for your help.

    Hi
    DSO Activation can be improve by unchecking the "SIDs Generation upon Activation" check box in the DSO settings as it takes lot of time to create SIDs while activations. We can go ahead with this option only when we dont have any reports based on that DSO
    Thanks & Regards
    Rohit

  • Process Chain - Follow on dependencies to DSO Activation

    Hi, I have a Data Load Process where the start routine is dependent on DSO data that was just previously activated.  For some reason it looks like the the time before the load and the time after the DSO activation are close by just seconds. 
    The Data Load Routine will drop records if the activated DSO data is not available and this seems like what I am witnessing.  I thought there was a way to configure the chain or job to wait until the previous is completely done.  or did that go away with 7.0...
    Is there a way to make sure the loading process doesn't start until the previous DSO activation is completed and the data is available?
    Thanks!

    Hi,
    Interuppt concept :
    If a process chain is only processed either in part or in its entirity if more than one start condition is filled, you use this process type to specify the additional conditions.
    The chain is started when the condition of the start process is filled. However, the interrupt process will interupt the processing of the chain (as long as its status is "active") up until the point at which the condition of the interrupt process is filled. Should the start process condition be filled again before the interupt process condition is filled, the chain will start again and will only run up until the point of interruption. As soon as the interrupt process condition is filled, the system continues the last run of the chain only. The earlier runs remain unchanged.
    The interrupt process schedules an additional background job that starts based on the relevant condition. Therefore the interrupt process is not really active during the interrupt phase; it does not use any resources during this time.
    If the interrupt processes are filled before the start process condition, the chain starts as soon as the start condition is filled; the interrupt process no longer interupts the chain because its condition has already been filled. If the interrupt process condition is is filled again before the start condition of the chain is filled, this does not influence the chain. It is not stopped by the interrupt process..
    so basically your interrupt will wait for an event like ex:..YABAP_YGTRFCEVENTRAISE_0035 ... so you can raise that event eother by some job or some program..bUt for you i think adding the waiting timw will be better option ..
    hope i cleared  you ..
    Regards,
    Shikha

  • How to check if a DSO Active Table is being used in any look-up's?

    Hi Gurus,
    We have a DSO that is being loaded on a weekly basis. Now this DSO is being loaded right from the time our project went live. There are no reports built on top of this DSO and the DSO is not being used as a Data Mart i.e. it doesn't feed any other DSO's or InfoCube's. Also this DSO is not being used in any MultiProviders.
    So the only sensible reason for using this DSO that we can think of is that the data from this DSO is being 'looked up' by some other DSO's or InfoCube at run-time. So Is it possible to check if the active data table of an DSO is being ;looked up' at run time by some other data loads? I already tried using an 'Where Used List' on the active data table of the DSO, but it didn't show any results.
    Thanks
    Arvind

    Try the following:
    Check the table RSAABAP in SE16, you can search the technical name of DSOs active table in field EDIC.
    You get all Code-IDs, where this table is used in ABAP coding.
    In RSAROUT you can check, which code-type it is.
    Now you know, if the DSO is used in any routines.
    Hope this helps.
    Regards
    Tobias

  • DSO Activation

    I have a standard DSO.  In the settings, the only thing checked is "Set Quality Status to 'OK' Automatically",  I have this loading using a process chain and in the chain, I have the Activate process included.
    The DSO loads with no problem, but the Activate step fails with error message "No active PSA table".
    Two things that seem weird:
    1.  Without doing anything, I go to the DSO > Manage and the DSO has been activated (so why does the process Activate in the process chain fail?)
    2.  If I Repeat the Activate step in the process chain, even though the process is active based on # 1 above, the Activate step turns green and completes the process chain.
    I am having this problem for several DSOs in several different chains.
    Thanks for any help.  Keith J

    PC- Display variant for DSO activation - click on Parallel processing -  click DS Activ option -
       Background with "A"
       Num of Par proessing = 6
    again Click on this time DS-SID GEN
    Background with "C"
       Num of Par proessing = 3
    Make sure you have the same settings for DSO activation which are failing?
    Also refer Note: 1301094 - SP21:Error during activation of DSO in a Process Chain
    Symptom
    When you execute a DTP for loading a Datastore Object error happens in the activation of Datastore. This typically happens in a process chain. The error messages are as follows:
    o  RSDRO 103: "PSA update failed"
    o  RSAODS 003: "Error occurred while deciding partition number"
    Solution
    SAP NetWeaver BI 7.00
               Import Support Package 21 for SAP NetWeaver BI 7. 00(SAPKW70021) into your BI system. The Support Package will be available when note 1270629 with the short text "SAPBINews NW BI 7.0 ABAP SP21", describing this Support Package in more detail, is released for customers.
    SAP NetWeaver BI 7.01 (SAP NW BI7.0 EnhP 1)
               Import Support Package 04 for SAP NetWeaver BI 7. 01 (SAPKW70104) into your BI system. The Support Package will be available when note 1227876 with the short text "SAPBINews NW7.01 BI ABAP SP04", describing this Support Package in more detail, is released for customers.
    SAP NetWeaver BI 7.10
               Import Support Package 08 for SAP NetWeaver BI 7. 10 BI (SAPKW71008) into your BI system. The Support Package will be available when note 1260071 with the short text "SAPBINews NW 7.10 BI SP08", describing this Support Package in more detail, is released for customers.
    SAP NetWeaver BI 7.11
               Import Support Package 02 for SAP NetWeaver BI 7. 11 (SAPKW71102) into your BI system. The Support Package will be available when note 1260072 with the short text "SAPBINews NW7.11 BI SP02", describing this Support Package in more detail, is released for customers.
    In cases the correction instructions can be used.
    Beforehand please definitely check the note 875986 for transaction SNOTE.
    This note may already be available before the Support Package is released. However, the short text will still contain the words "preliminary version" in this case.
    Edited by: Srinivas on Jul 29, 2010 4:30 PM

  • DSO Activation Error

    Experts,
    My request got successfully loaded into the DSO. Then I activated it and executed the request. Unfortunately no data showed up except for the field names. So I went back to the manage screen of the DSO and saw that the request had turned red. Why is the request turning red after activation. Why isnt it showing any data after activation. Before loading, when I previewed it, all the data was shown correctly.

    Hi Pooja,
    Loading a request is one part and activating the request is other in DSO. when you load the request entire data will come to new table and when it is activated the data is shifted to active table, at this point of time it will check each and every record and also some of the routines. Normally at the activation time you will get invalid characters and lower case/ upper case these type of errors.
    You can check the erroneous records in PSA and also in the red datapacket's messages in Monitor screen. You can edit the error at PSA level and manually you can process the data to DSO.
    Hope this will helps.
    Rgs,
    I.R.K

  • BI Dev client inactive & DSO activation problem

    Hi SAP Experts,
                      Am facing some problems in DSO activation. Firstly the Business content DSO was not activating .So I had to activate the Datasources on the R/3. There were no errors in the job log but the DSO was still inactive. On trying to manually activate it , its stated that the BI Dev client was inactive. So I went to the Source Sytems tab, activated the BI client but it failed showing the following error messages:
    1.EDI:Partner profile not available-> A partner profile could not be found with the following key:/IBDCLNT010/LS/
    This involves the key fields of the table EDPP1: PARNUM.PARTYP
    2.Entry in outbound table not found-> A partner profile could not be found with the following key:/IBDCLNT010/LS/RSRQST///
    This involves the key fields of the table EDP13:RCVPRN,RCVPRN,RCVPFC
    3.Entry in inbound table not found........LS/RSINFO :
    4.Similar to error 3 :...../LS/RSSEND
    5.Destination IBDCLNT010 has incorrect Unicode settings,adjust it to destination:
    The unicode settings do not match the source systems.Conversion errors might occur during data transfer.Adjust the destination accordingly.
    Has anybody seen this error log before. If so please do let me know your valuable suggestions.
    Thanks for taking the time to read this technical concern
    Edited by: Prathibha Pillai on Jul 29, 2008 7:58 AM

    Hi,
    As of 1-4 error messages.
    You must define in partner profiles (ts WE20) the message type RSRQST as outbound on BI side and inbound on R/3 side, the message types RSINFO, RSSEND as inbound on BI side and outbound on R/3 side.
    Regards,
    Alexander

  • Deadlock when deleting from rsstatmanpsa during DSO activation

    We are experiencing intermittent Oracle deadlocks during DSO activation in our BI system.  The deadlocks occur when the following SQL statement is executed:
          delete from rsstatmanpsa where
                 partnr >= l_s_status-rnr_sid and
                 psa     = l_s_status-dta.
    This is at line 83 of the SET STATUS method of class CL_RSSM_STATMAN.  (See below for runtime error details.)
    When these errors occur the background job for the DSO activation is cancelled with the message ABAP/4 processor: DBIF_RSQL_SQL_ERROR.  Strangely, when this occurs as part of a process chain, the status of the process variant does not get updated until/unless someone displays the process chain log, at which point the status changes and follow-on events are triggered.  In other words, the process chain does not seem to be receiving word that the DSO activation process has abended, so we do not receive alerts that a problem has occurred.
    Has anyone else experienced this issue?
    Thanks,
    Bob
    P.S.  We are running BI 7.0, Patch Level 15 on Oracle 10.2.0.4.0
    Runtime Errors         DBIF_RSQL_SQL_ERROR
    Exception              CX_SY_OPEN_SQL_DB
    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 "SET_STATUS" "(METHOD)", nor was it propagated by a RAISING clause.
    How to correct the error
    Database error text........: "ORA-00060: deadlock detected while waiting for
    resource"
    Internal call code.........: "[RSQL/DELE/RSSTATMANPSA ]"
    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_RSSM_STATMAN===============CP" or "CL_RSSM_STATMAN===============CM008"
    "SET_STATUS"
    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
    "SET_STATUS" "(METHOD)", or its possible occurrence must be declared in the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
    Information on where terminated
    Termination occurred in the ABAP program "CL_RSSM_STATMAN===============CP" -
    in "SET_STATUS".
    The main program was "RSPROCESS ".
    In the source code you have the termination point in line 83
    of the (Include) program "CL_RSSM_STATMAN===============CM008".
    The program "CL_RSSM_STATMAN===============CP" was started as a background job.
    Job Name....... "BI_PROCESS_ODSACTIVAT"
    Job Initiator.. "ALEREMOTE"
    Job Number..... 05302800
    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
    procedure "SET_STATUS" "(METHOD)", but it was neither handled locally nor
    declared
    in the RAISING clause of its signature.
    The procedure is in program "CL_RSSM_STATMAN===============CP "; its source
    code begins in line
    1 of the (Include program "CL_RSSM_STATMAN===============CM008 ".
    Source Code Extract
    Line
    SourceCde
    53
    if i_with_internal_check is initial.
    54
    l_s_status = i_s_status.
    55
    call function 'RSSM_GET_TIME'
    56
    importing
    57
    e_timestamps = l_s_status-ts_last_changed.
    58
    if l_s_status-ts_proc_started <= '10000101000000'.
    59
    l_s_status-ts_proc_started = l_s_status-ts_last_changed.
    60
    endif.
    61
    if l_s_status_exist is initial.
    62
    insert rsstatmanstatus from l_s_status.
    63
    if sy-subrc <> 0.
    64
    message x000.
    65
    endif.
    66
    else.
    67
    modify rsstatmanstatus from l_s_status.
    68
    if sy-subrc <> 0.
    69
    message x000.
    70
    endif.
    71
    endif.
    72
    delete from rsstatmanpart where
    73
    rnr      = l_s_status-rnr and
    74
    dta      = l_s_status-dta and
    75
    dta_type = l_s_status-dta_type.
    76
    select single * from rsstatmanpsa into l_s_psa where
    77
    rnr      = l_s_status-rnr and
    78
    psa      = l_s_status-dta.
    79
    if sy-subrc = 0.
    80
    delete from rsmdatastate_psa where
    81
    psa  = l_s_status-dta and
    82
    type = l_s_status-dta_type.
    >>>>>
    delete from rsstatmanpsa where
    84
    partnr >= l_s_status-rnr_sid and
    85
    psa     = l_s_status-dta.
    86
    else.
    87
    select single * from rsmdatastate_psa into l_ds_psa where
    88
    psa  = l_s_status-dta and
    89
    type = l_s_status-dta_type.
    90
    if sy-subrc = 0 and l_ds_psa-sid_checked > l_s_status-rnr_sid.
    91
    delete from rsmdatastate_psa where
    92
    psa  = l_s_status-dta and
    93
    type = l_s_status-dta_type.
    94
    delete from rsstatmanpsa where
    95
    partnr >= l_s_status-rnr_sid and
    96
    psa     = l_s_status-dta.
    97
    endif.
    98
    endif.
    99
    if i_with_commit = 'X'.
    100
    call function 'DB_COMMIT'.
    101
    endif.
    102
    endif.

    Walter,
    Thanks for the suggestion.  This is the same recommendation I just received from SAP.
    We are currently in the midst of regression testing for a major release, so cannot implement these corrections immediately.  I'll post again after we implement the corrections and let you know if they solve our problem.
    Thanks again.
    Bob

  • DSO Activation failed

    HI,
    Process step dso activation is failed due to Runtime error...I Checked in JOB Log it says ABAP/4 Processor : MESSAGE_TYPE_X and job is cancelled. So i went to ST@@ Tcode and released the dump. and again repeated the failed step.then it again failed due to same.Please tell me how to fix this issue.
    Regards,
    Swathi

    Hi,
    Please check the following threads, an SAP note has to be applied:
    Loaded for 4 times same dump in BI system
    DSO Activation Dump
    Thanks,
    Arminder

  • Getting Shor Dump while DSO Activation

    Hi Experts,
    I am getting Error while DSO Activation, I checked in ST22 Error is (SYSTEM_CORE_DUMPED), Please suggest me.
    Category               Internal Kernel Error
    Runtime Errors         SYSTEM_CORE_DUMPED
    Date and Time          25.02.2014 18:38:47
    Short Text
         Process terminated by signal 10.
    What happened?
         Error in the SAP kernel
         The current ABAP program "CL_RSODSO_DATASTORE=====
          terminated because the ABAP
         processor detected a system error.
    Thanks
    Sunil

    Hi,
    Take basis team help. error itself saying as related to internal kernel error.
    recently any changes were applied on server? if yes then those might be causing.
    please refer note - 517824.
    Inform to basis team and sort it out.
    Thanks

  • Getting Short Dump while DSO Activation

    Hi,
    I am getting Error while DSO Activation, I checked in ST22 Error is (SYSTEM_CORE_DUMPED), Please suggest.
    The kernel is latest version.
    Also we had implemented a couple of SAP Notes while we searched on the SDN and service market place. But still no luck.
    Category Internal Kernel Error
    Runtime Errors SYSTEM_CORE_DUMPED
    Date and Time          09.04.2014 16:14:13
    Short Text
    Process terminated by signal 10.
    What happened?
    Error in the SAP kernel
    The current ABAP program
    "CL_RSODSO_DATASTORE=====
    terminated because the ABAP
    processor detected a system error.
    Thanks,
    Sameer

    Hi,
    Yes this happens for a particular DSO only - 0FIAR_O03(DSO)
    Also the kernel is the latest one.
    I am from Basis. I have checked all the possibilities and have raised OSS message as well.
    Thanks,
    Sameer

Maybe you are looking for