Index

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

A

activating

a logical standby database, 8.3.2, 16.1

a physical standby database, 11.8.6, 16.1

Active Data Guard

and physical standby databases, 2.1.1, 9.2

and the real-time query feature, 9.2.1

adding

datafiles, 9.3.1, A.10.1.1, A.10.1.1

indexes on logical standby databases, 2.1.2, 10.5.4.1

new or existing standby databases, 1.3

online redo log files, 9.3.5

tablespaces, 9.3.1

adjusting

initialization parameter file

for logical standby database, 4.2.4.2

AFFIRM attribute, 15

ALTER DATABASE statement

ABORT LOGICAL STANDBY clause, 16.1

ACTIVATE STANDBY DATABASE clause, 8.3.2, 11.8.6, 16.1, 16.1

ADD STANDBY LOGFILE clause, 16.1, A.1.1

ADD STANDBY LOGFILE MEMBER clause, 16.1, A.1.1, A.1.1

ADD SUPPLEMENTAL LOG DATA clause, 16.1

CLEAR UNARCHIVED LOGFILES clause, 9.5

COMMIT TO SWITCHOVER clause, 8.3.1, 8.3.1, 8.3.1, 16.1

in Oracle Real Application Clusters, D.3.1

troubleshooting, A.4.2, A.4.2, A.4.3

CREATE CONTROLFILE clause, 9.5

CREATE DATAFILE AS clause, A.1.1

CREATE STANDBY CONTROLFILE clause, 3.2.2, A.1.3

REUSE clause, 16.1

DROP LOGFILE clause, A.1.1

DROP STANDBY LOGFILE MEMBER clause, 16.1, 16.1, 16.1, A.1.1

FORCE LOGGING clause, 2.3.2, 3.1.1, 13.4, 13.4, 16.1

GUARD clause, 10.2

MOUNT STANDBY DATABASE clause, 16.1

OPEN READ ONLY clause, 16.1

OPEN RESETLOGS clause, 3.2.2, 9.5

PREPARE TO SWITCHOVER clause, 8.3.1, 8.3.1, 16.1

RECOVER MANAGED STANDBY DATABASE clause, 3.2.6, 4.2.5, 16.1, 16.1, 16.1

background process, 7.3.1

canceling, 7.3.2

controlling Redo Apply, 7.3.1, 11.8.2

failover, 16.1

foreground session, 7.3.1

overriding the delay interval, 7.2.2

starting real time apply, 7.3.1

RENAME FILE clause, A.1.1, A.1.1

SET STANDBY DATABASE clause

TO MAXIMIZE AVAILABILITY clause, 16.1

TO MAXIMIZE PERFORMANCE clause, 8.1.4

TO MAXIMIZE PROTECTION clause, 16.1

START LOGICAL STANDBY APPLY clause, 7.4.1, 12.5, A.6

IMMEDIATE keyword, 7.4.1

starting SQL Apply, 4.2.5

STOP LOGICAL STANDBY APPLY clause, 7.4.2, 8.3.2, 16.1

ALTER SESSION DISABLE GUARD statement

overriding the database guard, 10.5.4

ALTER SESSION statement

ENABLE GUARD clause, 16.2

ALTER SYSTEM statement

SWITCH LOGFILE clause, 3.2.7

ALTER TABLESPACE statement, 9.3.4, 13.4.2, A.10.1.1

FORCE LOGGING clause, 9.3.6

alternate archive destinations

setting up initialization parameters for, A.2

ALTERNATE attribute, 15, 15

LOG_ARCHIVE_DEST_n initialization parameter, A.2

LOG_ARCHIVE_DEST_STATE_n initialization parameter, 6.2.2

ANALYZER process, 10.1

APPLIER process, 10.1

apply lag

monitoring in a real-time query environment, 9.2.1.1

apply lag tolerance

configuring in a real-time query environment, 9.2.1.2

apply services

defined, 1.2.2, 7.1

delaying application of redo data, 7.2.2, 15

real-time apply

defined, 7.2.1, 7.2.1

monitoring with LOG_ARCHIVE_TRACE, F.2

Redo Apply

defined, 7.1, 7.3

monitoring, 7.3.3

starting, 7.3.1

stopping, 7.3.2

SQL Apply

defined, 1.2.2, 7.1, 7.1

monitoring, 7.4.3

starting, 7.4.1

stopping, 7.4.2

applying

redo data immediately, 7.2.1

redo data on standby database, 1.2, 1.2.2, 7

SQL statements to logical standby databases, 7.4

applying state, 10.4.1

AQ_TM_PROCESSES dynamic parameter, A.4.2

archive destinations

alternate, A.2

archived redo log files

accessing information about, 9.5.1.3

applying

Redo Apply technology, 1.2.2

SQL Apply technology, 1.2.2

delaying application, 15

on the standby database, 7.2.2

deleting unneeded, 10.4.2

destinations

disabling, 6.2.2

enabling, 6.2.2

managing gaps, 1.7

B

BACKUP INCREMENTAL FROM SCN command

scenarios using, 11.10

backup operations

after failovers, 8.3.2

after unrecoverable operations, 13.4.3, 13.4.3

configuring on a physical standby database, 1.1.3

datafiles, 13.4.2

offloading on the standby database, 1.7

primary databases, 1.1.2

used by the broker, 1.3

using RMAN, 11

basic readable standby database See simulating a standby database environment

batch processing

on a logical standby database, 10.1.1.4

benefits

Data Guard, 1.7

logical standby database, 2.1.2

