Index

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

Numerics

24x365, 1.1

64-bit systems

migration from 32-bit, 5.4.3.1

A

access control

security, 3.12

Active Data Guard

See Oracle Active Data Guard

ADD COLUMN

default values for columns, 5.5.5

analysis

determining high availability requirements, 2.1

applications

failover, 3.1.2

online maintenance and upgrades, 5.5

applying interim database patches, 5.4.4

architectures

failures in, 1.1

MAA, 7

manageability, 2.2.5

Oracle Application Server, 7.6, 7.6.1

requirements, 1.1, 2.1

roadmap, 1.5

same processor platforms, 5.4.3

ASR

See Oracle Auto Service Request (ASR)

auditing

security control, 3.12

authentication

security controls, 3.12

automatic block repair, 3.13.9

automatic corruption repair, 3.1.2

automatic shared memory management

dynamic memory allocation, 5.2.2

availability

about, 1.1

disruptions, 1.3

roadmap, 1.5

B

backing out a transaction, 3.13.3

backups

Oracle Secure Backup, 3.5

between objects, 5.5.6

block recovery

using Flashback logs, 3.13.9

business impact analysis

internal knowledge management system example, 2.2.1

semiconductor manufacturer example, 2.2.1

C

Cluster Ready Services (CRS)

avoiding downtime during upgrades, 5.4.5

columns, invisible, 5.5.8

components

integrated with Oracle Restart, 3.18

computer failure, 1.4

corruptions

automatic repair, 3.1.2

prevention and detection, 3.10

costs

quantifying, 2.2.2

CREATE TRIGGER statement

clauses for, 5.5.4

crossedition triggers, 5.5.1.3

D

data corruptions, 1.4

detecting, 3.10

prevention and detection parameters, 3.10

data distribution

Oracle GoldenGate, 3.2

data encryption, 3.12

Data Guard

about, 3.1

benefits, 3.1, 3.1.2

configuring with Oracle GoldenGate, 5.4.8.5

system and cluster upgrades, 5.4.3

data integration

Oracle GoldenGate, 3.2

data protection

maximizing, 1.2

Data Recovery Advisor, 3.11

Database Server Grid

about, 9.1.1

Database Storage Grid

about, 9.1.2

database upgrades

using transportable tablespace, 5.4.8.3

databases

applying Oracle interim patches, 5.4.4

dynamic reconfiguration, 5.2.2

security, 3.12

datafiles, moving online, 5.2.1

data-loss tolerance, 2.2.4

DBA_FLASHBACK_TRANSACTION_STATE view, 3.13.3

DBMS_FLASHBACK.TRANSACTION_BACKOUT() procedure, 3.13.3

DDL with the WAIT option, 5.5.3

dependencies, 5.5.6

DISABLE clause

FOLLOWS clause

CREATE TRIGGER statement, 5.5.4

disaster recovery solutions

Oracle Application Server, 7.6.1

disk group

administering with Oracle ASM, 3.8

downtime

causes, 1.4

cost, 1.3, 2.2.2

minimizing with Oracle GoldenGate, 5.4.8.4

minimizing with Oracle GoldenGate and Data Guard, 5.4.8.5

mitigating, 1.3

reducing, 3.1.2

solutions summary

planned, 5.4

E

edition-based redefinition, 5.5.1

crossedition triggers, 5.5.1.3

editioning view, 5.5.1.2

editions, 5.5.1.1

ENABLE clause

CREATE TRIGGER statement, 5.5.4

encryption

of data, 3.12

Extended Datatype Support (EDS)

patch set and database upgrades, 5.4.8

F

failovers

applications, 3.1.2

services, 3.6.3

failure group

administering with Oracle ASM, 3.8

Oracle ASM, 3.8

failures

computer, 1.4

site, 1.4

storage, 1.4

fast application notification (FAN)

for hardware upgrades, 5.4.1

for operating system upgrades, 5.4.1

Fast Connection Failover

for nonpooled connections, 3.6.2

Fast Mirror Resync

Oracle ASM, 3.8

fast recovery area

about, 3.9

benefits, 3.9

flashback logs

block recovery using, 3.13.9

Flashback technology

G

grid computing, 9.1

H

