Size of a Materialized log view odly big

Question

Hi people,
Im trying to figure out a curiousity in a database. There is a table of 150 MB (lets call it mytable) it has a Materialized view log on it which is 3000 MB. There is one Materialized view based on the table on a different site. It refreshes every 15 minutes. Its a fast refresh. To me it seems that the log should be smaller than the table itself. So I' ve tried shrinking it. I tried different things, but nothing seems to work. Some help would be really great.
these are the things i' ve tried:
BEGIN
DBMS_MVIEW.PURGE_LOG('mytable',1,'delete');
END;
ALTER TABLE mlog$_mytable ENABLE ROW MOVEMENT;
ALTER MATERIALIZED VIEW LOG ON mytable SHRINK SPACE;
ALTER TABLE mlog$_mytable ENABLE ROW MOVEMENT;
ALTER TABLE mlog$_mytable SHRINK SPACE;
any help is welcome

Answer 1

If you had orphaned log registrations, then you would use dbms_mview.purge_snapshot_from_log. If you don't have orphans, then I don't think it will help.
PROCEDURE PURGE_SNAPSHOT_FROM_LOG
Argument Name Type In/Out Default?
SNAPSHOT_ID BINARY_INTEGER IN
You could also check what is in the log, or if it is empty. E.g
select * from MLOG$_EMP;