of a rolling upgrade, 12.1

physical standby database, 2.1.1

BFILE data types

in logical standby databases, C.1.2

block repair, automatic, 9.2.1.5

broker

command-line interface, 1.7

defined, 1.3

graphical user interface, 1.7

BUILDER process, 10.1

C

cascading redo data, 6.3

configuration requirements, 6.3

data protection considerations, 6.3.2

restrictions, 6.3

character sets

changing on primary databases, 13.8

configurations with differing, C.15

checklist

tasks for creating physical standby databases, 3.2, 3.2

tasks for creating standby databases, 4.2, 4.2

checkpoints

V$LOGSTDBY_PROGRESS view, 10.1.1.3

chunking

transactions, 10.1.1.1

CJQ0 process, A.4.2

CLEAR UNARCHIVED LOGFILES clause

of ALTER DATABASE, 9.5

collections data types

in logical standby databases, C.1.2

command-line interface

broker, 1.7

commands, Recovery Manager

DUPLICATE, E.2.1

COMMIT TO SWITCHOVER clause

of ALTER DATABASE, 8.3.1, 8.3.1, 16.1

in Oracle Real Application Clusters, D.3.1

troubleshooting, A.4.2, A.4.2, A.4.3

COMMIT TO SWITCHOVER TO PRIMARY clause

of ALTER DATABASE, 8.3.1

communication

between databases in a Data Guard configuration, 1.1

COMPATIBLE initialization parameter

setting after upgrading Oracle Database software, B.4

setting for a rolling upgrade, 12.2, 12.5, 12.5

complementary technologies, 1.6

COMPRESSION attribute, 15

configuration options

creating with Data Guard broker, 1.3

overview, 1.1

physical standby databases

location and directory structure, 2.4

standby databases

delayed standby, 7.2.2

configuring

backups on standby databases, 1.1.3

disaster recovery, 1.1.3

initialization parameters

for alternate archive destinations, A.2

listener for physical standby databases, 3.2.5

no data loss, 1.2.3

physical standby databases, 2.4

reporting operations on a logical standby database, 1.1.3

standby databases at remote locations, 1.1.3

constraints

handled on a logical standby database, 10.6.3

Context

unsupported data types, C.1.2

Context data types

in logical standby databases, C.1.2

control files

copying, 3.2.4

creating for standby databases, 3.2.2

CONVERT TO SNAPSHOT STANDBY clause on the ALTER DATABASE statement, 16.1

converting

a logical standby database to a physical standby database

aborting, 4.2.4.1

a physical standby database to a logical standby database, 4.2.4.1

COORDINATOR process, 10.1

LSP background process, 10.1

copying

control files, 3.2.4

CREATE CONTROLFILE clause

of ALTER DATABASE, 9.5

CREATE DATABASE statement

FORCE LOGGING clause, 13.4

CREATE DATAFILE AS clause

of ALTER DATABASE, A.1.1

CREATE STANDBY CONTROLFILE clause

of ALTER DATABASE, 3.2.2, 16.1, A.1.3

CREATE TABLE AS SELECT (CTAS) statements

applied on a logical standby database, 10.1.1.5

creating

indexes on logical standby databases, 10.5.4.1

D

data availability

balancing against system performance requirements, 1.7

Data Guard broker

defined, 1.3

distributed management framework, 8

failovers, 1.3

fast-start, 8

manual, 1.3, 8

fast-start failover, 1.3

switchovers, 8

Data Guard configurations

archiving to standby destinations using the log writer process, 7.2.1

defined, 1.1

protection modes, 1.4

upgrading Oracle Database software, B

data loss

due to failover, 1.2.3

switchover and, 8.1

data protection

balancing against performance, 1.7

benefits, 1.7

flexibility, 1.7

provided by Data Guard, 1

data protection modes

enforced by redo transport services, 1.2.1

overview, 1.4, 1.4

Data Pump utility

using transportable tablespaces with physical standby databases, 9.3.3

data types

BFILE, C.1.2

collections in logical standby databases, C.1.2

ROWID, C.1.2

Spatial, Image, and Context, C.1.2

UROWID, C.1.2

user-defined, C.1.2

database guard, 10.5.4

overriding, 10.5.4

database incarnation

changes with OPEN RESETLOGS, 9.4, 9.4

database roles

primary, 1.1.1, 8.1

standby, 1.1.2, 8.1

transitions, 1.2.3

database schema

physical standby databases, 1.1.2

databases

failover and, 8.1.4

role transition and, 8.1

surviving disasters and data corruptions, 1

upgrading software versions, 12.1

datafiles

adding to primary database, 9.3.1

monitoring, 9.5, 13.4.2

renaming on the primary database, 9.3.4

DB_FILE_NAME_CONVERT initialization parameter

setting at standby site after a switchover, A.4.4

setting on physical standby database, 3.2.3

when planning standby location and directory structure, 2.4

DB_NAME initialization parameter, 3.1.4

DB_ROLE_CHANGE system event, 8.1.5

DB_UNIQUE_NAME attribute, 15

DB_UNIQUE_NAME initialization parameter, A.4.3

required with LOG_ARCHIVE_CONFIG parameter, 14

setting database initialization parameters, 3.1.4

DBA_DATA_FILES view, 9.5

DBA_LOGMNR_PURGED_LOG view

list archived redo log files that can be deleted, 10.4.2

DBA_LOGSTDBY_EVENTS view, 10.3.1, 17, A.6

recording unsupported operations in, 10.5.1

DBA_LOGSTDBY_HISTORY view, 17

DBA_LOGSTDBY_LOG view, 10.3.2, 17

DBA_LOGSTDBY_NOT_UNIQUE view, 17

DBA_LOGSTDBY_PARAMETERS view, 17

DBA_LOGSTDBY_SKIP view, 17

DBA_LOGSTDBY_SKIP_TRANSACTION view, 17

DBA_LOGSTDBY_UNSUPPORTED view, 17

DBA_TABLESPACES view, 9.5

DBMS_ALERT, C.9.2

DBMS_AQ, C.9.2

DBMS_DESCRIBE, C.9.1

DBMS_JAVA, C.9.2

DBMS_LOB, C.9.1

DBMS_LOGSTDBY package

INSTANTIATE_TABLE procedure, 10.5.5

SKIP procedure, A.6

SKIP_ERROR procedure, A.3

SKIP_TRANSACTION procedure, A.6

DBMS_LOGSTDBY.BUILD procedure

building a dictionary in the redo data, 4.2.3.2

DBMS_METADATA, C.9.1

DBMS_OBFUSCATION_TOOLKIT, C.9.1

DBMS_OUTPUT, C.9.1

DBMS_PIPE, C.9.1

DBMS_RANDOM, C.9.1

DBMS_REDEFINITION, C.9.2

DBMS_REFRESH, C.9.2

DBMS_REGISTRY, C.9.2

DBMS_SCHEDULER, C.9.1

DBMS_SPACE_ADMIN, C.9.2

DBMS_SQL, C.9.1

DBMS_TRACE, C.9.1

DBMS_TRANSACTION, C.9.1

DBSNMP process, A.4.2

DDL Statements

that use DBLINKS, C.12.1

DDL statements

supported by SQL Apply, C

DDL transactions

applied on a logical standby database, 10.1.1.5

applying to a logical standby database, 10.1.1.5

DEFER attribute

LOG_ARCHIVE_DEST_STATE_n initialization parameter, 6.2.2

DELAY attribute, 15

LOG_ARCHIVE_DEST_n initialization parameter, 7.2.2

DELAY option

of ALTER DATABASE RECOVER MANAGED STANDBY DATABASE

cancelling, 7.2.2

delaying

application of archived redo log files, 15

application of redo log files, 7.2.2

deleting

archived redo log files

indicated by the DBA_LOGMNR_PURGED_LOG view, 10.4.2

not needed by SQL Apply, 10.4.2

deprecated attributes

on the LOG_ARCHIVE_DEST_n initialization parameter, 15

destinations

displaying with V$ARCHIVE_DEST view, 17

role-based definitions, 15

detecting

missing archived redo log files, 1.2.1, 1.7

DG_CONFIG attribute, 15

DGMGRL command-line interface

invoking failovers, 1.3, 8

simplifying switchovers, 1.3, 8

dictionary

building a LogMiner, 4.2.3.2

direct path inserts

SQL Apply DML considerations, 10.1.1.4

directory locations

Optimal Flexible Architecture (OFA), 2.4, 2.4

set up with ASM, 2.4

set up with OMF, 2.4

structure on standby databases, 2.4

disabling

a destination for archived redo log files, 6.2.2

disaster recovery

benefits, 1.7

configuring, 1.1.3

provided by Data Guard, 1

provided by standby databases, 1.1.3

disk I/O

controlling with the AFFIRM and NOAFFIRM attributes, 15

distributed transactions, C.13

DML

batch updates on a logical standby database, 10.1.1.4

DML transactions

applying to a logical standby database, 10.1.1.4

downgrading

Oracle Database software, B.6

DROP STANDBY LOGFILE clause

of ALTER DATABASE, A.1.1

DROP STANDBY LOGFILE MEMBER clause

of ALTER DATABASE, 16.1, 16.1, 16.1, A.1.1

dropping

online redo log files, 9.3.5

dynamic parameters

AQ_TM_PROCESSES, A.4.2

JOB_QUEUE_PROCESSES, A.4.2

E

ENABLE attribute

LOG_ARCHIVE_DEST_STATE_n initialization parameter, 6.2.2

ENABLE GUARD clause

of ALTER SESSION, 16.2

enabling

database guard on logical standby databases, 16.2

destinations for archived redo log files, 6.2.2

real-time apply

on logical standby databases, 7.4.1

on physical standby databases, 7.3.1

extensible indexes

supported by logical standby databases, C.1.2

F

failovers, 1.2.3

Data Guard broker, 1.3, 8

defined, 1.2.3, 8.1

displaying history with DBA_LOGSTDBY_HISTORY, 17

fast-start failover, 8

flashing back databases after, 8.4

logical standby databases and, 8.3.2

manual versus automatic, 1.2.3

performing backups after, 8.3.2

physical standby databases and, 16.1

preparing for, 8.1.4

simplifying with Data Guard broker, 8

transferring redo data before, 8.1.4

viewing characteristics for logical standby databases, 10.3.3

with maximum performance mode, 8.1.4

with maximum protection mode, 8.1.4

failure resolution policies

specifying for redo transport services, 15

fast-start failover

automatic failover, 1.3, 8

monitoring, 9.5

FGA_LOG$ table

replication on logical standbys, C.12.2

file specifications

renaming on the logical standby database, 10.5.3

Flashback Database

after a role transition, 8.4

after OPEN RESETLOGS, 13.3

after role transitions, 8.4

characteristics complementary to Data Guard, 1.6

physical standby database, 13.2.1

