Thursday, July 19, 2001, 12:42:33 PM, Kimberly Smith wrote:
KS> However, I was under the impression that you could not specify a next in the
KS> storage clause of a table creation. Yet you can. So what happens if I have
KS> a next defined? Do they pretty much just throw that away or should I really
KS> not define it?
It's been awhile since I've tested any of this, but I
believe Oracle just ignores whatever you specify for NEXT.
I do recall for sure the behavior with INITIAL. You can
specify INITIAL, but the autoallocate algorithm then takes
over to give you multiple extents that add up to whatever
size you requested for your initial extent. So with
autoallocate, you can use INITIAL to request a certain
amount of space, but you may get it in multiple extents.
Best regards,
Jonathan Gennick
mailto:[EMAIL PROTECTED] * 906.387.1698
http://Gennick.com * http://MichiganWaterfalls.com * http://MetalDrums.org
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Jonathan Gennick
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
