Skip Headers
Oracle® Database High Availability Best Practices
11g Release 2 (11.2)

E10803-06
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
Contact Us

Go to previous page
Previous
PDF · Mobi · ePub

Index

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

A

ACFS snapshot, 8.6.1
Active Data Guard option
assessing database waits, 9.3.8.5
Active Session History Reports (ASH), 5.2.3
Advanced Queuing (AQ), 9.3.1
alerts
Enterprise Manager, 12.2.1
ALTER DATABASE statement
CONVERT TO SNAPSHOT STANDBY, 9.6
specifying a default temporary tablespace, 5.2.8
ALTER DISKGROUP ALL MOUNT statement, 4.5.3
ALTER SESSION ENABLE RESUMABLE statement, 5.2.9
ANALYZE TABLE tablename VALIDATE STRUCTURE CASCADE, 9.3.8.3
application failover
DBMS_DG.INITIATE_FS_FAILOVER, 13.2.4
in an Oracle Data Guard configuration, 13.2.4
in an Oracle RAC configuration, 13.2.4
application workloads
database performance requirements for, 4.1
applications
defining as services, 6.2.5
failover, 13.2.4
Fast Application Notification (FAN), 6.1.1.2, 13.2.4
fast failover, 11.5
login storms, 11.5
monitor response times, 13.2.4
service brownouts, 12.2.3
tracking performance with Beacon, 12.2.2
upgrades, 14.2.9
Apply Lag
metric in Enterprise Manager, 12.2.4
AQ_HA_NOTIFICATIONS parameter, 11.1
AQ_TM_PROCESSES parameter, 9.4.1
architecture
high availability, 1.1
archival backups
keeping, 8.2.1
ARCHIVELOG mode, 5.1.1
archiver (ARCn) processes
reducing, 9.4.1
archiving strategy, 9.3.5
ASM
See Oracle Automatic Storage Management (Oracle ASM), 4.2
ASM_DISKGROUPS initialization parameter, 4.5.3
ASM_DISKSTRING parameter, 4.4.1
ASM_POWER_LIMIT
initialization parameter, 4.5.2
ASM_PREFERRED_READ_FAILURE_GROUPS initialization parameter
in extended clusters, 7.3.4
ASMCA utility
storage management, 4.5.8
ASMCMD command-line utility
storage management, 4.5.7
ASMLib, 4.4.6
disk labels, 4.4.4
ASR
See Oracle Auto Service Request (ASR)
asynchronous disk I/O, 5.1.7
asynchronous I/O
enabling, 7.1.3
V$IOSTAT_FILE view, 5.1.7
AUTOBACKUP statement
RMAN, 8.2.5
Automatic Database Diagnostic Monitor (ADDM), 5.2.3
automatic performance tuning, 5.2.3
automatic segment space management, 5.2.7
using, 5.2.7
Automatic Shared Memory Management, 5.1.9
Automatic Storage Management (Oracle ASM)
redundancy, 4.3.2.2
automatic tablespace point-in-time recovery TSPITR, 13.2.7.4
automatic undo management
described, 5.2.5
Automatic Workload Repository (AWR), 5.1.4, 5.2.3, 9.7
best practices, 5.2.3
evaluating performance requirements, 4.1
AWR
See Automatic Workload Repository (AWR)

B

backup and recovery
best practices, 8.2
checksums calculated during, 5.1.6.1
enabling with ARCHIVELOG mode, 5.1.1
backup files
fast recovery area disk group failure, 13.2.5.4
backup undo optimization, 8.1.3
backups
automatic, 8.2.5
comparing options, 8.3
configuring, 8.2
creating and synchronizing, 8.2.3
determine a retention policy, 8.2.1
keeping archival (long term), 8.2.1
OCR, 6.3.2
performing regularly, 8.5.4
RMAN recovery catalog, 8.2.2
Beacons, 12.2.2
configuring, 12.2.2
benefits
Data Guard broker, 9.3.1
high availability best practices, 1.2
best practices
AWR, 5.2.3
backup and recovery, 8.2
Data Guard configuration, 9
Database Resource Manager, 5.2.10
failover
manual, 9.4.2.4
failover (fast-start), 9.4.2.3, 13.2.2.2
failover (manual), 13.2.2.3, 13.2.2.3
fast connection failover configuration, 11
high availability, 1.1
Oracle ASM configuration, 4.4
Oracle ASM operational best practices, 4.5
Oracle ASM strategic, 4.3
Oracle Clusterware configuration, 6.2
Oracle Clusterware operations and management, 6.3
Oracle Database configuration, 5.1
Oracle Database operations and management, 5.2
Oracle GoldenGate configuration, 10.2
Oracle RAC configuration, 7.1, 7.1
Oracle RAC rolling upgrades, 14.2.4.2
storage subsystems, 4
switchover, 14.2.1.2
upgrades, 14.2.4.1
BLOCK CHANGE TRACKING clause, 8.2.4
brownouts, 12.2.3

C

