Deletion of pending update records In SM13

[Former Member]

Hi Experts,

We are in the process of upgrading our ECC 5 with Oracle 11g running on AIX 5.3 to ECC 6 with EHP4.

During the course, we have executed 3 iterations of the Production copy upgrades and were achieving minimal downtime.

Every time, the System Isolation Steps Before Switch To Downtime Step - Deletion of pending update records In SM13, takes about more than an hour which is a part of technical downtime.

I would request for some ideas of expediting this step. As this would drastically reduce our downtime.

BR,

Venky

[paul_power]

Hi Venky,

Could you post the section for this phase from the SApupConsole.log

regards,

Paul

[Former Member]

Hi Paul,

Thanks for your message.

Since this activity is manual, I do not think there is something in the sapconsole log.

The detailed query is as follows.

1. When I start the Downtime phase, is it mandatory to cleanup all the updates (Cancelled + Processed) or only the cancelled updates.

2. If I have to delete all the updates (Cancelled + Processed) which isapproximately 1 lac entries, then the duration required for this activity would be nearly a day.

This will directly impact Downtime phase during Production upgrade

Now in an event of cleaning up all cancelled & Processed update entries then request you to suggest a method to do it in a faster way.

BR,

Venky

[paul_power]

Hi Venky,

As long as you are in prepare or uptime of the upgrade you can

ignore the errors in the RSVBCHCK which say that there exist

update records (as it is normal that there are update records

in a system which is productively used).

In the downtime there is also a check on update records Phase JOB_RSVBCHCK2)

In the downtime this check cannot be ignored.

We recommend that you clean up as many updates and RFC calls as possible

. Otherwise, you

will have to clean them up during downtime.

To find terminated or outstanding updates, proceed as follows:

1. Call transaction SM13.

2. Delete the default values for the client, user, and time.

3. Select all the update requests.

To find outstanding outbound queue RFC calls, proceed as follows:

1. Call transaction SMQ1.

2. Delete the default values for the client.

3. Make sure that the list of outbound queue RFC calls is empty.

Otherwise you might lose data in other systems (for example, in SAP BI).

Repeat these checks when production operation ends.

regards,

Paul

[Former Member]

Hi Paul,

This is only our biggest concern now.

How to speed up the deletion process during the downtime if we have 1 lac + entries in SM13?

Is there any solution for this..

BR,

Venky