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

64-bit systems

migration from 32-bit, 4.1.2.1

A

access control

security, 3.14

Active Data Guard

See Oracle Active Data Guard option

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

applying interim database patches, 4.1.3

architectures

choosing, 7.2, 7.2

CPU, 3.6

failures in, 1.1

grid computing, 5.1

MAA, 7

manageability, 2.2.5

multiple standby database, 7.1.4.2

Oracle Application Server, 7.2, 7.3, 7.3.1

Oracle Clusterware, 7.1.2

Oracle Clusterware and Oracle Data Guard, 7.1.4.3, 7.1.5

Oracle Data Guard, 7.1.4

Oracle Data Guard standby hub, 7.1.4.2, 7.1.4.3

Oracle Database, 7.1.1

Oracle RAC, 7.1.3

Oracle RAC and Oracle Data Guard, 7.1.6

Oracle RAC on extended clusters, 7.1.3.2

Oracle RAC One Node, 7.1.3.1

Oracle Streams, 7.1.6, 7.1.7

recommendations, 7.2

requirements, 1.1, 2.1, 2.3

roadmap, 1.5

same processor platforms, 4.1.2

single standby database, 7.1.4, 7.1.4.1

ASM

See Oracle Automatic Storage Management (Oracle ASM)

auditing

security control, 3.14

authentication

security controls, 3.14

automatic block repair, 3.8.9, 3.20

automatic failover

Oracle Data Guard, 7.1.4.1

automatic maintenance tasks, 6.1

automatic shared memory management

dynamic memory allocation, 4.2.1

Automatic Workload Repository (AWR), 6.1

availability

about, 1.1

disruptions, 1.3

roadmap, 1.5

B

backing out a transaction, 3.8.3

backups

fast recovery area, 3.10

offload from the primary database, 3.6.1

Oracle Secure Backup, 3.13

between objects, 4.5.6

block corruption

repairing, 3.20

block recovery

reducing time, 3.20

using Flashback logs, 3.8.9

block recovery using flashback logs, 3.8.9

bounded recovery, 3.2

Bourne shell script

physru, 3.6.3

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

change assurance, 6

checkpointing

fast-start fault recovery, 3.2

choosing the correct high availability architecture, 7.2

client failover, 3.19

Cluster Ready Services (CRS)

avoiding downtime during upgrades, 4.1.5

clusters

extended, 7.1.3.2

Oracle Clusterware, 7.1.2

cold cluster failover, 7.1.2, 7.1.5

with Oracle Clusterware, 7.1.2

with Oracle Clusterware and Data Guard, 7.1.5

components

integrated with Oracle Restart, 3.3

compressed redo data

Oracle Data Guard, 7.1.4

computer failure, 1.4

corruptions

prevention and detection, 3.21

repairing, 3.20

costs

quantifying, 2.2.2

CPU architectures, 3.6

CREATE TRIGGER statement

clauses for, 4.5.4

crossedition triggers, 4.5.1.3

D

data corruptions, 1.4

automatic detection and repair, 3.20

detecting, 3.21

prevention and detection parameters, 3.21

data distribution

Oracle GoldenGate, 3.7

data encryption, 3.14

Data Guard

See Oracle Data Guard

data integration

Oracle GoldenGate, 3.7

data protection

maximizing, 1.2

Data Recovery Advisor, 3.12

data transformation, 3.7.1

data type restrictions

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

data types

supporting advanced with EDS, 3.6.3

Database Replay, 6.2

Database Server Grid, 5.1

about, 5.2

Database Storage Grid, 5.1

about, 5.3

database upgrades

using Oracle Streams, 4.1.10

using transportable tablespace, 4.1.10.2

databases

applying Oracle interim patches, 4.1.3

checkpointing, 3.2

dynamic reconfiguration, 4.2.1

security, 3.14

server grid, 5.1

data-loss tolerance, 2.2.4

DB_BLOCK_CHECKING initialization parameter, 3.21

DB_BLOCK_CHECKSUM initialization parameter, 3.21

DB_LOST_WRITE_PROTECT initialization parameter, 3.21

DB_ULTRA_SAFE initialization parameter, 3.21

DBA_FLASHBACK_TRANSACTION_STATE view, 3.8.3

DBFS Content Store, 3.18

DBMS_FLASHBACK.TRANSACTION_BACKOUT() procedure, 3.8.3

DDL with the WAIT option, 4.5.3

