Preface

Oracle9i Real Application Clusters Deployment and Performance explains the deployment issues for applications that use an Oracle9i Real Application Clusters database. This manual also provides post-deployment information about tuning Real Application Clusters environments for optimal performance.

Information in this manual applies to Real Application Clusters as it runs on all operating systems. Where necessary, this manual refers to platform-specific documentation.

See Also:

The Oracle9i Real Application Clusters Documentation Online Roadmap to help you use the online Oracle9i Real Application Clusters Documentation set

This preface contains these topics:

Audience

Oracle9i Real Application Clusters Deployment and Performance is written for database administrators and application developers working with Real Application Clusters. To use this document you should have a conceptual understanding of Real Application Clusters processing and its software and hardware components as described in Oracle9i Real Application Clusters Concepts and you should have installed Real Application Clusters using the document Oracle9i Real Application Clusters Installation and Configuration and related platform-specific documentation.

Organization

The five parts of this book and their contents are:

Part I: Introduction to Real Application Clusters Deployment

Part One introduces the high-level aspects of deploying applications in Real Application Cluster by describing how to take advantage of Oracle9i features. It also describes deployment of internet-based applications in e-commerce and data warehousing environments.

Chapter 1, "Introduction to Application Deployment for Real Application Clusters"

This chapter provides an overview of deployment issues for Real Application Clusters environments.

Chapter 2, "Online E-Commerce and Data Warehousing Application Deployment in Real Application Clusters"

This chapter briefly describes the deployment of online e-commerce-based and data warehousing applications for Real Application Clusters.

Part II: Scaling and Designing Applications for Oracle9i Real Application Clusters

Part Two describes technical issues and database design techniques for deploying scalable applications with Real Application Clusters.

Chapter 3, "Scaling Applications for Real Application Clusters"

This chapter describes how to optimize the scalability of your applications for deployment in Real Application Clusters environments.

Chapter 4, "Database Design Techniques for Real Application Clusters"

This chapter describes Real Application Clusters database design issues such as block and extent operations, contention reduction, and resource control strategies.

Part III: Oracle9i Real Application Clusters Performance Monitoring and Tuning

Part Three describes procedures for monitoring and tuning performance in Real Application Clusters.

Chapter 5, "General Tuning Recommendations for Real Application Clusters"

This chapter presents general tuning recommendations for Real Application Clusters.

Chapter 6, "Tuning Real Application Clusters and Inter-Instance Performance"

This chapter describes how to monitor and tune inter-instance performance in Real Application Clusters.

Part IV: Monitoring and Tuning Real Application Clusters Databases with Oracle Enterprise Manager

Part Four describes monitoring the performance of Real Application Clusters databases using Oracle Enterprise Manager.

Chapter 7, "Monitoring Performance with Oracle Performance Manager"

This chapter explains how monitor and tune Real Application Clusters databases with Oracle Enterprise Manager.

Part V: Oracle Real Application Clusters Reference

Part Five contains reference information for Real Application Clusters deployment and performance.

Appendix A, "Configuring Pre-Release 1 (9.0.1) Multi-Block Lock Assignments (Optional)"

This appendix explains how to override the Real Applications default resource control mechanisms.

Appendix B, "A Case Study in Real Application Clusters Database Design"

This appendix describes a case study for deploying Real Application Clusters.

Glossary

The glossary defines terms used in this book as well as terms relevant to the subject matter of this book.

Conventions

This section describes the conventions used in the text and code examples of this documentation set. It describes:

Conventions in Text

We use various conventions in text to help you more quickly identify special terms. The following table describes those conventions and provides examples of their use.