capacity planning, 6.3.1
change tracking
for incremental backups, 8.2.4
checkpointing
bind Mean Time To Recover (MTTR), 7.1.1
client connections
migrating to and from nodes, 6.1.1
clients
application failover, 13.2.4
configuring for failover, 11.1
load balancing, 6.2.6
cluster file system
using shared during software patching, 6.2.2
Cluster Health Monitor (CHM), 12.4
Cluster Ready Services (CRS)
described, 13.3.1.1
moving services, 13.2.3.2
recovering service availability, 13.3.1.1
relationship to OCR, 13.2.3.3
Cluster Time Synchronization Service (CTSS), 6.2.8
clustered ASM
enabling the storage grid, 4.2.1
clusters
extended, 7.3
clusterwide outage
restoring the standby database after, 13.3.4
COMMIT NOWAIT
Oracle GoldenGate, 10.2.3
COMPATIBLE initialization parameter, 14.2.3
complete site failover
recovery time objective (RTO), 13.2.1.2
compression
redo transport, 9.3.7.2
configuring databases for high availability
with the MAA Advisor, 12.3.4
configuring Oracle Database for shared server, 11.5
connection pools
adjusting number of, 11.5
Connection Rate Limiter
listener, 11.5
connect-time failover, 13.3.1.3
control files
in a fast recovery area disk group failure, 13.2.5.4
CONTROL_FILES initialization parameter, 13.2.5.4.1
coordinated, time-based, distributed database recovery, 13.2.8
corruptions
checking database files, 8.5.2
preventing with Data Recovery Advisor, 5.2.2
CREATE DISKGROUP statement
examples, 4.3.1, 4.3.2.1
CRS
See Cluster Ready Services (CRS)
crsctl command for system maintenance, 14.2.11
CRSD process
OCR backups, 6.3.2
CTSS
time management, 6.2.8
cumulative incremental backup set, 8.3

D

Dark Fiber
Dense Wavelength Division Multiplexing (DWDM), 7.1.4
data
criticality and RPO, 8.2.1
recovering backups and RTO, 8.2.1
data area
contents, 4.3.1
disk partitioning, 4.3.1
data area disk group failure
recovery options, 13.2.5.3
data corruption
detecting, 5.1.6.2
protection through Oracle ASM redundancy disk groups, 5.1.6.1
solution, 5.1.6.1
data failure
restoring fault tolerance on standby database, 13.3.5
Data Guard
archiving strategies, 9.3.5
broker, 9.3.1
using FAN/AQ, 9.3.1
database upgrades, 14.2.6.2
failover
best practices (fast-start), 9.4.2.3
best practices (manual), 9.4.2.4
recovery for data area disk group failures, 13.2.5.3
when to perform, 13.2.2.1
log apply services, 9.3.8
managing targets, 12.3.3
monitoring, 12.2.4
multiple standby databases, 9.3.9
performance, 9.7
platform migration, 14.2.7.4
protection against data corruption, 5.1.6.1
redo transport services, 9.2.1
restoring standby databases, 13.3.2
role transitions, 9.4.2.4
snapshot standby databases, 9.6
SQL Apply, 14.2.6.2
standby-first patch apply, 14.2.3
status events in Enterprise Manager, 12.2.4
switchover, 14.2.1.3
Data Pump
for platform migration, 14.2.7.7
moving the contents of the SYSTEM tablespace, 14.2.7.8
Data Recovery Advisor
detect and prevent data corruption, 5.2.2
data retaining backups, 8.2.1
data type restrictions
resolving with Extended Datatype Support (EDS), 14.2.6.2.1
data-area disk group failure
See Also Data Guard failover, fast-start failover, local recovery
database files
management optimizations, 4.2
Oracle ASM integration, 4.2
recovery-related, 4.3.1
database patch upgrades
recommendations, 14.2.4.1
Database Resource Manager, 5.2.10
best practices, 5.2.10
Database Upgrade Assistant (DBUA), 14.2.6.1
database upgrades
with edition-based redefinition, 14.2.8
with transient logical standby database, 14.2.6.2.2
databases
checking files for corruption, 8.5.2
configuration recommendations, 5
configuring with the MAA Advisor, 12.3.4
evaluating performance requirements, 4.1
migration, 14.2.7.5
object reorganization, 14.2.10
recovery in a distributed environment, 13.2.8
resolving inconsistencies, 13.2.7.3
switching primary and standby roles among, 14.2.1.1
upgrades, 14.2.6
DB_BLOCK_CHECKING initialization parameter, 5.1.6.1, 9.3.8.3
DB_BLOCK_CHECKSUM initialization parameter, 4.6.1, 5.1.6.1, 9.3.8.3
DB_CACHE_SIZE initialization parameter, 9.3.8.4
DB_CREATE_FILE_DEST initialization parameter
enabling Oracle Managed Files, 4.3.1
DB_CREATE_ONLINE_LOG_DEST_n initialization parameter
location of Oracle managed files, 4.3.1
DB_FLASHBACK_RETENTION_TARGET parameter, 5.1.4
DB_KEEP_CACHE_SIZE initialization parameter, 9.3.8.4
DB_LOST_WRITE_PROTECT initialization parameter, 5.1.6.1, 9.3.8.3
DB_RECOVERY_FILE_DEST initialization parameter
fast recovery area, 5.1.3
DB_RECOVERY_FILE_DEST_SIZE initialization parameter
limit for fast recovery area, 5.1.3
DB_RECYCLE_CACHE_SIZE initialization parameter, 9.3.8.4
DBCA
balancing client connections, 6.2.6
DBMS_DG.INITIATE_FS_FAILOVER PL/SQL procedure
application failover, 13.2.4
DBMS_FLASHBACK.TRANSACTION_BACKOUT PL/SQL procedure, 13.2.7.1
DBMS_REDEFINITION PL/SQL package, 14.2.10
DBVERIFY utility, 9.3.8.3
decision support systems (DSS)
application workload, 4.1
default temporary tablespace
specifying, 5.2.8
DEFAULT TEMPORARY TABLESPACE clause
CREATE DATABASE statement, 5.2.8
DEFAULT_SDU_SIZE sqlnet.ora parameter, 9.3.7.2
Dense Wavelength Division Multiplexing (DWDM or Dark Fiber), 7.1.4
Device Mapper
disk multipathing, 4.4.1
differential incremental backup set, 8.3
DISABLE BLOCK CHANGE TRACKING, 8.2.4
disabling parallel recovery, 5.1.10, 5.1.10
disk backup methods, 8.3
disk devices
ASMLib disk name defaults, 4.4.4
configuration, 4.3.1, 4.3.2.1, 4.3.4
disk labels, 4.4.4
multipathing, 4.4.1
naming
ASM_DISKSTRING parameter, 4.4.1
ASMLib, 4.4.6
partitioning for Oracle ASM, 4.3.1
protecting from failures, 4.3.2
disk errors
mining vendor logs, 4.5.6
disk failures
protection from, 4.3.2
restoring redundancy after, 4.3.2.2
disk groups
checking with V$ASM_DISK_IOSTAT view, 4.5.5
configuration, 4.3.1
determining size of, 4.3.2.2, 4.3.4
failure of fast recovery area, 13.2.5.4
imbalanced, 4.5.5
mounting, 4.5.3
offline after failures, 13.2.5.4
SYSASM access to Oracle ASM instances, 4.5.1
disk multipathing, 4.4.1
DISK_ASYNCH_IO initialization parameter, 5.1.7, 9.3.8.6
DISK_REPAIR_TIME parameter, 4.4.5
disks
Oracle ASM failures, 13.2.5.2, 13.2.5.2
distributed databases
recovering, 13.2.8
DNS failover, 13.2.1.3
dropped tablespace
fix using Flashback Database, 13.2.7.3
dropping database objects, 13.2.7.1
dual failures
restoring, 13.3.7
DWDM
Dense Wavelength Division Multiplexing., 7.1.4

