Results 1 to 2 of 2
  1. #1
    Join Date
    Sep 2003
    Posts
    5

    Question Unanswered: Rollback too large?

    I have an insert statement that inserts about 30,000 - 100,000 depending upon which market. Our dba's have our rollback segment set to around 22 GIG! I'm trying to explain to them that this may be a reason why the insert is taking 3 hours on our production box vs. our dev box that has a rollback seg of around 500 meg.

    Am I way off on this? Can a rollback segment that is too large actually slow things down?

    Thanks,
    Eric

  2. #2
    Join Date
    Aug 2003
    Location
    Where the Surf Meets the Turf @Del Mar, CA
    Posts
    7,776
    Provided Answers: 1

    Re: Rollback too large?

    Originally posted by natter
    I have an insert statement that inserts about 30,000 - 100,000 depending upon which market. Our dba's have our rollback segment set to around 22 GIG! I'm trying to explain to them that this may be a reason why the insert is taking 3 hours on our production box vs. our dev box that has a rollback seg of around 500 meg.

    Am I way off on this? Can a rollback segment that is too large actually slow things down?

    Thanks,
    Eric
    I seriously doubt having a large RBS is the source of 3 hour loads.
    The BEST way to actually determine where the problem exists is to
    ALTER SESSION SET SQL_TRACE=TRUE
    before starting to load the data.
    After the load completes, run the trace file thru TKPROF
    to see where all the time is being spent.

    Don't guess at what the problem may or may not be.
    Collect facts which will assist to indentify what really is the problem.

    HTH & YMMV

    HAND!

Posting Permissions

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