Skip to Content
0

Adapt new tablespace after EHP-upgrade

Jan 26, 2017 at 07:54 AM

366

avatar image

Hi,

We have recently upgraded our EHP and i see the newly created table space 740 is still 0 percent used where as old 702 is 98 percent used.

May i know the right procedure to adapt this new tablespace.

Regards,

Domnic

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

5 Answers

Reagan Benjamin
Jan 30, 2017 at 09:43 PM
0

What is the EHP level of the system? If the new tablespace is showing 0% then something could have gone wrong during the EHP update. It looks like the tool failed to move any of the objects to the new tablespace during the update (probably a bug?). I would first check the target system components against the stack file and whether it matches and raise an OSS message with the log files for SL Toolset to SAP. If this is a quality system then you may wait until you hear back from SAP or try moving the objects from the old tablespace to the new 740 release tablespace using the BRTools. You will need to stop SAP to move the objects to the new tablespace.

Show 3 Share
10 |10000 characters needed characters left characters exceeded
You will need to stop SAP to move the objects to the new tablespace.

Reagan - It can be done online using brspace. Just wanted to add so that requestor can use online tablespace migration if it is really required.

Regards,

Harish Karra

0

As the old tablespace contains all the objects, most likely BRTools might complain that the SAP system is running and should be stopped to move the objects from one tablespace to the other. Just a thought. If there is no such message thrown by the BRTools then this can be done without stopping the system.

0

Yes Reagan,

It is very much possible, it follows reorg process and being a non-system tablespace it doesn't need any downtime.

Regards,

Harish Karra

0
Janos Mucsi-Besze
Feb 01, 2017 at 10:06 AM
0

Check the TABARt assignment in TAORA,IAORA,TSORA Tablespaces. In the past and mostly nowadays as well, the Upgrade (SUM) is unable to handle inappropriate/unconsistent assignment within these tables. So sometimes the objects left in the 'old' tablespace whereas they should be placed in the new one already. If TABART assignment is correctly poiting to the new tablespace, reorganize the objects with BRSPACE from 'old' to 'new' Tablespace.

Regards,

János

Show 2 Share
10 |10000 characters needed characters left characters exceeded

Janos,

Thanks a lot for your suggestion,Checked TAORA,IAORA,TSORA in data browser if theres something better to check TABRT assignment, please update.

Regards,

Domnic

1

Hi Dominic.

It is easy to check these tables and entries in SE16. Or from DB level (e.g. in SQLPLUS). If there is a similar problem like yours, I am always checking the before mentioned tables only. Of ourse DBA_SEGMENTS and DBA_OBJECTS have to be checked as well to see the segments/objects assigned to the affected tablespaces.

Regards,

János

0
domnic domnic Feb 05, 2017 at 07:41 AM
0

Reagan and Janos,

Thanks for your replies, we are on EHP7 now, we have PSAPSR3, PSAPSR3702 and PSAPSR3740(new) ts, out of this 740 is zero percent used.

TABARt is assigned only to PSAPSR3 and PSAPSR3702 (but not a single entry pointing PSAPSR3740) for TAORA,IAORA,TSORA

Regards,

Domnic

Show 3 Share
10 |10000 characters needed characters left characters exceeded

How was the tablespace PSAPSR3740 created? Did you use BR*Tools? if yes could you supply the logs?

1

This is a focal point. As in case of manualy Tablespace creation you have the assign specific TABARTS manually to that tablespace. So during the TS creation BR*Tools takes care of the TAORA,IAORA,TSORA entries, so inserts and/or updates the corresponding entries.
In case the Tablespace got created by SUM tool, then SUM is responsible for the correct entries. But as I wrote before sometimes this fails.

1

Dear Janos and Benjami,

PSAPSR3740 is manually created using SQL>CreateTableSpcae and ADD DATA file commands.

can you please share how to add TABARTS to this table space now and bring it to the purpose it is meant for.

Thanks in advance.

Regards,

Domnic

0
Sergo Beradze Feb 06, 2017 at 12:34 PM
0

Hi Domnic,
are you sure you have DB02 datasets refreshed? Or you see it from Brtools?
Can you clarify that point?
BR, Sergo.

Show 4 Share
10 |10000 characters needed characters left characters exceeded

Hi Sergo,

yes i have DB02 statistics refreshed very frequently.

Regards,

Domnic

0

Hi Domnic, can you compare output of DB02 with the output of brtools (menu tbs extention).
Can you show how it looks like, pictures of both DB02 and Brtools TBs Extention menu.

BR, Sergo.

0

Dear Sergo,

Please check this from DB02 and BRTools

Kind Regards,

Domnic

db02.jpg (153.9 kB)
tbsext.jpg (64.3 kB)
0

Hi Domnic.
Please read carefully this note:
1805195 - Handling and troubleshooting of tablespaces during SAP Upgrades, Enhancement Packages and Support Packages updates

After you are sure, that all Tabarts are correct, proceed with this step from the note -->
Solution: move the tables/indexes to the new tablespace using the specific database tool for this action. In Oracle it is BRSPACE (included in BRTOOLS), see note #646681. Note #1715052 covers this situation as well.

BR, Sergo

0
Reagan Benjamin
Feb 12, 2017 at 12:48 AM
0

If you have created the tablespace manually from the SQL prompt then most likely that could be the reason. This is the reason why the BR*Tools should be used. As you have completed the upgrade then like I have suggested before you should consider moving the objects from the old tablespace to the new tablespace using the BR*Tools. Again using the BR*Tools. It should in fact take care of the TABART alignment during the move.

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Mr. Reagan,

Appreciate your help, can you please give me the procedure to move all the objects from old tablespace to new tablespace using BRTools please in prd env.

Kind Regards,

Domnic

0