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
- About Veritas File System
- Overview of Storage Foundation for Databases
- Section II. Deploying Oracle with Veritas InfoScale products
- Deployment options for Oracle in a Storage Foundation environment
- Deploying Oracle with Storage Foundation
- Setting up disk group for deploying Oracle
- Creating volumes for deploying Oracle
- Creating VxFS file system for deploying Oracle
- 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
- Configuring the Storage Foundation for Databases (SFDB) tools 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
- 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 summary reports of historical activity 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
- Improving database performance with Cached Quick I/O
- Section V. Using point-in-time copies
- Understanding point-in-time copy methods
- 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
- Creating a clone of an Oracle database by using space-optimized snapshots
- Administering Storage Checkpoints
- Database Storage Checkpoints for recovery
- 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
- Optimizing database storage using SmartTier for Oracle
- Extent balancing in a database environment 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
- 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
- About tuning Veritas Volume Manager (VxVM)
- About tuning VxFS
- About tuning Oracle databases
- About tuning Solaris for Oracle
- Troubleshooting SFDB tools
- About troubleshooting Storage Foundation for Databases (SFDB) tools
- About the vxdbd daemon
- Resources for troubleshooting SFDB tools
- Manual recovery of Oracle database
- Storage Foundation for Databases command reference for the releases prior to 6.0
- 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)
- Guidelines for Oracle recovery
- Database Storage Checkpoint Commands
- 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
FlashSnap configuration parameters
Table: FlashSnap - Configuration Parameters lists the FlashSnap configuration parameters that can be provided in the configuration file. If you want to specify the parameter on the command line, refer to the Command Line Option column of the table.
Table: FlashSnap - Configuration Parameters
Parameter | Description | Accepted Values | Command Line Option |
---|---|---|---|
VERSION | The version of the configuration file format. | n.n Example: 7 | NA |
FLASHSNAP_NAME (*) | A unique identifier of the FlashSnap configuration. | String Example: snap1 | --flashsnap_name snap1 OR --name snap1 |
ORACLE_SID (*) | The SID of the database of which the snapshot is to be taken. | String Example: orcl | --oracle_sid orcl OR -S orcl |
ORACLE_HOME (*) | The Oracle Home directory of the SID of the database. | Valid path Example: | --oracle_home /oracle/databaseHome OR -H /oracle/databaseHome |
APP_MODE | The mode of the application when the snapshot operation is being performed. | offline online instant | --app_mode offline OR online OR instant |
PFILE | The location of the database pfile, if the database is running with a pfile in a non-standard location. | pfile location | --pfile location |
SNAPSHOT_PLEX_TAG | The value of the putil2 attribute tag for the plexes that must be a part of the snapshot. | String Example: dbed_snap1 | --snapshot_plex_tag dbed_snap1 OR --plex_tag dbed_snap1 |
SNAPSHOT_VOL_PREFIX | The string prefixed to volume names to create snapshot volume names. | String Example: SNAPVOL_ | --snapshot_vol_prefix SNAPVOL_ |
SNAPSHOT_DG_PREFIX | The string prefixed to disk group names to create snapshot disk group names. | String Example: SNAPDG_ | --snapshot_dg_prefix SNAPDG_ |
SNAPSHOT_MIRROR | The number of mirrors that need to broken off to form the snapshot volumes. | Number | --snapshot_mirror 2 OR --n 2 |
SNAPSHOT_ARCHIVE_LOG | If this parameter is set, the snapshot operation is also performed on the archive log volumes. This parameter is applicable for Oracle databases only. | Y or N | --snapshot_archive_log OR --no_snapshot_archive_log |
SECONDARY_HOST | The host on which the snapshot can be mounted and the application can be cloned. | Host name | --secondary_host sys4 |
PFILE_MOD | The location of the file in the Oracle pfile format that is used to modify initialization parameters for the clone instance. | The location of the pfile. | --pfile_mod pfile_location |
MAPPED_MOUNTS | The paths where the snapshot volumes should be mounted. | dg1:volume1=path1; dg2:volume2=path2 Example: mydg:datavol=/tmp/fsnp; | --mapped_mounts mydg:datavol=/tmp/fsnp |
CLONE_PATH | The directory under which the snapshot volumes must be mounted. | Valid path
| --clone_path |
CLONE_NAME | The Oracle_SID of the clone instance. | String Example: clone1 | --clone_name clone1 |
EXTRA_OBJECTS | The list of additional objects that must be included in the snapshot disk groups. Examples of additional objects: volumes, volume sets, cache objects. | Comma-separated list of objects such that each object is specified as <diskgroup>:<object> | --extra_objects <dg1>:<vol1>,<dg2>:<vol2> OR --extra <dg1>:<co1> |
REVERSE_ RESYNC_ARCHIVE_LOG | Whether archivelog volume is to be reverse resynchronized. | Yes or No (Default: No) | --reverse_resync_archive_log <value> OR --rr_archive_log <value> |
REVERSE_ RESYNC_RECOVERY | Method for recovering database during reverse resynchronization. | Auto, Manual or Auto_Until_SCN (Default: Auto) | --reverse_resync_recovery <value> OR --rr_recovery <value> |
Note:
The path that is specified with the PFILE_MOD parameter is local to the system on which the clone operation is performed. If the clone operation is performed on a host other than the one from which the command is invoked, then the parameter file should be copied to the host on which the clone operation is performed.
Note:
(*) denotes that the parameter is mandatory.