RE: ISOLATION LEVEL
- From: "Kerber, Andrew W." <Andrew.Kerber@xxxxxxx>
- To: oracle.tutorials@xxxxxxxxx, "oracle-l" <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 10 Jul 2007 09:43:27 -0500
If there is no ddl to run, then it appears to me that set transaction
read only is the command Oracle designed for this situation. Or, as
Niall stated, use an anonymous block.
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of DBA Deepak
Sent: Tuesday, July 10, 2007 4:09 AM
To: oracle-l
Subject: ISOLATION LEVEL
Hi All,
Have a doubt on transaction isolation.
My requirement is to query several tables several times inside a piece
of code. The data needs to be consistent across multiple queries. The
underlying tables are subjected to change during the execution of the
piece of code.
I have two options to be used inside my piece of code to achieve
consistent/repeatable reads.
1> to use SET TRANSACTION READ ONLY;
2> to use ALTER SESSION SET ISOLATION_LEVEL=SERIALIZABLE;
My question is which option is preferable and why? Is there any
performance issues with one of these in the above mentioned scenarios?
Need your valuable feedback.
--
Regards,
Deepak
Oracle DBA
------------------------------------------------------------------------------
NOTICE: This electronic mail message and any attached files are confidential.
The information is exclusively for the use of the individual or entity intended
as the recipient. If you are not the intended recipient, any use, copying,
printing, reviewing, retention, disclosure, distribution or forwarding of the
message or any attached file is not authorized and is strictly prohibited. If
you have received this electronic mail message in error, please advise the
sender by reply electronic mail immediately and permanently delete the original
transmission, any attachments and any copies of this message from your computer
system. Thank you.
==============================================================================
Other related posts:
