Skip Headers

Oracle® Database High Availability Architecture and Best Practices
10g Release 1 (10.1)

Part Number B10726-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Feedback

Go to previous page
Previous
View PDF

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 Manager, 8.2
application failover, 10.1
configuration recommendations, 7.6
RAC not deployed, 7.6.3
application service brownouts, 8.2.2
apply instance failover, 10.1, 10.6
using SQL*Plus, 10.6.1
ARCH attribute of the LOG_ARCHIVE_DEST_n initialization parameter, 7.3.10
architecture
Data Guard only, 4.1
database only, 4.1
MAA, 4.1
Maximum Availability Architecture, 4.1
RAC only, 4.1
Streams, 4.1
archived redo log
recovering, 10.7.2.3
ARCHIVELOG mode, 7.1.5
archiving strategy, 7.3.1
ASM, 6.2.5
striping, 6.2.3
ASM disk group, 6.2.6
ASM failure groups, 6.2.6
ASYNC attribute, 7.3.11
async buffer size, 7.3.11
authentication checks, 7.3.14
automatic checkpoint tuning, 7.1.9
automatic segment space management, 7.1.13
automatic storage management, 6.2.5
description, 3.6
striping, 6.2.3
automatic undo management, 7.1.11
availability
definition, 1.2

B

backup and recovery
automatic disk-based, 7.5.7
double failures, 7.5.2.4
flash recovery area, 7.5.11
Oracle Cluster Registry, 7.5.15
recommendations, 7.5
schedule, 7.5.2.1
backup and recovery plans, 5.5
backup retention policy, 7.5.9
BACKUP VALIDATE RMAN command, 7.5.13
backups
incremental, 7.5.5
long-term, 7.5.2.5
bandwidth, 7.3.8
BLOCK CHANGE TRACKING, 7.5.13
block checking, 7.1.7
block checksums, 7.1.6
block media recovery, 10.7.3.2
block validation, 6.2.7
boot disk, 6.3.1.4
brownouts, 8.2.2

C

capacity planning, 5.3
CFS (cluster filesystem), 6.2.5
change control, 5.4
change management, 5.4
change tracking, 7.5.6
checkpoints, 7.1.8
cluster filesystem, 6.2.5
cluster interconnect, 6.3.2.2
Cluster Ready Services, 7.6
configuration recommendations, 7.6.5
CLUSTER_INTERCONNECTS initialization parameter, 7.2.2
clustering software, 6.4.2.1
clusterwide outage
restoring, 11.4
cold failover, 4.3
connection descriptor
parameters, 7.6.3.3
connection descriptors
production instances, 7.6.1
connect-time failover, 7.4.2
control file
recovering loss, 10.7.2.3
RMAN repository, 7.5.12
control file copies, 7.1.1
CONTROL_FILE_RECORD_KEEP_TIME initialization parameter, 7.1.2
corruption
BACKUP VALIDATE RMAN command, 7.5.13
recovery, 10.7
CPUs
recommended number, 6.3.1
CREATE DISKGROUP statement, 6.2.6
CRS
configuration recommendations, 7.6.5

D

data corruption
preventing, A.1
data failure
manual re-creation, 10.7.3.3
recovery, 10.1, 10.7
recovery with Data Guard, 10.7.1.2.4
recovery without Data Guard, 10.7.1.2.4
RMAN block media recovery, 10.7.3.2
RMAN datafile media recovery, 10.7.3.1
using Data Guard to recover, 10.7.3.4
data failure on standby database
restoring, 11.5
data failures
file or block media recovery, 7.5.2.3
Data Guard
benefits, 3.2
choosing failover, 10.3.1
configuration recommendations, 7.3
connect-time failover, 7.4.2
failover, 10.3
monitoring with Enterprise Manager, 8.2.4
recovering from data failure, 10.7.3.4
switchover, 10.4
using Enterprise Manager to manage targets, 8.3.3
Data Guard failover
using SQL*Plus, 10.3.3
Data Guard only architecture, 4.1
benefits, 4.1.3
Data Guard switchover
choosing, 10.4.1
using SQL*Plus, 10.4.3
data protection mode
changing, 7.3.7.2
data protection modes, 7.3.7
network configuration, 7.3.9
database area, 6.2.5
database configuration
recommendations, 7.1
database failover, 10.3
recovery, 10.1
database only architecture, 4.1
HA features and descriptions, 4.1.1
database patch upgrades
recommendations, 10.9.4
Database Resource Manager, 7.1.19
database switchover, 10.1, 10.4
datafile
recovering, 10.7.2.3
datafile block corruption
ANALYZE statement, 10.7.1.2.1
DBMS_REPAIR package, 10.7.1.2.1
DBVERIFY utility, 10.7.1.2.1
detecting, 10.7.1.1
recovery, 10.7.1
RMAN, 10.7.1.2.1
DB_FLASHBACK_RETENTION_TARGET initialization parameter, 7.1.17
DB_RECOVERY_FILE_DEST initialization parameter, 7.1.16
DB_RECOVERY_FILE_DEST_SIZE initialization parameter, 7.1.16
DB_UNIQUE_NAME initialization parameter, 7.3.15
DBMS_LOGSTDBY.SKIP procedure, 7.3.18.5
DBMS_REDEFINITION PL/SQL package, 10.11
DELAY parameter, 7.6.3.7
disaster recovery planning, 5.6
DNS failover, 10.2.1
downtime
causes, 1.4
cost, 2.2.2
driver version, 6.4.1.1
dropped tablespace
using Flashback Database, 10.8.3.2
dropping database objects, 10.8.2.2
dual failures
restoring, 11.7
dynamic reconfiguration
description, 3.8
dynamic service registration, 7.3.5

