Results 1 to 4 of 4
  1. #1
    Join Date
    Jan 2005

    Unanswered: What are the real risks of using commit_logging

    What are the risks of using commit_logging=batch in a critical application? The problem is that addm is reporting:

    Waits on event "log file sync" while performing COMMIT and ROLLBACK operations were consuming significant database time.
    and the application can't be modified in order to reduce the number of commits.


  2. #2
    Join Date
    Aug 2003
    Where the Surf Meets the Turf @Del Mar, CA
    Provided Answers: 1
    >What are the risks of using commit_logging=batch in a critical application

    post SQL & results that show what is actually gained by doing so.
    You can lead some folks to knowledge, but you can not make them think.
    The average person thinks he's above average!
    For most folks, they don't know, what they don't know.
    Good judgement comes from experience. Experience comes from bad judgement.

  3. #3
    Join Date
    Jun 2004
    Liverpool, NY USA
    How many log files do you have? You shouldn't have to wait on a log file.
    You do not need a parachute to skydive. You only need a parachute to skydive twice.

  4. #4
    Join Date
    Oct 2002
    Cape Town, South Africa
    • Setting commit_logging is set to batch, Oracle writes redo data in batches. This causes less traffic, but indices risk because an instance crash may cause loss of data that is being batched inside the log buffer.
    Good ol' Burleson knows his stuff:

    Basically, by setting logging to batch, you are taking a risk that any sort of failure (disk, power failure, etc.) could put your db in a situation where you can't recover.

Tags for this Thread

Posting Permissions

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