1. Index

Index

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

A

  • activating
    • a logical standby database 9.3.2
    • a physical standby database 12.8.3
  • Active Data Guard
    • and physical standby databases 2.1.1, 10.2
    • and the real-time query feature 10.2.1
  • adding
  • adjusting
    • initialization parameter file
      • for logical standby database 4.2.4.2
  • AFFIRM attribute 17.1
  • ALTER DATABASE statement
    • ACTIVATE STANDBY DATABASE clause 9.3.2, 12.8.3
    • ADD STANDBY LOGFILE clause 18.1
    • ADD STANDBY LOGFILE MEMBER clause 18.1, A.1.1
    • ADD SUPPLEMENTAL LOG DATA clause 18.1
    • COMMIT TO SWITCHOVER clause 9.3.1, 18.1
    • CREATE STANDBY CONTROLFILE clause 3.2.2
    • DROP STANDBY LOGFILE MEMBER clause 18.1
    • GUARD clause 11.2
    • MOUNT STANDBY DATABASE clause 18.1
    • OPEN READ ONLY clause 18.1
    • PREPARE TO SWITCHOVER clause 9.3.1, 18.1
    • RECOVER MANAGED STANDBY DATABASE clause 3.2.6, 4.2.5, 18.1
    • REGISTER LOGFILE clause A.4.1, G.3.1
    • RENAME FILE clause A.1.1
    • SET STANDBY DATABASE clause
      • TO MAXIMIZE AVAILABILITY clause 18.1
      • TO MAXIMIZE PERFORMANCE clause 9.1.4
      • TO MAXIMIZE PROTECTION clause 18.1
    • START LOGICAL STANDBY APPLY clause 8.4.1, 13.5, A.6
      • IMMEDIATE keyword 8.4.1
      • starting SQL Apply 4.2.5
    • STOP LOGICAL STANDBY APPLY clause 8.4.2, 9.3.2
  • alternate archive destinations
    • setting up initialization parameters for A.2
  • ALTERNATE attribute 17.2
    • LOG_ARCHIVE_DEST_n initialization parameter A.2
  • ALTER SESSION DISABLE GUARD statement
    • overriding the database guard 11.5.4
  • ALTER SESSION statement
    • ENABLE GUARD clause 18.2
  • ALTER TABLESPACE statement 10.3.4, A.10.1.1
  • application continuity
    • support in Oracle Data Guard 1.5.1
  • applying
    • redo data immediately 8.2.1
    • redo data on standby database 1.2.2, 8
    • SQL statements to logical standby databases 8.4
  • applying state 11.4.1
  • apply lag
    • monitoring in a real-time query environment 10.2.1.1
  • apply lag tolerance
    • configuring in a real-time query environment 10.2.1.2
  • apply services
  • archive destinations
    • alternate A.2
  • archived redo log files
  • ARCHIVELOG mode
    • software requirements 2.3.2
  • archiving
    • real-time apply 8.2.1
    • specifying
      • failure resolution policies for 17.14
    • to failed destinations 17.14
  • ASM
    • See Automatic Storage Management (ASM) 15.5
  • ASYNC attribute 17.15
  • attributes
    • deprecated for the LOG_ARCHIVE_DEST_n initialization parameter 17
  • AUD$ table
    • replication on logical standbys C.14.2
  • automatic block repair 10.2.1.5
  • automatic detection of missing log files 1.2.1, 1.8
  • automatic failover 1.2.3
  • Automatic Storage Management (ASM)
    • creating a standby database that uses 15.5
  • automatic switchover 1.2.3
    • See also switchovers 9.1

B

  • BACKUP INCREMENTAL FROM SCN command
  • backup operations
    • after unrecoverable operations 15.4.3
    • configuring on a physical standby database 1.1.5
    • offloading on the standby database 1.8
    • primary databases 1.1.2
    • used by the broker 1.3
    • using RMAN 12
  • basic readable standby database See simulating a standby database environment 2.3.2
  • batch processing
    • on a logical standby database 11.1.1.4
  • benefits
    • Data Guard 1.8
    • logical standby database 2.1.2
    • of a rolling upgrade 13.1
    • physical standby database 2.1.1
  • block repair, automatic 10.2.1.5
  • broker
    • command-line interface 1.8
    • defined 1.3
    • graphical user interface 1.8

C

  • cascaded redo transport destinations 7.3
  • cascading redo
    • non-real-time 7.3
    • real-time 7.3
  • cascading redo data 7.3
    • configuration requirements 7.3
    • restrictions 7.3
  • CDBs
    • creating a logical standby of 4.4
    • creating a physical standby of 3.5
  • character sets
    • changing on primary databases 15.9
    • configurations with differing C.18
  • checklist
    • tasks for creating physical standby databases 3.2
    • tasks for creating standby databases 4.2
  • checkpoints
  • chunking
  • command-line interface
  • COMMIT TO SWITCHOVER clause
  • COMPATIBLE initialization parameter
    • setting after upgrading Oracle Database software B.5
    • setting for a rolling upgrade 13.5
  • complementary technologies 1.6
  • COMPRESSION attribute 17.3
  • configuration options
    • creating with Data Guard broker 1.3
    • overview 1.1
    • physical standby databases
      • location and directory structure 2.4
    • standby databases
  • configuring
    • backups on standby databases 1.1.5
    • disaster recovery 1.1.5
    • initialization parameters
      • for alternate archive destinations A.2
    • listener for physical standby databases 5.1.1
    • no data loss 1.2.3
    • physical standby databases 2.4
    • reporting operations on a logical standby database 1.1.5
    • standby databases at remote locations 1.1.5
  • constraints
    • handled on a logical standby database 11.6.3
  • control files
    • copying 3.2.4
    • creating for standby databases 3.2.2
  • converting
    • a logical standby database to a physical standby database
    • a physical standby database to a logical standby database 4.2.4.1
  • CONVERT TO SNAPSHOT STANDBY clause on the ALTER DATABASE statement 18.1
  • COORDINATOR process
    • LSP background process 11.1
  • copying
  • CREATE STANDBY CONTROLFILE clause
  • CREATE TABLE AS SELECT (CTAS) statements
    • applied on a logical standby database 11.1.1.5
  • creating
    • indexes on logical standby databases 11.5.4.1

D

  • data availability
    • balancing against system performance requirements 1.8
  • database caching modes
    • force full database caching
      • status in Data Guard configurations 10.2.1.7
  • database guard 11.5.4
  • database incarnation
    • changes with OPEN RESETLOGS 10.4
  • database roles
  • databases
    • failover and 9.1.4
    • role transition and 9.1
    • surviving disasters and data corruptions 1
    • upgrading software versions 13.1
  • database schema
    • physical standby databases 1.1.2
  • datafiles
    • adding to primary database 10.3.1
    • monitoring 10.6
    • renaming on the primary database 10.3.4
  • Data Guard broker
    • defined 1.3
    • distributed management framework 9
    • failovers 1.3
      • fast-start 9
      • manual 1.3, 9
    • fast-start failover 1.3
    • switchovers 9
  • Data Guard configurations
    • archiving to standby destinations using the log writer process 8.2.1
    • defined 1.1
    • protection modes 1.4
    • upgrading Oracle Database software B
  • data loss
    • due to failover 1.2.3
    • switchover and 9.1
  • data protection
    • balancing against performance 1.8
    • flexibility 1.8
    • provided by Data Guard 1
  • data protection modes
    • enforced by redo transport services 1.2.1
    • overview 1.4
  • Data Pump utility
    • using transportable tablespaces with physical standby databases 10.3.3
  • DB_FILE_NAME_CONVERT initialization parameter
    • setting at standby site after a switchover A.4.3, G.3.3
    • setting on physical standby database 3.2.3
    • when planning standby location and directory structure 2.4
  • DB_ROLE_CHANGE system event 9.1.5
  • DB_UNIQUE_NAME attribute 17.4
  • DB_UNIQUE_NAME initialization parameter A.4.2, G.3.2
    • required with LOG_ARCHIVE_CONFIG parameter 16
    • setting database initialization parameters 3.1.4
  • DBA_LOGMNR_PURGED_LOG view
    • list archived redo log files that can be deleted 11.4.2
  • DBA_LOGSTDBY_EVENTS view 11.3.1, 19, A.6
  • DBA_LOGSTDBY_HISTORY view 19
  • DBA_LOGSTDBY_LOG view 11.3.2, 19
  • DBA_LOGSTDBY_NOT_UNIQUE view 19
  • DBA_LOGSTDBY_PARAMETERS view 19
  • DBA_LOGSTDBY_SKIP_TRANSACTION view 19
  • DBA_LOGSTDBY_SKIP view 19
  • DBA_LOGSTDBY_UNSUPPORTED view 19
  • DBA_TABLESPACES view 10.6
  • DBMS_LOGSTDBY.BUILD procedure
    • building a dictionary in the redo data 4.2.3.2
  • DBMS_LOGSTDBY package
    • INSTANTIATE_TABLE procedure 11.5.5
    • SKIP_ERROR procedure A.3
    • SKIP_TRANSACTION procedure A.6
    • SKIP procedure A.6
  • DBMS_ROLLING package
    • used for rolling upgrades 14
  • DDL statements
    • supported by SQL Apply C
  • DDL Statements
  • DDL transactions
    • applied on a logical standby database 11.1.1.5
    • applying to a logical standby database 11.1.1.5
  • DELAY attribute 17.5
    • LOG_ARCHIVE_DEST_n initialization parameter 8.2.2
  • delaying
    • application of archived redo log files 17.5
    • application of redo log files 8.2.2
  • deleting
    • archived redo log files
      • indicated by the DBA_LOGMNR_PURGED_LOG view 11.4.2
      • not needed by SQL Apply 11.4.2
  • deprecated attributes
    • on the LOG_ARCHIVE_DEST_n initialization parameter 17
  • destinations
    • displaying with V$ARCHIVE_DEST view 19
    • role-based definitions 17.17
  • detecting
    • missing archived redo log files 1.2.1, 1.8
  • DGMGRL command-line interface
    • invoking failovers 1.3, 9
    • simplifying switchovers 1.3, 9
  • dictionary
  • directory locations
    • Optimal Flexible Architecture (OFA) 2.4
    • structure on standby databases 2.4
  • direct path inserts
  • disabling
    • a destination for archived redo log files 7.2.2
  • disaster recovery
    • configuring 1.1.5
    • provided by Oracle Data Guard 1
    • provided by standby databases 1.1.5
  • disk I/O
    • controlling with the AFFIRM and NOAFFIRM attributes 17.1
  • distributed transactions C.15
  • DML
    • batch updates on a logical standby database 11.1.1.4
  • DML operations
  • DML transactions
    • applying to a logical standby database 11.1.1.4
  • downgrading
    • Oracle Database software B.7
  • dropping
    • online redo log files 10.3.5
  • DROP STANDBY LOGFILE MEMBER clause
    • of ALTER DATABASE 18.1

E

  • ENABLE GUARD clause
    • of ALTER SESSION 18.2
  • enabling
    • database guard on logical standby databases 18.2
    • destinations for archived redo log files 7.2.2
    • real-time apply
      • on logical standby databases 8.4.1

F

  • failovers 1.2.3
    • Data Guard broker 1.3, 9
    • defined 1.2.3
    • displaying history with DBA_LOGSTDBY_HISTORY 19
    • fast-start failover 9
    • flashing back databases after 9.4
    • logical standby databases and 9.3.2
    • manual versus automatic 1.2.3
    • physical standby databases and 18.1
    • preparing for 9.1.4
    • simplifying with Data Guard broker 9
    • transferring redo data before 9.1.4
    • viewing characteristics for logical standby databases 11.3.3
    • with maximum performance mode 9.1.4
    • with maximum protection mode 9.1.4
  • failure resolution policies
    • specifying for redo transport services 17.14
  • far sync instances 5
    • creating 5.1
    • supported protection modes 5.4
  • fast-start failover
    • automatic failover 1.3, 9
    • monitoring 10.6
  • FastSync mode 6.1
  • FGA_LOG$ table
    • replication on logical standbys C.14.2
  • file specifications
    • renaming on the logical standby database 11.5.3
  • Flashback Database
    • after a role transition 9.4
    • after OPEN RESETLOGS 15.3
    • after role transitions 9.4
    • characteristics complementary to Data Guard 1.6
    • physical standby database 15.2.1
  • force full database caching mode
    • status in Data Guard configurations 10.2.1.7

G

  • gap management
    • automatic detection and resolution 1.2.1, 1.8
    • detecting missing log files 1.8
    • registering archived redo log files
  • Global Data Services 1.6
  • global temporary tables

H

  • high availability
    • Oracle Real Application Clusters
      • characteristics complementary to Data Guard 1.6
    • provided by Oracle Data Guard 1
    • provided by Oracle RAC and Data Guard 1.6

I

  • idle state 11.4.1
  • incarnation of a database
  • initialization parameters
  • INITIALIZING state 11.4.1
  • INSTANTIATE_TABLE procedure

K

L

  • latency
  • listener.ora file
    • redo transport services tuning and A.7
    • troubleshooting A.1.2, A.7
  • loading dictionary state 11.4.1
  • LOCATION attribute 17.8
    • setting
      • LOG_ARCHIVE_DEST_n initialization parameter A.2
  • LOG_ARCHIVE_CONFIG initialization parameter 3.1.4, 3.2.3
    • example 17.4
    • listing unique database names defined with 19
    • relationship to DB_UNIQUE_NAME parameter 16
  • LOG_ARCHIVE_DEST_n initialization parameter
    • AFFIRM attribute 17.1
    • ALTERNATE attribute 17.2, A.2
    • ASYNC attribute 17.15
    • COMPRESSION attribute 17.3
    • DB_UNIQUE_NAME attribute 17.4
    • DELAY attribute 8.2.2, 17.5
    • deprecated attributes 17
    • LOCATION attribute 17.8, A.2
    • MANDATORY attribute 17.9
    • MAX_FAILURE attribute 17.10
    • NET_TIMEOUT attribute 17.11
    • NOAFFIRM attribute 17.1
    • NOALTERNATE attribute A.2
    • NODELAY attribute 8.2.2
    • NOREGISTER attribute 17.12
    • REOPEN attribute 17.14
    • SERVICE attribute 17.8
    • SYNC attribute 17.15
    • VALID_FOR attribute 17.17
  • LOG_ARCHIVE_MIN_SUCCEED_DEST initialization parameter 17.9
  • LOG_FILE_NAME_CONVERT initialization parameter
    • setting at standby site after a switchover A.4.3, G.3.3
    • setting on physical standby databases 3.2.3
    • when planning standby location and directory structure 2.4
  • log apply services
  • logical change records (LCR)
  • logical standby databases 1.1.2
    • adding
    • background processes 11.1
    • benefits 2.1.2
    • controlling user access to tables 11.2
    • creating 4
      • converting from a physical standby database 4.2.4.1
      • with Data Guard broker 1.3
    • database guard
    • data types
    • executing SQL statements on 1.1.2
    • failovers 9.3.2
      • displaying history of 19
      • handling failures A.3
      • viewing characteristics with V$LOGSTDBY_STATS 11.3.3
    • logical standby process (LSP) and 11.1
    • materialized views
    • monitoring 8.4.3, 19
    • renaming the file specification 11.5.3
    • setting up a skip handler 11.5.3
    • SQL Apply 1.2.2
      • resynchronizing with primary database branch of redo 11.6.5
      • skipping DDL statements C.13
      • skipping SQL statements C.13
      • starting real-time apply 8.4.1
      • stopping 8.4.2
      • technology 8.1
      • transaction size considerations 11.1.1.1
    • starting
    • states
    • support for primary databases with Transparent Data Encryption C.3
    • switchovers 9.3.1
    • throughput and latency 11.1.1.4, 11.1.1.5
    • upgrading B.4
  • logical standby process (LSP)
    • COORDINATOR process 11.1
  • LogMiner dictionary
    • using DBMS_LOGSTDBY.BUILD procedure to build 4.2.3.2
    • when creating a logical standby database 4.2.4.1
  • log writer process (LGWR)
    • ASYNC network transmission 17.15
    • NET_TIMEOUT attribute 17.11
    • SYNC network transmission 17.15

M

  • managed recovery operations
    • See: Redo Apply
  • MANDATORY attribute 17.9
  • MAX_FAILURE attribute 17.10
  • maximum availability mode
    • introduction 1.4
  • maximum performance mode 9.1.4
    • introduction 1.4
  • maximum performance protection mode 6.1
  • maximum protection mode
    • for Oracle Real Application Clusters D.2.2
    • introduction 1.4
    • standby databases and 9.1.4
  • memory
  • missing log sequence
    • detecting 1.8
    • See also gap management 1.8
  • modifying
    • a logical standby database 11.5.4
  • monitoring
    • primary database events 10.6
    • tablespace status 10.6
  • MOUNT STANDBY DATABASE clause
    • of ALTER DATABASE 18.1
  • multitenant container databases

N

  • NET_TIMEOUT attribute 17.11
  • network I/O operations
    • network timers
      • NET_TIMEOUT attribute 17.11
    • tuning
      • redo transport services A.7
  • network timeouts
  • NOAFFIRM attribute 17.1
  • NOALTERNATE attribute
    • LOG_ARCHIVE_DEST_n initialization parameter A.2
  • no data loss
    • data protection modes overview 1.4
    • ensuring 1.2.3
    • guaranteeing 1.2.3
    • provided by maximum availability mode 1.4
    • provided by maximum protection mode 1.4
  • NODELAY attribute
    • LOG_ARCHIVE_DEST_n initialization parameter 8.2.2
  • NOREGISTER attribute 17.12

O

  • OMF
    • See Oracle Managed Files (OMF) 15.5
  • on-disk database structures
    • physical standby databases 1.1.2
  • online data files
    • moving the location 2.5
  • online redo log files
  • OPEN READ ONLY clause
    • of ALTER DATABASE 18.1
  • OPEN RESETLOGS
    • flashing back after 15.3
  • OPEN RESETLOGS clause
    • database incarnation change 10.4
    • recovery 10.4
  • operational requirements 2.3, 2.3.2
  • Optimal Flexible Architecture (OFA)
    • directory structure 2.4
  • ORA-01102 message
  • Oracle Database software
    • requirements for upgrading with SQL Apply 13.2
    • upgrading 2.3.2, B.1
    • upgrading with SQL Apply 13.1
  • Oracle Enterprise Manager
    • invoking failovers 1.3, 9
    • invoking switchovers 1.3, 9
  • Oracle Managed Files (OMF)
    • creating a standby database that uses 15.5
  • Oracle RAC One Node
    • supported by Oracle Data Guard 1.6
  • Oracle Real Application Clusters
  • Oracle Recovery Manager utility (RMAN)
    • backing up files on a physical standby database 12
  • Oracle Sharding
    • supported by Oracle Active Data Guard 1.7
  • Oracle Standard Edition
    • simulating a standby database environment 2.3.2

P

  • pageout considerations 11.1.1.2
  • pageouts
  • parallel DML (PDML) transactions
  • patch set releases
  • performance
    • balancing against data availability 1.8
    • balancing against data protection 1.8
  • physical standby databases
    • and Oracle Active Data Guard 2.1.1
    • applying redo data 8.1, 8.3
      • Redo Apply technology 8.3
    • applying redo log files
    • benefits 2.1.1
    • configuration options 2.4
    • converting datafile path names 3.2.3
    • converting log file path names 3.2.3
    • converting to a logical standby database 4.2.4.1
    • creating
      • checklist of tasks 3.2
      • configuring a listener 5.1.1
      • directory structure 2.4
      • with Data Guard broker 1.3
    • defined 1.1.2
    • failover
      • checking for updates 9.1.4
    • flashing back after failover 15.2.1
    • monitoring 8.3.3, 10.6.1, 19
    • opening for read-only or read/write access 10.2
    • read-only 10.2
    • recovering through OPEN RESETLOGS 10.4
    • Redo Apply 1.2.2
    • resynchronizing with primary database branch of redo 10.4
    • role transition and 9.2, G
    • rolling forward with BACKUP INCREMENTAL FROM SCN command 12.8.1, 12.10
    • shutting down 10.1.2
    • starting
    • tuning the log apply rate 10.8
    • upgrading B.3
    • using transportable tablespaces 10.3.3
  • PL/SQL supplied packages
  • PREPARER process
    • staging LCRs in SGA 11.1
  • PREPARE TO SWITCHOVER clause
  • primary database
    • configuring
      • on Oracle Real Application Clusters 1.1.1
      • single-instance 1.1.1
    • datafiles
    • defined 1.1.1
    • gap resolution 1.8
    • monitoring events on 10.6
    • network connections
      • avoiding network hangs 17.11
      • handling network timeouts 17.11
    • Oracle Real Application Clusters and
    • preparing for
      • physical standby database creation 3.1
    • prerequisite conditions for
      • logical standby database creation 4.1
    • redo transport services on 1.2.1
    • reducing workload on 1.8
    • restore points
      • replicating to standby 10.7
    • switchover 9.1.3
    • tablespaces
  • primary databases
    • ARCHIVELOG mode 2.3.2
    • software requirements 2.3.2
  • primary key columns
  • private temporary tables
  • processes
  • protection modes
    • maximum availability mode 1.4
    • maximum performance 6.1
    • maximum performance mode 1.4
    • maximum protection mode 1.4
    • monitoring 10.6
    • setting on a primary database 6.2

Q

  • queries
    • offloading on the standby database 1.8

