Index

A B C D E F G H I L M N O P R S T U V W

A

advisor framework, 2.4.1

ALTER DATABASE RECOVER MANAGED STANDBY statement

enabling real-time query, 2.3.4.1

applications

defining a virtual IP address, 4.1.2

online maintenance and upgrades, 2.2.4

architecture

recommendations, 4.2

architectures

extended distance Oracle RAC, 4.1.4

Oracle Application Server, 4.3.1

single-instance Oracle Database (noncluster), 4.1.1

ASM_PREFERRED_READ_FAILURE_GROUPS initialization parameter, 4.1.4

automatic failover

Oracle Data Guard, 4.1.5.1

automatic maintenance tasks, 2.4.1

automatic storage management

description, 2.1.7

Automatic Storage Management (ASM)

failure groups, 4.1.4

Fast Mirror Resync, 2.1.7

server-based mirroring, 4.1.4

storage migration, 2.2.2.7

using normal or high redundancy, 4.1.4

volume manager, 4.1.4

with Database Storage Grid, 2.3.3

Automatic Workload Repository (AWR), 2.4.1

availability

definition, 1.2

B

backing out a transaction, 2.1.6

backups

Oracle Secure Backup, 2.1.9

block recovery

using Flashback logs

Flashback technologies, 2.1.6

block recovery using Flashback logs, 2.1.6

C

Cluster Ready Services (CRS)

avoiding downtime during upgrades, 2.2.2.5

cold cluster failover, 4.1.6

Oracle Clusterware and Data Guard, 4.1.6

with Oracle Clusterware, 4.1.2

cold failover cluster

described, 4.1.2

computer failure, 1.4

corruptions

prevention and detection of block corruption, 2.1.16

D

Dark Fiber

Dense Wavelength Division Multiplexing (DWDM), 4.1.4

data block corruption

prevention and detection parameters, 2.1.16

data corruption, 1.4

data corruptions

detecting, 2.1.16

Data Guard

benefits, 2.1.3

comparing to Streams, 2.1.4

hub architecture, 4.1.5.2

Data Guard hub, 4.1.5.2

Data Recovery Advisor, 2.1.10

Database Replay, 2.4.2

Database Server Grid, 2.3.1

description, 2.3.2

Database Storage Grid, 2.3.1

description, 2.3.3

database upgrades

using Oracle Streams, 2.2.2.8

databases

applying Oracle interim patches, 2.2.2.3

server grid, 2.3.1

DB_BLOCK_CHECKING initialization parameter, 2.1.16

DB_BLOCK_CHECKSUM initialization parameter, 2.1.16

DB_LOST_WRITE_PROTECT initialization parameter, 2.1.16

DB_ULTRA_SAFE initialization parameter, 2.1.16

DBA_FLASHBACK_TRANSACTION_STATE view, 2.1.6

DBMS_FLASHBACK.TRANSACTION_BACKOUT() procedure, 2.1.6

Dense Wavelength Division Multiplexing (DWDM or Dark Fiber), 4.1.4

downtime

causes, 1.4

cost, 3.2.2

DWDM

Dense Wavelength Division Multiplexing., 4.1.4

E

endian format platforms

avoiding downtime during migration of different, 2.2.2.10

avoiding downtime during migration of same, 2.2.2.9

extended distance clusters

architecture, 4.1.4

configuring a third site for a voting disk, 4.1.4

external redundancy

ASM server-based mirroring, 4.1.4

F

failovers

fast-start, 4.1.5.1

multiple standby database architecture, 4.1.5.2

single standby database architecture, 4.1.5.1

failure groups

specifying in an extended cluster, 4.1.4

failures

computer, 1.4

probability, 4.2

site, 1.4

storage, 1.4

Fast Mirror Resync

ASM, 2.1.7

fast-start failovers

single standby database failover, 4.1.5.1

fault diagnosability infrastructure, 2.4.1

flash recovery area

description, 2.1.11

Flashback Data Archive, 2.1.6

Flashback Database

description, 2.1.6

Flashback Drop

description, 2.1.6

flashback logs

used by Flashback features, 2.1.6

Flashback Query

description, 2.1.6

Flashback Restore Points

description, 2.1.6

Flashback Table

description, 2.1.6

Flashback technology

block recovery using Flashback logs, 2.1.6

Flashback Transaction

description, 2.1.6

Flashback Transaction Query

description, 2.1.6

Flashback Versions Query

description, 2.1.6

frequency of outages, 4.2

G

grid computing, 2.3.1

Database Server Grid, 2.3.1

Database Storage Grid, 2.3.1

grids

server and storage, 2.3.1

H

Hang Manager, 2.1.15, 2.4.1

hang or slow down, 1.4

HARD initiative, 2.1.14

Hardware Assisted Resilient Data (HARD) initiative, 2.1.14

hardware RAID storage subsystem

deferring mirroring to, 4.1.4

hardware upgrades

avoiding downtime during, 2.2.2.1

high availability

applications, 4.3.1

architecture, 1.2

business impact analysis, 3.2.1

importance, 1.3

high availability architectures

comparison, 4.2

high availability solution

characteristics, 1.2

hub-and-spoke configuration

Oracle Streams, 2.1.4

human errors, 1.4

I

intelligent infrastructure, 2.4.1

L

logical standby databases, 2.1.3

transient, 4.1.5.2

lost writes, 1.4

M

Manageability Overhead (MO), 4.2

Maximum Availability Architecture

benefits, 4.1.7

memory

automatic management of, 2.2.1.2

memory advisors, 2.4.1

MEMORY_MAX_TARGET initialization parameter, 2.2.1.2

MEMORY_TARGET initialization parameter, 2.2.1.2

migrating storage

avoiding downtime, 2.2.2.7

