Index

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

Numerics

24x365, 1.1

A

access control

security, 3.13

Active Data Guard option, 3.5.1, 5.4.1

Active Session History (ASH)

reporting on transient performance problems, 6.1

ADD COLUMN

default values for columns, 4.5.5

advisor framework, 6.1

ALTER DATABASE RECOVER MANAGED STANDBY statement

enabling real-time query, 5.4.1

analysis

determining high availability requirements, 2

applications

defining a virtual IP address, 7.1.2

online maintenance and upgrades, 4.5

architectures

extended Oracle RAC, 7.1.4

Oracle Application Server, 7.3.1

recommendations, 7.2

single-instance Oracle Database (noncluster), 7.1.1

auditing

security control, 3.13

authentication

security controls, 3.13

Automatic block repair, 3.7.9

automatic block repair, 3.18

automatic failover

Oracle Data Guard, 7.1.5.1

automatic maintenance tasks, 6.1

automatic shared memory management

dynamic memory allocation, 4.2.1

Automatic Storage Management Cluster File System (ACFS), 7.1.1

Automatic Storage Management File Systems (ASMFS), 3.8

Automatic Workload Repository (AWR), 6.1

availability

in nonclustered environments, 3.3

B

backing out a transaction, 3.7.3

backups

fast recovery area, 3.9

offload from the primary database, 3.5.1

Oracle Secure Backup, 3.12

between objects, 4.5.6

block corruption

repairing, 3.18

block recovery

using Flashback logs, 3.7.9

block recovery time

reducing, 3.18

bounded recovery

fast-start fault recovery, 3.2

budget planning, 2.3.1

business impact analysis

internal knowledge management system example, 2.2.1

semiconductor manufacturer example, 2.2.1

business performance planning, 2.3.1

C

checkpointing

fast-start fault recovery, 3.2

client failover, 3.17

Cluster Ready Services (CRS)

avoiding downtime during upgrades, 4.1.5

clusters

extended, 7.1.4

cold cluster failover, 7.1.2, 7.1.6

Oracle Clusterware and Data Guard, 7.1.6

cold failover cluster

described, 7.1.2

with Oracle Clusterware, 7.1.2

components

integrated with Oracle Restart, 3.3

compressed redo data

Oracle Data Guard, 7.1.5

computer failure, 1.4

corruptions

prevention and detection, 3.19

repairing, 3.18

costs

quantifying, 2.2.2

CREATE TRIGGER statement

clauses for, 4.5.4

crossedition triggers, 4.5.1.3

D

data block corruption

automatic detection and repair, 3.18

data corruptions, 1.4

detecting, 3.19

prevention and detection parameters, 3.19

data encryption, 3.13

Data Guard

benefits, 3.5

comparing to Oracle Streams, 3.6

hub architecture, 7.1.5.3

data protection

maximizing, 1.2

Data Recovery Advisor, 3.11

data type restrictions

resolving with Extended Datatype Support (EDS), 4.1.10.1, 4.1.10.3

database

applying interim database patches, 4.1.3

Database Replay, 6.2

Database Server Grid, 5.1

description, 5.2

Database Storage Grid, 5.1

description, 5.3

database upgrades

using Oracle Streams, 4.1.10

using transportable tablespaces, 4.1.10.2

databases

applying Oracle interim patches, 4.1.3

checkpointing, 3.2

dynamic reconfiguration, 4.2.1

security, 3.13

security auditing, 3.13

security of, 3.13

server grid, 5.1

data-loss tolerance, 2.2.4

DB_BLOCK_CHECKING initialization parameter, 3.19

DB_BLOCK_CHECKSUM initialization parameter, 3.19

DB_LOST_WRITE_PROTECT initialization parameter, 3.19

DB_ULTRA_SAFE initialization parameter, 3.19

DBA_FLASHBACK_TRANSACTION_STATE view, 3.7.3

DBFS Content Store, 3.16

DBMS_FLASHBACK.TRANSACTION_BACKOUT() procedure, 3.7.3

DDL with the WAIT option, 4.5.3

dependencies, 4.5.6

DISABLE clause

FOLLOWS clause

CREATE TRIGGER statement, 4.5.4

disk group

administering with Oracle ASM, 3.8

downtime

causes, 1.4

cost, 2.2.2

planned, 4.1

