Database Tuning (MOSC)

MOSC Banner

index behavior after truncate table or delete rows from table

edited Mar 15, 2016 11:18AM in Database Tuning (MOSC) 3 commentsAnswered ✓

oracle DB: 11.2.0.4

Load 250,000 rows daily in daily partition table.

I have a stage table that we truncate data everyday and reload aprox. 250,000 rows daily. This table have 1 bitmap and 2 btree indexes.

when I deleted all rows or truncated the table or inserted some rows back into the table. Indexes on this table were not marked UNUSABLE / STALE or INVALID. If we don't rebuild indexes every time we remove 20% + rows or truncate table, how does these indexes behave during select / insert/ delete /updates? does Oracle create/use a   bad plans?

One more thing I noticed that after I performed, truncate / delete update, the dba_ind_statistics/ dba_tab_statistics table did not show these indexes as stale.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center