RE: max_commit_propagation_delay
- From: "Lex de Haan" <lex.de.haan@xxxxxxxxxxxxxx>
- To: <mcdonald.connor@xxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Fri, 10 Jun 2005 09:40:02 +0200
I remember a situation where the value had to be lowered, for the following
reason:
they had multiple applications, running on different instances against the same
database;
at the same time, they had the requirement that inserts should be visible
immediately after commit.
with the default SCN generation process in a RAC environment, sometimes you will
not see those committed inserts.
bad application design, of course ...
kind regards,
Lex.
------------------------------------------------------------------
Steve Adams Seminar http://www.naturaljoin.nl/events/seminars.html
------------------------------------------------------------------
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Connor McDonald
Sent: Friday, June 10, 2005 06:13
To: oracle-l@xxxxxxxxxxxxx
Subject: max_commit_propagation_delay
In the absense of currently having a RAC environment to play around with, does
anyone have any "gut feel" responses to the impact of dropping the commit
propagation:
a) to any value under its default
b) to zero
(yeah, I know this is a "how long is a piece of string" question)
Cheers
Connor
--=20
Connor McDonald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
email: connor_mcdonald@xxxxxxxxx
web: http://www.oracledba.co.uk
"Semper in excremento, sole profundum qui variat"
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
