Index

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

A

ABORT LOGICAL STANDBY clause

of ALTER DATABASE, 13-5

ACTIVATE STANDBY DATABASE clause

of ALTER DATABASE, 7-25, 10-33, 13-5

ADD STANDBY LOGFILE clause

of ALTER DATABASE, 5-2 8, 8-17, A-2

ADD STA NDBY LOGFILE GROUP clause

of ALTER DATABASE, 5-28, 13-2

ADD STANDBY LOGFILE MEMBER clause

of ALTER DATABASE, 5-35, 13-2, A-2

ADD STANDBY MEMBER clause

of ALTER DATABAS E, 5-35

ADD SUPPLEMENTAL LOG DATA clause

< dd class="L2IX">of ALTER DATABASE, 4-9, 4-10, 13-2

ADD TEMPFILE clause

of ALTER TABLESPACE, 8-7

adding

datafiles, 8-10, 9-16, 9-17

examples, 8-11

indexes on logical standby data bases, 1-12, 2-4, 9-5

new or existing standby databases, 1-7

online redo log files, 5-35, 8-17

standby redo log group m embers, 5-35

tablespaces, 8-10

temporary files, 3-13, 4-17

AFFIRM attribute

LOG_ARCHIVE_DEST_n initialization parameter, 12-2, 12-4

setting for data pr otection, 5-29

ALTER DATABASE RECOVER MANAGED STAND BY DATABASE

cancelling the DELAY control option, 6-5

ALTER DATABASE RENAME FILE statement

modifying the standby control file, 8-15

ALTER DATABASE RENAME GLOBAL_NAME statement, 4-16

ALTER DATABASE statement

ABORT LOGICAL STANDBY clau se, 13-5

ACTIVATE STANDBY DATABASE clause, 7-25, 10-33, 13-5

ADD STANDBY LOGFILE clause, 5-28, 8-17, 13-2, A-2

ADD STANDBY LOGFILE GROUP clause, 5-28

ADD STANDBY LOGFILE MEMBER clause, 5-35, 13-2, A-2

ADD SUPPLEMENTAL LOG DATA c lause, 4-9, 4-10, 13-2

< dd class="L2IX">ALTER STANDBY LOGFILE clause, 5-28

ALTER STANDBY LOGFIL E GROUP clause, 5-28

CLEAR UNARCHIVED LOGFILES clause, 8-33

COMMIT TO SWITCHOVER clause, 7-12, 7-17, 7-21, 7-22 , 10-34, 13-2, F-4

in Real Application Clusters, B-9

trouble shooting, A-6, A-8, A-9

CREATE CONTROLFILE clause, 8-10, 8-32

CREATE DATAFILE AS clause, A-2

CREATE STANDBY CONTROLFILE clause, 3-7, 4-14, A-4

REUSE clause, 13-2

< /dd>

DROP LOGFILE clause, A-2

DROP STANDBY LOGFILE ME MBER clause, 13-3, A-2

FORCE LOGGI NG clause, 2-7, 3-2, 10-36, 13-3

GUARD clause, 9-3

keywords of, 9-3, 9-4

MOUNT STANDBY DATABASE clause, 13-3

OPEN READ ONLY clause, 13-3

OPEN RESETLOGS clause, 3-7, 4-16, 8-33

PREPARE TO SWITCHOVER clause, 7-20, 13-3

RECOVER MANAGED STANDBY DATABASE cla use, 3-14, 4-14, 4-17, 6-5, 8-6, 8-8, 10-18, 10-33, 13-4

background process, 6-6, 8-2

canceling, 6-7

canceling log apply services, 8-6

controlling Redo Apply, 6-6

failover, 13-5

foreground session, 6-6

initiating failover, 7-17

overriding the delay interval, 6-5, 12-17

starting real time appl y, 6-7

switchover scenario, 10-33

< /dl>

RENAME FILE clause, A-2

res trictions, A-2

SET STANDBY DATABASE clause

TO MAXIMIZE AVAILABILITY clause, 13-4

TO MAXIMIZE PERFORMANCE clau se, 7-10

TO MAXIMIZE PROTECTION clause, 13-4

START LOGICAL STANDBY APPLY clause, 6-11, 7-26, 13-5, A-12

IMMEDIATE keyword, 6-11, 9-14

NEW PRIMARY keyword, 7-26

starting SQL Apply, 4-17

STOP LOGICAL STANDBY APPLY clause, 6-11, 7-25, 10-23, 13-5

TEMPFILE clause, 3-13, 4-17

< /dl>

ALTER SESSION GUARD DISABLE

disabling the database guard to define a d atabase link, 7-26

ALTER SESSION statement

GUARD ENABLE clause, 13-6

ALTER SYSTEM statem ent

ARCHIVE LOG CURRENT clause, 3-14, 10-36

ALTER TABLESPACE statement, 8-12, 8-15, 9-17, 10-38

ADD TEMPFILE clause, 8-7

FORCE LOGGING clause, 8-18

skipping, 8-12, 9-8

altering

control files, 8-18

alternate archive destinations

setting up initialization parameters for, A-4

ALTERNATE attribute

LOG_ARCHIVE_DEST_n initialization parameter, 12-7, A-4

LOG_ARCHIVE_DEST_STATE_n initialization parameter, 5-4

ANALYZER process, 9-12

APPLIED_SCN column

of DBA_LOGSTDBY_PROGRESS view, 10-21

APPLIER process, 9-12

APPLY_SET procedure

of DBMS_LOGSTDBY, 9-3

APPLY_UNSET procedure

of DBMS_LOGSTDBY, 9-3

applying

redo data immediately, 6-3

redo data on standby database, 1-4, 1-5, 2-2 , 6-1

SQL statements to logical standby databases, 6-10

AQ_TM_PROCESSES dynamic parameter, A-8

ARCH attribute

LOG_ARCHIVE_DEST_n initialization parameter, 12-12

setting for data protection, 5 -29

archive destinations

alternate, A-4

archive gaps

causes of, 10-40

defined, 5-38

iden tifying the logs, 10-43

manually applying redo logs to standby database, 10-45

manually copying the logs in, 10-44

preventing, 10-42

ARCHIVE LOG CURRENT clau se

of ALTER SYSTEM, 3-14, 10-36

archive tracing

standby databases and, 5-44, E-1

archived redo log files

accessing information about, 6-8, 8-37

affected by COMPATIBLE initialization parameter, 5-32

applying

Redo Apply technology, 1-5

SQ L Apply technology, 1-5

to physical and logical standby databases, 1-3

delaying application, 10-31, 12-16

on the standby database, 6-4

deleting unneeded, 9-4

destinat ions

disabling, 5-4

displaying with DBA_LOGSTDBY_LOG view, 10-20

displaying with V$ARCHIVE_DEST_STATUS view, < a href="views.htm#88204">14-2

enabling, 5-4

determining the most recently archived, 5-43

listing, 10-20

managing gaps, 1-13, 5-38

See also gap m anagement

manually transmitting, 10-43

over view, 2-11

redo data transmitted, 1-4, 6-1

registering, 5-42, 10-23

during failover, 7-24

partial, 10-24

retrieving missing, 10-23

specifying

directory location on the standby data base, 5-32

standby databases and, 6-7, 6-11

troubleshooting switchover problems, A-6

verifying the contents of, 12-53

archiver process (ARCn)

defined, 5-10

setting up cross-instance archival, B-6

verifying the contents of completed archived redo log files, 12-53

< /dl>

archiving

cross-instance, B-5

real-time apply, 6-3

specifying

failure resolution policies for, 5-24

network transmission modes for, 5-15

with the STANDBY_ARCHIVE_DEST initialization parameter, 5-9

starting, 3-14

to failed destinations, 5-24

See also archived redo log files

See also log transport services

ARCn process

See archiver process (ARCn)

ASYNC attribute

initiating network I/O operations, 12-45

LOG_ARCHIVE_DEST_n initialization parameter, 12-43

