Index

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

A

Active Data Guard option, 2.1.3.1, 2.3.4.1
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.5
architectures
extended Oracle RAC, 4.1.4
Oracle Application Server, 4.3.1
recommendations, 4.2
single-instance Oracle Database (noncluster), 4.1.1
automatic failover
Oracle Data Guard, 4.1.5.1
automatic maintenance tasks, 2.4.1
Automatic Storage Management (ASM)
description, 2.1.6
Fast Mirror Resync, 2.1.6
storage migration, 2.2.2.7
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.5
backups
Oracle Secure Backup, 2.1.8
block recovery
using Flashback logs, 2.1.5

C

Cluster Ready Services (CRS)
avoiding downtime during upgrades, 2.2.2.5
clusters
extended, 4.1.4
cold failover cluster, 4.1.6
described, 4.1.2
Oracle Clusterware and Data Guard, 4.1.6
with Oracle Clusterware, 4.1.2
computer failure, 1.4
corruptions
prevention and detection, 2.1.14

D

data corruptions, 1.4
detecting, 2.1.14
prevention and detection parameters, 2.1.14
Data Guard
benefits, 2.1.3
comparing to Streams, 2.1.4
hub architecture, 4.1.5.2
Data Recovery Advisor, 2.1.9
data type restrictions
resolving with Extended Datatype Support (EDS), 2.2.2.8.1, 2.2.2.8.3
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
using transportable tablespaces, 2.2.2.8.2
databases
applying Oracle interim patches, 2.2.2.3
server grid, 2.3.1
DB_BLOCK_CHECKING initialization parameter, 2.1.14
DB_BLOCK_CHECKSUM initialization parameter, 2.1.14
DB_LOST_WRITE_PROTECT initialization parameter, 2.1.14
DB_ULTRA_SAFE initialization parameter, 2.1.14
DBA_FLASHBACK_TRANSACTION_STATE view, 2.1.5
DBMS_FLASHBACK.TRANSACTION_BACKOUT() procedure, 2.1.5
downtime
causes, 1.4
cost, 3.2.2

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 clusters
architecture, 4.1.4
overview, 4.1.4

F

failovers
fast-start, 4.1.5.1
multiple standby databases
architecture, 4.1.5.2
single standby database architecture, 4.1.5.1
failures
computer, 1.4
probability, 4.2
site, 1.4
storage, 1.4
Fast Mirror Resync
ASM, 2.1.6
fast-start failovers
single standby database failover, 4.1.5.1
Fast-Start Fault Recovery
benefits of using, 2.1.1
fault diagnosability infrastructure, 2.4.1
flash recovery area
description, 2.1.10
Flashback Data Archive, 2.1.5
Flashback Database
description, 2.1.5
Flashback Drop
description, 2.1.5
flashback logs
used by Flashback features, 2.1.5
Flashback Query
description, 2.1.5
Flashback Restore Points
description, 2.1.5
Flashback Table
description, 2.1.5
Flashback technologies
block recovery using Flashback logs, 2.1.5
Flashback technology
block recovery using Flashback logs, 2.1.5
Flashback Transaction
description, 2.1.5
Flashback Transaction Query
description, 2.1.5
Flashback Versions Query
description, 2.1.5
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 or slow down, 1.4
HARD initiative, 2.1.13
Hardware Assisted Resilient Data (HARD) initiative, 2.1.13
hardware upgrades
avoiding downtime during, 2.2.2.1
high availability
applications, 4.3.1
architecture, 1.2
architectures, 4.2
business impact analysis, 3.2.1
importance, 1.3
solutions, 1.2
hub-and-spoke configuration
Oracle Streams, 2.1.4
human errors, 1.4

I

intelligent infrastructure, 2.4.1
interblock corruption, 1.4
intrablock corruption, 1.4

L

logical corruption, 1.4
logical standby databases, 2.1.3.1
transient, 4.1.5.2
lost writes, 1.4

M

Manageability Overhead (MO), 4.2
Maximum Availability Architecture
benefits, 4.1.7
media corruption
physical corruption, 1.4
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
multiple standby databases
Data Guard hub, 4.1.5.2
failovers, 4.1.5.2
using transient logical standby, 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.5
online maintenance
application, 2.2.5
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
avoiding downtime when upgrading, 2.2.2.5
cold failover cluster, 4.1.2, 4.1.2
configured with Data Guard, 4.1.6
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 cluster, 4.1.4
with Data Guard architecture, 4.1.5
with Oracle Clusterware (cold failover cluster), 4.1.2
with Oracle RAC and Data Guard - MAA, 4.1.7
with Oracle RAC architecture, 4.1.3
with Streams architecture, 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 Real Application Clusters (Oracle RAC)
benefits, 2.1.2.1
extended clusters, 4.1.4
Storage Area Network (SAN), 4.1.4
Oracle Secure Backup
overview, 2.1.8
Oracle Streams
1-N or hub-and-spoke configuration, 2.1.4
comparing to Data Guard, 2.1.4
description, 2.1.4
performing database upgrades, 2.2.2.8
performing platform migrations, 2.2.2.8
outages
frequency, 4.2

P

physical corruption
media corruption, 1.4
physical standby databases, 2.1.3.1
real-time query, 2.3.4.1
planned activities
probability of failure during, 4.2
platform migrations
using Oracle Streams, 2.2.2.8
using transportable database, 2.2.2.9.1
probability
of different failures during unplanned and planned activities, 4.2
program global area (PGA)
automatic management, 2.2.1.2

R

Recovery Manager (RMAN)
description, 2.1.7
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.5
Return On Investment (ROI), 4.2
rollback
transactions, 2.1.5
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
servers
Oracle Clusterware requirements, 4.1.2
service level agreements (SLAs), 3.3
single standby database architecture
failovers, 4.1.5.1
site failure, 1.4
SLAs, 3.3
snapshot standby database, 2.1.3.1
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 databases
Active Data Guard option, 2.1.3.1, 2.3.4.1
example hub configurations, 4.1.5.2
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
ASM protection, 2.1.6
failures, 1.4
grid, 2.3.1
migration, 2.2.2.7
Storage Area Network (SAN)
extended clusters, 4.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 Oracle Secure Backup, 2.1.8
thin client watchdog
observer for fast-start failover, 4.1.5.1
Total Cost of Ownership (TCO), 4.2
transactions
backing out with Flashback Transaction, 2.1.5
transportable database
for platform migration, 2.2.2.9.1
for unplanned downtime, 2.2.4
transportable tablespaces
for unplanned downtime, 2.2.4
upgrading the database, 2.2.2.8.2
transportable technologies
for unplanned downtime, 2.2.4

U

Undo Advisor, 2.4.1
undo data
used by flashback features, 2.1.5
unplanned activities
probability of failure during, 4.2
unplanned downtime
transportable tablespaces, 2.2.4
transportable technologies, 2.2.4
upgrades
application, 2.2.5
database, 2.2.2.8
Oracle Clusterware, 2.2.2.5
using transportable tablespaces, 2.2.2.8.2
with logical standby databases, 4.1.5.2

V

V$DATABASE_BLOCK_CORRUPTION view, 2.1.14
virtual IP address
defining for applications, 4.1.2
Oracle Clusterware, 4.1.2

W

Web scaleability
using standby reader farms, 2.3.4.2