dependencies, 4.5.6

DISABLE clause

FOLLOWS clause

CREATE TRIGGER statement, 4.5.4

disaster recovery solutions

Oracle Application Server, 7.3.1

disk group

administering with Oracle ASM, 3.9

downtime

causes, 1.4

cost, 1.3, 2.2.2

minimizing with Oracle GoldenGate and Oracle Data Guard, 4.1.10.3

mitigating, 1.3

solutions summary

planned, 4.1

unplanned, 3.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

ENABLE clause

CREATE TRIGGER statement, 4.5.4

encryption

of data, 3.14

endian format platforms

avoiding downtime during migration of different, 4.1.12

avoiding downtime during migration of same, 4.1.11

Exadata Cell, 3.16

See also Oracle Exadata Storage Server Software

EXCLUDE STANDBY option

of the RMAN RECOVER BLOCK command, 3.20

extended clusters

architecture, 7.1.3.2

Extended Data Type Support (EDS)

rolling upgrades, 3.6.3

Extended Datatype Support (EDS)

patch set and database upgrades, 4.1.10

F

failovers

fast, 7.1.4.1

multiple standby databases

architecture, 7.1.4.2

single standby database architecture, 7.1.4.1

failure group

administering with Oracle ASM, 3.9

Oracle ASM, 3.9

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.9

fast recovery area

about, 3.10

benefits, 3.10

in a Data Guard configuration, 7.1.4

fast-start failover

single standby database failover, 7.1.4.1

Fast-Start Fault Recovery

benefits of using, 3.2

fault diagnosability infrastructure, 6.1

flashback logs

block recovery using, 3.8.9

used by Flashback features, 3.8

Flashback technology

block recovery using Flashback logs, 3.8.9

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

hangs or slow down, 1.4

HARD specifications, 3.21

Hardware Assisted Resilient Data (HARD) specifications, 3.21

hardware upgrades

avoiding downtime during, 4.1.1

using FAN during, 4.1.1

high availability

24x365, 1.1

about, 1.1, 1.1

analysis framework, 2.1

applications, 7.3.1

architectures, 1.1, 2.2.5, 7, 7.2

business impact analysis, 2.2.1

determining requirements, 2

importance, 1.2

maximizing, 1.2

Oracle Application Server, 7.3

Oracle Database, 7.1

planned downtime, 4.1

planning, 2.3.1

setting manageability goals, 2.2.5

single-instance databases, 3.3

solutions, 1.1

unplanned downtime, 3

I

indexes

invisible, 4.5.7

intelligent infrastructure, 6, 6.1

interblock corruption, 1.4

interconnects

Oracle RAC, 7.1.3

intrablock corruption, 1.4

invisible indexes, 4.5.7

I/O Resource Management

Oracle Storage Grid, 5.3

L

load balancing advisory, 3.4.2

logical corruption, 1.4

logical standby databases

about, 3.6.5

benefits of, 3.6.5

transient, 3.6.3, 3.6.3

LogMiner utility

about, 3.15

lost writes, 1.4

M

making data changes, 4.5.1.1

manageability

goals, 2.2.5

optimizing, 6

overhead (MO), 2.2.5, 7.2

manual block repair, 3.20

materialized views

logging control, 4.5.8

Maximum Availability Architecture

See Oracle Maximum Availability Architecture (MAA)

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

32-bit to 64-bit systems, 4.1.2.1

Oracle Exadata Storage Server Software, 4.1.8

storage, 4.1.7

mirroring

Oracle ASM native, 3.9

multimaster replication, 3.7.1

multiple standby databases

Data Guard hub, 7.1.4.3

failovers, 7.1.4.2

using transient logical standby, 3.6.3, 3.6.3

N

nodes

virtual IP addresses, 7.1.2

O

observer

fast-start failover, 7.1.4.1

one-off patches, 4.1.3

online database relocation utility, 7.1.3.1

online maintenance

application, 4.5

online redefnition of tables, 4.3

online reorganization

about, 4.3

online table redefinition, 4.5.9

OPatch utility

patch upgrades for Oracle RAC, 4.1.3

operating systems

requirements for Oracle Clusterware, 7.1.2

upgrades, 4.1.1

using FAN during upgrades, 4.1.1

Oracle Active Data Guard

standby databases

benefits of, 3.6.2

Oracle Active Data Guard option, 5.4.1

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)

about, 3.9

benefits, 3.9

