Initial Extent sizes on tables - Page 2
DBAsupport.com Forums - Powered by vBulletin
Page 2 of 2 FirstFirst 12
Results 11 to 18 of 18

Thread: Initial Extent sizes on tables

  1. #11
    Join Date
    Jun 2001
    Location
    Helsinki. Finland
    Posts
    3,938

    If LMTs are used, are Dr.Codd's principles of RDBMS violated?
    :-)))))))


  2. #12
    Join Date
    Nov 2001
    Location
    Chennai
    Posts
    22
    But tablespaces were part of DD

    Dr. Codd's rule states that data dictionary should be the ultimate reference point for all database objects. I understand that tablespaces are also part of the database object definitions and hence my query about violation of Codd's rules.....

  3. #13
    Join Date
    Jun 2000
    Location
    Madrid, Spain
    Posts
    7,448
    tablespace is transaparent, when Codd stated the rule I doubt tablespaces were invented?

  4. #14
    Join Date
    Nov 2001
    Location
    Chennai
    Posts
    22
    Now that LMTs have the storage parameters as part of themselves, how do we query them?


  5. #15
    Join Date
    Jun 2001
    Location
    Helsinki. Finland
    Posts
    3,938
    Originally posted by sundaju
    But tablespaces were part of DD

    Dr. Codd's rule states that data dictionary should be the ultimate reference point for all database objects. I understand that tablespaces are also part of the database object definitions and hence my query about violation of Codd's rules.....
    Which Codd's rule are you refering to? No rule of Codd mentions tablespaces.


  6. #16
    Join Date
    Jun 2000
    Location
    Madrid, Spain
    Posts
    7,448
    Originally posted by sundaju
    Now that LMTs have the storage parameters as part of themselves, how do we query them?

    they are stored in datafile headers that is why querying the storage parameters in LMT has more overhead

  7. #17
    Join Date
    Aug 2000
    Posts
    236
    Fellow DBA's,

    I was testing the use of LMT's on a test database. From a 14MB dump file, when I import it into a dictionary managed tablespace, it fills up 24 MB. But when the same dump is imported into an LMT, it need 340MB of datafile space.

    I know this sounds crazy, but does anybody have any explanations for this. Also when creating a LMT what is the difference between extent autoallocate and uniform size.

    Thanks,
    Nizar

  8. #18
    Join Date
    Nov 2001
    Location
    Chennai
    Posts
    22
    In LMTs,

    Uniform extents will cause Oracle to allocate extents of uniform size in the tablespace. If the initial extent size is greater than this size, then Oracle will allocate enough uniform extents to match the amount of space requested for the initial extent.

    On the other hand, when AUTO ALLOCATE is used, Oracle uses an internal algorith to control the extent sizes.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width