...
- Create manual refresh MViews representing the source Banner tables, henceforth referred to as the Banner Replicant MViews.
- Re-create indexes from Banner source tables to the Banner Replicant MViews.
- Create Materialized View Logs on the Banner Replicant MViews.
- The 10g documentation seems to prefer using rowid-based view logs and view creations for join MViews. We will be trying this method first.
- Create and test new Course Management MViews based on the Banner Replicant MViews and Logs.
- Testing will be performed via the DBMS_SNAPSHOT.Explain_MView procedure. This procedure analyzes an MView definition much like explain_plan does for a query, but provides important information on refresh status. We would have preferred to use DBMS_ADVISOR.Tune_Mview, but do not have a license for it.
Design Issues
- In According to the Oracle 10G , theredocumentation, the mviews we are creating are "simple join mviews" and should be eligible for fast refresh. I will be reformulating the mview and view definitions to use rowid based logs and mviews with rowid columns based on information from this page: http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14223/basicmv.htm#i1006803
Progress
- Banner Replicant MViews created with re-created Banner indexes.