distribution of files, 4.2.3

failure group, 3.9

Fast Mirror Resync, 3.9

native mirroring, 3.9

storage migration, 4.1.6

upgrading, 4.1.6

with Database Storage Grid, 5.3

Oracle Automatic Storage Management Cluster File System (Oracle ACFS), 3.9, 7.1.1

Oracle Call Interface (OCI), 3.4.2

Oracle Clusterware

about, 7.1.2

advantages over third-party clusterware, 7.1.2

avoiding downtime when upgrading, 4.1.5

benefits, 7.1.2

cold cluster failover, 7.1.2

configured with Data Guard, 7.1.5

Oracle Data Guard

about, 3.6

benefits, 3.6, 7.1.4

benefits of, 3.6

configured with Oracle Clusterware, 7.1.5

configuring with Oracle GoldenGate, 3.7.2, 4.1.10.3

hub architecture, 7.1.4.3

multiple standby database architecture, 7.1.4.2

single standby database architecture, 7.1.4.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 Data Guard, 7.1.4

with Oracle Clusterware (cold cluster failover), 7.1.2

with Oracle Clusterware and Oracle Data Guard, 7.1.5

with Oracle RAC, 7.1.3

with Oracle RAC and Oracle Data Guard - MAA, 7.1.6

with Oracle RAC on an extended cluster, 7.1.3.2

with Oracle Streams, 7.1.7

Oracle Database File System (DBFS), 3.18, 7.1.4

Oracle Database Resource Manager Instance Caging, 7.1.3.1

Oracle Enterprise Manager Grid Control, 6, 6.3

Oracle Exadata Database Machine, 3.17

Oracle Exadata Storage Server Software, 3.16

combined with Sun Oracle Database Machine, 3.17

migrating, 4.1.8

upgrading, 4.1.9

Oracle Flashback Data Archive, 3.8.10

Oracle Flashback Database, 3.8.8

Oracle Flashback Drop, 3.8.6

Oracle Flashback Query, 3.8.1

Oracle Flashback Table, 3.8.5

Oracle Flashback technology, 3.8

Oracle Flashback Transaction, 3.8.3

Oracle Flashback Transaction Query, 3.8.4

Oracle Flashback Version Query, 3.8.2

Oracle GoldenGate, 3.7

about, 3.7

comparing to Oracle Streams, 3.7

configure to minimize downtime, 4.1.10.3

configuring with Oracle Data Guard, 3.7.2

Oracle interim (one-off) patches, 4.1.3

applying, 4.1.3

avoiding downtime during, 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)

about, 1.5

architectures, 7

benefits, 7.1.6

roadmap, 1.5

Oracle RAC One Node, 7.1.3.1

online database relocation utility, 7.1.3.1

Oracle Real Application Clusters (Oracle RAC)

about, 7.1.3

applying Oracle interim database patches, 4.1.3

automatic redundant interconnects, 7.1.3

benefits, 3.4.2

extended clusters, 7.1.3.2

operating system and hardware upgrades, 4.1.1

Storage Area Network (SAN), 7.1.3.2

Oracle Real Application Clusters One Node

See Oracle RAC One Node

Oracle Restart, 3.3

Oracle Secure Backup

about, 3.13

benefits, 3.13

Oracle Streams, 3.7

comparing to Oracle GoldenGate, 3.7

performing database upgrades, 4.1.10

performing platform migrations, 4.1.10

rolling upgrades, 4.5.2, 4.5.2

Oracle UCP runtime connection load balancing, 3.4.2

Oracle VM

Domain Live Migration, 5.5

with Oracle RAC One Node, 7.1.3.1

outages

frequency, 7.2, 7.2

types of, 1.4

P

performance

ASH sampling to address transient problems, 6.1

physical corruption, 1.4

physical standby databases

benefits of, 3.6.1

collecting ASH samples, 6.1

real-time query, 5.4.1

snapshot standby, 3.6.4

transient logical standby database, 3.6.3

physru shell script, 3.6.3

planned activities

probability of failure during, 7.2

planned downtime

online patching, 4.1.4

recovery times, 7.2

planned outages

minimizing with Oracle GoldenGate and Oracle Data Guard, 4.1.10.3

platform migrations

using Oracle Streams, 4.1.10

using transportable database, 4.1.11.1

policy management

security, 3.14

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, 5.4.1

collecting ASH samples on, 6.1

reconfiguring

