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 1
    • a physical standby database 1
  • Active Data Guard
    • and physical standby databases 1 , 2
    • and the real-time query feature 1
  • adding
    • datafiles 1 , 2
    • indexes on logical standby databases 1
    • new or existing standby databases 1
    • online redo log files 1
    • tablespaces 1
  • adjusting
    • initialization parameter file
      • for logical standby database 1
  • AFFIRM attribute 1
  • ALTER DATABASE statement
    • ACTIVATE STANDBY DATABASE clause 1 , 2
    • ADD STANDBY LOGFILE clause 1
    • ADD STANDBY LOGFILE MEMBER clause 1 , 2
    • ADD SUPPLEMENTAL LOG DATA clause 1
    • COMMIT TO SWITCHOVER clause
      • troubleshooting 1
    • CREATE STANDBY CONTROLFILE clause
      • REUSE clause 1
    • DROP STANDBY LOGFILE MEMBER clause 1
    • GUARD clause 1
    • MOUNT STANDBY DATABASE clause 1
    • OPEN READ ONLY clause 1
    • PREPARE TO SWITCHOVER clause 1 , 3
    • RECOVER MANAGED STANDBY DATABASE clause
      • canceling 1
      • failover 1
    • REGISTER LOGFILE clause 1 , 2
    • RENAME FILE clause 1
    • SET STANDBY DATABASE clause
      • TO MAXIMIZE AVAILABILITY clause 1
      • TO MAXIMIZE PERFORMANCE clause 1
      • TO MAXIMIZE PROTECTION clause 1
    • START LOGICAL STANDBY APPLY clause
      • IMMEDIATE keyword 1
      • starting SQL Apply 1
    • STOP LOGICAL STANDBY APPLY clause 1 , 2
  • alternate archive destinations
    • setting up initialization parameters for 1
  • ALTERNATE attribute
    • LOG_ARCHIVE_DEST_n initialization parameter 1
  • ALTER SESSION DISABLE GUARD statement
    • overriding the database guard 1
  • ALTER SESSION statement
    • ENABLE GUARD clause 1
  • ALTER TABLESPACE statement 1 , 2
  • application continuity
    • support in Oracle Data Guard 1
  • applying
    • redo data immediately 1
    • redo data on standby database 1 , 2
    • SQL statements to logical standby databases 1
  • applying state 1
  • apply lag
    • monitoring in a real-time query environment 1
  • apply lag tolerance
    • configuring in a real-time query environment 1
  • apply services
    • defined 1 , 2
    • delaying application of redo data 1 , 2
    • real-time apply
      • defined 1
    • Redo Apply
      • defined 1 , 2
      • monitoring 1
      • starting 1
      • stopping 1
    • SQL Apply
      • defined 1 , 2
      • monitoring 1
      • starting 1
      • stopping 1
  • archive destinations
    • alternate 1
  • archived redo log files
    • accessing information about 1
    • applying
      • Redo Apply technology 1
      • SQL Apply technology 1
    • delaying application
      • on the standby database 1
    • deleting unneeded 1
    • destinations
      • disabling 1
      • enabling 1
    • managing gaps
      • See also gap management 1
    • redo data transmitted 1 , 2
    • registering
      • during failover 1
    • standby databases and 1 , 2 , 3
    • troubleshooting switchover problems 1 , 2
  • ARCHIVELOG mode
    • software requirements 1
  • archiver processes (ARCn)
    • influenced by MAX_CONNECTIONS attribute 1
  • archiving
    • real-time apply 1
    • specifying
      • failure resolution policies for 1
    • to failed destinations 1
  • ASM
    • See Automatic Storage Management (ASM) 1
  • ASYNC attribute 1
  • attributes
    • deprecated for the LOG_ARCHIVE_DEST_n initialization parameter 1
  • AUD$ table
    • replication on logical standbys 1
  • automatic block repair 1
  • automatic detection of missing log files 1 , 2
  • automatic failover 1
  • Automatic Storage Management (ASM)
    • creating a standby database that uses 1
  • automatic switchover
    • See also switchovers 1

B

  • BACKUP INCREMENTAL FROM SCN command
    • scenarios using 1 , 2
  • backup operations
    • after unrecoverable operations 1
    • configuring on a physical standby database 1
    • offloading on the standby database 1
    • primary databases 1
    • used by the broker 1
    • using RMAN 1
  • basic readable standby database See simulating a standby database environment 1
  • batch processing
    • on a logical standby database 1
  • benefits
    • Data Guard 1
    • logical standby database 1
    • of a rolling upgrade 1
    • physical standby database 1
  • block repair, automatic 1
  • broker
    • command-line interface 1
    • defined 1
    • graphical user interface 1

