Index

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

A

alerts

Enterprise Manag er, 8-3

application failover, 10-2

configuration recommendations, 7-44

RA C not deployed, 7-47

application service brownouts, 8-9

apply instance failover, 10-2, 10-18

using SQL*Plus, 10-19

ARCH attribute of the LOG_ARCHIVE_DEST_n initialization parameter, 7-28

architecture

Data Guard only, 4-2

database only, 4-2

MAA, 4-2

Maximum Availability Architecture, 4-2

RAC only, 4-2

Streams, 4-2

archived redo log

recovering, 10-32

ARCHIVELOG mode, 7-4

archiving strategy, 7-16

ASM, 6-5

stri ping, 6-3

ASM disk group, 6-7

ASM failure groups, 6-6

ASYNC attribute, 7-29

async buffer size, 7-29

authentica tion checks, 7-31

automatic checkpoint tuning, 7-6

automatic segment space management, 7-9

auto matic storage management, 6-5

description, 3-6

striping, 6-3

automatic un do management, 7-7

availability

definiti on, 1-2

B

backup and recovery

automatic disk-based, 7-40

double failures, 7-38

flash recovery area, 7-41

Oracl e Cluster Registry, 7-43

recommendations, 7-3 6

schedule, 7-38

backup and recovery pla ns, 5-7

backup retention policy, 7-40

BACKUP VALIDATE RMAN command, 7-43

backups

incremental, 7-39

long-term, 7-39

bandwidth, 7-25

BLOCK CHANGE TR ACKING, 7-43

block checking, 7-5

block checksums, 7-4

block media recovery, 10-33

block validation, 6-8

boot disk, 6-10

brownouts, 8-9

C

capacity planning, 5-4

CFS (cluster filesystem), 6-5

change control, 5-5

change manageme nt, 5-4

change tracking, 7-40

checkpoints, 7-5

cluster filesystem, 6 -5

cluster interconnect, 6-11

Cluster Ready Services , 7-44

configuration recommendations, 7-50

CLUSTER_INTERCONNECTS initialization parameter, 7-13

clustering software, 6-13

clusterwide outage

restoring, 11-14

cold failover, 4-15

connection descriptor

parameters, 7-49

connection descriptors

produ ction instances, 7-45

connect-time failover, 7-36

control file

recovering loss, 10-30

RMAN repository, 7-42

control file copies, 7-2

CONTROL_FILE_RECORD_KEEP_TIME initialization parameter, 7-3

corruption

BACKUP VALIDATE RMAN command , 7-43

recovery, 10-22

CPUs

recommended number, 6-9

CREATE DISKGROUP statement, 6-7

CRS

configuration recommendations, 7-50

D

data corr uption

preventing, A-1

data fail ure

manual re-creation, 10-34

recovery, < a href="recover.htm#1006150">10-2, 10-22

recovery with Data Guard, 10-27

recovery without Data Guard, 10-26

RMAN block media recovery, 10-33

RMAN datafile media recovery, 10-33

using Data Guard to recover, 10-35

data failure on standby database

restoring, 11-16

data failures

file or block media recovery, 7-38

Data Guard

benefits, 3-2

choosing failover, 10-10

configuration recommendations, 7-13

connect-time failover, 7-36

failover, 10-10

monitoring wi th Enterprise Manager, 8-11

recovering from data failure, 10-35

switchover, 10-12

using Enterprise Manager to manage targets, 8-12

Data Guard failover

using SQL*Plus, 10-11

Data Guard only archite cture, 4-2

benefits, 4-7

Data Guard switchover

choosing, 10-13

using SQL*Plus, 10-13

data pro tection mode

changing, 7-24

da ta protection modes, 7-22

network configuration, 7-26

database area, 6-4

database configuration

recommendations, 7-2

database failover, 10-10

recovery, 10-2

database only architecture, 4-2

HA features and descriptions, 4-3

database patch upgrades

recommendations, 10-48

Database Resource Manager, 7-11

database switchover, 10-2, 10-12

datafile

recovering, 10-30

datafile block corruption

ANALYZE statement, 10-25

DBMS_REPAIR package, 10-25

DBVERIFY utility, 10-25

detecting, 10-23

recovery, 10-23

RMAN, 10-25

DB_FLASHBACK_RETENTION_TARGET initializa tion parameter, 7-11

