Is the MV set up for FAST REFRESH or
COMPLETE?
If FAST REFRESH, check to see if the tablespace
of MV Log table, named MLOG$_<tablename> where <tablename> is the
first 20 characters of the table on which the log is based, has enough space
for the mlog$ to grow.
If complete refresh, do it manually from command
line
exec
DBMS_SNAPSHOT.REFRESH('<tablename>,'CF')
and see what error message is given. A few things
come to my mind
(1) not enough temp space for the sorting to
occur for he MV
(2) not enough rollback segment
space.
Either way, you will see the exact error it fails
on.
HTH.
Arup Nanda
----- Original Message -----
Sent: Friday, February 21, 2003 8:19
AM
Subject: Replication
I was asked of
a problem in a friend's site about replication.
The
problem.
They
implemented replication using Materialized Views with an refresh update of
ON DEMAND and some immediate. It works for some days and suddenly some
MV stop replicating.
He has checked
metalink, but can't open a TAR.
Is there any
recommendation that you can give him to check.
Ramon E.
Estevez
809-565-3121
