Results 1 to 5 of 5
  1. #1
    Join Date
    Aug 2002
    Location
    Shanghai , China
    Posts
    63

    Unanswered: 200MB Rollback Seg

    The SYstem is only accessed by around 20 users and but it does have some large batch process .
    So the 4 rollback seg is created with 200 MB each . Then User
    never faced any problem on the rollback extends:-)

    My question is what's the harm to set the rollback seg bigger like that .
    Oracle is an ocean . I am just a little fish

  2. #2
    Join Date
    Jul 2002
    Posts
    12
    Don't you think oracle takes resource to manage those 200MB or larger?

  3. #3
    Join Date
    Aug 2002
    Location
    Shanghai , China
    Posts
    63
    But at this moment , I can not say how much overhead oracle should take to control the 200MB rollback seg .

    It seems no problem at all
    Oracle is an ocean . I am just a little fish

  4. #4
    Join Date
    Feb 2001
    Location
    NC, USA
    Posts
    200
    I wouldn't worry about it for that size, but if you really don't want it hanging around you could always alter the batch job to bring the segment online only while it's running.

  5. #5
    Join Date
    Apr 2002
    Location
    California, USA
    Posts
    482

    Cool

    No overhead for those big rollback segments. Oracle requires resources only they are in use. You can create some small one for no-batch jobs, and use the huge one's only when the batch job is running.

    Add this in the begging of your batch job:

    ALTER TRANSACTION USE ROLLBACK SEGMENT "huge_rbs_name";

    Hope that helps,

    clio_usa
    OCP - DBA

    .
    .
    .

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •