Oracle数据仓库要点解析.ppt

* * The restrictions prior to Oracle9i were to guarantee the same operating system, the same database version and same blocksize. In current data warehouse environments, transportable tablespaces are mainly used to transport data from a central data warehouse to a dependent data mart or from an Operational Data Store (ODS) to a data warehouse. Leveraging transportable tablespaces as a transport mechanism between an OLTP source system and the data warehouse failed very often due to the restriction on database blocksize. Beginning with Oracle9i, the restriction of having the same blocksize for transportable tablespaces is removed. * * * Reports Developer ships with iDS Oracle9iAS Reports The Reports Multi-tiered Server allows you to run reports on a remote application server. It handles client requests by entering all requests into a job queue and when one server抯 report runtime engine becomes available, the next report is dispatched to run. As the number of the jobs in the queue increases, the reports server can spawn more engines until it reaches the maximum that you have defined. All idle engines are shut down after a specified period of time. So, the user requests a report to run from their browser, the web listener runs the Reports Server CGI or servlet which then spawns an engine, the report definition file is accessed, a connection to the database is made via sql*net to run the query and the final result is displayed back to the user. In this environment, all report definition files are placed on this middle tier server. So, there is no need to deploy any software to your end users, all they need is a browser. Which ultimately reduces the cost of maintenance, deployment and total cost of ownership. Reports that have been generated to the cache remain accessible to users who try to run the same report at a later point in time. This improves performance in addition to ensuring less load on the report server. You can also have a clustered configuration