hangs or slow down, 1.4

hardware upgrades

avoiding downtime during, 5.4.1

using FAN during, 5.4.1

high availability

24x365, 1.1

about, 1.1, 1.1

applications, 7.6.1

architectures, 1.1, 2.2.5, 7

business impact analysis, 2.2.1

determining requirements, 2.1

importance, 1.2

maximizing, 1.2

Oracle Application Server, 7.6

planned downtime, 5.4

setting manageability goals, 2.2.5

single-instance databases, 3.18

solutions, 1.1

unplanned downtime, 4

I

indexes

invisible, 5.5.7

indexes, multiple on same set of columns, 5.5.9

instance failure, 3.6.3

interblock corruption, 1.4

intrablock corruption, 1.4

invisible columns, 5.5.8

invisible indexes, 5.5.7

L

load balancing

advisory, 3.6.3

run-time connection, 3.6.3

load balancing advisory, 3.6.2

logical corruption, 1.4

lost writes, 1.4

M

making data changes, 5.5.1.1

manageability

goals, 2.2.5

overhead (MO), 2.2.5

Maximum Availability Architecture

See Oracle Maximum Availability Architecture (MAA)

media corruption

physical corruption, 1.4

memory

automatic management of, 5.2.3

MEMORY_MAX_TARGET initialization parameter, 5.2.3

MEMORY_TARGET initialization parameter, 5.2.3

metadata

dependencies, 5.5.6

migrating storage

avoiding downtime, 5.1.4

migrations

32-bit to 64-bit systems, 5.4.3.1

storage, 5.1.4

mirroring

Oracle ASM native, 3.8

N

network bonding, 3.6.3

O

offloading database activity, 3.1.2

one-off patches, 5.4.4

online maintenance

application, 5.5

online redefinition

of tables, 5.3

online table redefinition, 5.5.10

online, moving datafiles, 5.2.1

OPatch utility

patch upgrades for Oracle RAC, 5.4.4.1

operating systems

upgrades, 5.4.1

using FAN during upgrades, 5.4.1

Oracle Active Data Guard

benefits of standby databases, 3.1.1

for physical standby databases, 9.2.1

Oracle Application Server

high availability architectures, 7.6.1

security, 7.6.1

Oracle ASM Cluster File System (ACFS), 3.15.2

Oracle Auto Service Request (ASR), 6.9.3

Oracle Automatic Storage Management (Oracle ASM)

about, 3.8

benefits, 3.8

distribution of files, 5.2.4

failure group, 3.8

Fast Mirror Resync, 3.8

native mirroring, 3.8

storage migration, 5.4.6

upgrading, 5.4.6

Oracle Automatic Storage Management Cluster File System (Oracle ACFS), 3.8

Oracle Call Interface (OCI), 3.6.2

Oracle Clusterware

avoiding downtime when upgrading, 5.4.5

cold cluster failover, 3.6.3

Oracle Data Guard

See Data Guard

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

Oracle Database File System (DBFS), 3.1.2, 3.15.1

Oracle Enterprise Manager, 3.6.3

Oracle Exadata Database Machine, 8.1

Oracle Exadata Storage Server Software

combined with Oracle Database Machine, 8.1

upgrading, 5.4.7

Oracle Flashback Data Archive, 3.13.10

Oracle Flashback Database, 3.13.8

Oracle Flashback Drop, 3.13.6

Oracle Flashback Query, 3.13.1

Oracle Flashback Table, 3.13.5

Oracle Flashback technology, 3.13

block recovery using Flashback logs, 3.13.9

Oracle Flashback Transaction, 3.13.3

Oracle Flashback Transaction Query, 3.13.4

Oracle Flashback Version Query, 3.13.2

Oracle GoldenGate

about, 3.2

configure to minimize downtime, 5.4.8.5

rolling upgrades, 5.5.2

upgrades, 5.4.8.4

Oracle interim (one-off) patches, 5.4.4

applying, 5.4.4

avoiding downtime during, 5.4.4

Oracle Maximum Availability Architecture (MAA)

about, 1.5

architectures, 7

roadmap, 1.5

Oracle Quality of Service (QoS) Management, 3.6.3

Oracle RAC One Node, 3.6.3