E

Enterprise Manager
alerts, 8.2
availability, 8.4
configuring listener, 8.5.1
Database Targets page, 8.2.2
HA architecture, 8.4
HA architecture recommendations, 8.4.1.1
location of Management Repository, 8.5.2
managing Data Guard targets, 8.3.3
managing metrics, 8.2.3
managing patches, 8.3.2
metric, 8.2
monitoring Data Guard, 8.2.4
Notification Rules, 8.2.1
performance, 8.2.2
Policy Violations, 8.3.1
recommended notification rules, 8.2.2
unscheduled outages of Enterprise Manager, 8.4.2
EXTERNAL REDUNDANCY clause, 6.2.6

F

failover
apply instance, 10.6
apply instance using SQL*Plus, 10.6.1
Data Guard, 10.3
database, 10.3
RAC and Data Guard, 10.6
FAILOVER parameter, 7.6.3.4
failure detection
operating system, 6.4.1.2
failure groups, 6.2.6
FAL_SERVER and FAL_CLIENT initialization parameters, 7.3.5
FAST_START_MTTR_TARGET initialization parameter, 7.1.9
fast-start checkpointing, 7.1.9
fencing
operation system, 6.4.1.2
flash recovery area, 6.2.5
backups, 7.5.11
description, 3.11
recommendations for configuring, 7.1.16
size, 7.5.10
tape backups, 7.5.8
Flashback Database, 10.8, 10.8.3.1
description, 3.7.6
enabling, 7.1.17
Flashback Drop, 10.8, 10.8.2.2
description, 3.7.5
Flashback Query, 10.8, 10.8.1.1
description, 3.7.1
Flashback Table, 10.8, 10.8.2.1
description, 3.7.4
flashback technology
example, 10.8.1.4
recovering from user error, 10.8
Flashback Transaction Query, 10.8, 10.8.1.3
description, 3.7.3
Flashback Version Query, 10.8, 10.8.1.2
description, 3.7.2
FORCE LOGGING mode, 7.3.3

G

Grid Control home page, 8.2

H

HA architectures
comparison, 4.2
HARD initiative, 3.12, 6.2.7, A.1
hardware
fencing, 6.3.1.3
Hardware Assisted Resilient Data (HARD) initiative, 3.12, A.1
Hardware Assisted Resilient Data initiative, 6.2.7
hardware components
redundant, 6.2.1
high availability
business impact analysis, 2.2.1
importance, 1.3
importance of documentation, 5.8
operational policies, 5.1
training people, 5.8
high availability architecture
characteristics, 1.2
high availability solution
characteristics, 1.2

I

identical hardware, 6.3.3
index rebuilding, 10.11
initialization parameters
primary and physical standby example, 7.3.1
intelligent storage arrays, 6.2.6
interim patch upgrade, 10.9
I/O operations
load balancing, 6.2.4

J

JDBC fast connection failover, 7.6, 7.6.2
journal file systems, 6.4.1.5

L

latency
effect on primary throughput, 7.3.10
listener.ora file, 7.3.5
listener.ora file sample, B.2.2
load balancers
application server, 6.5.1.2
network, 6.5.1.2
load balancing
I/O operations, 6.2.4
LOAD_BALANCE parameter, 7.6.3.3
local archiving first, 7.3.1
locally managed tablespaces, 7.1.12
LOG_ARCHIVE_DEST_2 initialization parameter, 7.3.5
LOG_ARCHIVE_FORMAT initialization parameter, 7.3.1
LOG_ARCHIVE_LOCAL_FIRST initializatioin parameter, 7.3.1
LOG_ARCHIVE_LOCAL_FIRST initialization parameter, 7.3.13
logging, 6.4.1.5
logical standby archive destination, 7.3.1
logical standby database
configuration recommendations, 7.3, 7.3.18
restoring, 11.3.2
upgrade, 10.10
upgrades, 10.1
logical standby failover
using SQL*Plus, 10.3.3.2
logical standby switchover
using SQL*Plus, 10.4.3.2
logical volume, 6.2.5