C

  • cascaded redo transport destinations 1
  • cascading redo
    • non-real-time 1
    • real-time 1
  • cascading redo data
    • configuration requirements 1
    • restrictions 1
  • CDBs
    • creating a logical standby of 1
    • creating a physical standby of 1
  • character sets
    • changing on primary databases 1
    • configurations with differing 1
  • checklist
    • tasks for creating physical standby databases 1
    • tasks for creating standby databases 1
  • checkpoints
    • V$LOGSTDBY_PROGRESS view 1
  • chunking
    • transactions 1
  • command-line interface
    • broker 1
  • COMMIT TO SWITCHOVER clause
    • of ALTER DATABASE
      • troubleshooting 1
  • COMPATIBLE initialization parameter
    • setting after upgrading Oracle Database software 1
    • setting for a rolling upgrade 1
  • complementary technologies 1
  • COMPRESSION attribute 1
  • configuration options
    • creating with Data Guard broker 1
    • overview 1
    • physical standby databases
      • location and directory structure 1
    • standby databases
      • delayed standby 1
  • configuring
    • backups on standby databases 1
    • disaster recovery 1
    • initialization parameters
      • for alternate archive destinations 1
    • listener for physical standby databases 1
    • no data loss 1
    • physical standby databases 1
    • reporting operations on a logical standby database 1
    • standby databases at remote locations 1
  • constraints
    • handled on a logical standby database 1
  • control files
    • copying 1
    • creating for standby databases 1
  • converting
    • a logical standby database to a physical standby database
      • aborting 1
    • a physical standby database to a logical standby database 1
  • CONVERT TO SNAPSHOT STANDBY clause on the ALTER DATABASE statement 1
  • COORDINATOR process
    • LSP background process 1
  • copying
    • control files 1
  • CREATE STANDBY CONTROLFILE clause
    • of ALTER DATABASE 1 , 2
  • CREATE TABLE AS SELECT (CTAS) statements
    • applied on a logical standby database 1
  • creating
    • indexes on logical standby databases 1

D

  • data availability
    • balancing against system performance requirements 1
  • database caching modes
    • force full database caching
      • status in Data Guard configurations 1
  • database guard
    • overriding 1
  • database incarnation
    • changes with OPEN RESETLOGS 1
  • database roles
    • primary 1
    • standby 1 , 2
    • transitions 1
  • databases
    • failover and 1
    • role transition and 1
    • surviving disasters and data corruptions 1
    • upgrading software versions 1
  • database schema
    • physical standby databases 1
  • datafiles
    • adding to primary database 1
    • monitoring 1
    • renaming on the primary database 1
  • Data Guard broker
    • defined 1
    • distributed management framework 1
    • failovers
      • fast-start 1
      • manual 1 , 2
    • fast-start failover 1
    • switchovers 1
  • Data Guard configurations
    • archiving to standby destinations using the log writer process 1
    • defined 1
    • protection modes 1
    • upgrading Oracle Database software 1
  • data loss
    • due to failover 1
    • switchover and 1
  • data protection
    • balancing against performance 1
    • benefits 1
    • flexibility 1
    • provided by Data Guard 1
  • data protection modes
    • enforced by redo transport services 1
    • overview 1
  • Data Pump utility
    • using transportable tablespaces with physical standby databases 1
  • DB_FILE_NAME_CONVERT initialization parameter
    • setting at standby site after a switchover 1
    • setting on physical standby database 1
    • when planning standby location and directory structure 1
  • DB_ROLE_CHANGE system event 1
  • DB_UNIQUE_NAME attribute 1
  • DB_UNIQUE_NAME initialization parameter
    • required with LOG_ARCHIVE_CONFIG parameter 1
    • setting database initialization parameters 1
  • DBA_LOGMNR_PURGED_LOG view
    • list archived redo log files that can be deleted 1
  • DBA_LOGSTDBY_EVENTS view 1 , 2 , 3
  • DBA_LOGSTDBY_HISTORY view 1
  • DBA_LOGSTDBY_LOG view 1 , 2
  • DBA_LOGSTDBY_NOT_UNIQUE view 1
  • DBA_LOGSTDBY_PARAMETERS view 1
  • DBA_LOGSTDBY_SKIP_TRANSACTION view 1
  • DBA_LOGSTDBY_SKIP view 1
  • DBA_LOGSTDBY_UNSUPPORTED view 1
  • DBA_TABLESPACES view 1
  • DBMS_LOGSTDBY.BUILD procedure
    • building a dictionary in the redo data 1
  • DBMS_LOGSTDBY package
    • INSTANTIATE_TABLE procedure 1
    • SKIP_ERROR procedure 1
    • SKIP_TRANSACTION procedure 1
    • SKIP procedure 1
  • DBMS_ROLLING package
    • used for rolling upgrades 1
  • DDL statements
    • supported by SQL Apply 1
  • DDL Statements
    • that use DBLINKS 1
  • DDL transactions
    • applied on a logical standby database 1
    • applying to a logical standby database 1
  • DELAY attribute
    • LOG_ARCHIVE_DEST_n initialization parameter 1
  • delaying
    • application of archived redo log files 1
    • application of redo log files 1
  • deleting
    • archived redo log files
      • indicated by the DBA_LOGMNR_PURGED_LOG view 1
      • not needed by SQL Apply 1
  • deprecated attributes
    • on the LOG_ARCHIVE_DEST_n initialization parameter 1
  • destinations
    • displaying with V$ARCHIVE_DEST view 1
    • role-based definitions 1
  • detecting
    • missing archived redo log files 1 , 2
  • DGMGRL command-line interface
    • invoking failovers 1 , 2
    • simplifying switchovers 1 , 2
  • dictionary
    • building a LogMiner 1
  • directory locations
    • Optimal Flexible Architecture (OFA) 1
    • structure on standby databases 1
  • direct path inserts
    • SQL Apply DML considerations 1
  • disabling
    • a destination for archived redo log files 1
  • disaster recovery
    • benefits 1
    • configuring 1
    • provided by Oracle Data Guard 1
    • provided by standby databases 1
  • disk I/O
    • controlling with the AFFIRM and NOAFFIRM attributes 1
  • distributed transactions 1
  • DML
    • batch updates on a logical standby database 1
  • DML operations
    • on temporary tables 1
  • DML transactions
    • applying to a logical standby database 1
  • downgrading
    • Oracle Database software 1
  • dropping
    • online redo log files 1
  • DROP STANDBY LOGFILE MEMBER clause
    • of ALTER DATABASE 1

