on 12-03-2012 9:18 AM
Hi,
I have a LOB segment which is 126 GB in size. The total size of my db is 294GB which means that the LOB segment occupies almost 42% of the total size.
Is there any way of compressing it? If so, what are the analysis to be done before proceeding with the compression.
The SAP system is a PI system and oracle version being used is 11gR2. OS: Sun solaris.
Regards,
Varsha Bellary.
Hi Varsha,
Please find the how to information in the document, below;
Note 1431296 - LOB conversion and table compression with BRSPACE 7.20
By the way, I assume that you have a problem with the payload tables such as SXMSCLUP and SXMSCLUR. Belong to the PI system, I suggest you activate the switch procedure first . Then, archive the payload tables, periodically. Please find the related documents, below;
Archive procedure:
Switch procedure:
http://wiki.sdn.sap.com/wiki/display/XI/Overview+of+the+Switch+Deletion+Procedure
By doing so, table reogranization will be done by the system automatically, when the threshold level exceeded.
On the other hand, you can reorganize the tables manually, in order to reclaim the free space to the storage.
Best regards,
Orkun Gedik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Gedik,
i am performing table compression one of PROD system , i have sort out the all tables using the scripts as per note 1438410.
i have a small doubt in LOB list , what are the differences between S1,B1,B2 and B3.
is there any latest note for SQL scripts .. can you please help me.
regards,
Balaram
Hi Balaram,
>> i have a small doubt in LOB list , what are the differences between S1,B1,B2 and B3.
Could you clarify what script you are running?
>> is there any latest note for SQL scripts .. can you please help me
OSS notes have been updating, regularly. So, you'll be find latest version when you browse
Best regards,
Orkun Gedik
Hm, this sounds familiar. Theoretically yes you can try to compress the lob segment. Things that can spoil your efforts:
- lobs can have inline (in the table block) storage for objects < 4kb
- lob data often is already compressed
- you don't have a securefile lob already (mainly objects created prior 11g)
Check notes:
LOB conversion and table compression with BRSPACE 7.20
Oracle 11g Advanced Compression for SAP Systems
Oracle 11g: SecureFiles - The new way to store LOB data
Now to the PI specifics. I am guessing the lob segment is a column in table SXMSCLUP, which is one of the main tables that hold message data.
If that is true, then i have to ask if you are regularly deleting data from that table? You either have to delete old messages or apply a archiving strategy to prevent SXMSCLUP from growing endlessly.
Cheers Michael
PS: just that you know, we have an issue where the table's lobsegment was still growing even when we properly delete old data from it (PI 7.3 / Oracle 11.2.0.2)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
89 | |
10 | |
9 | |
9 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.