DSO's activation multiple failures

[Former Member]

Hi Guru's,

I monitor a 7.3 (7.31 SP9) BW system with hundred of infoproviders (7 T° data) and almost everyday I face failures with DSO activations processes in our chains.

In 95% of the cases, I just need to repeat the process and it goes green ; with some DSO's, I put in place a second activation process into the chain in order to make my life better 😉

In 5% of the cases, the root cause is identified (bad data ; locks ; ...), but in most of the other 95% cases, I am unable to find the reason ??

Message is typically:

     Error when inserting the data record for data package

      45

     Message no. RSODSO_PROCESSING002

     Diagnosis:

     The data records could not be saved. This may be due to the following

     reasons:

     o   You tried to save a record that is already stored in the database.

         This error only occurs with DataStore objects and the option Unique

         Data Records.

     o   A unique index was created for the table of active data.

         You can check this in the Data Warehousing Workbench by choosing the

         Indexes folder in the DataStore object display.

     o   There is a technical problem in the database.

     Error code: DBIF_RSQL_SQL_ERROR

Our DB is a DB6 ( version 10.05.0007)

Any idea about how I should investigate further?

Thanks in advance for your help,

Regards,

Thomas

[john_hawk · Accepted solution]

Hi Saposs,

Time to get your Basis team involved.

SAP Note 1943633 - SYSTEM_CANCELED upon activation of a Data Store Object (DSO) request

indicates that this error can occur if there is an inconsistency in indexes between the application data dictionary and the database.

Resolution

Please check the indexes via transaction SE14 or transactoin DB02 and create/rebuild them as required...

Right click on the DSO -> Manage -> Contents -> Active Data -> Copy the name of the table from the top of the screen.

Go to transaction SE11 (Data Dictionary Tables, DD) -> Enter DSO Active Table name -> Display -> Indexes.

Go to transaction SE14 (Database Tables, DB) -> Enter DSO Active Table name -> Edit -> Indexes -> Double-click on the Primary Index -> Check the Status.

Determine if the index exists in both the data dictionary and at database level and also that it is consistent. If it does not exist in either one of the transactions then recreate the DD or DB object. If it is inconsistent please delete and recreate in both the DD and the DB. Please see SAP Note  117219 for further considerations.

Alternatively, you can check via transaction DB02 -> Click Diagnostic Node -> Click Missing Tables and Indexes.

Also

SAP Note 2092206 - SYSTEM_CANCELED shortdump in DSO Activation - Background Jobs

describes how running multiple DSO activations in parrallel can cause resource error.

I have found is also causes problems at the database layer. with cross-locking.

Additionally

Check to see if you are attempting to run an Attribute change run concurrently with DSO activation. Bot are SID generation intensive and can cause cross-locking.

Please don't forget to record your final solution and to mark the question as answered.

Good luck,

John Hawk

[former_member186445]

as the activation goes well with a repeat, the data in the dso is not the issue.

If you have a lot of dso's the cause could be that you don't have enough background processes available. you can check with basis team for this. also make sure you don't activate the same dso at the same moment in two different chains.

M.

[Former Member]

Hi,

Maybe also you have a other Load process with routines and they are reading the object when the system is trying to access it. This happends o me when have a big system with Sales Orders, Billing Items, COPA DSO etc.

Unfortunately identify this is not an easy task since you need to review coding and several flows.

Hope this helps.

Regards.