Re: ON COMMIT FAST MViews seems to be less than bulletproof

From: Jared Still <jkstill_at_gmail.com>
Date: Mon, 18 Jun 2007 21:30:55 -0700
Message-ID: <bf46380706182130r2e580ce9mdc79761fda2a37ce@mail.gmail.com>

On 6/15/07, Brady, Mark <Mark.Brady_at_constellation.com> wrote:
>
>
> Fri Jun 15 10:49:03 2007
>
> Following on-commit snapshots not refreshed :
>
> DEALNET.BROWSER_MV_INFO
>
> DEALNET.BROWSER_MV_STATUS
>

Not a lot to go on here.

As Alexander Fatkulin has pointed out, putting a constraint on the MV can break the refresh.

Do you have any unique indexes on your MV tables to mirror what is found on a source table?
Or unique indexes of any kind for that matter?

If so, you may need to recreate them as std indexes. Unique indexes cause problems with
Materialized Views, as duplicate values can exist during the refresh.

Jared

-- 
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist

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

Received on Mon Jun 18 2007 - 23:30:55 CDT