LOCALLY MANAGED TABLESPACES IN 8i
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 7 of 7

Thread: LOCALLY MANAGED TABLESPACES IN 8i

  1. #1
    Join Date
    Oct 2001
    Posts
    9
    I AM CONFUSED ABOUT A FEATURE OF LOCALLY MANAGED TABLESPACES.
    IN A LOCALLY MANAGED TABLESPACE WE CAN NOT GIVE STORAGE FEATURES
    LIKE INITIAL , NEXT EXTENT , BUT WHILE CREATING A TABLE INSIDE A
    LOCALLY MANGAGED TABLESPACE IT IS ALLOWING ME TO GIVE THESE
    PARAMETERS ?
    HOW , CAN ANYONE EXPLAIN THIS.


  2. #2
    Join Date
    Jun 2001
    Location
    Helsinki. Finland
    Posts
    3,938
    If your uniform extent size is say 1M, and you try to create a table with initial 5M, Oracle will allocate 5 extents each being 1M. 1M is the uniform size of the tablespace. In that case, your initial segment will consists of 5 extents.


  3. #3
    Join Date
    Jun 2000
    Location
    Madrid, Spain
    Posts
    7,447
    because initial, next still works at segment level but physically they are divided in extent sizes


    for example tablespace uniform extent size is 512K, you specify initial 2M, Oracle will allocate 4 512K extents for your initial, same applies for next

  4. #4
    Join Date
    Oct 2001
    Posts
    9

    re: locally managed tablespaces

    FIRST OF ALL THANX FOR THE PROMPT REPLY
    BUT I AM STILL BNOT CLEAR.
    WHY IT IS ALLOWING THE SYNTAX FOR STORAGE SETTINGS WHEN ON TABLESPACE LEVEL ITSELF IT DOES NOT PERMIT THE SETTINGS.
    REGARDS
    AMIT

  5. #5
    Join Date
    Jun 2000
    Location
    Madrid, Spain
    Posts
    7,447
    If you want to know you probably have to ask developers in Oracle, I dont think even the support would know why
    But since many people still think a large initial would improve perfomance dramatically therefore they wont get *used* when they cannot set storage at segment level

  6. #6
    Join Date
    Jun 2001
    Location
    Helsinki. Finland
    Posts
    3,938
    With LMTs it doesn't really matter how many segments/extents you have.


  7. #7
    Join Date
    Sep 2001
    Posts
    112
    It's for backwards compatibility of applications that run on an Oracle database.

    Take BroadVision for example. When you create a table in BV it gives the storage parameters as a parameter to Oracle. This cannot be changed by me so if including these parameters in LMT caused an error this app would stop working. So they are effectively read and ignored by Oracle.

    That way my third party software keeps working. Maybe in the future it will raise an error.

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