DBAsupport.com Forums - Powered by vBulletin
Results 1 to 3 of 3
  1. #1
    Join Date
    Jul 2002

    Whether COALESCE table space is need for LMT tables..?

    Whether COALESCE table space is need for LMT tables..?

  2. #2
    Join Date
    May 2002
    Locally Managed Tablespaces

    A tablespace that manages its own extents maintains a bitmap in each datafile to keep track of the free or used status of blocks in that datafile. Each bit in the bitmap corresponds to a block or a group of blocks. When an extent is allocated or freed for reuse, Oracle changes the bitmap values to show the new status of the blocks. These changes do not generate rollback information because they do not update tables in the data dictionary (except for special cases such as tablespace quota information).

    Locally managed tablespaces have the following advantages over dictionary managed tablespaces:

    * Local management of extents automatically tracks adjacent free space, eliminating the need to coalesce free extents.
    * Local management of extents avoids recursive space management operations. Such recursive operations can occur in dictionary managed tablespaces if consuming or releasing space in an extent results in another operation that consumes or releases space in a data dictionary table or rollback segment.

  3. #3
    Join Date
    Mar 2004
    Quote Originally Posted by skdas
    Whether COALESCE table space is need for LMT tables..?
    System will take care of LMT's, stay
    "What is past is PROLOGUE"

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

We have made updates to our Privacy Policy to reflect the implementation of the General Data Protection Regulation.