FORCE LOGGING clause

of ALTER DATABASE, 2.3.2, 3.1.1, 13.4, 13.4, 16.1

of ALTER TABLESPACE, 9.3.6

of CREATE DATABASE, 13.4

G

gap management

automatic detection and resolution, 1.2.1, 1.7

detecting missing log files, 1.7

registering archived redo log files

during failover, 8.3.2

GV$INSTANCE view, D.3.1

H

high availability

benefits, 1.7

provided by Data Guard, 1

provided by Oracle RAC and Data Guard, 1.6

I

idle state, 10.4.1

Image data types

in logical standby databases, C.1.2

incarnation of a database

changed, 9.4, 9.4

initialization parameters

DB_UNIQUE_NAME, 3.1.4, A.4.3

LOG_ARCHIVE_MIN_SUCCEED_DEST, 15

LOG_ARCHIVE_TRACE, F.2

LOG_FILE_NAME_CONVERT, E.2.2.4

modifying for physical standby databases, 3.2.3

setting for both the primary and standby roles, 15

INITIALIZING state, 10.4.1

INSTANTIATE_TABLE procedure

of DBMS_LOGSTDBY, 10.5.5

J

JOB_QUEUE_PROCESSES dynamic parameter, A.4.2

K

KEEP IDENTITY clause, 4.2.4.1

L

latency

on logical standby databases, 10.1.1.4, 10.1.1.5

listener.ora file

configuring, 3.2.5

redo transport services tuning and, A.7

troubleshooting, A.1.2, A.7

loading dictionary state, 10.4.1

LOCATION attribute, 15

setting

LOG_ARCHIVE_DEST_n initialization parameter, A.2

log apply services

Redo Apply

monitoring, 9.5.1

starting, 9.1.1

stopping, 9.1.2

tuning for Redo Apply, 9.6

log writer process (LGWR)

ASYNC network transmission, 15

NET_TIMEOUT attribute, 15

SYNC network transmission, 15

LOG_ARCHIVE_CONFIG initialization parameter, 3.1.4, 3.1.4, 3.2.3

example, 15

listing unique database names defined with, 17

relationship to DB_UNIQUE_NAME parameter, 14

relationship to DG_CONFIG attribute, 15

LOG_ARCHIVE_DEST_n initialization parameter

AFFIRM attribute, 15

ALTERNATE attribute, 15, 15, A.2

ASYNC attribute, 15

COMPRESSION attribute, 15

DB_UNIQUE_NAME attribute, 15

DELAY attribute, 7.2.2, 15

deprecated attributes, 15

LOCATION attribute, 15, A.2

MANDATORY attribute, 15

MAX_CONNECTIONS attribute, 15

MAX_FAILURE attribute, 15

NET_TIMEOUT attribute, 15

NOAFFIRM attribute, 15

NOALTERNATE attribute, A.2

NODELAY attribute, 7.2.2

NOREGISTER attribute, 15

REOPEN attribute, 15, 15

SERVICE attribute, 15

SYNC attribute, 15

VALID_FOR attribute, 15

LOG_ARCHIVE_DEST_STATE_n initialization parameter

ALTERNATE attribute, 6.2.2

DEFER attribute, 6.2.2

ENABLE attribute, 6.2.2

LOG_ARCHIVE_MAX_PROCESSES initialization parameter

relationship to MAX_CONNECTIONS, 15

LOG_ARCHIVE_MIN_SUCCEED_DEST initialization parameter, 15

LOG_ARCHIVE_TRACE initialization parameter, F.2

LOG_FILE_NAME_CONVERT initialization parameter

setting at standby site after a switchover, A.4.4

setting on physical standby databases, 3.2.3

when planning standby location and directory structure, 2.4

logical change records (LCR)

converted by PREPARER process, 10.1

exhausted cache memory, 10.1.1.2

staged, 10.1

logical standby databases, 1.1.2

adding

datafiles, A.10.1.1

indexes, 2.1.2, 10.5.4.1

tables, 10.5.5

background processes, 10.1

benefits, 2.1.2

controlling user access to tables, 10.2

creating, 4

converting from a physical standby database, 4.2.4.1

with Data Guard broker, 1.3

data types

supported, C, C.1.1

unsupported, C.1.2

database guard

overriding, 10.5.4

executing SQL statements on, 1.1.2

failovers, 8.3.2

displaying history of, 17, 17

handling failures, A.3

viewing characteristics with V$LOGSTDBY_STATS, 10.3.3

logical standby process (LSP) and, 10.1

materialized views

creating on, 2.1.2

support for, C.11

monitoring, 7.4.3, 17

renaming the file specification, 10.5.3

setting up a skip handler, 10.5.3

SQL Apply, 1.2.2

resynchronizing with primary database branch of redo, 10.6.5

skipping DDL statements, C.11

skipping SQL statements, C.11

starting real-time apply, 7.4.1

stopping, 7.4.2

technology, 7.1

transaction size considerations, 10.1.1.1

starting

real-time apply, 7.4.1, 7.4.1

states

applying, 10.4.1

idle, 10.4.1

initializing, 10.4.1

loading dictionary, 10.4.1

waiting on gaps, 10.4.1

support for primary databases with Transparent Data Encryption, C.2

switchovers, 8.3.1, 8.3.1

throughput and latency, 10.1.1.4, 10.1.1.5

upgrading, B.3

rolling upgrades, 2.3.2

logical standby process (LSP)

COORDINATOR process, 10.1

LogMiner dictionary