setting for data protection, 5-29

< /dl>

Asynchronous AutoLog, 5-3

asynchro nous network I/O operations, 12-43

attribute compatibility

LOG_ARCHIVE_DEST_n initialization parameter, 12-55

< /dd>

authentication

checks using SYS credentials, 5-19

to transfer redo data, 5-20

automatic detection of missing log files, 1-4, 1-12, 5-38

automatic failover, 7-2

< dd class="L1IX">Automatic Storage Management (ASM)

creating a standby database that uses, 10-46

automatic switchover, 7-2

See also switchovers

B

backup operations

after unrecoverable operations, 10-39

configuring on a physical standby database, 1-3

datafiles, 10-38

DB_FILE_NAME_CONVERT option of the RMAN DUPLICATE command, D-6

offloading on the standby database, 1-12

primary databases, 1-2, 7-18

used by the broker, 1-7

u sing RMAN, 8-18

benefits

Data Guard, 1-12

logical standby database, 2-4

physical standby database, 2-2

standby redo logs versus ar chived redo logs, 2-12

broker

com mand-line interface, 1-13

defined, 1-7

graphical user interface, 1-13

BUILD procedure

of DBMS_LOGSTDBY, 9-3

BUILDE R process, 9-11

C

CANCEL option

managed recovery and, 8-3

canceling

log apply services, 8-6

cascaded redo log destinat ions

defined, C-1

for logical standby databases, C-3

for physical standby databases, C-1, C-2

materialized view on logical standby databases, C-7

require standby redo log files, 2-12

role transitions, C-4

Redo Apply, C-4

SQL Apply, C-4

scenario, C-5 to C-8

< dd class="L1IX">changing

destination attributes, 12-2

global name

logical standby database, 4-16

logical standby database name, 4-15

checklist

tasks for creating physical standby databases, 3-6

tasks for creating standby databases, 4-7

C JQ0 process, A-8

CLEAR UNARCHIVED LOGFILES clause

< dd class="L2IX">of ALTER DATABASE, 8-9, 8-33

< dd class="L1IX">command-line interface

broker, 1-13

< /dd>

commands, Recovery Manager

DUPLICATE, D-2

COMMIT TO SWITCHOVER clause

of ALTER DATABASE, 7-12, 7-17, 7-21, 7-22, 10-34, 13-2, F-4

in Real Application Clusters, B-9

troubleshooting, A-6, A-8, A-9

COMMIT TO SWITCHOVER TO PRIMARY claus e

of ALTER DATABASE, 7-22

communication

between databases in a Data Guard configuration, 1-2

COMPATIBLE initialization parameter

effect on directory l ocation for archived redo log files, 5-32

complementary techn ologies, 1-10

configuration options

crea ting with Data Guard broker, 1-7

of redo logs, 2 -11

overview, 1-2

physical standby databases

location and directory structure, 2-8

requirements for password files, 5-20

standby databases

cross-instance archival, 5-3, B-5

delayed application of archived redo log files on, 10-31

delayed standby, 6-4

typical, 1 -3

configuring

backups on standby databases, 1-3

cascaded redo log destinations, C-2

disaster recovery, 1-3

initialization parameters

for alternate archive destinations, A-4

for physical standby database, 3-8

in anticipation of a failover, 7-9

in anticipation of a switchover, 7-6

to create a standby database with a time lag, 10-31

to set up l og transport services, 5-5

listener for physical standby data bases, 3-12

no data loss, 1-6

physical standby databases, 2-8

redo logs, 2-11

reporting operations on a logical standby database, 1-3

standby databases at remote locations, 1-3

standby redo log fil es, 5-26

standby redo log groups, 5 -27

constraints

handled on a logical standby database, 9-7

control files

altering, 8-18

copying, 3-11

creatin g for standby databases, 3-7, 4-13

effect o n physical standby databases, 8-18

modifying with ALTER DATABASE RENAME FIL E statement, 8-15

planning growth of, 5 -35

switchover and, 7-12

CONTROL_ FILE_RECORD_KEEP_TIME initialization parameter, 5-36

COORDINATOR proces s, 9-12

LSP background process, 4-19, 9-12

copying

a new tablespace to a remote standby database, 8-12

control files, 3-11

tablespace to a remote standby location, 8-12

CREATE CONTROLFILE clause

effect on physical standby databases, 8-18

of ALTER DATABASE, 8-10, 8-32

CREATE DATABASE statement

FORCE LOGGI NG clause, 10-36

CREATE DATAFILE AS clause

of ALTER DATABASE, A-2

CREATE STANDBY CONTROLF ILE clause

of ALTER DATABASE, 3-7, 4-14, 13-2, A-4

CR EATE TABLESPACE statement

skipping, 9-8

CREATE TEMPORARY TABLESPACE statement, 8-7

TEMPFIL E clause, 8-7

creating

back u p files for the primary database, 8-18

database link, 7-25

indexes on logical standby databases, 9-5

standby redo log files, 5-28

temporary files, 3-13, 4-16

for read-only physical stand by databases, 8-7

temporary tablespaces

for read-only physical standby databases, 8-7

traditio nal initialization parameter file

for physical standby database, 3- 8

for standby database, 4-11

cr oss-instance archival, 5-3

in Real Application Clusters c onfigurations, B-4

setting destinations, B-5

standby redo log files and, B-4

using the lo g writer process, B-4

D

data availability

balancing against system performance requirements, 1-12

data corruption

safeguarding against, 1-12< /dd>

Data Guard broker

defined, 1-7

Data Guard configurations

archiving to standby destinations usin g the archive process, 5-6

archiving to standby destinations using the log writer process, 5-17, 6-3

defin ed, 1-2

log transport services and, 5-2< /a>

protection modes, 1-9

data loss

due to failover, 1-6

minimizing, 7-15

switchover and, 7-2

data protection

balancing against performance, 1-12

benefits, 1-12

ensuring no data loss, 2-3

flexibility, 1-12

provided by Data Guard, 1-1

data protection modes

affect on network timeouts, 12-32

enforced by log transpo rt services, 1-4

influence on network reconnection, 12-32

maximum availability mode, 5-29, 13-4

maximum performance mode, 5-29, 13-4

maximum protection mode, 5-29, 13-4

minimum set of requirements, 5-29

overview, 1-9

setting up synchronous and asynchronous netw ork I/O operations, 12-43

specifying, 5-29

Data Pump utility

using transportable tablespaces with physical standby databases, 8-15

database incarnation

changes with OPEN RESETLOGS, 8-30, 9-23

database link

creating, 7-25

database roles

irreversible transitions, 1-6

LOGSTDBY_ADMINISTRATOR, 9-2

primary, 1-2, 7-2

role manag ement services, 1-6

role reversals, 1-6

SELECT_CATALOG_ROLE, 9-2

standby, 1-2, 7-2

transition, 7-2

database schema

physical standby databases, 1-2

databases

cascading standby databases See cascaded redo log destinations

failover a nd, 7-8

primary See primary database

role transition and, 7-2

surviving disasters and data corruptions, 1-1

upgrading software v ersions, 9-18

using password files, 5-2 0

datafiles

adding to primary database, 8-10

deleting from the primary database, 8-13

renaming on the primary database, 8-15

datatypes

filtering out unsupported from SQL Apply, 9-8

o n logical standby databases

supported, 4-2

unsupported, 4-2

tables unsupported by SQL Apply, 4-3

DB_FILE_NAME_CONVERT initialization parameter

location for transportable tablespaces, 8-14

DB_FILE_NAME_CON VERT option

RMAN DUPLICATE command, D-6

DB_NAME initialization parameter, 3-4, 11-3

DB_RECOVERY_FILE_DEST initialization parameter

setting up recovery areas, 5-6

DB_UNIQUE_NAME attribute

LOG_A RCHIVE_DEST_n initialization parameter, 12-14

DB_UNIQUE_N AME initialization parameter, A-9

required for shared fl ash recovery areas, 5-9

DBA_DATA_FILES view, 8-32

DBA_LOGMNR_PURGED_LOG view

list archived redo log files that can be deleted, 9-4

DBA_LOGSTDBY_EVENTS view, 9-10, 14-1, A-11

DBA_LOGSTDBY_LOG view, 6-13, 14-1

listing archived redo log files, 10-20

DBA_LOGSTDBY_NOT_U NIQUE view, 4-6, 14-1

DBA_LOGSTDBY_PARAMETERS v iew, 14-1

DBA_LOGSTDBY_PROGRESS view, 6-14, < a href="manage_ls.htm#1014274">9-14, 14-1

querying SCN informat ion and, 10-21

DBA_LOGSTDBY_SKIP view, 14-1

determining SQL Apply support for schemas, 4-3

DBA_LOGSTDBY_SKIP_TRANSACTION view, 14-1

DBA_LOGSTDBY_UN SUPPORTED view, 4-3, 14-1

DBA_TABLESPACES view, 8-32

DBMS_LOGSTDBY package

APPLY_SET p rocedure, 9-3

APPLY_UNSET procedure, 9-3

BUILD procedure, 9-3

INSTANTIATE_TABLE procedure, < a href="manage_ls.htm#1041846">9-3, 9-9

SKIP procedure, 9-3, 9-8, A-12

SKIP_ERROR procedure, 9-3, A-5

S KIP_TRANSACTION procedure, 9-3, A-12

UNSKIP procedure, 9-3, 9-9

UNSKIP_ER ROR procedure, 9-3

UNSKIP_TRANSACTION procedure, 9-3

using to manage SQL Apply, 9-2

DBMS_LOGSTDBY.APPLY_SET procedure

delay applying archived redo log files, 6-5

DBMS_LOGSTDBY.GUARD_BYPASS_OFF procedure, 9-18

DBMS_LOGSTDBY.GUARD_BYPASS_ON procedure, 9-18

DBMS_M VIEW.REFRESH routine

refreshing materialized views, 9-18

DBNEWID (nid) utility, 4-15

DBSNMP process, A-8

DDL transactions

filtering from SQL apply, 9-8

dead connection

t roubleshooting, A-13

DEFER attribute

LOG_ARCHIVE_DEST_STATE_n initialization parameter, 5-4, 10-35

DELAY attribute

LOG_ARCHIVE_DEST_n initializati on parameter, 6-4, 10-31, 12-16

DELAY option

of ALTER DATABASE RECOVER MANAGED STA NDBY DATABASE

cancelling, 6-5

delaying

application of archived redo log files, 10-31 , 12-16

application of redo log files, 6-4

deleting

archived redo log files

indicated by the DBA_LOGMNR_PURGED_LOG view, 9-4

not ne eded by SQL Apply, 9-4

datafiles, 8-13

online redo log files, 8-17

DEPEN DENCY attribute

LOG_ARCHIVE_DEST_n initialization parameter, 5-37, 12-19

destinations

changing attributes, 12-2

cross-instance archival, 5-3, B-4

defining role-based with VALID_F OR attribute, 7-10

displaying with V$ARCHIVE_DEST view, 14-2

Oracle Change Data Capture archival, 5-3

Oracle Streams archival, 5-3

role-based definitions, 12-50

setting cross-instance archival operations, B-5

shared, 5-37, 12-19

specifying, 5-4

verifying settings for role transitions, 10-9

detecting

missing archived redo log files, 1-4, 1-12, 5-38

network disconnects between primary and standby databases, 12-32

determining

the applied redo log data, 9-14

the highest applicable (newest) SCN, 10-20

direct path load operations

physical standby data bases and, 8-18

directory locations

archived redo log files, 5-32

Optimal Flexible Architecture (OFA ), 2-8

set up with ASM, 2-7, 2-8

set up with OMF, 2-7, 2-8

specifying with STANDBY_ARCHIVE_DEST initialization parameter, 5-32

< dd class="L2IX">structure on standby databases, 2-7

disabling

a destination for archived redo log files, 5-4

database guard to define a database link, 7-26

disaste r recovery

benefits, 1-12

configuring, < a href="concepts.htm#1038592">1-3

provided by Data Guard, 1-1

provided by standby databases, 1-3

ReadMe file at standby site, 10-13

DISCONNECT FROM SESSION, 8- 2

DML transactions

filtering from SQL apply, 9-8

downstream capture database

Oracle Streams and Data Guard log transport services, 5-3

DROP STANDBY LOGFILE claus e

of ALTER DATABASE, A-2

DROP STANDBY LOGFILE MEMBER clause

of ALTER DATABASE, 13-3, A-2

dropping

datafiles

examples, 8-13

online redo log files, 8-17

tablespaces from primary database, 8-13

dynamic parameters

AQ_TM_PROCESSES, A-8

JOB_QUEUE_PROCESSES, A-8

dynamic performance views, 8-33

See also views

E

ENABLE attribute

LOG_ARCHIVE_DEST_STATE_n initialization parameter, 5-4, 10-35

enabling

database guard on l ogical standby databases, 13-6

destinations for archived redo log files, 5-4

real-time apply

on logical standb y databases, 9-13

supplemental logging, 4-9

events

recording, 9- 10

viewing on logical standby databases, 9-10

EXPIRE_TIME parameter

setting on the standby database, 12-32

F

failovers, 1-6

and cascaded redo log configurations, C-4

defined, 1-6, 7-2

determining the target logica l standby database, 10-19

logical standby databases and, 7-22, 10-10, 10-19

manual versus automatic, 7-2

minimal data loss and, 10-22

minimal performance impact, 10-22

physical standby databases and, 7-14, 10-10, 13-5

preparing for, 7-9

re-creating after, 7-15

transferring redo data before, < a href="role_management.htm#1023738">7-9

with maximum performance mode, 7-10

with maximum protection mode, 7-10

with real-time apply enabled, 7-3

failure resolution polici es

specifying for log transport services, 5-24

< /dd>

FAL_CLIENT initialization parameter, 5-40

FAL_SER VER initialization parameter, 5-40

false network failure detection, 12-32, 12-33

fixed views

See views

flash recovery areas

default location, 5-6, 5-7, 12-24

setting up, 5-6

sharing among multiple databases, 5-9< /dd>

STANDBY_ARCHIVE_DEST=LOCATION parameter, 5-9

Flashback Database

after OPEN RESETLOGS, 10-28

characteristics complementary to Data Guard, 1-10

logical stan dby database, 10-27

physical standby database, 10-25

FORCE LOGGING clause

of ALTER DATABASE, 2-7, 3-2, 10-36, 13-3

of ALTER TABLESPACE, 8-18

of CREATE D ATABASE, 10-36

G

gap management, 5-38

automatic detection and resolution, 1- 4, 1-12

defined, 5-38

detecting missing log files, 1-13

registering archived redo log files, 5-42

during failover, 7-24

See also archived redo log files

global dynamic performance views, 8-34

See also views

globa l name

changing

logical standby databases, 4-16

GUARD clause

of ALTER DATABASE, 9-3

GUARD DISABLE clause

of ALT ER SESSION, 7-26

GUARD ENABLE clause

of ALTER SESSION, 13-6

GV$ fixed views, 8-34

See also views

GV$INSTANCE view, B-9

H

hardware

requirements for Data Guard configurations, 2-5

high availability

benefits, 1-12< /dd>

provided by Data Guard, 1-1

provided by RAC and Data G uard, 1-10

I

incarnation of a database

changed, 8-30, 9-23

initialization parameter file

creating from server parameter file

for physical standby database, 3-8

for standby database, 4-11

modifying

for physical sta ndby database, 3-8

initialization parameters

CONTROL_FILE_RECORD_KEEP_TIME, 5-36

DB_FILE_NAM E_CONVERT, D-7

DB_UNIQUE_NAME, A-9

FAL_CLIENT, 5-40

FAL_SERVER, 5-40

LOG_ARCHIVE_DEST, 10-45

LOG_A RCHIVE_DEST_n, 12-1 to 12-55

< dd class="L2IX">LOG_ARCHIVE_DEST_STATE_n, 5-4

LOG_ARCHIVE_FORMAT, 5-33

LOG_ARCHIVE_MIN_SUCCEED_DEST, 1 2-26

LOG_ARCHIVE_TRACE, 5-44, E-1, < a href="trace.htm#637281">E-2

LOG_FILE_NAME_CONVERT, D-7

modifying for physical standby databases, 3-8

PARALLEL_MAX_SERVERS, 4-13, 9-28

setting for both the primary and standby roles, 12-50

SORT_AREA_SIZE, 8-9

STANDBY_ARCHIVE_DEST, 5-32

USER_DUMP_DE ST, E-1

initiating

network I/O ope rations, 12-45

INSTANTIATE_TABLE procedure

of DBMS_LOGSTDBY, 9-3, 9-9

irreversible role transitions, 1-6

J

JOB_ QUEUE_PROCESSES dynamic parameter, A-8

K

keywords

on the VALID_FOR attribute, 12-51

L

LGWR attribute

LOG_ARCHIVE_DEST_n initialization parameter, 12-12

setting for data protection, 5-29

LGWR process

See log writer process (LGWR)

listener.ora file

configuring, 3-12

log transport services tuning and, A-13

troubleshooting, 10-35, A-3, A-13

listing

archived redo log files, 10-20

LOCATIO N attribute

setting

flash recovery area with USE_DB_RECOVERY_ FILE_DEST, 5-8

LOG_ARCHIVE_DEST_n initialization parameter, 12-23, A-4

log ap ply services

and role transitions, A-9

defined, 1-4, 6-1

delaying applicat ion of redo data, 6-4, 10-31, 12-16

real-time apply

and role transitions, 7-3

and standby redo log files, 2-11

defined, 6-1, 6-3

monitoring with L OG_ARCHIVE_TRACE, E-3

monitoring with V$ARCHIVE_DEST_STATUS view, 6-8

Redo Apply

defined, 6-2

monitoring, 6-7, 8-34< /a>

starting, 6-6, 8-1

stopping, 6-7, 8-3

tuning the log apply rate, 6-16

SQL Apply

d efined, 1-5, 6-2

managing with DBMS_LOGS TDBY package, 9-2

monitoring, 6-11, 9-11

starting, 4-14, 6-11

stopping, 6-11

log transport services, 5-1 to 5-44

archive destinations

alternate, A-4

cross-instance, 5-3

Oracle Change Data C apture, 5-3

Oracle Streams, 5-3

quotas, B-7

re-archiving to failed destinations, 5-24

role-specific, 5-21

shared, 5-37, 12-19

specifying with the LOG_ARCHIVE_DEST_n initialization parameter, 5-5

< dd class="L2IX">archived redo log files

generating filenames, 5-33

listing with V$ARCHIVED_LOG view, 5-33

specifying directory locations for, 5-32

defined, 1-4, 5-1

handling archive failures, 5-24

monitoring, 5-42, 5-44

network

ASYNC network transmission, 5-16

SYNC network transmission, 5-15

tuning, A-12

protection modes

choosing, 5-25

maximum availability mode, 1-9, 5-25

maximum performance mode, 1-9, 5-26

maximum protection mode, 1-9, 5-25

providing no data loss, 5-15

setting, 5-29

secure redo transmission, 5-19

standby redo log files

configuring, 5-26

log w riter process (LGWR)

ASYNC network transmission, 5-16, 12-43

defined, 5-14

local archiving, 5-4

NET_TIMEOUT attribute

of LOG_ARCHIVE_DEST_n initialization parameter, 12-32

reconnecting after a network timeout, 12-32

SYNC network transmission, 12-43

LOG_ARCHIVE_DEST_10 initiali zation parameter

default flash recovery area, 5-6, 5-7, 12-24

LOG_ARCHIVE_ DEST_n initialization parameter, 12-1 to 12-55

AFFIRM attribute, 12-2, 12-4

setting for data protection, 5-29

ALTERNATE attribute, 12-7, A-4

ARCH attribute, 12-12

< dd class="L3IX">setting for data protection, 5-29

ASYNC attri bute, 12-43

setting for data protection, 5-29

attribute compatibility, 12- 55

DB_UNIQUE_NAME attribute, 12-14

DELAY attribute, 6-4, 10-31, 12-16

DEPENDENCY attribute, 5-37, 12-19

LGWR attribute, 12-12

setting for data protection, 5-29

LOCATION attribu te, 12-23, A-4

MANDATORY a ttribute, 12-26

MAX_FAILURE attribute, 12-28, 12-42

NET_TIMEOUT attribute, 12-31

NOAFFIRM attribute, 12-4

NOALTERNATE attribute, 12-7, A-4< /dd>

NODB_UNIQUE_NAME attribute, 12-14

NODELAY att ribute, 6-4, 12-16

NODEPENDENCY attribute, 12-19

NOMAX_FAILURE attribute, 12-28, 12-42

NONET_TIMEOUT attribute, 12-31

NOQUOTA_SIZE attribute, 12-3 4

NOQUOTA_USED attribute, 12-37

NOREGISTE R attribute, 12-39

NOREOPEN attribute, 5-24, 12-41

NOTEMPLATE attribute, 12-47

NOVERIFY attribute, 12-53

ONDEMAND attribute, 12-34

OPTIONAL attribute, 12-26

overview, 5-4

QUOTA_SIZE attribute, 12-34, B-7

QUOTA_USED attribute, 12-37

REOPEN attribute, 5-24, 12-41

SERVICE attribute, 12-23

se tting up recovery areas, 5-6

SYNC attribute, 5-15, 12-43

setting for data protection , 5-29

TEMPLATE attribute, 12-47

VALID_FOR attribute, 5-21, 12-50

VERIFY attribute, 12-53

LOG_ARCHIVE_DEST_STATE_n initialization parameter, 5-4

ALTERNATE attribute, 5-4

DEFER attribute, 5-4, 10-35

ENABLE attribute, 5-4, 10-35

RESET attribute, 5-4

LOG_ARCHIVE_FORMAT initialization parameter, 5-33< /dd>

LOG_ARCHIVE_MIN_SUCCEED_DEST initialization parameter, 12-26

< dd class="L1IX">LOG_ARCHIVE_TRACE initialization parameter, 5-44, E-1, E-2

logical corruptions

resolving, 1-12

logical standby databases

access for queries and reporting purposes, 1-3

adding

datafiles, 9-16

indexes, 1-12 , 2-4, 9-5

tables, 9-9

applying redo data, 6-10

applying redo log files

DBMS_LOGSTDBY.APPLY_SET procedure, 6-5< /a>

delaying, 6-5

SQL Apply technology, 1-5

SQL apply technology, 6-2

s upported datatypes, 4-2

unsupported objects, 4- 3

background processes, 4-19, 9 -12

benefits, 1-12, 2-4

cascading, C-1, C-3

changing the global name, 4-16

controlling user access to database tables, 9-3

creating

modifying initialization parameters f or, 4-13

with Data Guard broker, 1-7

< /dl>

DDL statements automatically skipped, 4-4

defined, 1-3

enabling

supplemental logging on, < a href="create_ls.htm#92479">4-11

executing SQL statements on, 1-3

failovers, 7-22, 10-10

target of, 10-19

handling failures , A-5

logical standby process (LSP) and, 4-19, 9-12

managing, 9-1 to 9-28

materialized views

creating on , 1-12, 2-4, C-4, C-7

refreshing on, 9-18

s upport for, 4-4

monitoring, 9-10, 14-1

SQL Apply, 6-11

parallel execution processes, 9-28

read-only opera tions, 1-12

recovering through OPEN RESETLOGS, 9-23

scenarios

recovery, 10-36

setting VALID_FOR attribute, 10-4

skipping

SQL statements, 4-4, 9-7

tables, 9-7

SQL Apply technology, 1-5, 6-2

starting

real-time apply, 6-11, 9-13

SQL Apply , 4-14, 6-11

stopping

SQL Appy, 6-11

supported datatypes, 4-2

switchovers, 7-19, 10-10

tuning system performance, 9-24

uniquely identifying tables, 4-5

unsupported

datatypes, 4-2

sequences, 4-3

tables, 4-3

upgrading Oracle database software on, 9-18

zero downtime instantiation, 4-7

logical standby process (LSP)

ARCn archival processing, 5-11, 5-13

COORDINATOR process, 4-19, 9-12

LGWR SYNC archival processing, 5-17

M

managed recovery operations

See Redo Apply

managed rec overy process (MRP)

ARCn archival processing, 5-11, 5-13

LGWR SYNC archival processing, 5-17

See also Redo Apply

MANDATORY attribute

LOG_ARCHIVE_DEST_n initialization parameter, 5-34, 12-26

materialized views

creating on logical standby databases, 1-12, 2 -4, C-7

on cascaded redo log destinations, C-4

refreshing on logical standby databases, 9-18

MAX_FAILURE attribute

LOG_ARCHIVE_DEST_n initialization parameter, 12-28, 12-42

maximum ava ilability mode

defined, 5-25

influe nce on network reconnection, 12-32

introduction, 1-9

requires standby redo log files, 2-12

setting, 5-29

maximum performance mode, 7-10

influence on network reconnection, 12-32

introduction, 1-9, 5-2 6

setting, 5-29

maximum protection mode

for Real Application Clusters, B-7

influence on network reconnection, 12-32

introduction, 1-9, 5-25

requires standby redo log files, 2-12

setting, 5-29

standby databases and, 7-10

media recovery

parallel, 6-17

missing log sequence

See also gap management

d etecting, 1-12, 1-13

modifying

a logical standby database, 9-5

initial ization parameters for logical standby databases, 4-13

initialization paramet ers for physical standby databases, 3-8

monitoring

log apply services, 6-8

log transport services, 5-42

standby databases, 8-9

MOUNT STANDBY DATABASE clause

of ALTER DATABASE, 13-3

MRP

See managed recovery process

N

NET_TIMEOUT attribute

LOG_ARCHIVE_DEST_n initialization parameter, 12-31

network I/O operations

coordinating timeout parameter values, 12-33

detecting a disconnect, 12-32

false failures, 12-32, 12-33

influence of data protection modes, 12-32

initiat ing, 12-45

network timers

EXPIR E_TIME parameter, 12-32

NET_TIMEOUT attribute, 12-31

setting comparably on primary and standby databases, 12-32

setting up synchronous or asynchronous, 12-43

troubleshooting, A-13

tuning

log transport services, A-12

network timeouts

acknowledging, 12-32

NEWEST_SCN column

of DBA_LOGSTDBY_PROGRESS view, 10-21

no data loss

benefits, 1-12

data protection modes overview, 1-9

ensuring, 1-6, 2-3

environments, 5-15

guaranteeing, 1-6

pr ovided by maximum availability mode, 1-9, 5-25

provided by maximum protection mode, 1-9, 5-25< /dd>

NOAFFIRM attribute

LOG_ARCHIVE_DEST_n initialization parameter, < a href="log_arch_dest_param.htm#96914">12-4

NOALTERNATE attribute

LOG_ARCHIVE_DEST_n initialization parameter, 12-7, A-4

NODB_UNIQUE_NAME attribute

LOG_ARCHIVE_DEST_n initial ization parameter, 12-14

NODELAY attribute

LOG_ARCHIVE_DEST_n initialization parameter, 6-4, 12-16

NODELAY option

of Redo Apply operations, 10-33

NODEPENDENCY attribute

LOG_ARCHIVE_DEST_n initialization parameter, 12-19

NOMA X_FAILURE attribute

LOG_ARCHIVE_DEST_n initialization parameter, 12-28, 12-42

NONET_TIMEOUT attribute

LOG_ARCHIVE_DEST_n initialization parameter, 12-31

< /dd>

NOQUOTA_SIZE attribute

LOG_ARCHIVE_DEST_n initialization parameter, 12-34

NOQUOTA_USED attribute

LOG_ARCHIVE_DEST_n initialization parameter, 12-37

NORE GISTER attribute

LOG_ARCHIVE_DEST_n initialization parameter, 12-39

NOREOPEN attribute

LOG_ARCHIVE_DEST_n initializati on parameter, 5-24, 12-41

NOTEMPLATE attribute

LOG_ARCHIVE_DEST_n initialization parameter, 12-47

NOVERIFY attribute

LOG_ARCHIVE_DEST_n initialization parameter, 12-53

O

of the ALTER DATABASE statement, 8-15

ONDEMAND attribute

LOG_ARCHIVE_DEST_n initialization parameter, 12-34

on-disk database structures

physical standby databases, 1-2< /a>

online redo log files

adding, 8-17

archive gap management, 5-38

deleting, 8-17

dropping, 8-17

OPEN READ ONLY clause

of ALTER DATABASE, 13-3

OPEN RESETLOGS clause

database incarnation change, 8-30, 9-23

of ALTER DATABASE, 3-7, 4-16, 8-33

recovery, 8-30, 9-23

operating systems

requirements for Data Guard configurations, 2-5

operational requirements, 2-5, 2-6

standby databases

operating system requirements, 2-5

Optimal Flexible Architecture (OFA)

directory structure, 2-8

OPTIONAL attribute

LOG_ARCHI VE_DEST_n initialization parameter, 5-34, 12-26

ORA-01102 message

causing switchover failures, A-9

Oracle Advanced Security

providing secu re redo transmission, 5-19, 5-20

Oracle Automatic Storage Management (ASM), 2-7, 2-8

Oracle Change Data Capture archival, 5-3

Oracle Manage d Files (OMF), 2-7, 2-8

creating a standby database that uses, 10-46

Oracle Net

communication between databases in a Data Guard configuration, 1-2

setting the EXPIRE_TIME parameter, 12-32

Oracle Recovery Manager utility (RMAN)

backing up files on a physical standby database, 8-18

Oracle Streams

archival, 5-3

downstream capture database, 5-3

P

parallel execution processes

logical standby databases, 5-11

adjusting, 9-28< /dd>

physical standby databases, 5-11

tuning the log apply rate, 6-16

specifying

MAX_SERVERS parameter of the DBMS_LOGSTDBY.APPLY_SET procedure, 9-28

< dd class="L3IX">PARALLEL_MAX_SERVERS initialization parameter, 4-11, 4-12, 4-13, 6-17, 9-28, 11-5

PARALLEL option

of Redo Apply operations, 6-8

tuning the log apply rate for Redo Apply , 6-16

parallel recovery

on p hysical standby databases, 6-8

PARALLEL_MAX_SERVERS initializatio n parameter, 4-13, 9-28

spe cifying

creating a logical standby database, 4-11, 6-17, 11-5

partial archived r edo log files

registering, 10-24

password files

requirements, 5-20

setting REMOTE_LOGIN_PASSWORDFILE initialization parameter, 5-20

performance

balancing against data availability, 1-12

balancing against data protection, 1-12

monitoring log transport services, 5-44

physical standby databases

altering

control files, 8-18

online redo log files, 8-17

applying redo log fi les, 1-5, 6-2

cascading, < a href="cascade_appx.htm#636031">C-1

starting, 6-6

benefits, 2-2

configuration options, 2- 8

delayed standby, 6-4

cr eating

checklist of tasks, 3-6

configurin g a listener, 3-12

directory structure, 2-10< /dd>

initialization parameters for, 3-8

temporary tablespace , 8-7

traditional initialization parameter file, 3-8

with Data Guard broker, 1-7

crea ting and associating a temporary tablespace with temporary files, 8-7

defin ed, 1-2

direct path load operations, 8-18

failover, 10-10

checking for updates, 7-11

preparing for, 7-9

monitoring, 6-7, 8-9, 14-1

online backups and, 2-3

read-on ly, 2-2, 8-3

recovering through OPEN RESETL OGS, 8-30

Redo Apply, 2-2

resynchronizing with primary database branch of redo, 8-30, 9-23

role transition and, 7-11

setting VALI D_FOR attribute, 10-2

shutting down, 8-3

starting

log apply services, 6-6

support for DDL, 2-3

support for DML, 2-3

switchovers, 7-11, 10-10

using transportable tablespaces, 8-14

PREPARE TO SWITCHOVER clause

of ALTER DATABASE, 7 -20, 13-3

PREPARER process, 9 -11

primary database

backups and, 7-18, 8-18

configuring

for cross-i nstance archival, B-4

on Real Application Clusters, 1-2

single-instance, 1-2

datafi les

adding, 8-10

renaming, 8-13

defined, 1-2

fa ilover and, 7-2

gap resolution, 1-13

gathering redo log archival information, 5-43

initialization parameters

and physical standby database, 3-8

log transport services on, 1-4

network connect ions

avoiding network hangs, 12-31

detecting disconnections, 12-32

handling network timeouts, 12-32

terminating, 12-32< /dd>

preparing for

logical standby database creation, 4-1

physical standby database creation, 3-1

Real Application Clusters and

setting up, B-2, B-5

reducing workload on, 1-1 2

setting archive tracing, 5-44

sharing a fla sh recovery area, 5-9

switchover, 7-4

switchovers

initiating, 7-12

tablespaces

adding, 8-10

dropping, 8-13

primary role, 1-2

processes

archiver (ARCn), 5-10

CJQ0, A-8

DBSNMP, A-8

log writer (LGWR), 5-14

preventing switchover, A-8

QMN0, A-8

See a lso managed recovery process (MRP)

production database

< em class="Italic">See primary database

protection modes

maximum availability mode, 1-9, 5-25

maximum performance mode, 1-9, 5-26

maximum protection mode, 1-9, 5-25

See data protection modes

Q

QMN0 process, A-8

queries

improved performance, 1-12

offloading on the st andby database, 1-12

QUOTA_SIZE attribute

LOG_ARCHIVE_DEST_n initialization parameter, 12-34, B-7

QUOTA_USED attribute

LOG_ARCHIVE_DEST_n initiali zation parameter, 12-37

R

raw devices

standby redo log files residing on, 2-12

READER process, 9-11

read-only operations, 1-4

definition, 2-2

logical standby databases, 1-12

physical standby databases and, 8-3

Real Application Clusters, 5-3, B-3

characteristics complementary to Data Guard, 1-10

cross-instance archival, B-4

instance re covery, B-5

performing switchover and, 7-7, B-8

primary databases and, 1-2< /a>, B-2, B-5

setting

cross-instance archiving, B-5

maximum data protection , B-7

standby databases and, 1-2< /a>, B-1, B-4

using standby redo log files, 5-28, B-4

using standby red o logs, 2-12

real-time apply

and role transitions, 7-3

and SQL Apply, 9-13

defined, 6-1, 6-3

monitoring progress in V$ARCHIVE_DEST_STATUS, 6-8

overview of log apply services, 1-4

require standby redo log files, 2-12

RFS process with, 6-1

starting, 6-7

on logical standby, 6-11

starting on logical standby databases, 9-13

st opping

on logical standby, 6-11

on phys ical standby databases, 8-3

tracing data with LOG_ARCHIVE_TRACE i nitialization parameter, E-3

using standby redo log files, 2-11

recommendations for secure redo transmission, 5-1 9

reconnecting

after a network timeout, 12-32

network connection

when in maximum availability mode, < a href="log_arch_dest_param.htm#101930">12-32

when in maximum performance mode, 12-32

when in maximum protection mode, 12-32

recording logical standby database events, 9-10

RECOVER MANAGED STANDBY DATABASE clause

of ALTER DATABASE, 3-14, 4-14, 4-17, 6-5 , 6-6, 8-6, 8-8, 10-18, 10-33, 13-4, 13-5

background process, 6-6, 8-2

canceling

log apply services, 6-7, 8-6

controlling Redo Apply, 6-6

foreground session, 6-6

initiating failover, 7-17

overriding the delay interval, 6-5, 12-17

starting real time apply, 6-7

switchover scenario, 10-33

recovering

after a NOLOGGING clause is specified, 10-36

from errors, 9-15

physical standby databases

after an OPEN RESETLOGS, 8-30, 9-23

through resetlogs, 8-30, 9-23

Recovery Manager

characteristics co mplementary to Data Guard, 1-11

commands

DUPLICATE, D-2

DB_FILE_NAME_CONVERT option of the DUPLICATE comman d, D-6

standby database

creating, D-2, D-8

creating standby control files, D-3

creating using image copies, D-20

DB_FILE_NAME_CONVERT initialization parameter, D-7

LOG_FILE_NAME_CONV ERT initialization parameter, D-7

naming standby datafiles, D-5

preparing using RMAN, D-2

starting RMAN and standby instance, D-10

re-creating

a table on a logical standby database, 9-9

Redo Apply

defined, 1-5, 2-2 , 6-2

flashing back after failover, 10-25, 10-27

monitoring, 6-8

options

NODELAY, 10-33

PARALLE L, 6-8

role transitions and cascaded redo log configurations, C-4

starting, 3-14, 6-7

stopping, 8-3

technology, 1-5

tuning the log apply rate, 6-16

redo data

applying

through Redo Apply tech nology, 1-5

through SQL Apply technology, 1-5

to standby database, 6-1

to standby databases, < a href="concepts.htm#1033716">1-2

archiving on the standby system, 1-4, 6-1

transmitting, 1-2, 1-4, 5-1 to 5-24

validated, 1-12

redo log files

delaying application, 6-4

redo logs

automatic application on physical standby databases, 6-6

configuration considerations, 2-11

in Data Guard configurations, 2-11

logging supplemental information, 4-8, < a href="create_ls.htm#91575">4-9

secure redo transmission, 5-20

update standby database tables, 1-12

refreshing materialized views, 9-18

LOG_ARCHIVE_DEST_n initialization parameter, 12-39

of ALTER DATABASE, 12-40, 13-4, A-6

of ALTER DATABASE, 5-42, 7-24, 10-23

LOG_ARCHIVE_DEST_n initialization parameter, 12-41

registering

archi ved redo log files, 5-42, 10-23

during failover, 7-24

partial archived redo log files, 10-24

RELY constraint

creating, 4-7

remote file server process (RFS)

< dd class="L2IX">defined, 2-10, 5-17, 6-1

log writer process and, 6-3, 12-13

standby redo log files reused by, 5-34

REMOTE_LOGIN_PASSWORDFILE initialization parameter

secure redo transmission, 5-20

RENAME FILE clause, 8-15

of ALTER DATABASE, A-2

RENAME GLOBAL_NAME clause of the ALTER DATABASE statement, 4-16

renaming

datafiles

on the primary database, 8-15

setting the STANDBY_FILE_MANAGEMENT parameter, 8-15

REOPEN attribute

LOG_ARCHIVE_DEST_n initialization parameter, < a href="log_transport.htm#1232785">5-24, 12-41

report ing operations

configuring, 1-3

offloadi ng on the standby database, 1-12

performing on a logical standby database, < a href="concepts.htm#1038229">1-3

requirements

data protectio n modes, 5-29

RESET attribute

LOG_ARCHIVE_DEST_STATE_n initialization parameter, 5-4

R ESETLOGS_ID columns

viewing in V$DATABASE_INCARNATION view, 8-36< /a>

resolving

logical corruptions, 1-12

resynchronizing

physical standby databases with a new b ranch of redo, 8-30, 9-23

