The Information Source model for IFS Business Intelligence Services describes a Star Schema model consisting of Facts (transactions) and Dimensions (basic data). If an Information Source is supposed to support a Data Mart solution, then the necessary storage containers, representing the Facts and the Dimensions, have to created in the Data Mart.
More details about Materialized Views...
Note: The refresh functionality mentioned here only handles the refreshing of Materialized Views referred by Information Sources available in IFS Business Intelligence Services.
An overview of Business Intelligence related Materialized Views can be found in the feature BI Materialized Views in Solution Manager in IEE.
Figure 1:Overview of BI Materialized Views
Note: A Materialized View definition that contains non-deterministic function calls
will lead to the Materialized View in the database, marked as having the
staleness UNKNOWN. The reason is that, it is not possible to trace changes
from functions. A Materialized View with staleness UNKNOWN will by
default be treated as FRESH, i.e. it will be marked with a green indicator. This means that Materialized Views with staleness UNKNOWN
will not be refreshed, neither if ordered manually nor if being part of a
scheduled refresh job. As soon as the main source tables referenced by the
Materialized View are modified, the Materialized View will be marked as not
up-to-date, i.e. with a yellow indicator.
If however it is required to treat a Materialized View with staleness
UNKNOWN
as not up-to-date, i.e. marked with a yellow indicator, this is possible
by modifying the BI Services parameter
REFRESH_UNKNOWN_MV.
Use the feature to:
A Materialized View will have one of the following refresh modes:
Select this mode to refresh a Materialized View on demand. A change made to the relative data in the reference tables are kept on hold and will affect the Materialized View when a refresh is ordered.
This is the default mode recommended for most purposes. Preserving a snapshot state means that IFS Business Intelligence Services can be used to analyze data that is consistent.
Select this mode to refresh a Materialized View on
commit. This is performed instantly when a change is made in the reference
table on commit.
Setting the mode to COMMIT will affect
the performance on general commit used on the tables having a Materialized View Log defined.
It also takes away the possibility to keep the information in a static state,
it is beneficiary when analyzing the available information.
By default, all Materialized Views are defined with the refresh mode DEMAND. This means that the Materialized Views will not be updated automatically when new data is entered into the system. It is possible but, not recommended to modify the refresh mode from DEMAND to COMMIT.
The Refresh Mode can be changed in the Context Menu via Change Refresh Mode To in BI Materialized View window. Refer Figure 2:BI Materialized Views.
Figure 2: BI Materialized Views
A Materialized View will have one of the following refresh methods.
This means that Oracle can handle incremental update of the Materialized View.
This means that the Materialized View has to be recreated from scratch. Can be used for complex Materialized View definitions. This is the recommended refresh mode.
Note: It is recommended to create Materialized Views with the refresh method COMPLETE and refresh mode DEMAND.
Read more about special subjects related to administration of Materialized Views here.