mirroring

deferring to RAID storage subsystem, 4.1.4

multiple standby database architecture

failovers, 4.1.5.2

multiple standby database environment

using transient logical standby, 4.1.5.2

multiple standby databases

Data Guard hub, 4.1.5.2

N

nodes

virtual IP addresses, 4.1.2

O

Observer

fast-start failover, 4.1.5.1

one-off patches, 2.2.2.3

online application maintenance and upgrades, 2.2.4

online maintenance

application, 2.2.4

online reorganization

description, 2.2.3

opatch utility

patch upgrades for Oracle RAC, 2.2.2.3

operating systems

requirements for Oracle Clusterware, 4.1.2

Oracle Application Server

high availability architectures, 4.3.1

Oracle Clusterware

advantages over third-party clusterware, 4.1.2

cold cluster failover, 4.1.2

cold failover cluster, 4.1.2

configured with Data Guard, 4.1.6

configuring a third site for a voting disk, 4.1.4

Oracle Clusterware (CRS)

avoiding downtime when upgrading

upgrades, 2.2.2.5

Oracle Data Guard

configured with Oracle Clusterware, 4.1.6

multiple standby database architecture, 4.1.5.2

single standby database architecture, 4.1.5.1

Oracle Database

basic architecture, 4.1.1

with an Oracle RAC extended distance cluster, 4.1.4

with Oracle Clusterware (cold cluster failover), 4.1.2

Oracle Database with Data Guard architecture

benefits, 4.1.5

Oracle Database with Oracle RAC and Data Guard - MAA

benefits, 4.1.7

Oracle Database with Oracle RAC architecture

benefits, 4.1.3

Oracle Database with Streams architecture

benefits, 4.1.8

Oracle Enterprise Manager Grid Control, 2.4.3

Oracle interim (one-off) patches, 2.2.2.3

avoiding downtime during, 2.2.2.3

Oracle Management Agents

Oracle Enterprise Management Grid Control, 2.4.3

Oracle Management Repository

Oracle Enterprise Manager Grid Control, 2.4.3

Oracle Management Service (OMS)

Oracle Enterprise Manager Grid Control, 2.4.3

Oracle RAC

extended distance clusters, 4.1.4

Storage Area Network (SAN), 4.1.4

Oracle Secure Backup (OSB)

overview, 2.1.9

Oracle Steams

performing platform migrations, 2.2.2.8

Oracle Streams

1-N or hub-and-spoke configuration, 2.1.4

performing database upgrades, 2.2.2.8

outages

frequency, 4.2

P

physical standby databases, 2.1.3

real-time query, 2.3.4.1

planned activities

probability of failure during, 4.2

platform migrations

using Oracle Streams, 2.2.2.8

preferred read failure groups

specifying ASM, 4.1.4

probability

of different failures during unplanned and planned activities, 4.2

program global area (PGA)

automatic management, 2.2.1.2

R

Real Application Clusters

benefits, 2.1.2

real-time query standby databases, 2.1.3, 2.3.4.1

Recovery Manager (RMAN)

description, 2.1.8

recovery point objective (RPO)

description, 3.2.4, 4.2

recovery time objective (RTO)

description, 3.2.3, 4.2

restore points

Flashback, 2.1.6

Return On Investment (ROI), 4.2

rollback

transactions, 2.1.6

rolling upgrades

using transient logical standby, 4.1.5.2

S

secure communications

between tiers in grid control environments, 2.4.3

segment advisor, 2.4.1

server generated alerts, 2.4.1

server grid, 2.3.1

server-based mirroring

ASM, 4.1.4

servers

Oracle Clusterware requirements, 4.1.2

service level agreements, 3.3

single standby database architecture

failovers, 4.1.5.1

site failure, 1.4

SLAs, 3.3

Snapshot Standby Database, 2.1.3

snapshot standby database

in a multiple standby database environment, 4.1.5.2

SQL Access Advisor, 2.4.1

SQL Performance Analyzer, 2.4.2

SQL Tuning Advisor, 2.4.1

SSL

enabling for secure communications, 2.4.3

standby database hub

example configurations, 4.1.5.2

standby databases

logical standby, 4.1.5.2

snapshot standby in a multistandby database environment, 4.1.5.2

standby reader farms, 2.3.4.2

storage

migration, 2.2.2.7

mirroring to RAID, 4.1.4

Storage Area Network (SAN)

extended distance clusters, 4.1.4

storage failure, 1.4

storage grid, 2.3.1

Streams

comparing to Data Guard, 2.1.4

description, 2.1.4

system global area (SGA)

automatic management, 2.2.1.2

system upgrades

avoiding downtime during, 2.2.2.1

T

tape backups

with OSB, 2.1.9

thin client watchdog

observer for fast-start failover, 4.1.5.1

third site

for a voting disk, 4.1.4

Total Cost of Ownership (TCO), 4.2

transactions

backing out with Flashback Transaction, 2.1.6

transportable database

for unplanned downtime, 2.1.5

transportable tablespaces

for unplanned downtime, 2.1.5

transportable technologies

for unplanned downtime, 2.1.5

U

Undo Advisor, 2.4.1

undo data

used by flashback features, 2.1.6

unplanned activities

probability of failure during, 4.2

unplanned downtime

transportable tablespaces, 2.1.5

transportable technologies, 2.1.5

upgrades

application, 2.2.4

database, 2.2.2.8

with logical standby databases, 4.1.5.2

V

V$DATABASE_BLOCK_CORRUPTION view, 2.1.16

virtual IP address

defining for applications, 4.1.2

Oracle Clusterware, 4.1.2

volume manager

ASM, 4.1.4

voting disk

configuring a third site, 4.1.4

W

web scaleability

using standby reader farms, 2.3.4.2