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
Relocating old table data to a lower cost or secondary tier
In some databases such as TELCO applications, call detail records (CDR) accumulate very quickly. For regulatory purposes, these records must be saved for several years, causing the size of the database to grow at an enormous rate. If the CDR table is partitioned, the old partitions can be relocated to the lower cost tier. However, if the CDR table is not partitioned, alternatives are needed. One potential alternative is described below.
The extents for CDR tables are allocated on demand. This means extent 100 is created much earlier than extent 900. It also means that the activity for CDR records in extent 100 is less. From the extent-id, using dba_extents and dba_segments dictionary tables, file, offset, length information can be generated. From this information, you can relocate the identified portion of the file to the secondary tier.
To relocate old table data to a lower cost or secondary tier
- Identify the less active objects or segments of the database using an Oracle AWR report.
- Determine the storage tier to which the less active objects or segments can be relocated.
- To ensure an up-to-date SFDB repository, run dbed_update.
- Run the command to move the table CDR_100 to tier-2.
$ dbdst_obj_move -S PROD -H /home_dir -t CDR_100 -c tier-2
The command in the example below displays the set datafiles where the specified table/index resides. If the underlying file system is a multi-volume file system, it will display the corresponding volume and tier name.
To verify that the database segment is relocated to the correct tier
- Run the command to view the relocated table:
$ dbdst_obj_view -S PROD -H /home_dir -o CDR_100
For more on using the dbdst_obj_move command:
See Optimizing sub-file database object placement using SmartTier for Oracle.