Distributed Oracle Data Network Independence Oracle Tips by Burleson Consulting

The Data Warehouse Development Life Cycle

Distributed Oracle Data Warehouses

Hardware Independence

Hardware independence refers to the ability to query and update information regardless of the hardware platform on which the data resides. For example, a single query initiated on a PC might retrieve information from an IMS on a mainframe, a Lotus database on a PC, and an Oracle database on a midrange host.

Operating System Independence

In a truly distributed database, a query should not be dependent on any operating system. For example, a distributed database should have no problem allowing PC-based queries to be entered from either MS-DOS or OS/2 systems, and users should be able to access databases residing on MVS/ESA, Unix, or any other operating system.

Network Independence

Network protocols should not be an issue for distributed databases, and Oracle has included a multiple community feature as part of SQL*Net to address different protocols. Oracle allows LU6.2 nodes to coexist with TCP/IP protocols, and automatic conversion routines allow synchronous channels (such as those on IBM mainframes) to communicate in the asynchronous world of Unix.

Database Independence

Database independence refers to the ability to retrieve and update information from many different database architectures. Oracle implements this feature via its gateway products that allow communication with legacy databases.

---

This is an excerpt from "High Performance Data Warehousing", copyright 1997.

If you like Oracle tuning, you may enjoy the book Oracle Tuning: The Definitive Reference , with over 900 pages of BC's favorite tuning tips & scripts.  You can buy it directly from the publisher and save 30%, and get instant access to the code depot of Oracle tuning scripts.