E

  • ENABLE GUARD clause
    • of ALTER SESSION 1
  • enabling
    • database guard on logical standby databases 1
    • destinations for archived redo log files 1
    • real-time apply
      • on logical standby databases 1
  • extended datatype support
    • during replication 1

F

  • failovers
    • Data Guard broker 1 , 2
    • defined 1 , 2
    • displaying history with DBA_LOGSTDBY_HISTORY 1
    • fast-start failover 1
    • flashing back databases after 1
    • logical standby databases and 1
    • manual versus automatic 1
    • physical standby databases and 1
    • preparing for 1
    • simplifying with Data Guard broker 1
    • transferring redo data before 1
    • viewing characteristics for logical standby databases 1
    • with maximum performance mode 1
    • with maximum protection mode 1
  • failure resolution policies
    • specifying for redo transport services 1
  • far sync instances
    • creating 1
    • supported protection modes 1
  • fast-start failover
    • automatic failover 1 , 2
    • monitoring 1
  • FastSync mode 1
  • FGA_LOG$ table
    • replication on logical standbys 1
  • file specifications
    • renaming on the logical standby database 1
  • Flashback Database
    • after a role transition 1
    • after OPEN RESETLOGS 1
    • after role transitions 1
    • characteristics complementary to Data Guard 1
    • physical standby database 1
  • force full database caching mode
    • status in Data Guard configurations 1

G

  • gap management
    • automatic detection and resolution 1 , 2
    • detecting missing log files 1
    • registering archived redo log files
      • during failover 1
  • Global Data Services 1
  • global temporary tables
    • DML operations 1

H

  • high availability
    • benefits 1
    • provided by Oracle Data Guard 1
    • provided by Oracle RAC and Data Guard 1

I

  • idle state 1
  • incarnation of a database
    • changed 1
  • initialization parameters
    • DB_UNIQUE_NAME 1 , 2 , 3
    • LOG_ARCHIVE_MIN_SUCCEED_DEST 1
    • LOG_FILE_NAME_CONVERT 1
    • setting for both the primary and standby roles 1
  • INITIALIZING state 1
  • INSTANTIATE_TABLE procedure
    • of DBMS_LOGSTDBY 1

K

  • KEEP IDENTITY clause 1

