Oracle Database Discussions

Hello members,

I am currently doing maintenance work on a 10.2 application. This has quite a few xmltype columns, and I've noticed one thing;
all of these are created with no considerations given to physical properties. Meaning - among other things - that all are enable storage in row.

I am planning to do something about this, but first I was reading through the lob developers guide (Both 11.2 and 10.2 since we are in our final year of 10g)

Doing this, I came across this little sentence:

TABLESPACE and LOB Index
Best performance for LOBs can be achieved by specifying storage for LOBs in a tablespace different from the one used for the table that contains the LOB. If many different LOBs are accessed frequently, then it may also be useful to specify a separate tablespace for each LOB column or attribute in order to reduce device contention.


Which strikes me as kind of odd, playing the performance card here. It makes me wonder if this is the "Separate Index Table Space" revived?

Or is there more to it? - Is there any reason for separate lob tablespace, and if no performance reason, what then?

Any comments?

Regards
Peter

P.S: I may decide to enjoy my week-end, so I may not follow up right away ;)