Oracle8i Parallel Server Concepts and Administration
Release 8.1.5






Prev Next


This manual describes the Oracle Parallel Server (OPS) and supplements the Oracle8i Administrator's Guide and Oracle8i Concepts.

This manual prepares you to successfully implement parallel processing by providing a thorough presentation of the concepts and procedures involved. Information in this manual applies to OPS as it runs on all operating systems.


Oracle8i Parallel Server Concepts and Administration contains information that describes the features and functionality of the Oracle8i and the Oracle8i Enterprise Edition products. Oracle8i and the Oracle8i Enterprise Edition have the same basic features. However, several advanced features are available only with the Oracle8i Enterprise Edition, and some of these are optional. For example, to use client application failover, you must have the Enterprise Edition and the Parallel Server Option.  

For information about the differences between Oracle8i and the Oracle8i Enterprise Edition and the available features and options, please refer to Getting to Know Oracle8i.

Intended Audience

This manual is written for database administrators and application developers who work with Oracle Parallel Server.


Part I: Parallel Processing Fundamentals

Chapter 1, "Parallel Processing and Parallel Databases"  

This chapter introduces parallel processing and parallel database technologies that offer great advantages for online transaction processing and decision support applications.  

Chapter 2, "Implementing Parallel Processing"  

This chapter explains how to attain the goals of speedup and scaleup by effectively implementing parallel processing and parallel database technology.  

Chapter 3, "Parallel Hardware Architecture"  

This chapter describes the range of available hardware implementations that allow parallel processing, and surveys their advantages and disadvantages.  

Part II: Oracle Parallel Server Concepts

Chapter 4, "How Oracle Implements Parallel Processing"  

This chapter gives a high-level view of how OPS provides high performance parallel processing.  

Chapter 5, "Oracle Instance Architecture for Oracle Parallel Server"  

This chapter explains features of Oracle multiple instance architecture that differ from an Oracle server in exclusive mode.  

Chapter 6, "Oracle Database Architecture for the Parallel Server"  

This chapter describes features of Oracle database architecture that pertain to the multiple instances of OPS.  

Chapter 7, "Overview of Locking Mechanisms"  

This chapter provides an overview of internal OPS locking mechanisms.  

Chapter 8, "Integrated Distributed Lock Manager"  

This chapter explains the role of the Integrated Distributed Lock Manager in controlling access to resources in OPS.  

Chapter 9, "Parallel Cache Management Instance Locks"  

This chapter provides a conceptual overview of PCM locks. The planning and allocation of PCM locks is one of the most complex tasks facing the Oracle Parallel Server database administrator.  

Chapter 10, "Non-PCM Instance Locks"  

This chapter describes some of the most common non-PCM instance locks.  

Chapter 11, "Space Management and Free List Groups"  

This chapter explains space management concepts.  

Chapter 12, "Application Analysis"  

This chapter provides a conceptual framework for optimizing OPS application design.  

Part III: OPS System Development Procedures

Chapter 13, "Designing Databases for Parallel Server"  

This chapter prescribes a general methodology for designing systems optimized for OPS.  

Chapter 14, "Creating a Database and Objects for Multiple Instances"  

This chapter describes aspects of database creation that are specific to OPS.  

Chapter 15, "Allocating PCM Instance Locks"  

This chapter explains how to allocate PCM locks to datafiles by specifying values for parameters in the initialization file of an instance.  

Chapter 16, "Ensuring IDLM Capacity for Resources and Locks"  

This chapter explains how to reduce contention for shared resources and gain maximum performance from OPS by ensuring that adequate space is available in the Integrated Distributed Lock Manager for all the necessary locks and resources.  

Chapter 17, "Using Free List Groups to Partition Data"  

This chapter explains how to allocate free lists and free list groups to partition data. By doing this you can minimize contention for free space when using multiple instances.  

Part IV: OPS System Maintenance Procedures

Chapter 18, "Administering Multiple Instances"  

This chapter describes how to administer instances of OPS.  

