Veritas InfoScale™ 8.0.2 Storage and Availability Management for Oracle Databases - AIX, Linux, Solaris
- Section I. Storage Foundation High Availability (SFHA) management solutions for Oracle databases
- Overview of Storage Foundation for Databases
- Introducing Storage Foundation High Availability (SFHA) Solutions for Oracle
- About Veritas File System
- About Veritas Volume Manager
- About Dynamic Multi-Pathing (DMP)
- About Cluster Server
- About Cluster Server agents
- About Veritas InfoScale Operations Manager
- Feature support for Oracle across Veritas InfoScale 8.0.2 products
- Use cases for Veritas InfoScale products
- Overview of Storage Foundation for Databases
- Section II. Deploying Oracle with Veritas InfoScale products
- Deployment options for Oracle in a Storage Foundation environment
- Oracle deployment options in a Storage Foundation environment
- Oracle single instance in a Storage Foundation environment
- Single instance Oracle with off-host in a Storage Foundation environment
- Single instance Oracle in a highly available cluster with Storage Foundation High Availability
- Single instance Oracle in a parallel cluster with SF Cluster File System HA environment
- About Oracle RAC in a Storage Foundation for Oracle RAC environment
- About Oracle in a replicated Storage Foundation environment
- Deploying Oracle and Storage Foundation in a virtualization environment
- Deploying Oracle with Storage Foundation SmartMove and Thin Provisioning
- Deploying Oracle with Storage Foundation
- Tasks for deploying Oracle databases
- Planning your Oracle storage
- About selecting a volume layout for deploying Oracle
- Setting up disk group for deploying Oracle
- Creating volumes for deploying Oracle
- Creating VxFS file system for deploying Oracle
- Mounting the file system for deploying Oracle
- Installing Oracle and creating database
- Deploying Oracle in an off-host configuration with Storage Foundation
- Deploying Oracle with High Availability
- Deploying Oracle with Volume Replicator (VVR) for disaster recovery
- Deployment options for Oracle in a Storage Foundation environment
- Section III. Configuring Storage Foundation for Database (SFDB) tools
- Configuring and managing the Storage Foundation for Databases repository database
- About the Storage Foundation for Databases (SFDB) repository
- Requirements for Storage Foundation for Databases (SFDB) tools
- Storage Foundation for Databases (SFDB) tools availability
- Configuring the Storage Foundation for Databases (SFDB) tools repository
- Backing up and restoring the Storage Foundation for Databases (SFDB) repository
- Updating the Storage Foundation for Databases (SFDB) repository after adding a node
- Updating the Storage Foundation for Databases (SFDB) repository after removing a node
- Removing the Storage Foundation for Databases (SFDB) repository
- Configuring authentication for Storage Foundation for Databases (SFDB) tools
- Configuring and managing the Storage Foundation for Databases repository database
- Section IV. Improving Oracle database performance
- About database accelerators
- Improving database performance with Veritas Extension for Oracle Disk Manager
- About Oracle Disk Manager in the Veritas InfoScale products environment
- Setting up Veritas Extension for Oracle Disk Manager in SFHA environment
- Configuring the Veritas Extension for Oracle Disk Manager in SFHA environment
- How to prepare existing database storage for Oracle Disk Manager in SFHA environment
- Verifying that Oracle Disk Manager is configured in SFHA environment
- Disabling the Oracle Disk Manager feature in SFHA environment
- Improving database performance with Veritas Cached Oracle Disk Manager
- About Cached ODM in SFHA environment
- Configuring Cached ODM in SFHA environment
- Administering Cached ODM settings with Cached ODM Advisor in SFHA environment
- Generating reports of candidate datafiles by using Cached ODM Advisor in SFHA environment
- Generating a basic report of the current read activity by using Cached ODM Advisor in SFHA environment
- Generating summary reports of historical activity by using Cached ODM Advisor in SFHA environment
- Generating historical activity reports on individual datafiles by using Cached ODM Advisor in SFHA environment
- Enabling and disabling Cached ODM on data files by using Cached ODM Advisor in SFHA environment
- Display the Cached ODM states of the database files by using Cached ODM Advisor in SFHA environment
- Show Cached ODM statistics by using Cached ODM Advisor in SFHA environment
- Displaying ODM I/O statistics by using Cached ODM Advisor in SFHA environment
- Generating reports of candidate datafiles by using Cached ODM Advisor in SFHA environment
- Improving database performance with Quick I/O
- About Quick I/O
- Creating Oracle database files as Quick I/O files using qiomkfile
- Preallocating space for Quick I/O files using the setext command
- Accessing regular VxFS files as Quick I/O files
- Converting Oracle files to Quick I/O files
- About sparse files
- Handling Oracle temporary tablespaces and Quick I/O
- Displaying Quick I/O status and file attributes
- Extending a Quick I/O file
- Using Oracle's AUTOEXTEND with Quick I/O files
- Recreating Quick I/O files after restoring a database
- Disabling Quick I/O
- Creating Quick I/O files in Solaris local zone
- Improving database performance with Cached Quick I/O
- Section V. Using point-in-time copies
- Understanding point-in-time copy methods
- About point-in-time copies
- When to use point-in-time copies
- About Storage Foundation point-in-time copy technologies
- Point-in-time copy solutions supported by SFDB tools
- About snapshot modes supported by Storage Foundation for Databases (SFDB) tools
- Volume-level snapshots
- About Reverse Resynchronization in volume-level snapshots (FlashSnap)
- Storage Checkpoints
- About FileSnaps
- Considerations for Oracle point-in-time copies
- Administering third-mirror break-off snapshots
- Administering space-optimized snapshots
- Planning to create an instant space-optimized snapshot
- Preparing a legacy volume for the creation of an instant snapshot
- Creating a shared cache object
- Creating a clone of an Oracle database by using space-optimized snapshots
- Creating multiple clones using FlashSnap snapshots
- Recovering the clone database manually
- Administering Storage Checkpoints
- About Storage Checkpoints
- Database Storage Checkpoints for recovery
- Creating a Database Storage Checkpoint
- Deleting a Database Storage Checkpoint
- Mounting a Database Storage Checkpoint
- Unmounting a Database Storage Checkpoint
- Creating a database clone using a Database Storage Checkpoint
- Restoring database from a Database Storage Checkpoint
- Gathering data for offline-mode Database Storage Checkpoints
- Administering FileSnap snapshots
- Backing up and restoring with Netbackup in an SFHA environment
- Understanding point-in-time copy methods
- Section VI. Optimizing storage costs for Oracle
- Understanding storage tiering with SmartTier
- Configuring and administering SmartTier
- Configuring SmartTier for Oracle
- SmartTier for Oracle command requirements
- Defining database parameters
- Configuring storage classes
- Converting a Veritas File System (VxFS) to a VxFS multi-volume file system
- Classifying volumes into a storage class
- Displaying free space on your storage class
- Adding new volumes to a storage class
- Removing volumes from a storage class
- Optimizing database storage using SmartTier for Oracle
- Running reports using SmartTier for Oracle
- Extent balancing in a database environment using SmartTier for Oracle
- Running sub-file database object reports using SmartTier for Oracle
- Optimizing sub-file database object placement using SmartTier for Oracle
- Configuring SmartTier for Oracle
- SmartTier use cases for Oracle
- Compressing files and databases to optimize storage costs
- Using the Compression Advisor tool
- About the Compression Advisor tool
- Compressing Oracle archive logs using Compression Advisor
- Displaying compression candidate data files using Compression Advisor
- Compressing Oracle data files using Compression Advisor
- Displaying compressed data files using Compression Advisor
- Uncompressing Oracle data files using Compression Advisor
- Compression Advisor command reference
- Section VII. Managing Oracle disaster recovery
- Section VIII. Storage Foundation for Databases administrative reference
- Storage Foundation for Databases command reference
- Tuning for Storage Foundation for Databases
- Additional documentation
- About tuning Veritas Volume Manager (VxVM)
- About tuning VxFS
- About tuning Oracle databases
- About tuning AIX Virtual Memory Manager
- About tuning Solaris for Oracle
- Troubleshooting SFDB tools
- About troubleshooting Storage Foundation for Databases (SFDB) tools
- About the vxdbd daemon
- Troubleshooting vxdbd
- Resources for troubleshooting SFDB tools
- Troubleshooting SmartTier for Oracle
- Upgrading Storage Foundation for Databases (SFDB) tools from 5.0.x to 8.0.2 (2184482)
- Troubleshooting Reverse Resynchronization
- Manual recovery of Oracle database
- Storage Foundation for Databases command reference for the releases prior to 6.0
- About SFDB commands backward compatibility
- Storage Foundation for Databases (SFDB) tools features which are no longer supported
- Preparing storage for Database FlashSnap
- About creating database snapshots
- FlashSnap commands
- Creating a snapplan (dbed_vmchecksnap)
- Validating a snapplan (dbed_vmchecksnap)
- Displaying, copying, and removing a snapplan (dbed_vmchecksnap)
- Creating a snapshot (dbed_vmsnap)
- Backing up the database from snapshot volumes (dbed_vmclonedb)
- Cloning a database (dbed_vmclonedb)
- Resynchronizing the snapshot to your database
- Removing a snapshot volume
- Guidelines for Oracle recovery
- Database Storage Checkpoint Commands
- Creating or updating the repository using dbed_update
- Creating Storage Checkpoints using dbed_ckptcreate
- Displaying Storage Checkpoints using dbed_ckptdisplay
- Mounting Storage Checkpoints using dbed_ckptmount
- Unmounting Storage Checkpoints using dbed_ckptumount
- Performing Storage Rollback using dbed_ckptrollback
- Removing Storage Checkpoints using dbed_ckptremove
- Cloning the Oracle instance using dbed_clonedb
- Section IX. Reference
- Appendix A. VCS Oracle agents
- Appendix B. Sample configuration files for clustered deployments
- Appendix C. Database FlashSnap status information
- Appendix D. Using third party software to back up files
About the Veritas File System intent log
Most file systems rely on full structural verification by the fsck utility as the only means to recover from a system failure. For large disk configurations, this involves a time-consuming process of checking the entire structure, verifying that the file system is intact, and correcting any inconsistencies. VxFS provides fast recovery with the VxFS intent log and VxFS intent log resizing features.
VxFS reduces system failure recovery times by tracking file system activity in the VxFS intent log. This feature records pending changes to the file system structure in a circular intent log. The intent log recovery feature is not readily apparent to users or a system administrator except during a system failure. By default, VxFS file systems log file transactions before they are committed to disk, reducing time spent recovering file systems after the system is halted unexpectedly.
During system failure recovery, the VxFS fsck utility performs an intent log replay, which scans the intent log and nullifies or completes file system operations that were active when the system failed. The file system can then be mounted without requiring a full structural check of the entire file system. Replaying the intent log might not completely recover the damaged file system structure if there was a disk hardware failure; hardware problems might require a complete system check using the fsck utility provided with VxFS.
The mount command automatically runs the VxFS fsck command to perform an intent log replay if the mount command detects a dirty log in the file system. This functionality is only supported on a file system mounted on a Veritas Volume Manager (VxVM) volume, and is supported on cluster file systems.
See the fsck_vxfs(1M) manual page and mount_vxfs(1M) manual page.
The VxFS intent log is allocated when the file system is first created. The size of the intent log is based on the size of the file system - the larger the file system, the larger the intent log. You can resize the intent log at a later time by using the fsadm commnad.
See the fsadm_vxfs(1M) manual page.
The maximum default intent log size for disk layout Version 7 or later is 256 megabytes.
Note:
Inappropriate sizing of the intent log can have a negative impact on system performance.