R

  • read-only operations 1.2.2
    • physical standby databases and 10.2
  • real-time apply
    • defined 8.2.1
    • starting
      • on logical standby 8.4.1
    • starting on logical standby databases 8.4.1
    • stopping
      • on logical standby 8.4.2
      • on physical standby databases 10.1.2
  • real-time cascading 7.3
  • real-time query feature 10.2
  • recovering
    • from errors A.10.1
    • logical standby databases 11.6.5
    • physical standby databases
      • after an OPEN RESETLOGS 10.4
    • through resetlogs 10.4, 11.6.5
  • RECOVER MANAGED STANDBY DATABASE CANCEL clause
  • RECOVER MANAGED STANDBY DATABASE clause
  • RECOVER TO LOGICAL STANDBY clause
    • converting a physical standby database to a logical standby database 4.2.4.1
  • Recovery Manager
    • characteristics complementary to Data Guard 1.6
    • standby database
      • creating E.2.1
      • LOG_FILE_NAME_CONVERT initialization parameter E.2.2.3.1
      • preparing using RMAN E.2.2
  • re-creating
    • a table on a logical standby database 11.5.5
  • redirecting DML operations
  • redirecting PL/SQL
  • Redo Apply
  • redo data
    • applying
      • through Redo Apply technology 1.2.2
      • through SQL Apply technology 1.2.2
      • to standby database 8.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, 8.1
    • building a dictionary in 4.2.3.2
    • cascading 7.3
    • transmitting 1.1.2, 1.2.1
  • redo gaps 7.6.3
  • redo log files
    • delaying application 8.2.2
  • redo logs
    • automatic application on physical standby databases 8.3.1
    • update standby database tables 1.8
  • redo transport services 7
    • archive destinations
      • alternate A.2
      • re-archiving to failed destinations 17.14
    • authenticating sessions
    • configuring 7.2
    • configuring security 7.2.1
    • defined 1.2.1
    • gap detection 7.6.3
    • handling archive failures 17.14
    • monitoring status 7.6.1
    • network
    • protection modes
      • maximum availability mode 1.4
      • maximum performance mode 1.4
      • maximum protection mode 1.4
    • receiving redo data 7.2.3
    • sending redo data 7.2.2
    • synchronous and asynchronous disk I/O 17.1
    • wait events 7.6.4
  • registering
    • archived redo log files
  • REGISTER LOGFILE clause
  • REGISTER LOGICAL LOGFILE clause
    • of ALTER DATABASE 9.3.2
  • RELY constraint
  • remote file server process (RFS)
    • log writer process and 8.2.1
  • RENAME FILE clause
    • of ALTER DATABASE A.1.1
  • renaming
    • datafiles
      • on the primary database 10.3.4
      • setting the STANDBY_FILE_MANAGEMENT parameter 10.3.4
  • REOPEN attribute 17.14
  • reporting operations
    • configuring 1.1.5
    • offloading on the standby database 1.8
  • requirements
    • of a rolling upgrade 13.2
  • restart considerations
  • restore points
    • replicating to standby 10.7
  • resynchronizing
    • logical standby databases with a new branch of redo 11.6.5
    • physical standby databases with a new branch of redo 10.4
  • retrieving
    • missing archived redo log files 1.2.1, 1.8
  • RMAN BACKUP INCREMENTAL FROM SCN command 12.8.1, 12.10
  • RMAN backups
    • accessibility in Data Guard environment 12.1.3
    • association in Data Guard environment 12.1.2
    • interchangeability in Data Guard environment 12.1.1
  • role-based destinations
  • role management services
    • defined 9
  • role transitions 1.2.3, 9.1
    • choosing a type of 9.1.1
    • defined 1.2.3
    • flashing back the databases after 9.4
    • logical standby database and 9.3
    • monitoring 10.6
    • physical standby databases and 9.2, G
    • reversals 1.2.3, 9.1
  • role transition triggers 9.1.5
    • DB_ROLE_CHANGE system event 9.1.5
  • rollback
  • rolling upgrade
    • software requirements 2.3.2
  • rolling upgrades
    • benefits 13.1
    • DBMS_ROLLING package 14
    • patch set releases 2.3.2
    • requirements 13.2
    • setting the COMPATIBLE initialization parameter 13.5
    • use of KEEP IDENTITY clause 4.2.4.1
    • using Active Data Guard 14