E

edition-based redefinition, 10.1.4, 14.2.8
ENABLE BLOCK CHANGE TRACKING, 8.2.4
endian format
determining, 14.2.7.3
Enterprise Manager
alerts, 12.2.1
Beacon
application failover, 13.2.4
Database Targets page, 12.2.3
High Availability Console (HA Console), 12.3.3
home page, 12.2.1
MAA Advisor, 12.3.4
managing Data Guard targets, 12.3.3
managing patches, 12.3.2
metrics, 12.2.1
notification rules, 12.2.2, 12.2.3
performance, 12.2.3
policy violations, 12.3.1
Policy Violations, 12.3.1
Support Workbench, 12.2.2
Enterprise Manager monitoring, 12.2
equations
standby redo log files, 9.3.6
Estimated Failover Time
event in Enterprise Manager, 12.2.4
Exadata Database Machine
and MAA best practices, 2.11
HARD, 4.6.1
extended clusters
overview, 7.3
setting the ASM_PREFERRED_READ_FAILURE_GROUPS parameter, 7.3.4
extents
Oracle ASM mirrored, 5.1.6.1, 5.1.6.1
external redundancy
Oracle ASM disk failures, 13.2.5.2
Oracle ASM server-based mirroring, 7.3.4
EXTERNAL REDUNDANCY clause
on the CREATE DISKGROUP statement, 4.3.2.1
Extraction, Transformation, and Loading (ETL)
application workload, 4.1

F

