TRUNCATE Table Command
From: Rennick Sandra <t89003_at_isdserv.dehavilland.ca>
Date: 1995/06/15
Message-ID: <1995Jun15.180113.6313_at_dhnews.dehavilland.ca>#1/1
Date: 1995/06/15
Message-ID: <1995Jun15.180113.6313_at_dhnews.dehavilland.ca>#1/1
We have just encountered an interesting situation using the TRUNCATE TABLE command with the DROP STORAGE option. We have a table that was originally defined with a NEXT extent of 1M. Several weeks ago, we changed the NEXT extent to be 10M. After we truncated the table, the NEXT extent was redefined to the original value of 1M. Not knowing that this would happen, we then attempted to import data into the table, and ran out of extents.
Has anyone seen this before? Can anyone explain why this happened?
We are using ORACLE 7.0.16 on AIX.
Thanks
Sandra Rennick Received on Thu Jun 15 1995 - 00:00:00 CEST