unplanned, 3.1

downtime cost, 1.3

dynamic reconfiguration, 4.2.1

E

edition-based redefinition, 4.5.1

crossedition triggers, 4.5.1.3

editioning view, 4.5.1.2

editions, 4.5.1.1

editioning view, 4.5.1.2

editions, 4.5.1.1

ENABLE clause

CREATE TRIGGER statement, 4.5.4

encryption

of data, 3.13

endian format platforms

avoiding downtime during migration of different, 4.1.12

avoiding downtime during migration of same, 4.1.11

Exadata Cell, 3.15

EXCLUDE STANDBY option

of the RMAN RECOVER BLOCK command, 3.18

extended clusters

architecture, 7.1.4

overview, 7.1.4

F

failovers

fast-start, 7.1.5.1

multiple standby databases

architecture, 7.1.5.2

single standby database architecture, 7.1.5.1

failure group

administering with Oracle ASM, 3.8

Oracle ASM, 3.8

failures

computer, 1.4

probability, 7.2

site, 1.4

storage, 1.4

fast application notification (FAN)

for hardware upgrades, 4.1.1

for operating system upgrades, 4.1.1

Fast Connection Failover

for nonpooled connections, 3.4.2

Fast Mirror Resync

Oracle ASM, 3.8

fast recovery area

benefits, 3.9

description, 3.9

in a Data Guard configuration, 7.1.5

fast-start failovers

single standby database failover, 7.1.5.1

Fast-Start Fault Recovery

benefits of using, 3.2

fault diagnosability infrastructure, 6.1

flashback data archive, 3.7.10

Flashback Database

description, 3.7.8

Flashback Drop

description, 3.7.6

flashback logs

used by Flashback features, 3.7

Flashback Query

description, 3.7.1

Flashback Restore Points

description, 3.7.7

Flashback Table

description, 3.7.5

Flashback technologies

block recovery using Flashback logs, 3.7.9

Flashback technology

block recovery using Flashback logs, 3.7.9

Flashback Transaction

description, 3.7.3

Flashback Transaction Query

description, 3.7.4

Flashback Version Query

description, 3.7.2

forward crossedition triggers, 4.5.1.3

frequency of outages, 7.2

FUSE (Filesystem in Userspace) API

with Client for Database Filesystem (CDF), 3.16

G

grid computing, 5.1

Database Server Grid, 5.1

Database Storage Grid, 5.1

grids

server and storage, 5.1

growth planning, 2.3.1

H

hang or slow down, 1.4

HARD initiative, 3.19

Hardware Assisted Resilient Data (HARD) initiative, 3.19

hardware upgrades

avoiding downtime during, 4.1.1

using FAN during, 4.1.1

high availability, 1.1

24x365, 1.1

applications, 7.3.1

architecture, 1.1

architectures, 7.2

business impact analysis, 2.2.1

description, 1.1

determining requirements, 2

importance, 1.2

maximizing, 1.2

planned downtime, 4.1

planning, 2.3.1

setting manageability goals, 2.2.5

single-instance databases, 3.3

solutions, 1.1

high availability analysis framework, 2.1

high availability architectures, 2.2.5

hub-and-spoke configuration

Oracle Streams, 3.6

human errors, 1.4

I

indexes

invisible, 4.5.7

intelligent infrastructure, 6.1

interblock corruption, 1.4

intrablock corruption, 1.4

invisible indexes, 4.5.7

I/O Resource Management (IORM)

Oracle Storage Grid, 5.3

L

load balancing advisory, 3.4.2

logical corruption, 1.4

logical standby databases, 3.5.1

transient, 7.1.5.2

logical unit numbers (LUNs)

defined, Glossary

LogMiner

description, 3.14

lost writes, 1.4

LUNs

M

making data changes, 4.5.1.1

manageability goals, 2.2.5

manageability overhead, 2.2.5

Manageability Overhead (MO), 7.2

manual block repair, 3.18

materialized views

logging control, 4.5.8

Maximum Availability Architecture

benefits, 7.1.7

media corruption

physical corruption, 1.4

memory

automatic management of, 4.2.2

memory advisors, 6.1

MEMORY_MAX_TARGET initialization parameter, 4.2.2

MEMORY_TARGET initialization parameter, 4.2.2

metadata

dependencies, 4.5.6