using DBMS_LOGSTDBY.BUILD procedure to build, 4.2.3.2

when creating a logical standby database, 4.2.4.1

M

managed recovery operations

See Redo Apply

MANDATORY attribute, 15

materialized views

creating on logical standby databases, 2.1.2

MAX_CONNECTIONS attribute

configuring Oracle RAC for parallel archival, 15

reference, 15

MAX_FAILURE attribute, 15

maximum availability mode

introduction, 1.4

maximum performance mode, 8.1.4

introduction, 1.4

maximum performance protection mode, 5.1

maximum protection mode

for Oracle Real Application Clusters, D.2.2

introduction, 1.4

standby databases and, 8.1.4

memory

exhausted LCR cache, 10.1.1.2

missing log sequence

N

NET_TIMEOUT attribute, 15

network connections

configuring multiple, 15

in an Oracle RAC environment, 15

network I/O operations

network timers

NET_TIMEOUT attribute, 15

tuning

redo transport services, A.7

network timeouts

acknowledging, 15

no data loss

data protection modes overview, 1.4

ensuring, 1.2.3

guaranteeing, 1.2.3

provided by maximum availability mode, 1.4

provided by maximum protection mode, 1.4

NOAFFIRM attribute, 15

NOALTERNATE attribute

LOG_ARCHIVE_DEST_n initialization parameter, A.2

NODELAY attribute

LOG_ARCHIVE_DEST_n initialization parameter, 7.2.2

NOREGISTER attribute, 15

O

OMF

See Oracle Managed Files (OMF)

on-disk database structures

physical standby databases, 1.1.2

online redo log files

adding, 9.3.5

dropping, 9.3.5

OPEN READ ONLY clause

of ALTER DATABASE, 16.1

OPEN RESETLOGS

flashing back after, 13.3

OPEN RESETLOGS clause

database incarnation change, 9.4, 9.4

of ALTER DATABASE, 3.2.2, 9.5

recovery, 9.4, 9.4

operational requirements, 2.3, 2.3.2

Optimal Flexible Architecture (OFA)

directory structure, 2.4, 2.4

ORA-01102 message

causing switchover failures, A.4.3

Oracle Automatic Storage Management (ASM), 2.4

Oracle Database software

requirements for upgrading with SQL Apply, 12.2

upgrading, 2.3.2, B.1

upgrading with SQL Apply, 12.1

Oracle Enterprise Manager

invoking failovers, 1.3, 8

invoking switchovers, 1.3, 8

Oracle Managed Files (OMF), 2.4

creating a standby database that uses, 13.5

Oracle Net

communication between databases in a Data Guard configuration, 1.1

Oracle Real Application Clusters

characteristics complementary to Data Guard, 1.6

configuring for multiple network connections, 15

primary databases and, 1.1.1, D.1.1

setting

maximum data protection, D.2.2

standby databases and, 1.1.2, D.1

Oracle Recovery Manager utility (RMAN)

backing up files on a physical standby database, 11

Oracle Standard Edition

simulating a standby database environment, 2.3.2

P

pageout considerations, 10.1.1.2

pageouts

SQL Apply, 10.1.1.2

parallel DML (PDML) transactions

SQL Apply, 10.1.1.3, 10.1.1.4

patch set releases

upgrading, 2.3.2

performance

balancing against data availability, 1.7

balancing against data protection, 1.7

physical standby databases

and Oracle Active Data Guard, 2.1.1

applying redo data, 7.1, 7.3

Redo Apply technology, 7.3

applying redo log files

starting, 7.3.1

benefits, 2.1.1

configuration options, 2.4

converting datafile path names, 3.2.3

converting log file path names, 3.2.3

converting to a logical standby database, 4.2.4.1

creating

checklist of tasks, 3.2

configuring a listener, 3.2.5

directory structure, 2.4

initialization parameters for, 3.2.3

with Data Guard broker, 1.3

defined, 1.1.2

failover

checking for updates, 8.1.4

flashing back after failover, 13.2.1

monitoring, 7.3.3, 9.5.1, 17

opening for read-only or read/write access, 9.2

read-only, 9.2

recovering through OPEN RESETLOGS, 9.4

Redo Apply, 1.2.2

resynchronizing with primary database branch of redo, 9.4, 9.4

role transition and, 8.2

rolling forward with BACKUP INCREMENTAL FROM SCN command, 11.10

shutting down, 9.1.2

starting

apply services, 7.3.1

real-time apply, 7.3.1

synchronizing with the primary database, 11.10

tuning the log apply rate, 9.6

upgrading, B.2

using transportable tablespaces, 9.3.3

PL/SQL supplied packages

supported, C.9.1

unsupported, C.9.2

PREPARE TO SWITCHOVER clause

of ALTER DATABASE, 8.3.1, 8.3.1, 16.1

PREPARER process, 10.1

staging LCRs in SGA, 10.1

primary database

backups and, 8.3.2

configuring

on Oracle Real Application Clusters, 1.1.1

single-instance, 1.1.1

datafiles

adding, 9.3.1

defined, 1.1.1

failover and, 8.1

gap resolution, 1.7

initialization parameters

and physical standby database, 3.2.3

monitoring events on, 9.5

network connections

avoiding network hangs, 15

handling network timeouts, 15

Oracle Real Application Clusters and

setting up, D.1.1

preparing for

physical standby database creation, 3.1

prerequisite conditions for

logical standby database creation, 4.1

redo transport services on, 1.2.1

reducing workload on, 1.7

switchover, 8.1.3

tablespaces

adding, 9.3.1

primary databases

ARCHIVELOG mode, 2.3.2

software requirements, 2.3.2

primary key columns

logged with supplemental logging, 4.2.3.2, 10.1.1.4

primary role, 1.1.1

processes

CJQ0, A.4.2

DBSNMP, A.4.2

preventing switchover, A.4.2

QMN0, A.4.2

SQL Apply architecture, 10.1, 10.4.1

protection modes

maximum availability mode, 1.4

maximum performance, 5.1

maximum performance mode, 1.4

maximum protection mode, 1.4

monitoring, 9.5

setting on a primary database, 5.2

Q

QMN0 process, A.4.2

queries

offloading on the standby database, 1.7

R

READER process, 10.1

read-only operations, 1.2.2

physical standby databases and, 9.2

real-time apply

defined, 7.2.1

overview of log apply services, 1.2

starting, 7.3.1

on logical standby, 7.4.1

starting on logical standby databases, 7.4.1

starting on physical standby databases, 7.3.1

stopping

on logical standby, 7.4.2

on physical standby databases, 9.1.2

tracing data with LOG_ARCHIVE_TRACE initialization parameter, F.2

real-time query feature, 9.2

and Oracle Active Data Guard, 9.2, 9.2.1

configuring apply lag tolerance, 9.2.1.2

forcing Redo Apply synchronization, 9.2.1.3

monitoring apply lag, 9.2.1.1

restrictions, 9.2.1.4

using, 9.2.1

RECORD_UNSUPPORTED_OPERATIONS

example, 10.5.1

RECOVER MANAGED STANDBY DATABASE CANCEL clause

aborting, 4.2.4.1

RECOVER MANAGED STANDBY DATABASE clause

canceling the DELAY control option, 7.2.2

of ALTER DATABASE, 3.2.6, 4.2.5, 7.3.1, 16.1, 16.1, 16.1, 16.1

background process, 7.3.1

controlling Redo Apply, 7.3.1, 11.8.2

foreground session, 7.3.1

overriding the delay interval, 7.2.2

starting real time apply, 7.3.1

RECOVER TO LOGICAL STANDBY clause

converting a physical standby database to a logical standby database, 4.2.4.1

recovering

from errors, A.10.1

logical standby databases, 10.6.5

physical standby databases

after an OPEN RESETLOGS, 9.4, 9.4

through resetlogs, 9.4, 10.6.5

Recovery Manager

characteristics complementary to Data Guard, 1.6

commands

DUPLICATE, E.2.1

standby database

creating, E.2.1

LOG_FILE_NAME_CONVERT initialization parameter, E.2.2.4

preparing using RMAN, E.2.2

re-creating

a table on a logical standby database, 10.5.5

Redo Apply

defined, 1.2.2, 7.1

flashing back after failover, 13.2.1

starting, 3.2.6, 7.3.1

stopping, 9.1.2

technology, 1.2.2

tuning the log apply rate, 9.6

redo data

applying

through Redo Apply technology, 1.2.2

through SQL Apply technology, 1.2.2

to standby database, 7.1

to standby databases, 1.1.2

applying during conversion of a physical standby database to a logical standby database, 4.2.4.1

archiving on the standby system, 1.2.2, 7.1

building a dictionary in, 4.2.3.2

cascading, 6.3

manually transferring, 2.3.2

transmitting, 1.1.2, 1.2.1

redo gaps, 6.4.3

manual resolution, 6.4.3.1

reducing resolution time, 6.4.3

redo log files

delaying application, 7.2.2

redo logs

automatic application on physical standby databases, 7.3.1

update standby database tables, 1.7

redo transport services, 6

archive destinations

alternate, A.2

re-archiving to failed destinations, 15

authenticating sessions

using a password file, 6.2.1.2

using SSL, 6.2.1.1

configuring, 6.2

configuring security, 6.2.1

defined, 1.2.1

gap detection, 6.4.3

handling archive failures, 15

monitoring status, 6.4.1

network

tuning, A.7

protection modes

maximum availability mode, 1.4

maximum performance mode, 1.4

maximum protection mode, 1.4

receiving redo data, 6.2.3

sending redo data, 6.2.2

synchronous and asynchronous disk I/O, 15

wait events, 6.4.4

of ALTER DATABASE, 16.1, A.4.1

of ALTER DATABASE, 8.3.2

registering

archived redo log files

during failover, 8.3.2

RELY constraint

creating, 4.1.2

remote file server process (RFS)

log writer process and, 7.2.1

RENAME FILE clause

of ALTER DATABASE, A.1.1, A.1.1

renaming

datafiles

on the primary database, 9.3.4

setting the STANDBY_FILE_MANAGEMENT parameter, 9.3.4

REOPEN attribute, 15, 15

reporting operations

configuring, 1.1.3

offloading on the standby database, 1.7

performing on a logical standby database, 1.1.2

requirements

of a rolling upgrade, 12.2

restart considerations

SQL Apply, 10.1.1.3

resynchronizing

logical standby databases with a new branch of redo, 10.6.5

physical standby databases with a new branch of redo, 9.4, 9.4

retrieving

missing archived redo log files, 1.2.1, 1.7

RMAN

incremental backups, 11.10

rolling forward physical standby databases, 11.10

RMAN BACKUP INCREMENTAL FROM SCN command, 11.10

RMAN backups

accessibility in Data Guard environment, 11.1.3

association in Data Guard environment, 11.1.2

interchangeability in Data Guard environment, 11.1.1

role management services

defined, 8

role transition triggers, 8.1.5

DB_ROLE_CHANGE system event, 8.1.5

role transitions, 1.2.3, 8.1

choosing a type of, 8.1.1

defined, 1.2.3

flashing back the databases after, 8.4

logical standby database and, 8.3

monitoring, 9.5

physical standby databases and, 8.2

reversals, 1.2.3, 8.1

role-based destinations

setting, 15

rollback

after switchover failures, A.4.5

rolling upgrade

software requirements, 2.3.2

rolling upgrades

benefits, 12.1

patch set releases, 2.3.2

requirements, 12.2

setting the COMPATIBLE initialization parameter, 12.2, 12.5, 12.5

unsupported data types and storage attributes, 12.4

use of KEEP IDENTITY clause, 4.2.4.1

ROWID data types

in logical standby databases, C.1.2

S

scenarios

recovering

after NOLOGGING is specified, 13.4

schemas

identical to primary database, 1.1.2

SCN

using for incremental backups, 11.10

sequences

unsupported on logical standby databases, C.10

SERVICE attribute, 15

SET STANDBY DATABASE clause

of ALTER DATA, 16.1

of ALTER DATABASE, 8.1.4, 16.1

shutting down

physical standby database, 9.1.2

simulating

standby database environment, 2.3.2

skip handler

setting up on a logical standby database, 10.5.3

SKIP procedure

of DBMS_LOGSTDBY, A.6

SKIP_ERROR procedure

of the DBMS_LOGSTDBY package, A.3

SKIP_TRANSACTION procedure

of DBMS_LOGSTDBY, A.6

snapshot standby databases, 1.1.2

managing, 9.7

software requirements, 2.3.2

rolling upgrades, 2.3.2, 2.3.2

Spatial data types

in logical standby databases, C.1.2

SQL Apply, 7.4.2, 10.1.1.2

after an OPEN RESETLOGS, 10.6.5

ANALYZER process, 10.1

APPLIER process, 10.1

applying CREATE TABLE AS SELECT (CTAS) statements, 10.1.1.5

applying DDL transactions, 10.1.1.5, 10.1.1.5

applying DML transactions, 10.1.1.4

architecture, 10.1, 10.4.1

BUILDER process, 10.1

COORDINATOR process, 10.1

defined, 1.2.2, 7.1

deleting archived redo log files, 10.4.2

parallel DML (PDML) transactions, 10.1.1.3, 10.1.1.4

performing a rolling upgrade, 12.1

PREPARER process, 10.1

READER process, 10.1

requirements for rolling upgrades, 12.2

restart considerations, 10.1.1.3

rolling upgrades, 2.3.2

starting

real-time apply, 7.4.1

stopping

real-time apply, 7.4.2

support for DDL statements, C

support for PL/SQL supplied packages, C.9.1

supported data types, C.1.1

transaction size considerations, 10.1.1.1

unsupported data types, C.1.2

unsupported PL/SQL supplied packages, C.9.2

viewing current activity, 10.1

of processes, 10.1

what to do if it stops, A.6

SQL sessions

causing switchover failures, A.4.2

SQL statements

executing on logical standby databases, 1.1.2, 1.2.2

skipping on logical standby databases, C.11

standby database

creating logical, 4

standby databases

about creating using RMAN, E.2.1

apply services on, 7.1

applying redo data on, 7

applying redo log files on, 1.2.2, 1.7

ARCn processes using multiple network connections, 15

configuring, 1.1

maximum number of, 2

on Oracle Real Application Clusters, 1.1.2, D.1

on remote locations, 1.1.3

single-instance, 1.1.2

creating, 1.1.2, 3

checklist of tasks, 4.2

directory structure considerations, 2.4

if primary uses ASM or OMF, 13.5

on remote host with same directory structure, E.3

with a time lag, 7.2.2

defined, 2.1

failover

preparing for, 8.1.4

failover to, 8.1.4

LOG_FILE_NAME_CONVERT initialization parameter, E.2.2.4

operational requirements, 2.3, 2.3.2

preparing to use RMAN, E.2.2

recovering through OPEN RESETLOGS, 9.4

resynchronizing with the primary database, 1.7

rolling forward with RMAN incremental backups, 11.10

SET AUXNAME command, E.2.2.4

SET NEWNAME command, E.2.2.4

software requirements, 2.3.2

starting apply services on physical, 7.3.1

T

tables

logical standby databases

adding on, 10.5.5

re-creating tables on, 10.5.5

unsupported on, C.10

tablespaces

adding

a new datafile, A.10.1.1

to primary database, 9.3.1

monitoring status changes, 9.5

moving between databases, 9.3.3

target standby database

for switchover, 8.1.2

terminating

network connection, 15

text indexes

supported by logical standby databases, C.1.2

throughput

on logical standby databases, 10.1.1.4, 10.1.1.5

time lag

delaying application of archived redo log files, 7.2.2, 15

in standby database, 7.2.2, 15

TIME_COMPUTED column, 8.1.2

TIME_COMPUTED column of the V$DATAGUARD_STATS view, 8.1.2

tnsnames.ora file

redo transport services tuning and, A.7

troubleshooting, A.1.2, A.4.4, A.7

trace files

levels of tracing data, F.2

setting, F.1

tracking real-time apply, F.2

transaction size considerations

SQL Apply, 10.1.1.1

Transparent Data Encryption

support by SQL Apply, C.2

transportable tablespaces

using with a physical standby database, 9.3.3

