Do you have any JOB_QUEUE_PROCESSES defined in your instance (in the
INIT.ORA file)? These processes are responsible for doing the refreshing of
snapshots/materialized views.
Andrew Schneider <aschneider_at_powervision.com> wrote in message
news:lajS3.143$vl4.626_at_client...
> I have an OLTP/Data Warehousing Manufacturing application that uses
> Materialized Views as rollup entities. I am using FAST refresh via a
> Materialized View Log on the Master operational table. When I add records
> to the master table and commit them, they only propagate to the
Materialized
> View Log and not the Materialized View itself. I tried using DBMS_MVIEW
to
> manually refresh the Materialized View to no avail. What action do I need
> to take for enabling DML propagation from the Materialized View Log to the
> Materialized View? Below is the DDL for the Materialized View data
> structures:
>
> CREATE MATERIALIZED VIEW LOG
> ON tbl_signal
> TABLESPACE tbs_signal_mvw_log
> PCTFREE 10
> PCTUSED 60
> INITRANS 4
> MAXTRANS 255
> STORAGE
> (
> INITIAL 1M
> NEXT 1M
> MINEXTENTS 5
> MAXEXTENTS 120
> PCTINCREASE 0
> )
> PARALLEL
> WITH PRIMARY KEY
> /
>
>
> CREATE MATERIALIZED VIEW mvw_signal
> TABLESPACE tbs_signal_mvw
> PCTFREE 10
> PCTUSED 60
> INITRANS 4
> MAXTRANS 255
> STORAGE
> (
> INITIAL 1M
> NEXT 1M
> MINEXTENTS 20
> MAXEXTENTS 120
> PCTINCREASE 0
> )
> PARALLEL
> BUILD IMMEDIATE
> REFRESH FAST
> AS
> SELECT row_id,
> reel_id,
> frame_id,
> acq_date,
> capacitance
> FROM tbl_signal
> /
>
>
>
>
>
Received on Fri Oct 29 1999 - 14:10:53 CDT