DB_RECOVERY_FILE_DEST initialization parameter, 7-10

DB_RECOVERY_FILE_DEST_SIZE initialization parameter, 7-10

DB_UNIQUE_NAME initialization parameter, 7-32

DBMS_LOGSTDBY.SKIP procedure, 7-35

DBMS_REDEFINITION PL/SQL package, 10-54

DELAY parameter, 7-49

disaster recovery planning, 5-8

DNS failover, 10-7

downtime

causes, 1-4

cost, 2-3

driver version, 6-12

dropped tablespace

using Flashback Database, 10-44

dropping database objects, 10-42

dual failures

restoring, 11-20

dynamic reconfiguration

description, 3-8

< /dl>

dynamic service registration, 7-20

E

Enterprise Manager

alerts, 8-3

availab ility, 8-13

configuring listener, 8-19

Database Targets page, 8-9

HA architecture, 8-13

HA architecture recommendations, 8-15

location of Management Repository, 8-20

managing Data Guard targets, < a href="monitor.htm#1007686">8-12

managing metrics, 8-10

managing patches, 8-12

metric, 8-4

monitoring Data Guard, 8-11

Notification Rules, 8-5

performance, 8-9

Policy Vi olations, 8-12

recommended notification rules, 8-10

unscheduled outages of Enterprise Manager, 8-17

EXTERNAL REDUNDANCY clause, 6-7

< h2 class="GroupTitlesIX">F

failover

apply instance, 10-18

apply instance using SQL*Pl us, 10-19

Data Guard, 10-10

database, 10-10

RAC and Data Guard, 10-1 8

FAILOVER parameter, 7-49

failure detec tion

operating system, 6-12

fail ure groups, 6-6

FAL_SERVER and FAL_CLIENT initialization parameters, 7-20

FAST_START_MTTR_TARGET initialization parameter, 7-6

fast-start checkpointing, 7-5

fencing

operation system, 6-12

flash recovery ar ea, 6-5

backups, 7-41

description, 3-11

recommendations for configuring, 7-10

size, 7-41

tape backup s, 7-40

Flashback Database, 10-37, 10-43

description, 3-8< /dd>

enabling, 7-10

Flashback Drop, 10-37, 10-42

description, 3-8

Flashback Query, 10-36, 10-38

description, 3-7

Flashback Table, 10-37, 10-41

description, 3-8

flashback technology

example, 10-39

recovering from user error, 10-35

Flashback Transaction Query, 10-37, 10-39

description, 3-8

Flashback Version Query, 10-36, 10-38

description, 3-8

FORCE LOGGIN G mode, 7-19

G

Grid Control home page, 8-3

H

HA architectures

comparison, 4-12

HARD initiative, 3-11, 6-8, A-1

hardware

fencing, 6-10

Hardware Assisted Resilient Data (HARD) initiative, 3-11, A-1

Hardware Assisted Resilient Data initiative, 6-8

hardware components

redund ant, 6-3

high availability

busin ess impact analysis, 2-3

importance, 1-3< /dd>

importance of documentation, 5-11

operational policies, 5-2

training people, 5-11

high availability architecture

characteristics, 1-3

high availability solution

characteristics, 1-2

I

identical hardware, 6-11

index rebuilding, 10-54

initialization parameters

primary and physical standby example, 7-17

intelligent storage arrays, 6-7

interim patch upgrade, 10-45

I/O operations

load balancing, 6-4

J

JDBC fast connection failover, 7-44, 7-47

journal file systems, 6-13

L

latency

effect on primary throughput, 7-28

listener.ora file, 7-21

listener.o ra file sample, N-8

load balancers

appli cation server, 6-16

network, 6-16

load balancing

I/O operations, 6-4

LOAD_BALANCE parameter, 7-49

local archiving first, 7-17

locally managed tablespaces, 7-9

LOG_ARCHIVE_DEST_2 initialization parameter, 7-20

LOG_ARC HIVE_FORMAT initialization parameter, 7-17

LOG_ARCHIVE_LOCAL_FIRST initializ atioin parameter, 7-17

LOG_ARCHIVE_LOCAL_FIRST initialization parameter, 7-31

logging, 6-13

logic al standby archive destination, 7-17

logical standby database

configuration recommendations, 7-14, 7-33

restoring, 11-13

