Sorry but this is not the problem as all the mviews are working and accounted for On 1/17/07, Hemant K Chitale <hkchital@xxxxxxxxxxxxxx> wrote:
And also if you have an MV that had registered to do Fast Refresh's but is no longer refreshing itself (eg the DBMS_MVIEW.REFRESH job for the MV has been dropped because users "no longer need the MV") At 11:09 PM Tuesday, Yavor Ivanov wrote: > I think you problem is deeper. > The described behaviour sounds like you have more mvews > registered in the log, than you have realy refreshing. This may > happen if you drop a database and it does not unregister it's > mviews form the master; or if you drop some mview and the > connection with the master is not working in that exact moment, so > the mview does not unregister itself. You can check what registered > mviews you have anf when they are refreshed using the folowing > query on the master site: Hemant K Chitale http://web.singnet.com.sg/~hkchital and http://hemantoracledba.blogspot.com
-- Vincent Verpoort ,.-~`"'~-.,_,.-~`"'~-.,_,.-~`"'~-.,_,.-~`"'~-.,_,.-~`"'~-.,_ Communiceren is begrepen worden ^*<-._,.->*^*<-._,.->*^*<-._,.->*^*<-._,.->*^*<-._,.->*^*<-.