Oracle Database Administration from Zero to Hero - Shrinking Segments (Part 2 of 2)

This lecture covers methods for managing database space, focusing on shrinking tables, deallocating unused space, and moving tables. It explains the steps for shrinking database segments, including enabling row movement and handling table indexes. The lecture also discusses the use of COMPACT and CASCADE options, analyzing table space, and guidelines for deciding when to shrink tables. Additionally, it covers deallocating unused space and moving tables while maintaining index usability.

What is a necessary step before shrinking a database table?

• Disable all indexes

• Delete all data

• Increase the high watermark

• Enable row movement

Which option is used to shrink dependent objects along with a table?

• COMPACT

• CASCADE

• REBUILD

• DEALLOCATE

What is the primary benefit of shrinking fragmented tables?

• Increased index performance

• Higher transaction speed

• Reduced number of blocks to scan

• Lower memory usage

When should you consider shrinking a table?

• When the table is newly created

• When the table is rarely used

• When there is a high percentage of deleted space

• When the table is frequently accessed

What is the effect of the ONLINE option when moving a table?

• It disables all indexes

• It pauses all DML operations

• It allows DML operations to continue

• It speeds up the move process

What happens to indexes when a table is moved without the UPDATE INDEXES option?

• They are automatically rebuilt

• They become unusable

• They are deleted

• They remain usable

What does the DEALLOCATE UNUSED statement do?

• Releases unused blocks above the high watermark

• Compacts the table

• Moves the table to a new tablespace

• Releases used blocks