L

  • latency
    • on logical standby databases 1 , 2
  • listener.ora file
    • redo transport services tuning and 1
    • troubleshooting 1 , 2
  • loading dictionary state 1
  • LOCATION attribute
    • setting
      • LOG_ARCHIVE_DEST_n initialization parameter 1
  • LOG_ARCHIVE_CONFIG initialization parameter
    • example 1
    • listing unique database names defined with 1
    • relationship to DB_UNIQUE_NAME parameter 1
  • LOG_ARCHIVE_DEST_n initialization parameter
    • AFFIRM attribute 1
    • ALTERNATE attribute 1 , 3
    • ASYNC attribute 1
    • COMPRESSION attribute 1
    • DB_UNIQUE_NAME attribute 1
    • DELAY attribute 1 , 2
    • deprecated attributes 1
    • LOCATION attribute 1 , 2
    • MANDATORY attribute 1
    • MAX_CONNECTIONS attribute 1
    • MAX_FAILURE attribute 1
    • NET_TIMEOUT attribute 1
    • NOAFFIRM attribute 1
    • NOALTERNATE attribute 1
    • NODELAY attribute 1
    • NOREGISTER attribute 1
    • REOPEN attribute 1
    • SERVICE attribute 1
    • SYNC attribute 1
    • VALID_FOR attribute 1
  • LOG_ARCHIVE_MAX_PROCESSES initialization parameter
    • relationship to MAX_CONNECTIONS 1
  • LOG_ARCHIVE_MIN_SUCCEED_DEST initialization parameter 1
  • LOG_FILE_NAME_CONVERT initialization parameter
    • setting at standby site after a switchover 1
    • setting on physical standby databases 1
    • when planning standby location and directory structure 1
  • log apply services
    • Redo Apply
      • monitoring 1
      • starting 1
      • stopping 1
    • tuning for Redo Apply 1
  • logical change records (LCR)
    • exhausted cache memory 1
    • staged 1
  • logical standby databases
    • adding
      • datafiles 1
      • indexes 1
      • tables 1
    • background processes 1
    • benefits 1
    • controlling user access to tables 1
    • creating
      • converting from a physical standby database 1
      • with Data Guard broker 1
    • database guard
      • overriding 1
    • data types
      • supported 1 , 2
      • unsupported 1
    • executing SQL statements on 1
    • failovers
      • displaying history of 1
      • handling failures 1
      • viewing characteristics with V$LOGSTDBY_STATS 1
    • logical standby process (LSP) and 1
    • materialized views
      • support for 1
    • monitoring 1 , 2
    • renaming the file specification 1
    • setting up a skip handler 1
    • SQL Apply
      • resynchronizing with primary database branch of redo 1
      • skipping DDL statements 1
      • skipping SQL statements 1
      • starting real-time apply 1
      • stopping 1
      • technology 1
      • transaction size considerations 1
    • starting
      • real-time apply 1
    • states
      • applying 1
      • idle 1
      • initializing 1
      • loading dictionary 1
    • support for primary databases with Transparent Data Encryption 1
    • switchovers 1
    • throughput and latency 1 , 2
    • upgrading
      • rolling upgrades 1
  • logical standby process (LSP)
    • COORDINATOR process 1
  • LogMiner dictionary
    • using DBMS_LOGSTDBY.BUILD procedure to build 1
    • when creating a logical standby database 1
  • log writer process (LGWR)
    • ASYNC network transmission 1
    • NET_TIMEOUT attribute 1
    • SYNC network transmission 1

M

  • managed recovery operations
    • See: Redo Apply
  • MANDATORY attribute 1
  • MAX_CONNECTIONS attribute
    • configuring Oracle RAC for parallel archival 1
    • reference 1
  • MAX_FAILURE attribute 1
  • maximum availability mode
    • introduction 1
  • maximum performance mode
    • introduction 1
  • maximum performance protection mode 1
  • maximum protection mode
    • for Oracle Real Application Clusters 1
    • introduction 1
    • standby databases and 1
  • memory
    • exhausted LCR cache 1
  • missing log sequence
    • detecting 1
    • See also gap management 1
  • modifying
    • a logical standby database 1
  • monitoring
    • primary database events 1
    • tablespace status 1
  • MOUNT STANDBY DATABASE clause
    • of ALTER DATABASE 1
  • multitenant container databases
    • See CDBs 1 , 2

N

  • NET_TIMEOUT attribute 1
  • network connections
    • configuring multiple 1
    • in an Oracle RAC environment 1
  • network I/O operations
    • network timers
      • NET_TIMEOUT attribute 1
    • tuning
      • redo transport services 1
  • network timeouts
    • acknowledging 1
  • NOAFFIRM attribute 1
  • NOALTERNATE attribute
    • LOG_ARCHIVE_DEST_n initialization parameter 1
  • no data loss
    • data protection modes overview 1
    • ensuring 1
    • guaranteeing 1
    • provided by maximum availability mode 1
    • provided by maximum protection mode 1
  • NODELAY attribute
    • LOG_ARCHIVE_DEST_n initialization parameter 1
  • NOREGISTER attribute 1

O

  • OMF
    • See Oracle Managed Files (OMF) 1
  • on-disk database structures
    • physical standby databases 1
  • online data files
    • moving the location 1
  • online redo log files
    • adding 1
    • dropping 1
  • OPEN READ ONLY clause
    • of ALTER DATABASE 1
  • OPEN RESETLOGS
    • flashing back after 1
  • OPEN RESETLOGS clause
    • database incarnation change 1
    • recovery 1
  • operational requirements 1 , 2
  • Optimal Flexible Architecture (OFA)
    • directory structure 1
  • ORA-01102 message
    • causing switchover failures 1 , 2
  • Oracle Database software
    • requirements for upgrading with SQL Apply 1
    • upgrading 1 , 2
    • upgrading with SQL Apply 1
  • Oracle Enterprise Manager
    • invoking failovers 1 , 2
    • invoking switchovers 1 , 2
  • Oracle Managed Files (OMF)
    • creating a standby database that uses 1
  • Oracle RAC One Node
    • supported by Oracle Data Guard 1
  • Oracle Real Application Clusters
    • characteristics complementary to Data Guard 1
    • configuring for multiple network connections 1
    • primary databases and 1 , 2
    • setting
      • maximum data protection 1
    • standby databases and 1 , 2
  • Oracle Recovery Manager utility (RMAN)
    • backing up files on a physical standby database 1
  • Oracle Sharding
    • supported by Oracle Active Data Guard 1
  • Oracle Standard Edition
    • simulating a standby database environment 1

P

  • pageout considerations 1
  • pageouts
    • SQL Apply 1
  • parallel DML (PDML) transactions
    • SQL Apply 1 , 2
  • patch set releases
    • upgrading 1
  • performance
    • balancing against data availability 1
    • balancing against data protection 1
  • physical standby databases
    • and Oracle Active Data Guard 1
    • applying redo data
      • Redo Apply technology 1
    • applying redo log files
      • starting 1
    • benefits 1
    • configuration options 1
    • converting datafile path names 1
    • converting log file path names 1
    • converting to a logical standby database 1
    • creating
      • checklist of tasks 1
      • configuring a listener 1
      • directory structure 1
      • with Data Guard broker 1
    • defined 1
    • failover
      • checking for updates 1
    • flashing back after failover 1
    • monitoring 1 , 2 , 3
    • opening for read-only or read/write access 1
    • read-only 1
    • recovering through OPEN RESETLOGS 1
    • Redo Apply 1
    • resynchronizing with primary database branch of redo 1
    • role transition and 1 , 2
    • rolling forward with BACKUP INCREMENTAL FROM SCN command 1 , 2
    • shutting down 1
    • starting
      • apply services 1
    • tuning the log apply rate 1
    • upgrading 1
    • using transportable tablespaces 1
  • PL/SQL supplied packages
    • supported 1
    • unsupported 1
  • PREPARER process
    • staging LCRs in SGA 1
  • PREPARE TO SWITCHOVER clause
    • of ALTER DATABASE 1 , 3
  • primary database
    • configuring
      • on Oracle Real Application Clusters 1
      • single-instance 1
    • datafiles
      • adding 1
    • defined 1
    • failover and 1
    • gap resolution 1
    • monitoring events on 1
    • network connections
      • avoiding network hangs 1
      • handling network timeouts 1
    • Oracle Real Application Clusters and
      • setting up 1
    • preparing for
      • physical standby database creation 1
    • prerequisite conditions for
      • logical standby database creation 1
    • redo transport services on 1
    • reducing workload on 1
    • switchover 1
    • tablespaces
      • adding 1
  • primary databases
    • ARCHIVELOG mode 1
    • software requirements 1
  • primary key columns
    • logged with supplemental logging 1 , 2
  • processes
    • SQL Apply architecture 1 , 2
  • protection modes
    • maximum availability mode 1
    • maximum performance 1
    • maximum performance mode 1
    • maximum protection mode 1
    • monitoring 1
    • setting on a primary database 1

Q

  • queries
    • offloading on the standby database 1

