Re: Re[4]: what exactly 'tim' means in a 10046 TRACE file ?

From: Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk>
Date: Wed, 31 Mar 2004 18:44:35 +0100
Message-ID: <017c01c41747$da404b20$7102a8c0@Primary>

Note in-line

Regards

Jonathan Lewis
http://www.jlcomp.demon.co.uk

The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html

April 2004 Iceland http://www.index.is/oracleday.php June 2004 UK - Optimising Oracle Seminar

• Original Message ----- From: "Edgar Chupit" <chupit_at_tsi.lv> To: "Anjo Kolk" <oracle-l_at_freelists.org> Sent: Wednesday, March 31, 2004 5:34 PM Subject: Re[4]: what exactly 'tim' means in a 10046 TRACE file ?
  :
  : Here is my little test, could somebody confirm that by "fixing"
  : application so it wouldn't insert "duplicate" rows we could perform
  : better than now?
  :
  

As a general rule - yes.

The overhead of 'duplicate key' is that Oracle inserts the row, generating undo and redo, then inserts index entries for the row, generating more undo and redo, until it hits the index that causes the problem. Then it rolls back, generating more redo. Then it looks up the name of the constraint / unique index that caused the problem so that it can insert it into the error message string. It can be a lot of work.

---

Please see the official ORACLE-L FAQ: http://www.orafaq.com

---

To unsubscribe send email to: oracle-l-request_at_freelists.org put 'unsubscribe' in the subject line.

--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------

Received on Wed Mar 31 2004 - 11:45:16 CST