| Restriction on local index partitions? [message #61820] |
Wed, 02 June 2004 10:48 |
Michael
Messages: 61
Registered: October 1999
|
Member |
|
|
We are on 9.2.0.3 on Solaris 8.
I just took over as dba for a large DWH, and just ran into a problem with the index on a large partitioned table. This table is divided into monthly partitions. Up until Nov of '03, the tablespaces for the new monthly partitions were defined as locally managed autoallocate, and Oracle was doing a fine job adding the index partitions into the tablespaces created for the table partitions. Then the previous dba created a bunch of new tablespaces for the future partitions (at that time, Dec 03 to May 04), but these tablespaces are all defined as locally managed with a uniform extent size of 10m. Now, Oracle is dumping all of the new index partitions into the default tablespace, which in this case is the first (oldest) partition in the table, April of 2000. I seem to remember reading that this is the expected behavior, because Oracle wants to manage the space itself and does not want to see a uniform extent size for index partitions. I am having a devil of a time confirming this, and would appreciate if someone out here can confirm my suspicion and provide a reference.
Thanks.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
