ak, I have located my indexes in different tablespaces according to size of the index and catagory. Small indexes are in one tablespace with 4K extents and medium in 1M extents with the large in 20M extends. The tables that are partitioned also have the indexes partitioned. Some tables span multiple datafiles as one years worth of data for some tables is over 3 GIG.Works out great with the sizes I used in this database as there is very little free space on the tablespaces. I created them to accomidate the sizes needed. I have very few table or indexes with over 100 extents. Ron >>> [EMAIL PROTECTED] 07/22/03 12:54PM >>> At present we have one tablespace containign all indexes . Some indexes are big in size some are small . Currently tablespace is dict managed. This tablespace currently highly fragmented . Now I am planning to move the indexes to a LMT. Now how to decide what should be the extent size for uniform extents ? What is better approach to divide indexs A ) should I devide them that based on size ( big, small ) and create seperate tablespaces with different values for extent size . b) or seperate them based on modules sooo that accounting and manufactring related indexes goes to different tablespace.
Does number of extents is a performance issue in LMT as well ? Any experience ? Thanks, -ak -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Ron Rogers INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
