Index
A B C D E F G H I L M N O P R S T U V W
A
- alerts
-
- Enterprise Manager, 3.2
- ALTER SESSION ENABLE RESUMABLE statement, 2.2.3.7
- ANALYZE TABLE tablename VALIDATE STRUCTURE CASCADE, 2.2.2.5
- applications
-
- datatype support, 2.4.1.3
- defining as services, 2.3.1
- failover, 4.2.5
- fast failover, 2.6
- managing with Oracle Clusterware, 2.3.2
- service brownouts, 3.2.2
- tracking performance with Beacon, 3.2.1
- upgrades, 4.4.5
- architecture
-
- high availability, 1.1
- ARCHIVELOG mode, 2.2.1.1
- archiving strategy, 2.4.4.4
- ASM
-
- See Automatic Storage Management (ASM)
- asm_diskstring parameter, 2.1.4
- ASMLib, 2.1.2
- asynchronous disk I/O, 2.2.2.6
- Automatic Database Diagnostic Monitor (ADDM), 2.2.3.1
- automatic performance tuning, 2.2.3.1
- automatic segment space management, 2.2.3.5
-
- using, 2.2.3.5
- Automatic Shared Memory Management, 2.2.2.8
- Automatic Storage Management (ASM)
-
- and HARD-compliant storage, 2.1.6
- asm_diskstring parameter, 2.1.4
- ASMLib, 2.1.2
- database file management, 2.1.2
- disk device allocation, 2.1.3
- disk group size, 2.1.5
- migrating databases to and from, 2.1.2, 4.4.1.1
- recovery, 4.2.6
- redundancy, 2.1.5
- with disk multipathing software, 2.1.4
- automatic undo management
-
- described, 2.2.3.3
- Automatic Workload Repository (AWR), 2.2.3.1
-
- best practices, 2.2.3.1
- evaluating performance requirements, 2.1.1
- AWR
-
- See Automatic Workload Repository (AWR)
B
- backup and recovery
-
- best practices, 2.5
- checksums calculated during, 2.2.1.2
- enabling with ARCHIVELOG mode, 2.2.1.1
- recommendations, 2.5
- backups
-
- configuring, 2.5
- OCR, 2.3.5
- Beacons, 3.2.1
-
- configuring, 3.2.1
- benefits
-
- Grid Control, 1.4
- high availability best practices, 1.2
- logical standby database, 2.4.1.2
- physical standby database, 2.4.1.1
- best practices, 1.1
-
- AWR, 2.2.3.1
- backup and recovery, 2.5
- Data Guard configurations, 2.4
- failover (fast-start), 2.4.7.2.2, 4.2.2.2
- failover (manual), 2.4.7.2.3, 4.2.2.2, 4.2.2.2.2
- operational, 1.4
- RAC configurations, 2.3, 2.3
- security policy, 1.4
- storage subsystems, 2.1
- switchover, 2.4.7.1.1, 4.2.3.2
- upgrades, 4.4.2.1
- block checking
-
- preventing corruption, 2.2.2.5
- block checksums, 2.2.1.2
- block media recovery, 4.2.7.2
- block validation
-
- end-to-end, 2.1.6
- broker
-
- benefits, 2.4.4.3
- brownouts, 3.2.2
C
- checksums, 2.2.1.2
- client failover
-
- best practices, 2.6.2
- clients
-
- application failover, 4.2.5
- configuring for failover, 2.6.1
- load balancing, 2.3.3
- Cluster Ready Services (CRS)
-
- described, 4.3.1.1
- recovering service availability, 4.3.1.1
- clusters
-
- management, 2.3.2
- clusterwide outage
-
- restoring the standby database after, 4.3.4
- complete site failover
-
- recovery time objective (RTO), 4.2.1.2
- configurations
-
- RAC, 2.3
- connect-time failover, 4.3.1.2
- corruption
-
- detecing in-memory, 2.2.1.2
- detecting, 2.2.1.2
- detecting redo record, 2.2.1.2
- recovery, 4.2.7
- corruptions
-
- preventing memory and data, 2.2.2.5
- crash recovery
-
- bounded, 2.2.2.10
- CREATE DISKGROUP statement
-
- examples, 2.1.3, 2.1.3, 2.1.5
- CRS
-
- See Cluster Ready Services (CRS)
- CRSD process
-
- OCR backups, 2.3.5
D
- data
-
- protecting against corruption, 2.1.6
- protecting outside of the database, 2.4.9
- data area disk group failure
-
- recovery options, 4.2.6.3
- data corruption
-
- HARD protection, 2.1.6, 4.1.1.1
- recovery with Data Guard, 4.2.7.1
- data failure
-
- manual re-creation, 4.2.7.4
- recovery, 4.2.7, 4.2.7.1
- restoring fault tolerance on standby database, 4.3.5
- RMAN block media recovery, 4.2.7.2
- RMAN datafile media recovery, 4.2.7.3
- Data Guard
-
- adding to a RAC primary, 5.3
- archiving strategies, 2.4.4.4
- broker, 2.4.4.3
- choosing a standby type, 2.4.1.2
- cloning physical standby databases, 2.4.8
- failover
-
- best practices (fast-start), 2.4.7.2.2
- best practices (manual), 2.4.7.2.3
- recovery for data area disk group failures, 4.2.6.3
- using Enterprise Manager, 4.2.2.2.1
- using SQL*Plus, 4.2.2.2.2
- when to perform, 4.2.2.1
- log apply services, 2.4.6
- managing targets, 3.3.3
- monitoring, 3.2.4
- performance, 2.4.10
- recovery from data corruption and data failure, 4.2.7.1
- redo transport services, 2.4.5
- restoring standby databases, 4.3.2
- role transitions, 2.4.7
- switchover
-
- best practices, 2.4.7.1.1
- using Enterprise Manager, 4.2.3.2.1
- using SQL*Plus, 4.2.3.2.2
- data protection modes, 2.4.2
- Data Pump
-
- moving the contents of the SYSTEM tablespace, 4.4.4.4
- data-area disk group failure
-
- See Also Data Guard failover, fast-start failover, local recovery
- database area
-
- contents, 2.1.3
- disk partitioning, 2.1.3
- database block checking, 2.2.2.5, 2.2.2.5
- database configuration
-
- recommendations, 2.2
- database files
-
- ASM integration, 2.1.2
- management optimizations, 2.1.2
- recovery related, 2.1.3
- database patch upgrades
-
- recommendations, 4.4.2.1
- Database Resource Manager, 2.2.3.8
- Database Upgrade Assistant (DBUA), 4.4.3.1
- databases
-
- configuring maximum RAC instance, 2.3.7
- evaluating performance requirements, 2.1.1
- migration, 4.4.4.1
- object reorganization, 4.4.6
- resolving inconsistencies, 4.2.8.3
- switching primary and standby roles amongst, 4.2.3.1
- upgrades
-
- upgrades, 4.4.3
- datafile block corruption
-
- recovery, 4.2.7
- datatypes
-
- supported by standby databases, 2.4.1.3
- DB_BLOCK_CHECKING initialization parameter, 2.2.2.5
- DB_BLOCK_CHECKSUM initialization parameter, 2.2.1.2, 2.2.1.2
- DB_CACHE_SIZE initialization parameter, 2.4.6.1
- DB_CREATE_FILE_DEST initialization parameter
-
- enabling Oracle managed files (OMF), 2.1.3
- DB_FLASHBACK_RETENTION_TARGET initialization parameter, 2.2.2.3
- DB_KEEP_CACHE_SIZE initialization parameter, 2.4.6.1
- DB_RECOVERY_FILE_DEST initialization parameter
-
- enabling Oracle managed files (OMF), 2.1.3
- flash recovery area, 2.2.2.2
- DB_RECOVERY_FILE_DEST_SIZE initialization parameter
-
- enabling Oracle managed files (OMF), 2.1.3
- limit for flash recovery area, 2.2.2.2
- DB_RECYCLE_CACHE_SIZE initialization parameter, 2.4.6.1
- DBCA
-
- balancing client connections, 2.3.3
- DBMS_FILE_TRANSFER package, 4.4.1.1
- DBMS_REDEFINITION PL/SQL package, 4.4.6, 4.4.6
- DBVERIFY utility, 2.2.2.5
- DEFAULT TEMPORARY TABLESPACE clause
-
- of the CREATE DATABASE statement, 2.2.3.6
- Device Mapper
-
- disk multipathing, 2.1.4
- disabling parallel recovery, 2.2.2.11
- disaster-recovery site
-
- distanced from the primary site, 2.4.2
- disk devices
-
- configuration, 2.1.3, 2.1.5
- multipathing, 2.1.4
- naming
-
- asm_diskstring parameter, 2.1.4
- ASMLib, 2.1.2
- partitioning for ASM, 2.1.3
- protecting from failures, 2.1.5
- disk failures
-
- protection from, 2.1.5
- restoring redundancy after, 2.1.5
- disk group configuration, 2.1.3
- disk groups
-
- determining proper size of, 2.1.5
- determining size of, 2.1.5
- disk multipathing, 2.1.4
- DISK_ASYNCH_IO initialization parameter, 2.2.2.6, 2.4.6.1
- distances
-
- between the disaster-recovery site and the primary site, 2.4.2
- DNS failover, 4.2.1.3
- downtime
-
- reducing, 1.4
- dropped tablespace
-
- using Flashback Database, 4.2.8.3
- dropping database objects, 4.2.8.1
- dual failures
-
- restoring, 4.3.7
- dynamic instance registration
-
- LISTENER.ORA file example, A.2.2
- SQLNET.ORA file example, A.2.1
- TNSNAMES.ORA file example, A.2.3
E
- enabling, 2.2.2.5
- endian format
-
- determining, 4.4.4
- end-to-end block validation, 2.1.6
- Enterprise Manager
-
- alerts, 3.2
- Data Guard failover, 4.2.2.2.1
- Data Guard switchover, 4.2.3.2.1
- Database Targets page, 3.2.2
- managing patches, 3.3.2
- metrics, 3.2, 3.2.3
- notification rules, 3.2.1, 3.2.2
- performance, 3.2.2
- equations
-
- setting PARALLEL_MIN_SERVERS, 2.2.2.10
- standby redo log files, 2.4.4.5
- EXTERNAL REDUNDANCY clause
-
- on the CREATE DISKGROUP statement, 2.1.5
F
- failover (fast-start)
-
- best practices, 2.4.7.2.2
- reinstating the former primary database, 4.3.2
- failover (manual)
-
- best practices, 2.4.7.2.3
- when to perform, 4.2.2.1
- failovers
-
- application, 4.2.5
- complete site, 4.2.1
- defined, 4.2.2
- described, 4.2.2.2
- effect on network routes, 4.2.1.3
- Enterprise Manager, 4.2.2.2.1
- fast application, 2.6
- nondisruptive, 2.1.4
- restoring standby databases after, 4.3.2
- failure groups
-
- defining, 2.1.5
- failures
-
- space allocation, 2.2.3.7
- fast application failover, 2.6
- Fast Application Notification (FAN), 4.2.5
- FAST_START_MTTR_TARGET initialization parameter, 2.2.2.10, 2.2.2.11, 2.4.6.1
-
- controlling instance recovery time, 2.2.2.4
- fast-start fault recovery
-
- instance recovery, 2.2.2.4
- fault tolerance
-
- configuring storage subsystems, 2.1
- restoring, 4.3
- restoring after OPEN RESETLOGS, 4.3.6
- flash recovery area
-
- contents, 2.1.3
- disk group failures, 4.2.6.4
- disk partitioning, 2.1.3
- local recovery steps, 4.2.6.4
- local restart steps, 4.2.6.4
- low-cost storage grid, 2.1.1
- using, 2.2.2.2
- Flashback Database, 4.2.8, 4.2.8.3
-
- correcting human errors, 2.2.2.3
- enabling, 2.2.2.3, 2.2.2.3
- in Data Guard configurations, 2.4.4.1
- setting maximum memory, 2.2.2.7
- Flashback Drop, 4.2.8, 4.2.8.1
- flashback free buffer waits wait event, 2.2.2.3
- Flashback Query, 4.2.8, 4.2.8.2
- Flashback Table, 4.2.8, 4.2.8.1
- flashback technologies
-
- resolving database-wide inconsistencies, 4.2.8.3
- flashback technology
-
- example, 4.2.8.2
- recovering from user error, 4.2.8
- solutions, 4.2.8
- Flashback Transaction Query, 4.2.8, 4.2.8.2
- Flashback Version Query, 4.2.8, 4.2.8.2
- FORCE LOGGING mode, 2.4.4.2
G
- Grid Control
-
- See Oracle Grid Control, Enterprise Manager
- GV$SYSSTAT view
-
- gathering workload statistics, 2.1.1
H
- HARD
-
- See Hardware Assisted Resilient Data (HARD)
- Hardware Assisted Resilient Data (HARD)
-
- data corruption, preventing, 2.1.6, 4.1.1.1
- when using ASM, 2.1.6
- high availability
-
- described, 1.1, 1.1
- requirements, 2.2.1
- restoring after fast-start failover, 4.3.2
- host bus adapters (HBA)
-
- load balancing across, 2.1.4
- hosts
-
- using dynamic instance registration
-
- LISTENER.ORA file example, A.2.2
- SQLNET.ORA file example, A.2.1
- TNSNAMES.ORA file example, A.2.3
- HR service
-
- scenarios, 4.3.1.1
- human errors
-
- correcting with Flashback Database, 2.2.2.3
- recovery, 4.2.8
I
- index blocks, 2.2.2.5
- index rebuilding, 4.4.6
- initialization parameters
-
- primary and physical standby example, 2.4.4.4
- in-memory block change checking, 2.2.2.5
- in-memory corruption
-
- detecting, 2.2.1.2
- instance failure
-
- recovery, 2.2.2.4
- instance failures
-
- single, 4.2.4.1
- instance recovery
-
- bounded, 2.2.2.10
- controlling with fast-start fault recovery, 2.2.2.4
- parallel execution, 2.2.2.9
- interconnect subnet
-
- verification with Oracle ORADEBUG utility, 2.3.6
- interim patch upgrade, 4.4.2
- I/O bandwidth
-
- for flash recovery area, 2.2.2.3
- I/O operations
-
- load balancing, 2.1.4
- tuning, 2.4.6.1
L
- library
-
- ASMLib support for ASM, 2.1.2
- LISTENER.ORA file sample, A.2.2
- listeners
-
- balancing clients across, 2.3.3
- LISTENER.ORA file example, A.2.2
- SQLNET.ORA file example, A.2.1
- TNSNAMES.ORA file example, A.2.3
- load balancing
-
- client connections, 2.3.3
- I/O operations, 2.1.4
- through disk multipathing, 2.1.4
- LOAD_BALANCE parameter
-
- balancing client connections, 2.3.3
- load-balancing application services, 4.3.1.2
- local archiving first, 2.4.4.4
- local recovery
-
- for data area disk group failures, 4.2.6.3
- for flash recovery area disk group failures, 4.2.6.4
- local restart steps
-
- for fast recovery of flash recovery area, 4.2.6.4
- locally managed tablespaces, 2.2.3.4
-
- described, 2.2.3.4
- location migration, 4.4.4
- log apply services
-
- best practices, 2.4.6
- LOG_ARCHIVE_FORMAT initialization parameter, 2.4.4.4
- LOG_ARCHIVE_LOCAL_FIRST initialization parameter, 2.4.4.4
- LOG_BUFFER initialization parameter, 2.2.2.7
- logical standby databases
-
- benefits of, 2.4.1.2
- failover, 4.2.2.2.3
- switchover, 4.2.3.2.3
- upgrades on, 4.4.3.2
- logical unit numbers (LUNs), 2.1.5
-
- defined, Glossary
- low-cost storage subsystems, 2.1.1
- LUNs
-
- See Also logical unit numbers (LUNs)
- See logical unit numbers (LUNs), 2.1.5
M
- MAA
-
- See Oracle Maximum Availability Architecture (MAA)
- manageability
-
- improving, 2.2.3
- manual failover
-
- best practices, 2.4.7.2.3, 4.2.2.2.2
- when to perform, 4.2.2.1
- maximum availability mode
-
- described, 2.4.2
- redo transport requirements, 2.4.5.1
- when to use, 2.4.2
- maximum performance mode
-
- described, 2.4.2
- redo transport requirements, 2.4.5.1
- when to use, 2.4.2
- maximum protection mode
-
- described, 2.4.2
- initialization parameter example, 2.4.4.4
- when to use, 2.4.2
- media failure
-
- recovery, 4.2.7
- memory management, 2.2.2.8
- metrics
-
- Enterprise Manager, 3.2
- migrating
-
- Data Guard to a RAC primary, 5.3
- databases to and from ASM, 2.1.2
- to MAA, 5
- to RAC from a single instance, 5.2
- Transportable Database, 4.4.4.1
- mirroring
-
- across storage arrays, 2.1.5
- monitoring
-
- Oracle Grid Control, 1.4
- rebalance operations, 4.4.1.2
- multipathing (disks)
-
- path abstraction, 2.1.4
N
- Network Attached Storage (NAS), 2.4.6.1
- network detection and failover
-
- CRS and RAC, 2.3.6
- network routes
-
- after site failover, 4.2.1.3
- before site failover, 4.2.1.3
- node failures
-
- multiple, 4.2.4.1
- node recovery
-
- bounded, 2.2.2.10
- non database object corruption and recommended repair, 4.2.7
- nondisruptive failovers, 2.1.4
- nonindex organized-table blocks, 2.2.2.5
-
- checking, 2.2.2.5
- NORMAL REDUNDANCY clause
-
- on the CREATE DISKGROUP statement, 2.1.5
- notification rules
-
- recommended, 3.2.2
- SLA influence on monitoring, 3.2.1
O
- OCR
-
- backups of, 2.3.5
- described, 2.3.4
- recovering, 4.2.4.3
- ocrconfig -export command, 2.3.5
- OMF
-
- See Oracle managed files
- online log groups
-
- minimum, 2.2.2.1
- online object reorganization, 4.4.6
- online redo log files
-
- multiplex, 2.2.2.1
- Online Reorganization and Redefinition, 4.4.6
- opatch command-line utility, 4.4.2
- operational best practices, 1.4
- ORA-1578 error, 2.2.1.2
- ORA-16625 error, 4.2.2.2.1
- Oracle Cluster Registry (OCR)
-
- See OCR
- Oracle Clusterware
-
- described, 2.3.2
- OCR mirroring, 2.3.4
- system maintenance, 4.4.7
- Oracle Data Pump
-
- platform migrations, 4.4.4.3
- Oracle Database 10g
-
- configuration recommendations, 2.2
-
- Data Guard, 2.4
- RAC configuration recommendations, 2.3
- Oracle Grid Control
-
- benefits, 1.4
- home page, 3.2
- managing Data Guard targets, 3.3.3
- Policy Violations, 3.3.1
- Oracle managed files (OMF)
-
- database file management, 2.1.3
- disk and disk group configuration, 2.1.3
- flash recovery area, 2.2.2.2
- Oracle Management Agent, 3.2
- Oracle Maximum Availability Architecture (MAA)
-
- defined, Glossary
- described, 1.3
- environment, 5.1
- web site, 1.3
- Oracle Net
-
- configuration file examples, A.2
- Oracle ORADEBUG utility
-
- verifying interconnect subnet, 2.3.6
- Oracle Resilient Low-Cost Storage Initiative, 2.1.1
- Oracle Secure Backup
-
- OCR backups, 2.3.5
- Oracle Streams
-
- database migration, 4.4.4.2
- online database upgrade, 4.4.5
- upgrades using, 4.4.3.3
- Oracle Universal Installer, 4.4.2.1
- outages
-
- managing unscheduled and scheduled, 4
- scheduled, 4.1.2
- types, 4.1.1
- unscheduled, 4.1.1
P
- parallel executions, accelerating, 2.2.2.9
- parallel recovery
-
- disabling, 2.2.2.11
- PARALLEL_EXECUTION_MESSAGE_SIZE initialization parameter, 2.4.6.1
-
- setting, 2.2.2.9
- PARALLEL_MIN_SERVERS initialization parameter
-
- tuning, 2.2.2.10
- partitions
-
- allocating disks for ASM use, 2.1.3
- patch sets
-
- rolling upgrades, 4.4.2
- patches
-
- managing with Enterprise Manager, 3.3.2
- path failures
-
- protection from, 2.1.4
- performance
-
- application, tracking with Beacon, 3.2.1
- asynchronous disk I/O, 2.2.2.6
- automatic tuning, 2.2.3.1
- Data Guard, 2.4.10
- database, gathering requirements, 2.1.1
- overhead of enabling checksums, 2.2.1.2
- physical standby databases
-
- benefits of, 2.4.1.1
- failover, 4.2.2.2.2
- location migrations, 4.4.4.5
- switchover, 4.2.3.2.2
- using as a clone, 2.4.8
- platform migration
-
- endian format for, 4.4.4
- platform migrations, 4.4.3, 4.4.4
- pool
-
- resizing, 2.2.2.8
- primary database
-
- distance from the disaster-recovery site, 2.4.2
- reinstating after a fast-start failover, 4.3.2
- restoring fault tolerance, 4.3.6
- protection modes
-
- described, 2.4.2
- determining appropriate, 2.4.2
- See Also data protection modes, maximum protection mode, maximum availability mode, maximum performance mode
R
- RAC
-
- adding Data Guard, 5.3
- application failover, 4.2.5
- client failover, 2.6.2
- configurations, 2.3
- migrating from a single instance, 5.2
- network detection and failover, 2.3.6
- recovery from unscheduled outages, 4.2.4
- restoring failed nodes or instances, 4.3.1
- rolling patch upgrade, 4.4.2.1
- rolling upgrades, 4.4.2
- system maintenance, 4.4.7
- voting disk, 2.3.4
- RAC environments
-
- adding disks to nodes, 2.1.2
- LISTENER.ORA file sample for, A.2.2
- SQLNET.ORA file sample for, A.2.1
- TNSNAMES.ORA file sample for, A.2.3
- RAID, 2.1.5
-
- logical unit numbers (LUNs), 2.1.5
- RAID protection, 2.1.5
- rebalance operations
-
- ASM disk partitions, 2.1.3, 2.1.3
- monitoring, 4.4.1.2
- recommendations
-
- database configuration, 2.2
- recovery
-
- bounded, 2.2.2.10
- recovery files
-
- created in the recovery area location, 2.2.2.2
- recovery point objective (RPO)
-
- defined, Glossary
- for data area disk group failures, 4.2.6.3
- recovery steps for scheduled outages, 4.1.2.1
- recovery steps for unscheduled outages, 4.1.1.1
- recovery time objective (RTO)
-
- defined, Glossary
- described, 4.2.1.2
- for data-area disk group failures, 4.2.6.3
- RECOVERY_ESTIMATED_IOS initialization parameter
-
- for parallel recovery, 2.2.2.11
- RECOVERY_PARALLELISM initialization parameter, 2.2.2.11
- redo log files and groups
-
- checksum, 2.2.1.2
- size, 2.2.2.1
- redo transport services
-
- best practices, 2.4.5
- redundancy
-
- CREATE DISKGROUP DATA statement, 2.1.5
- disk devices, 2.1.5
- restoring after disk failures, 2.1.5
- reinstatement, 4.3.2
- remote archiving, 2.4.4.4
- REMOTE_ARCHIVE_ENABLE initialization parameter, 2.4.4.4
- resetlogs on production database
-
- restoring standby database, 4.3.6
- resource management
-
- using Database Resource Manager, 2.2.3.8
- restoring
-
- client connections, 4.3.1.2
- failed instances, 4.3.1
- failed nodes, 4.3.1
- services, 4.3.1.1
- resumable space allocation, 2.2.3.7
-
- space allocation
-
- failures, 2.2.3.7
- RESUMABLE_TIMEOUT initialization parameter, 2.2.3.7
- RMAN
-
- calculates checksums, 2.2.1.2
- RMAN BACKUP command
-
- VALIDATE option, 2.2.2.5
- RMAN BACKUP VALIDATE command, 4.2.7.2
- RMAN block media recovery, 4.2.7.2
- RMAN BLOCKRECOVER command, 4.2.7.2
- RMAN data file media recovery, 4.2.7.3
- RMAN datafile media recovery, 4.2.7.3
- role transitions
-
- best practices, 2.4.7
- role-based destinations, 2.4.4.4
- rolling upgrades
-
- patch set, 4.4.2
- row and transaction inconsistencies, 4.2.8.2
- RPO
-
- See recovery point objective (RPO)
- RTO
-
- See recovery time objective (RPO)
S
- SALES scenarios
-
- setting initialization parameters, 2.4.4.4
- SAME
-
- See stripe and mirror everything (SAME)
- scenarios
-
- ASM disk failure and repair, 4.2.6.2.1
- Data Guard failover, 4.2.2.2.1
- Data Guard switchover, 4.2.3.2.1
- fast-start failover, 4.3.2.1
- HR service, 4.3.1.1
- object reorganization, 4.4.6
- recovering from human error, 4.2.8.2
- SALES, 2.4.4.4
- verifying interconnect subnet, 2.3.6
- scheduled outages
-
- described, 4.1.2
- recovery from, 4.1.2.1
- reducing downtime for, 4.4
- types of, 4.1.2
- See Also unscheduled outages
- secondary site outage
-
- restoring the standby database after, 4.3.4
- security
-
- recommendations, 1.4
- semantic block checking, 2.2.2.5
- server parameter file
-
- See SPFILE
- service availability
-
- recovering, 4.3.1.1
- service level agreements (SLA), 1.3
-
- effect on monitoring and notification, 3.2.1
- operational best practices, 1.4
- service tests and Beacons
-
- configuring, 3.2.1
- services
-
- RAC application failover, 4.2.5
- RAC application workloads, 2.3.1
- tools for administration, 2.3.1
- SGA_TARGET initialization parameter, 2.2.2.8
- site failover
-
- network routes, 4.2.1.3
- SLA
-
- See service level agreements (SLA)
- sort operations
-
- improving, 2.2.3.6
- space management, 2.2.3.5
- SPFILE
-
- samples, A.1
- SQL Access Advisor, 2.2.3.1
- SQL Tuning Advisor, 2.2.3.1
- SQLNET.ORA file sample, A.2.1
- standby databases
-
- choosing physical versus logical, 2.4.1.3
- comparing logical and physical, 2.4.1
- datatype support, 2.4.1.3
- distance from the primary site, 2.4.2
- restoring, 4.3.2
- standby redo log files (SRLs)
-
- determining number of, 2.4.4.5
- STANDBY_ARCHIVE_DEST initialization parameter, 2.4.4.4
- Storage Area Network (SAN), 2.4.6.1
- Storage array based RAID, 2.1.5
- storage arrays
-
- mirroring across, 2.1.5
- storage subsystems, 2.1
-
- configuring ASM, 2.1.2
- configuring redundancy, 2.1.5
- performance requirements, 2.1.1
- stripe and mirror everything (SAME), 2.1.2
- switchover
-
- described, 4.2.3.1
- Enterprise Manager, 4.2.3.2.1
- See Also Data Guard
- to a logical standby database, 4.2.3.2.3
- to a physical standby database, 4.2.3.2.2
- system failure
-
- recovery, 2.2.2.4
- system maintenance, 4.4.7
- system resources
-
- assessing, 2.4.6.1
- SYSTEM tablespace
-
- moving the contents of, 4.4.4.4
T
- table inconsistencies, 4.2.8.1
- tablespaces
-
- locally managed, 2.2.3.4
- renaming, 4.4.6, 4.4.6
- temporary, 2.2.3.6, 2.2.3.6
- TCP Nagle algorithm
-
- disabling, 2.4.5.3.3
- temporary tablespaces, 2.2.3.6, 2.2.3.6
- test environments
-
- operational best practices for, 1.4
- TNSNAMES.ORA file sample, A.2.3
- Transportable Database, 4.4.4.1
- transportable tablespaces
-
- database upgrades, 4.4.3.4
- platform migration, 4.4.4.4
U
- undo retention
-
- tuning, 2.2.3.3
- undo space
-
- managing, 2.2.3.3
- UNDO_MANAGEMENT initialization parameter
-
- automatic undo management, 2.2.3.3
- UNDO_RETENTION initialization parameter
-
- automatic undo management, 2.2.3.3
- UNDO_TABLESPACE initialization parameter
-
- automatic undo management, 2.2.3.3
- unscheduled outages
-
- described, 4.1.1
- RAC recovery, 4.2.4
- recovery from, 4.1.1.1, 4.2
- types, 4.1.1
- See Also scheduled outages
- upgrades
-
- application, 4.4.5
- best practices, 4.4.2.1
- Database Upgrade Assistant (DBUA), 4.4.3.1
- USABLE_FILE_MB column
-
- on the V$ASM_DISKGROUP view, 2.1.5
- user error
-
- flashback technology, 4.2.8
V
- V$ASM_DISK view, 2.4.6.1
- V$ASM_DISKGROUP
-
- REQUIRED_MIRROR_FREE_MB column, 2.1.5
- V$ASM_DISKGROUP view
-
- REQUIRED_MIRROR_FREE_MB column, 2.1.5
- USABLE_FILE_MB column, 2.1.5
- V$ASM_OPERATION view
-
- monitoring rebalance operations, 4.4.1.2
- V$EVENT_HISTOGRAM view, 2.4.6.1
- V$INSTANCE_RECOVERY view
-
- tuning recovery processes, 2.2.2.11
- V$OSSTAT view, 2.4.6.1
- V$SESSION_WAITS view, 2.4.6.1
- V$SYSTEM_EVENT view, 2.4.6.1
- V$SYSTEM_EVENTS view, 2.4.6.1
- VALID_FOR attribute, 2.4.4.4
- VALIDATE option
-
- on the RMAN BACKUP command, 2.2.2.5
- validation
-
- checksums during RMAN backup, 2.2.1.2
- end-to-end block validation technology, 2.1.6
- VIP address
-
- connecting to applications, 2.3.1
- described, 2.3.1
- during recovery, 4.3.1.1
- workload management, 2.3.1
- Virtual Internet Protocol (VIP) Address
-
- See AlsoVIP address
- Virtual Internet Protocol Configuration Assistant (VIPCA)
-
- VIP address configuration, 2.3.1
- voting disk (RAC)
-
- best practices, 2.3.4
W
- wait events
-
- flashback free buffer waits, 2.2.2.3
- web sites
-
- ASMLib, 2.1.2
- MAA, 1.3
- workload management
-
- connecting through VIP address, 2.3.1
- workloads
-
- examples, 2.1.1
- gathering statistics, 2.1.1