failovers
application, 13.2.4
comparing manual and fast-start failover, 9.4.2.1
complete site, 13.2.1
defined, 13.2.2
described, 13.2.2.2
effect on network routes, 13.2.1.3
Fast Application Notification (FAN), 9.3.1
Fast Connection Failover, 11.5
manual
best practices, 9.4.2.4
when to perform, 9.4.2.1, 13.2.2.1
nondisruptive, 4.4.1
restoring standby databases after, 13.3.2
failure detection
CRS response, 13.2.3.2
failure groups
ASM redundancy, 4.3.5
defining, 4.3.2.2
multiple disk failures, 13.2.5.4
specifying in an extended cluster, 7.3.4
failures
rebalancing Oracle ASM disks, 13.2.5.2
space allocation, 5.2.9
Fast Application Notification (FAN), 6.1.1.2, 13.2.4
after failovers, 9.3.1
Fast Connection Failover, 11.5
fast local restart
after fast recovery area disk group failure, 13.2.5.4.1
fast recovery area
backups, 8.4.3
contents, 4.3.1
disk group failures, 13.2.5.4
disk partitioning, 4.3.1
local recovery steps, 13.2.5.4.3
using, 5.1.3
FAST_START_MTTR_TARGET initialization parameter, 5.1.10, 7.1.1
controlling instance recovery time, 5.1.5
setting in a single-instance environment, 7.1.1
FAST_START_PARALLEL_ROLLBACK initialization parameter
determining how many processes are used for transaction recovery, 7.1.2
fast-start failover
comparing to manual failover, 9.4.2.1
fast-start fault recovery
instance recovery, 5.1.5
FastStartFailoverAutoReinstate configuration property, 13.3.2
fault tolerance
configuring storage subsystems, 4
restoring, 13.3
restoring after OPEN RESETLOGS, 13.3.6
flash recovery area
See fast recovery area, 12.3.3
Flashback Database, 13.2.7, 13.2.7.3
enabling, 5.1.4, 5.1.4
in Data Guard configurations, 9.3.3
setting maximum memory, 5.1.8
Flashback Drop, 13.2.7, 13.2.7.1
flashback logs
fast recovery area disk group failure, 13.2.5.4
Flashback Query, 13.2.7, 13.2.7.2
Flashback Table, 13.2.7, 13.2.7.1
flashback technology
example, 13.2.7.2
recovering from user error, 13.2.7
resolving database-wide inconsistencies, 13.2.7.3
resolving tablespace inconsistencies, 13.2.7.4
solutions, 13.2.7
Flashback Transaction, 13.2.7
DBMS_FLASHBACK.TRANSACTION_BACKOUT PL/SQL procedure, 13.2.7.1
Flashback Transaction Query, 13.2.7, 13.2.7.2
Flashback Version Query, 13.2.7, 13.2.7.2
FORCE LOGGING mode, 5.1.1, 9.3.4
full data file copy, 8.3
full or level 0 backup set, 8.3

G

gap resolution
compression, 9.3.7.2
GoldenGate (Oracle GoldenGate), 10
Grid Control (Oracle Grid Control)
monitoring, 12.2
guaranteed restore points, 8.1.4
GV$SYSSTAT view
gathering workload statistics, 4.1

H

HA (Oracle High Availability technologies), 1.3
HARD Hardware Assisted Resilient Data, 4.6.1
Hardware Assisted Resilient Data (HARD)
when using Oracle ASM, 4.3.5
hardware RAID storage subsystem
deferring mirroring to, 7.3.4
High Availability
(HA) Console
monitoring databases, 12.3.3
described, 1.1
restoring after fast-start failover, 13.3.2
high redundancy
Automatic Storage Management (Oracle ASM)
disk groups, 4.3.2.2
Oracle ASM disk failures, 13.2.5.2
Oracle ASM disk groups, 4.3.1
host bus adapters (HBA)
load balancing across, 4.4.1
HR service
scenarios, 13.3.1.1
human errors
recovery, 13.2.7

I

imbalanced disk groups
checking, 4.5.5
incremental backups
BLOCK CHANGE TRACKING, 8.2.4
incrementally updated backup, 8.3
initialization parameters
primary and physical standby example, 9.3.5
instance failures
recovery, 5.1.5
single, 13.2.3.1
instance recovery
controlling with fast-start fault recovery, 5.1.5
interconnect subnet
verifying, 6.2.9
interim patches, 14.2.2
I/O operations
load balancing, 4.4.1
tuning, 9.3.8.6

K

KEEP IDENTITY clause, 14.2.6.2.2
KEEP option
RMAN BACKUP command, 8.2.1

L

library
ASMLib support for Oracle ASM, 4.4.6
listener connection rate throttling, 11.5
listeners
balancing clients across, 6.2.6
Connection Rate Limiter, 11.5
load balancing
application services, 13.3.1.3
client connections, 6.2.6
I/O operations, 4.4.1
through disk multipathing, 4.4.1
LOAD_BALANCE parameter, 6.2.6, 11.1
balancing client connections, 6.2.6
local homes
use during rolling patches, 6.2.2
local recovery
after fast recovery area disk group failure, 13.2.5.4.1
for data area disk group failures, 13.2.5.3
for fast recovery area disk group failures, 13.2.5.4.3
locally managed tablespaces, 5.2.6
described, 5.2.6
log apply services
best practices, 9.3.8
LOG_ARCHIVE_DEST_n initialization parameter, 9.3.9
LOG_ARCHIVE_FORMAT initialization parameter, 9.3.5
LOG_ARCHIVE_MAX_PROCESSES initialization parameter, 9.3.7.1
setting in a multiple standby environment, 9.3.7.1
setting in an Oracle RAC, 9.3.7.1
LOG_BUFFER initialization parameter, 5.1.4, 5.1.8
LOG_FILE_NAME_CONVERT initialization parameter, 9.4.1, 9.4.2.2
logical standby databases
failover, 13.2.2.3
switchover, 14.2.1.3
upgrades on, 14.2.6.2
logical unit numbers (LUNs), 4.3.2.1
defined, Glossary
login storms
controlling with shared server, 11.5
preventing, 11.5
low bandwidth networks
compression on, 9.3.7.2
low-cost storage subsystems, 4.1
LUNs
See Also logical unit numbers (LUNs)
See logical unit numbers (LUNs), 4.3.2.1

M

