Index

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

A

activating

a clone database, 12.6

a logical standby database, 7.3.2, 15.1, B.3

a physical standby database, 7.2.2, 10.2.6, 12.6, 12.6, 12.8.2, 15.1

a read/write physical standby database, 12.6

activating a clone database, 12.6

adding

data files, 8.3.1, A.9.1.1, A.9.1.1

indexes on logical standby databases, 1.6, 2.1.2, 9.4.5.1

new or existing standby databases, 1.3

online redo log files, 5.7.3.1, 8.3.5, 8.3.5, 8.3.5

standby redo log, 3.1.3

standby redo log group members, 5.7.3.2

tablespaces, 8.3.1

adjusting

initialization parameter file

for logical standby database, 4.2.4.3

AFFIRM attribute, 5.6.2, 14

ALTER DATABASE statement

ABORT LOGICAL STANDBY clause, 15.1

ACTIVATE STANDBY DATABASE clause, 7.2.2, 7.3.2, 10.2.6, 12.6, 12.6, 12.8.2, 15.1, 15.1

ACTIVATE STANDBY DATABASE statement, 12.6

ADD STANDBY LOGFILE clause, 3.1.3, 8.3.5, 15.1, A.1.2

ADD STANDBY LOGFILE GROUP clause, 3.1.3

ADD STANDBY LOGFILE MEMBER clause, 5.7.3.2, 5.7.3.2, 5.7.3.2, 15.1, A.1.2, A.1.2

ADD SUPPLEMENTAL LOG DATA clause, 15.1

ALTER STANDBY LOGFILE clause, 3.1.3, 3.1.3

ALTER STANDBY LOGFILE GROUP clause, 3.1.3

CLEAR UNARCHIVED LOGFILES clause, 8.5

COMMIT TO SWITCHOVER clause, 7.2.1, 7.2.2, 7.3.1, 7.3.1, 7.3.1, 12.8.3, 12.8.3, 15.1

in Real Application Clusters, D.3.1

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

CREATE CONTROLFILE clause, 8.5

CREATE DATAFILE AS clause, A.1.2

CREATE STANDBY CONTROLFILE clause, 3.2.2, A.1.4

REUSE clause, 15.1

DROP LOGFILE clause, A.1.2

DROP STANDBY LOGFILE MEMBER clause, 15.1, 15.1, 15.1, A.1.2

FORCE LOGGING clause, 2.3.2, 3.1.1, 12.10, 12.10, 15.1

MOUNT STANDBY DATABASE clause, 15.1

OPEN READ ONLY clause, 15.1

OPEN RESETLOGS clause, 3.2.2, 8.5

PREPARE TO SWITCHOVER clause, 7.3.1, 7.3.1, 15.1

RECOVER MANAGED STANDBY DATABASE clause, 3.2.6, 4.2.5, 6.2.2, 8.2.2, 12.2.1, 12.8.2, 15.1, 15.1, 15.1

background process, 6.3.1, 8.1.1

canceling, 6.3.3

canceling log apply services, 8.2.2

controlling Redo Apply, 6.3.1

failover, 15.1

foreground session, 6.3.1

initiating failover, 7.2.2

overriding the delay interval, 6.2.2, 14

starting real time apply, 6.3.2

switchover scenario, 12.8.3

RENAME FILE clause, 8.3.3, A.1.2, A.1.2

SET STANDBY DATABASE clause

TO MAXIMIZE AVAILABILITY clause, 15.1

TO MAXIMIZE PERFORMANCE clause, 7.1.4

TO MAXIMIZE PROTECTION clause, 15.1

START LOGICAL STANDBY APPLY clause, 6.4.1, 7.3.2, 11.5, A.5

IMMEDIATE keyword, 6.4.2, 9.4.1

NEW PRIMARY keyword, 7.3.2

starting SQL Apply, 4.2.5

STOP LOGICAL STANDBY APPLY clause, 6.4.3, 7.3.2, 11.5, 12.2.2, 15.1

ALTER SESSION DISABLE GUARD statement

overriding the database guard, 9.4.5

ALTER SESSION GUARD DISABLE

disabling the database guard to define a database link, 7.3.2

ALTER SESSION statement

GUARD ENABLE clause, 15.2

ALTER SYSTEM statement

ARCHIVE LOG CURRENT clause, 3.2.6, 3.2.7, 12.9

ALTER TABLESPACE statement, 8.3.4, 12.10.2, A.9.1.1

FORCE LOGGING clause, 8.3.6

alternate archive destinations

setting up initialization parameters for, A.2

ALTERNATE attribute, 14, 14

LOG_ARCHIVE_DEST_n initialization parameter, A.2

LOG_ARCHIVE_DEST_STATE_n initialization parameter, 5.2.2

ANALYZER process, 9.1

APPLIED_SCN column

of V$LOGSTDBY_PROGRESS view, 12.2.2

APPLIER process, 9.1

applying

redo data immediately, 6.2.1

redo data on standby database, 1.2, 1.2.2, 2.1.1, 6

SQL statements to logical standby databases, 6.4

applying state, 9.3.1

AQ_TM_PROCESSES dynamic parameter, A.4.2

ARCH attribute, 14

LOG_ARCHIVE_DEST_n initialization parameter

setting for data protection, 5.6.2

archive destinations

alternate, A.2

archive gap

registering missing log files, 5.8.4

archive gaps

causes of, 12.11.1

defined, 5.8

finding with DBA_LOGSTDBY_LOG view, 5.8.4

finding with V$ARCHIVE_GAP view, 5.8.4

identifying the logs, 12.11.2

manually applying redo logs to standby database, 12.11.4

manually copying the logs in, 12.11.3

manually resolving on a physical standby database, 5.8.4

preventing, 12.11.1.2

registering missing log files, 5.8.4

ARCHIVE LOG CURRENT clause

of ALTER SYSTEM, 3.2.6, 3.2.7, 12.9

archive tracing

standby databases and, 5.9.1, G.1

archived redo log files

accessing information about, 8.5.3.6, 8.5.4.4

affected by COMPATIBLE initialization parameter, 5.7.1

applying

Redo Apply technology, 1.2.2

SQL Apply technology, 1.2.2

delaying application, 12.8, 14

on the standby database, 6.2.2

deleting unneeded, 9.3.2

destinations

disabling, 5.2.2

displaying with DBA_LOGSTDBY_LOG view, 12.2.2

displaying with V$ARCHIVE_DEST_STATUS view, 16

enabling, 5.2.2

determining the most recently archived, 5.9.1

finding gaps on logical standby databases, 5.8.4

finding gaps on physical standby databases, 5.8.4, 5.8.4

listing, 12.2.2

managing gaps, 1.6, 5.8, 5.8

B

BACKUP INCREMENTAL FROM SCN command

scenarios using, 12.7

backup operations

after failovers, 7.2.2, 7.3.2

after unrecoverable operations, 12.10.3, 12.10.3

configuring on a physical standby database, 1.1.3

data files, 12.10.2

DB_FILE_NAME_CONVERT option of the RMAN DUPLICATE command, F.1.3

offloading on the standby database, 1.6

primary databases, 1.1.2

used by the broker, 1.3

using RMAN, 10

basic readable standby database See simulating a standby database environment

batch processing

on a logical standby database, 9.1.1.4

benefits

Data Guard, 1.6

logical standby database, 2.1.2

of a rolling upgrade, 11.1

physical standby database, 2.1.1

standby redo logs versus archived redo logs, 2.5.2

BFILE data types

in logical standby databases, C.1.2

BINARY_DEGREE data types

in logical standby databases, C.1.1

BINARY_FLOAT data types

in logical standby databases, C.1.1

BLOB data types

in logical standby databases, C.1.1

broker

command-line interface, 1.6

defined, 1.3

graphical user interface, 1.6

BUILDER process, 9.1

C

CANCEL option

managed recovery and, 8.1.2

canceling

log apply services, 8.2.2, 8.2.2

cascaded destinations

defined, E

for logical standby databases, E.1.2

for physical standby databases, E, E.1.1

materialized view on logical standby databases, E.3.3

require standby redo log files, 2.5.2

role transitions, E.2

Redo Apply, E.2.1

SQL Apply, E.2.2

scenario, E.3.1

CHAR data types

in logical standby databases, C.1.1

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

chunking

transactions, 9.1.1.1

CJQ0 process, A.4.2

CLEAR UNARCHIVED LOGFILES clause

of ALTER DATABASE, 8.3, 8.5

CLOB data types

in logical standby databases, C.1.1

clone database

ACTIVATE STANDBY DATABASE clause, 12.6

activating, 12.6

activating a physical standby database, 12.6

creating a restore point for, 12.6

creating restore point for, 12.6

DB_RECOVERY_FILE_DEST initialization parameter, 12.6

DB_RECOVERY_FILE_DEST_SIZE initialization parameter, 12.6

clone databases

converting a physical standby database to, 12.6

cloning

a physical standby database, 12.6

activating a read/write database, 12.6

CREATE RESTORE POINT command, 12.6

creating a restore point, 12.6

cluster tables

in logical standby databases, C.2.1

collections data types

in logical standby databases, C.1.2

command-line interface

broker, 1.6

commands, Recovery Manager

DUPLICATE, F.1.1

COMMIT TO SWITCHOVER clause

of ALTER DATABASE, 7.2.1, 7.2.2, 7.3.1, 7.3.1, 12.8.3, 12.8.3, 15.1

in Real Application Clusters, D.3.1

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

COMMIT TO SWITCHOVER TO PRIMARY clause

of ALTER DATABASE, 7.3.1

communication

between databases in a Data Guard configuration, 1.1

COMPATIBLE initialization parameter

effect on directory location for archived redo log files, 5.7.1

setting for a rolling upgrade, 11.2, 11.4, 11.5

complementary technologies, 1.5

configuration options

creating with Data Guard broker, 1.3

of redo logs, 2.5.1

overview, 1.1

physical standby databases

location and directory structure, 2.4

requirements for password files, 5.3.3

standby databases

archived redo log repository, 5.2.1

delayed application of archived redo log files on, 12.8

delayed standby, 6.2.2

typical, 1.1.3

configuring

backups on standby databases, 1.1.3

cascaded destinations, E.1.1

disaster recovery, 1.1.3

initialization parameters

for alternate archive destinations, A.2

for physical standby database, 3.2.3

to create a standby database with a time lag, 12.8

to set up redo transport services, 5.2.2

listener for physical standby databases, 3.2.5

no data loss, 1.2.3

physical standby databases, 2.4

redo logs, 2.5.1

reporting operations on a logical standby database, 1.1.3

standby databases at remote locations, 1.1.3

standby redo log files, 3.1.3, 3.1.3

standby redo log groups, 3.1.3, 3.1.3

constraints

handled on a logical standby database, 9.5.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

modifying with ALTER DATABASE RENAME FILE statement, 8.3.3

planning growth of, 5.7.4

switchover and, 7.2.1

CONTROL_FILE_RECORD_KEEP_TIME initialization parameter, 5.7.4.2

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

LSP background process, 9.1

copying

control files, 3.2.4

CREATE CONTROLFILE clause

of ALTER DATABASE, 8.5

CREATE DATABASE statement

FORCE LOGGING clause, 12.10

CREATE DATAFILE AS clause

of ALTER DATABASE, A.1.2

CREATE RESTORE POINT command, 12.6

CREATE RESTORE POINT statement

activating a clone database, 12.6

CREATE STANDBY CONTROLFILE clause

of ALTER DATABASE, 3.2.2, 15.1, A.1.4

CREATE TABLE AS SELECT (CTAS) statements

applied on a logical standby database, 9.1.1.5

creating

a new password file, 4.2.4.2

database link, 7.3.2

indexes on logical standby databases, 9.4.5.1

standby database

that use OMF, F.3.1, F.3.2

standby redo log files, 3.1.3

traditional initialization parameter file

for physical standby database, 3.2.3

cross-instance archival

in Real Application Clusters configurations, D.1.2

standby redo log files and, D.1.2

using the log writer process, D.1.2

D

data availability

balancing against system performance requirements, 1.6

data corruption

safeguarding against, 1.6

data files

adding to primary database, 8.3.1

deleting from the primary database, 8.3.2

monitoring, 8.5, 12.10.2

renaming on the primary database, 8.3.4

Data Guard broker

defined, 1.3

distributed management framework, 7

failovers, 1.3

fast-start, 7

manual, 1.3, 7

fast-start failover, 1.3

switchovers, 7

Data Guard configurations

archiving to standby destinations using the archive process, 5.2.2

archiving to standby destinations using the log writer process, 5.3.2.2, 6.2.1

defined, 1.1

protection modes, 1.4

redo transport services and, 5.1

upgrading Oracle Database software, B

data loss

due to failover, 1.2.3

minimizing, 7.2.2

switchover and, 7.1

data protection

balancing against performance, 1.6

benefits, 1.6

ensuring no data loss, 2.1.1

flexibility, 1.6

provided by Data Guard, 1

data protection modes

affect on network timeouts, 14

enforced by redo transport services, 1.2.1

influence on network reconnection, 14

maximum availability mode, 5.6.2

maximum performance mode, 5.6.2

maximum protection mode, 5.6.2

minimum set of requirements, 5.6.2

overview, 1.4, 1.4

setting up synchronous and asynchronous network I/O operations, 14

specifying, 5.6.2

Data Pump utility

using transportable tablespaces with physical standby databases, 8.3.3

data types

BFILE, C.1.2

BINARY_DEGREE, C.1.1

BINARY_FLOAT, C.1.1

BLOB, C.1.1

CHAR, C.1.1

CLOB, C.1.1

collections in logical standby databases, C.1.2

DATE, C.1.1

encrypted columns, C.1.2

INTERVAL, C.1.1

LONG, C.1.1

LONG RAW, C.1.1

NCHAR, C.1.1

NCLOB, C.1.1

NUMBER, C.1.1

NVARCHAR2, C.1.1

RAW, C.1.1

ROWID, C.1.2

Spatial, Image, and Context, C.1.2

TIMESTAMP, C.1.1

UROWID, C.1.2

user-defined, C.1.2

VARCHAR, C.1.1

VARCHAR2, C.1.1

XML type, C.1.2

database guard, 6.1

overriding, 9.4.5

database incarnation

changes with OPEN RESETLOGS, 8.4, 8.4

database link

creating, 7.3.2

database roles

primary, 1.1.1, 7.1

standby, 1.1.2, 7.1

transitions, 1.2.3

database schema

physical standby databases, 1.1.2

Database Upgrade Assistant (DBUA), B.1

databases

cascading standby databases See cascaded destinations

cloning, 12.6

failover and, 7.1.4

primary See primary database

role transition and, 7.1

surviving disasters and data corruptions, 1

upgrading software versions, 11.1

using password files, 5.3.3

DATE data types

in logical standby databases, C.1.1

DB_FILE_NAME_CONVERT initialization parameter

location for transportable tablespaces, 8.3.3

DB_FILE_NAME_CONVERT option

RMAN DUPLICATE command, F.1.3

DB_NAME initialization parameter, 3.1.4

DB_RECOVERY_FILE_DEST initialization parameter

setting for clone database, 12.6

setting up recovery areas, 5.2.3

DB_RECOVERY_FILE_DEST_SIZE initialization parameter

setting for clone database, 12.6

DB_ROLE_CHANGE system event, 7.1.3, 7.1.4

DB_UNIQUE_NAME attribute, 14

DB_UNIQUE_NAME initialization parameter, A.4.4

required for shared flash recovery areas, 5.2.3.4

required with LOG_ARCHIVE_CONFIG parameter, 13

setting database initialization parameters, 3.1.4

DBA_DATA_FILES view, 8.5

DBA_LOGMNR_PURGED_LOG view

list archived redo log files that can be deleted, 9.3.2

DBA_LOGSTDBY_EVENTS view, 9.2.1, 16, A.5

capturing logical standby, 11.4

DBA_LOGSTDBY_HISTORY view, 16

DBA_LOGSTDBY_LOG view, 9.2.2, 16

finding gaps on logical standby databases, 5.8.4

listing archived redo log files, 12.2.2

DBA_LOGSTDBY_NOT_UNIQUE view, 16

DBA_LOGSTDBY_PARAMETERS view, 16

DBA_LOGSTDBY_SKIP view, 16, 16

determining SQL Apply support for schemas, C.4

DBA_LOGSTDBY_SKIP_TRANSACTION view, 16

DBA_LOGSTDBY_UNSUPPORTED view, 16, C.4

DBA_TABLESPACES view, 8.5, 8.5

DBMS_ALERT, C.3.2

DBMS_AQ, C.3.2

DBMS_DESCRIBE, C.3.1

DBMS_JAVA, C.3.2

DBMS_JOB, C.3.2

DBMS_LOB, C.3.1

DBMS_LOGSTDBY package

INSTANTIATE_TABLE procedure, 9.4.6

SKIP procedure, A.5

SKIP_ERROR procedure, A.3

SKIP_TRANSACTION procedure, A.5

DBMS_LOGSTDBY procedure

capturing events in DBA_LOGSTDBY_EVENTS table, 11.4

DBMS_LOGSTDBY.APPLY_SET procedure

delay applying archived redo log files, 6.2.2

DBMS_LOGSTDBY.BUILD procedure

building a dictionary in the redo data, 4.2.3.2

DBMS_LOGSTDBY.BUILD subprogram

uses Flashback Query, 4.2.3.2

DBMS_METADATA, C.3.1

DBMS_OBFUSCATION_TOOLKIT, C.3.1

DBMS_OUTPUT, C.3.1

DBMS_PIPE, C.3.1

DBMS_RANDOM, C.3.1

DBMS_REDEFINITION, C.3.2

DBMS_REFRESH, C.3.2

DBMS_REGISTRY, C.3.2

DBMS_SCHEDULER, C.3.2

DBMS_SPACE_ADMIN, C.3.2

DBMS_SQL, C.3.1

DBMS_TRACE, C.3.1

DBMS_TRANSACTION, C.3.1

DBSNMP process, A.4.2

DDL statements

supported by SQL Apply, C

DDL transactions

applied on a logical standby database, 9.1.1.5

applying to a logical standby database, 9.1.1.5

DEFER attribute

LOG_ARCHIVE_DEST_STATE_n initialization parameter, 5.2.2, 12.9

DELAY attribute, 14

LOG_ARCHIVE_DEST_n initialization parameter, 6.2.2, 12.8

DELAY option

of ALTER DATABASE RECOVER MANAGED STANDBY DATABASE

cancelling, 6.2.2

delaying

application of archived redo log files, 12.8, 14

application of redo log files, 6.2.2

deleting

archived redo log files

indicated by the DBA_LOGMNR_PURGED_LOG view, 9.3.2

not needed by SQL Apply, 9.3.2

data files, 8.3.2

online redo log files, 8.3.5

DEPENDENCY attribute, 14

LOG_ARCHIVE_DEST_n initialization parameter, 5.7.5

deprecated attributes

on the LOG_ARCHIVE_DEST_n initialization parameter, 14

destinations

archived redo log repository, 5.2.1

cross-instance archival, D.1.2

displaying with V$ARCHIVE_DEST view, 16

Oracle Change Data Capture archival, 5.2.1

Oracle Streams archival, 5.2.1

role-based definitions, 14

shared, 5.7.5, 14

specifying, 5.2.2

verifying settings for role transitions, 12.1.4

detecting

missing archived redo log files, 1.2.1, 1.6, 5.8

network disconnects between primary and standby databases, 14

determining

the highest applicable (newest) SCN, 12.2.2

DG_CONFIG attribute, 14

on the LOG_ARCHIVE_CONFIG initialization parameter, 5.6.2

DGMGRL command-line interface

invoking failovers, 1.3, 7

simplifying switchovers, 1.3, 7

dictionary

building a LogMiner, 4.2.3.2

direct path inserts

SQL Apply DML considerations, 9.1.1.4

directory locations

archived redo log files, 5.7.1

Optimal Flexible Architecture (OFA), 2.4, 2.4

set up with ASM, 2.3.2, 2.4

set up with OMF, 2.3.2, 2.4

specifying with STANDBY_ARCHIVE_DEST initialization parameter, 5.7.1

structure on standby databases, 2.4

disabling

a destination for archived redo log files, 5.2.2

database guard to define a database link, 7.3.2

disaster recovery

benefits, 1.6

configuring, 1.1.3

provided by Data Guard, 1

provided by standby databases, 1.1.3

ReadMe file at standby site, 12.2.1

DISCONNECT FROM SESSION, 8.1.1

disk I/O

controlling with the AFFIRM and NOAFFIRM attributes, 14

DML

batch updates on a logical standby database, 9.1.1.4

DML transactions

applying to a logical standby database, 9.1.1.4

downstream capture database

Oracle Streams and Data Guard redo transport services, 5.2.1

DROP STANDBY LOGFILE clause

of ALTER DATABASE, A.1.2

DROP STANDBY LOGFILE MEMBER clause

of ALTER DATABASE, 15.1, 15.1, 15.1, A.1.2

dropping

data files

examples, 8.3.2

online redo log files, 8.3.5

tablespaces from primary database, 8.3.2

dynamic parameters

AQ_TM_PROCESSES, A.4.2

JOB_QUEUE_PROCESSES, A.4.2

dynamic performance views, 8.5.2

E

ENABLE attribute

LOG_ARCHIVE_DEST_STATE_n initialization parameter, 5.2.2, 12.9

enabling

database guard on logical standby databases, 15.2

destinations for archived redo log files, 5.2.2

real-time apply, 8.2.2

on logical standby databases, 6.4.2, 9.4.1

on physical standby databases, 6.3.2

encrypted columns, C.4

logical standby databases, C.1.2

extensible indexes

supported by logical standby databases, C.1.2

F

failovers, 1.2.3

and cascaded configurations, E.2, E.2.1, E.2.2

choosing a target standby database, 12.2, 12.2.2

Data Guard broker, 1.3, 7

defined, 1.2.3, 7.1

displaying history with DBA_LOGSTDBY_HISTORY, 16

fast-start failover, 7

FINISH FORCE, 7.2.2

flashing back databases after, 7.4

logical standby databases and, 7.3.2, 12.2.2

manual versus automatic, 1.2.3, 7

minimal data loss and, 12.2.2

minimal performance impact, 12.2.2

performing backups after, 7.2.2, 7.3.2

physical standby databases and, 7.2.2, 15.1

preparing for, 7.1.4

re-creating after, 7.2.2

simplifying with Data Guard broker, 7

transferring redo data before, 7.1.4

using DB_ROLE_CHANGE system event after, 7.1.4

viewing characteristics for logical standby databases, 9.2.3

with maximum performance mode, 7.1.4

with maximum protection mode, 7.1.4

failure resolution policies

specifying for redo transport services, 5.5, 14, 14

FAL_CLIENT initialization parameter, 5.8.3

FAL_SERVER initialization parameter, 5.8.3

false network failure detection, 14, 14

fast-start failover

automatic failover, 1.3, 7

enhancements in Oracle Enterprise Manager, Preface

monitoring, 8.5

finding

missing log files, 5.8.4

fixed views

See views

flash recovery areas

default location, 5.2.3, 5.2.3.1, 5.2.3.1, 14

setting up, 5.2.3

sharing among multiple databases, 5.2.3.4

STANDBY_ARCHIVE_DEST=LOCATION parameter, 5.2.3.3

Flashback Database

after a role transition, 7.4

after OPEN RESETLOGS, 12.5

after role transitions, 7.4

characteristics complementary to Data Guard, 1.5

clone database, 12.6

enabling for guaranteed restore point, 12.6

logical standby database, 12.4.2, 12.4.2

physical standby database, 12.4.1

Flashback Query

used by DBMS_LOGSTDBY.BUILD subprogram, 4.2.3.2

FORCE keyword

on RECOVER MANAGED STANDBY DATABASE FINISH, 7.2.2

FORCE LOGGING clause

of ALTER DATABASE, 2.3.2, 3.1.1, 12.10, 12.10, 15.1

of ALTER TABLESPACE, 8.3.6

of CREATE DATABASE, 12.10

G

gap management, 5.8

automatic detection and resolution, 1.2.1, 1.6

defined, 5.8

detecting missing log files, 1.6

registering archived redo log files, 5.8.4

during failover, 7.3.2

H

hardware

requirements for Data Guard configurations, 2.3.1

heap-organized tables

in logical standby databases, C.2.1

high availability

benefits, 1.6

provided by Data Guard, 1

provided by RAC and Data Guard, 1.5

I

idle state, 9.3.1

Image data types

in logical standby databases, C.1.2

incarnation of a database

changed, 8.4, 8.4

index-organized tables

in logical standby databases, C.2.1

initialiation parameters

DB_UNIQUE_NAME, 3.1.4

initialization parameter file

creating from server parameter file

for physical standby database, 3.2.3

modifying

for physical standby database, 3.2.3

initialization parameters

CONTROL_FILE_RECORD_KEEP_TIME, 5.7.4.2

DB_FILE_NAME_CONVERT, F.1.3

DB_UNIQUE_NAME, A.4.4

FAL_CLIENT, 5.8.3

FAL_SERVER, 5.8.3

LOG_ARCHIVE_DEST, 12.11.3

LOG_ARCHIVE_DEST_STATE_n, 5.2.2

LOG_ARCHIVE_FORMAT, 5.7.1

LOG_ARCHIVE_MIN_SUCCEED_DEST, 14

LOG_ARCHIVE_TRACE, 5.9.1, G.1, G.2.2

LOG_FILE_NAME_CONVERT, F.1.4

modifying for physical standby databases, 3.2.3

setting for both the primary and standby roles, 14

STANDBY_ARCHIVE_DEST, 5.7.1, 5.7.1

USER_DUMP_DEST, G.2

INITIALIZING state, 9.3.1

INSTANTIATE_TABLE procedure

of DBMS_LOGSTDBY, 9.4.6

INTERVAL data types

in logical standby databases, C.1.1

J

JOB_QUEUE_PROCESSES dynamic parameter, A.4.2

L

latency

on logical standby databases, 9.1.1.4, 9.1.1.5

LGWR attribute, 14

asynchronous redo transmission, 5.3.2.3, 14, 14

LOG_ARCHIVE_DEST_n initialization parameter

setting for data protection, 5.6.2

LGWR process

See log writer process (LGWR)

listener.ora file

configuring, 3.2.5

redo transport services tuning and, A.6

troubleshooting, 12.9, A.1.3, A.6

listing

archived redo log files, 12.2.2

loading dictionary state, 9.3.1

LOCATION attribute, 14

setting

flash recovery area with USE_DB_RECOVERY_FILE_DEST, 5.2.3.2

LOG_ARCHIVE_DEST_n initialization parameter, A.2

log apply services

defined, 1.2.2, 6.1

delaying application of redo data, 6.2.2, 12.8, 14

real-time apply

and standby redo log files, 2.5

defined, 6.1, 6.2.1, 6.2.1

monitoring with LOG_ARCHIVE_TRACE, G.2.2

monitoring with V$ARCHIVE_DEST_STATUS view, 8.5.4.3

Redo Apply

defined, 6.1, 6.3

monitoring, 6.3.4, 8.5.3, 8.5.4

starting, 6.3.1, 8.1.1

stopping, 6.3.3, 8.1.2

tuning the log apply rate, 8.6

SQL Apply

defined, 1.2.2, 6.1, 6.1

monitoring, 6.4.4

starting, 6.4.2

stopping, 6.4.3

tuning for Redo Apply, 8.6

log writer process (LGWR)

ASYNC network transmission, 5.3.2.1, 14

defined, 5.3.2

local archiving, 5.2.2

NET_TIMEOUT attribute, 14

reconnecting after a network timeout, 14

SYNC network transmission, 14

LOG_ARCHIVE_CONFIG initialization parameter, 3.1.4, 3.1.4, 3.2.3, 5.4.2, 5.4.2, 13

example, 14

listing unique database names defined with, 16

relationship to DB_UNIQUE_NAME parameter, 13

relationship to DG_CONFIG attribute, 14

with the DG_CONFIG attribute, 5.6.2

LOG_ARCHIVE_DEST_10 initialization parameter

default flash recovery area, 5.2.3, 5.2.3.1, 5.2.3.1, 14

LOG_ARCHIVE_DEST_n initialization parameter, 5.3.2.1

AFFIRM attribute, 5.6.2, 14

ALTERNATE attribute, 14, 14, A.2

ARCH attribute, 5.6.2, 14

ASYNC attribute, 14

setting for data protection, 5.6.2

DB_UNIQUE_NAME attribute, 14

DELAY attribute, 6.2.2, 12.8, 14

DEPENDENCY attribute, 5.7.5, 14

deprecated attributes, 14

LGWR attribute, 14

setting for data protection, 5.6.2

LOCATION attribute, 14, A.2

MANDATORY attribute, 14

MAX_CONNECTIONS attribute, 14

MAX_FAILURE attribute, 14

NET_TIMEOUT attribute, 14

NOAFFIRM attribute, 14

NOALTERNATE attribute, A.2

NODELAY attribute, 6.2.2, 6.2.2

NOREGISTER attribute, 14

NOREOPEN attribute, 5.5.1

OPTIONAL attribute, 14

overview, 5.2.2

QUOTA_SIZE attribute, D.2.2

REOPEN attribute, 5.5.1, 14, 14

SERVICE attribute, 14

setting up recovery areas, 5.2.3

SYNC attribute, 14

setting for data protection, 5.6.2

TEMPLATE attribute, 14

VALID_FOR attribute, 5.4.1, 14

VERIFY attribute, 14

LOG_ARCHIVE_DEST_STATE_n initialization parameter, 5.2.2

ALTERNATE attribute, 5.2.2

DEFER attribute, 5.2.2, 12.9

ENABLE attribute, 5.2.2, 12.9

RESET attribute, 5.2.2

LOG_ARCHIVE_FORMAT initialization parameter, 5.7.1

LOG_ARCHIVE_MIN_SUCCEED_DEST initialization parameter, 14

LOG_ARCHIVE_TRACE initialization parameter, 5.9.1, 5.9.1, G.1, G.2.2

logical change records (LCR)

converted by PREPARER process, 9.1

exhausted cache memory, 9.1.1.2

staged, 9.1

logical corruptions

resolving, 1.6

logical standby databases, 1.1.2

adding

datafiles, A.9.1.1

indexes, 1.6, 2.1.2, 9.4.5.1

tables, 9.4.6

archive gaps

finding with DBA_LOGSTDBY_LOG view, 5.8.4

manually resolving, 5.8.4

background processes, 9.1

benefits, 1.6, 2.1.2

cascading, E, E.1.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, 9.4.5

executing SQL statements on, 1.1.2

failovers, 7.3.2

displaying history of, 16, 16

flashing back after, 12.4.2

handling failures, A.3

target of, 12.2.2

viewing characteristics with V$LOGSTDBY_STATS, 9.2.3

logical standby process (LSP) and, 9.1

materialized views

creating on, 1.6, 2.1.2, E.1.2, E.3.3

support for, C.5

monitoring, 6.4.4, 16

password file, 4.2.4.2

read-only operations, 1.6

setting VALID_FOR attribute, 12.1.2, 12.1.2

SQL Apply, 1.2.2

DBMS_LOGSTDBY.APPLY_SET procedure, 6.2.2

delaying, 6.2.2

resynchronizing with primary database branch of redo, 9.5.4

skipping DDL statements, C.5

skipping SQL statements, C.5

starting real-time apply, 6.4.2, 9.4.1

stopping, 6.4.3

technology, 6.1

transaction size considerations, 9.1.1.1

starting

real-time apply, 6.4.2, 6.4.2

states

applying, 9.3.1

idle, 9.3.1

initializing, 9.3.1

loading dictionary, 9.3.1

waiting on gaps, 9.3.1

switchovers, 7.3.1, 7.3.1

throughput and latency, 9.1.1.4, 9.1.1.5

UNDO_RETENTION initialization parameter, 4.2.3.2

upgrading, B.3

rolling upgrades, 2.3.2

logical standby process (LSP)

ARCn archival processing, 5.3.1.2

COORDINATOR process, 9.1

LGWR SYNC archival processing, 5.3.2.2

LogMiner dictionary

using DBMS_LOGSTDBY.BUILD procedure to build, 4.2.3.2

when creating a logical standby database, 4.2.4.1

LONG data types

in logical standby databases, C.1.1

LONG RAW data types

in logical standby databases, C.1.1

M

managed recovery operations

See Redo Apply

managed recovery process (MRP)

ARCn archival processing, 5.3.1.2

launching parallel recovery processes, 5.3.1.2

LGWR SYNC archival processing, 5.3.2.2

N

NCHAR data types

in logical standby databases, C.1.1

NCLOB data types

in logical standby databases, C.1.1

NET_TIMEOUT attribute, 14

ignored for LGWR ASYNC destinations, 5.3.2.3

network I/O operations

coordinating timeout parameter values, 14

detecting a disconnect, 14

false failures, 14, 14

influence of data protection modes, 14

network timers

NET_TIMEOUT attribute, 14

setting up synchronous or asynchronous, 14

tuning

redo transport services, A.6

network timeouts

acknowledging, 14

for LGWR ASYNC destinations, 5.3.2.3

NEWEST_SCN column

of V$LOGSTDBY_PROGRESS view, 12.2.2

no data loss

benefits, 1.6

data protection modes overview, 1.4

ensuring, 1.2.3, 2.1.1

environments, 5.3.2.1

guaranteeing, 1.2.3

provided by maximum availability mode, 1.4, 5.6.1.2

provided by maximum protection mode, 1.4, 5.6.1.1

NOAFFIRM attribute, 14

NOALTERNATE attribute

LOG_ARCHIVE_DEST_n initialization parameter, A.2

NODELAY attribute

LOG_ARCHIVE_DEST_n initialization parameter, 6.2.2, 6.2.2

NODELAY option

of Redo Apply operations, 12.8.3

NOREGISTER attribute, 14

NOREOPEN attribute

LOG_ARCHIVE_DEST_n initialization parameter, 5.5.1

NUMBER data types

in logical standby databases, C.1.1

NVARCHAR2 data types

in logical standby databases, C.1.1

O

off-site archiving of redo data, 5.2.1

OMF

See Oracle Managed Files (OMF)

on-disk database structures

physical standby databases, 1.1.2

online redo log files

adding, 8.3.5, 8.3.5

archive gap management, 5.8

deleting, 8.3.5

dropping, 8.3.5

OPEN READ ONLY clause

of ALTER DATABASE, 15.1

OPEN RESETLOGS

flashing back after, 12.5

OPEN RESETLOGS clause

database incarnation change, 8.4, 8.4

of ALTER DATABASE, 3.2.2, 8.5

recovery, 8.4, 8.4

opening

physical standby database for read/write access, 12.6

operating systems

requirements for Data Guard configurations, 2.3.1

operational requirements, 2.3, 2.3.1, 2.3.2

standby databases

operating system requirements, 2.3.1

Optimal Flexible Architecture (OFA)

directory structure, 2.4, 2.4

OPTIONAL attribute, 14

LOG_ARCHIVE_DEST_n initialization parameter, 5.7.2

ORA-01102 message

causing switchover failures, A.4.4

Oracle Advanced Security

providing secure redo transmission, 5.3.3, 5.3.3

Oracle Automatic Storage Management (ASM), 2.3.2, 2.4

Oracle Change Data Capture archival, 5.2.1

Oracle Database

requirements for upgrading with SQL Apply, 11.2

upgrading, B.1

upgrading with SQL Apply, 11.1

Oracle Database Enterprise Edition

software requirements, 2.3.2

Oracle databases

upgrading, 2.3.2

Oracle Enterprise Manager

enhancements, Preface

invoking failovers, 1.3, 7

invoking switchovers, 1.3, 7

Oracle Managed Files (OMF), 2.3.2, 2.4

creating a standby database that uses, 12.12

creating standby databases that use, F.3.1, F.3.2

Oracle Net

communication between databases in a Data Guard configuration, 1.1

Oracle Recovery Manager utility (RMAN)

backing up files on a physical standby database, 10

Oracle Standard Edition

simulating a standby database environment, 2.3.2

Oracle Streams

archival, 5.2.1

downstream capture database, 5.2.1

P

pageout considerations, 9.1.1.2

pageouts

SQL Apply, 9.1.1.2

Parallel DDL (PDDL) transactions

SQL Apply, 9.1.1.5

parallel DML (PDML) transactions

SQL Apply, 9.1.1.3, 9.1.1.4

parallel execution processes

logical standby databases, 5.3.1.2

physical standby databases, 5.3.1.2

tuning the log apply rate, 8.6

specifying

PARALLEL_MAX_SERVERS initialization parameter, 8.6, 13

PARALLEL option

tuning the log apply rate for Redo Apply, 8.6

parallel recovery processes

initiated for Redo Apply, 5.3.1.2

PARALLEL_MAX_SERVERS initialization parameter

specifying

creating a logical standby database, 8.6, 13

partial archived redo log files

registering, 12.2.2

password files

creating new, 4.2.4.2

requirements, 5.3.3

setting REMOTE_LOGIN_PASSWORDFILE initialization parameter, 5.3.3

patch set releases

upgrading, 2.3.2

performance

balancing against data availability, 1.6

balancing against data protection, 1.6

monitoring redo transport services, 5.9.2

physical standby databases

activating as a clone database, 12.6

altering

online redo log files, 8.3.5

applying redo data, 6.1, 6.3

cascading, E

Redo Apply technology, 6.3

applying redo log files

starting, 6.3.1

benefits, 2.1.1

choosing a target for failover, 12.2.1

cloning

creating a restore point, 12.6

for testing, development, and reporting, 12.6

configuration options, 2.4

converting to a logical standby database, 4.2.4.1

converting to a read/write database, 12.6

creating

checklist of tasks, 3.2

configuring a listener, 3.2.5

directory structure, 2.4

initialization parameters for, 3.2.3

traditional initialization parameter file, 3.2.3

with Data Guard broker, 1.3

defined, 1.1.2

failover

checking for updates, 7.1.4

finding gaps with V$ARCHIVE_GAP view, 5.8.4

flashing back after failover, 12.4.1

manually resolving archive gaps, 5.8.4, 5.8.4

monitoring, 6.3.4, 8.3, 8.5.4, 16

online backups and, 2.1.1

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

opening for read/write access, 12.6

read-only, 2.1.1, 8.2

read/write testing and reporting, 12.6

recovering through OPEN RESETLOGS, 8.4

Redo Apply, 1.2.2, 2.1.1

resynchronizing with primary database branch of redo, 8.4, 8.4

role transition and, 7.2

rolling forward

when lagging far behind the primary database, 12.7.1

when nologging changes applied to a small subset of data files, 12.7.2

when nologging changes are widespread, 12.7.3

rolling forward with BACKUP INCREMENTAL FROM SCN command, 12.7

setting VALID_FOR attribute, 12.1.1, 12.1.1

shutting down, 8.1.2

starting

log apply services, 6.3.1

real-time apply, 6.3.2

support for DDL, 2.1.1

support for DML, 2.1.1

synchronizing with the primary database, 12.7

tuning the log apply rate, 8.6

upgrading, B.2

using transportable tablespaces, 8.3.3

PL/SQL supplied packages

supported, C.3.1

unsupported, C.3.2

PREPARE TO SWITCHOVER clause

of ALTER DATABASE, 7.3.1, 7.3.1, 15.1

PREPARER process, 9.1

staging LCRs in SGA, 9.1

primary database

backups and, 7.2.2, 7.3.2

configuring

for cross-instance archival, D.1.2

on Real Application Clusters, 1.1.1

single-instance, 1.1.1

data files

adding, 8.3.1

renaming, 8.3.2.1

defined, 1.1.1

failover and, 7.1

gap resolution, 1.6

gathering redo log archival information, 5.9.1

initialization parameters

and physical standby database, 3.2.3

monitoring events on, 8.5

network connections

avoiding network hangs, 14

detecting disconnections, 14

handling network timeouts, 14

preparing for

physical standby database creation, 3.1

prerequisite conditions for

logical standby database creation, 4.1

Real Application Clusters and

setting up, D.1.1, D.1.2

redo transport services on, 1.2.1

reducing workload on, 1.6

setting archive tracing, 5.9.1

sharing a flash recovery area, 5.2.3.4

switchover, 7.1.3

switchovers

initiating, 7.2.1

tablespaces

adding, 8.3.1

dropping, 8.3.2

primary databases

ARCHIVELOG mode, 2.3.2

software requirements, 2.3.2

using V$ARCHIVED_LOG view to find missing log files, 5.8.4

primary key columns

logged with supplemental logging, 4.2.3.2, 9.1.1.4

primary role, 1.1.1

processes

archiver (ARCn), 5.3.1

CJQ0, A.4.2

DBSNMP, A.4.2

log writer (LGWR), 5.3.2

preventing switchover, A.4.2

QMN0, A.4.2

Q

QMN0 process, A.4.2

queries

improved performance, 1.6

offloading on the standby database, 1.6

QUOTA_SIZE attribute

LOG_ARCHIVE_DEST_n initialization parameter, D.2.2

R

RAW data types

in logical standby databases, C.1.1

raw devices

standby redo log files residing on, 2.5.2

READER process, 9.1

read-only operations, 1.2.2

definition, 2.1.1

logical standby databases, 1.6

physical standby databases and, 8.2

read/write databases, 12.6

Real Application Clusters, D.1.2

characteristics complementary to Data Guard, 1.5

cross-instance archival, D.1.2

performing switchover and, D.2.4.1, D.2.4.2

primary databases and, 1.1.1, D.1.1, D.1.2

setting

maximum data protection, D.2.3

standby databases and, 1.1.2, D.1, D.1.2

using standby redo log files, 3.1.3, D.1.2

using standby redo logs, 2.5.2

real-time apply

and SQL Apply, 9.4.1

defined, 6.1, 6.2.1

monitoring progress in V$ARCHIVE_DEST_STATUS, 8.5.4.3

overview of log apply services, 1.2

require standby redo log files, 2.5.2

RFS process with, 6.1

starting, 6.3.2

on logical standby, 6.4.2

starting on logical standby databases, 6.4.2, 9.4.1

starting on physical standby databases, 6.3.2

stopping

on logical standby, 6.4.3

on physical standby databases, 8.1.2

tracing data with LOG_ARCHIVE_TRACE initialization parameter, G.2.2

using standby redo log files, 2.5

recommendations for secure redo transmission, 5.3.3

reconnecting

after a network timeout, 14

network connection

when in maximum availability mode, 14

when in maximum protection mode, 14

RECOVER MANAGED STANDBY DATABASE CANCEL clause

aborting, 4.2.4.1

RECOVER MANAGED STANDBY DATABASE clause

canceling the DELAY control option, 6.2.2

FORCE keyword, 7.2.2

of ALTER DATABASE, 3.2.6, 4.2.5, 6.2.2, 6.3.1, 8.2.2, 8.2.2, 12.2.1, 12.8.2, 15.1, 15.1, 15.1, 15.1

background process, 6.3.1, 8.1.1

controlling Redo Apply, 6.3.1

foreground session, 6.3.1

initiating failover, 7.2.2

overriding the delay interval, 6.2.2, 14

starting real time apply, 6.3.2

switchover scenario, 12.8.3

RECOVER TO LOGICAL STANDBY clause

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

recovering

after a NOLOGGING clause is specified, 12.10.1

from errors, A.9.1

logical standby databases, 9.5.4

physical standby databases

after an OPEN RESETLOGS, 8.4, 8.4

through resetlogs, 8.4, 9.5.4

Recovery Manager

characteristics complementary to Data Guard, 1.5

commands

DUPLICATE, F.1.1

DB_FILE_NAME_CONVERT option of the DUPLICATE command, F.1.3

standby database

creating, F.1.1, F.2

creating standby control files, F.1.2

creating using image copies, F.7.1

DB_FILE_NAME_CONVERT initialization parameter, F.1.3

LOG_FILE_NAME_CONVERT initialization parameter, F.1.4

naming standby datafiles, F.1.3

preparing using RMAN, F.1

setting up with OMF, F.3.1, F.3.2

starting RMAN and standby instance, F.3

re-creating

a table on a logical standby database, 9.4.6

Redo Apply

defined, 1.2.2, 2.1.1, 6.1

flashing back after failover, 12.4.1, 12.4.2

monitoring, 8.5.4.3

options

NODELAY, 12.8.3

parallel recovery processes and MRP, 5.3.1.2

read/write testing and reporting, 12.6

resolving archive gaps, 5.8.4

role transitions and cascaded configurations, E.2.1

starting, 3.2.6, 6.3.2

stopping, 8.1.2

technology, 1.2.2

tuning the log apply rate, 8.6, 8.6

redo data

applying

through Redo Apply technology, 1.2.2

through SQL Apply technology, 1.2.2

to standby database, 6.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, 6.1

building a dictionary in, 4.2.3.2

manually transferring, 2.3.2

transmitting, 1.1.2, 1.2.1, 5

validated, 1.6

redo log files

delaying application, 6.2.2

redo logs

automatic application on physical standby databases, 6.3.1

configuration considerations, 2.5.1

in Data Guard configurations, 2.5.1

secure redo transmission, 5.3.3

update standby database tables, 1.6

redo transport services, 5.1

archive destinations

alternate, A.2

archived redo log repository, 5.2.1

Oracle Change Data Capture, 5.2.1

Oracle Streams, 5.2.1

quotas, D.2.2

re-archiving to failed destinations, 5.5.1, 14

role-specific, 5.4.1

shared, 5.7.5, 14

specifying with the LOG_ARCHIVE_DEST_n initialization parameter, 5.2.2

archived redo log files

generating filenames, 5.7.1

listing with V$ARCHIVED_LOG view, 5.7.1

specifying directory locations for, 5.7.1

defined, 1.2.1, 5.1

handling archive failures, 5.5, 14

monitoring, 5.9.1, 5.9.2

network

ASYNC network transmission, 5.3.2.1

SYNC network transmission, 5.3.2.1

tuning, A.6

protection modes

choosing, 5.6.1

maximum availability mode, 1.4, 5.6.1.2

maximum performance mode, 1.4, 5.6.1.3

maximum protection mode, 1.4, 5.6.1.1

providing no data loss, 5.3.2.1

setting, 5.6.2

secure redo transmission, 5.3.3

standby redo log files

configuring, 3.1.3

synchronous and asynchronous disk I/O, 14

using the log writer process, 5.3.2.3, 14, 14

of ALTER DATABASE, 15.1, A.4.1

registering missing log files, 5.8.4, 5.8.4

of ALTER DATABASE, 5.8.4, 7.3.2, 12.2.2

registering

archived redo log files, 5.8.4, 12.2.2

during failover, 7.3.2

missing log files, 5.8.4, 5.8.4

partial archived redo log files, 12.2.2

RELY constraint

creating, 4.1.2

remote file server process (RFS)

defined, 2.5, 5.3.2.2, 6.1

log writer process and, 6.2.1

standby redo log files reused by, 5.7.3.1

REMOTE_LOGIN_PASSWORDFILE initialization parameter

secure redo transmission, 5.3.3

RENAME FILE clause

of ALTER DATABASE, A.1.2, A.1.2

renaming

data files

on the primary database, 8.3.4

setting the STANDBY_FILE_MANAGEMENT parameter, 8.3.4

REOPEN attribute, 14, 14

LOG_ARCHIVE_DEST_n initialization parameter, 5.5.1

reporting operations

configuring, 1.1.3

offloading on the standby database, 1.6

performing on a logical standby database, 1.1.2

repository

for temporary storage of archived redo log files, 5.2.1

requirements

data protection modes, 5.6.2

of a rolling upgrade, 11.2

RESET attribute

LOG_ARCHIVE_DEST_STATE_n initialization parameter, 5.2.2

RESETLOGS_ID columns

viewing in V$DATABASE_INCARNATION view, 8.5.3.4

resolving

logical corruptions, 1.6

restart considerations

SQL Apply, 9.1.1.3

restore points

creating, 12.6

creating guaranteed, 12.6

using the CREATE RESTORE POINT command, 12.6

resynchronizing

logical standby databases with a new branch of redo, 9.5.4

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

retrieving

missing archived redo log files, 1.2.1, 1.6, 5.8, 12.2.2

reusing records in the control files, 5.7.4

RFS

See remote file server process (RFS)

RMAN

incremental backup

rolling forward databases that lag far behind the primary, 12.7.1

rolling forward databases when nologging changes applied to a small subset of data files, 12.7.2

rolling forward databases when nologging changes are widespread, 12.7.3

incremental backups, 12.7

rolling forward physical standby databases, 12.7

RMAN BACKUP INCREMENTAL FROM SCN command, 12.7

role management services

defined, 7

role transitions, 1.2.3, 7.1

and cascaded configurations, E.2

choosing a type of, 7.1.1

choosing the best available standby database, 12.2

defined, 1.2.3

flashing back the databases after, 7.4

logical standby database and, 7.3

monitoring, 8.5

physical standby databases and, 7.2

reversals, 1.2.3, 7.1

writing triggers to manage tasks after, 7.1.3, 7.1.4

role-based destinations

setting, 14

rollback

after switchover failures, A.4.6

rolling upgrade

software requirements, 2.3.2

rolling upgrades

benefits, 11.1

patch set releases, 2.3.2

requirements, 11.2

setting the COMPATIBLE initialization parameter, 11.2, 11.4, 11.5

unsupported data types and storage attributes, 11.4

ROWID data types

in logical standby databases, C.1.2

S

scenarios

cascaded destinations, E.3.1

choosing best standby database for role transition, 12.2

recovering

a logical standby database, 12.10.1

after NOLOGGING is specified, 12.10

from a network failure, 12.9

time lag in redo logs, 12.8

schemas

data manipulation on logical standby databases, 1.6

DBA_LOGSTDBY_SKIP list of skipped, C.4

identical to primary database, 1.1.2

skipped by SQL Apply, C.4

SCN

determine the highest applicable (newest), 12.2.2

using for incremental backups, 12.7

secure redo transmission, 5.3.3

segment compression storage type

in logical standby databases, C.2.2

sequences

unsupported on logical standby databases, C.4

SERVICE attribute, 14

SET STANDBY DATABASE clause

of ALTER DATA, 15.1

of ALTER DATABASE, 7.1.4, 15.1

setting

data protection mode, 5.6.2

VALID_FOR attributes

for a logical standby database, 12.1.2

for a physical standby database, 12.1.1

sharing

destinations, 5.7.5, 14

flash recovery area, 5.2.3.4

shutting down

physical standby database, 8.1.2

simulating

standby database environment, 2.3.2

SKIP procedure

of DBMS_LOGSTDBY, A.5

SKIP_ERROR procedure

of the DBMS_LOGSTDBY package, A.3

SKIP_TRANSACTION procedure

of DBMS_LOGSTDBY, A.5

snapshot

obtained by Flashback Query, 4.2.3.2

software requirements, 2.3.2

Oracle Database Enterprise Edition, 2.3.2

rolling upgrades, 2.3.2, 2.3.2

Spatial data types

in logical standby databases, C.1.2

SQL Apply, 6.4.3, 9.1.1.2

after an OPEN RESETLOGS, 9.5.4

ANALYZER process, 9.1

APPLIER process, 9.1

applying CREATE TABLE AS SELECT (CTAS) statements, 9.1.1.5

applying DDL transactions, 9.1.1.5, 9.1.1.5

applying DML transactions, 9.1.1.4

architecture, 9.1, 9.3.1

BUILDER process, 9.1

COORDINATOR process, 9.1

defined, 1.2.2, 6.1

deleting archived redo log files, 9.3.2

parallel DDL transactions, 9.1.1.5

parallel DML (PDML) transactions, 9.1.1.3, 9.1.1.4

performing a rolling upgrade, 11.1

PREPARER process, 9.1

READER process, 9.1

requirements for rolling upgrades, 11.2

restart considerations, 9.1.1.3

role transitions and cascaded configurations, E.2.2

rolling upgrades, 2.3.2

schemas skipped, C.4

starting

real-time apply, 6.4.2

stopping

real-time apply, 6.4.3

support for DDL statements, C

support for PL/SQL supplied packages, C.3.1

support for storage types, C.2.1

supported data types, C.1.1

transaction size considerations, 9.1.1.1

unsupported data types, C.1.2

unsupported PL/SQL supplied packages, C.3.2

unsupported storage types, C.2.2

unsupported table data types, C.4

unsupported tables using table compression, C.4

viewing current activity, 9.1

of processes, 9.1

what to do if it stops, A.5

with real-time apply, 9.4.1

SQL Apply resolving archive gaps, 5.8.4

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

switchover and, 7.2.1

standby database

creating logical, 4

standby databases

about creating using RMAN, F.1.1

applying redo data on, 6

applying redo log files on, 1.2.2, 1.6

cascading, E

choosing a target for role transitions, 12.2

configuring, 1.1

archived redo log repository, 5.2.1

cross-instance archival, D.1.2

delayed application of archived redo log files on, 12.8

mandatory destinations, 5.7.2

maximum number of, 2

on Real Application Clusters, 1.1.2, D.1, D.1.2

on remote locations, 1.1.3

optional destinations, 5.7.2

single-instance, 1.1.2

creating, 1.1.2, 3, F.7.1

checklist of tasks, 4.2

directory structure considerations, 2.4

if primary uses ASM or OMF, 12.12

on local host, F.6

on remote host with different directory structure, F.5

on remote host with same directory structure, F.4

using RMAN, F.2, F.2

with a time lag, 6.2.2, 12.8.1

creating control files

using RMAN, F.1.2, F.1.2

DB_FILE_NAME_CONVERT initialization parameter, F.1.3

defined, 2.1

failover

preparing for, 7.1.4

failover to, 7.1.4

re-creating after, 7.2.2

hardware requirements, 2.3.1

log apply services on, 6.1

LOG_FILE_NAME_CONVERT initialization parameter, F.1.4

modifying the control file, 8.3.3

naming datafiles using RMAN, F.1.3

operational requirements, 2.3, 2.3.2

preparing to use RMAN, F.1

recovering through OPEN RESETLOGS, 8.4

resynchronizing with the primary database, 1.6

reverting back to primary database, A.4.6

rolling forward with RMAN incremental backups, 12.7, 12.7.1

SET AUXNAME command, F.1.4

SET NEWNAME command, F.1.3, F.1.4

setting the NETWORK_TIMEOUT attribute, 5.3.2.3

setting up to use OMF files, F.3.1, F.3.2

sharing

a flash recovery area, 5.2.3.4

software requirements, 2.3.2

starting log apply services on physical, 6.3.1

starting RMAN and standby instance, F.3

viewing database incarnation information, 8.5.3.4

viewing RESETLOGS_ID, 8.5.3.4

wait events configured for, 5.9.2

T

tables

data types unsupported by SQL Apply, C.4

logical standby databases

adding on, 9.4.6

re-creating tables on, 9.4.6

unsupported on, C.4

unsupported in a logical standby database, 11.4

using table compression, C.4

with encrypted columns, C.4

tablespaces

adding

a new data file, A.9.1.1

to primary database, 8.3.1

dropping from primary database, 8.3.2

monitoring status changes, 8.5

moving between databases, 8.3.3

target standby database

for switchover, 7.1.2

target standby databases

choosing a logical standby database for failover, 12.2.2

