Oracle8 Tuning Release 8.0 A58246-01 |
|
You can enhance Oracle performance by adjusting database applications, the database itself, and the operating system. Making such adjustments is known as tuning. Proper tuning of Oracle provides the best possible database performance for your specific application and hardware configuration.
Note: Oracle8 Tuning contains information that describes the features and functionality of the Oracle8 and the Oracle8 Enterprise Edition products. Oracle8 and Oracle8 Enterprise Edition have the same basic features. However, several advanced features are available only with the Enterprise Edition, and some of these are optional. For example, to use application failover, you must have the Enterprise Edition and the Parallel Server Option.
For information about the differences between Oracle8 and the Oracle8 Enterprise Edition and the features and options that are available to you, please refer to Getting to Know Oracle8 and the Oracle8 Enterprise Edition.
This manual is an aid for people responsible for the operation, maintenance, and performance of Oracle. To use this book, you could be a database administrator, application designer, or programmer. You should be familiar with Oracle8, the operating system, and application design before reading this manual.
This manual contains six parts:
This chapter provides an overview of tuning issues. It defines performance tuning and the roles of people involved in the process. |
|
This chapter presents the recommended tuning method, and outlines its steps in order of priority. |
|
Chapter 3: Diagnosing Performance Problems in an Existing System |
This chapter provides an overview of performance factors in existing systems that have been properly designed. |
This chapter introduces the full range of diagnostic tools available for monitoring production systems and determining performance problems. |
Chapter 5: Evaluating Your System's Performance Characteristics |
This chapter describes the various types of application that use Oracle databases and the suggested approaches and features available when designing each. |
This chapter introduces integrated Oracle8 features for tuning enterprise-scale data warehouses. |
This chapter explains how to use parallel execution features for improved performance. |
|
Chapter 20: Understanding Parallel Execution Performance Issues |
This chapter provides a conceptual explanation of parallel execution performance issues. |
Chapter 21: Diagnosing Parallel Execution Performance Problems |
This chapter explains how to diagnose and solve performance problems in parallel execution. |
This manual assumes you have already read Oracle8 Concepts, the Oracle8 Application Developer's Guide, and Oracle8 Administrator's Guide.
For more information about Oracle Enterprise Manager and its optional applications, please see the following publications:
Oracle Enterprise Manager Concepts Guide
Oracle Enterprise Manager Administrator's Guide
Oracle Enterprise Manager Application Developer's Guide
Oracle Enterprise Manager: Introducing Oracle Expert
Oracle Enterprise Manager: Oracle Expert User's Guide
Oracle Enterprise Manager Performance Monitoring User's Guide. This manual describes how to use Oracle TopSessions, Oracle Monitor, and Oracle Tablespace Manager.
This section explains the conventions used in this manual including the following:
This section explains the conventions used within the text:
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 words within text are book titles or emphasized words.
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:
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.
We value and appreciate your comments as an Oracle user and reader of the manuals. As we write, revise, and evaluate our documentation, your opinions are the most important input we receive. Please use the reader's comment form to tell us what you like and dislike about this manual or other Oracle manuals. If the form is not available, please use the following address: