Hello,
we have delete a CM(store DB) from the Portal over the pathe
systemadministation, systemconfiguration, knowledge management, content
management.
Then we select the systemadministration reports.We execute the reports
CM-Repository-Databasecheck and the unconfiguration cm repositories. We
found 4 millions objects. Then we remove this objects with this report.
The table in the Portal KMC_DBRM_CONTENT at the moment is about 230GB!
We have reorg the table via db13 from the Solution Manager but the free
space after the reorg ist not the free space we have expected.
We open a message in the sapnet and this ist the answere:
saptpp:2> select max(length(content)),min(length(content)) from
KMC_DBRM_CONTENT
5643029 6
1 record(s) selected.
saptpp:3> select sum(bigint(length(content))) from KMC_DBRM_CONTENT
177737257162
1 record(s) selected.
This means that the maximum length of the lob field of table
KMC_DBRM_CONTENT is ~5.6MB. All LOB data together have a length of
~177GB. I assume that the rest of the data is
1. regular table data for the ~5.4mio table entries
2. administrative overhead for LOBs
3. wasted space for the LOB data
I suggest to check the following link
http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/topic/com.ibm.db2.luw.admin.dbobj.doc/doc/c0052385.html
From SAP point of view, there is little we can do about this. I assume
that DB2 is working as designed at this point.
We can´t reorg this table and if we fill this table because we must send 6000000 pictures to the portal in the km we need a lot of harddisk-space. We use a standard webservice. Here the second answere from the sap.
Hello,
I again checked the system. The number of entries in the table is
5507193.
select sum(bigint(length(content))) from KMC_DBRM_CONTENT
1
-
-
199983271544
1 record(s) selected.
select avg(bigint(length(content))) from KMC_DBRM_CONTENT
1
-
-
36351
1 record(s) selected.
Also, there are 286727312 kByte allocated for the LOB Object. So the
table has ~290GB. ~200GB is for the LOB data. The rest is wasted space.
So we see that the LOB object wastes about 30% of it's space. With the
allocation strategy in mind I assume this is somehow realistic.
If you need to check the space requirements before and after deletion ofdata (+ REORG), run the following set of SQL commands before and after
deletion.
select sum(bigint(length(content))) from saptppdb.KMC_DBRM_CONTENT
;
select avg(bigint(length(content))) from saptppdb.KMC_DBRM_CONTENT
;
select substr(tabname,1,20) as table,
data_object_l_size,data_object_p_size,long_object_l_size,long_object_p_size,lob_object_l_size,lob_object_p_size from sysibmadm.admintabinfo
where tabname = 'KMC_DBRM_CONTENT'
We can´s use the sore filesystem because we have so many folders.
Anybody an idea?
