SP12 - central note 1969109 v15 - hungry on heap and activation taking forever

[francois_keen]

Hello SAP Solution Manager community.

I would be curious to know if anybody faced issues trying to implement the note 1969109 v15. I just updated from SP10 to SP12 and I'm having terrible problems trying to get the note in.

I did implement the notes 2025948 and 2069753 of the section I.1) of 1969109

And the note 875986 is in its latest version.

I couldnt see any pre-reqs I would be missing listed in 1969109 and 2020219

So far I had the note implementation which failed a few times as it was running out of heap.

I had to restore my DB as I ended up with multiple inactive objects.  Manual activation with dozens of SCCR keys didnt seem a viable option!

I have now extended the heap to 4 GB and so far, the activation part of the note 1969109has been running for more than 5 hours grabbing already 3.5 GB of heap... While this is running I thought I would take a few minutes to create this SCN discussion.

It is usually current that after solman patching, central notes are big and take long, but so far I never ever saw something like that before.

Has anybody faced such a problem while trying to implement central note 1969109 v15 just after an update to SP12 ? [no one shared heap, crazy long activation times in this thread]

Looking forward to hearing back from your experiences.

Thanks and best regards

Francois

[divyanshu_srivastava3 · Accepted solution]

Hi Francois,

What is the error or dump you get while application of note ?

May be, you should share the complete error details once.

Regards,

[francois_keen · Accepted solution]

Hello Divyanshu

Thanks for the quick reply.

Well the only error I had so far was a classic error something like "couldnt extend internal table" which was due to the memory exhaustion as I reached the max allowed heap for DIA process which at that time was 2GB. Unfortunately I didnt take a note of the dump so I do not know which Runtime error or program was being run at that time. Since then I had to restore my DB as the central note failed activation left me with dozens of inactive objects.

My question  was to know if anybody else faced such a voracious appetite for heap after having updated to SP12 and trying to implement the central note 1969109

So right now, I am waiting hopping it will complete at some point, and I will keep extending the heap using rsmemory hopping the activation of the objects will finish at some point...

Right now, I can see a long running CL_WB_CROSSREFERENCE==========CP which is all in memory [no DB accesses] and the heap keeps growing... If it fails again and if it fails during the execution of this class I could maybe, after next DB restore, implement 2023460 before trying the central note one more time...

best regards

Francois

[francois_keen · Accepted solution]

ok more than 4 GB of heap, 5 hours running, the objects will never activate!

I launched the debugger and the method in use was CL_WB_CROSSREFERENCE SAVE_INDEX so the note  2023460 sounds quite helpful.

I will be restoring my DB and I will try this first thing tomorrow...

Update from 27th of Nov. After having restored the DB and implemented 2023460 before the central note 1969109 v15, activation took 30 mins and a bit less than a GB of heap was used.

This note 2023460 should totally be listed as mandatory in 1969109...

[Khouri · Accepted solution]

Hello,

We have exactly the same issues when we tried to implement the central note 1969109 after SPS12

It terminated with  the following a short dump:

----------------------------------------------------

Category               Resource Shortage

Runtime Errors      TSV_TNEW_PAGE_ALLOC_FAILED

Short text

  No more storage space available for extending an internal table.

What happened?

  You attempted to extend an internal table, but the required space was

  not available.

Error analysis

    The internal table "\CLASS=CL_WB_CROSSREFERENCE\METHOD=SAVE_INDEX\DATA=L_MODIFY

    _WBCROSSI" could not be further extended.

-----------------------------------------------------

When we check the status of note 1669109 (SNOTE) it is "Completely implemented" but we can many notes under the Node "In Processing"!

How to check the Consistency of the implementation and how to continue with the open notes without going for a DB restore?

The DB restore will need a bigger effort and we have just only an online Backup available!

And I totally agree with Francois about the mandatory of note 2023460 before starting the implementation of 1969109.

Thanks in advance for your input.

Best regards,

Hadi

[shaun_wimpory2 · Accepted solution]

Hi Hadi,

Did you manage to work through this issue without the need to restore the database?  If so, could you please tell me how you accomplished it?

Regards

Shaun

[Khouri · Accepted solution]

Hi Shaum,

Yes we manage to survive without a restore

You should  first check the note postprocessing in system preparation (SOLMAN_SETUP) and then verify if you have any "inactive objects" in your system for that go to SE80 and choose "Inactive objects" in case you find any activate them one by one, you have to register every object to be activated in SMP, we looked for a way to perform a mass activation without reg. key but I guess it not recommended and we use the save way and activated them one by one but anyway not comparable to the effort you will have with a restore.

I think the above is not general and most probably depending what is still inactive therefore I suggest to create an OSS message to assist you for this matter.

Hope it helps.

Best regards,

Hadi

[francois_keen · Accepted solution]

Hello Shaun

As mentioned in my initial post, I also considered activating manually but didnt want to go trough the process of regitsering so many objects.

considering that the central note is a time consuming post upgrade task, and unfortunately one of the numerous post ugrade tasks, I do not have my system yet opened to end users yet at that time, which means going back to the point in time just before starting applying the central note is very easy...  much easier than trying to activate numerous objects.

in my case, after having restored the DB, i then implenented the note 2023460 , then the central note 1969109 v15, activation took only 30 mins and a bit less than a GB of heap was used.

So if you have a DBA team that can do the restore for you, it means you only need to stop solman, get the restore done, start solman, apply note 2023460 before applying the central note 1969109 ... that is much faster than spending time registering one object at a time and activating it.

As you wish!

Best regards