M

MAA, 4.1
benefits, 4.1.4
configuration recommendations, 7.4
Management Agent, 8.2
MAX_SERVERS initialization parameter, 7.3.18.2
Maximum Availability Architecture, 4.1
benefits, 4.1.4
maximum availability mode, 7.3.7
maximum performance mode, 7.3.7
maximum protection mode, 7.3.7
media failure
datafile recovery, 10.7.2.3
recovery, 10.7, 10.7.2
media recovery
performance, 7.3.17.1
metric
Enterprise Manager, 8.2
middle-tier applications
service callouts for notification, 7.6.6
mirroring and striping data, 6.2.3
mirroring disks, 6.4.1.6
monitoring
Enterprise Manager, 8.1
multiple node failures, 10.5.1.1.2
multiple standby instances, 7.4.1

N

network components
redundant, 6.5.1.1
network configuration
performance assessment, 7.3.8
network recommendations
all architectures, 6.5.1
RAC, 6.5.2
network recovery objective, 2.2.3
network time protocol, 6.4.2.2
nod failure
multiple, 10.5.1.1.2
node failure
single, 10.5.1.1.1
notification
RAC not deployed, 7.6.3
notification rules
recommended, 8.2.2
notifications
middle-tier applications, 7.6.6
NRO, 2.2.3
NTP, 6.4.2.2

O

object reorganization, 10.1
OCR
backing up, 7.5.15
recovering, 10.7.2.3
OCR protection, 6.2.8.1
ocrconfig tool
backing up Oracle Cluster Registry, 7.5.15
OIFCFG, 6.5.2
online index reorganization, 10.11.2
online object reorganization, 10.1, 10.11
online redo log file
recovering, 10.7.2.3
online redo log files
multiplex, 7.1.4
online reorganization
description, 3.4
online servicing, 6.2.2
online table reorganization, 10.11.1
online tablespace reorganization, 10.11.3
opatch
applying a patch, 10.9.1
listing installed software and patches, 10.9.3
rolling back a patch, 10.9.2
opatch command-line utility, 10.9
operating system parameters, 6.4.1.4
operating system version, 6.4.1.1
Oracle Advanced Security, 7.3.14
Oracle Cluster Registry
backing up, 7.5.15
backups, 7.5.15
recovering, 10.7.2.3
Oracle Cluster Registry protection, 6.2.8.1
Oracle Fail Safe
description, 3.9
Oracle Interface Configuration, 6.5.2
Oracle Net configuration files
samples, B.2
outages
scheduled, 9.2
unscheduled, 9.1

P

PARALLEL_MAX_SERVERS initialization parameter, 7.3.18.3
partial site failover
network routes, 10.2.2
patch
applying with opatch, 10.9.1
rolling back, 10.9.2
patch level, 6.4.1.1
patch upgrade, 10.1, 10.9
patch upgrades
rolling, 10.9
patches
managing with Enterprise Manager, 8.3.2
physical standby database
configuration recommendations, 7.3, 7.3.17
restoring, 11.3.1
physical standby failover
using SQL*Plus, 10.3.3.1
physical standby switchover
using SQL*Plus, 10.4.3.1
primary key constraints, 7.3.18.1
production database activated
restoring, 11.6

R

RAC
benefits, 3.1
configuration recommendations, 7.2
rolling upgrade, 10.1
supported cluster system, 6.3.2.1
RAC availability notifications, 7.6.2
RAC instances
registering with remote listeners, 7.2.1
RAC only architecture, 4.1
benefits, 4.1.2
RAC recovery, 10.1, 10.5.2
unscheduled outages, 10.5.1
RAC rolling upgrade, 10.9, 10.9
RAC rolling upgrades
recomendations, 10.9.4
raw device, 6.2.5
Real Application Clusters
benefits, 3.1
real time apply, 7.3.4
recommendations
component characteristics, 6.1
configuring storage, 6.2
database configuration, 7.1
redundant hardware components, 6.2.1
recovery catalog, 7.5.3
Recovery Manager
description, 3.10
using, 7.5.1
recovery point objective, 2.2.4
recovery time objective, 2.2.3
redo data
secure transmission, 7.3.14
redo log files and groups
size, 7.1.3
redundant hardware, 6.3.1.2
RELY constraint, 7.3.18.1
remote archiving, 7.3.1
remote listeners
registering instances, 7.2.1
REMOTE_ARCHIVE_ENABLE initialization parameter, 7.3.1
resetlogs on production database
restoring standby database, 11.6
restoring failed instances
RAC, 11.2
restoring failed nodes
RAC, 11.2
restoring RAC instance
client connections, 11.2.2
restoring service, 11.2.1
resumable space allocation, 7.1.15
RESUMABLE_TIMEOUT initialization parameter, 7.1.15
RETENTION GUARANTEE clause, 7.1.11
RETRIES parameter, 7.6.3.6
RMAN
description, 3.10
using, 7.5.1
RMAN autobackup, 7.5.4
RMAN datafile media recovery, 10.7.3.1
RMAN recovery catalog, 7.5.2.5
RMAN repository
control file, 7.5.12
role-based destinations, 7.3.1
rolling back a patch, 10.9.2
rolling patch upgrades, 10.9
rolling upgrade, 10.1
row and transaction inconsistencies, 10.8.1
RPO, 2.2.4
RTO, 2.2.3