Oracle Real Application Clusters (Oracle RAC)

applying Oracle interim database patches, 5.4.4

benefits, 3.6.2

operating system and hardware upgrades, 5.4.1

Oracle Real Application Clusters One Node

See Oracle RAC One Node

Oracle Restart, 3.18

Oracle Secure Backup

about, 3.5

benefits, 3.5

Oracle Solaris ZFS Storage Appliance Replication, 3.15.3

Oracle UCP run-time connection load balancing, 3.6.2

Oracle VM

Domain Live Migration, 9.3.2

outages

types of, 1.4

P

patching

rolling, 3.6.3

physical corruption, 1.4

physical standby databases

real-time query, 9.2.1

planned downtime

online patching, 5.4.2

planned outages

minimizing with Oracle GoldenGate, 5.4.8.4

minimizing with Oracle GoldenGate and Data Guard, 5.4.8.5

Plug and Play, 3.6.3

pluggable databases, 9.3

policy management

security, 3.12

policy-based cluster management, 3.6.3

portable databases, 9.3

prioritizing

high availability investment, 2.2.2

Program Global Area (PGA)

automatic management, 5.2.3

R

real-time query, 9.2.1

reconfiguring

databases dynamically, 5.2.2

Recovery Manager (RMAN)

about, 3.4

benefits, 3.4

recovery point objective (RPO)

about, 2.2.4

recovery time objective (RTO)

about, 2.2.3

replication

Oracle GoldenGate, 3.2

restore points

Oracle Flashback, 3.13.7

return on investment (ROI), 2.2.6

reverse crossedition triggers, 5.5.1.3

roadmap to Maximum Availability Architecture (MAA), 1.5

rollback

transactions, 3.13.3

rolling patching, 3.6.3

rolling upgrades, 3.6.3

Oracle GoldenGate, 5.5.2

row level security

virtual private database, 3.12

run-time connection load balancing, 3.6.2, 3.6.3

S

scalability

with Oracle RAC, 3.6.3

SCAN, 3.6.3

security

about, 3.12

benefits, 3.12

data encryption, 3.12

Oracle Application Server, 7.6.1

Oracle ASM, 3.8

RMAN, 3.4

services

failover, 3.6.3

simple database rolling upgrades, 5.4.8.1

single-instance databases

Oracle Restart, 3.18

site failure, 1.4

SQL Apply, 5.4.8, 5.4.8.1

standby databases

active, 9.2

benefits, 3.1

Oracle Active Data Guard, 9.2.1

standby reader farms, 9.2.2

storage

failures, 1.4, 3.8

migration, 5.1.4

Oracle ASM protection, 3.8

System Global Area (SGA)

automatic management, 5.2.3

system upgrades

avoiding downtime during, 5.4.1

T

tables

editionable, 5.5.1.2

tape backups

with Oracle Secure Backup, 3.5

total cost of ownership (TCO), 2.2.6

transactions

backing out with Flashback Transaction, 3.13.3

transportable tablespace

upgrading the database, 5.4.8.3

U

unplanned downtime

causes, 1.4

solutions summary, 4

upgrade

simple rolling, 5.4.8.1

using Oracle GoldenGate, 5.4.8.4

upgrades

application, 5.5

cluster, 5.4.3

database, 5.4.8

hardware, 5.4.1

operating system, 5.4.1, 5.4.3

Oracle ASM, 5.4.6

Oracle Clusterware, 5.4.5

Oracle Exadata Storage Server Software, 5.4.7

Oracle Real Application Clusters (Oracle RAC), 5.4.1

patches, 5.4.4

rolling, 3.6.3

rolling with Oracle GoldenGate, 5.5.2

SQL Apply, 5.4.8

using crossedition triggers, 5.5.1.3

using transportable tablespace, 5.4.8.3

V

virtual IP (VIP) address

managed by Oracle Clusterware, 3.6.1

virtual private database

security, 3.12

virtualization

with Oracle VM Domain Live Migration, 9.3.2

W

WAIT option

specifying DDL with, 5.5.3

web scalability

using standby reader farms, 9.2.2

workload

offloading, 3.1.2

workload management, 3.6.3

Z

zero data loss, 3.1.2