choosing physical standby databases for failover, 12.2.1

TEMPLATE attribute, 14

terminating

network connection, 14

text indexes

supported by logical standby databases, C.1.2

throughput

on logical standby databases, 9.1.1.4, 9.1.1.5

time lag

delaying application of archived redo log files, 6.2.2, 12.8, 14

in standby database, 6.2.2, 12.8.1, 14

TIMESTAMP data types

in logical standby databases, C.1.1

tnsnames.ora file

redo transport services tuning and, A.6

troubleshooting, 12.9, A.1.3, A.4.5, A.6

trace files

levels of tracing data, G.2.2

location of, G.2

setting, G.2.1

tracking real-time apply, G.2.2

transaction size considerations

SQL Apply, 9.1.1.1

transportable tablespaces

defining location with DB_FILE_NAME_CONVERT parameter, 8.3.3

setting the STANDBY_FILE_MANAGEMENT parameter, 8.3.3

using with a physical standby database, 8.3.3

triggers

handled on a logical standby database, 9.5.3

troubleshooting

if SQL Apply stops, A.5

last redo data was not transmitted, A.4.1

listener.ora file, 12.9, A.1.3, A.6

logical standby database failures, A.3

processes that prevent switchover, A.4.2

SQL Apply, A.5

switchovers, A.4

active SQL sessions, A.4.2

active use sessions, A.4.3

ORA-01102 message, A.4.4

roll back and start over, A.4.6

tnsnames.ora file, 12.9, A.1.3, A.4.5, A.6

tuning

determining if you have enough standby redo log groups, 5.7.3.1

log apply rate for Redo Apply, 8.6

U

UNDO_RETENTION initialization parameter

recommendations, 4.2.3.2

unique-index columns

logged with supplemental logging, 4.2.3.2, 9.1.1.4

unrecoverable operations, 12.10.2

backing up after, 12.10.3

unsupported data types

during a rolling upgrade, 11.4

unsupported PL/SQL supplied packages, C.3.2

unsupported storage types, C.2.2

unsupported tables

for logical standby database during a rolling upgrade, 11.4

upgrading

Oracle Database, B, B.1

Oracle Database software, 11.1

Oracle database software, 2.3.2

Oracle database software version, 11.1

requirements, 11.2

UROWID data types

in logical standby databases, C.1.2

user errors

safeguarding against, 1.6

user sessions

causing switchover failures, A.4.3

USER_DUMP_DEST initialization parameter, G.2

user-defined data types

in logical standby databases, C.1.2

USING CURRENT LOGFILE clause, 8.2.2

starting real time apply, 6.3.2

using RMAN

using image copies, F.7.1

V

V$ARCHIVE_DEST view, 5.9.1, 12.9, 16, A.1.3

displaying implicit default value of STANDBY_ARCHIVE_DEST parameter, 5.7.1

displaying information for all destinations, 16

V$ARCHIVE_DEST_STATUS view, 5.9.1, 8.5.4.3, 8.5.4.3, 16

log apply services and MANAGED REAL TIME column, 8.5.4.3

V$ARCHIVE_GAP view, 16

finding gaps on physical standby databases, 5.8.4

V$ARCHIVED_LOG view, 5.7.1, 5.9.1, 8.5.4.4, 12.11.2, 16, A.4.1

determining the most recently archived redo log file, 5.9.1

locating missing log files, 5.8.4

V$DATABASE view, 16

monitoring fast-start failover, 8.5

switchover and, 7.2.1, 7.2.1

SWITCHOVER_STATUS column and, 7.2.1, 7.2.1, 7.2.1, A.4.1

V$DATABASE_INCARNATION view, 16

obtaining database incarnation information, 8.5.3.4

V$DATAFILE view, 12.10.2, 12.10.3, 16

V$DATAGUARD_CONFIG view, 16

listing database names defined with LOG_ARCHIVE_CONFIG, 16

V$DATAGUARD_STATUS view, 8.5.4.6, 16

V$LOG view, 5.9.1, 16

V$LOG_HISTORY view, 8.5.3.6, 8.5.4.5, 16

V$LOGFILE view, 16

V$LOGSTDBY view, Preface

V$LOGSTDBY_PROCESS view, 9.1, 9.2.4, 9.2.4, 9.3.1, 9.6.3.1, 9.6.3.2, 16, 16

V$LOGSTDBY_PROGRESS view, 9.2.5, 16

querying SCN information and, 12.2.2

RESTART_SCN column, 9.1.1.3

V$LOGSTDBY_STATE view, 7.1.2, 9.2.6, 9.3.1, 16

V$LOGSTDBY_STATS view, 9.1, 9.2.7, 16

failover characteristics, 9.2.3

V$LOGSTDBY_TRANSACTION view, 16

V$MANAGED_STANDBY view, 8.5.4.2, 8.5.4.2, 16

V$RECOVER_FILE view, 8.5, 8.5

V$SESSION view, A.4.2, A.4.3

V$STANDBY_LOG view, 7.3.2, 7.3.2, 16

V$THREAD view, 8.5

VALID_FOR attribute, 14

examples, 5.4.1

overview, 5.4.1

verifying, 12.1.4

validating

redo data, 1.6

VARCHAR data types

in logical standby databases, C.1.1

VARCHAR2 data types

in logical standby databases, C.1.1

VERIFY attribute, 14

verifying

contents of archived redo log files, 14

logical standby databases, 4.2.6

physical standby databases, 3.2.7

role-based destination settings, 12.1.4

standby redo log groups, 3.1.3

versions

upgrading Oracle database software, 11.1

views, 8.5.2, 16

DBA_LOGSTDBY_EVENTS, 9.2.1, 16, A.5

DBA_LOGSTDBY_HISTORY, 16

DBA_LOGSTDBY_LOG, 9.2.2, 12.2.2, 16

DBA_LOGSTDBY_NOT_UNIQUE, 16

DBA_LOGSTDBY_PARAMETERS, 16

DBA_LOGSTDBY_SKIP, 16, 16

DBA_LOGSTDBY_SKIP_TRANSACTION, 16

DBA_LOGSTDBY_UNSUPPORTED, 16, C.4

DBA_TABLESPACES, 8.5

displaying history of switchovers and failovers, 16

GV$INSTANCE, D.3.1

V$ARCHIVE_DEST, 5.9.1, 12.9, 16, A.1.3

V$ARCHIVE_DEST_STATUS, 5.9.1, 8.5.4.3, 8.5.4.3, 8.5.4.3, 16

V$ARCHIVE_GAP, 16

V$ARCHIVED_LOG, 5.7.1, 5.9.1, 8.5.4.4, 12.11.2, 16

V$DATABASE, 16

V$DATABASE_INCARNATION, 16

V$DATAFILE, 12.10.2, 12.10.3, 16

V$DATAGUARD_CONFIG, 16

V$DATAGUARD_STATUS, 8.5.4.6, 16

V$LOG, 5.9.1, 16

V$LOG_HISTORY, 8.5.3.6, 8.5.4.5, 16

V$LOGFILE, 16

V$LOGSTDBY, Preface

V$LOGSTDBY_PROCESS, 9.1, 9.2.4, 16

V$LOGSTDBY_PROGRESS, 9.2.5, 16

V$LOGSTDBY_STATE, 9.2.6, 16

V$LOGSTDBY_STATS, 9.1, 9.2.7, 16

V$LOGSTDBY_TRANSACTION, 16

V$MANAGED_STANDBY, 8.5.4.2, 8.5.4.2, 16

V$RECOVER_FILE, 8.5, 8.5

V$SESSION, A.4.2, A.4.3

V$STANDBY_LOG, 3.1.3, 7.3.2, 7.3.2, 16

V$THREAD, 8.5

W

wait events, 5.9.2

for standby destinations, 5.9.2

monitoring the performance of the redo transport modes, 5.9.2

WAITING FOR DICTIONARY LOGS state, 9.3.1

waiting on gap state, 9.3.1

X

XML type data types

in logical standby databases, C.1.2

Z

zero data loss

See no data loss

zero downtime instantiation

logical standby databases, 4.2