S

SAME methodology, 6.2.3
scheduled outage planning, 5.7
scheduled outages
preparation, 9.2.3
primary site recovery steps, 9.2.1
RAC recovery, 10.5.2
secondary site recovery steps, 9.2.2
types, 9.2
secondary site outage
restoring, 11.4
secure transmission of redo data, 7.3.14
security policies, 5.10
security recommendations, 7.1.18
server hardware recommendations
all architectures, 6.3.1
Data Guard only and MAA, 6.3.3
RAC only and MAA, 6.3.2
server parameter file, 7.1.20
recovering, 10.7.2.3
server parameter file samples, B
server software
recommendations for all architectures, 6.4.1
service level agreement
components, 5.2
service level agreements, 2.3
service level management, 5.2
SERVICE_NAME parameter, 7.6.3.5
services
creation, 7.6.4
publishing production, 7.6.8
publishing standby, 7.6.7
single node failure, 10.5.1.1.1
site failover, 10.2.1
network routes, 10.2.1
partial, 10.2.2
recovery, 10.1
WAN traffic managers, 6.5.3.2
SLA
components, 5.2
SLAs, 2.3
software area, 6.2.5
SPFILE, 7.1.20
recovering, 10.7.2.3
SPFILE samples, B
SQL Apply
skipping objects, 7.3.18.5
sqlnet.ora file sample, B.2.1
SQLNET.SEND_BUF_SIZE and SQLNET.RECV_BUF_SIZE Oracle Net parameters, 7.3.6
SRLs, 7.3.2
SSH port forwarding, 7.3.12
standby archive destination, 7.3.1
standby control file
recovering loss, 10.7.2.3
standby database
comparing logical and physical, 7.3
restoring, 11.3
standby database unique name, 7.3.15
standby instances
multiple, 7.4.1
standby redo log
recovering, 10.7.2.3
standby redo logs, 7.3.2
STANDBY_ARCHIVE_DEST initialization parameter, 7.3.1
storage area
flash recovery area, 6.2.5
storage areas
database area, 6.2.5
software area, 6.2.5
storage arrays
online servicing, 6.2.2
storage devices
data validation, A.1
storage recommendations
Data Guard only and MAA, 6.2.5.1
RAC only and MAA, 6.2.5.1, 6.2.8
Streams
description, 3.3
Streams architecture, 4.1
benefits, 4.1.5
supplemental logging, 7.3.18.1
swap partitions
mirroring, 6.4.1.3
switchover steps, 10.4

T

table inconsistencies, 10.8.2
tablespace renaming, 10.11
TAF, 7.6.3
TCP parameters, 6.5.3.1
temporary file systems, 6.4.1.3
temporary tablespaces, 7.1.14
TIMED_STATISTICS initialization parameter, 7.1.10
tnsnames.ora file, 7.3.5
tnsnames.ora file sample, B.2.3
TRANSACTION_CONSISTENCY initialization parameter, 7.3.18.4
Transparent Application Failover, 7.6.3
transportable tablespace feature, 3.5

U

UNDO_MANAGEMENT initialization parameter, 7.1.11
UNDO_RETENTION initialization parameter, 7.1.11
UNDO_TABLESPACE initialization parameter, 7.1.11
unscheduled outages
Enterprise Manager, 8.4.2
primary site recovery steps, 9.1.1
RAC recovery, 10.5.1
secondary site recovery steps, 9.1.2
types, 9.1
upgrade
rolling for patches, 10.9
using logical standby database, 10.1, 10.10
user error
flashback technology, 10.8
recovery, 10.1

V

V$MTTR_TARGET_ADVICE view, 7.1.9
VALID_FOR attribute, 7.3.1
versions
operating system, patch, driver, 6.4.1.1

W

WAN environment
tuning the network, 7.3.6
WAN traffic managers, 6.5.3.2