S

  • schemas
    • identical to primary database 1.1.2
  • sequences
    • unsupported on logical standby databases C.12
    • using in Oracle Active Data Guard 10.2.6
  • SERVICE attribute 17.8
  • SET STANDBY DATABASE clause
  • shutting down
    • physical standby database 10.1.2
  • simulating
    • standby database environment 2.3.2
  • SKIP_ERROR procedure
    • of the DBMS_LOGSTDBY package A.3
  • SKIP_TRANSACTION procedure
    • of DBMS_LOGSTDBY A.6
  • skip handler
    • setting up on a logical standby database 11.5.3
  • SKIP procedure
    • of DBMS_LOGSTDBY A.6
  • snapshot standby databases 1.1.2
  • software requirements 2.3.2
  • SQL Apply 8.4.2, 11.1.1.2
    • after an OPEN RESETLOGS 11.6.5
    • applying CREATE TABLE AS SELECT (CTAS) statements 11.1.1.5
    • applying DDL transactions 11.1.1.5
    • applying DML transactions 11.1.1.4
    • architecture 11.1, 11.4.1
    • defined 1.2.2, 8.1
    • deleting archived redo log files 11.4.2
    • parallel DML (PDML) transactions 11.1.1.3, 11.1.1.4
    • performing a rolling upgrade 13.1
    • requirements for rolling upgrades 13.2
    • restart considerations 11.1.1.3
    • rolling upgrades 2.3.2
    • starting
    • stopping
    • supported data types C.1.1
    • support for DDL statements C
    • support for PL/SQL supplied packages C.11.1
    • transaction size considerations 11.1.1.1
    • unsupported data types C.1.2
    • unsupported PL/SQL supplied packages C.11.2
    • what to do if it stops A.6
  • SQL statements
    • executing on logical standby databases 1.1.2, 1.2.2
    • skipping on logical standby databases C.13
  • STANDBY_FILE_MANAGEMENT initialization parameter
    • when renaming datafiles 10.3.4
  • standby database
    • creating logical 4
  • standby databases
    • about creating using RMAN E.2.1
    • applying redo data on 8
    • applying redo log files on 1.2.2, 1.8
    • apply services on 8.1
    • configuring 1.1
      • maximum number of 2
      • on Oracle Real Application Clusters 1.1.2, D.1
      • on remote locations 1.1.5
      • single-instance 1.1.2
    • creating 1.1.2
      • checklist of tasks 4.2
      • directory structure considerations 2.4
      • if primary uses ASM or OMF 15.5
      • on remote host with same directory structure E.3
      • with a time lag 8.2.2
    • defined 2.1
    • failover
    • failover to 9.1.4
    • LOG_FILE_NAME_CONVERT initialization parameter E.2.2.3.1
    • operational requirements 2.3, 2.3.2
    • preparing to use RMAN E.2.2
    • recovering through OPEN RESETLOGS 10.4
    • redirecting DML operations 10.2.2.1
    • redirecting PL/SQL 10.2.2.2
    • resynchronizing with the primary database 1.8
    • software requirements 2.3.2
    • starting apply services on physical 8.3.1
  • standby redo log files
    • and real-time apply 8.2.1
  • standby redo logs
  • standby role 1.1.2
  • starting
  • START LOGICAL STANDBY APPLY clause
  • STOP LOGICAL STANDBY APPLY clause
  • stopping
    • real-time apply
      • on logical standby databases 8.4.2
    • real-time apply on physical standby databases 8.3.2
    • Redo Apply 8.3.2
    • SQL Apply 8.4.2
  • streams capture
    • running on a logical standby 11.6.6
  • supplemental logging
  • supported data types
    • for logical standby databases C, C.14
  • supported PL/SQL supplied packages C.11.1
  • SWITCHOVER_STATUS column
  • switchovers 1.2.3
    • choosing a target standby database 9.1.2
    • defined 1.2.3
    • displaying history with DBA_LOGSTDBY_HISTORY 19
    • fails with ORA-01102 A.4.2, G.3.2
    • flashing back databases after 9.4
    • logical standby databases and 9.3.1
    • manual versus automatic 1.2.3
    • monitoring 10.6
    • no data loss and 9.1
    • preparing for 9.1.3
    • seeing if the last archived redo log file was transmitted A.4.1, G.3.1
    • setting DB_FILE_NAME_CONVERT after A.4.3, G.3.3
    • setting LOG_FILE_NAME_CONVERT after A.4.3, G.3.3
    • simplifying with Data Guard broker 1.3, 9
    • starting over A.4.4, G.3.4
    • typical use for 9.1.3
  • SYNC attribute 17.15
  • system events
  • system global area (SGA)
    • logical change records staged in 11.1
  • system resources
    • efficient utilization of 1.8

T

  • tables
    • logical standby databases
  • tablespaces
    • adding
    • monitoring status changes 10.6
    • moving between databases 10.3.3
  • target standby database
  • terminal destinations 7.3
  • terminating
    • network connection 17.11
  • throughput
  • TIME_COMPUTED column 9.1.2
  • TIME_COMPUTED column of the V$DATAGUARD_STATS view 9.1.2
  • time lag
    • delaying application of archived redo log files 8.2.2, 17.5
    • in standby database 8.2.2
  • tnsnames.ora file
  • transaction size considerations
  • Transparent Data Encryption
    • support by SQL Apply C.3
  • transportable tablespaces
    • using with a physical standby database 10.3.3
  • triggers
    • handled on a logical standby database 11.6.3
    • role transitions 9.1.5
  • troubleshooting
  • tuning
    • log apply rate for Redo Apply 10.8