MAA
See Oracle Maximum Availability Architecture (MAA)
manageability
improving, 5.2
managing scheduled outages, 14.1.1, 14.1.2
manual failover
best practices, 9.4.2.4, 13.2.2.3
comparing to fast-start failover, 9.4.2.1
when to perform, 9.4.2.1, 13.2.2.1
Maximum Availability Architecture (MAA) Advisor page, 12.3.4
maximum availability mode
redo transport requirements, 9.2.2
maximum number of connections
adjusting in the mid tier connection pool, 11.5
maximum performance mode
redo transport requirements, 9.2.2
maximum protection mode
initialization parameter example, 9.3.5
Mean Time To Recover (MTTR)
checkpointing, 7.1.1
reducing with Data Recovery Advisor, 5.2.2
memory consumption
managing with MEMORY_TARGET parameter, 4.4.2
memory management, 5.1.9
MEMORY_TARGET initialization parameter, 4.4.2
metrics
Enterprise Manager, 12.2.1
for Data Guard in Enterprise Manager, 12.2.4
mid tier connection pool
adjusting maximum number of connections, 11.5
migrating
planning for, 14.2.7
transportable database, 14.2.7.5
migration planning, 14.2.7.2
migration strategy
scheduled outages, 14.2.7.1
minimizing space usage, 8.3
minimizing system resource consumption, 8.3
mining vendor logs for disk errors, 4.5.6
mirrored extents
protection from data corruptions, 5.1.6.1, 5.1.6.1
mirroring
across storage arrays, 4.3.2.2
deferring to RAID storage subsystem, 7.3.4
monitoring
application response time, 13.2.4
Enterprise Manager, 12.2
Oracle Grid Control, 12.2
rebalance operations, 14.2.5.2.2
mounting disk groups, 4.5.3
multipathing (disks)
path abstraction, 4.4.1
multiple disk failures, 13.2.5.4

N

net services parameter
DEFAULT_SDU_SIZE, 9.3.7.2
RECV_BUF_SIZE, 9.3.7.2
SEND_BUF_SIZE, 9.3.7.2
TCP.NODELAY, 9.3.7.2
Network Attached Storage (NAS), 9.3.8.6
network detection and failover
Oracle Clusterware and Oracle RAC, 6.2.9
network routes
after site failover, 13.2.1.3
before site failover, 13.2.1.3
network server processes (LNSn), Glossary
Network Time Protocol (NTP), 6.2.8
NOCATALOG Mode
creating backups, 8.2.3
node failures
multiple, 13.2.3.1
nodes
migrating client connections, 6.1.1
nondisruptive failovers, 4.4.1
normal redundancy
Oracle ASM disk failures, 13.2.5.2
NORMAL REDUNDANCY clause
on the CREATE DISKGROUP statement, 4.3.2.2
notification rules
recommended, 12.2.3
service-level requirement influence on monitoring, 12.2.2
notifications
application failover, 13.2.4
NTP, 6.2.8

O

