Datawarehouse loadings are periodic, and summary tables are useful to improve efficiency and the answer time of our reports. A physical optimisation resource that can bring big improvements in our system is the utilization of materialized views.
The view materialized is not more that a view, defined with one sentences SQL, of which in addition to storing his definition, store the data that returns, realizing an initial load and afterwards each true time a freshen of the same.
Like this, if we have a Datawarehouse that update daily, could use views materialized to go updating intermediate tables that feed our diagrams of DWH, or directly to implement tables agregadas that will freshen from our tables base.
The creation of this type of views no so complex as it can seem, the most important is to have clear each how much time want to update the information of the views, and which method of freshen to use.
Also will have to ensure us that our licence of base of data allows us use them (has to be a version Enterprise).
In order to be able to make all the steps you must initiate the session in the database with a user with administration permissions, you can use the SYSTEM user, for example
These tablespaces are the location where Oracle will save the objects of the scheme which we are going to create.
Tablespace for data, with initial size of 1024 Mb, and autoextensive
CREATE TABLESPACE "APPDAT" LOGGING DATAFILE '/export/home/oracle/oradata/datafiles/APPDAT.dbf' SIZE 1024M EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO
CREATE TABLESPACE "APPIDX" LOGGING DATAFILE '/export/home/oracle/oradata/datafiles/APPIDX.dbf' SIZE 512M EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO
CREATE USER “APP” PROFILE “DEFAULT” IDENTIFIED BY “APPPWD”
DEFAULT TABLESPACE “APPDAT” TEMPORARY TABLESPACE “TEMP” ACCOUNT UNLOCK;
If you want to access the Oracle 9i online documentation you can do it following the link
Is the original Oracle Help installed in a public access site.