| parameter max_commit_propogation_delay in RAC env. [message #136557] |
Thu, 08 September 2005 13:35  |
ashishsinghal77
Messages: 9
Registered: August 2005
|
Junior Member |
|
|
Hi,
I am using 2 instance in rac env. and updating data in 1 instance and reading the same data in other instance, after the commit also for sometimes changes are not visible immediately into the 2'nd instance, can i use max_commit_propogation_delay parameter to see the immediate effect of commit, by setting this parameter value to 0.
i want to know what are the effects of setting this parameter value to 0. and by setting this parameter value to 0 will i be able to resolve the problem..
Ashish
|
|
|
|
|
|
| Re: parameter max_commit_propogation_delay in RAC env. [message #137163 is a reply to message #136933] |
Tue, 13 September 2005 08:54  |
ashishsinghal77
Messages: 9
Registered: August 2005
|
Junior Member |
|
|
Hi Frank,
Thanx for ut response..
i set the parameter max_commit_popogation_delay = 0, bt then also my queries are not syncronized,
like we have 2 nodes, and in 1 nodes we are updating 1 table and immediatly after commit we are reading the same data from the 2'nd node but the changes are nt vivible in the second node..
can u please advise me what i can do in this situation..
Regards
Ashish
|
|
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