migrating storage

avoiding downtime, 4.1.7

migrations

Oracle Exadata Storage Server Software, 4.1.8

mirroring

Oracle ASM native, 3.8

multiple standby databases

Data Guard hub, 7.1.5.3

failovers, 7.1.5.2

using transient logical standby, 7.1.5.2

N

network server processes (LNSn), Glossary

nodes

virtual IP addresses, 7.1.2

O

Observer

fast-start failover, 7.1.5.1

one-off patches, 4.1.3

online application maintenance and upgrades, 4.5

online maintenance

application, 4.5

online reorganization

description, 4.3

online table redefinition, 4.5.9

OPatch utility

patch upgrades for Oracle RAC, 4.1.3

operating system upgrades

using FAN during, 4.1.1

operating systems

requirements for Oracle Clusterware, 7.1.2

Oracle Active Data Guard

collecting ASH samples on, 6.1

Oracle Application Server

high availability architectures, 7.3.1

security, 7.3.1

Oracle Automatic Storage Management (Oracle ASM)

benefits, 3.8

description, 3.8

distribution of files, 4.2.3

failure group, 3.8

Fast Mirror Resync, 3.8

native mirroring, 3.8

storage migration, 4.1.7

with Database Storage Grid, 5.3

Oracle Call Interface (OCI), 3.4.2

Oracle Clusterware

advantages over third-party clusterware, 7.1.2

avoiding downtime when upgrading, 4.1.5

cold failover cluster, 7.1.2, 7.1.2

configured with Data Guard, 7.1.6

Oracle Data Guard

configured with Oracle Clusterware, 7.1.6

description, 3.5

multiple standby database architecture, 7.1.5.2

single standby database architecture, 7.1.5.1

system and cluster upgrades, 4.1.2

Oracle Data Provider for .NET (ODP.NET), 3.4.2

Oracle Database

basic architecture, 7.1.1

with an Oracle RAC extended cluster, 7.1.4

with Data Guard architecture, 7.1.5

with Oracle Clusterware (cold cluster failover), 7.1.2

with Oracle RAC and Data Guard - MAA, 7.1.7

with Oracle RAC architecture, 7.1.3

with Oracle Streams architecture, 7.1.8

Oracle Database File System (DBFS), 3.16, 7.1.5

Oracle Enterprise Manager Grid Control, 6.3

Oracle Exadata Storage Server Software, 3.15

migrating, 4.1.8

upgrading, 4.1.9

Oracle Exadata Storage Server Software See Also Exadata Cell

Oracle interim (one-off) patches, 4.1.3

avoiding downtime during, 4.1.3

Oracle interim database patches

applying, 4.1.3

Oracle Management Agents

Oracle Enterprise Management Grid Control, 6.3

Oracle Management Repository

Oracle Enterprise Manager Grid Control, 6.3

Oracle Management Service (OMS)

Oracle Enterprise Manager Grid Control, 6.3

Oracle Maximum Availability Architecture (MAA)

defined, Glossary

Oracle Real Application Clusters (Oracle RAC)

applying Oracle interim database patches, 4.1.3

benefits, 3.4.2

extended clusters, 7.1.4

operating system and hardware upgrades, 4.1.1

Storage Area Network (SAN), 7.1.4

Oracle Restart, 3.3

Oracle Secure Backup

benefits, 3.12

overview, 3.12

Oracle Streams

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

comparing to Data Guard, 3.6

description, 3.6

performing database upgrades, 4.1.10

performing platform migrations, 4.1.10

rolling upgrades, 4.5.2

Oracle UCP, 3.4.2

Oracle UCP runtime connection load balancing, 3.4.2

Oracle VM

Secure Live Migration, 5.5

outages

frequency, 7.2

types of, 1.4

P

performance

ASH sampling to address transient problems, 6.1

physical corruption

media corruption, 1.4

physical standby databases, 3.5.1

collecting ASH samples, 6.1

real-time query, 5.4.1

planned activities

probability of failure during, 7.2

planning

business performance, budget, and growth, 2.3.1

platform migrations

using Oracle Streams, 4.1.10

using transportable database, 4.1.11.1

policy management

security, 3.13

primary database

offload backups from, 3.5.1

prioritizing

high availability investment, 2.2.2

probability

of different failures during unplanned and planned activities, 7.2