databases dynamically, 4.2.1

Recovery Manager (RMAN)

about, 3.11

benefits, 3.11

recovery point objective (RPO)

about, 2.2.4, 7.2

recovery time objective (RTO)

about, 2.2.3, 7.2

recovery times

planned downtime, 7.2

reducing downtime from data block corruption, 3.20

unplanned downtime, 7.2

redundant interconnect, 7.1.3

relocation

online database, 7.1.3.1

replication

Oracle GoldenGate, 3.7

Oracle Streams, 3.7

restore points

Oracle Flashback, 3.8.7

return on investment (ROI), 2.2.6, 7.2

optimizing, 5

reverse crossedition triggers, 4.5.1.3

RMAN RECOVER BLOCK command

repairing data block corruption, 3.20

roadmap to Maximum Availability Architecture (MAA), 1.5

rollback

transactions, 3.8.3

rolling upgrades

Oracle Streams, 4.5.2

supporting data types with Extended Data Type Support (EDS), 3.6.3

using Oracle Streams, 4.5.2

using the physru shell script, 3.6.3

using transient logical standby, 3.6.3, 3.6.3

row level security

virtual private database, 3.14

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.18

security

about, 3.14

benefits, 3.14

between tiers in firewall-protected environments, 6.3

data encryption, 3.14

Oracle Application Server, 7.3.1

Oracle ASM, 3.9

RMAN, 3.11

Segment Advisor, 6.1

server grid, 5.1

server-generated alerts, 6.1

servers

Oracle Clusterware requirements, 7.1.2

service-level agreements (SLAs), 2.1

single standby database architecture

failovers, 7.1.4.1

single-instance databases

Oracle Restart, 3.3

site failure, 1.4

SLAs, 2.1

snapshot standby database

about, 3.6.4

snapshot standby databases

benefits of, 3.6.4

SQL Access Advisor, 6.1

SQL Apply

upgrades, 4.1.10, 4.1.10.1

with Extended Datatype Support (EDS), 4.1.10.1

with logical standby databases, 3.6.5

with Oracle Streams, 7.1.7

SQL Performance Analyzer, 6.2

SQL Tuning Advisor, 6.1

SSL

See Secure Sockets Layer (SSL)

standby databases

active, 5.4

Active Data Guard option, 5.4.1

benefits of, 3.6

example hub configurations, 7.1.4.3

logical standby, 3.6.3, 3.6.3

multiple-standby architecture, 7.1.4.2

single-standby architecture, 7.1.4.1

snapshot standby database, 3.6.1

transient logical standby database, 3.6.1

standby reader farms, 5.4.2

storage

failures, 1.4, 3.9

grid, 5.1

migration, 4.1.7

Oracle ASM protection, 3.9

Storage Area Network (SAN)

extended clusters, 7.1.3.2

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.13

thin client watchdog

observer for fast-start failover, 7.1.4.1

total cost of ownership (TCO), 2.2.6, 7.2

transactions

backing out with Flashback Transaction, 3.8.3

transient logical standby databases

about, 3.6.3

benefits of, 3.6.3

physru shell script, 3.6.3

transportable database

for platform migration, 4.1.11.1

for unplanned downtime, 4.4

transportable tablespace

for unplanned downtime, 4.4

upgrading the database, 4.1.10.2

U

Undo Advisor, 6.1

undo data

used by flashback features, 3.8

unplanned activities

probability of failure during, 7.2

unplanned downtime

causes, 1.4

recovery times, 7.2

solutions summary, 3.1

transportable technologies, 4.4

updatable standby databases, 3.6.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 ASM, 4.1.6

Oracle Clusterware, 4.1.5

Oracle Exadata Storage Server Software, 4.1.9

Oracle Real Application Clusters (Oracle RAC), 4.1.1

patches, 4.1.3

rolling with Oracle Streams, 4.5.2

using crossedition triggers, 4.5.1.3

using transportable tablespace, 4.1.10.2

with logical standby databases (SQL Apply), 3.6.3, 3.6.3

V

V$DATABASE_BLOCK_CORRUPTION view, 3.21

virtual IP (VIP) address

defining for applications, 7.1.2

managed by Oracle Clusterware, 3.4.1

virtual private database

security, 3.14

virtualization

with Oracle VM Domain Live Migration, 5.5

W

WAIT option

specifying DDL with, 4.5.3

Web scalability

using standby reader farms, 5.4.2