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 Member]

Hello Akshay,

In shadow Instance (usr/sap/sid/sum/abap/<sid>) which data exactly is cloned from the original system into the shadow instance. Suppose to say that my total data base size is 300gb.

Thanks,

Maruthi.

[Akshay_G]

Hello Maruthi,

Have you read this post completely with all the comments?

To answer with your query:

Reagan Benjamin wrote:
During the upgrade SUM tool asked you to create a tablespace called PSAPSR3702X for the upgrade activity.
The shadow system was created with this tablespace.
The table space is NOT a temporary tablespace, instead this is the tablespace where the upgraded components reside.
The shadow instance has no relevance once the downtime has been completed.
During the downtime phase the system does a switch of the shadow instance to the main instance with the new kernel and that is the reason why the SUM tool prompts you to back up the database, the upgrade directory and the old kernel before you proceed with the downtime phase.

I believe your are trying to get an estimate on required free space for performing upgrade using SUM.

Based on your tablespace PSAPSR3702 or similar you shall be prompted to create additional tablespace PSAPSR3702X of specific size. The size of the shadow instance directory depends on this size.

For your ref:

1) Size of PSAPSR3702 before upgrading with SUM=> 18.5 Gigs

2) Size of new Tablespace PSAPSR3702X => 32 Gigs 75% Consumed

3) Size of PSAPSR3702 after upgrade => 18.5 Gigs 100% Free

4) Shadow Instance Directory Size => Approx. 21 Gigs.

-Akshay

[Former Member]

To be Honest no.

But,

I greatly admire the way of your response...

Thank you so much Akshay.

[Reagan]

Hello

The database content is not copied to /usr/sap/sid/sum/abap/<sid>

The upgrade activity only works with the repository data.

There will be only one database for the main system and the shadow system.

The file system /usr/sap/sid/sum/abap/<sid> is used for the upgrade activity where the shadow instance is created along with the upgrade activity logs, etc.

Read these discussions:

http://scn.sap.com/thread/3414014

http://scn.sap.com/thread/3410181

Regards

RB

[Former Member]

Hello Reagan,

The discussions really helped me a lot....

Thank you Reagan.