upgrade, 10-49

upgrades, 10-3

logical standby fa ilover

using SQL*Plus, 10-12

lo gical standby switchover

using SQL*Plus, 10-14

< dd class="L1IX">logical volume, 6-5

M

MAA, 4-2

benefits, 4-9

configuration recommendations, 7-35

Management Agent, 8-2

MAX_SERVERS initialization parameter, 7-33

Maximum Availability Architecture, 4-2

benefits, 4-9

maximum availability mode, 7-23

maximum performance mode, 7-23

max imum protection mode, 7-22

media failure

datafile recovery, 10-30

recovery, 10-22, 10-29

media recovery

performanc e, 7-32

metric

Enterprise Mana ger, 8-4

middle-tier applications

service callouts for notification, 7-50

mirroring and striping data, 6-3

mirroring disks, 6-13

monitoring

Enterprise Manager, 8-2

multiple node failures, 10-16

multiple standby instances, 7-35

N

network components

redun dant, 6-14

network configuration

performance assessment, 7-25

network recommendations

all architectures, 6-14

RAC, 6-17

network recovery objective, 2-4

network time protocol, 6-14

nod failure

m ultiple, 10-16

node failure

sin gle, 10-16

notification

RAC not deployed, 7-47

notification rules

recommended, 8-10

notifications

middle-tier applications, 7-50

NRO, 2-4

NTP, 6-14

O

object reorgan ization, 10-3

OCR

backing up, 7-43

recovering, 10-32

OCR protection, 6-9

ocrconfig tool

backi ng up Oracle Cluster Registry, 7-43

OIFCFG, 6-17

online index reorganization, 10-54

onli ne object reorganization, 10-3, 10-53

onlin e redo log file

recovering, 10-31

online redo log files

multiplex, 7-3

online reorganization

description, 3-5

online servicing, 6-3

online table reorganization, 10-54

online tablespace reorganization, 10-54

opatch

applying a patch, 10-46

listing installed software and patches, 10-47

rolling back a patch, 10-47

opatch command-line utility, 10 -45

operating system parameters, 6-13

operating syst em version, 6-12

Oracle Advanced Security, 7-31

Oracle Cluster Registry

backing up, 7-4 3

backups, 7-43

recovering, 10-32

Oracle Cluster Registry protection, 6-9

Oracle Fail Safe

description, 3-9

Oracle Interface Configuration, 6-17

Oracle Net configuratio n files

samples, N-8

outages

scheduled, 9-8

unscheduled, 9-2

P

PARALLEL_MAX_SERVERS initialization parameter, 7-34

partial site failover

network routes, 10-8

patch

applying with opatch, 10-46

rolling back, 10-47

patch level, 6-12

patch upgrade, 10-3 , 10-45

patch upgrades

rolling, 10-45

patches

managing with Enterprise M anager, 8-12

physical standby database

configuration recommendations, 7-14, 7-32

restoring, 11-10

physical standby failover

using SQL*Plus, 10-11

physical standby switcho ver

using SQL*Plus, 10-14

prima ry key constraints, 7-33

production database activated

restoring, 11-18

RAC

benefits, 3-2

configuration recommendations, 7-12

rolling upgrade, 10-3

supported cluster system, 6-11

RAC availability notifications, 7-47

RAC instances

registering with remote li steners, 7-13

RAC only architecture, 4-2

benefits, 4-5

RAC recovery, 10-2, 10-17

unscheduled outages, 10-15

RAC rolling upgrade, 10-45

RAC rolling upgrades

recomendations, 10-48

raw device, 6-5

Real A pplication Clusters

benefits, 3-2

real time apply, 7-20

recommendations

component characteristics, 6-2

configuring storage, 6-2

database configuration, 7-2

redundant h ardware components, 6-3

recovery catalog, 7-39

Recovery Manager

description, 3-10

using, 7-37

recovery point object ive, 2-5

recovery time objective, 2-4

redo data

secure transmission, 7-31

redo log files and groups

size, 7-3

redundant hardware, 6-10

RELY constraint, 7-33

remote archiving, 7-17

remote listeners

registering instances, 7-13

REMOTE_ARCHIVE_ENABLE initialization parameter, 7-16

rese tlogs on production database

restoring standby database, 11-18< /dd>

restoring failed instances

RAC, 11- 2