OCI_EVENTS parameter, 11.1
OCR
backups of, 6.3.2
failure of, 13.2.3.3
recovering, 13.2.3.3
ocrconfig -showbackup command, 6.3.2
OMF
See Oracle Managed Files
online patching, 14.2.2
online redo log files
multiplex, 5.1.2
Online Reorganization and Redefinition, 14.2.10
Online Transaction Processing (OLTP)
application workload, 4.1
opatch command-line utility, 14.2.4
optimizing
recovering times, 8.3
Oracle ACFS snapshot, 8.6.1
Oracle ASM
See Oracle Automatic Storage Management (Oracle ASM), 4.2
Oracle Auto Service Request (ASR), 2.10.2
Oracle Automatic Storage Management (Oracle ASM)
ASM_DISKSTRING parameter, 4.4.1
ASMLib, 4.4.6
clustering to enable the storage grid, 4.2.1
configuring with ASMCA, 4.5.8
database file management, 4.2
disk device allocation, 4.3.1
disk failures, 13.2.5.2, 13.2.5.2
disk group size, 4.3.2.2, 4.3.4
failure groups, 7.3.4
failure groups and redundancy, 4.3.5
handling disk errors, 4.5.6
HARD-compliant storage, 4.3.5
imbalanced disk groups, 4.5.5
managing memory with MEMORY_TARGET parameter, 4.4.2
managing with ASMCMD, 4.5.7
migrating databases to and from, 14.2.5.2.1
multiple disk failures, 13.2.5.4
Oracle Restart, 4.2.2
power limit for faster rebalancing, 4.6.2
REBALANCE POWER, 4.5.2
rebalancing, 4.5.4
rebalancing disks after a failure, 13.2.5.2
recovery, 13.2.5
redundancy, 4.3.2.2, 5.1.6.1, 5.1.6.1
rolling upgrade, 14.2.5.2.3
server-based mirroring, 7.3.4
SYSASM role, 4.5.1, 4.5.1
using disk labels, 4.4.4
using normal or high redundancy, 4.3.2.2, 7.3.4
volume manager, 7.3.4
with disk multipathing software, 4.4.1
Oracle Cluster Registry (OCR)
failure of, 13.2.3.3
Oracle Clusterware
capacity planning, 6.3.1
CTSS time management, 6.2.8
system maintenance, 14.2.11
verifying the interconnect subnet, 6.2.9
Oracle Data Guard
See Data Guard, 9
Oracle Data Pump
for platform migration, 14.2.7.7
platform migrations, 14.2.7.7
Oracle Database 11g
configuration recommendations, 5
Data Guard, 9
extended cluster configurations, 7.3
Oracle RAC configuration recommendations, 7.1
Oracle Enterprise Manager
High Availability (HA) Console, 12.3.3
MAA Advisor page, 12.3.4
Oracle Flashback Database
restoring fault tolerance to configuration, 13.3.2
Oracle GoldenGate
and Oracle RAC, 10.1.2
best practices, 10
configuring, 10
database migration, 14.2.7.6
for database upgrades, 14.2.6.3
overview, 10
replicat commit, 10.2.3
replicat COMMIT NOWAIT, 10.2.3
upgrades using, 14.2.6.3
with Oracle Data Guard, 10.1.3
Oracle Grid Control
home page, 12.2.1
monitoring, 12.2
Oracle High Availability technologies, 1.3
Oracle Managed Files (OMF)
database file management, 4.3.1
disk and disk group configuration, 4.3.1
fast recovery area, 5.1.3
Oracle Management Agent, 12.2
monitoring targets, 12.2
Oracle Maximum Availability Architecture (MAA)
defined, Glossary
described, 1.3
website, 1.3
Oracle Notification Service (ONS)
after failovers, 9.3.1
Oracle RAC rolling patch upgrades, 14.2.4
Oracle Real Application Clusters (Oracle RAC)
adding disks to nodes, 4.4.6
application failover, 13.2.4
configuration, 7.1
extended clusters, 7.3
network detection and failover, 6.2.9
preparing for switchovers, 9.4.1
recovery from unscheduled outages, 13.2.3
restoring failed nodes or instances, 13.3.1
rolling upgrade, 14.2.4
rolling upgrades, 14.2.4
setting LOG_ARCHIVE_MAX_PROCESSES initialization parameter, 9.3.7.1
system maintenance, 14.2.11
using redundant dedicated connections, 7.1.4
verifying the interconnect subnet, 6.2.9
voting disk, 6.2.7, 7.3.2, 13.2.3.3
Oracle Restart, 4.2.2, 5.2.1
Oracle Secure Backup, 8.1.3
OCR backups, 6.3.2
Oracle Storage Grid, 4.6
Oracle Streams
and Oracle GoldenGate, 10.1.1
Oracle Sun SFS Storage Appliance, 8.6.2
Oracle Universal Installer, 14.2.4.2
outages
unscheduled, 13.1

P

parallel recovery
disabling, 5.1.10
PARALLEL_EXECUTION_MESSAGE_SIZE parameter, 5.1.4
partitions
allocating disks for Oracle ASM use, 4.3.1
patch sets
rolling upgrades, 14.2.4
patches
managing with Enterprise Manager, 12.3.2
rolling, 6.2.2
using shared cluster file system, 6.2.2
path failures
protection from, 4.4.1
performance
application, tracking with Beacon, 12.2.2
asynchronous disk I/O, 5.1.7
automatic tuning, 5.2.3
Data Guard, 9.7
database, gathering requirements, 4.1
physical standby databases
as snapshot standby databases, 9.6
failover, 13.2.2.3
location migrations, 14.2.7.9
real-time query, 9.5
switchover, 14.2.1.3
platform migrations, 14.2.6
endian format for, 14.2.7.3
with physical standby database, 14.2.7.4
point-in-time recovery
TSPITR, 13.2.7.4
pool
resizing, 5.1.9
power limit
setting for rebalancing, 4.6.2
preferred read failure groups
specifying Oracle ASM, 7.3.4
preventing login storms, 11.5
primary database
reinstating after a fast-start failover, 13.3.2
restoring fault tolerance, 13.3.6
PROCESSES initialization parameter, 4.4.3

Q

quorum disk
voting disk, 7.3.2

R

