RE: dbms_refresh
- From: Chuck Boddy <Chuck.Boddy@xxxxxxxxxxxxxxx>
- To: Jared Still <jkstill@xxxxxxxxx>
- Date: Wed, 13 Oct 2010 10:59:19 -0700
Hi Jared,
I'll try that...The materialized view in question is just a snapshot table..the
trigger populates a table with aggregate values...pretty straightforward...
Thanks,
Chuck
From: Jared Still [mailto:jkstill@xxxxxxxxx]
Sent: Wednesday, October 13, 2010 10:28 AM
To: Chuck Boddy
Cc: Alisher Yuldashev; oracle-l
Subject: Re: dbms_refresh
On Wed, Oct 13, 2010 at 10:21 AM, Chuck Boddy
<Chuck.Boddy@xxxxxxxxxxxxxxx<mailto:Chuck.Boddy@xxxxxxxxxxxxxxx>> wrote:
Hi Alisher,
I have a trigger off of one of the materialized views that I want to fire
before the other materialized views. The trigger was created after the refresh
group with the list of materialized views that are being refreshed. So, I want
to change the order, but can't see how this can occur.
There are probably several ways to do this.
1) use 2 refresh groups. use a stored procedure to execute the refreshes in
the order you want
2) use dbms_scheduler with 2 refresh groups and dependencies
...
A trigger on an MV? Sounds dangerous...
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
Oracle Blog: http://jkstill.blogspot.com
Home Page: http://jaredstill.com
Other related posts:
