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
Creating an extent balanced file system using SmartTier for Oracle
Any multi-volume file system (MVFS) can become an extent balanced file system, if the storage tier has a chunk size associated with the class. The dbdst_admin command permits the user to define a chunk size for the class.
For example, the following dbdst_admin commands define chunk sizes for the gold and silver storage classes:
$ /opt/VRTS/bin/dbdst_admin -S $ORACLE_SID \ -o definechunk=gold:256K
$ /opt/VRTS/bin/dbdst_admin -S $ORACLE_SID \ -o definechunk=silver:128K
For example:
$ /opt/VRTS/bin/dbdst_admin -S $ORACLE_SID \ -o definechunk=TIER1:256K
The above commands make storage class gold as extent balanced.
Once the chunksize is defined for a storage tier, we can classify any MVFS into this storage tier.
For example, assume that /oradata is the filesystem created on volume-set /dev/vx/dsk/oradg/ora_vset, and contains database datafiles. Let us further assume that datafile names end with extension *.dbf. To define storage class in this MVFS, the following dbdst_classify command is used:
$ /opt/VRTS/bin/dbdst_classify -S $ORACLE_SID \ -M /dev/vx/dsk/oradg/ora_vset -v vol1:GOLD,vol2:GOLD,vol3:GOLD
For example:
$ /opt/VRTS/bin/dbdst_classify -S VRTS11r2 \ -M /dev/vx/dsk/dstdatadgot/datavol -v datavol1:FAST,datavol2:MEDIUM
It is important to note that, an MVFS can have multiple storage tiers and that each tier may have a different chunk size. For example, for the same MVFS in the above example, we can define another storage tier using the dbdst_classify command:
$/opt/VRTS/bin/dbdst_classify -S $ORACLE_SID \ -M /dev/vx/dsk/oradg/ora_vset -v vol4:silver,vol5:silver
For example:
$ /opt/VRTS/bin/dbdst_classify -S VRTS11r2 \ -M /dev/vx/dsk/dstarchdgot/archvol -v archvol1:FAST,archvol2:MEDIUM
At this point we have two storage tiers in MVFS /oradata each having different chunksizes. To create the real extent balance, we need to assign a SmartTier policy and to enforce it.
To define and enforce the policy, you could use the following dbdst_preset_policy command:
$/opt/VRTS/bin/dbdst_preset_policy -S $ORACLE_SID \ -d /oradata -P GOLD=*.dbf:SILVER=*.inx
The above example creates a SmartTier policy, assigns the policy to /oradata and enforces the policy. All datafiles of the form *.dbf will be extent balanced in GOLD tier with chunksize 256K and all index files of the form *.inx will be extent balanced in SILVER tier with chunk size 128K.
Another example:
$ /opt/VRTS/bin/dbdst_preset_policy -S VRTS11r2 \ -d /data11r2/VRTS11r2 -P "MEDIUM=temp*.dbf:FAST=*.log" Assign placement policy file successful on filesystem /data11r2 Begin enforcing filesystem /data11r2 ... Enforce placement policy successful on filesystem /data11r2
To view the space usage in the /oradata MVFS use the dbdst_show_fs command. For example:
$ /opt/VRTS/bin/dbdst_show_fs -S $ORACLE_SID -m /oradata
For example:
$ /opt/VRTS/bin/dbdst_show_fs -S VRTS11r2 -m /data11r2 -o volume VOLUME NAME SIZE USED AVAILABLE TAG ----------- ---- ---- --------- --- datavol-b4vset 10240000 3585514 6654486 PRIMARY datavol1 1024000 1024000 0 FAST datavol2 4608000 2347872 2260128 MEDIUM
When the GOLD or SILVER tier requires more space, we could add extra space by adding new volumes to the respective storage tier using the dbdst_addvol command. For example:
$ /opt/VRTS/bin/dbdst_addvol -S $ORACLE_SID \ -M /dev/vx/dsk/oradg/ora_vset -v vol7:GOLD
As soon as you add a new volume, the SmartTier policy is enforced and the extents are balanced over the new volume too. This can be viewed by using the dbdst_show_fs command again.
To view detailed extent information about a given file, you can use the fsmap command. For example:
$ /opt/VRTSvxfs/sbin/fsmap -a /oradata/emp.dbf
$ /opt/VRTS/bin/fsmap -a /oradata/emp.dbf
$ fsmap -a /standby/oradata1_1/slave/system01.dbf |more Volume Extent Type File Offset Extent Size File vol1 Data 0 262144 /standby/oradata1_1/slave/system01.dbf vol2 Data 262144 8192 /standby/oradata1_1/slave/system01.dbf vol3 Data 270336 131072 /standby/oradata1_1/slave/system01.dbf vol1 Data 401408 262144 /standby/oradata1_1/slave/system01.dbf vol2 Data 663552 180224 /standby/oradata1_1/slave/system01.dbf vol3 Data 843776 32768 /standby/oradata1_1/slave/system01.dbf vol1 Data 876544 49152 /standby/oradata1_1/slave/system01.dbf vol2 Data 925696 65536 /standby/oradata1_1/slave/system01.dbf vol3 Data 991232 196608 /standby/oradata1_1/slave/system01.dbf