Home » Server Options » Replication » Materialized view not refresh
Materialized view not refresh [message #127690] Tue, 12 July 2005 21:22 Go to next message
nhom9a
Messages: 51
Registered: July 2005
Location: VN
Member
hi all.
I have a materialized view .it will run very good if i don't create a trigger. I know why trigger don't refresh because this trigger use to insert data from one table to another table and have some records don't suit criteria. But I think I have some records suit too. Why my trigger not refresh and why no records can insert to another table althought suit criterial.
Can anybody help me ?
Thanks.
  • Attachment: err.bmp
    (Size: 667.70KB, Downloaded 346 times)

[Updated on: Tue, 12 July 2005 23:39]

Report message to a moderator

Re: Materialized view not refresh [message #127796 is a reply to message #127690] Wed, 13 July 2005 07:30 Go to previous message
Frank Naude
Messages: 4420
Registered: April 1998
Senior Member
Hi,

Looks like your refresh is causing the trigger to fire, but the trigger doesn't work. You will have to fix the trigger.

$ oerr ora 12008
12008, 00000, "error in materialized view refresh path"
// *Cause:  Table SNAP$_<mview_name> reads rows from the view
//          MVIEW$_<mview_name>, which is a view on the master table
//          (the master may be at a remote site).  Any
//          error in this path will cause this error at refresh time.
//          For fast refreshes, the table <master_owner>.MLOG$_<master>
//          is also referenced.
// *Action: Examine the other messages on the stack to find the problem.
//          See if the objects SNAP$_<mview_name>, MVIEW$_<mview_name>,
//          <mowner>.<master>@<dblink>, <mowner>.MLOG$_<master>@<dblink>
//          still exist.
$ oerr ora 1422
01422, 00000, "exact fetch returns more than requested number of rows"
// *Cause: The number specified in exact fetch is less than the rows returned.
// *Action: Rewrite the query or change number of rows requested


Best regards.

Frank
Previous Topic: Data replication
Next Topic: Put a hold on dbms_jobs/replication during master backup
Goto Forum:
  


Current Time: Thu Dec 18 06:46:48 CST 2014

Total time taken to generate the page: 0.21467 seconds