>3gb ram, why cant rollback/temp be in RAM ? (arguement sake)
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 4 of 4

Thread: >3gb ram, why cant rollback/temp be in RAM ? (arguement sake)

Hybrid View

  1. #1
    Join Date
    Apr 2002
    Location
    Phoenix, AZ
    Posts
    175
    Hi All,

    I was wondering with greater amounts of RAM available these days, why can the Rollback Segments and the Temporary
    Segment be part of the RAM.

    I have about 3.5 Gig of RAM on the Server, I dont see why all Rollback and sorts should be written to Disk.
    There is this Sort Segment but it has got its own limitations of sizing.

    Thanks
    Sridhar

  2. #2
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,092
    Rollback in memory? Sounds like a pretty bad idea to me. What happens if your server reboots and you have 1200 transactions in memory?
    Jeff Hunter
    marist89@yahoo.com
    http://marist89.blogspot.com/
    Get Firefox!
    "I pledge to stop eating sharks fin soup and will not do so under any circumstances."

  3. #3
    Join Date
    Apr 2002
    Location
    Phoenix, AZ
    Posts
    175
    Are'nt the transaction in the Redolog ?

    What about temporaty segment ?

  4. #4
    Join Date
    Apr 2001
    Location
    London
    Posts
    725
    You need to learn more about what heppens when an instance fails and how oracle recovers itself to point of failure to understand why rbs is not stored in memmory.

    As far as temporary tablespace is concerned. If you got enough memmory, you don't have to use it.

    set a large value for sort_area_size and monitor v$systat so that sorts(disk) is equal to 0.



    Once you have eliminated all of the impossible,
    whatever remains however improbable,
    must be true.

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