DBAsupport.com Forums - Powered by vBulletin
Results 1 to 5 of 5

Thread: Poorly sized SYS objects

  1. #1
    Join Date
    Oct 2000
    Location
    Germany
    Posts
    1,185
    I want to reorganize the SYS objects in my database so as not to use so many extents.

    Specifically, I have:

    TableName Extents Size

    IDL_UB1$ 663 86 MB
    SOURCE$ 209 54 MB
    IDL_UB2$ 53 6 MB
    DEPENDENCY$ 35 4 MB
    IDL_SB4$ 24 3 MB
    IDL_CHAR$ 18 2 MB

    I have read on this forum that SYS objects are not included in an Export/Import.

    I would like to find a way to minimize the extents in some of these objects.

    Any ideas?

    Thanks

  2. #2
    Join Date
    May 2000
    Location
    ATLANTA, GA, USA
    Posts
    3,135
    To minimize the number of extents owned by SYS is very difficult. One way of doing is: Take full export. Change the parameters of INITIAL and NEXT in SQL.BSQ file, and then recreate the database.

    Otherwise, just change the NEXT parameter in SYSTEM tablespace. But this will be used only for new extents.

  3. #3
    Join Date
    Oct 2000
    Location
    Germany
    Posts
    1,185
    Thanks for your response.

    I have read on this forum that Oracle will not offer support if the SQL.BSQ file is changed.

  4. #4
    Join Date
    Oct 2000
    Location
    Halifax, Nova Scotia
    Posts
    197
    You are absolutely right dknight. If you alter the bsq file then Oracle will not support you. Its kind of a steep price to pay.
    Don't be afraid to try something new. Amateurs built the Ark, professionals built the Titanic

  5. #5
    Join Date
    Sep 2000
    Posts
    128
    If you don't want to edit your sql.bsq file, you could always create your new database, but before importing modify the 'next' paameters of the objects you want before importing.

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