ret rieving

missing archived redo log files, 1-4, 1-12, 5-38, 10-23

reusing records in the control files, 5-35

RFS

See remote file server process (RFS)

role management services

defined, 1-6, 7-1

role transitions, 7-2

and cascaded redo log configurations, C-4

choosing a type of, 7-2

d efining role-based with VALID_FOR attribute, 7-10

logical standby dat abase and, 7-19

physical standby databases and, 7-11

reversals, 1-6, 7-2

with real-time apply, 7-3

role-based destinations

setting, 12-50

rollback

after switchover failures, A-10< /a>

S

scenarios

cascaded redo log destinations, C-5 to C-8

choosing best st andby database for role transition, 10-10

recovering

a logical standby database, 10-36

after NOLOGGING is specifie d, 10-36

from a network failure, 10-35< /dd>

time lag in redo logs, 10-31

sche mas

data manipulation on logical standby databases, 1-12

DBA_LOGSTDBY_SKIP list of skipped, 4-3

identical to primary database, 1-2

skipped by SQL Apply, 4-3

SCN

determine the highest applicable (newest), 10-20

secure redo transmission, 5-19

sequences

unsupported on logical standby databases, 4 -3

SERVICE attribute

LOG_ARCHIVE_DEST_n initialization parame ter, 12-23

SET STANDBY DATABASE clause

of ALTER DATABASE, 7-10, 13-4

setting

data protection mode, 5-29

network timers on primary and standby databases, 12-32

VALID_FOR attributes

for a logical standby database, 10-4

for a physical standby database, 10-2

< dd class="L1IX">sharing

destinations, 5-37, 12-19

flash recovery area, 5-9

shutting down

physical standby database, 8-3

SKIP procedure

of DBMS_LOGSTDBY, 9-3, 9-8, A-12

SKIP_ERROR procedure

of DBMS_LOGSTDBY, 9-3

of the DBMS_LOGSTDBY package, A-5

SKIP_TRANSACTION pr ocedure

of DBMS_LOGSTDBY, 9-3, A-12

skipping

ALTER TABLESPACE, 9-8

standby redo log files, 10-33

SORT_AREA_SIZE initialization parameter, 8-9

SQL Apply, 6-11

ANALYZER process, 9-12

APPLIER process, 9-12

BUILDER process, 9-11

COORDINATOR process, 9-12

DBMS_LOGSTD BY PL/SQL package and, 9-2

defined, 1-5, 6-2

deleting archived redo log files, 9-4< /a>

managing, 9-2

PREPARER process, 9-11

READER process, 9-11

role tra nsitions and cascaded redo log configurations, C-4

schemas skipped, 4-3

starting

real-time apply, 6-11

stopping

real-time apply, 6-11

uniquely identifying table rows, 4-5

unsupported table datatypes, 4-3

unsupported tables using table compression, 4-3

viewing activity with V$LOGSTDBY view, 9-11

what to do if it stops, A-11

with real-time apply, 9-13

SQL sessions

causing switchover failures, A-6

SQL state ments

executing on logical standby databases, 1-3, 1-5

skipping on logical standby databases, 4-4, 9-8

switchover and, 7-12

standby databases

about creating using RMAN, D-2

applying redo data on, 6-1

applying redo log fil es on, 1-4, 1-12

cascading, C-1

configuring, 1-2

cross-instance archival, 5-3, B-4, B-5

delayed application of archived redo log files on, 10 -31

mandatory destinations, 5-34

maximum numb er of, 2-1

network connections, 12-32< /a>

on Real Application Clusters, 1-2, B-1< /a>, B-4

on remote locations, 1-3

optional destinations, 5-34

single-instance, 1-2

creating, 1-2, 3-1, 4-1

checklist of tasks, 4-7

directory structure considerations, 2-7

if primary uses ASM or OMF, 10-46

on local host, D-19

on remote host with different directory structure, D-13

on remote host with same directory structure, D-11

traditional initialization parameter file, 4-11

using RMAN, D-8

using image copies, D-20

with a time lag, 6-4, 10-32

creating control files

using RMAN, D-3

DB_FILE_NAME_CONVERT initialization parameter, D-7

defin ed, 2-1

failover to, 7-8

re-creating after, 7-15

hardware re quirements, 2-5

log apply services on, 6-1< /dd>

LOG_FILE_NAME_CONVERT initialization parameter, D-7

mod ifying the control file, 8-15

naming datafiles using RMAN, D-5

operational requirements, 2-5, 2-6

preparing to use RMAN, D-2

recovering through OPEN RESETLOGS, 8-30, 9-23

resynchroni zing with the primary database, 1-13

reverting back to primary database, A-10

SET AUXNAME command, D-7

SET NEWNAME command, D-6, D-7

sharing

a flash recovery area, 5-9

skipping standby redo log files, 10-33

starting log apply service s on physical, 6-6

starting RMAN and standby instance, D-10

viewing RESETLOGS_ID, 8-36

wait ev ents configured for, 5-44

See also logical standby databases

See also physical standby databases

standby redo log files

ad vantages, 2-12

and real-time apply, 2-11, 6-3

creating, 5-26, 5-28

log groups and members, 5-27

cross-instance archival and, B-4

network tran smission modes for, 5-15

on raw devices, 2- 12

overview, 2-12

Real Application Clusters and, 5-28, B-4

requirements for

cascaded log destinations, 2-12

maximum availability m ode, 2-12

maximum protection mode, 2-12

protection modes, 1-10

real-time apply, 2-12

standby redo log groups

adding members, 5-35

determining if you have enough, 5-34

recommended number, 5-27

st andby role, 1-2

STANDBY_ARCHIVE_DEST initialization parameter, 5-32

archiving to the recovery area, 5-9

implicit default value, 5-32

STANDBY_FILE_MANAGEMENT initialization parameter

setting for transportable tablespaces, 8-15

when renaming datafiles, 8-15

START LOGICAL STANDBY APPLY clause

IMMEDIATE keyword, 6-11, 9-14

of ALTER DATABASE, 4- 17, 6-11, 7-26, 13- 5, A-12

starting

log ical standby databases, 4-14, 4-15, 4-16

physical standby databases, 3-13

real-time ap ply, 6-11

on logical standby databases, 6-11, 9-13

on physical standby databases, 6-7

Redo Apply, 3-14, 6-7, 8-1

SQL Apply, 4-17, 6-11

STOP LOGICAL STANDBY APPLY clause

of ALTER DATABASE, 6-11, 7-25, 10-23, 13-5

stopping

real-time apply

on logical standby databases, 6-11

real-time apply on physical standby databases, 6-7

Redo Apply, 6-7

SQL Apply, 6-11

superceding

apply delay interval, 6-5

supplemental logging

adding data to redo logs, 4-8, 4-9

creating a unique key, 4-6

enabling on the logical standby database, 4-11

on primary database, 4-8

SUPPLEMENTAL_LOG_DATA_PK column

of V$DATABASE, 4-9

SUPPLEMENTAL_ LOG_DATA_UI column

of V$DATABASE, 4-9

SWITCHOVER_STATUS column

of V$DATABASE view, 7-12, 7-13, A-6

switc hovers, 1-6

and cascaded redo log configurations, C-4

Redo Apply, C-4

SQL Apply, C-4

control files and, 7-12

defined, 1-6, 7-2

fails with ORA-01102, A-9

failure to apply redo data after, A-9

initiating on the primary database, 7-12

logical standby databases and, 7- 19, 10-10

manual versus automatic, 7-2

no data loss and, 7-2

physical standb y databases and, 7-8, 7-11, 7-13, 10-10

preparing for, 7-6

prevented by

active SQL sessions, A-6

active user sessions, A-8

CJQ0 process, A-8

DBSNMP process, A-8

processes, A-8

QMN0 process, A-8

seeing if the last archived redo log file was transmitted, A-6

SQL statements and, 7-12

standby databases not involved in, 7-14