RAID protection, 4.3.2.1
real-time apply
configuring for switchover, 9.4.1
real-time query
Active Data Guard option, 9.5
rebalance operations, 4.5.2
monitoring, 14.2.5.2.2
Oracle ASM disk partitions, 4.3.1, 4.3.1
REBALANCE POWER
limits, 4.5.2
rebalancing, 4.5.4
Oracle ASM disk groups, 4.5.2, 4.5.5
Oracle ASM disks after failure, 13.2.5.2
setting Oracle ASM power limit, 4.6.2
recommendations
database configuration, 5
recovery
coordinated, time-based, distributed database recovery, 13.2.8
options for fast recovery area, 13.2.5.4
steps for unscheduled outages, 13.1.1
testing procedures, 8.5.3
times optimizing, 8.3
recovery catalog
including in regular backups, 8.5.4
RMAN repository, 8.2.2
recovery files
created in the recovery area location, 5.1.3
Recovery Manager
See Also RMAN
recovery point objective (RPO)
criticality of data, 8.2.1
defined, Glossary
for data area disk group failures, 13.2.5.3
solutions for disk group failures, 13.2.5.4
recovery time objective (RTO)
defined, Glossary
described, 13.2.1.2
for data-area disk group failures, 13.2.5.3
recovery time, 8.2.1
solutions for disk group failures, 13.2.5.4
RECOVERY_ESTIMATED_IOS initialization parameter
for parallel recovery, 5.1.10
RECOVERY_PARALLELISM initialization parameter, 5.1.10, 5.1.10
RECV_BUF_SIZE sqlnet.ora parameter, 9.3.7.2
recycle bin, 13.2.7.1
Redo Apply
real-time query, 9.5
Redo Apply Rate
event in Enterprise Manager, 12.2.4
redo data
compressing, 9.3.7.2
redo log members
fast recovery area disk group failure, 13.2.5.4
redo transport services
best practices, 9.2.1
redundancy
Automatic Storage Management (Oracle ASM), 4.3.2.2
CREATE DISKGROUP DATA statement, 4.3.2.1
dedicated connections, 7.1.4
disk devices, 4.3.2
restoring after disk failures, 4.3.2.2
reinstatement, 13.3.2
FastStartFailoverAutoReinstate property, 13.3.2
remote archiving, 9.3.5
REMOTE_LISTENER parameter, 6.2.5, 6.2.6
resetlogs on primary database
restoring standby database, 13.3.6
resource consumption
minimizing, 8.3
resource management
using Database Resource Manager, 5.2.10
response times
detecting slowdown, 13.2.4
restore points, 8.1.4
restoring
client connections, 13.3.1.3
failed instances, 13.3.1
failed nodes, 13.3.1
services, 13.3.1.1
resumable space allocation, 5.2.9, 5.2.9
RESUMABLE_TIMEOUT initialization parameter, 5.2.9
RESYNC CATALOG command
resynchronize backup information, 8.2.3
RETENTION GUARANTEE clause, 5.2.5, 5.2.5, 8.2.7
retention policy for backups, 8.2.1
RMAN
backup undo optimization, 8.1.3
BACKUP VALIDATE command, 9.3.8.3
calculates checksums, 5.1.6.1
creating standby databases, 9.3.2
database backups, 8.1.2
DUPLICATE command, 8.5.3
DUPLICATE TARGET DATABASE FOR STANDBY command, 9.3.2
FROM ACTIVE DATABASE command, 9.3.2
recovery catalog, 8.2.2
TSPITR, 13.2.7.4
unused block compression, 8.1.3
VALIDATE command, 8.5.2
RMAN BACKUP command
KEEP option, 8.2.1
role transitions
best practices, 9.4.2.4
role-based destinations, 9.3.5
rolling patches, 6.2.2
rolling upgrade
Oracle RAC, 14.2.4
rolling upgrades
patch set, 14.2.4
row and transaction inconsistencies, 13.2.7.2
RPO
See recovery point objective (RPO)
RTO
See recovery time objective (RPO)

S

SALES scenarios
setting initialization parameters, 9.3.5
SAME
See stripe and mirror everything (SAME)
scenarios
fast-start failover, 13.3.2.1
HR service, 13.3.1.1
object reorganization, 14.2.10
Oracle ASM disk failure and repair, 13.2.5.2.1
recovering from human error, 13.2.7.2
SALES, 9.3.5
scheduled outages
Data Guard standby-first patch apply, 14.2.3
described, 14.1
edition-based redefinition, 14.2.8
migration, 14.2.7
migration planning, 14.2.7.2
migration strategy, 14.2.7.1
online patching, 14.2.2
Oracle ASM
rolling upgrade, 14.2.5.2.3
Oracle Real Application Clusters (Oracle RAC) rolling patch upgrades, 14.2.4
platform migration, 14.2.7.4
primary site, 14.1.1
recommended solutions, 14.1.1, 14.1.2
reducing downtime for, 14.2
secondary site, 14.1.2
switchback, 14.2.1
switchover, 14.2.1
transportable tablespaces upgrades, 14.2.6.4
upgrades with Oracle GoldenGate, 14.2.6.3
See Also unscheduled outages
secondary site outage
restoring the standby database after, 13.3.4
SEND_BUF_SIZE sqlnet.ora parameter, 9.3.7.2
server parameter file (SPFILE), 5.2.4, 9.3.5
backup with RMAN, 8.2.5
server-based mirroring
Oracle ASM, 7.3.4
service availability
recovering, 13.3.1.1
service level agreements (SLA), 1.3
effect on monitoring and notification, 12.2.2
service tests and Beacons
configuring, 12.2.2
SERVICE_TIME
service-level goal, 6.2.6
services
and FAN, 6.1.1.1
automatic relocation, 13.2.3.2
definition of, 6.1.1.1
making highly available, 6.2.3
Oracle RAC application failover, 13.2.4
Oracle RAC application workloads, 6.2.5
relocation after application failover, 13.2.4
tools for administration, 6.2.5
SGA_TARGET initialization parameter, 5.1.9
shared server
configuring Oracle Database, 11.5
site failover
network routes, 13.2.1.3
SMON process
in a surviving instance, 7.1.1
sort operations
improving, 5.2.8
space management, 5.2.7
space usage
minimizing, 8.3
SQL Access Advisor, 5.2.3
SQL Apply, 14.2.6.2
SQL Tuning Advisor, 5.2.3
SRVCTL
Oracle Restart, 4.2.2
standby databases
configuring multiple, 9.3.9
creating, 9.3.2
restoring, 13.3.2
standby redo log files
determining number of, 9.3.6
standby-first patch apply (Data Guard), 14.2.3
STATISTICS_LEVEL initialization parameter, 9.7
Statspack
assessing database waits, 9.3.8.5
storage
mirroring to RAID, 7.3.4
storage appliance, 8.6.2
Storage Area Network (SAN), 9.3.8.6
storage arrays
mirroring across, 4.3.2.2
multiple disk failures in, 13.2.5.4
storage grid
through clustered Oracle ASM, 4.2.1
storage subsystems, 4
configuring Oracle ASM, 4.2
configuring redundancy, 4.3.2
performance requirements, 4.1
stripe and mirror everything (SAME), 4.2
Support Workbench, 12.2.2
switchovers
configuring real-time apply, 9.4.1
described, 14.2.1.1
in Oracle RAC, 9.4.1
reducing archiver (ARCn) processes, 9.4.1
See Also Data Guard
setting the LOG_FILE_NAME_CONVERT initialization parameter, 9.4.1
to a logical standby database, 14.2.1.3
to a physical standby database, 14.2.1.3
SYSASM role
Oracle ASM Authentication, 4.5.1
system failure
recovery, 5.1.5
system maintenance, 14.2.11
system resources
assessing, 9.3.8.7
SYSTEM tablespace
moving the contents of, 14.2.7.8

