Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 E-mail Us
 Oracle Articles
New Oracle Articles

 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog

 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Oracle Support

 SQL Tuning

 Oracle UNIX
 Oracle Linux
 Remote s
 Remote plans
 Application Server

 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S


 Consulting Staff
 Consulting Prices
 Help Wanted!


 Oracle Posters
 Oracle Books

 Oracle Scripts

Don Burleson Blog 







Table Replication Techniques

Oracle Tips by Burleson Consulting

The Data Warehouse Development Life Cycle

Distributed Oracle Data Warehouses

Table Replication Techniques

One of the easiest ways to improve warehouse availability is with data replication. In order to bypass many of the problems inherent with network communications, data is copied and stored in multiple Oracle databases. Mainly, warehouses replicate information to improve reliability and maximize query response times. As you may know, in a client/server environment, it is often difficult to get all of the data to all of the users who require the information. It is also difficult to balance processing requirements between light data users (e.g., online transaction processing systems) and heavy data users (e.g., data warehouse systems for marketing). Data replication is often a desirable choice when processing requirements demand that online systems get fast response times while intensive I/O analysis is performed concurrently against the same information.

Another benefit of table replication is that if there is a failure with one of the component databases, the replicated database information remains available. This type of data replication is commonly called data distribution. Data distribution is not always the same thing as a distributed database. With data distribution, information can be redundantly copied to another database, whereas in “true” distributed databases the information is not replicated even though the data may reside in many databases. As mentioned earlier, some installations create master-slave replication, where a master database is used for updating multiple query, or slave, databases each day. The master-slave method usually has a "change" database that keeps track of all changes made to the master database. When the time comes to propagate the changes to the slave databases, a background task is triggered to copy the data, and the changed entries are then removed from the change database.

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.

Oracle Training at Sea
oracle dba poster

Follow us on Twitter 
Oracle performance tuning software 
Oracle Linux poster


Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  

and include the URL for the page.


Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


Copyright © 1996 -  2020

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.