Oracle partitioned indexes...
-
I thought that I understood them, but they aren't working as I expected. Perhaps someone can help dispel my confusion? I have a table that is comprised of an incrememnting, numeric primary key, a date field, and several other fields (that are irrelevant to the problem). It is range partitioned by day on the date field, thus creating a new table partition for every 24 hours of data. The problem comes when I need to drop an old partition. I created the PK index as LOCAL, which (as I understood from the documentation) should have made it equipartition with the table. However, when the old partition(s) are dropped, it becomes unusable, and rebuilding the index can take hours (it is a VLDB). Any ideas what I am doing wrong..? Thank you.
-
I thought that I understood them, but they aren't working as I expected. Perhaps someone can help dispel my confusion? I have a table that is comprised of an incrememnting, numeric primary key, a date field, and several other fields (that are irrelevant to the problem). It is range partitioned by day on the date field, thus creating a new table partition for every 24 hours of data. The problem comes when I need to drop an old partition. I created the PK index as LOCAL, which (as I understood from the documentation) should have made it equipartition with the table. However, when the old partition(s) are dropped, it becomes unusable, and rebuilding the index can take hours (it is a VLDB). Any ideas what I am doing wrong..? Thank you.
Found this answer from Ask Tom... It appears that I have no choice but to use a global index on the PK.