R

  • read-only operations
    • physical standby databases and 1
  • real-time apply
    • defined 1
    • starting
      • on logical standby 1
    • starting on logical standby databases 1
    • stopping
      • on logical standby 1
      • on physical standby databases 1
  • real-time cascading 1
  • real-time query feature
    • and Oracle Active Data Guard 1 , 2
    • configuring apply lag tolerance 1
    • forcing Redo Apply synchronization 1
    • monitoring apply lag 1
    • restrictions 1
    • using 1
  • recovering
    • from errors 1
    • logical standby databases 1
    • physical standby databases
      • after an OPEN RESETLOGS 1
    • through resetlogs 1 , 2
  • RECOVER MANAGED STANDBY DATABASE CANCEL clause
    • aborting 1
  • RECOVER MANAGED STANDBY DATABASE clause
    • of ALTER DATABASE 1 , 2 , 3 , 4
  • RECOVER TO LOGICAL STANDBY clause
    • converting a physical standby database to a logical standby database 1
  • Recovery Manager
    • characteristics complementary to Data Guard 1
    • standby database
      • creating 1
      • LOG_FILE_NAME_CONVERT initialization parameter 1
      • preparing using RMAN 1
  • re-creating
    • a table on a logical standby database 1
  • Redo Apply
    • defined 1 , 2
    • flashing back after failover 1
    • starting 1
    • stopping 1
    • technology 1
    • tuning the log apply rate 1
  • redo data
    • applying
      • through Redo Apply technology 1
      • through SQL Apply technology 1
      • to standby database 1
      • to standby databases 1
    • applying during conversion of a physical standby database to a logical standby database 1
    • archiving on the standby system 1 , 2
    • building a dictionary in 1
    • cascading 1
    • transmitting 1 , 2
  • redo gaps
    • manual resolution 1
    • reducing resolution time 1
  • redo log files
    • delaying application 1
  • redo logs
    • automatic application on physical standby databases 1
    • update standby database tables 1
  • redo transport services
    • archive destinations
      • alternate 1
      • re-archiving to failed destinations 1
    • authenticating sessions
      • using SSL 1
    • configuring 1
    • configuring security 1
    • defined 1
    • gap detection 1
    • handling archive failures 1
    • monitoring status 1
    • network
      • tuning 1
    • protection modes
      • maximum availability mode 1
      • maximum performance mode 1
      • maximum protection mode 1
    • receiving redo data 1
    • sending redo data 1
    • synchronous and asynchronous disk I/O 1
    • wait events 1
  • registering
    • archived redo log files
      • during failover 1
  • REGISTER LOGFILE clause
    • of ALTER DATABASE 1 , 2
  • REGISTER LOGICAL LOGFILE clause
    • of ALTER DATABASE 1
  • RELY constraint
    • creating 1
  • remote file server process (RFS)
    • log writer process and 1
  • RENAME FILE clause
    • of ALTER DATABASE 1
  • renaming
    • datafiles
      • on the primary database 1
      • setting the STANDBY_FILE_MANAGEMENT parameter 1
  • REOPEN attribute 1
  • reporting operations
    • configuring 1
    • offloading on the standby database 1
  • requirements
    • of a rolling upgrade 1
  • restart considerations
    • SQL Apply 1
  • resynchronizing
    • logical standby databases with a new branch of redo 1
    • physical standby databases with a new branch of redo 1
  • retrieving
    • missing archived redo log files 1 , 2
  • RMAN BACKUP INCREMENTAL FROM SCN command 1 , 2
  • RMAN backups
    • accessibility in Data Guard environment 1
    • association in Data Guard environment 1
    • interchangeability in Data Guard environment 1
  • role-based destinations
    • setting 1
  • role management services
    • defined 1
  • role transitions
    • choosing a type of 1
    • defined 1
    • flashing back the databases after 1
    • logical standby database and 1
    • monitoring 1
    • physical standby databases and 1 , 2
    • reversals 1 , 2
  • role transition triggers
    • DB_ROLE_CHANGE system event 1
  • rollback
    • after switchover failures 1
  • rolling upgrade
    • software requirements 1
  • rolling upgrades
    • benefits 1
    • DBMS_ROLLING package 1
    • patch set releases 1
    • requirements 1
    • setting the COMPATIBLE initialization parameter 1
    • use of KEEP IDENTITY clause 1
    • using Active Data Guard 1

