FWIW, there is a strong case for keeping consistent datafile sizes, similar to the argument for extent sizes. This makes for easier file exchanges for hot to not-so-hot disks, or copying the database to a new system. And segment extent size should be kept in mind, i.e., you don't want to be adding 500Mb files to your tablespace with segment extent size of 128Mb. That gives you about 23% wasted space.
Mike -----Original Message----- OK, I know we had the debate already but lets have another go at it. Say you got a tablespace, lets call it RBS and its for rollbacks. Now, for what reason would you create a 500M file and 4 50M files for this puppy as opposed to just one file. I just cannot see the reasoning for this at all. None. Natta. Zilch. So educate me please if someone out there knows a legit reason they would do this. Lets assume for the sake of argument that disk size and mount point size is not a limitation. Space available to me on any one mount point is unlimited. ___________________________ Kimberly Smith Portland, OR [EMAIL PROTECTED] -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Hand, Michael T 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).
