Index for a 200MB table grew to 4GB in 10.2.0.3 database.
Hi All,
recently we faced a problem where we need to drop and recreate index for a 200MB table (Size in physical, logically it have almost100k rows only). this table is heavily used in our application and there are lot of deletion and insertions goes on this table 24*7. its index grew to 4GB. i want to know what could be the problem of this happening on oracle 10g (10.2.0.3.0 version) database. it there anything to monitor this kind of issue or someway to limit the size of any index in database. and how does it impact functioning of database.
Is there any bug in 10.2.0.3.0 which i am missing here.
recently we faced a problem where we need to drop and recreate index for a 200MB table (Size in physical, logically it have almost100k rows only). this table is heavily used in our application and there are lot of deletion and insertions goes on this table 24*7. its index grew to 4GB. i want to know what could be the problem of this happening on oracle 10g (10.2.0.3.0 version) database. it there anything to monitor this kind of issue or someway to limit the size of any index in database. and how does it impact functioning of database.
Is there any bug in 10.2.0.3.0 which i am missing here.
0