T

table inconsistencies, 13.2.7.1
tablespace point-in-time recovery (TSPITR), 13.2.7.4
tablespaces
locally managed, 5.2.6
resolving inconsistencies, 13.2.7.4
temporary, 5.2.8, 5.2.8
targets
in Enterprise Manager, 12.2
monitoring, 12.2
TCP Nagle algorithm
disabling, 9.3.7.2
TCP.NODELAY sqlnet.ora parameter, 9.3.7.2
temporary tablespaces, 5.2.8, 5.2.8
THROUGHPUT
service-level goal, 6.2.6
transaction recovery
determining how many processes are used, 7.1.2
transient logical standby database
rolling upgrade, 14.2.6.2.2
Transport Lag
event in Enterprise Manager, 12.2.4
transportable database, 14.2.7.5
transportable tablespaces
database upgrades, 14.2.6.4
platform migration, 14.2.7.8

U

undo retention
tuning, 5.2.5
undo space
managing, 5.2.5
UNDO_MANAGEMENT initialization parameter, 8.2.7
automatic undo management, 5.2.5
UNDO_RETENTION initialization parameter, 8.2.7
automatic undo management, 5.2.5
UNDO_TABLESPACE initialization parameter
automatic undo management, 5.2.5
unscheduled outages
Data Guard switchover, 14.2.1.3
described, 13.1
Oracle RAC recovery, 13.2.3
recovery from, 13.1.1, 13.2
types, 13.1
See Also scheduled outages
unused block compression, 8.1.3
upgrades
application, 14.2.9
applying interim patches, 14.2.2
best practices, 14.2.4.1
Database Upgrade Assistant (DBUA), 14.2.6.1
methods, 14.2.6
online patching, 14.2.2
Oracle RAC rolling
best practices, 14.2.4.2
USABLE_FILE_MB column
on the V$ASM_DISKGROUP view, 4.3.2.2
user error
flashback technology, 13.2.7

V

V$ASM_DISK view, 9.3.8.7
V$ASM_DISK_IOSTAT view
checking disk group imbalance, 4.5.5
V$ASM_DISKGROUP view
REQUIRED_MIRROR_FREE_MB column, 4.3.2.2
USABLE_FILE_MB column, 4.3.2.2
V$ASM_OPERATION view
monitoring rebalance operations, 14.2.5.2.2
V$EVENT_HISTOGRAM view, 9.3.8.5
V$INSTANCE_RECOVERY view
tuning recovery processes, 5.1.10
V$IOSTAT_FILE view
asynchronous I/O, 5.1.7
V$OSSTAT view, 9.3.8.7, 9.7
V$SESSION_WAIT view, 9.3.8.5
V$SYSMETRIC_HISTORY view, 9.7
V$SYSMETRIC_SUMMARY view, 9.7
V$SYSTEM_EVENT view, 9.3.8.5, 9.3.8.7
VALID_FOR attribute, 9.3.5
VALIDATE option
on the RMAN BACKUP command, 9.3.8.3
validation
checksums during RMAN backup, 5.1.6.1
verifying the interconnect subnet, 6.2.9
VIP address
connecting to applications, 6.2.5
described, 6.2.5
during recovery, 13.3.1.1
Virtual Internet Protocol (VIP) Address
See VIP address
volume manager
Oracle ASM, 7.3.4
voting disk (Oracle RAC)
best practices, 6.2.7
corrupted, 13.2.3.3
quorum disk, 7.3.2

W

wait events
assessing with Active Data Guard and Statspack, 9.3.8.5
websites
ASMLib, 4.4.6
MAA, 1.3
workloads
examples, 4.1
gathering statistics, 4.1

Z

ZFS storage appliance, 8.6.2