Chapter 19, "Tuning to Optimize Performance"  

This chapter provides an overview of tuning issues.  

Chapter 20, "Cache Fusion and Inter-instance Performance"  

This chapter describes Cache Fusion in detail and explains how to monitor Cache Fusion and inter-instance performance.  

Chapter 21, "Backing Up the Database"  

This chapter explains how to protect your data by archiving the online redo log files and periodically backing up the datafiles, the control file for your database, and the parameter files for your instances.  

Chapter 22, "Recovering the Database"  

This chapter describes Oracle recovery features on a parallel server.  

Chapter 23, "Migrating from a Single Instance to Parallel Server"  

This chapter describes database conversion from a single instance Oracle database to a multi-instance Oracle database using the parallel server option.  

Part V: Reference

Appendix A, "Differences Among Versions"  

This appendix describes the differences between this release and previous releases of the Oracle that pertain to OPS.  

Appendix B, "Restrictions"  

This appendix lists restrictions for OPS.  

Related Documents

Before reading this manual, you should have already read Oracle8i Concepts and the Oracle8i Administrator's Guide.


This section explains the conventions used in this manual including the following:


This section explains the conventions used within the text:

UPPERCASE Characters

Uppercase text is used to call attention to command keywords, object names, parameters, filenames, and so on.

For example, "If you create a private rollback segment, the name must be included in the ROLLBACK_SEGMENTS parameter of the parameter file."

Italicized Characters

Italicized words within text are book titles or emphasized words.

Syntax Diagrams and Notation

The syntax diagrams and notation in this manual show the syntax for SQL commands, functions, hints, and other elements. This section tells you how to read syntax diagrams and examples and write SQL statements based on them.


Keywords are words that have special meanings in the SQL language. In the syntax diagrams in this manual, keywords appear in uppercase. You must use keywords in your SQL statements exactly as they appear in the syntax diagram, except that they can be either uppercase or lowercase. For example, you must use the CREATE keyword to begin your CREATE TABLE statements just as it appears in the CREATE TABLE syntax diagram.


Parameters act as place holders in syntax diagrams. They appear in lowercase. Parameters are usually names of database objects, Oracle datatype names, or expressions. When you see a parameter in a syntax diagram, substitute an object or expression of the appropriate type in your SQL statement. For example, to write a CREATE TABLE statement, use the name of the table you want to create, such as EMP, in place of the table parameter in the syntax diagram. (Note that parameter names appear in italics in the text.)

This list shows parameters that appear in the syntax diagrams in this manual and examples of the values you might substitute for them in your statements:

Parameter   Description   Examples  


The substitution value must be the name of an object of the type specified by the parameter.  



The substitution value must be a character literal in single quotes.  

'Employee Records'  


The substitution value must be a condition that evaluates to TRUE or FALSE.  

ename > 'A'  



The substitution value must be a date constant or an expression of DATE datatype.  





The substitution value can be an expression of any datatype.  

sal + 1000  


The substitution value must be an integer.  



The substitution value must be an expression of datatype ROWID.  



The substitution value must be a SELECT statement contained in another SQL statement.  

SELECT ename

FROM emp  



The substitution value must be an identifier for a SQL statement or PL/SQL block.  



Code Examples

SQL and SQL*Plus commands and statements appear separated from the text of paragraphs in a monospaced font. For example:

   INSERT INTO emp (empno, ename) VALUES (1000, 'SMITH'); 
   ALTER TABLESPACE users ADD DATAFILE 'users2.ora' SIZE 50K; 

Example statements may include punctuation, such as commas or quotation marks. All punctuation in example statements is required. All example statements terminate with a semicolon (;). Depending on the application, a semicolon or other terminator may or may not be required to end a statement.

Uppercase words in example statements indicate the keywords within Oracle SQL. When you issue statements, however, keywords are not case sensitive.

Lowercase words in example statements indicate words supplied only for the context of the example. For example, lowercase words may indicate the name of a table, column, or file.


Copyright © 1999 Oracle Corporation.

All Rights Reserved.