rbs settings in limited diskspace
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 3 of 3

Thread: rbs settings in limited diskspace

  1. #1
    Join Date
    Oct 2002
    Location
    Singapore
    Posts
    49

    rbs settings in limited diskspace

    Hi,

    Is there any good standard to follow when configuring the RBS. Currently running 8.1.6 using the default rbs created when db was created using the Installer. There are 8 rbs segments under its' own tablespace called RBS.

    We have a huge transaction that cause the rbs to grow till the entire file system becomes full (100%), thus hanging the entire database. The RBS tablespace is autoextensible. We were thinking of making the RBS tablespace non-extensible to prevent such a case from happening. Does this have any impact?

    Another question, when a rollback occurs, due to a process that is killed before commiting, will archive logs be generated because of this?

    Thanks.
    Regards
    CF

  2. #2
    Join Date
    Dec 2002
    Location
    Bangalore ( India )
    Posts
    2,434

    Re: rbs settings in limited diskspace

    Originally posted by feng11
    Hi,

    We were thinking of making the RBS tablespace non-extensible to prevent such a case from happening. Does this have any impact?

    Surely u will face probs, if transaction are tooo big....u will get snapshot error or rollback seg too small error........

    TO overcom.....commit the TRAN in program regularly........

    abhay.
    funky...

    "I Dont Want To Follow A Path, I would Rather Go Where There Is No Path And Leave A Trail."

    "Ego is the worst thing many have, try to overcome it & you will be the best, if not good, person on this earth"

  3. #3
    Join Date
    Sep 2001
    Posts
    37
    Originally posted by feng11

    The RBS tablespace is autoextensible. We were thinking of making the RBS tablespace non-extensible to prevent such a case from happening. Does this have any impact?
    There's is one way to control de extension of yor RBS in 8i, and it's
    using the Optimal Size parameter in the storage clause of the RBS.
    When you set it, RBS that have extended beyond this value will automatically shrink.

    You can check the Rollback's use statistics joining V$ROLLSTAT and V$ROLLNAME for then estimate the optimal size of your RBS.
    This value should be set to minimize the number of extensions and shrinks required for support the size and volume of transactions.

    Estimate a value and check statistics periodically.. if there are pretty much shrinks you must increase Optimal Size of your RBS.

    This method allow you to keep autoextend TRUE in your RBS for larger transactions.. and allow you a better space administration for them.

    Hope it helps..

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