S

  • schemas
    • identical to primary database 1
  • sequences
    • unsupported on logical standby databases 1
    • using in Oracle Active Data Guard 1
  • SERVICE attribute 1
  • SET STANDBY DATABASE clause
    • of ALTER DATA 1
    • of ALTER DATABASE 1 , 2
  • shutting down
    • physical standby database 1
  • simulating
    • standby database environment 1
  • SKIP_ERROR procedure
    • of the DBMS_LOGSTDBY package 1
  • SKIP_TRANSACTION procedure
    • of DBMS_LOGSTDBY 1
  • skip handler
    • setting up on a logical standby database 1
  • SKIP procedure
    • of DBMS_LOGSTDBY 1
  • snapshot standby databases
    • managing 1
  • software requirements
    • rolling upgrades 1
  • SQL Apply
    • after an OPEN RESETLOGS 1
    • applying CREATE TABLE AS SELECT (CTAS) statements 1
    • applying DDL transactions 1
    • applying DML transactions 1
    • architecture 1 , 2
    • defined 1 , 2
    • deleting archived redo log files 1
    • parallel DML (PDML) transactions 1 , 2
    • performing a rolling upgrade 1
    • requirements for rolling upgrades 1
    • restart considerations 1
    • rolling upgrades 1
    • starting
      • real-time apply 1
    • stopping
      • real-time apply 1
    • supported data types 1
    • support for DDL statements 1
    • support for PL/SQL supplied packages 1
    • transaction size considerations 1
    • unsupported data types 1
    • unsupported PL/SQL supplied packages 1
    • what to do if it stops 1
  • SQL statements
    • executing on logical standby databases 1 , 2
    • skipping on logical standby databases 1
  • STANDBY_FILE_MANAGEMENT initialization parameter
    • when renaming datafiles 1
  • standby database
    • creating logical 1
  • standby databases
    • about creating using RMAN 1
    • applying redo data on 1
    • applying redo log files on 1 , 2
    • apply services on 1
    • ARCn processes using multiple network connections 1
    • configuring
      • maximum number of 1
      • on Oracle Real Application Clusters 1 , 2
      • on remote locations 1
      • single-instance 1
    • creating
      • checklist of tasks 1
      • directory structure considerations 1
      • if primary uses ASM or OMF 1
      • on remote host with same directory structure 1
      • with a time lag 1
    • defined 1
    • failover
      • preparing for 1
    • failover to 1
    • LOG_FILE_NAME_CONVERT initialization parameter 1
    • operational requirements 1 , 2
    • preparing to use RMAN 1
    • recovering through OPEN RESETLOGS 1
    • resynchronizing with the primary database 1
    • software requirements 1
    • starting apply services on physical 1
  • standby redo log files
    • and real-time apply 1
  • standby redo logs
    • creating and managing 1
  • standby role 1
  • starting
    • logical standby databases 1
    • physical standby databases 1
    • real-time apply
      • on logical standby databases 1
    • Redo Apply 1
    • SQL Apply 1 , 2
  • START LOGICAL STANDBY APPLY clause
    • IMMEDIATE keyword 1
    • of ALTER DATABASE 1 , 2 , 3 , 4
  • STOP LOGICAL STANDBY APPLY clause
    • of ALTER DATABASE 1 , 2
  • stopping
    • real-time apply
      • on logical standby databases 1
    • real-time apply on physical standby databases 1
    • Redo Apply 1
    • SQL Apply 1
  • streams capture
    • running on a logical standby 1
  • supplemental logging
    • setting up to log primary key and unique-index columns 1 , 2
  • supported data types
    • for logical standby databases 1 , 2
  • supported PL/SQL supplied packages 1
  • SWITCHOVER_STATUS column
    • of V$DATABASE view 1
  • switchovers
    • choosing a target standby database 1
    • defined 1 , 2
    • displaying history with DBA_LOGSTDBY_HISTORY 1
    • fails with ORA-01102 1 , 2
    • flashing back databases after 1
    • logical standby databases and 1
    • manual versus automatic 1
    • monitoring 1
    • no data loss and 1
    • preparing for 1
    • seeing if the last archived redo log file was transmitted 1 , 2
    • setting DB_FILE_NAME_CONVERT after 1
    • setting LOG_FILE_NAME_CONVERT after 1
    • simplifying with Data Guard broker 1 , 2
    • starting over 1
    • typical use for 1
  • SYNC attribute 1
  • system events
    • role transitions 1
  • system global area (SGA)
    • logical change records staged in 1
  • system resources
    • efficient utilization of 1