restoring failed nodes

RAC, 1 1-2

restoring RAC instance

client connections, 11-5

restoring service, 11-4

resumable space allocation, 7-9

RESUMABLE_TIMEOUT initialization paramet er, 7-10

RETENTION GUARANTEE clause, 7-8< /dd>

RETRIES parameter, 7-49

RMAN

description, 3-10

using, 7-37

RMAN autobackup, 7-39

RMAN datafile media recovery, 10-33

RMAN recovery catalog, 7-39

RMAN repository

control file, 7-42

role-based destinations, 7-17

rolling back a pa tch, 10-47

rolling patch upgrades, 10-45

rolling upgrade, 10-3

row and transaction inconsistencies , 10-37

RPO, 2-5

RTO , 2-4

S

SAME methodology, 6-3

scheduled outage planning, 5-9

scheduled outages

preparation, 9-12

primary site recovery steps, 9-9

RAC recovery, 10-17

secondary site recovery steps, 9-11

types, 9-8

secondary site outage

restoring, 11-14

secure transmission of redo data, 7-31

security policies, 5-13

security recommendations, 7-11

server hardware recommendations

all architectures, < a href="sysnet.htm#1011813">6-9

Data Guard only and MAA, 6-11

RAC only and MAA, 6-10

server parameter file, 7-12

recovering, 10-32

server parameter file samples, N-1

server software

recommendations for all architectures, 6-12

service level agreement

components, 5-3

service level agreements, 2-5

service level management, 5-2

SERVICE_NAME parameter, 7-49

services

creation, 7-50

publishing pro duction, 7-51

publishing standby, 7-51

single node failure, 10-16

site failover, 10-3

network routes, 10-5

partial, 10-7

recovery, 10-2< /dd>

WAN traffic managers, 6-18

SLA

components, 5-3

SLAs, 2-5

software area, 6-4

SPFILE, 7-12

recovering, 10-32

SPFILE samples, N-1

SQL Apply

skipping objects, 7-35

sqlnet.ora file sample, N-8

SQLNET.SEND_BUF_SIZE and SQLNET.RECV_BUF_SIZE Oracle Net parameters, 7-22

SRLs, 7-19

SSH port forwarding, 7-30

standby archive destination, 7-17

standby control file

recovering loss, 10-30

standby database

comparing logical and physical, 7-14

restoring, 11-10

stand by database unique name, 7-32

standby instances

multiple, 7-35

standby redo log

recovering, 10-31

standby redo logs, 7-19

STANDBY_ARCHIVE_DEST initialization parameter, 7-17

storage area

flash recovery area, 6-5

storage areas

database area, 6-4

software area, 6-4

storage arrays

online servicing, 6-3

storage devices

data validation, A-1

storage recommendations

Data Guard only and MAA, 6-5

RAC only and MAA, 6-5, 6-9

Streams

description, 3-4

Streams architecture, 4-2

benefits, 4-10< /dd>

supplemental logging, 7-33

swap partitions

mirroring, 6-12

switchover steps, 10-12

SYNC attribute

PARALLEL/NOPARALLEL , 7-27

T

table inconsistencies, 10-41

tablespace renaming, 10-54

TAF, 7-47

TCP parameters, 6-17

temporary file systems, 6-13

temporary tablespaces, 7-9

TIMED_STATISTICS initialization parameter, 7-7

tnsnames.ora file, 7-21

tnsnames.ora file sample, N-9

TRANSACTION_CONSISTENCY initialization parameter, 7-34

Transparent Application Failover, 7-47

transportable tablespace feature, 3-5

U

UNDO_MANAGEMENT initialization pa rameter, 7-7

UNDO_RETENTION initialization parameter, 7-7

UNDO_TABLESPACE initialization parameter, 7-7

unscheduled outages

Enterprise Manager, 8-17

primary site recovery steps, 9-4

RAC recovery, 10-15

secondary site recovery steps, 9-6

types, 9-2

upgrade

rolling f or patches, 10-45

using logical standby database, 10-3, 10-49

user error

f lashback technology, 10-35

recovery, 10-3

V

V$MTTR_TARGET_ADVICE view, 7-6

VALID_FOR attribute, 7-17

versions

op erating system, patch, driver, 6-12

W

WAN environment

tuning the network, 7-22

WAN traffic managers, 6-18