U

  • unique-index columns
  • unrecoverable operations
  • unsupported PL/SQL supplied packages C.11.2
  • upgrading
    • Oracle Database software 2.3.2, 13.1, B, B.1
      • setting the COMPATIBLE initialization parameter B.5

V

  • V$ARCHIVE_DEST_STATUS view 19
  • V$ARCHIVE_DEST view 19, A.1.2
    • displaying information for all destinations 19
  • V$ARCHIVE_GAP view 19
  • V$ARCHIVED_LOG view 10.6.1.4, 19
  • V$DATABASE_INCARNATION view 19
  • V$DATABASE view 19
    • monitoring fast-start failover 10.6
    • SWITCHOVER_STATUS column and A.4.1, G.3.1
  • V$DATAFILE view 15.4.3, 19
  • V$DATAGUARD_CONFIG view 19
    • listing database names defined with LOG_ARCHIVE_CONFIG 19
  • V$DATAGUARD_STATS view 9.1.2, 19
  • V$DATAGUARD_STATUS view 10.6.1.6
  • V$FS_FAILOVER_STATS view 19
  • V$LOG_HISTORY view 10.6.1.5, 19
  • V$LOGFILE view 19
  • V$LOGSTDBY_PROCESS view 11.3.4, 11.4.1, 11.7.3.1, 11.7.3.2, 19
  • V$LOGSTDBY_PROGRESS view 11.3.5, 19
  • V$LOGSTDBY_STATE view 9.1.2, 11.3.6, 11.4.1, 19
  • V$LOGSTDBY_STATS view 11.3.7, 19
    • failover characteristics 11.3.3
  • V$LOGSTDBY_TRANSACTION view 19
  • V$LOG view 19
  • V$MANAGED_STANDBY view 10.6.1.3, 19
  • V$REDO_DEST_RESP_HISTOGRAM
    • using to monitor synchronous redo transport response time 7.6.2
  • V$REDO_DEST_RESP_HISTOGRAM view 19
  • V$STANDBY_EVENT_HISTOGRAM view 19
  • V$STANDBY_LOG view 19
  • VALID_FOR attribute 17.17
  • verifying
    • logical standby databases 4.2.6
    • physical standby databases 3.2.7
  • versions
    • upgrading Oracle Database software 13.1
  • views
    • DBA_LOGSTDBY_EVENTS 11.3.1, 19, A.6
    • DBA_LOGSTDBY_HISTORY 19
    • DBA_LOGSTDBY_LOG 11.3.2, 19
    • DBA_LOGSTDBY_NOT_UNIQUE 19
    • DBA_LOGSTDBY_PARAMETERS 19
    • DBA_LOGSTDBY_SKIP 19
    • DBA_LOGSTDBY_SKIP_TRANSACTION 19
    • DBA_LOGSTDBY_UNSUPPORTED 19
    • V$ARCHIVE_DEST 19, A.1.2
    • V$ARCHIVE_DEST_STATUS 19
    • V$ARCHIVED_GAP 19
    • V$ARCHIVED_LOG 10.6.1.4, 19
    • V$DATABASE 19
    • V$DATABASE_INCARNATION 19
    • V$DATAFILE 15.4.3, 19
    • V$DATAGUARD_CONFIG 19
    • V$DATAGUARD_STATS 19
    • V$DATAGUARD_STATUS 10.6.1.6
    • V$FS_FAILOVER_STATS 19
    • V$LOG 19
    • V$LOG_HISTORY 10.6.1.5, 19
    • V$LOGFILE 19
    • V$LOGSTDBY_PROCESS 11.3.4, 19
    • V$LOGSTDBY_PROGRESS 11.3.5, 19
    • V$LOGSTDBY_STATE 11.3.6, 19
    • V$LOGSTDBY_STATS 11.3.7, 19
    • V$LOGSTDBY_TRANSACTION 19
    • V$MANAGED_STANDBY 10.6.1.3, 19
    • V$REDO_DEST_RESP_HISTOGRAM 19
    • V$STANDBY_EVENT_HISTOGRAM 19
    • V$STANDBY_LOG 19

W

  • wait events
    • for redo transport services 7.6.4
  • WAITING FOR DICTIONARY LOGS state 11.4.1