program global area (PGA)

automatic management, 4.2.2

R

real-time query

collecting ASH samples on, 6.1

reconfiguring

databases dynamically, 4.2.1

Recovery Manager (RMAN)

benefits, 3.10

description, 3.10

recovery point objective (RPO)

defined, Glossary

description, 2.2.4, 7.2

recovery time

reducing downtime from data block corruption, 3.18

recovery time objective (RTO)

defined, Glossary

description, 2.2.3, 7.2

restore points

Flashback, 3.7.7

Return On Investment (ROI), 7.2

Return on Investment (ROI)

optimizing, 5

return on investment (ROI), 2.2.6

reverse crossedition triggers, 4.5.1.3

RMAN RECOVER BLOCK command

repairing data block corruption, 3.18

rollback

transactions, 3.7.3

rolling upgrades

Oracle Streams, 4.5.2

using transient logical standby, 7.1.5.2

row level security

virtual private database, 3.13

RPO

See recovery point objective (RPO)

RTO

See recovery time objective (RPO)

runtime connection load balancing, 3.4.2

S

secure communications

between tiers in grid control environments, 6.3

Secure Sockets layer (SSL)

enabling for secure communications, 6.3

use with grid control, 6.3

SecureFile LOBs, 3.16

security

benefits, 3.13

between tiers in firewall-protected environments, 6.3

data encryption, 3.13

description, 3.13

Oracle Application Server, 7.3.1

Oracle ASM, 3.8

RMAN, 3.10

segment advisor, 6.1

server generated alerts, 6.1

server grid, 5.1

servers

Oracle Clusterware requirements, 7.1.2

service-level agreements (SLAs), 2.1

single standby database architecture

failovers, 7.1.5.1

single-instance databases

Oracle Restart, 3.3

site failure, 1.4

SLAs, 2.1

snapshot standby database, 3.5.1

in a multiple standby database environment, 7.1.5.2

SQL Access Advisor, 6.1

SQL Performance Analyzer, 6.2

SQL Tuning Advisor, 6.1

SSL

See Secure Sockets layer (SSL)

standby databases

Active Data Guard option, 3.5.1, 5.4.1

example hub configurations, 7.1.5.3

logical standby, 7.1.5.2

snapshot standby in a multistandby database environment, 7.1.5.2

standby reader farms, 5.4.2

storage

failures, 1.4

grid, 5.1

migration, 4.1.7

Oracle ASM protection, 3.8

Storage Area Network (SAN)

extended clusters, 7.1.4

storage failures

protecting against, 3.8

system global area (SGA)

automatic management, 4.2.2

system upgrades

avoiding downtime during, 4.1.1

T

tables

editionable, 4.5.1.2

tape backups

with Oracle Secure Backup, 3.12

thin client watchdog

observer for fast-start failover, 7.1.5.1

Total Cost of Ownership (TCO), 7.2

total cost of ownership (TCO), 2.2.6

transactions

backing out with Flashback Transaction, 3.7.3

transportable database

for platform migration, 4.1.11.1

for unplanned downtime, 4.4

transportable tablespaces

for unplanned downtime, 4.4

upgrading the database, 4.1.10.2

transportable technologies

for unplanned downtime, 4.4

U

Undo Advisor, 6.1

undo data

used by flashback features, 3.7

unplanned activities

probability of failure during, 7.2

unplanned downtime

transportable tablespaces, 4.4

transportable technologies, 4.4

upgrades

application, 4.5

cluster, 4.1.2

database, 4.1.10

hardware, 4.1.1

operating system, 4.1.1, 4.1.2

Oracle Clusterware, 4.1.5

Oracle Exadata Storage Server Software, 4.1.9

Oracle Real Application Clusters (Oracle RAC), 4.1.1

rolling with Oracle Streams, 4.5.2

using crossedition triggers, 4.5.1.3

using transportable tablespaces, 4.1.10.2

with logical standby databases, 7.1.5.2

V

V$DATABASE_BLOCK_CORRUPTION view, 3.19

virtual IP address

defining for applications, 7.1.2

Oracle Clusterware, 7.1.2

virtual private database

security, 3.13

virtualization

with Oracle VM Secure Live Migration, 5.5

W

WAIT option

specifying DDL with, 4.5.3

Web scaleability

using standby reader farms, 5.4.2