Index
A
- active-active GoldenGate configuration
- active-active replication / GoldenGate and Streams
- Active Data Guard
- about / Oracle Active Data Guard, Why Active Data Guard?
- benefits / Oracle Active Data Guard
- features / Why Active Data Guard?, Active Data Guard features
- licensing / Oracle Data Guard license
- enabling / Enabling Active Data Guard
- enabling, if Redo Apply is running / Time for action – enabling Active Data Guard if Redo Apply is running using SQL *PLUS
- enabling, if standby database is shutdown / Time for action – enabling Active Data Guard if the standby database is shut down
- enabling, broker used / Time for action – enabling Active Data Guard using broker
- monitoring / Monitoring Active Data Guard
- monitoring, from primary database / From primary
- monitoring, from standby database / From standby
- working, with PeopleSoft / Active Data Guard with PeopleSoft, Time for action – Active Data Guard with PeopleSoft
- working, with EBS / Active Data Guard with EBS
- working, with TopLink / Active Data Guard with TopLink
- working, with Oracle BI / Active Data Guard with Oracle BI
- working, with SAP / Active Data Guard with SAP
- Active Data Guard features
- ADRCI utility
- advanced compression, Data Guard
- AFFIRM attribute
- alert log files
- ALL Database Guard mode
- applications, working with Active Data Guard
- architecture, Data Guard
- archived log deletion policy
- archive log mode, primary database
- ARCH transportation mode
- ASYNC attribute
- Asynchronous redo transport (ASYNC) method
- automatic block media repair, corruption / Automatic block media repair
- automatic deletion process, logical standby database
B
- best practices, Data Guard
- best practices, RMAN
- block change tracking
- block change tracking (BCT) feature / RMAN integration
- block corruption
C
- cascade standby databases
- centralized and simple management
- client-side components, Data Guard broker
- client-side TAF
- Cloud Control integration
- components, Data Guard broker
- COMPRESSION attribute
- conflict / GoldenGate and Streams
- connection failover
- corruption
- corruption detection
- corruption prevention
- CPU/SPU patches
- Critical Patch Update (CPU)
- cross-platform Data Guard
D
- database objects, logical standby database
- database properties, Data Guard broker
- database versions, Data Gaurd
- database wait events
- Data Guard
- Data Guard administration home page
- Data Guard background processes
- Data Guard broker
- Data Guard broker configuration
- Data Guard broker issues
- Data Guard broker logs
- Data Guard configuration
- Data Guard failover
- Data Guard Monitor (DMON) logfiles / Gathering diagnostic data
- Data Guard Monitor Process (DMON) / Introduction to Data Guard broker
- Data Guard performance
- Data Guard services
- Data Guard settings, logical standby database
- Data Guard switchover
- about / Switchover
- performing / Switchover
- performing, with physical standby database using SQL*Plus / Performing switchover with a physical standby database using SQL*Plus, Time for action – switchover with a physical standby using SQL*Plus
- primary and standby databases, verifying / Time for action – preliminary tests before performing switchover
- performing, with physical standby database using broker / Performing switchover with a physical standby database using broker, Time for action – switchover with a physical standby using broker
- performing, with physical standby database using EM Cloud Control / Performing switchover with a physical standby database using EM Cloud Control, Time for action – switchover with a physical standby using EM Cloud Control
- performing, logical standby database using SQL*Plus / Performing switchover with a logical standby database using SQL*Plus, Time for action – switchover with a logical standby database using SQL*Plus
- performing, logical standby database using broker / Performing switchover with a logical standby database using broker, Time for action – switchover with a logical standby using broker
- Data Guard tracing
- Data Guard tracing levels
- Data Guard tuning
- Data Guard wait events
- data loss consideration, physical standby database
- data protection
- data protection modes, Data Guard
- DB_BLOCK_CHECKING parameter
- DB_BLOCK_CHECKSUM parameter
- DB_FILE_NAME_CONVERT parameter
- DB_LOST_WRITE_PROTECT parameter
- DB_NAME parameter
- DB_UNIQUE_NAME
- DB_UNIQUE_NAME parameter
- DELAY attribute
- DGMGRL
- diagnostic data
- DMON (Data Guard Broker Monitor Process) / Data Guard background processes
- dynamic performance views
E
F
- failover, role transitions
- FAL_SERVER parameter
- FAN
- Fast-start failover
- fast-start failover
- FastStartFailoverLagLimit property / Time for action – configuring fast-start failover
- FastStartFailoverThreshold property / Time for action – configuring fast-start failover
- FCF
- flashback
- about / Using flashback on a standby database
- using, on standby database / Using flashback on a standby database, Time for action – using flashback on a standby database
- enabling / Time for action – using flashback on a standby database
- retention period, adjusting / Time for action – using flashback on a standby database
- table information, gathering before truncation / Time for action – using flashback on a standby database
- table, truncating / Time for action – using flashback on a standby database
- time, capturing / Time for action – using flashback on a standby database
- data, verifying on standby database / Time for action – using flashback on a standby database
- time-based flashback, performing / Time for action – using flashback on a standby database
- data, verifying after flashback / Time for action – using flashback on a standby database
- data, exporting from standby database / Time for action – using flashback on a standby database
- table, importing in primary database / Time for action – using flashback on a standby database
- table data, verifying after importing in primary database / Time for action – using flashback on a standby database
- MRP, starting on standby database / Time for action – using flashback on a standby database
- force logging, primary database
- foreign archived logs, logical standby database
- FRA, primary database
- FSFO (fast-start failover)
- FSFP (Data Guard broker fast-start failover pinger process) / Data Guard background processes
G
- gap
- GoldenGate
- GoldenGate and Streams
- Guaranteed restore point
H
I
J
L
- LOCATION attribute
- logical block corruption
- logical standby database
- logical standby database configuration
- logical standby database customization
- logical standby database verification
- LOG_ARCHIVE_CONFIG parameter
- LOG_ARCHIVE_DEST_n parameter
- LOG_ARCHIVE_DEST_STATE_n parameter
- LOG_ARCHIVE_MAX_POCESSES parameter
- LOG_FILE_NAME_CONVERT parameter
- loop detection / GoldenGate and Streams
- LSP0 (Logical Standby Coordinator Process) / Data Guard background processes
- LSP1 (Logical Standby Dictionary Build Process) / Data Guard background processes
- LSP2 (Logical Standby Set Guard Process) / Data Guard background processes
M
N
- network bandwidth consideration, physical standby database
- network tuning, Data Guard
- NET_TIMEOUT aattribute
- NET_TIMEOUT attribute
- NOAFFIRM attribute
- NOLOGGING changes
- NONE Database Guard mode
- NSAn (Redo Transport NSA1 Process) / Data Guard background processes
- NSSn (Redo Transport NSA1 Process) / Data Guard background processes
O
- observer configuration, Fast-start failover
- OMF
- one-off patches
- online redo log (ORL) files
- OPatch
- ORA-10458 error
- ORA-12514 error
- ORA-16715 error
- ORA-16737 error
- ORA-16797 error
- Oracle BI
- Oracle Call Interface (OCI) / Fast Application Notification (FAN)
- Oracle Data Guard and RAC
- Oracle Data Guard evolution
- Oracle Enterprise Manager Cloud Control integration
- Oracle Real Application Clusters (RAC)
- Oracle Universal Connection Pool (UCP) / Fast Application Notification (FAN)
P
- patch, Data Guard configuration
- patches
- patch history
- patching
- patch set
- Patch Set Updates (PSU)
- PeopleSoft
- physical block corruption
- physical standby database
- physical standby database instance
- PITR (Point-in-Time Recovery) / Using flashback on a standby database
- post-installation steps, physical standby database
- primary database
- primary database, physical standby database
- PSU patches
R
- RAC integration
- Real Application Cluster (RAC)
- Recovery Manager (RMAN)
- Recovery Time Objective (RTO) / Cloud Control Data Guard administration home page
- Recovery Time Objective (RTO) value / Failover
- Redo Apply
- redo apply, physical standby database
- redo transport and apply tuning, Data Guard
- redo transport authentication problems, troubleshooting
- redo transport services
- REOPEN attribute
- RFS
- RFS (Remote File Server) / Data Guard background processes
- RMAN Catalog application
- RMAN duplicate
- RMAN incremental backup
- RMAN integration
- RMAN settings, for Data Guard environment
- role transitions
- role transitions, Data Guard broker
- Rolling Upgrade Using Transient Logical Standby
- performing / Time for action – performing a rolling upgrade using the transient logical standby database
- protection mode, ensuring / Time for action – performing a rolling upgrade using the transient logical standby database
- compatibility, ensuring / Time for action – performing a rolling upgrade using the transient logical standby database
- Data Guard broker, disabling / Time for action – performing a rolling upgrade using the transient logical standby database
- flashback, enabling / Time for action – performing a rolling upgrade using the transient logical standby database
- guaranteed restore point, creating / Time for action – performing a rolling upgrade using the transient logical standby database
- log miner dictionary, creating / Time for action – performing a rolling upgrade using the transient logical standby database
- physical standby database, converting to logical standby database / Time for action – performing a rolling upgrade using the transient logical standby database
- apply status, monitoring / Time for action – performing a rolling upgrade using the transient logical standby database
- SQL Apply, starting / Time for action – performing a rolling upgrade using the transient logical standby database
- logical standby database, upgrading / Time for action – performing a rolling upgrade using the transient logical standby database
- Switchover to upgraded 11.2.0.3 / Time for action – performing a rolling upgrade using the transient logical standby database
- physical standby database, retransforming / Time for action – performing a rolling upgrade using the transient logical standby database
- logical standby database, starting from new version binary / Time for action – performing a rolling upgrade using the transient logical standby database
- redo transport, enabling / Time for action – performing a rolling upgrade using the transient logical standby database
- upgraded standby database, verifying / Time for action – performing a rolling upgrade using the transient logical standby database
S
- SAP
- Security Patch Update (SPU)
- select failover
- selective replication, logical standby database
- server-side components, Data Guard broker
- server-side TAF
- Server Control Utility (SRVCTL) / Configuring the server-side TAF
- SERVICE attribute
- Service Level Agreements (SLAs) / Network bandwidth consideration
- session failover
- Single Client Access Names (SCAN) / Configuring the client-side TAF
- snapshot standby database
- SQL*Plus
- SQL Apply / Logical standby database
- SRL groups
- srvctl add service command / Configuring the server-side TAF
- srvctl modify service command / Configuring the server-side TAF
- standby control file
- standby database
- standby database, Data Guard broker
- standby database-related initialization parameters
- STANDBY Database Guard mode
- STANDBY_FILE_MANAGEMENT parameter
- storage-based replication solutions
- Streams
- switchover, role transitions
- SYNC attribute
- synchronization, physical standby database
- Synchronous redo transport (SYNC)
T
- TAF
- TopLink
- trace files
- troubleshooting
- TSPITR (Tablespace Point-in-Time Recovery) operations
U
- UNNAMED datafiles errors
- user interfaces
V
- V$ARCHIVED_LOG view
- V$ARCHIVE_DEST_STATUS view
- V$ARCHIVE_GAP view
- V$DATABASE view
- V$DATAGUARD_CONFIG view
- V$DATAGUARD_STATUS view
- V$LOGSTDBY_PROCESS view
- V$MANAGED_STANDBY view
- VALID_FOR attribute
- version 7.3, Data Guard
- version 8i, Data Guard
- version 9i, Data Guard
- version 10g, Data Guard
- version 11g, Data Guard
..................Content has been hidden....................
You can't read the all page of ebook, please click
here login for view all page.