This has nothing to do with ASM which only exists on 10g. Nor do I believe that what you are seeing is directly related to ASSM in 9+. It looks to me that your tablespace was created using auto-allocate as the allocation method and the behavior you described is in line with it. It would be helpful if you had posted the create tablespace DDL or the dba_tablespaces values for the tablespace. HTH -- Mark D Powell -- -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Mercadante, Thomas F Sent: Friday, December 17, 2004 9:56 AM To: Oracle-L Subject: Automatic Space Management Observation All, I finally turned ASM on in my 9.2 database. The tablespaces were created with no defaults - no uniform extent sizes. Oracle created the tables all with 1M extent size. When loading a table, I notice that the first 64 extents were all 1M in size. The last 9 extents are all 8M in size. So, is this how ASM works? Just curious if anyone else has had similar or different experiences? Thomas Mercadante Oracle Certified Professional -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l