Thanks for the question, vinesh.
Asked: April 28, 2022 - 10:57 am UTC
Last updated: May 03, 2022 - 3:49 am UTC
Version: 19c
Viewed 1000+ times
You Asked
Team,
For our reference , looks like any table structure or sample data is not needed over here.
Below is the stats of our DB user
SEGMENT_TYPE SIZE_IN_GIG(GB)
INDEX 121.2262573
LOBINDEX 0.010986328
LOBSEGMENT 3.181213379
TABLE 171.7533569
I had a question from my Project Manager ,stating why the index segment type is taking such huge sizes.
A small note : Tables are occupying 170 GB and at the same time Indexes are occupying 120 GB . Looks like Indexes are occupying huge space.
I Request our humble intellectuals to throw some light on this.
Any suggestions most welcome.
Any detailed recommendations on how Indexes work internally is most welcome.
Further do you recommend us to rebuild the indexes using "alter index index_name rebuild online".
Or Gathering the schema stats would help us in reducing the sizes ?
Thanks and Regards,
Vinesh
and Connor said...
It is not uncommon for indexes to be on similar size to the tables in your database. I don't see any cause for concern in those numbers you've quoted.
Further do you recommend us to rebuild the indexesNo. See the following video
plus this excellent whitepaper
https://richardfoote.files.wordpress.com/2007/12/index-internals-rebuilding-the-truth.pdf Maybe start looking at DBA_INDEX_USAGE to see if there are any indexes in there you do not need, and monitor them over time.