Table defragmentation/resizing question: Is this dangerous ?

Suddenly, I'm starting to doubt about a procedure used here:

• On a production database, table A goes to its MAX EXTENT REACHED

Resolution:

• The DBA exports the table with export (CONSISTENT=Y)
• The DBA drops the table (Or truncates and adjust storage)
• The DBA re-imports the table

Is this OK or should I arrange for ALL USERS to exit and prevent them to connect during this intervention ?

If the DBA permits the users to connect whil fixing the problem, while the table is dropped and while it is in the process of being reloaded, I wonder what happens if users are hitting the table (inserting or deleting in it).

Isn't the integrity of the data compromised ?

Thanks Received on Mon Jan 17 2000 - 14:28:02 CST