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
How Oracle Disk Manager works with Oracle Managed Files
The following example illustrates the relationship between Oracle Disk Manager and Oracle Managed Files (OMF). The example shows the init.ora contents and the command for starting the database instance. To simplify Oracle UNDO management, the init.ora parameter UNDO_MANAGEMENT is set to AUTO. This is known as System-Managed Undo.
Note:
Before building an OMF database, you need the appropriate init.ora default values. These values control the location of the SYSTEM tablespace, online redo logs, and control files after the CREATE DATABASE statement is executed.
$ cat initPROD.ora UNDO_MANAGEMENT = AUTO DB_CREATE_FILE_DEST = '/PROD' DB_CREATE_ONLINE_LOG_DEST_1 = '/PROD' db_block_size = 4096 db_name = PROD $ sqlplus /nolog SQL> connect / as sysdba SQL> startup nomount pfile= initPROD.ora
The Oracle instance starts.
Total System Global Area 93094616 bytes Fixed Size 279256 bytes Variable Size 41943040 bytes Database Buffers 50331648 bytes Redo Buffers 540672 bytes
To implement a layout that places files associated with the EMP_TABLE tablespace in a directory separate from the EMP_INDEX tablespace, use the ALTER SYSTEM statement. This example shows how OMF handles file names and storage clauses and paths. The layout allows you to think of the tablespaces as objects in a file system as opposed to a collection of datafiles. Since OMF uses the Oracle Disk Manager file resize function, the tablespace files are initially created with the default size of 100MB and grow as needed. Use the MAXSIZE attribute to limit growth.
The following example shows the commands for creating an OMF database and for creating the EMP_TABLE and EMP_INDEX tablespaces in their own locale.
Note:
The directory must exist for OMF to work, so the SQL*Plus HOST command is used to create the directories:
SQL> create database PROD;
The database is created.
SQL> HOST mkdir /PROD/EMP_TABLE; SQL> ALTER SYSTEM SET DB_CREATE_FILE_DEST = '/PROD/EMP_TABLE';
The system is altered.
SQL> create tablespace EMP_TABLE DATAFILE AUTOEXTEND ON MAXSIZE \ 500M;
A tablespace is created.
SQL> ALTER SYSTEM SET DB_CREATE_FILE_DEST = '/PROD/EMP_INDEX';
The system is altered.
SQL> create tablespace EMP_INDEX DATAFILE AUTOEXTEND ON MAXSIZE \ 100M;
A tablespace is created.
Use the ls command to show the newly created database:
$ ls -lFR total 638062 drwxr-xr-x 2 oracle11g dba 96 May 3 15:43 EMP_INDEX/ drwxr-xr-x 2 oracle11g dba 96 May 3 15:43 EMP_TABLE/ -rw-r--r-- 1 oracle11g dba 104858112 May 3 17:28 ora_1_BEhYgc0m.log -rw-r--r-- 1 oracle11g dba 104858112 May 3 17:27 ora_2_BEhYu4NA.log -rw-r--r-- 1 oracle11g dba 806912 May 3 15:43 ora_BEahlfUX.ctl -rw-r--r-- 1 oracle11g dba 10489856 May 3 15:43 ora_sys_undo_BEajPSVq.dbf -rw-r--r-- 1 oracle11g dba 104861696 May 3 15:4 ora_system_BEaiFE8v.dbf -rw-r--r-- 1 oracle11g dba 186 May 3 15:03 PROD.ora ./EMP_INDEX: total 204808 -rw-r--r-- 1 oracle11g dba 104861696 May 3 15:43 ora_emp_inde_BEakGfun.dbf ./EMP_TABLE: total 204808 -rw-r--r-- 1 oracle11g dba 104861696 May 3 15:43 ora_emp_tabl_BEak1LqK.dbf