Oracle® Database High Availability Architecture and Best Practices 10g Release 1 (10.1) Part Number B10726-02 |
|
|
View PDF |
This book is a database high availability reference. It describes Oracle database architectures and features as well as recommended practices that can help your business achieve high availability. It provides guidelines for choosing the appropriate high availability solution.
This preface contains these topics:
This book is intended for chief technology officers, information technology architects, database administrators, system administrators, network administrators, and application administrators who perform the following tasks:
Plan data centers
Implement data center policies
Maintain high availability systems
Plan and build high availability solutions
Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. 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/
Accessibility of Code Examples in Documentation
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.
Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.
This document contains:
This part provides an overview of high availability (HA) and describes the Oracle features that can be used to achieve high availability.
Chapter 1, "Overview of High Availability"
This chapter defines high availability and the need for HA architecture and practices. It describes in general terms what is necessary to achieve high availability. It gives examples of outages and their impact on businesses. It also explains the scope of the book and how to use the book.
Chapter 2, "Determining Your High Availability Requirements"
This chapter describes service level agreements and business requirements. It provides guidelines for determining whether data loss is acceptable and discusses the performance and manageability impact of HA practices.
Part II, "Oracle Database High Availability Features, Architectures, and Policies"
This part explains what business requirements influence the decision to implement a high availability solution. After the essential factors have been identified, defined, and described, the factors are used to provide guidance about choosing a high availability architecture.
Chapter 3, "Oracle Database High Availability Features"
This chapter provides high-level descriptions of Oracle HA features.
Chapter 4, "High Availability Architectures"
This chapter describes validated HA architectures.
Chapter 5, "Operational Policies for High Availability"
This chapter describes operational best practices for HA.
Part III, "Configuring a Highly Available Oracle Environment"
This part describes how to configure the high availability architectures.
Chapter 6, "System and Network Configuration"
This chapter provides recommendations for configuring the subcomponents that make up the database server tier and the network.
Chapter 7, "Oracle Configuration Best Practices"
This chapter recommends Oracle configuration and best practices for the database, Oracle Real Application Clusters, Oracle Data Guard, Maximum Availability Architecture, backup and recovery, and fast application failover.
Part IV, "Managing a Highly Available Oracle Environment"
This part describes how to manage an HA Oracle environment.
Chapter 8, "Using Oracle Enterprise Manager for Monitoring and Detection"
This chapter describes how to monitor and detect system availability. It emphasizes Oracle Enterprise Manager.
Chapter 9, "Recovering from Outages"
This chapter contains a decision matrix for determining what actions to take for specific outages.
Chapter 10, "Detailed Recovery Steps"
This chapter contains detailed steps for recovering from the outages described in Chapter 9, "Recovering from Outages".
Chapter 11, "Restoring Fault Tolerance"
This chapter describes the following types of repair: restoring failed nodes in a Real Application Cluster, restoring the standby database after a failover, restoring fault tolerance after secondary site or clusterwide scheduled outage, restoring fault tolerance after a standby database data failure, restoring fault tolerance after the production database is activated, and restoring fault tolerance after dual failures.
Appendix A, "Hardware Assisted Resilient Data (HARD) Initiative"
This appendix contains information about the Hardware Assisted Resilient Data (HARD) initiative.
Appendix B, "Database SPFILE and Oracle Net Configuration File Samples"
This appendix contains database SPFILE
and Oracle Net configuration file samples.
For more information, see the Oracle database documentation set. These books may be of particular interest:
Oracle Real Application Clusters Deployment and Performance Guide
Oracle Application Server 10g High Availability Guide
Many books in the documentation set use the sample schemas of the seed database, which is installed by default when you install Oracle. Refer to Oracle Database Sample Schemas for information on how these schemas were created and how you can use them yourself.
Printed documentation is available for sale in the Oracle Store at
http://oraclestore.oracle.com/
To download free release notes, installation documentation, white papers, or other collateral, please visit the Oracle Technology Network (OTN). You must register online before using OTN; registration is free and can be done at
http://otn.oracle.com/membership/index.html
If you already have a username and password for OTN, then you can go directly to the documentation section of the OTN Web site at
http://otn.oracle.com/documentation/index.html
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. | Oracle 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 Query the Use the |
lowercase monospace (fixed-width) font |
Lowercase monospace typeface indicates executable programs, filenames, directory names, and sample user-supplied elements. Such elements include computer and database names, net service names and connect identifiers, 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 start SQL*Plus.
The password is specified in the Back up the datafiles and control files in the The Set the Connect as The |
lowercase italic monospace (fixed-width) font |
Lowercase italic monospace font represents placeholders or variables. | You can specify the parallel_clause .
Run |
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 |
---|---|---|
[ ] |
Anything enclosed in brackets is optional. |
DECIMAL (digits [ , precision ]) |
{ } |
Braces are used for grouping items. |
{ENABLE | DISABLE} |
| |
A vertical bar represents a choice of two options. |
{ENABLE | DISABLE} [COMPRESS | NOCOMPRESS] |
... |
Ellipsis points mean repetition in syntax descriptions.
In addition, ellipsis points can mean an omission in code examples or text. |
CREATE TABLE ... AS subquery; SELECT col1, col2, ... , coln FROM employees; |
Other symbols | You must use symbols other than brackets ([ ]), braces ({ }), vertical bars (|), and ellipsis points (...) exactly 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. Because these terms are not case sensitive, you can use them in either UPPERCASE or lowercase. |
SELECT last_name, employee_id FROM employees; SELECT * FROM USER_TABLES; DROP TABLE hr.employees; |
lowercase |
Lowercase typeface indicates user-defined programmatic elements, such as 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; |
Conventions for Windows Operating Systems
The following table describes conventions for Windows operating systems and provides examples of their use.
Convention | Meaning | Example |
---|---|---|
Choose Start > menu item | How to start a program. | To start the Database Configuration Assistant, choose Start > Programs > Oracle - HOME_NAME > Configuration and Migration Tools > Database Configuration Assistant. |
File and directory names | File and directory names are not case sensitive. The following special characters are not allowed: left angle bracket (<), right angle bracket (>), colon (:), double quotation marks ("), slash (/), pipe (|), and dash (-). The special character backslash (\) is treated as an element separator, even when it appears in quotes. If the filename begins with \\, then Windows assumes it uses the Universal Naming Convention. | c:\winnt"\"system32 is the same as C:\WINNT\SYSTEM32 |
C:\> |
Represents the Windows command prompt of the current hard disk drive. The escape character in a command prompt is the caret (^). Your prompt reflects the subdirectory in which you are working. Referred to as the command prompt in this manual. |
C:\oracle\oradata> |
Special characters | The backslash (\) special character is sometimes required as an escape character for the double quotation mark (") special character at the Windows command prompt. Parentheses and the single quotation mark (') do not require an escape character. Refer to your Windows operating system documentation for more information on escape and special characters. |
C:\>exp HR/HR TABLES=employees QUERY=\"WHERE job_id='SA_REP' and salary<8000\" |
HOME_NAME |
Represents the Oracle home name. The home name can be up to 16 alphanumeric characters. The only special character allowed in the home name is the underscore. |
C:\> net start OracleHOME_NAMETNSListener |
ORACLE_HOME and ORACLE_BASE |
In releases prior to Oracle8i release 8.1.3, when you installed Oracle components, all subdirectories were located under a top level ORACLE_HOME directory. The default for Windows NT was C:\orant .
This release complies with Optimal Flexible Architecture (OFA) guidelines. All subdirectories are not under a top level All directory path examples in this guide follow OFA conventions. Refer to Oracle Database Installation Guide for Windows for additional information about OFA compliances and for information about installing Oracle products in non-OFA compliant directories. |
Go to the ORACLE_BASE \ ORACLE_HOME \rdbms\admin directory. |