01.09.2016 Views

Beginning Oracle Database 11g Administration From Novice to Professional

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

CHAPTER 3 ORACLE ARCHITECTURE 53<br />

<strong>Database</strong> vs. Instance<br />

In <strong>Oracle</strong> terminology, the word database is used <strong>to</strong> collectively indicate the data files and<br />

supporting files on the s<strong>to</strong>rage disks attached <strong>to</strong> the host computer, and the word instance<br />

is used <strong>to</strong> describe the various computer processes resident in computer memory and<br />

memory areas shared by these processes. This is in contrast <strong>to</strong> database architectures such<br />

as Microsoft SQL Server and IBM DB2, for which the word instance indicates a collection<br />

of databases that share common memory resources—that is, the relationship between<br />

instances and databases is one-<strong>to</strong>-many. The relationship between <strong>Oracle</strong> instances and<br />

databases, on the other hand, is either one-<strong>to</strong>-one (one instance per database) or many<strong>to</strong>-one<br />

(multiple instances per database). The many-<strong>to</strong>-one configuration is called Real<br />

Application Clusters (RAC)—the database lives on shared disks, and instances on multiple<br />

computers attach <strong>to</strong> the database.<br />

In Figure 3-1, the database is represented by the panel on the far right labeled Disk<br />

S<strong>to</strong>rage. The three blocks in the middle—labeled Server Processes, SGA, and Background<br />

Processes—represent the instance.<br />

<strong>Database</strong><br />

The most concrete aspect of a database is the files on the s<strong>to</strong>rage disks connected <strong>to</strong> the<br />

database host. In this section, I briefly discuss each category of file. Placement, sizing, and<br />

other configuration details are discussed in Chapters 5 and 6.<br />

Software<br />

The location of the database software is called the <strong>Oracle</strong> home and is usually s<strong>to</strong>red in<br />

the environment variable . There are two species of database software: server<br />

software and client software. Server software is necessary <strong>to</strong> create and manage the database<br />

and is required only on the database host. Client software is necessary <strong>to</strong> utilize the<br />

database and is required on every user’s computer—the most common example is the<br />

SQL*Plus command-line <strong>to</strong>ol.<br />

Configuration Files<br />

The most important database configuration file is the one containing the settings used<br />

during database startup. It comes in two versions: a text version called a pfile and a binary<br />

version called an spfile. You will see an example in Chapter 6. The pfile and spfile specify<br />

such details as the amount of computer memory that <strong>Oracle</strong> may use during operation.<br />

The pfile is traditionally referred <strong>to</strong> as the file.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!