starting ove r, A-10

typical use for, 7-4

using Real Application Clusters and, 7-7, B-8

V$DATABASE view and, 7-12, 7-13

verifying, 7-13

with real-t ime apply enabled, 7-3

SYNC attribute

LOG_ARCHIVE_DEST_n initialization parameter, 5-15, 12-43

setting for data protection, 5-29< /dd>

SYS user account

password file requirements, 5-20

REMOTE_LOGIN_PASSWORDFILE initialization parameter, 5-20

system resources

efficient utilization of, < a href="concepts.htm#1037439">1-12

T

tables

da tatypes unsupported by SQL Apply, 4-3

logical standby databases

adding on, 9-9

identifying rows in, 4-5

re-creating tables on, 9-9

skip ping on, 9-7

unsupported on, 4-3

using table compression, 4-3

tablespaces < dl class="L2IX">

adding

a new datafile, 9-17

to primary database, 8-10

creating and ass ociating temporary files, 8-7

dropping from primary database, 8-13

moving between databases, 8-14

sorting without, 8-8

TCP/IP network interconnect

expired network timers, 12-32

TEMPFILE clause

of ALTER DATABASE, 3-13, 4-17

of CREATE TEMPORARY TABLESPACE, 8-7

TEMPLATE attribute

LOG_ARCHIVE_DEST_n initialization parameter, 12-47

tempfiles

See temporary files

temporary files

adding, 3-13, 4-17, 8-7

creating, 3-13, 4 -16, 8-8

and associating with a temporary tablespace, 8-7

temporary tablespaces

adding tempfile entries, 8-7

creating, 8-7

on physical standby databases, 8-7

terminating

network connection, 12-31

time lag

delaying application of archived redo log files, 6-4, 10-31, 12-16

in standby database, 6-4, 10-32, 12-16

tnsnames.ora file

log transport services t uning and, A-13

troubleshooting, 10-35 , A-3, A-9, A-13

trace files

levels of tracing data, E-2

location of, E-1

setting, E-2

tracking real-time apply, E-3

transportable tablespaces

defining location with DB_FILE_NAME_CONVERT parameter, 8-14

setting the STANDBY_FILE_MANAGEMENT parameter, 8-15< /a>

using with a physical standby database, 8-14

triggers

handled on a logical standby database, 9-7

troubleshooting

dead network connections, A-13

if SQL Apply stops, A-11

las t redo data was not transmitted, A-6

listener.ora file, 10-35, A-3, A-13

logical standby database failures, A-5

processes that preven t switchover, A-8

SQL Apply, A-11

switchovers, A-5

active SQL s essions, A-6

active use sessions, A-8

ORA-01102 message, A-9

redo is not appl ied after successful, A-9

roll back and start over, A-10

tnsnames.ora file, 10-35, A-3, A-9, A-13

tuning

determining if you have enough standby redo log groups, 5-34

logical standby databases, 9-24

U

unrecoverable operations, 10-37

backing up after, 10-39

UNSKIP procedure

of DBMS_LOGSTDBY, 9-3, 9-9

UNSKIP_ERROR procedure

of DBMS_LOGSTDBY, 9-3

UNSKIP_TRANSACTION procedure

of DBMS_LOGSTDBY, 9-3

upgrading

Oracle database software version, 9-18

user errors

saf eguarding against, 1-12

user sessions

causing switchover failures, A-8

USER_DUMP_DEST init ialization parameter, E-1

USING CURRENT LOGFILE clause

starting real time apply, 6-7

V

V$ARCHI VE_DEST view, 5-43, 10-35, 14-2 , A-3

displaying implicit default value of STANDBY_A RCHIVE_DEST parameter, 5-32

displaying information for all destinations , 14-2

V$ARCHIVE_DEST_STATUS view, 5-43, 6-8, 14-2

log apply s ervices and MANAGED REAL TIME column, 6-8

V$ARCHIVE_GAP view, 14-2

V$ARCHIVED_LOG view, 5-33, 5-43, 6-8, 10-43, 14-2, A-6

determining the most recently a rchived redo log file, 5-43

V$DATABASE view, 14-2

SUPPLEMENTAL_LOG_DATA_PK column, 4-9

SUPPLEMENTAL_LOG_DATA_UI column, 4-9

switchover and, 7-12, 7-13

SWITCHOVER_STATUS column and, 7-12, 7-13, A-6

V$DATABASE_INCARNATION view, 14-2

obtaining database incarnation information

standby databases

viewing database incarnation information, 8-36

V$DATAF ILE view, 10-37, 10-39, 14-2

V$DATAGUARD_CONFIG view, 14-2

V$DATAGUARD_STATUS view, 6-9, 14-2

V$LOG view, 5-43, 14-2

V$LOG_HISTORY view, 6-9 , 8-37, 14-3

V$LOGFILE view, 14-2

V$LOGSTDBY view, 9-12, 14-3

viewing SQL Apply, 9-11

V$L OGSTDBY_STATS view, 9-13, 14-3

V$MANAGED_STAN DBY view, 6-7, 14-3

V$RECOVER_FILE view, 8-32

V$SESSION view, A-6, A-8

V$STANDBY_LOG view, 14-3

V $THREAD view, 8-32

VALID_FOR attribute

defining role-based destinations, 7-10

examples, 5-22

format for keywords, 12-51

LOG_ARCHIVE_DEST_n initialization parameter, 12-50

overview , 5-21

values and role-based conditions, 12-51

verifying, 10-9

valida ting

redo data, 1-12

VERIFY at tribute

LOG_ARCHIVE_DEST_n initialization parameter, 12-5 3

verifying

contents of archived redo log files, 12-53

logical standby databases, 4-17

physical standby databases, 3-14

role-based destination settin gs, 10-9

standby redo log groups, 5-29< /a>

versions

upgrading Oracle database software, 9-18

views, 8-34, 1 4-1

DBA_LOGSTDBY_EVENTS, 9-10, 14-1, A-11

DBA_LOGSTDBY_LOG, 6-13< /a>, 10-20, 14-1

DBA_LOGSTDBY_NOT_UNIQUE, 4-6, 14-1

DBA_LOGSTDBY_PARAMETERS, 14-1

DBA_LOGSTDBY_PROGRESS, 6-14, 9-14, 14-1

DBA_LOGSTDBY_SKIP, 14-1

< dd class="L2IX">DBA_LOGSTDBY_SKIP_TRANSACTION, 14-1

DBA_LOGSTDBY_UNSUPPORTED, 4-3, 14-1

DBA_TABLESPACES, 8-32

GV$INSTANCE, B-9

V$ARCHIVE_DEST, < a href="log_transport.htm#1067182">5-43, 10-35, 14-2, A-3

V$ARCHIVE_DEST_STATUS, 5-43, 6-8, 14-2

V$ARCHIVE_GAP, 14-2

V$ARCHIVED_LOG, 5-33, 5-43 , 6-8, 10-43, 14-2

V$DATABASE, 14-2

V$DATABASE_INCARNATION, 14-2

V$DATAFILE, 10-37, 10-39, 14-2

V$DATAGUARD_CONFIG, 14-2

V$ DATAGUARD_STATUS, 6-9, 14-2

V$LOG, 5-43, 14-2

V$LOG_HISTORY, 6-9, 8-37, 14-3

V$LOGFILE, 14-2

V$LOGSTDBY, 9-12, 14- 3

V$LOGSTDBY_STATS, 9-13, 14-3

V$MANAGED_STANDBY, 6-7, 14-3

V$RE COVER_FILE, 8-32

V$SESSION, A-6, < a href="troubleshooting.htm#637141">A-8

V$STANDBY_LOG, 5-29, 14-3

V$THREAD, 8-32

W

wait events, 5-44

for standby destinati ons, 5-44

monitoring the performance of the log transport modes, 5-44

Z

zero data loss

See no data loss

zero downtime insta ntiation

logical standby databases, 4-7