RE: max_commit_propagation_delay

From: Lex de Haan <lex.de.haan_at_naturaljoin.nl>
Date: Sat, 11 Jun 2005 13:18:13 -0500 (EST)
Message-Id: <20050610073339.1D50942E0@node42.naturaljoin.lan>

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_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Connor McDonald
Sent: Friday, June 10, 2005 06:13
To: oracle-l_at_freelists.org
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:

1. to any value under its default
2. 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_at_yahoo.com
web: http://www.oracledba.co.uk

"Semper in excremento, sole profundum qui variat"

--
http://www.freelists.org/webpage/oracle-l



--
http://www.freelists.org/webpage/oracle-l

Received on Sat Jun 11 2005 - 14:21:30 CDT