Software Update Manager: Clean up tasks, Shadow Instance & Temp. Tablespace X

[#1]

Hi Experts,

I wanted to know that after an upgrade activity using SUM (Software Update Manager) how should I proceed with the cleanup tasks.

As SUM uses a shadow instance for the upgrade and for which a temporary table space is required, we can release some space once the upgrade has completed, right?

In my case (SPS08 upgrade in Solution Manager 7.1), a temporary tablespace PSAPSR3702X of 32GB was required before execution.

So I created that in order to upgrade my system.

My upgrade went successful, and now I would like to cleanup the space that was occupied during the upgrade.

I believe that scope here for cleanup is:

1) The temporary SAP Tablespace PSAPSR3720X (32 GB), data file is under /oracle/<SID>/sapdata4

2) SUM Directory (Upgrade directory /usr/sap/<SID>/SUM, which is 21G and contains the logs,files, shadow instance)

What should be the approach to process the clean-up post upgrade?

A) Is this approach feasible?

1. Stop SAP & DB
2. Drop SAP Temporary Tablespace
3. Drop SUM Directory
4. Start SAP & DB and validate

I also looked up SAP note 1732061, which is central note for SUM, it talks about, Do not select "Cleanup and start afresh" before finalization.

So in the postprocessing phase after the upgrade completes and just before Finalization phase, I have selected "Continue" as per the above mentioned note during the upgrade.

B) Or is it that, if I start SUM again and I get an option in the beginning "Cleanup & Start Afresh" which shall do the necessary cleanup, though I am not really sure, if this the possible feature of SUM!

Which is the correct approach? Could you please suggest, as I have worked with SUM for the first time.

Regards,

Akshay.

[former_member25156]

Hi -

We have an SUM related question. We are upgrading an ECC System, and something happened with the upgrade where, in the SUM directory, the following folders were deleted in /usr/sap/put/SUM:

bin

bin_nuc

buffer

cofiles

control

data

exe

htdoc

There were no processes running at the time, and it was at the prompt to start downtime, phase : DOWNCONF_DTTRANS

After looking into the (already upgraded) QA SUM directory, I could do a compare, and saw that we can potentially use the folders from QA and copy them over and restart the SUM tool. Is this something to consider? Or do we restart the whole process?

Thank you!

[rajarshic]

Hi Ronald,

If you are using the same version of SUM and target software components both for QA and the present environment, it should not be much issue except the fact that the directory HTDOCS contain information in the form of log files about how the entire process was executed till your downtime phase (like software components selected and execution time for each phase) for your DEV environement which you can't replace with the QA one. I'd suggest to reset the upgrade process after restoring the QA directories and see how it progresses.

Thanks

[Former Member]

Hi Ronald,

from my point of view also, a restart of the upgrade is essential. The data and cofiles under SUM directory directories include upgrade-specific transport files.

Regards.

Serhat