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

As one example...

SQL> create table t (n number);

Table created.

SQL> create materialized view mv_t
 2   refresh complete on commit
 3   with rowid
 4   as select * from t;

Materialized view created.

SQL> alter materialized view mv_t add constraint ck_n check (n > 0);

Materialized view altered.

SQL> insert into t values (-1);

1 row created.

SQL> commit;
commit
*
ERROR at line 1:
ORA-12008: error in materialized view refresh path
ORA-02290: check constraint (SYSTEM.CK_N) violated

alert log:

Mon Jun 18 09:10:19 2007
Following on-commit snapshots not refreshed :
SYSTEM.MV_T

On 6/15/07, Brady, Mark <Mark.Brady@xxxxxxxxxxxxxxxxx> wrote:





This is on Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64bit Production



From the Alert Log we see:





Fri Jun 15 10:49:03 2007

Following on-commit snapshots not refreshed :

DEALNET.BROWSER_MV_INFO

DEALNET.BROWSER_MV_STATUS

Fri Jun 15 10:49:41 2007

Following on-commit snapshots not refreshed :

DEALNET.BROWSER_MV_INFO

DEALNET.BROWSER_MV_STATUS

Fri Jun 15 11:52:56 2007

Following on-commit snapshots not refreshed :

DEALNET.BROWSER_MV_INFO

DEALNET.BROWSER_MV_STATUS





I've googled this and I find a lot of posts asking what causes this but not
a lot of posts for what causes this and how to prevent it. Can anyone point
me to a cause?



TIA,

Mark >>> This e-mail and any attachments are confidential, may contain
legal,
professional or other privileged information, and are intended solely for
the
addressee. If you are not the intended recipient, do not use the information
in this e-mail in any way, delete this e-mail and notify the sender. CEG-IP2




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


Other related posts: