Solution : https://service.sap.com/sap/support/notes/741478 (SAP Service marketplace login required)
Summary :
Materialized views in SAP are database objects that store the result of a query physically; they can be refreshed based on changes in the underlying data. They are distinct from standard views, which dynamically retrieve data at runtime, as materialized views store a snapshot of data, reducing runtime query costs and complexity. SAP does not generally utilize materialized views except during specific table reorganization procedures using DBMS_REDEFINITION. Materialized views require proper primary key constraints or must be based on ROWID. Creation and refresh options include fast, complete, and force methods, controlled by DBMS scheduler jobs and Oracle scripts with the creation command syntax `CREATE MATERIALIZED VIEW`. Auxiliary Oracle Data Dictionary views and indexes may be created to support materialized views operationally. Potential pitfalls include space issues in default tablespaces during online reoperations using materialized views.
Key words :
architectureoracle9i sql reference-> create materialized view refer, oracle9i advanced replication-> 3 materialized view concepts, alter table <table> add primary_key, create large i_snap$ indexes implicitly, create materialized view my_mat_view<refresh_mode>, increased redo log count, significant redo log count, avoid reorganizing large tables, 30 minutes equals 1 day multiplied, create materialized view authorization
Related Notes :
| 646681 | Reorganization of tables with BRSPACE |
| 584548 | Unusually high number of redo logs |
| 541538 | FAQ: Reorganization |
| 105047 | Support for Oracle functions in the SAP environment |