T

  • tables
    • logical standby databases
      • adding on 1
      • re-creating tables on 1
      • unsupported on 1
  • tablespaces
    • adding
      • a new datafile 1
      • to primary database 1
    • monitoring status changes 1
    • moving between databases 1
  • target standby database
    • for switchover 1
  • terminal destinations
    • configuring 1
  • terminating
    • network connection 1
  • throughput
    • on logical standby databases 1 , 2
  • TIME_COMPUTED column 1
  • TIME_COMPUTED column of the V$DATAGUARD_STATS view 1
  • time lag
    • delaying application of archived redo log files 1 , 2
    • in standby database 1
  • tnsnames.ora file
    • redo transport services tuning and 1
    • troubleshooting 1 , 2 , 3
  • transaction size considerations
    • SQL Apply 1
  • Transparent Data Encryption
    • support by SQL Apply 1
  • transportable tablespaces
    • using with a physical standby database 1
  • triggers
    • handled on a logical standby database 1
    • role transitions 1
  • troubleshooting
    • if SQL Apply stops 1
    • last redo data was not transmitted 1 , 2
    • listener.ora file 1 , 2
    • logical standby database failures 1
    • SQL Apply 1
    • switchovers
      • ORA-01102 message 1 , 2
      • roll back and start over 1
    • tnsnames.ora file 1 , 2 , 3
  • tuning
    • log apply rate for Redo Apply 1

U

  • unique-index columns
    • logged with supplemental logging 1 , 2
  • unrecoverable operations
    • backing up after 1
  • unsupported PL/SQL supplied packages 1
  • upgrading
    • Oracle Database software
      • setting the COMPATIBLE initialization parameter 1

V

  • V$ARCHIVE_DEST_STATUS view 1
  • V$ARCHIVE_DEST view
    • displaying information for all destinations 1
  • V$ARCHIVE_GAP view 1
  • V$ARCHIVED_LOG view 1 , 2
  • V$DATABASE_INCARNATION view 1
  • V$DATABASE view
    • monitoring fast-start failover 1
    • SWITCHOVER_STATUS column and 1
  • V$DATAFILE view 1 , 2
  • V$DATAGUARD_CONFIG view
    • listing database names defined with LOG_ARCHIVE_CONFIG 1
  • V$DATAGUARD_STATS view 1 , 2
  • V$DATAGUARD_STATUS view 1
  • V$FS_FAILOVER_STATS view 1
  • V$LOG_HISTORY view 1 , 2
  • V$LOGFILE view 1
  • V$LOGSTDBY_PROCESS view 1 , 3 , 4 , 5 , 6
  • V$LOGSTDBY_PROGRESS view
    • RESTART_SCN column 1
  • V$LOGSTDBY_STATE view 1 , 2 , 3 , 4
  • V$LOGSTDBY_STATS view
    • failover characteristics 1
  • V$LOGSTDBY_TRANSACTION view 1
  • V$LOG view 1
  • V$MANAGED_STANDBY view 1 , 3
  • V$REDO_DEST_RESP_HISTOGRAM
    • using to monitor synchronous redo transport response time 1
  • V$REDO_DEST_RESP_HISTOGRAM view 1
  • V$STANDBY_EVENT_HISTOGRAM view 1
  • V$STANDBY_LOG view 1
  • VALID_FOR attribute 1
  • verifying
    • logical standby databases 1
    • physical standby databases 1
  • versions
    • upgrading Oracle Database software 1
  • views
    • DBA_LOGSTDBY_EVENTS 1 , 2 , 3
    • DBA_LOGSTDBY_HISTORY 1
    • DBA_LOGSTDBY_LOG 1 , 2
    • DBA_LOGSTDBY_NOT_UNIQUE 1
    • DBA_LOGSTDBY_PARAMETERS 1
    • DBA_LOGSTDBY_SKIP 1
    • DBA_LOGSTDBY_SKIP_TRANSACTION 1
    • DBA_LOGSTDBY_UNSUPPORTED 1
    • V$ARCHIVE_DEST 1 , 2
    • V$ARCHIVE_DEST_STATUS 1
    • V$ARCHIVED_GAP 1
    • V$ARCHIVED_LOG 1 , 2
    • V$DATABASE 1
    • V$DATABASE_INCARNATION 1
    • V$DATAFILE 1 , 2
    • V$DATAGUARD_CONFIG 1
    • V$DATAGUARD_STATS 1
    • V$DATAGUARD_STATUS 1
    • V$FS_FAILOVER_STATS 1
    • V$LOG 1
    • V$LOG_HISTORY 1 , 2
    • V$LOGFILE 1
    • V$LOGSTDBY_PROCESS 1 , 2
    • V$LOGSTDBY_PROGRESS 1 , 2
    • V$LOGSTDBY_STATE 1 , 2
    • V$LOGSTDBY_STATS 1 , 2
    • V$LOGSTDBY_TRANSACTION 1
    • V$MANAGED_STANDBY 1 , 3
    • V$REDO_DEST_RESP_HISTOGRAM 1
    • V$STANDBY_EVENT_HISTOGRAM 1
    • V$STANDBY_LOG 1

W

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