Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: Phantom Read

Re: Phantom Read

From: Mark D Powell <Mark.Powell_at_eds.com>
Date: 8 Jun 2005 08:11:33 -0700
Message-ID: <1118243493.496124.308640@o13g2000cwo.googlegroups.com>


dd, the drawback of serializable reads is that attempting to make transactions run this way kills application performance. Either the sessions single thread or error off because Oracle is unable to serialize the transaction.

The Oracle concurrency model was chosen to provide high concurrent data access while providing time consistent views of the data. You need to give consideration to the effect of concurrent access to the data involved in all multistatement transactions. The fact that writers do not block readers is very important in situation such as where you try to use table triggers to enforce referential integrity rules rather than FK.

HTH -- Mark D Powell -- Received on Wed Jun 08 2005 - 10:11:33 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US