How to find the right component in SAP market place regarding Update records are stuck in SM13?

[former_member250442]

Still 5000+ record found in SM13

[JL23]

by describing the problem in more detail,

[former_member250442]

The updates are stuck in SM13 but there are no processes in SM66 that shows with UPD2. Dead lock issues caused the pile up of updates and now these updates are orphaned and the process are not associated for the given UPD2 processes. This is inconsistencies in the SIS structure. Then we have opened a connection too.

After that SAP reply:

Assign this incident to BC-CST-UP team for analysis.

They have loged into the system and check those update requests entries in Status "V1 processed".

The modules for " MCV_STATISTICS_UPD_V2_ORDER", (type V2) which remain in 'init' status.

Please note that status V1 processed means that the init phase has been correctly processed and the V2 modules
have been forwarded for processing.

Checking the update server (where the update request should have been done), they point to server psapap23_PRD_23.

If you go to SM51 -> Select the application server psapap23_PRD_23 -> Goto -> Server information -> Queue information,

you can see that it faced an overflow under the UP2 work process -that are responsible for the V2-.
Type Req waiting max.req wait Max req
UP2 0 2.000 2.000 44.111.416 44.111.416

It seems that all UP2 work processes from that server were occupied, and the Dispatcher queue for UP2 requests got full.

It could happen that there were massive V1 update processes finished at the same time, which may cause the
UP2 queue overflow for server "psapap23_PRD_23".

As no more UPD2 requestes could be processed due to the dispatcher overflow, the update requests remain in sm13 in

Status "V1 processed" (V1 updates have been correctly processed and the V2 modules have not been processed yet).

Please take a look at the following Note, which explains how to re-process all those updates:

1898302 - The V2 update process cannot proceed with error 'Error adding a request to the dispatcher queue ( UP2)'
1510367 - Re-processing failed update records via SM13

After that we reply:

Please Find the attachment...!!!!

We have checked both the notes prior to creating the incident.

Our situation is one of the jobs that’s running causes deadlocks and there by the UP2 is held up by the table.

Once these update errors are fixed by the functional teams. The rest of the updates that are in the SM13 are processed by the other functional teams in a massive way , select all and hit Repeat Update.

So the first note , 1898302 - The V2 update process cannot proceed with error 'Error adding a request to the dispatcher queue ( UP2) è We are already aware as to why this happened.

As per the second note , the action is already performed by the Functional users , The updates were repeated as per 1510367 - Re-processing failed update records via SM13.

But the updates are stuck in “Started” State ever since. We would like to complete processing these updates. Please let us know if there is a way we can do this in a systematic way within SAP

We have requested the functional user to repeat the update as well. The attached shows that wrong update code error. Please let us know how this issue can be addressed. There are 5000+ updates pending causing inconsistencies in SIS structures,

And also

For MAILLORD_USER, we found the related SAP job is possibly SD-U-DLY-MAIL SALES*. However the jobs all completed normally and the update status is still “Started”.

Initially SAP(SAP Market place) Team sending this incident to o BC-CST-UP team for analysis and then assign to other team.

At last they says AP-ACC-SAR is not the right component for this incident and we are not sure which is the right component. Kindly forward it to the right component.

So, Could you please check and let us know for the same.