on 02-11-2015 7:38 AM
Hi,
I have a table with some data sitting across the Landscape including Production. Now, for some reason, if I want to change Table Space that was initially assigned to the Table from SE11, should I do it right away? Or Do I need to delete the Table and re-create it with New Table Space?
In fact, I have same question for the one that I created/activated in Development System but not yet applied to any other Systems? Do I need to simply change Table Space and Re-Activate it or should it be Delete and Create table with new Table Space?
I am worried about Table Re-Creation since this is going to purge the entire data, however this looks like the recommended way. Please share your thoughts?
Regards,
Naveen Inuganti
You wont be able to extend the table but the tablespace as the table sit on tablespace.
If you extend the tablespace then your space issue should be resolved as long you have sufficient freespace at OS level. There is no benefit moving the table from one tablespace to another as long as this table is IO expensive and you would like to store on separate disk but if you have SAN as storage then no need create separate tablespace.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sunil,
Thanks for your attention.
I understand what you are saying, but I think I am dealing with different scenario here. We really don't want to extend the existing Table Space or deal with it any more. We want to use one of custom Table Space that can be managed and controlled by BASIS. Based on this decision, we want to come-up with a process or a guideline for developer to use proposed custom Table space going forward.
I said going forward but we want to consider the stuff that is not yet fully deployed to/functioning in production (various projects). This is what I mean when I say, some of them are in Staging, Quality and Production with some data.
I think that very high level overview on scenario.. but hope where we are standing technically is clear.
Since BASIS cannot get into this adjustment every time, we are asking developers to do it from SE11. Now, the question is "For the Active Table with incorrect Table Space -- Do I need to delete and re-create table from SE11 or just change TableSpace and activate it?"
Regards,
Naveen
Standard or custom tablespace can both be controlled by Basis.
Which option are you willing to change at tablespace level ?
Customer (and not custom) tablespace PSAPSR3USR is just there to hold customer specific tables...
Only few customer creates a dedicated specific tablespace layout, most of the time to handle VLDB (very large database).
Changing the tablespace used for a table should be done through SAP BR*Tools.
I do not see the use of interfacing BR*Tools through ABAP code.
Deleting / recreating the table is not the good way to change the tablespace, please take some time to read my answer and the provided links.
Thanks for those links. That explained the whole process in great detail.
My question sounds like BASIS job (of course I am in SQL for SAP page though).. however, I want to understand one of the SE11 feature here..
but let me put my question with an example.
I have TableA created and activated with data class as APPL0 and moved to Quality system.
Now, I modified data class from APPL0 to USER from SE11 Table Technical Setting, which is different Table Space. If I move this Technical Setting Change to Quality System - what will happen there?
Will automatically changes Table Space of my TableA or BASIS involvement required?
Regards,
Naveen
If you change the data class i dont think the table is going to move in different tablespace as the table is already exist. You or basis team may need to perform the table move to different tablespace.
I dont think you should change the table data class so eailsy and as and when you want. I think You should be very careful about this and assigning the data class is not Basis task.
Changing the data class won't have any impact at DB level on an existing object, it won't change the tablespace used to store an existing table.
It will only have an impact for tables that are not created yet at database level.
When changing the data class of an existing object, if you are willing to change the tablespace used to store that object, you will need to use BR*Tools at OS level to move the table to an other tablspace (reorg).
Regards
There is a mapping of the Data class to the tablespace . ( Tables TA<DB> , IA<DB> eg :TAORA/IAORA ) , A change in the data class will not change the table from already existing tablespace to new tablespace .
You may not require your BASIS team to move this as it can be done from SE14 as well .
If Basis team is doing this using DB methods make sure that they update tables IA<ORA> AND TA<ORA>
But i believe this TB movement is neede as i have seen issues during the upgrade ( especially when using SUM tool )
541542 - Upgrade phase INIT_CNTRANS: Container inconsistency
1805195 - Handling and troubleshooting of tablespaces during Upgrades, EhPs and SPs updates
Thanks ,
Manu
After making the change
SE14-->Storage Parameters
Extras -> Force Conversion
I am not able to test this in Oracle as all the systems at my disposal is on DB6 . If the above doesnot work then you may request BASIS team to move the TABLE using BR Tools . After that you may check in SE14
Thanks ,
Manu
User | Count |
---|---|
82 | |
9 | |
9 | |
7 | |
7 | |
7 | |
7 | |
6 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.