cancel
Showing results for 
Search instead for 
Did you mean: 

0ORGUNIT hierarchy DBSQL_DUPLICATE_KEY_ERROR during activation

SvenS
Participant

Hello

We just did an upgrade of our SP from SP16->SP17 in BW 7.4.
After doing this upgrade we noticed that our hierarchy of 0ORGUNIT was failing in the process chains.
When checking the messages we get following: Internal session terminated with a runtime error DBSQL_DUPLICATE_KEY_ERROR (see ST22).

When checking ST22 in the debugger I saw that the code is trying to insert /BI0/IORGUNIT (SID hierarchy structure) in the method _SAVE_INCL.
And here it crashes. When I check this table I see nothing out of the ordinary.


I read a lot of posts about this and tried following:
Activation the M version of the hierarchy in RSH1 -> throws the error.
Deleting the hierarchy and reloading it -> throws the error.
Ran all possible tests in RSRV for master data and hierarchy -> all passed without errors.
Activating the hierarchy through a program -> throws the error.

I found following SAP NOTE: https://launchpad.support.sap.com/#/notes/2497296.
Which just says hey you have to go to SP18 which we like to avoid.

Any other ideas on how to solve this problem? I also like to avoid to manually search the hierarchy since it is time dependant and has over 5000 entries.

Kind regards
Sven

Accepted Solutions (1)

Accepted Solutions (1)

himanshi020
Participant

Dear Sven,

Kindly have a look on the below SAP KBA:

2524868 - Activation of hierarchies lead to short dump CL_RRHI_INCL_CREATOR

Also, is it possible for you to attach the ST22 dump(HTML format)?

BR,

Himanshi Goel

SvenS
Participant
0 Kudos

Hello Himanshi

The note you linked seems to have the note that I'm looking for in it: Note 2579310.
This one seems to fit the problem I have, I will ask our basis team if they can implement it.
If it corrects our problem I will accept the answer.

Kind regards
Sven

himanshi020
Participant
0 Kudos

Hello Sven,

Sure, keep me posted about the results. 🙂

BR,

Himanshi Goel

SvenS
Participant
0 Kudos

We now implemented note 2579310, but of course just doing this would be to easy...
RRHI_HIERA_SVER_DELETE which was implemented in _SAVE_INCL of course now has a new parameter and now we need a note for that...

Kind regards
Sven

himanshi020
Participant
0 Kudos

Sven, kindly confirm if you have followed the below mentioned steps as provided in SAP KBA(2524868):

Step 1: Check and implement these SAP Note corrections (with support package or with SNOTE)

Step 2: Afterwards (!) run the report RRHI_CORRECT_OSID_KTAB (again) with the option "Delete old versions (i-Table)" (field delver).

BR,

Himanshi Goel

SvenS
Participant
0 Kudos

We finally got it working, after also implementing note 2497541 with all of its prerequisites the hierarchy can be activated again.
As for the notes you mentioned it was searching through a lot, since apparently we already implemented some notes in the past but not everything etc. But in the end 2579310 and 2497541 were all we needed since we needed _SAVE_INCL updated with the FM RRHI_HIERA_SVER_DELETE and we needed the FM RRHI_HIERA_SVER_DELETE updated with the new optional parameter I_FORCE_DEL.
Also note 2497541 updated RRHI_CORRECT_OSID_KTAB which was not working anymore in our system for some reason.

Thank you for your help, your initial note brought me to this solution!

Kind regards
Sven Swennen

himanshi020
Participant
0 Kudos

That's great, Sven. I'm glad it worked. 🙂

Have a good day!

Answers (0)