Convention	Meaning	Example
Bold	Bold typeface indicates terms that are defined in the text or terms that appear in a glossary, or both.	When you specify this clause, you create an index-organized table.
Italics	Italic typeface indicates book titles or emphasis.	Oracle9i Database Concepts Ensure that the recovery catalog and target database do not reside on the same disk.
`UPPERCASE monospace (fixed-width font)`	Uppercase monospace typeface indicates elements supplied by the system. Such elements include parameters, privileges, datatypes, RMAN keywords, SQL keywords, SQL*Plus or utility commands, packages and methods, as well as system-supplied column names, database objects and structures, usernames, and roles.	You can specify this clause only for a `NUMBER` column. You can back up the database by using the `BACKUP` command. Query the `TABLE_NAME` column in the `USER_TABLES` data dictionary view. Use the `DBMS_STATS`.`GENERATE_STATS` procedure.
`lowercase monospace (fixed-width font)`	Lowercase monospace typeface indicates executables, filenames, directory names, and sample user-supplied elements. Such elements include computer and database names, net service names, and connect identifiers, as well as user-supplied database objects and structures, column names, packages and classes, usernames and roles, program units, and parameter values. Note: Some programmatic elements use a mixture of UPPERCASE and lowercase. Enter these elements as shown.	Enter `sqlplus` to open SQL*Plus. The password is specified in the `orapwd` file. Back up the datafiles and control files in the `/disk1/oracle/dbs` directory. The `department_id`, `department_name`, and `location_id` columns are in the `hr.departments` table. Set the `QUERY_REWRITE_ENABLED` initialization parameter to `true.` Connect as `oe` user. The `JRepUtil` class implements these methods.
`lowercase monospace (fixed-width font) italic`	Lowercase monospace italic font represents placeholders or variables.	You can specify the `parallel_clause`. Run `U``old_release``.SQL` where `old_release` refers to the release you installed prior to upgrading.

Conventions in Code Examples

Code examples illustrate SQL, PL/SQL, SQL*Plus, or other command-line statements. They are displayed in a monospace (fixed-width) font and separated from normal text as shown in this example:

SELECT username FROM dba_users WHERE username = 'MIGRATE';

The following table describes typographic conventions used in code examples and provides examples of their use.

Convention	Meaning	Example
[ ]	Brackets enclose one or more optional items. Do not enter the brackets.	`DECIMAL (``digits` `[ ,` `precision` `])`
{ }	Braces enclose two or more items, one of which is required. Do not enter the braces.	`{ENABLE \| DISABLE}`
\|	A vertical bar represents a choice of two or more options within brackets or braces. Enter one of the options. Do not enter the vertical bar.	`{ENABLE \| DISABLE}` `[COMPRESS \| NOCOMPRESS]`
`...`	Horizontal ellipsis points indicate either: That we have omitted parts of the code that are not directly related to the example That you can repeat a portion of the code	`CREATE TABLE ... AS` `subquery``;` `SELECT` `col1``,` `col2``, ... ,` `coln` `FROM employees;`
. . .	Vertical ellipsis points indicate that we have omitted several lines of code not directly related to the example.
Other notation	You must enter symbols other than brackets, braces, vertical bars, and ellipsis points as shown.	`acctbal NUMBER(11,2);` `acct CONSTANT NUMBER(4) := 3;`
`Italics`	Italicized text indicates placeholders or variables for which you must supply particular values.	`CONNECT SYSTEM/``system_password` `DB_NAME =` `database_name`
`UPPERCASE`	Uppercase typeface indicates elements supplied by the system. We show these terms in uppercase in order to distinguish them from terms you define. Unless terms appear in brackets, enter them in the order and with the spelling shown. However, because these terms are not case sensitive, you can enter them in lowercase.	`SELECT last_name, employee_id FROM employees;` `SELECT * FROM USER_TABLES;` `DROP TABLE hr.employees;`
`lowercase`	Lowercase typeface indicates programmatic elements that you supply. For example, lowercase indicates names of tables, columns, or files. Note: Some programmatic elements use a mixture of UPPERCASE and lowercase. Enter these elements as shown.	`SELECT last_name, employee_id FROM employees;` `sqlplus hr/hr` `CREATE USER mjones IDENTIFIED BY ty3MU9;`

Documentation Accessibility

Oracle's goal is to make our products, services, and supporting documentation accessible to the disabled community with good usability. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For additional information, visit the Oracle Accessibility Program Web site at:

http://www.oracle.com/accessibility/

JAWS, a Windows screen reader, may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, JAWS may not always read a line of text that consists solely of a bracket or brace.