| |
 |
|
Donald K. Burleson
Oracle Tips |
Oracle Database
Distribution
* Failure at one node is less likely to affect other nodes. The
global system is at least partially available as long as a single
node of the database is active. No single failure will halt all
processing or be a performance bottleneck. For example, if the
Pittsburgh node goes down, it won’t affect the Omaha node, as long
as Omaha doesn’t require any of Pittsburgh’s data.
* Failure recovery is on a per-node
basis.
* A data dictionary exists for each local database.
* Nodes can upgrade software independently, within reason.
As DBA you will need to understand the structures and limits of the
distributed environment if you are required to maintain a
distributed environment. The features of a two-phase commit, as well
as naming resolution and the other distributed topics, will be
covered in Chapter 14. Figure 1.3 shows a distributed database
structure.
This is an
excerpt by Mike Ault’s book “Oracle
Administration & Management”. If you want more current Oracle tips
by Mike Ault, check out his new book “Mike
Ault’s Oracle Internals Monitoring & Tuning Scripts” or
Ault’s Oracle Scripts Download.
|