triggers

handled on a logical standby database, 10.6.3

role transitions, 8.1.5

troubleshooting

if SQL Apply stops, A.6

last redo data was not transmitted, A.4.1

listener.ora file, A.1.2, A.7

logical standby database failures, A.3

processes that prevent switchover, A.4.2

SQL Apply, A.6

switchovers, A.4

active SQL sessions, A.4.2

ORA-01102 message, A.4.3

roll back and start over, A.4.5

tnsnames.ora file, A.1.2, A.4.4, A.7

tuning

log apply rate for Redo Apply, 9.6

U

unique-index columns

logged with supplemental logging, 4.2.3.2, 10.1.1.4

unrecoverable operations, 13.4.2

backing up after, 13.4.3

unsupported data types

during a rolling upgrade, 12.4

unsupported operations

capturing in DBA_LOGSTDBY_EVENTS view, 10.5.1

unsupported PL/SQL supplied packages, C.9.2

upgrading

Oracle Database software, 2.3.2, 12.1, B, B.1

setting the COMPATIBLE initialization parameter, B.4

UROWID data types

in logical standby databases, C.1.2

user-defined data types

in logical standby databases, C.1.2

USING CURRENT LOGFILE clause

starting real time apply, 7.3.1

V

V$ARCHIVE_DEST view, 17, A.1.2

displaying information for all destinations, 17

V$ARCHIVE_DEST_STATUS view, 17

V$ARCHIVE_GAP view, 17

V$ARCHIVED_LOG view, 9.5.1.3, 17, A.4.1

V$DATABASE view, 17

monitoring fast-start failover, 9.5

SWITCHOVER_STATUS column and, A.4.1

V$DATABASE_INCARNATION view, 17

V$DATAFILE view, 13.4.2, 13.4.3, 17

V$DATAGUARD_CONFIG view, 17

listing database names defined with LOG_ARCHIVE_CONFIG, 17

V$DATAGUARD_STATS view, 8.1.2, 17

V$DATAGUARD_STATUS view, 9.5.1.5, 17

V$FS_FAILOVER_STATS view, 17

V$LOG view, 17

V$LOG_HISTORY view, 9.5.1.4, 17

V$LOGFILE view, 17

V$LOGSTDBY_PROCESS view, 10.1, 10.3.4, 10.3.4, 10.4.1, 10.7.3.1, 10.7.3.2, 17

V$LOGSTDBY_PROGRESS view, 10.3.5, 17

RESTART_SCN column, 10.1.1.3

V$LOGSTDBY_STATE view, 8.1.2, 10.3.6, 10.4.1, 17

V$LOGSTDBY_STATS view, 10.1, 10.3.7, 17

failover characteristics, 10.3.3

V$LOGSTDBY_TRANSACTION view, 17

V$MANAGED_STANDBY view, 9.5.1.2, 9.5.1.2, 17

V$REDO_DEST_RESP_HISTOGRAM

using to monitor synchronous redo transport response time, 6.4.2

V$REDO_DEST_RESP_HISTOGRAM view, 17

V$SESSION view, A.4.2

V$STANDBY_EVENT_HISTOGRAM view, 17

V$STANDBY_LOG view, 17

V$THREAD view, 9.5

VALID_FOR attribute, 15

verifying

logical standby databases, 4.2.6

physical standby databases, 3.2.7

versions

upgrading Oracle Database software, 12.1

views

DBA_LOGSTDBY_EVENTS, 10.3.1, 17, A.6

DBA_LOGSTDBY_HISTORY, 17

DBA_LOGSTDBY_LOG, 10.3.2, 17

DBA_LOGSTDBY_NOT_UNIQUE, 17

DBA_LOGSTDBY_PARAMETERS, 17

DBA_LOGSTDBY_SKIP, 17

DBA_LOGSTDBY_SKIP_TRANSACTION, 17

DBA_LOGSTDBY_UNSUPPORTED, 17

GV$INSTANCE, D.3.1

V$ARCHIVE_DEST, 17, A.1.2

V$ARCHIVE_DEST_STATUS, 17

V$ARCHIVED_GAP, 17

V$ARCHIVED_LOG, 9.5.1.3, 17

V$DATABASE, 17

V$DATABASE_INCARNATION, 17

V$DATAFILE, 13.4.2, 13.4.3, 17

V$DATAGUARD_CONFIG, 17

V$DATAGUARD_STATS, 17

V$DATAGUARD_STATUS, 9.5.1.5, 17

V$FS_FAILOVER_STATS, 17

V$LOG, 17

V$LOG_HISTORY, 9.5.1.4, 17

V$LOGFILE, 17

V$LOGSTDBY_PROCESS, 10.1, 10.3.4, 17

V$LOGSTDBY_PROGRESS, 10.3.5, 17

V$LOGSTDBY_STATE, 10.3.6, 17

V$LOGSTDBY_STATS, 10.1, 10.3.7, 17

V$LOGSTDBY_TRANSACTION, 17

V$MANAGED_STANDBY, 9.5.1.2, 9.5.1.2, 17

V$REDO_DEST_RESP_HISTOGRAM, 17

V$SESSION, A.4.2

V$STANDBY_EVENT_HISTOGRAM, 17

V$STANDBY_LOG, 17

V$THREAD, 9.5

W

wait events

for redo transport services, 6.4.4

WAITING FOR DICTIONARY LOGS state, 10.4.1

waiting on gap state, 10.4.1

Z

zero downtime instantiation

logical standby databases, 4.2