RE: Refresh multiple MV's in a single transaction
Date: Wed, 5 Nov 2008 15:42:03 -0600
So what you are saying is that the transactions that are performing the refresh of the group is are all getting read consistency, but commits occur after each MV is refreshed, so other users querying the MV's will not get read consistency. Correct?
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Finn Jorgensen Sent: Wednesday, November 05, 2008 3:32 PM To: Goulet, Richard
Subject: Re: Refresh multiple MV's in a single transaction
That's what I thought it was for too, but it's not. See my original post :)
I will look into this although the "atomic_refresh" parameter is also present in dbms_mview.refresh(list) and defaults to "true" (according to the documentation) but it doesn't work like that.
On Wed, Nov 5, 2008 at 4:00 PM, Goulet, Richard <Richard.Goulet_at_parexel.com<mailto:Richard.Goulet_at_parexel.com>> wrote: Look into refresh groups. You can have multiple MV's in a single refresh group. Oracle(r) Database Advanced Replication, 3 Materialized View Concepts and Architecture
[CONFIDENTIALITY AND PRIVACY NOTICE] Information transmitted by this email is proprietary to Medtronic and is intended for use only by the individual or entity to which it is addressed, and may contain information that is private, privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient or it appears that this mail has been forwarded to you without proper authority, you are notified that any use or dissemination of this information in any manner is strictly prohibited. In such cases, please delete this mail from your records. To view this notice in other languages you can either select the following link or manually copy and paste the link into the address bar of a web browser: http://emaildisclaimer.medtronic.comReceived on Wed Nov 05 2008 - 15:42:03 CST