Quantcast
Channel: SCN : Discussion List - SAP on Oracle
Viewing all articles
Browse latest Browse all 1892

TST03 LOB Segment grows a lot after billing process

$
0
0

Hello,

 

I have a question about LOB Segment corresponding to TST03 (field DCONTENT). TST03 is a table from TEMSE.

 

We are using ECC 6.0 / NW 7.01.

 

After a billing process job which creates arround 5 spool requests with arround 19.100 pages without graphics nor logos, I noticed that DB size growed arround 16 Gb the first time.

 

I used DB02 to detect the grow cause and it was due to the LOB Segment corresponding to field TST03-DCONTENT.

 

Using SP12 (menu TEMSE -> MEMORY ALLOCATION) I noticed that the TEMSE grow was due to these spool requests we generated.

 

I read SAP note [500340 - FAQ: LOBS|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=745639] and detected that this LOB Segment had RETENTION attribute activated.

 

We deleted the spool requests with SP01 transaction (or report RSPO1041) and run again the billing process. Then de LOB Segment growed again arround 16 Gb (now with a total size of arround 32 Gb). I understood again the meaning of RETENTION property explained in that SAP note.

 

Then I decided to activate property PCTVERSION instead of RETENTION. I set PCTVERSION to 1 (1% of allocated space for this LOB Segment is now reserved for storing before images). In this case (32 Gb size) arround 320 Mb is reserved.

 

We deleted again the last spool requests and run once more time the billing process. I supposed that this LOB, with 32 Gb reserved would not grow now again, as it had 320 Mb reserved for undo management and the rest to 32 Gb with free blocks.

 

But we detected that this LOB Segment growed again to 43.530 Mb.

 

We deleted again the spool requests and run again the billing process (always is the same billing process). Now the LOB segment growed 320 Mb, to a total size of 43.850 Mb. This is normal if we suppose that the billing process spool requests  need these 43.530 Mb more or less. As the LOB Segment had 435 Mb reserved for undo (1% of 43.530 Mb), it needed to increase its size that quantity more or less.

 

I have 2 questions:

 

- Is this LOB Segment behavour correct according to its PCTVERSION=1 property activated (instead of RETENTION)?

 

- Is it normal that about 19.100 billing pages (without images nor logos) in 5 spool requests used 43.850 Mb in LOB Segment corresponding to table TST03? This is an average of arround 2,2 Mb/page.

 

I think I do not understand something about LOB Segments.

 

Any help will be appreciated.

 

Thanks in advance and best regards.


Viewing all articles
Browse latest Browse all 1892

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>