Veritas Storage Foundation for Oracle 5.
Legal Notices © Copyright 2008 Hewlett-Packard Development Company, L.P. Publication Date: 2008 Confidential computer software. Valid license from HP required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Contents Technical Support ............................................................................................... 4 Chapter 1 Introducing Veritas Storage Foundation for Oracle ............................................................................... 17 About Veritas Storage Foundation for Oracle .................................... Components of Veritas Storage Foundation for Oracle .................. How Veritas Volume Manager works ...............................................
8 Contents About restoring file systems using Storage Checkpoints ................ About quotas ......................................................................... About cluster functionality (optional) ........................................ How Veritas Storage Mapping works ............................................... How Veritas Database FlashSnap works ........................................... How Veritas Extension for Oracle Disk Manager works .......................
Contents Chapter 3 Managing the SFDB repository ......................................... 67 About the SFDB repository ............................................................. Runtime management tasks for the SFDB repository .......................... Starting, stopping, and checking the SFDB repository with sfua_db_config ................................................................ Backing up and restoring the SFDB repository with sfua_rept_adm ...................................................
10 Contents Collecting I/O statistics ......................................................... About I/O statistics ............................................................... Effects of read-aheads on I/O statistics ..................................... Other tools for analysis ......................................................... Enabling and disabling Cached Quick I/O for individual files .............. Setting cache advisories for individual files ...............................
Contents Obtaining Storage Mapping information for a list of tablespaces ................................................................... Oracle file mapping (ORAMAP) ..................................................... Mapping components ............................................................ Storage Mapping views .......................................................... Verifying Oracle file mapping setup ......................................... Enabling Oracle file mapping ...................
12 Contents Database Dynamic Storage Tiering command requirements ......... Defining database parameters ................................................ Setting up storage classes ...................................................... Converting a VxFS file system to a VxFS multi-volume file system .......................................................................... Classifying volumes into a storage class .................................... Displaying free space on your storage classes ..........
Contents One or two snapshot hosts ..................................................... Hosts and storage for Database FlashSnap ..................................... Single-host configuration ...................................................... Two-host or Oracle RAC configuration ..................................... Host and storage requirements ............................................... Creating a snapshot mirror of a volume or volume set used by the database ...................................
14 Contents About obtaining volume I/O statistics ...................................... About tuning VxFS ..................................................................... How monitoring free space works ............................................ How tuning VxFS I/O parameters works ................................... About tunable VxFS I/O parameters ......................................... About obtaining file I/O statistics using the Quick I/O interface .........................................
Contents Administering Storage Checkpoint quotas using dbed_ckptquota ............................................................. Performing Storage Rollback using dbed_ckptrollback ................ Removing Storage Checkpoints using dbed_ckptremove .............. Managing the Capacity Planning Utility using dbed_ckptplan ....... Cloning the Oracle instance using dbed_clonedb ........................ Creating and working with snapplans using dbed_vmchecksnap ..............................................
16 Contents About backing up and restoring Quick I/O files using Legato NetWorker .......................................................................... 377 About using backup software other than Veritas NetBackup to back up and restore ODM files ....................................................... 378 Appendix C Veritas Database FlashSnap status information ........ 379 Database FlashSnap snapshot status and database status .................. 379 Snapshot status details .........................
Chapter 1 Introducing Veritas Storage Foundation for Oracle This chapter includes the following topics: ■ About Veritas Storage Foundation for Oracle ■ How Veritas Volume Manager works ■ How Veritas File System works ■ How Veritas Storage Mapping works ■ How Veritas Database FlashSnap works ■ How Veritas Extension for Oracle Disk Manager works ■ How Database Dynamic Storage Tiering works ■ About the vxdbd daemon ■ About Veritas Storage Foundation for Oracle graphical user interface ■ Ab
18 Introducing Veritas Storage Foundation for Oracle About Veritas Storage Foundation for Oracle Note: Veritas Storage Foundation/High Availability (HA) for Oracle is available only with the Enterprise Edition. Unless otherwise noted, features pertain to both the Standard and Enterprise Edition products.
Introducing Veritas Storage Foundation for Oracle About Veritas Storage Foundation for Oracle ■ A feature of the Enterprise Edition, VxFS Storage Checkpoint technology lets you create a point-in-time image of a file system. Storage Checkpoints are treated like any other VxFS file system and can be created, mounted, unmounted, and removed with VxFS and Veritas Storage Foundation administrative utilities.
20 Introducing Veritas Storage Foundation for Oracle How Veritas Volume Manager works ■ Veritas Enterprise Administrator Veritas Enterprise Administrator (VEA) is the infrastructure that allows you to access Veritas Storage Foundation for Oracle, Veritas Volume Manager, and Veritas File System information and features through the GUI.
Introducing Veritas Storage Foundation for Oracle How Veritas Volume Manager works Table 1-1 Veritas Volume Manager features (continued) Feature Benefit Dirty Region Logging (DRL) Speeds the recovery of mirrored volumes after a system crash. SmartSync Recovery Accelerator Increases the availability of mirrored volumes by only resynchronizing changed data. Volume snapshots Allows backup of volumes based on disk mirroring.
22 Introducing Veritas Storage Foundation for Oracle How Veritas Volume Manager works Table 1-1 Veritas Volume Manager features (continued) Feature Benefit Veritas FlashSnap Agent for Symmetrix Separately licensed, optional feature that includes a set of commands that allows you to use EMC TimeFinder in conjunction with VxVM disk groups and volumes that have been created on Symmetrix standard devices.
Introducing Veritas Storage Foundation for Oracle How Veritas Volume Manager works About disk groups A disk group is a collection of disks that share a common configuration (for example, configuration objects that belong to a single database). We recommend creating one disk group for each database. You can move a disk group and its components as a unit from one host to another host.
24 Introducing Veritas Storage Foundation for Oracle How Veritas Volume Manager works in the first subdisk from beginning to end. Data is then accessed in the remaining subdisks sequentially from beginning to end, until the end of the last subdisk. You can use concatenation with multiple subdisks when there is insufficient contiguous space for the plex on any one disk. This form of concatenation can be used for load balancing between disks, and for head movement optimization on a particular disk.
Introducing Veritas Storage Foundation for Oracle How Veritas Volume Manager works provide redundancy of data. A volume can consist of up to 32 mirrors. Each of these mirrors must contain disk space from different disks for the redundancy to be effective. How striping plus mirroring (mirrored-stripe or RAID-0+1) works VxVM supports the combination of mirroring above striping. The combined layout is called a mirrored-stripe layout.
26 Introducing Veritas Storage Foundation for Oracle How Veritas Volume Manager works slow write performance. RAID-5 is useful if the database workload is read-intensive (as in many data warehousing applications). You can snapshot a RAID-5 volume and move a RAID-5 subdisk without losing redundancy. About online relayout As databases grow and usage patterns change, online relayout lets you change volumes to a different layout, with uninterrupted data access. Relayout is accomplished online and in place.
Introducing Veritas Storage Foundation for Oracle How Veritas Volume Manager works About dirty region logging Dirty region logging (DRL), if enabled, speeds the recovery of mirrored volumes after a system crash. DRL keeps track of the regions that have changed due to I/O writes to a mirrored volume. DRL uses this information to recover only those portions of the volume that need to be recovered.
28 Introducing Veritas Storage Foundation for Oracle How Veritas Volume Manager works ■ Space-optimized instant snapshots ■ Emulation of third-mirror snapshots See “About Veritas Database FlashSnap” on page 218. About Veritas FastResync Veritas FastResync (previously called Fast Mirror Resynchronization or FMR) is included with the Enterprise Edition. It is also included as part of the Veritas FlashSnap option with the Standard Edition.
Introducing Veritas Storage Foundation for Oracle How Veritas Volume Manager works FastResync maps on disk so that they can survive system reboots and system crashes. When the disk groups are rejoined, this allows the snapshot plexes to be quickly resynchronized. This ability is not supported by non-persistent FastResync. If persistent FastResync is enabled on a volume or on a snapshot volume, a DCO and a DCO log volume are associated with the volume.
30 Introducing Veritas Storage Foundation for Oracle How Veritas Volume Manager works the volume configuration for any possible performance impact. It is also a good idea to designate additional disks as spares to augment the spare pool. While a disk is designated as a spare, you cannot use the space on that disk for the creation of VxVM objects within its disk group. VxVM also lets you free a spare disk for general use by removing it from the pool of hot-relocation disks.
Introducing Veritas Storage Foundation for Oracle How Veritas File System works output is sent to the screen, but you can redirect it to a file using standard UNIX redirection. See the Veritas Volume Manager Administrator's Guide. About cluster functionality (optional) VxVM includes an optional, separately licensable clustering feature, known as Cluster Volume Manager, that enables VxVM to be used in a cluster environment. With the clustering option, VxVM supports up to 16 nodes per cluster.
32 Introducing Veritas Storage Foundation for Oracle How Veritas File System works See the Veritas File System Administrator's Guide. About Veritas Quick I/O Databases can run on either file systems or raw devices. Database administrators often create their databases on file systems because it makes common administrative tasks (such as moving, copying, and backing up) easier. However, running databases on most file systems significantly reduces database performance.
Introducing Veritas Storage Foundation for Oracle How Veritas File System works About extent-based allocation The HFS file system supplied with HP-UX uses block-based allocation schemes that provide good random access to files and acceptable latency on small files. For larger files, like database files, this block-based architecture limits throughput. This limitation makes the HFS file system a less than optimal choice for database environments.
34 Introducing Veritas Storage Foundation for Oracle How Veritas File System works How the defragmentation utility works Free resources are originally aligned in the most efficient order possible and are allocated to files in a way that is considered by the system to provide optimal performance. When a file system is active for extended periods of time, new files are created, old files are removed, and existing files grow and shrink.
Introducing Veritas Storage Foundation for Oracle How Veritas File System works Support for multi-volume file systems The multi-volume file system (MVS) feature allows several volumes to be represented by a single logical object. All I/O to and from an underlying logical volume is directed by way of volume sets. A volume set is a container for multiple different volumes. This feature can be used only in conjunction with Veritas Volume Manager.
36 Introducing Veritas Storage Foundation for Oracle How Veritas File System works Storage Checkpoints also keep track of the block change information that enables incremental database backup at the block level. Storage Checkpoints are writable, and can be created, mounted, and removed.
Introducing Veritas Storage Foundation for Oracle How Veritas Storage Mapping works You can use quotas to limit the amount of file system space used by Storage Checkpoints. With Veritas Storage Foundation for Oracle, you can enable, disable, set, and display quota values for a single file system, for multiple file systems, or for all file systems in a database using the dbed_ckptquota command. See “Administering Storage Checkpoint quotas using dbed_ckptquota” on page 326.
38 Introducing Veritas Storage Foundation for Oracle How Veritas Database FlashSnap works This command can help you avoid I/O contention. For example, you can use the information to avoid backing up two tablespaces that share the same physical disk. Both storage object statistics and the storage structure are displayed in the Veritas Storage Foundation for Oracle GUI. See “About Storage Mapping ” on page 133.
Introducing Veritas Storage Foundation for Oracle How Veritas Extension for Oracle Disk Manager works How Veritas Extension for Oracle Disk Manager works Veritas Extension for Oracle Disk Manager is a custom storage interface defined by Oracle Corporation first introduced in Oracle9. Oracle Disk Manager allows Oracle9 and above to exploit system bandwidth through an improved Application Programming Interface (API) that contains advanced kernel support for file I/O.
40 Introducing Veritas Storage Foundation for Oracle About the vxdbd daemon The DBA can also create a file relocation policy for database files, which would relocate files based on how frequently a file is used. See “About Database Dynamic Storage Tiering” on page 183. About the vxdbd daemon The vxdbd daemon handles communication to and from the Veritas Storage Foundation for Oracle software. By default, vxdbd communicates with Veritas Storage Foundation for Oracle over port number 3233.
Introducing Veritas Storage Foundation for Oracle About Veritas Storage Foundation for Oracle graphical user interface To stop the vxdbd daemon ◆ As root, use the vxdbdctrl stop command: /opt/VRTSdbcom/bin/vxdbdctrl stop To change the communications port used by the vxdbd daemon 1 As the root user, stop the vxdbd daemon: /opt/VRTSdbcom/bin/vxdbdctrl stop 2 In the /etc/vx/vxdbed/admin.
42 Introducing Veritas Storage Foundation for Oracle About Veritas NetBackup (optional) ■ Automate tasks, such as creating or cloning a database using a Storage Checkpoint, with the scheduler. (Java-based GUI only.) ■ Roll back databases, tablespaces, or datafiles to Storage Checkpoints. ■ Collect and display statistics on file system and Oracle space usage. ■ Collect and display storage object I/O statistics and the storage structure.
Introducing Veritas Storage Foundation for Oracle About Veritas Storage Foundation/High Availability for Oracle (optional) System (VxFS) available through Veritas Storage Foundation for Oracle. BLI Backup reduces both the time required to complete a database backup and the amount of data transferred during backups. It also allows more frequent backups, resulting in more up-to-date backup images.
44 Introducing Veritas Storage Foundation for Oracle About Veritas Storage Foundation/High Availability for Oracle (optional) Note: Veritas Storage Foundation/HA (VCS) for Oracle is available only for the Enterprise Edition.
Chapter 2 Setting up databases This chapter includes the following topics: ■ Tasks for setting up new databases ■ About setting up a disk group ■ Creating a disk group ■ Adding disks to a disk group ■ About selecting a volume layout ■ Creating a volume ■ Creating a volume set ■ Adding a volume to a volume set ■ File system creation guidelines ■ Creating a VxFS file system ■ Mounting a file system ■ Unmounting a file system ■ About fragmentation ■ Resizing a file system Tasks fo
46 Setting up databases Tasks for setting up new databases Determine the number and sizes of file See the Veritas File System Administrator's systems you need for the database you want Guide. to create. Create volumes to meet your file system ■ See “About selecting a volume layout” needs. You can use disk mirroring as a on page 50. safeguard against disk failures and striping ■ See “Creating a volume ” on page 52. for better performance. ■ See “About tuning VxVM ” on page 287.
Setting up databases About setting up a disk group If you are not currently running on VxVM and VxFS, make sure Veritas Storage Foundation for Oracle is installed and convert your existing database configuration. See the Veritas Storage Foundation for Oracle Installation Guide. For backup and recovery on the same host, See “About Storage Checkpoints and Storage you can use the Storage Checkpoint facility Rollback” on page 151. to create file system snapshots of the database.
48 Setting up databases Creating a disk group and a dg suffix. The dg suffix helps identify the object as a disk group. Also, each disk name must be unique within the disk group. ■ Never create database files using file systems or volumes that are not in the same disk group. In earlier releases of Veritas Volume Manager, a system installed with VxVM was configured with a default disk group, rootdg, that had to contain at least one disk.
Setting up databases Creating a disk group Usage notes Veritas Storage Foundation for Oracle only supports single disk groups. ■ Veritas Storage Foundation for Oracle RAC supports shared disk groups. If you are in an Oracle RAC environment: ■ ■ Create disk groups on the shared disks from the master node. To determine if a node is a master or slave, run the following command: vxdctl -c mode ■ RAID-5 volumes are not supported for sharing in a cluster.
50 Setting up databases Adding disks to a disk group # /opt/VRTS/bin/vxdg -s init PRODdg PRODdg01=c1t2d0 Adding disks to a disk group When a disk group is first created, it can contain only a single disk. You may need to add more disks to the disk group. Before adding disks, review the following: Usage notes When you place a disk under VxVM control, the disk is initialized. Initialization destroys any existing data on the disk.
Setting up databases About selecting a volume layout Disk I/O is one of the most important determining factors of your database's performance. Having a balanced I/O load usually means optimal performance. Designing a disk layout for the database objects to achieve balanced I/O is a crucial step in configuring a database. When deciding where to place tablespaces, it is often difficult to anticipate future usage patterns.
52 Setting up databases Creating a volume a high read ratio, however, RAID-5 performance is similar to that of a striped volume. Volume configuration guidelines Follow these guidelines when selecting volume layouts: ■ Put the database log files on a file system created on a striped and mirrored (RAID-0+1) volume separate from the index or data tablespaces. Stripe multiple devices to create larger volumes if needed. Use mirroring to improve reliability. Do not use VxVM RAID-5 for redo logs.
Setting up databases Creating a volume set After you decide on a volume layout, you can use the vxassist command to create the volume. Before creating a volume, make sure the following conditions are met: Usage notes Creating a volume requires a disk group name, volume name, volume size, and volume layout. You will also need to know subdisk names if you are creating a striped volume. ■ Striped or mirrored volumes require at least two disks.
54 Setting up databases Adding a volume to a volume set Usage notes Before creating a volume set, you must have at least one volume created. See “Creating a volume ” on page 52. ■ A maximum of 256 volumes may be configured in a volume set. ■ ■ Only Veritas File System is supported on a volume set. ■ The first volume in a volume set must be larger than 20MB. ■ Raw I/O from and to a volume set is not supported.
Setting up databases File system creation guidelines To add a volume to a volume set ◆ Use the vxvset command as follows: # /usr/sbin/vxvset [-g diskgroup] [-f] addvol volset \ volume Warning: The -f (force) option must be specified if the volume being added, or any volume in the volume set, is either a snapshot or the parent of a snapshot. Using this option can potentially cause inconsistencies in a snapshot hierarchy if any of the volumes involved in the operation is already in a snapshot chain.
56 Setting up databases Creating a VxFS file system It is possible to have a file system block size that is smaller than the database block size because the database block-size limit can be bigger than the file system block size. It is fine if the file system block size is smaller than the database block size because VxFS will not perform multiple I/O operations for each database I/O operation. VxFS is capable of performing I/Os with multiple blocks.
Setting up databases Creating a VxFS file system ■ size is the size of the new file system (optional) If you do not specify size, the file system will be as large as the underlying volume. For example, to create a VxFS file system that has an 8 KB block size and supports files larger than 2 GB on the newly created db01 volume: # /usr/sbin/mkfs -F vxfs -o largefiles,bsize=8192,\ logsize=2000 /dev/vx/rdsk/PRODdg/db01 The -o largefiles specific option allows you to create files larger than 2 GB.
58 Setting up databases Mounting a file system To enable large files on a file system that was created without the largefiles option ◆ Use the fsadm command as follows: # /opt/VRTS/bin/fsadm -F vxfs -o largefiles \ /mount_point Note: Make sure the applications and tools you use can handle large files before enabling the large file capability. Applications and system administration utilities can experience problems if they are not large file aware.
Setting up databases Unmounting a file system Usage notes ■ 59 The mount point must be an absolute path name (that is, it must begin with /). See the mount_vxfs (1M) manual page for more information about mount settings. ■ See the mount (1M) manual page for more information about generic mount options.
60 Setting up databases About fragmentation Before unmounting a file system, review the following: Prerequisites ■ A file system must exist and be mounted in order to be unmounted. Usage notes ■ You cannot unmount a file system that is in use. See the umount (1M) manual page for more information on mounting file systems.
Setting up databases About fragmentation On an active file system, the original order is lost over time as files are created, removed, or resized. As space is allocated and deallocated from files, the available free space becomes broken into fragments. This means that space must be assigned to files in smaller and smaller extents. This process is known as fragmentation. Fragmentation leads to degraded performance and availability. The degree of fragmentation depends on file system usage and activity.
62 Setting up databases About fragmentation ■ /opt/VRTS/bin/fsadm [-F vxfs] -o s, which prints the number of free extents of each size. Defragmenting a file system You can use the online administration utility fsadm to defragment or reorganize file system directories and extents. The fsadm utility defragments a file system mounted for read/write access by: ■ Removing unused space from directories. ■ Making all small files contiguous. ■ Consolidating free blocks for file system.
Setting up databases About fragmentation -t Specifies a maximum length of time to run, in seconds. Note: The -t and -p options control the amount of work performed by fsadm, either in a specified time or by a number of passes. By default, fsadm runs five passes. If both -t and -p are specified, fsadm exits if either of the terminating conditions are reached. -p Specifies a maximum number of passes to run. The default is five.
64 Setting up databases Resizing a file system To defragment a file system ◆ Run the fsadm command followed by the options specifying the type and amount of defragmentation. Complete the command by specifying the mount point or raw device to identify the file system.
Setting up databases Resizing a file system Prerequisites ■ This task requires a mounted file system. You must know either the desired size or the amount of space to add to or subtract from the file system size. Usage notes ■ See the (1M) manual page. See the fsadm_vxfs(1M) manual page.
66 Setting up databases Resizing a file system Prerequisites ■ You must know the new desired size of the file system. Usage notes ■ vxresize works with VxFS, JFS (derived from VxFS), and HFS file systems only. If the file system is mounted and Online JFS (full VxFS), you can grow or shrink the size. If the file system is mounted and either Base JFS (Lite VxFS) or HFS, you cannot grow or shrink the size.
Chapter 3 Managing the SFDB repository This chapter includes the following topics: ■ About the SFDB repository ■ Runtime management tasks for the SFDB repository ■ Adding a new system to an HA configuration ■ Reconfiguring virtual IP address for repository configuration ■ Accessing an off-host repository in a non-VCS environment About the SFDB repository The Storage Foundation for Databases (SFDB) repository stores metadata information required by Storage Foundation for Oracle software.
68 Managing the SFDB repository Runtime management tasks for the SFDB repository transaction log files, yymmddxx.log. VxDBMS supports remote client access from any host in the network that has proper authorization and configuration. SFDB requires only occasional interaction outside of the initial installation and configuration of Veritas Storage Foundation for Oracle. See the Veritas Storage Foundation Installation Guide for more information on configuring the SFDB repository.
Managing the SFDB repository Runtime management tasks for the SFDB repository ■ Create and configure a schedule for automatically backing up the SFDB repository, including specifying the type of backup (full or incremental), its start time and frequency, and the destination directory for the backed up files. ■ Restore the repository from backup files. ■ Disable or enable an existing backup schedule.
70 Managing the SFDB repository Runtime management tasks for the SFDB repository Table 3-1 sfua_rept_adm command options (continued) Option Description -o space_monitor_disable Disables the free-space monitoring schedule, if one exists. -t full | incr Specifies the type of backup schedule being created, enabled , or disabled by the accompanying -o option. Specify full for a full backup or incr for an incremental backup.
Managing the SFDB repository Runtime management tasks for the SFDB repository Table 3-1 sfua_rept_adm command options (continued) Option Description -u smtp_sender Specifies the SMTP sender in whose name the warning email is emailed when the repository file system free space falls below the threshold specified by the -w option.
72 Managing the SFDB repository Adding a new system to an HA configuration ■ Check the system console for error messages received at the time the backup was scheduled. ■ Verify the existence of the proper backup files in the backup directory (specified by -m backup_dest). The type of repository backup you schedule determines which files should be found in this directory. If an incremental backup, only repository transaction log files (yymmddxx.log) are created there.
Managing the SFDB repository Reconfiguring virtual IP address for repository configuration To add a new system to the SFDB repository 1 After installing Veritas Storage Foundation for Oracle, add the new system to the cluster. See the Veritas Cluster Server User's Guide.
74 Managing the SFDB repository Accessing an off-host repository in a non-VCS environment To change the virtual IP address for a cluster environment 1 Change the IP address for the cluster. 2 Update the IP address for the repository configuration in HA environment by running the following set of commands. 3 Unconfigure the SFUA repository. # /opt/VRTSdbcom/bin/sfua_db_config -o unconfig_cluster 4 Import the repository disk group. 5 Start the repository disk volume.
Chapter 4 Using Veritas Quick I/O This chapter includes the following topics: ■ About Quick I/O ■ Creating 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 A
76 Using Veritas Quick I/O About Quick I/O Note: Veritas recommends that you use Veritas Extension for Oracle Disk Manager. See “Setting up Veritas Extension for Oracle Disk Manager” on page 125. How Quick I/O works Veritas Quick I/O supports direct I/O and kernel asynchronous I/O and allows databases to access regular files on a VxFS file system as raw character devices. The benefits of using Quick I/O are: ■ Improved performance and processing throughput by having Quick I/O files act as raw devices.
Using Veritas Quick I/O About Quick I/O Supporting direct I/O I/O on files using read() and write() system calls typically results in data being copied twice: once between user and kernel space, and later between kernel space and disk. In contrast, I/O on raw devices is direct. That is, data is copied directly between user space and disk, saving one level of copying. As with I/O on raw devices, Quick I/O avoids extra copying.
78 Using Veritas Quick I/O About Quick I/O contiguous space on the file system, the file is created as a series of direct extents. Accessing a file using direct extents is inherently faster than accessing the same data using indirect extents. Internal tests have shown performance degradation in OLTP throughput when using indirect extent access. In addition, this type of preallocation causes no fragmentation of the file system.
Using Veritas Quick I/O Creating database files as Quick I/O files using qiomkfile Depending on whether you are creating a new database or are converting an existing database to use Quick I/O, you have the following options: If you are creating a new database: ■ You can use the qiomkfile command to preallocate space for database files and make them accessible to the Quick I/O interface. See “Creating database files as Quick I/O files using qiomkfile” on page 79.
80 Using Veritas Quick I/O Creating database files as Quick I/O files using qiomkfile -a Creates a symbolic link with an absolute path name for a specified file. Use the -a option when absolute path names are required. However, the default is to create a symbolic link with a relative path name. -e Extends a file by a specified amount to allow Oracle tablespace resizing. See “Extending a Quick I/O file” on page 94. -h Specifies the Oracle datafile header size.
Using Veritas Quick I/O Preallocating space for Quick I/O files using the setext command To create a database file as a Quick I/O file using qiomkfile 1 Create a database file using the qiomkfile command: $ /opt/VRTS/bin/qiomkfile -h headersize -s file_size /mount_point/filename 2 Create tablespaces on this file using SQL*Plus statements. For example: $ sqlplus /nolog SQL> connect / as sysdba SQL> create tablespace ts1 datafile '/mount_point/filename.
82 Using Veritas Quick I/O Preallocating space for Quick I/O files using the setext command Before preallocating space with setext, make sure the following conditions have been met: Prerequisites ■ The setext command requires superuser (root) privileges. Usage notes ■ You can use the chown command to change the owner and group permissions on the file after you create it. See the setext (1M) manual page for more information.
Using Veritas Quick I/O Accessing regular VxFS files as Quick I/O files Accessing regular VxFS files as Quick I/O files You can access regular VxFS files as Quick I/O files using the ::cdev:vxfs: name extension. While symbolic links are recommended because they provide easy file system management and location transparency of database files, the drawback of using symbolic links is that you must manage two sets of files (for instance, during database backup and restore).
84 Using Veritas Quick I/O Converting Oracle files to Quick I/O files To access an existing regular file as a Quick I/O file on a VxFS file system 1 Access the VxFS file system mount point containing the regular files: $ cd /mount_point 2 Create the symbolic link: $ mv filename .filename $ ln -s .filename::cdev:vxfs: filename This example shows how to access the VxFS file dbfile as a Quick I/O file: $ cd /db01 $ mv dbfile .dbfile $ ln -s .
Using Veritas Quick I/O Converting Oracle files to Quick I/O files Prerequisites ■ Log in as the Database Administrator (typically, the user ID oracle) to run the qio_getdbfiles and qio_convertdbfiles commands. ■ You must predefine the Oracle environment variable $ORACLE_SID. Change to the ORACLE_SID environment variable must be defined.
86 Using Veritas Quick I/O Converting Oracle files to Quick I/O files -a Lets you include all datafiles, including those that are potentially sparse. (Use this option only for debugging purposes, as sparse files are not candidates for use with Quick I/O.) -T Lets you specify the type of database as ora.
Using Veritas Quick I/O Converting Oracle files to Quick I/O files To extract a list of Oracle files to convert ◆ With the database instance up and running, run the qio_getdbfiles command from a directory for which you have write permission: $ cd /extract_directory $ /opt/VRTSdbed/bin/qio_getdbfiles -T ora The qio_getdbfiles command extracts the list file names from the database system tables and stores the file names and their size in bytes in a file called mkqio.dat under the current directory.
88 Using Veritas Quick I/O Converting Oracle files to Quick I/O files To convert the Oracle database files to Quick I/O files 1 Shut down the database. 2 Run the qio_convertdbfiles command from the directory containing the mkqio.dat file: $ cd /extract_directory $ /opt/VRTSdbed/bin/qio_convertdbfiles The list of files in the mkqio.dat file is displayed. For example: file1 file2 file3 file4 file5 --> --> --> --> --> .file1::cdev:vxfs: .file2::cdev:vxfs: .file3::cdev:vxfs: .file4::cdev:vxfs: .
Using Veritas Quick I/O About sparse files To undo the previous run of qio_convertdbfiles and change Quick I/O files back to regular VxFS files 1 If the database is running, shut it down. 2 Run the following command from the directory containing the mkqio.dat file: $ cd /extract_directory $ /opt/VRTSdbed/bin/qio_convertdbfiles -u The list of Quick I/O files in the mkqio.dat file is displayed. For example: .file1::cdev:vxfs: .file2::cdev:vxfs: .file3::cdev:vxfs: .file4::cdev:vxfs: .
90 Using Veritas Quick I/O Handling Oracle temporary tablespaces and Quick I/O So a 1TB file system can potentially store up to 2TB worth of files if there are sufficient blocks containing zeroes. Quick I/O files cannot be sparse and will always have all blocks specified allocated to them. Handling Oracle temporary tablespaces and Quick I/O You can create a new temporary tablespace using Quick I/O files.
Using Veritas Quick I/O Handling Oracle temporary tablespaces and Quick I/O To drop an existing temporary tablespace and recreate using Quick I/O files 1 Drop the temporary tablespace, including its contents: $ sqlplus /nolog SQL> connect / as sysdba; SQL> drop tablespace tablespace_name including contents; 2 Create a Quick I/O file on a VxFS file system: $ /opt/VRTS/bin/qiomkfile -h header_size -s size \ /mount_point/filename.
92 Using Veritas Quick I/O Displaying Quick I/O status and file attributes size 100M reuse \ temporary; Tablespace created. This example shows how to drop tablespace tempts, create a Quick I/O file temp01.dbf, and then create a new temporary tablespace tempts using the create temporary tablespace command: $ sqlplus /nolog SQL> connect / as sysdba; SQL> drop tablespace tempts including contents; Tablespace dropped. $ /opt/VRTS/bin/qiomkfile -h 32k -s 100M /db01/temp01.
Using Veritas Quick I/O Displaying Quick I/O status and file attributes 93 To list all files on the current file system, including Quick I/O files and their links ◆ Use the ls -al command with the file names: $ ls -al filename .filename The following example shows how to use the -a option to display the absolute path name created using qiomkfile: $ ls -al d* .d* -rw-r--r-- 1 oracle dba lrwxrwxrwx 1 oracle .dbfile::cdev:vxfs: dba 104890368 19 Oct 2 13:42 .
94 Using Veritas Quick I/O Extending a Quick I/O file Extending a Quick I/O file Although Quick I/O files must be preallocated, they are not limited to the preallocated sizes. You can grow or “extend” a Quick I/O file by a specific amount or to a specific size, using options to the qiomkfile command. Extending Quick I/O files is a fast, online operation and offers a significant advantage over using raw devices.
Using Veritas Quick I/O Using Oracle's AUTOEXTEND with Quick I/O files ■ 2 is the file system's mount point Extend the Quick I/O file using the qiomkfile command: $ /opt/VRTS/bin/qiomkfile -e extend_amount /mount_point/filename or $ /opt/VRTS/bin/qiomkfile -r newsize /mount_point/filename An example to show how to grow VxFS file system /db01 to 500MB and extend the emp.dbf Quick I/O file by 20MB: # /opt/VRTS/bin/fsadm -b 500M /db01 $ /opt/VRTS/bin/qiomkfile -e 20M /db01/emp.
96 Using Veritas Quick I/O Using Oracle's AUTOEXTEND with Quick I/O files For Quick I/O files or raw devices, AUTOEXTEND does not know how to grow the underlying Quick I/O files or devices. Therefore, the Quick I/O file size must be large enough to accommodate the new size before AUTOEXTEND can grow the datafile. You can use AUTOEXTEND with Quick I/O files in the following ways: ■ Preallocate the Quick I/O file to a size at least as big as the maximum growth size expected for this database file.
Using Veritas Quick I/O Recreating Quick I/O files after restoring a database To extend a Quick I/O file using qiomkfile ◆ If the datafile is running low on free blocks, use the qiomkfile command to extend the Quick I/O file: $ /opt/VRTS/bin/qiomkfile -e extend_amount \ /mount_point/filename The following example shows how to monitor the free space on the tablespace EMP on file system /db01: $ sqlplus /nolog SQL> connect / as sysdba; SQL> select * from dba_free_space where tablespace_name = ’EMP’; SQL> e
98 Using Veritas Quick I/O Disabling Quick I/O Usage notes The qio_recreate command supports only conventional Quick I/O files. ■ Refer to the qio_recreate(1M) manual page for more information. ■ To recreate Quick I/O files after recovering a database ◆ Use the qio_recreate command as follows: # /opt/VRTSdbed/bin/qio_recreate You will not see any output if the command is successful. When you run the qio_recreate command, the following actions occur: If... Then...
Using Veritas Quick I/O Disabling Quick I/O To disable Quick I/O 1 If the database is running, shut it down. 2 To change Quick I/O files back to regular VxFS files, run the following command from the directory containing the mkqio.dat list: $ /opt/VRTSdbed/bin/qio_convertdbfiles -u The list of Quick I/O files in the mkqio.dat file is displayed. For example: .file1::cdev:vxfs: .file2::cdev:vxfs: .file3::cdev:vxfs: .file4::cdev:vxfs: .
100 Using Veritas Quick I/O Disabling Quick I/O
Chapter 5 Using Veritas Cached Quick I/O This chapter includes the following topics: ■ About Cached Quick I/O ■ Enabling Cached Quick I/O on a file system ■ Determining candidates for Cached Quick I/O ■ Enabling and disabling Cached Quick I/O for individual files About Cached Quick I/O Veritas Cached Quick I/O maintains and extends the database performance benefits of Veritas Quick I/O by making more efficient use of large, unused system memory through a selective buffering mechanism.
102 Using Veritas Cached Quick I/O About Cached Quick I/O For example, consider a system configured with 12GB of physical memory, an operating system using 1GB, and a total Oracle size of 3.5GB. Unless you have other applications running on your system, the remaining 7.5GB of memory is unused. If you enable Cached Quick I/O, these remaining 7.5GB become available for caching database files. Note: You cannot allocate specific amounts of the available memory to Cached Quick I/O.
Using Veritas Cached Quick I/O Enabling Cached Quick I/O on a file system speeds up system reads by accessing the system buffer cache and avoiding disk I/O when searching for information. Having data at the cache level improves database performance in the following ways: ■ For read operations, Cached Quick I/O caches database blocks in the system buffer cache, which can reduce the number of physical I/O operations and therefore improve read performance.
104 Using Veritas Cached Quick I/O Enabling Cached Quick I/O on a file system Prerequisites ■ You must have permission to change file system behavior using the vxtunefs command to enable or disable Cached Quick I/O. By default, you need superuser (root) permissions to run the vxtunefs command, but other system users do not. Superuser (root) must specifically grant database administrators permission to use this command as follows: # chown root:dba /sbin/fs/vxfs4.1/vxtunefs # chmod 4550 /sbin/fs/vxfs4.
Using Veritas Cached Quick I/O Enabling Cached Quick I/O on a file system 105 To enable the qio_cache_enable flag for a file system ◆ Use the vxtunefs command as follows: # /sbin/fs/vxfs4.1/vxtunefs -s -o qio_cache_enable=1 / mount_point For example: # /sbin/fs/vxfs4.1/vxtunefs -s -o qio_cache_enable=1 /db02 where /db02 is a VxFS file system containing the Quick I/O files and setting the qio_cache_enable flag to “1” enables Cached Quick I/O.
106 Using Veritas Cached Quick I/O Enabling Cached Quick I/O on a file system ■ volname is the name of the volume For example: /dev/vx/dsk/PRODdg/db01 qio_cache_enable=1 /dev/vx/dsk/PRODdg/db02 qio_cache_enable=1 where /dev/vx/dsk/PRODdg/db01 is the block device on which the file system resides. The tunefstab (4) manual pages contain information on how to add tuning parameters. See the tunefstab (4) manual page.
Using Veritas Cached Quick I/O Determining candidates for Cached Quick I/O For example: # /opt/VRTS/bin/vxtunefs /db01 The vxtunefs command displays output similar to the following: Filesystem i/o parameters for /db01 read_pref_io = 65536 read_nstream = 1 read_unit_io = 65536 write_pref_io = 65536 write_nstream = 1 write_unit_io = 65536 pref_strength = 10 buf_breakup_size = 1048576 discovered_direct_iosz = 262144 max_direct_iosz = 1048576 default_indir_size = 8192 qio_cache_enable = 1 write_throttle = 0 m
108 Using Veritas Cached Quick I/O Determining candidates for Cached Quick I/O Before determining candidate files for Quick I/O, make sure the following conditions have been met: Prerequisites ■ You must enable Cached Quick I/O for the file systems. See “Enabling Cached Quick I/O on a file system” on page 103. Usage notes ■ See the qiostat (1M) manual page for more information.
Using Veritas Cached Quick I/O Determining candidates for Cached Quick I/O The second line of information is defined as follows: ■ CREAD is the number of reads from the VxFS cache (or total number of reads to Quick I/O files with cache advisory on) ■ PREAD is the number of reads going to the disk for Quick I/O files with the cache advisory on ■ HIT RATIO is displayed as a percentage and is the number of CREADS minus the number of PREADS times 100 divided by the total number of CREADS.
110 Using Veritas Cached Quick I/O Determining candidates for Cached Quick I/O Using the sample output above as an example, the file /db01/system.dbf does not benefit from the caching because the cache-hit ratio is zero. In addition, the file receives very little I/O during the sampling duration. However, the file /db01/stk.dbf has a cache-hit ratio of 21.6 percent.
Using Veritas Cached Quick I/O Enabling and disabling Cached Quick I/O for individual files benchmark test in which Cached Quick I/O was enabled for a certain set of data files resulted in improved performance, you can also use those results as the basis for enabling Cached Quick I/O.
112 Using Veritas Cached Quick I/O Enabling and disabling Cached Quick I/O for individual files To enable Cached Quick I/O for an individual file ◆ Use the qioadmin command to set the cache advisory to ON as follows: $ /opt/VRTS/bin/qioadmin -S filename=ON /mount_point For example, running qiostatshows the cache hit ratio for the file /db01/system.dbfreaches a level that would benefit from caching. To enable Cached Quick I/O for the file /db01/system.
Using Veritas Cached Quick I/O Enabling and disabling Cached Quick I/O for individual files To enable or disable individual file settings for Cached Quick I/O automatically after a reboot or mount ◆ Add cache advisory entries in the /etc/vx/qioadmin file as follows: device=/dev/vx/dsk// filename,OFF filename,OFF filename,OFF filename,ON For example, to make the Cached Quick I/O settings for individual files in the /db01 file system persistent, edit the /etc/vx/qioadmin file similar to
114 Using Veritas Cached Quick I/O Enabling and disabling Cached Quick I/O for individual files To display the current cache advisory settings for a file ◆ Use the qioadmin command with the -P option as follows: $ /opt/VRTS/bin/qioadmin -P filename /mount_point For example, to display the current cache advisory setting for the file cust.dbfin the /db01file system: $ /opt/VRTS/bin/qioadmin -P cust.dbf /db01 cust.
Chapter 6 Using Veritas Concurrent I/O This chapter includes the following topics: ■ About Concurrent I/O ■ Enabling and disabling Concurrent I/O About Concurrent I/O Veritas Concurrent I/O improves the performance of regular files on a VxFS file system without the need for extending namespaces and presenting the files as devices. This simplifies administrative tasks and allows databases, which do not have a sequential read/write requirement, to access files concurrently.
116 Using Veritas Concurrent I/O Enabling and disabling Concurrent I/O How Concurrent I/O works Traditionally, UNIX semantics require that read and write operations on a file occur in a serialized order. Because of this, a file system must enforce strict ordering of overlapping read and write operations. However, databases do not usually require this level of control and implement concurrency control internally, without using a file system for order enforcement.
Using Veritas Concurrent I/O Enabling and disabling Concurrent I/O 117 Enabling Concurrent I/O Because you do not need to extend name spaces and present the files as devices, you can enable Concurrent I/O on regular files. Before enabling Concurrent I/O, review the following: Prerequisites ■ To use the Concurrent I/O feature, the file system must be a VxFS file system. ■ Make sure the mount point on which you plan to mount the file system exists. ■ Make sure the DBA can access the mount point.
118 Using Veritas Concurrent I/O Enabling and disabling Concurrent I/O For example, to mount a file system named /datavolon a mount point named /oradata: # /usr/sbin/mount -F vxfs -o cio /dev/vx/dsk/oradg/datavol \ /oradata Disabling Concurrent I/O If you need to disable Concurrent I/O, unmount the VxFS file system and mount it again without the mount option. To disable Concurrent I/O on a file system using the mount command 1 Shutdown the Oracle instance.
Chapter 7 Using Veritas Extension for Oracle Disk Manager This chapter includes the following topics: ■ About Oracle Disk Manager ■ About Oracle Disk Manager and Oracle Managed Files ■ Setting up Veritas Extension for Oracle Disk Manager ■ How to prepare existing database storage for Oracle Disk Manager ■ Converting Quick I/O files to Oracle Disk Manager files ■ Verifying that Oracle Disk Manager is configured ■ Disabling the Oracle Disk Manager feature About Oracle Disk Manager Veritas Exte
120 Using Veritas Extension for Oracle Disk Manager About Oracle Disk Manager Oracle Disk Manager reduces administrative overhead by providing enhanced support for Oracle Managed Files. Veritas Extension for Oracle Disk Manager has Quick I/O-like capabilities, but is transparent to the user. Unlike Veritas Quick I/O, files managed using Veritas Extension for Oracle Disk Manager do not require special file naming conventions. The Oracle Disk Manager interface uses regular database files.
Using Veritas Extension for Oracle Disk Manager About Oracle Disk Manager ■ Supporting kernel asynchronous I/O ■ Supporting direct I/O and avoiding double buffering ■ Avoiding kernel write locks on database files ■ Supporting many concurrent I/Os in one system call ■ Avoiding duplicate opening of files per Oracle instance ■ Allocating contiguous datafiles About kernel asynchronous I/O support Asynchronous I/O performs non-blocking system level reads and writes, allowing the system to perform mu
122 Using Veritas Extension for Oracle Disk Manager About Oracle Disk Manager and Oracle Managed Files can be accomplished with one system call when Oracle uses the Oracle Disk Manager I/O interface. This interface reduces the number of system calls performed to accomplish the same work, reducing the number of user space/kernel space context switches. About avoiding duplicate file opens Oracle Disk Manager allows files to be opened once, providing a “file identifier.
Using Veritas Extension for Oracle Disk Manager About Oracle Disk Manager and Oracle Managed Files By default, OMF datafiles are created with auto-extend capability. This attribute reduces capacity planning associated with maintaining existing databases and implementing new applications. Due to disk fragmentation that occurs as the tablespace grows over time, database administrators have been somewhat cautious when considering auto-extensible tablespaces. Oracle Disk Manager eliminates this concern.
124 Using Veritas Extension for Oracle Disk Manager About Oracle Disk Manager and Oracle Managed Files 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.
Using Veritas Extension for Oracle Disk Manager Setting up Veritas Extension for Oracle Disk Manager -rw-r--r--rw-r--r--rw-r--r--rw-r--r-- 1 1 1 1 oracle9i oracle9i oracle9i oracle9i dba dba dba dba 806912 May 3 15:43 ora_BEahlfUX.ctl 10489856 May 3 15:43 ora_sys_undo_BEajPSVq.dbf 104861696 May 3 15:4 ora_system_BEaiFE8v.dbf 186 May 3 15:03 PROD.ora ./EMP_INDEX: total 204808 -rw-r--r-- 1 oracle9i dba 104861696 May 3 15:43 ora_emp_inde_BEakGfun.dbf .
126 Using Veritas Extension for Oracle Disk Manager Setting up Veritas Extension for Oracle Disk Manager Linking the Veritas extension for Oracle Disk Manager library into Oracle home You must use the following procedures to link the Veritas extension for Oracle Disk Manager library into Oracle home for Oracle 11g, Oracle 10g, and Oracle 9i. To link the Veritas extension for Oracle Disk Manager library into Oracle home for Oracle 11g ◆ Use the mv and ln commands as follows.
Using Veritas Extension for Oracle Disk Manager How to prepare existing database storage for Oracle Disk Manager To link the Veritas extension for Oracle Disk Manager library into Oracle home for Oracle9i ◆ Use the mv and ln commands as follows. For HP-UX PA, enter: # mv ${ORACLE_HOME}/lib/libodm9.sl \ ${ORACLE_HOME}/lib/libodm9.sl.orig # ln -s /opt/VRTSodm/lib/libodm.sl \ ${ORACLE_HOME}/lib/libodm9.sl For HP-UX IA, enter: # mv ${ORACLE_HOME}/lib/libodm9.so \ ${ORACLE_HOME}/lib/libodm9.so.
128 Using Veritas Extension for Oracle Disk Manager Converting Quick I/O files to Oracle Disk Manager files Converting Quick I/O files to Oracle Disk Manager files If you plan to run Veritas Storage Foundation for Oracle with Oracle9i or later, and you have been using Quick I/O files, it is recommended that you convert your Quick I/O files to regular files. This should be done after you upgrade Veritas Storage Foundation for Oracle. Note: If you are running an earlier version of Oracle (Oracle 8.
Using Veritas Extension for Oracle Disk Manager Verifying that Oracle Disk Manager is configured Prerequisites ■ /opt/VRTSodm/lib/libodm.sl must exist. ■ If you are using Oracle9i, $ORACLE_HOME/lib/libodm9.sl is linked to /opt/VRTSodm/lib/libodm.sl. ■ If you are using Oracle 10g, $ORACLE_HOME/lib/libodm10.sl is linked to /opt/VRTSodm/lib/libodm.sl. ■ The VRTSdbed license must be valid. ■ The VRTSodm package must be installed.
130 Using Veritas Extension for Oracle Disk Manager Disabling the Oracle Disk Manager feature To verify that Oracle Disk Manager is running 1 Start the Oracle database. 2 Check that the instance is using the Oracle Disk Manager function: # cat /dev/odm/stats # echo $? 0 3 Verify that the Oracle Disk Manager is loaded: # /usr/sbin/kcmodule -P state odm state loaded 4 In the alert log, verify the Oracle instance is running.
Using Veritas Extension for Oracle Disk Manager Disabling the Oracle Disk Manager feature To disable the Oracle Disk Manager feature in an Oracle instance 1 Shut down the database instance. 2 Use the rm and the ln commands to remove the link to the Oracle Disk Manager Library as follows: For Oracle 11g, enter: # rm ${ORACLE_HOME}/lib/limodm11.sl # ln -s ${ORACLE_HOME}/lib/libodm11.sl \ ${ORACLE_HOME}/lib/libodm11.sl For Oracle 10g, enter: # rm ${ORACLE_HOME}/lib/limodm10.
132 Using Veritas Extension for Oracle Disk Manager Disabling the Oracle Disk Manager feature
Chapter 8 Using Storage Mapping This chapter includes the following topics: ■ About Storage Mapping ■ Verifying Veritas Storage Mapping setup ■ Using vxstorage_stats ■ Using dbed_analyzer ■ Oracle file mapping (ORAMAP) About Storage Mapping Storage mapping is included with Veritas Storage Foundation for Oracle Enterprise Edition. Storage mapping enables you to map datafiles, tablespaces, and tables to physical devices.
134 Using Storage Mapping Verifying Veritas Storage Mapping setup Mapping Service (VxMS), a library that assists in the development of distributed SAN applications that must share information about the physical location of files and volumes on a disk. The Veritas Storage Mapping option supports Oracle's set of storage APIs called Oracle Mapping (“ORAMAP” for short) that lets Oracle determine the mapping information for files and devices.
Using Storage Mapping Using vxstorage_stats To verify that your system is using the Veritas Storage Mapping option 1 Verify that you have a license key for the Storage Mapping option. # /opt/VRTS/bin/vxlictest -n "VERITAS Mapping Services" -f \ "Found_Edi_map" Found_Edi_map feature is licensed 2 Verify that the VRTSvxmsa package is installed. # swlist VRTSvxmsa # VRTSvxmsa VRTSvxmsa.admin VRTSvxmsa.libraries VRTSvxmsa.logging VRTSvxmsa.plugins 2.1-REV=2002.08.
136 Using Storage Mapping Using vxstorage_stats Usage notes ■ The -s option displays the file statistics for the specified file. ■ The -c count option specifies the number of times to display statistics within the interval specified by -i interval. The -i interval option specifies the interval frequency for displaying updated I/O statistics. ■ The -f filename option specifies the file to display I/O mapping and statistics for. ■ For more information, see the vxstorage_stats(1m) online manual page.
Using Storage Mapping Using vxstorage_stats TY NAME NSUB DESCRIPTION fi /oradata/system01.
138 Using Storage Mapping Using vxstorage_stats To display I/O statistics information ◆ Use the vxstorage_stats command with the -s option: $ /opt/VRTSdbed/bin/vxstorage_stats -s -f file_name For example: $ /opt/VRTSdbed/bin/vxstorage_stats -s -f \ /data/system01.dbf Output similar to the following is displayed: I/O OPERATIONS I/O BLOCKS(512 byte) AVG TIME(ms) OBJECT WRITE AVG_RD READ B_READ B_WRITE 2479 8 5068810 AVG_WR /data/system01.dbf 2 0.
Using Storage Mapping Using vxstorage_stats To display Storage Mapping and I/O statistics information at repeated intervals 139
140 Using Storage Mapping Using vxstorage_stats ◆ Use the vxstorage_stats command with the -i interval and -c count options to display storage mapping and I/O statistics information at repeated intervals. The -i interval option specifies the interval frequency for displaying updated I/O statistics and the -c count option specifies the number of times to display statistics.
Using Storage Mapping Using dbed_analyzer EMC000184502242:32:0d:01 1 1336 8 190456 - - Using dbed_analyzer This release adds table-level mapping, with which for a given table dbed_analyzer lists the disks on which it resides and the space it occupies on each disk. Use the -o sort=table option to use this enhancement. Users previously could find which tablespace resides on which disk, but with table-level mapping a user can learn on which disk a heavily-used table resides.
142 Using Storage Mapping Using dbed_analyzer Usage notes ■ ■ ■ ■ ■ The -o sort=tbs option provides the layout of the specified tablespaces on the physical disk as well as the amount of disk space they are using. The -o sort=disk option provides the name of the disks containing the specified tablespaces as well as the amount of disk space the tablespaces are using. The -o sort=table option identifies the disk and the space occupied on it by the specified table or list of tables.
Using Storage Mapping Using dbed_analyzer ROLL_1 ROLL_2 ORDERS ORD_IDX QTY_IDX ITM_IDX ROLL_1 QTY_IDX ROLL_2 ITEM 143 /usr1/oracle/rw/DATA/roll_1_5000 c3t21000020379DBD5F /usr1/oracle/rw/DATA/roll_2_6000 c3t21000020379DBD5F /usr1/oracle/rw/DATA/orders_4000 c3t21000020379DBD5F /usr1/oracle/rw/DATA/ord_idx_10000 c3t21000020379DBD5 /usr1/oracle/rw/DATA/qty_idx_7001 c3t21000020379DB /usr1/oracle/rw/DATA/itm_idx_2001 c3t21000020379DB /usr1/oracle/rw/DATA/roll_1_5001 c3t21000020379DBD5 /usr1/oracle/rw/DATA/qty
144 Using Storage Mapping Oracle file mapping (ORAMAP) Oracle file mapping (ORAMAP) Veritas has defined and implemented two libraries: libvxoramap_64.so for HPUX PA and libvxoramap_64.sl for HPUX IA architecture. These two libraries provide a mapping interface to Oracle9 release 2 or later. The libvxoramap_64.
Using Storage Mapping Oracle file mapping (ORAMAP) This component contains information about the element's mapping structure, such as the element's size, type, number of subelements, and a brief description. Element components are exported to the user through V$MAP_ELEMENT. ■ Subelement components A mapping subelement component describes the link between an element and the next element in the I/O stack.
146 Using Storage Mapping Oracle file mapping (ORAMAP) Table 8-1 Storage mapping information in Oracle dynamic performamce views (continued) View Description V$MAP_FILE_IO_STACK Contains the hierarchical arrangement of storage containers for the file. This information is displayed as a series of rows. Each row represents a level in the hierarchy. Verifying Oracle file mapping setup Before you enable Oracle file mapping, verify that $ORACLE_HOME and ORCLfmap directories are properly set up.
Using Storage Mapping Oracle file mapping (ORAMAP) To enable Oracle file mapping with the Veritas Storage Mapping option 1 Ensure that the file filemap.ora exists and contains a valid entry for the Veritas mapping library for Oracle file mapping. # cd $ORACLE_HOME/rdbms/filemap/etc # cat filemap.ora For 64-bit Oracle, the filemap.ora file should contain the following setting: lib=Veritas:/opt/VRTSdbed/lib/libvxoramap_64.so lib=Veritas:/opt/VRTSdbed/lib/libvxoramap_64.
148 Using Storage Mapping Oracle file mapping (ORAMAP) To access dynamic performance views 1 Confirm that the Veritas mapping library for Oracle file mapping has been enabled. SQL> select lib_idx idx, lib_name name, vendor_name vname, \ path_name path from v$map_library; 2 After file mapping has been enabled, Oracle datafiles can be mapped using the DBMS_STORAGE_MAP package. For example, this shows how to map a datafile using SQL: SQL> execute dbms_storage_map.map_file('/oracle/dbs/qio10m.
Using Storage Mapping Oracle file mapping (ORAMAP) From Oracle Enterprise Manager, you can view storage mapping information and a graphical display of the storage layout. Storage mapping information cannot be viewed with the Oracle 10g version of the Oracle Enterprise Manager client. However, the Oracle9i version of Oracle Enterprise Manager can be used with Oracle 10g to view storage mapping information. For more information about Oracle Enterprise Manager, refer to your Oracle documentation.
150 Using Storage Mapping Oracle file mapping (ORAMAP) 9 By default, storage layout information is displayed in a tabular format. That is, the Tabular Display icon is selected. To view a graphical display of the storage layout, click the Graphical Display icon. 10 Expand the objects to display their storage layout information graphically. 11 To exit, choose Exit from the File menu.
Chapter 9 Using Storage Checkpoints and Storage Rollback This chapter includes the following topics: ■ About Storage Checkpoints and Storage Rollback ■ Space requirements for Storage Checkpoints ■ Performance of Storage Checkpoints ■ Storage Checkpoint allocation policies ■ Backing up and recovering the database using Storage Checkpoints ■ Cloning the Oracle instance using dbed_clonedb ■ Guidelines for Oracle recovery ■ Using the GUI to perform Storage Checkpoint-related operations About S
152 Using Storage Checkpoints and Storage Rollback About Storage Checkpoints and Storage Rollback Storage Checkpoint image is managed and available through the GUI, or the Veritas Storage Foundation command line interface (CLI). Veritas NetBackup also makes use of Storage Checkpoints to provide a very efficient Oracle backup mechanism. See the Veritas Storage Foundation for Oracle Graphical User Interface Guide. A direct application of the Storage Checkpoint facility is Storage Rollback.
Using Storage Checkpoints and Storage Rollback Space requirements for Storage Checkpoints primary file system, and less and less of the block map in the Storage Checkpoint points back to blocks on the primary file system. You can set a quota to limit how much space a file system will give to all storage checkpoints, to prevent the checkpoints from consuming all free space. See the command dbed_ckptquota for more information.
154 Using Storage Checkpoints and Storage Rollback Space requirements for Storage Checkpoints that are used to keep track of the block changes contain only file system block maps, and therefore require very little additional space (less than 1 percent of the file system size). When you use Veritas NetBackup to back up your database, Veritas NetBackup creates one set of Storage Checkpoints to provide a consistent view of the file systems for the database backups.
Using Storage Checkpoints and Storage Rollback Performance of Storage Checkpoints If you are restoring some of the files in the file system, you should first remove the data-full Storage Checkpoints that are no longer needed. If you have very limited free space on the file system, you may have to remove all data-full Storage Checkpoints in order for the restore to succeed. Always reserve free disk space for growing volumes and file systems.
156 Using Storage Checkpoints and Storage Rollback Storage Checkpoint allocation policies file system over multiple volumes, each volume with properties of its own. This helps administrators specify which data goes on which volume types. For more details about MVS, see Veritas Volume Manager Administrator's Guide. Setting up a storage configuration for MVS operations is a system administrator's responsibility and requires superuser (root) privileges.
Using Storage Checkpoints and Storage Rollback Storage Checkpoint allocation policies Once the assigned policy is deleted, the allocation for metadata and file data for subsequent requests of storage checkpoint will return to the no policy assigned state. For VxFS file systems disk layout Version 7, the volumes on the VxFS Multi-Volume File System cvan be either one of these types: dataonly and metadataok. Only metadataok volumes can be used to store checkpoint metadata.
158 Using Storage Checkpoints and Storage Rollback Storage Checkpoint allocation policies See “Creating and working with Storage Checkpoint allocation policies using dbed_ckptpolicy” on page 323. Note: You cannot administer Storage Checkpoint allocation policies through the the GUI. The following are usage notes for the dbed_ckptpolicy and dbed_ckptcreate commands: Usage notes See the dbed_ckptpolicy(1M) and dbed_ckptcreate(1M) manual pages for more information.
Using Storage Checkpoints and Storage Rollback Storage Checkpoint allocation policies 159 To create a Storage Checkpoint allocation policy ◆ Use the dbed_ckptpolicy command as follows: $ /opt/VRTS/bin/dbed_ckptpolicy -S ORACLE_SID \ -o create -p ckpt_policy Note: A partial policy indicates that the Storage Checkpoint allocation policy does not include all the file systems used by the database.
160 Using Storage Checkpoints and Storage Rollback Storage Checkpoint allocation policies ■ Use the -p ckpt_data_policy[,ckpt_metadata_policy] option to the dbed_ckptcreate command to supply policies when executed. Note: The command automatically assigns the policies when the Storage Checkpoint is created. Note: You must run the db2ed_update command once before creating the checkpoint. The following procedure uses dbed_ckptpolicy to assign an allocation policy to an existing Storage Checkpoint.
Using Storage Checkpoints and Storage Rollback Storage Checkpoint allocation policies 161 To assign an allocation policy to a new Storage Checkpoint 1 Use dbed_ckpcreate to assign an allocation policy to a new Storage Checkpoint. $ dbed_ckptcreate -S PROD -H -o online \ -p ckpt_data,ckpt_metadata As a result, a Storage Checkpoint allocation policy is assigned to Checkpoint_1096060122, which is a new Storage Checkpoint.
162 Using Storage Checkpoints and Storage Rollback Storage Checkpoint allocation policies To display a Storage Checkpoint allocation policy ◆ Use the -o display option to list all the Storage Checkpoint allocation policies contained in the file systems used by the database.
Using Storage Checkpoints and Storage Rollback Storage Checkpoint allocation policies 163 To display the allocation policies assigned to a Storage Checkpoint ◆ Use the -o display -c checkpoint_xxxxxxxxx option to display the allocation policies assigned to the Storage Checkpoint.
164 Using Storage Checkpoints and Storage Rollback Storage Checkpoint allocation policies ckpt_sample /mvsfs/v2 mvsv5 ckpt_sample /mvsfs/v1 mvsv2,mvsv3 where mvsv4 is the volume currently using the allocation policy. The output displays the volumes that are currently assigned in the Storage Checkpoint allocation policy. You are prompted to enter any new volumes to which you would want to assign the Storage Checkpoint allocation policy.
Using Storage Checkpoints and Storage Rollback Backing up and recovering the database using Storage Checkpoints 4 Upgrade the volume set's file system to Version 6 disk layout: # vxupgrade -n 6 /mnt1 See the Veritas File System Installation Guide and the vxfsconvert(1M) and vxupgrade(1M) manual pages for information on upgrading VxFS disk layouts: 5 Add the new volume to the volume set: # vxvset -g dgname addvol myvset new_vol 6 Add the new volume to the file system.
166 Using Storage Checkpoints and Storage Rollback Backing up and recovering the database using Storage Checkpoints recovery. Rolling the database forward is not supported; that is, you cannot apply archived redo logs. Note: Storage Foundation for Oracle RAC configurations do not support rollbacks using instant Storage Checkpoint. To allow the easiest recovery, always keep ARCHIVELOG mode enabled, regardless of whether the database is online or offline when you create Storage Checkpoints.
Using Storage Checkpoints and Storage Rollback Backing up and recovering the database using Storage Checkpoints 167 To verify that a Storage Checkpoint is error-free using the command line 1 Create and mount a Storage Checkpoint: $ /opt/VRTS/bin/dbed_ckptcreate -S PROD -H /oracle/product \ -o online Storage Checkpoint Checkpoint_903937870 created.
168 Using Storage Checkpoints and Storage Rollback Backing up and recovering the database using Storage Checkpoints the dbed_ckptmount command, and then back it up using tools such as tar or cpio. The following are usage notes for backing up a database with the dbed_ckptcreate command: Usage notes ■ See the dbed_ckptcreate(1M), dbed_ckptmount(1M), tar(1), and cpio(1) manual pages for more information.
Using Storage Checkpoints and Storage Rollback Cloning the Oracle instance using dbed_clonedb 169 Note: Some database changes made after a Storage Checkpoint was taken may make it impossible to perform an incomplete recovery of the databases after Storage Rollback of an online or offline Storage Checkpoint using the current control files. For example, you cannot perform incomplete recovery of the database to the point right before the control files have recorded the addition or removal of datafiles.
170 Using Storage Checkpoints and Storage Rollback Cloning the Oracle instance using dbed_clonedb You have the option to manually or automatically recover the database when using the dbed_clonedb command: ■ Manual (interactive) recovery, which requires using the -i option, of the clone database allows the user to control the degree of recovery by specifying which archive log files are to be replayed.
Using Storage Checkpoints and Storage Rollback Cloning the Oracle instance using dbed_clonedb Table 9-1 dbed_clonedb command options (continued) Option Description -i Runs the command in interactive mode where you must respond to prompts by the system. The default mode is non-interactive. (Optional) -o umount Shuts down the clone database and unmounts the Storage Checkpoint file system. -o restartdb Mounts the Storage Checkpoint file system and starts the clone database.
172 Using Storage Checkpoints and Storage Rollback Cloning the Oracle instance using dbed_clonedb Control file 'ora_control2' path not explicitly specified in init file; assuming ORACLE_HOME/dbs All redo-log files found Copying initTEST9i.ora to initNEW9.ora in /local/oracle9/1/testvol Altering db_name in initNEW9.ora Altering control file locations in initNEW9.
Using Storage Checkpoints and Storage Rollback Cloning the Oracle instance using dbed_clonedb Resetting logs on new database NEW9 Database instance NEW9 is up and running To clone an Oracle instance with automatic Oracle recovery ◆ Use the dbed_clonedb command as follows: $ /opt/VRTS/bin/dbed_clonedb -S NEW9 -m /local/oracle9/1 \ -c Checkpoint_988813047 Primary Oracle SID is TEST9i New Oracle SID is NEW9 Checkpoint_988813047 not mounted at /local/oracle9/1 Mounting Checkpoint_988813047 at /loca
174 Using Storage Checkpoints and Storage Rollback Guidelines for Oracle recovery Database NEW9 is being reconfigured Starting automatic (full) database recovery Shutting down clone database Altering clone database archive log directory Updating log_archive_dest in clone database init file Found archive log destination at /testvol Mounting clone database Resetting logs on new database NEW9 Database instance NEW9 is up and running To shut down the clone database and unmount the Storage Checkpoint ◆ Use t
Using Storage Checkpoints and Storage Rollback Guidelines for Oracle recovery A control file is a small binary file that describes the structure of the database and must be available to mount, open, and maintain the database. The control file stores all necessary database files information, log file information, the name of the database, and the timestamp of database creation, as well as synchronization information such as Storage Checkpoint and log sequence information that is needed for recovery.
176 Using Storage Checkpoints and Storage Rollback Using the GUI to perform Storage Checkpoint-related operations ■ RECOVER DATABASE UNTIL TIME \ ’yyyy-mm-dd:hh:mm:ss’ using backup controlfile; ■ RECOVER DATABASE UNTIL CHANGE scn; To open the database after an incomplete media recovery, use the following: ◆ ALTER DATABASE OPEN RESETLOGS; RESETLOGS resets the log sequence. The RESETLOGS option is required after an incomplete media recovery.
Chapter 10 Converting existing database configurations to VxFS This chapter includes the following topics: ■ About converting LVM volume groups to VxVM disk groups ■ Converting native file systems to VxFS for Oracle Disk Manager ■ Converting native file systems to VxFS with Quick I/O ■ Upgrading from earlier VxFS version layouts ■ Converting from raw devices About converting LVM volume groups to VxVM disk groups If you are currently using VxFS file systems for your database and the file systems
178 Converting existing database configurations to VxFS Converting native file systems to VxFS for Oracle Disk Manager Note: As is customary before performing any kind of conversion or upgrade, back up your database and LVM configuration information before converting LVM volume groups to VxVM disk groups. For detailed information on converting LVM volume groups, you must refer to the volume manager migration guide. See the Veritas Volume Manager Migration Guide.
Converting existing database configurations to VxFS Converting native file systems to VxFS with Quick I/O 7 Restore the backup created in step 2 to the new VxFS file system. 8 Restart the database. Converting native file systems to VxFS with Quick I/O If you are currently using file systems native to your operating system, use the procedure to upgrade each file system used by the database to a VxFS file system with Quick I/O.
180 Converting existing database configurations to VxFS Converting from raw devices Usage notes ■ The vxupgrade command lets you to upgrade the VxFS file system disk layout while the file system is mounted. See the vxupgrade(1M) manual page for more details. ■ VxFS supports four file system disk layouts: Versions 4, 5, 6, and 7.
Converting existing database configurations to VxFS Converting from raw devices To convert from raw devices to VxFS with Quick I/O 1 Create a VxFS file system using a size that is 10 percent larger than the original database or total raw device size. You can create more file systems based on your performance and availability requirements. See “Creating a VxFS file system ” on page 56. 2 Shut down the database. 3 Preallocate Quick I/O files using qiomkfile.
182 Converting existing database configurations to VxFS Converting from raw devices To convert from raw devices to regular files for ODM 1 Create a VxFS file system using a size that is 10 percent larger than the original database or total raw device size. You can create more file systems based on your performance and availability requirements. See “Creating a VxFS file system ” on page 56. 2 Shut down the database. 3 Preallocate the files for ODM using odmmkfile.
Chapter 11 Using Database Dynamic Storage Tiering This chapter includes the following topics: ■ About Database Dynamic Storage Tiering ■ Configuring Database Dynamic Storage Tiering ■ Dynamic Storage Tiering policy management ■ Running Database Dynamic Storage Tiering reports ■ Extent balancing in a database environment ■ Database Dynamic Storage Tiering use cases for Oracle About Database Dynamic Storage Tiering More and more data is being retained.
184 Using Database Dynamic Storage Tiering About Database Dynamic Storage Tiering ■ Resilience class: Each class consists of non-mirrored volumes, mirrored volumes, and n-way mirrored volumes. For example, a database is usually made up of data, an index, and logs. The data could be set up with a three-way mirror because data is critical. The index could be set up with a two-way mirror because the index is important, but can be recreated.
Using Database Dynamic Storage Tiering About Database Dynamic Storage Tiering About VxVM volume sets Volume sets allow several volumes to be represented by a single logical object. Volume sets cannot be empty. All I/O from and to the underlying volumes is directed via the I/O interfaces of the volume set. The volume set feature supports the multi-volume enhancement to Veritas File System (VxFS).
186 Using Database Dynamic Storage Tiering Configuring Database Dynamic Storage Tiering of the StartVolumes and StopVolumes attributes are both 1, the DiskGroup agent onlines and offlines the volumes during the import and deport operations of the disk group. When using volume sets, set StartVolumes and StopVolumes attributes of the DiskGroup resource that contains the volume set to 1. If a file system is created on the volume set, use a Mount resource to mount the volume set.
Using Database Dynamic Storage Tiering Configuring Database Dynamic Storage Tiering Because the Database Dynamic Storage Tiering commands retrieve database information from the repository, the repository must be up to date.
188 Using Database Dynamic Storage Tiering Configuring Database Dynamic Storage Tiering Table 11-1 dbdst_admin command options (continued) Option Description list Lists all the Database Dynamic Storage Tiering parameters of the database, including class name and description. This option should be used exclusively from the other options. maxclass= Maximum number of storage classes allowed in the database. Default value is 4. minclass= Minimum number of storage classes allowed in the database.
Using Database Dynamic Storage Tiering Configuring Database Dynamic Storage Tiering 189 Note: If you do not want to change specific default values, you can omit those parameters when you run the dbdst_admin command. You only need to enter the parameters that need to be changed.
190 Using Database Dynamic Storage Tiering Configuring Database Dynamic Storage Tiering Removing storage classes If you no longer require a specific storage class, you can remove it. You cannot remove the pre-defined storage classes (PRIMARY, SECONDARY, and BALANCE).
Using Database Dynamic Storage Tiering Configuring Database Dynamic Storage Tiering Prerequisites Usage notes ■ The Oracle database must not be active. ■ Create at least one additional volume. 191 You must convert the single-volume file system on which you plan to implement Database Dynamic Storage Tiering. ■ The file system should be unmounted when you run the dbdst_convert command.
192 Using Database Dynamic Storage Tiering Configuring Database Dynamic Storage Tiering Usage notes You must convert your VxFS file system to a multi-volume file system first. ■ Storage classes must be registered using the dbdst_admin command before assigning classes to volumes. ■ The database can be online or offline.
Using Database Dynamic Storage Tiering Configuring Database Dynamic Storage Tiering To display the free space on a storage class ◆ Use the dbdst_show_fs command as follows: $ /opt/VRTS/bin/dbdst_show_fs -S $ORACLE_SID -o volume \ -m mount_point Adding new volumes to a storage class Use the dbdst_addvol command to add volumes to a volume set. Before adding a volume, review the following information: Usage notes ■ The database must be inactive when adding volumes to a storage class.
194 Using Database Dynamic Storage Tiering Dynamic Storage Tiering policy management Dynamic Storage Tiering policy management You can choose to manually relocate files or tablespaces, or you can use a preset Dynamic Storage Tiering (DST) policy. Relocating files You can relocate flashback logs, archive logs, datafiles, and external files if the files are no longer being used frequently. For example, if you maintain seasonal data, you may choose to move the files when you are in different seasons.
Using Database Dynamic Storage Tiering Dynamic Storage Tiering policy management 195 Relocating tablespaces Use the dbdst_tbs_move command to move tablespaces to the desired storage class. The command queries the SFDB repository for the tablespace file names, then performs a one-time move based on your immediate requirements.
196 Using Database Dynamic Storage Tiering Dynamic Storage Tiering policy management -p SALES_Q1 -c SLOW Using preset policies Use the dbdst_preset_policy command to set a policy based on file name patterns before the files are created. Table 11-4 on page 196. shows the dbdst_preset_policy options. Table 11-4 dbdst_preset_policy command options Option Description -d directory Indicates the directory on which the placement policy will be applied.
Using Database Dynamic Storage Tiering Running Database Dynamic Storage Tiering reports Running Database Dynamic Storage Tiering reports You can create a report that lists all updated allocation policies or you can view an audit report, which lists recent relocation changes for a specific date range resulting from your policies. Viewing modified allocation policies To create a list of modified allocation policies, use the dbdst_report command with the policy option.
198 Using Database Dynamic Storage Tiering Extent balancing in a database environment To increase space, you could perform a volume relayout using the vxrelayout command. However, changing a large volume from a four-way striped volume to six-way striped volume involves moving old block information into temporary space and writing those blocks from the temporary space to a new volume, which takes a long time.
Using Database Dynamic Storage Tiering Database Dynamic Storage Tiering use cases for Oracle The extent balancing policy is intended for balancing data extents belonging to files across volumes defined in the policy. However, there is no restriction imposed in assigning extent balancing policy for metadata. Note: If the fixed extent size is less than the chunk size, then the extent size will be limited to the largest multiple of the fixed extent size that is less than the chunk size.
200 Using Database Dynamic Storage Tiering Database Dynamic Storage Tiering use cases for Oracle To add the fast_storage and slow_storage storage classes ◆ Use the dbdst_admin command as follows: $ /opt/VRTS/bin/dbdst_admin -S PROD -o addclass=\ fast_storage:"Fast Storage for Production DB" $ /opt/VRTS/bin/dbdst_admin -S PROD -o addclass=\ slow_storage:"Slow Storage for Production DB" To convert the database's file system and add volumes for use with Database Dynamic Storage Tiering ◆ Use the dbdst_con
Using Database Dynamic Storage Tiering Database Dynamic Storage Tiering use cases for Oracle product_tab, and uses underlying DST services to immediately relocate those files to the fast_storage and slow_storage placement classes respectively.
202 Using Database Dynamic Storage Tiering Database Dynamic Storage Tiering use cases for Oracle technology to correct any accidental errors quickly. The database generates large number of archive logs per day. If the database goes down for any reason, there is business requirement to bring the database back online and functional with in 15 minutes. To prevent Oracle log switch delays during transactions, the archive logs need to be created in a fast EMC array.
Using Database Dynamic Storage Tiering Database Dynamic Storage Tiering use cases for Oracle 203 To convert the database's file system and add volumes for use with Database Dynamic Storage Tiering ◆ Use the dbdst_convert command as follows: $ /opt/VRTS/bin/dbdst_convert -S PROD \ -M /dev/vx/dsk/oradg/oralog -v emc_v1,clarion_v1,jbod_v1 To classify volumes into storage classes ◆ Use the dbdst_classify command as follows: $ /opt/VRTS/bin/dbdst_classify -S PROD \ -M /dev/vx/dsk/oradg/oralog -v emc_v1:NEW
204 Using Database Dynamic Storage Tiering Database Dynamic Storage Tiering use cases for Oracle
Chapter 12 Using the Space Capacity Planning Utility for Storage Checkpoints This chapter includes the following topics: ■ About planning file system space for Storage Checkpoints ■ Starting the Storage Checkpoint Capacity Planning utility ■ Creating Capacity Planning schedules ■ Displaying Capacity Planning schedules ■ Displaying file system space usage information ■ Removing Capacity Planning schedules About planning file system space for Storage Checkpoints This is the last major release of
206 Using the Space Capacity Planning Utility for Storage Checkpoints Starting the Storage Checkpoint Capacity Planning utility which you plan to create Storage Checkpoints, and how many Storage Checkpoints you want to retain on your system at any given time.
Using the Space Capacity Planning Utility for Storage Checkpoints Creating Capacity Planning schedules To start the Storage Checkpoint Capacity Planning utility ◆ At the administrative prompt, enter: $ /opt/VRTSdbed/bin/dbed_ckptplan The Storage Checkpoint Capacity Planning utility starts up and displays the associated operations: VERITAS Storage Foundation for Oracle (ORACLE_SID 'PROD') Menu: Storage Checkpoint Capacity Planning 1 2 3 4 Create Capacity Planning Schedules Display Capacity Planning Sched
208 Using the Space Capacity Planning Utility for Storage Checkpoints Creating Capacity Planning schedules To create Capacity Planning schedules using the Capacity Planning Utility 1 From the Storage Checkpoint Capacity Planning menu, type 1 to select Create Capacity Planning Schedules: VERITAS Storage Foundation for Oracle (ORACLE_SID 'PROD') Menu: Storage Checkpoint Capacity Planning 1 2 3 4 Create Capacity Planning Schedules Display Capacity Planning Schedules Display Space Usage Information Remove
Using the Space Capacity Planning Utility for Storage Checkpoints Creating Capacity Planning schedules 3 209 Supply the schedule-creation information when prompted. When you finish entering the schedule information, the Storage Checkpoint Capacity Planning utility displays the schedule you created and lets you confirm or edit it.
210 Using the Space Capacity Planning Utility for Storage Checkpoints Displaying Capacity Planning schedules Displaying Capacity Planning schedules Use the Storage Checkpoint Capacity Planning utility to display all the Capacity Planning schedules you created.
Using the Space Capacity Planning Utility for Storage Checkpoints Displaying file system space usage information Displaying file system space usage information Use the Storage Checkpoint Capacity Planning utility to display space-usage information for VxFS file systems and the associated Storage Checkpoints. You can monitor this space-usage information as your Storage Checkpoint-creation schedules progress.
212 Using the Space Capacity Planning Utility for Storage Checkpoints Displaying file system space usage information VERITAS Storage Foundation for Oracle (ORACLE_SID 'PROD') Menu: Display Space Usage Information 1 2 3 4 Display Display Display Display Space Space Space Space Usage Usage Usage Usage for the Current Instance for a List of File Systems for All File Systems by Schedule ? q x Display Help About the Current Menu Exit From Current Menu Exit From Capacity Planning Utility Select Operation
Using the Space Capacity Planning Utility for Storage Checkpoints Removing Capacity Planning schedules Planning_00001_956758441 Wed Oct 27 07:14:01 2001 4.0KB Total space required by 3 Storage Checkpoint(s) is 90.0KB Press to continue...
214 Using the Space Capacity Planning Utility for Storage Checkpoints Removing Capacity Planning schedules To remove Capacity Planning schedules using the Capacity Planning Utility
Using the Space Capacity Planning Utility for Storage Checkpoints Removing Capacity Planning schedules ◆ 215 From the Storage Checkpoint Capacity Planning menu, type 4 to select Remove Capacity Planning Schedules: VERITAS Storage Foundation for Oracle (ORACLE_SID 'PROD') Menu: Storage Checkpoint Capacity Planning 1 2 3 4 Create Capacity Planning Schedules Display Capacity Planning Schedules Display Space Usage Information Remove Capacity Planning Schedules ? q x Display Help About the Current Menu Ex
216 Using the Space Capacity Planning Utility for Storage Checkpoints Removing Capacity Planning schedules -- ----------- ---------- -------------1 2001-12-15 2001-12-15 Daily at at 1 a.m. Do you want to delete schedule #1? [y,n,q,?] y Do you want to remove the Storage Checkpoints created by Capacity Planning schedule #1? [y,n,q,?] (default: y) Generating the output /etc/vx/vxdba/logs/plan00001.out', please wait... Removed schedule ' 00001' successfully.
Chapter 13 Using Database FlashSnap for backup and off-host processing This chapter includes the following topics: ■ About Veritas Database FlashSnap ■ How to plan for Database FlashSnap ■ Hosts and storage for Database FlashSnap ■ Summary of database snapshot steps ■ 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
218 Using Database FlashSnap for backup and off-host processing About Veritas Database FlashSnap About Veritas Database FlashSnap Veritas Database FlashSnap is included with Veritas Database Edition Enterprise Edition. Database FlashSnap lets you capture an online image of an actively changing database at a given instant, known as a snapshot. You can perform backups and off-host processing tasks on snapshots while providing continuous availability of your critical data, with minimal interruption to users.
Using Database FlashSnap for backup and off-host processing About Veritas Database FlashSnap Typical database problems solved with Database FlashSnap Database FlashSnap is designed to enable you to use database snapshots to overcome the following types of problems encountered in enterprise database environments: ■ In many companies, there is a clear separation between the roles of system administrators and database administrators.
220 Using Database FlashSnap for backup and off-host processing About Veritas Database FlashSnap developers, system testers, and quality assurance groups with a realistic basis for testing the robustness, integrity, and performance of new applications. ■ Logical Error Recovery Logical errors caused by an administrator or an application program can compromise the integrity of a database.
Using Database FlashSnap for backup and off-host processing About Veritas Database FlashSnap create database clones based on the snapshots on either the same host or a secondary one, or on the same host if used within Oracle RAC. A database clone can be used on a secondary host for off-host processing, including decision-support analysis and reporting, application development and testing, database backup, and logical error recovery.
222 Using Database FlashSnap for backup and off-host processing About Veritas Database FlashSnap the original volumes from the snapshot volumes is known as reverse resynchronization. In Oracle RAC, this command must be run on the CVM master node. ■ dbed_vmclonedb (used on the primary or secondary host) Mounts and starts a clone database using snapshot volumes. It can also shut down a clone database and deport its volumes, as well as restart a clone database that has been shut down.
Using Database FlashSnap for backup and off-host processing How to plan for Database FlashSnap Use this option to clone or back up a database. With the offline option, the database must be shut down when the snapshot is created, and online redo logs are required. Note: In Oracle RAC configurations, only the online option can be used. How to plan for Database FlashSnap Before using Database FlashSnap, you must determine your intended application.
224 Using Database FlashSnap for backup and off-host processing Hosts and storage for Database FlashSnap With Veritas Storage Foundation for Oracle RAC, Database FlashSnap can be used on the same cluster that the database resides on. Setting up a storage configuration for Database FlashSnap operations is a system administrator's responsibility and requires superuser (root) privileges. Database FlashSnap utilities do not address setting up an appropriate storage configuration.
Using Database FlashSnap for backup and off-host processing Hosts and storage for Database FlashSnap Because Veritas Storage Foundation for Oracle RAC uses multiple hosts, an Oracle RAC configuration appears much like a two-host configuration, but without the concepts of "off-host" processing or primary and secondary hosts. Figure 13-2 shows a two-host configuration, or the equivalent with an Oracle RAC configuration.
226 Using Database FlashSnap for backup and off-host processing Hosts and storage for Database FlashSnap ■ Oracle datafiles, archive logs, redo logs, and control files are in a single disk group. In addition, before attempting to use Database FlashSnap with two hosts, ensure that: ■ The versions of Veritas Storage Foundation for Oracle on the primary and secondary hosts are the same. ■ The same version of Oracle is installed on both hosts.
Using Database FlashSnap for backup and off-host processing Hosts and storage for Database FlashSnap Prerequisites ■ You must be logged in as superuser (root). ■ The disk group must be version 110 or later. For more information on disk group versions, see the vxdg(1M) online manual page. ■ Be sure that a data change object (DCO) and a DCO log volume are associated with the volume for which you are creating the snapshot.
228 Using Database FlashSnap for backup and off-host processing Hosts and storage for Database FlashSnap Usage notes ■ Create a separate disk group for Oracle database-related files. Do not share volumes between Oracle database files and other software. ■ ORACLE_HOME cannot be included in the snapshot mirror. ■ Resynchronization speed varies based on the amount of data changed in both the primary and snapshot volumes during the break-off time.
Using Database FlashSnap for backup and off-host processing Hosts and storage for Database FlashSnap 3 Verify that a DCO and DCO log are attached to the volume: vxprint -g diskgroup -F%fastresync volume_name vxprint -g diskgroup -F%hasdcolog volume_name This command returns on if a DCO and DCO log are attached to the specified volume.
230 Using Database FlashSnap for backup and off-host processing Hosts and storage for Database FlashSnap 7 Verify that the dbed_flashsnap tag has been set on the data plex for each volume in the volume set: vxprint -g diskgroup -F%name -e"pl_v_name in \"volume_name\" \ && p2 in \"dbed_flashsnap\"" For example: # vxprint -g PRODdg -F%name -e"pl_v_name in \"snapdata\" \ && p2 in \"dbed_flashsnap\"" snapdata-02 8 Verify the disk group configuration: vxprint -g diskgroup For example: # vxprint -g PRODdg
Using Database FlashSnap for backup and off-host processing Hosts and storage for Database FlashSnap To create a snapshot mirror of a volume set 1 Create a volume: vxassist -g diskgroup make volume_name size disk_name For example: # vxassist -g PRODdg make snapvset_1 8g snap01 # vxassist -g PRODdg make snapvset_2 4g snap01 2 Create a volume set for use by VxFS: vxvset -g diskgroup -t vxfs make vset_name volume_name For example: # vxvset -g PRODdg -t vxfs make snapvset snapvset_1 3 Add the volume to
232 Using Database FlashSnap for backup and off-host processing Hosts and storage for Database FlashSnap 5 Verify that a DCO and DCO log are attached to each volume in the volume set: vxprint -g diskgroup -F%fastresync volume_name vxprint -g diskgroup -F%hasdcolog volume_name This command returns on if a DCO and DCO log are attached to the specified volume.
Using Database FlashSnap for backup and off-host processing Hosts and storage for Database FlashSnap 8 Set the dbed_flashsnap tag on the break-off data plex for each volume in the volume set: vxedit -g diskgroup set putil2=dbed_flashsnap plex_name For example: # vxedit -g PRODdg set putil2=dbed_flashsnap snapvset_1-02 # vxedit -g PRODdg set putil2=dbed_flashsnap snapvset_2-02 233
234 Using Database FlashSnap for backup and off-host processing Hosts and storage for Database FlashSnap 9 Verify that the dbed_flashsnap tag has been set on the data plex for each volume in the volume set: vxprint -g diskgroup -F%name -e"pl_v_name in \"volume_name\" \ && p2 in \"dbed_flashsnap\"" For example: # vxprint -g PRODdg -F%name -e"pl_v_name in \"snapvset_1\" \ && p2 in \"dbed_flashsnap\"" snapvset_1-02 # vxprint -g PRODdg -F%name -e"pl_v_name in \"snapvset_2\" \ && p2 in \"dbed_flashsnap\"" sn
Using Database FlashSnap for backup and off-host processing Hosts and storage for Database FlashSnap 10 Verify the snapshot volume configuration: vxprint -g diskgroup For example: # vxprint -g PRODdg TY NAME ASSOC dg PRODdg PRODdg KSTATE - LENGTH - dm snap01 dm snap02 - 33483648 33483648 - ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED DISABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED DISABLED ENABLED 16777216 16777216 16777216 16777216 167772
236 Using Database FlashSnap for backup and off-host processing Hosts and storage for Database FlashSnap # vxprint -g PRODdg -F%fastresync data_vol on Verify that a DCO and a DCO log are attached to the volume: # vxprint -g PRODdg -F%hasdcolog data_vol on Create a snapshot mirror of data_vol: # vxsnap -g PRODdg addmir data_vol alloc=PRODdg02 List the data plexes: # vxprint -g PRODdg -F%name -e"pl_v_name in \"data_vol\"" data_vol-01 data_vol-02 Choose the plex that is in the SNAPDONE state.
Using Database FlashSnap for backup and off-host processing Hosts and storage for Database FlashSnap v pl sd pl sd dc v pl sd pl sd data_vol fsgen data_vol-01 data_vol PRODdg03-01 data_vol-01 data_vol-02 data_vol PRODdg02-01 data_vol-02 data_vol_dco data_vol data_vol_dcl gen data_vol_dcl-01 data_vol_dcl PRODdg01-01 data_vol_dcl-01 data_vol_dcl-02 data_vol_dcl PRODdg02-02 data_vol_dcl-02 ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED DISABLED ENABLED 4194304 4194304 4194304 4194304 41943
238 Using Database FlashSnap for backup and off-host processing Hosts and storage for Database FlashSnap To upgrade an existing volume created with an earlier version of VxVM 1 Upgrade the disk group that contains the volume to a version 120 or higher before performing the remainder of this procedure.
Using Database FlashSnap for backup and off-host processing Hosts and storage for Database FlashSnap 6 Use the following command on the volume to upgrade it: # vxsnap [-g diskgroup] prepare volume \ alloc="disk_name1,disk_name2" Provide two disk names to avoid overlapping the storage of the snapshot DCO plex with any other non-moving data or DCO plexes. The vxsnap prepare command automatically enables persistent FastResync on the volume and on any snapshots that are generated from it.
240 Using Database FlashSnap for backup and off-host processing Hosts and storage for Database FlashSnap Reattach any snapshot volume back to the primary volume to be upgraded: # vxsnap -g PRODdg snapback SNAP-data_vol Turn off FastResync on the volume to be upgraded: # vxvol -g PRODdg set fastresync=off data_vol Disassociate and remove any older DCO object and DCO volumes: # vxassist -g PRODdg remove log data_vol logtype=dco Upgrade the volume by associating a new DCO object and DCO volume: # vxsnap
Using Database FlashSnap for backup and off-host processing Hosts and storage for Database FlashSnap pl sd v pl sd pl sd dc v pl sd pl sd data_vol-03 PRODdg02-01 data_vol-03 data_vol fsgen data_vol-01 data_vol PRODdg01-01 data_vol-01 data_vol-04 data_vol PRODdg02-03 data_vol-04 data_vol_dco data_vol data_vol_dcl gen data_vol_dcl-01 data_vol_dcl PRODdg01-02 data_vol_dcl-01 data_vol_dcl-02 data_vol_dcl PRODdg02-02 data_vol_dcl-02 DISABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENAB
242 Using Database FlashSnap for backup and off-host processing Hosts and storage for Database FlashSnap pl v pl sd pl sd dc v pl sd pl sd data_vol-03 data_vol fsgen data_vol-01 data_vol PRODdg01-01 data_vol-01 data_vol-04 data_vol PRODdg02-03 data_vol-04 data_vol_dco data_vol data_vol_dcl gen data_vol_dcl-01 data_vol_dcl PRODdg01-02 data_vol_dcl-01 data_vol_dcl-02 data_vol_dcl PRODdg02-02 data_vol_dcl-02 DISABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED DISABLED ENABLED 4194304
Using Database FlashSnap for backup and off-host processing Summary of database snapshot steps 4 Remove the volume plexes for vxdbavol and ORACLE_HOME. # vxplex -g diskgroup -o rm dis plex_name 5 Log in as the DBA user and revalidate your snapplan. $ /opt/VRTS/bin/dbed_vmchecksnap -S ORACLE_SID -H ORACLE_HOME \ -f SNAPPLAN -o validate Summary of database snapshot steps You can use Database FlashSnap commands to create a snapshot of your entire database on the same host or on a different one.
244 Using Database FlashSnap for backup and off-host processing Summary of database snapshot steps Note: Make sure the volumes used by the database are configured properly before attempting to take a snapshot. This requires superuser (root) privileges. Anytime you change the structure of the database (for example, by adding or deleting datafiles, converting PFILE to SPFILE, or converting SPFILE to PFILE), you must run dbed_update.
Using Database FlashSnap for backup and off-host processing Summary of database snapshot steps 4 On the secondary host, use the dbed_vmclonedb command to create a clone database using the disk group deported from the primary host. The dbed_vmclonedb command imports the disk group that was deported from the primary host, recovers the snapshot volumes, mounts the file systems, recovers the database, and brings the database online. If the secondary host is different, the database name can be same.
246 Using Database FlashSnap for backup and off-host processing Summary of database snapshot steps Figure 13-3 Prerequisites for creating a snapshot of your database Determine your storage configuration Prepare hosts and storage for Database FlashSnap Create a default snapplan (dbed_vmchecksnap -o setdefaults) Change the default values? Yes Modify the snapplan No Validate the snapplan (dbed_vmchecksnap -o validate) Pass validation? No Yes Fix the error SNAPSHOT There are many actions you can
Using Database FlashSnap for backup and off-host processing Creating a snapplan (dbed_vmchecksnap) Figure 13-4 Database FlashSnap process SNAPSHOT Create the snapshot volumes (dbed_vmsnap -o snapshot) Do you want to clone the database? No Yes Resynchronize the snapshot volumes? Use the clone on a secondary host? The snapshot disk group will be imported Yes Yes No Resynchronize.
248 Using Database FlashSnap for backup and off-host processing Creating a snapplan (dbed_vmchecksnap) You can name a snapplan file whatever you choose. Each entry in the snapplan file is a line in parameter=argument format. Table 13-1 shows which parameters are set when using dbed_vmchecksnap to create or validate a snapplan.
Using Database FlashSnap for backup and off-host processing Creating a snapplan (dbed_vmchecksnap) Table 13-1 Parameter values for dbed_vmchecksnap (continued) Parameter Value SNAPSHOT_MODE online or offline or instant Specifies whether the database snapshot should be online, offline, or instant. If the snapshot is created while the database is online, the dbed_vmsnap command will put the tablespaces into backup mode.
250 Using Database FlashSnap for backup and off-host processing Creating a snapplan (dbed_vmchecksnap) Table 13-1 Parameter values for dbed_vmchecksnap (continued) Parameter Value ALLOW_REVERSE_RESYNC yes or no By default, reverse resynchronization is off (set equal to no). If it is set to yes, data from the snapshot volume can be used to update the primary volume. SNAPSHOT_MIRROR Specifies the number of plexes to be snapshot. The default value is 1.
Using Database FlashSnap for backup and off-host processing Creating a snapplan (dbed_vmchecksnap) Usage notes ■ The snapplan must be created on the primary host. After creating the snapplan using the dbed_vmchecksnap command, you can use a text editor to review and update the file, if necessary. ■ It is recommended that you create a local working directory to store your snapplans in. ■ See the dbed_vmchecksnap(1M) online manual page for more information.
252 Using Database FlashSnap for backup and off-host processing Creating a snapplan (dbed_vmchecksnap) ARCHIVELOG_DEST=/prod_ar SNAPSHOT_ARCHIVE_LOG=yes SNAPSHOT_MODE=online SNAPSHOT_PLAN_FOR=database SNAPSHOT_PLEX_TAG=dbed_flashsnap SNAPSHOT_VOL_PREFIX=SNAP_ ALLOW_REVERSE_RESYNC=no SNAPSHOT_MIRROR=1 In this example, a snapplan, snap2, is created for a snapshot image in a two-host configuration, and default values are set.
Using Database FlashSnap for backup and off-host processing Creating a snapplan (dbed_vmchecksnap) Snapplan snap1 for PROD ===================================================== SNAPSHOT_VERSION=5.
254 Using Database FlashSnap for backup and off-host processing Creating a snapplan (dbed_vmchecksnap) To create a multi-mirror snaphot 1 Add the second mirror and DCO log. When allocating storage for the second mirror and DCO logs, make sure the snap volumes are splittable. If snap volumes are not splittable, dbed_vmchecksnap fails with appropriate errors. # vxsnap -g dg_a addmir dg_a_vol1 alloc=dg_a03 2 Tag the newly added mirror with the same tag as that of the first mirror.
Using Database FlashSnap for backup and off-host processing Validating a snapplan (dbed_vmchecksnap) This example shows how to establish a mandatory archive destination using SQL*Plus: alter system set log_archive_dest_1 = \ 'LOCATION=/ora_mnt/oracle/oradata/PROD/archivelogs MANDATORY \ [REOPEN]' [scope=both]; For more information about Oracle parameters for archiving redo logs, see your Oracle documentation. For example, the scope=both parameter value does not work in Oracle 10gR2.
256 Using Database FlashSnap for backup and off-host processing Validating a snapplan (dbed_vmchecksnap) To validate a snapplan 1 Change directories to the working directory your snapplan is stored in: $ cd /working_directory 2 Validate the snapplan using the dbed_vmchecksnap command: $ /opt/VRTS/bin/dbed_vmchecksnap -S ORACLE_SID \ -H ORACLE_HOME -f SNAPPLAN -o validate In an HA environment, you must modify the default snapplan, use the virtual host name defined for the resource group for the PRIMAR
Using Database FlashSnap for backup and off-host processing Validating a snapplan (dbed_vmchecksnap) Volume prodvol1 on PRODdg is ready for snapshot. Original plex and DCO log for prodvol1 is on PRODdg1. Snapshot plex and DCO log for prodvol2 is on PRODdg2. Volume prodvol2 on PRODdg is ready for snapshot. Original plex and DCO log for prodvol2 is on PRODdg1. Snapshot plex and DCO log for prodvol2 is on PRODdg2.
258 Using Database FlashSnap for backup and off-host processing Displaying, copying, and removing a snapplan (dbed_vmchecksnap) Displaying, copying, and removing a snapplan (dbed_vmchecksnap) Consider these notes before listing all snapplans for a specific Oracle database, displaying a snapplan file, or copying and removing snapplans. Usage notes If the local snapplan is updated or modified, you must re-validate it.
Using Database FlashSnap for backup and off-host processing Displaying, copying, and removing a snapplan (dbed_vmchecksnap) To display detailed information for a snapplan ◆ Use the dbed_vmchecksnap command as follows: $ /opt/VRTS/bin/dbed_vmchecksnap -S ORACLE_SID \ -f SNAPPLAN -o list In the following example, the snapplan snap1 is displayed. $ /opt/VRTS/bin/dbed_vmchecksnap -S PROD -f snap1 -o list SNAPSHOT_VERSION=4.
260 Using Database FlashSnap for backup and off-host processing Creating a snapshot (dbed_vmsnap) To copy a snapplan from the repository to your current directory ◆ If you want to create a snapplan similar to an existing snapplan, you can simply create a copy of the existing snapplan and modify it. To copy a snapplan from the repository to your current directory, the snapplan must not already be present in the current directory.
Using Database FlashSnap for backup and off-host processing Creating a snapshot (dbed_vmsnap) Prerequisites Usage notes ■ You must be logged in as the Oracle database administrator. ■ You must create and validate a snapplan using dbed_vmchecksnap before you can create a snapshot image with dbed_vmsnap. ■ The dbed_vmsnap command can only be used on the primary host, or if in an Oracle RAC configuration, on the CVM master node. Do not share volumes between Oracle database files and other software.
262 Using Database FlashSnap for backup and off-host processing Creating a snapshot (dbed_vmsnap) Note: To force snapshot creation, use the -F option. The -F option can be used after a snapshot operation has failed and the problem was fixed without using Veritas Storage Foundation for Oracle commands. (That is, the volumes were synchronized without using Veritas Storage Foundation for Oracle commands.) In this situation, the status of the snapplan will appear as unavailable for creating a snapshot.
Using Database FlashSnap for backup and off-host processing Backing up the database from snapshot volumes (dbed_vmclonedb) dbed_vmsnap ended at 2004-04-02 14:16:11 In this example, a snapshot image of the primary database, PROD, is created for a two-host configuration. In this case, the SECONDARY_HOST parameter specifies a different host name than the PRIMARY_HOST parameter in the snapplan. Note: This example does not apply to an Oracle RAC configuration.
264 Using Database FlashSnap for backup and off-host processing Backing up the database from snapshot volumes (dbed_vmclonedb) Figure 13-5 Example system configuration for database backup on the primary host Primary host for database Local disks Controllers c1 c2 c3 Database volumes are created on these disks c4 Disk Arrays Snapshot volumes are created on these disks Back up to disk, tape or other media by primary host Figure 13-6 shows a typical configuration when snapshot volumes are used on
Using Database FlashSnap for backup and off-host processing Backing up the database from snapshot volumes (dbed_vmclonedb) Figure 13-6 Example system configuration for database backup on a secondary host Network Primary host for database Secondary host Local disks Local disks Controllers c1 c2 c3 Volumes created on these disks are accessed by the primary host Controllers c4 c1 Disk Arrays c2 c3 c4 Snapshot volumes created on these disks are accessed by both hosts Back up to disk, tape or ot
266 Using Database FlashSnap for backup and off-host processing Backing up the database from snapshot volumes (dbed_vmclonedb) Usage notes The dbed_vmclonedb command can be used on the secondary host. ■ In a single-host configuration, the primary and secondary hosts are the same. ■ In a single-host configuration, -r relocate_path is required. ■ ■ If SNAPSHOT_MODEis set to offlineor instant, a two-host configuration is required and -r relocate_path is not allowed.
Using Database FlashSnap for backup and off-host processing Cloning a database (dbed_vmclonedb) Consider the following limitations when working with Storage Checkpoints carried over from the primary database: ■ Any mounted Storage Checkpoints must be unmounted before running the following command: $ /opt/VRTS/bin/dbed_vmclonedb -o umount,new_sid=new_sid \ -f SNAPPLAN ■ It is only possible to mount a Storage Checkpoint carried over with the snapshot volumes in a two-host configuration if the snapshot vol
268 Using Database FlashSnap for backup and off-host processing Cloning a database (dbed_vmclonedb) See “Backing up the database from snapshot volumes (dbed_vmclonedb)” on page 263. You can also back up the primary database to tape using snapshot volumes. The resynchronization functionality of Database FlashSnap allows you to quickly refresh the clone database with up-to-date information from the primary database.
Using Database FlashSnap for backup and off-host processing Cloning a database (dbed_vmclonedb) Prerequisites ■ You must be logged in as the Oracle database administrator. Before you can use the dbed_vmclonedb command, review the procedure for taking a snapshot of a database, especially the steps required to validate a snapplan and to create the snapshot. See “Summary of database snapshot steps” on page 243. See “Validating a snapplan (dbed_vmchecksnap)” on page 255.
270 Using Database FlashSnap for backup and off-host processing Cloning a database (dbed_vmclonedb) To mount a database and recover it manually 1 Start and mount the clone database to allow manual database recovery: $ /opt/VRTS/bin/dbed_vmclonedb -S ORACLE_SID -g snap_dg \ -o mountdb,new_sid=new_sid,server_name=svr_name -f SNAPPLAN \ [-H ORACLE_HOME] [-r relocate_path] 2 Recover the database manually.
Using Database FlashSnap for backup and off-host processing Cloning a database (dbed_vmclonedb) In this example, file systems are mounted without recovering the clone database. The clone database must be manually recovered before it can be used. This example is for a clone created on a secondary host.
272 Using Database FlashSnap for backup and off-host processing Cloning a database (dbed_vmclonedb) ■ SNAPPLAN is the name of the snapplan file. ■ ORACLE_HOME is the ORACLE_HOME setting for the ORACLE_SID database. ■ relocate_path is the name of the initial mount point for the snapshot image. Note: When cloning a database on a secondary host, ensure that PRIMARY_HOST and SECONDARY_HOST parameters in the snapplan file are different.
Using Database FlashSnap for backup and off-host processing Cloning a database (dbed_vmclonedb) Note: Any mounted Storage Checkpoints need to be unmounted before running dbed_vmclonedb -o umount.
274 Using Database FlashSnap for backup and off-host processing Cloning a database (dbed_vmclonedb) To start the clone database ◆ Use the dbed_vmclonedb command as follows: $ /opt/VRTS/bin/dbed_vmclonedb -S ORACLE_SID -g snap_dg \ -o restartdb,new_sid=new_sid,server_name=svr_name -f SNAPPLAN \ [-H ORACLE_HOME] [-r relocate_path] In this example, the clone database is re-started on the same host as the primary database (a single-host configuration).
Using Database FlashSnap for backup and off-host processing Cloning a database (dbed_vmclonedb) 275 To recreate the Oracle tempfiles 1 If the tempfiles were not residing on the same file systems as the datafiles, dbed_vmclonedb will display the WARNING and INFOmessages similar to the following: WARNING: Not all tempfiles were included in snapshot for $ORACLE_SID, there is no snapshot volume for /clone_path/temp02.dbf. WARNING: Could not recreate tempfiles for $ORACLE_SID due to lack of free space.
276 Using Database FlashSnap for backup and off-host processing Resynchronizing your database to the snapshot 5 In the add_tf.$ORACLE_SID.sql file, edit the sizes and default path names of the tempfiles as needed to reside on cloned volumes configured for database storage. Note: Do not run the script without first editing it because path names may not exist and the specified mount points may not contain sufficient space. 6 After you have modified the add_tf.$ORACLE_SID.
Using Database FlashSnap for backup and off-host processing Resynchronizing your database to the snapshot Prerequisites ■ You must be logged in as the Oracle database administrator. ■ Before you can reverse resynchronize the snapshot image, review the database snapshot procedure and create the snapshot. Before you execute the reverse_resync_commit command, you must remove the old archive log when ODM is enabled.
278 Using Database FlashSnap for backup and off-host processing Resynchronizing your database to the snapshot To abort reverse resynchronization ◆ Use the -o reverse_resync_abort option of the dbed_vmsnap command: $ /opt/VRTS/bin/dbed_vmsnap -S ORACLE_SID -f SNAPPLAN \ -o reverse_resync_abort The -o reverse_resync_abort option aborts -o reverse_resync_begin, unmounts the snapshot volumes, and mounts the original volumes back with the file systems that are configured to use the volume.
Using Database FlashSnap for backup and off-host processing Resynchronizing the snapshot to your database dbed_vmsnap started at 2004-04-02 16:16:44 The option reverse_resync_abort has been completed. dbed_vmsnap ended at 2004-04-02 16:16:51 Reverse resychronization changes are committed on the primary host. $ /opt/VRTS/bin/dbed_vmsnap -S PROD -f snap1 \ -o reverse_resync_commit dbed_vmsnap started at 2004-04-02 16:18:44 The option reverse_resync_commit has been completed.
280 Using Database FlashSnap for backup and off-host processing Removing a snapshot volume Usage notes The dbed_vmsnap command can only be executed on the primary host, or if in an Oracle RAC configurration, on the CVM master node. ■ In a two-host configuration, the dbed_vmsnap command imports the disk group that was deported from the secondary host and joins the disk group back to the original disk group. The snapshot volumes again become plexes of the original volumes.
Using Database FlashSnap for backup and off-host processing Using Database FlashSnap in an HA environment If the snapshot has not been taken and the snapshot plex (mirror) exists: ■ Remove the snapshot as follows: # vxsnap -g diskgroup rmmir volume 2 Remove the DCO and DCO volume: # vxsnap -g diskgroup unprepare volume 3 Remove the snapplan: # /opt/VRTS/bin/dbed_vmchecksnap -S db -f snapplan -o remove For example, the following commands will remove a snapshot volume from disk group PRODdg: # vxsnap -
282 Using Database FlashSnap for backup and off-host processing Using Database FlashSnap in an HA environment primary database is down, it starts the failover process and the repository is unmounted and the dbed_vmsnap command is aborted. To avoid the VCS failover process 1 As root, temporarily freeze the VCS resource group for the database: # hagrp -freeze ResourceGroup 2 Shut down the primary database.
Chapter 14 Using Veritas NetBackup for database backup This chapter includes the following topics: ■ About using Veritas NetBackup for backup and restore ■ Using Veritas NetBackup to backup and restore Quick I/O files ■ About using Veritas NetBackup to backup and restore Oracle Disk Manager files About using Veritas NetBackup for backup and restore Veritas NetBackup provides for high performance, online (hot) backups of databases that must be available on a 24x7 basis, as well as offline (cold) data
284 Using Veritas NetBackup for database backup Using Veritas NetBackup to backup and restore Quick I/O files same data twice. This would happen if both the link and the file it points to were included in the list of files to be backed up. A Quick I/O file consists of two components: a hidden file with the space allocated for it, and a link that points to the Quick I/O interface of the hidden file.
Using Veritas NetBackup for database backup About using Veritas NetBackup to backup and restore Oracle Disk Manager files Note: The Oracle backup and restore utility cannot be used to back up and restore Quick I/O files. Some back up software may not be able to back up and restore VxFS extent attributes. See the qio_recreate(1M) online manual page for information on how to restore missing Quick I/O files.
286 Using Veritas NetBackup for database backup About using Veritas NetBackup to backup and restore Oracle Disk Manager files
Chapter 15 Tuning for performance This chapter includes the following topics: ■ Additional documentation ■ About tuning VxVM ■ About tuning VxFS ■ About tuning Oracle databases ■ About tuning HP-UX Additional documentation Use the tuning tips and information provided in this chapter in conjunction with other more in-depth publications, such as: ■ Oracle Performance Tuning Tips & Techniques (Osborne McGraw-Hill) ■ Oracle9i Installation Guide (Oracle Corporation) ■ Oracle 10g Installation Gui
288 Tuning for performance About tuning VxVM capable of adopting reasonable defaults for all configuration parameters. On very large systems, however, there may be configurations that require additional tuning of these parameters, both for capacity and performance reasons. For more information on tuning VxVM, see the Veritas Volume Manager Administrator's Guide.
Tuning for performance About tuning VxFS TYP NAME READ WRITE READ WRITE READ WRITE vol blop 0 0 0 0 0.0 0.0 vol foobarvol 0 0 0 0 0.0 0.0 vol rootvol 73017 181735 718528 1114227 26.8 27.9 vol swapvol 13197 20252 105569 162009 25.8 397.0 vol testvol 0 0 0 0 0.0 0.0 Additional information is available on how to use the vxstat output to identify volumes that have excessive activity and how to reorganize, change to a different layout, or move these volumes.
290 Tuning for performance About tuning VxFS free space have less fragmentation and better extent allocation. Regular use of the df command to monitor free space is desirable. Full file systems may have an adverse effect on file system performance. Full file systems should therefore have some files removed or should be expanded. See the fsadm_vxfs(1M) manual page. About monitoring fragmentation Fragmentation reduces performance and availability.
Tuning for performance About tuning VxFS and running the extent fragmentation report feature of fsadm before and after the reorganization. The “before” result is the degree of fragmentation prior to the reorganization. If the degree of fragmentation approaches the percentages for bad fragmentation, reduce the interval between fsadm. If the degree of fragmentation is low, increase the interval between fsadm runs.
292 Tuning for performance About tuning VxFS write_pref_io The preferred write request size. The file system uses this parameter in conjunction with the write_nstream value to determine how to do flush behind on writes. The default value is 64K. read_nstream The number of parallel read requests of size read_pref_io that you can have outstanding at one time. The file system uses the product of read_nstream multiplied by read_pref_io to determine its read ahead size.
Tuning for performance About tuning VxFS initial_extent_ size Changes the default initial extent size. VxFS determines the size of the first extent to be allocated to the file based on the first write to a new file. Normally, the first extent is the smallest power of 2 that is larger than the size of the first write. If that power of 2 is less than 8K, the first extent allocated is 8K.
294 Tuning for performance About tuning VxFS max_seqio_extent_size Increases or decreases the maximum size of an extent. When the file system is following its default allocation policy for sequential writes to a file, it allocates an initial extent that is large enough for the first write to the file. When additional extents are allocated, they are progressively larger (the algorithm tries to double the size of the file with each new extent) so each extent can hold several writes' worth of data.
Tuning for performance About tuning VxFS write_throttle Warning: The write_throttle parameter is useful in special situations where a computer system has a combination of a lot of memory and slow storage devices. In this configuration, sync operations (such as fsync()) may take so long to complete that the system appears to hang.
296 Tuning for performance About tuning VxFS If an application is doing sequential I/O to large files, it should issue requests larger than the discovered_direct_iosz. This causes the I/O requests to be performed as discovered direct I/O requests, which are unbuffered like direct I/O but do not require synchronous inode updates when extending the file. If the file is too large to fit in the cache, then using unbuffered I/O avoids throwing useful data out of the cache and lessons CPU overhead.
Tuning for performance About tuning VxFS 297 There are three primary statistics to consider: ■ file I/O activity ■ volume I/O activity ■ raw disk I/O activity If your database is using one file system on a striped volume, you may only need to pay attention to the file I/O activity statistics. If you have more than one file system, you may need to monitor volume I/O activity as well. First, use the qiostat -r command to clear all existing statistics.
298 Tuning for performance About tuning VxFS File I/O statistics help identify files with an unusually large number of operations or excessive read or write times. When this happens, try moving the “hot” files or busy file systems to different disks or changing the layout to balance the I/O load. Mon May 11 16:21:20 2015 /db/dbfile01 813 0 813 0 0.3 0.0 /db/dbfile02 0 813 0 813 0.0 5.5 /db/dbfile01 816 0 816 0 0.3 0.0 /db/dbfile02 0 816 0 816 0.0 5.
Tuning for performance About tuning VxFS To obtain i/0 statistics ◆ Use the odmstat command as follows: # /opt/VRTS/bin/odmstat -i 5 /mnt/odmfile* OPERATIONS FILE NAME FILE BLOCKS AVG TIME(ms) READ WRITE READ WRITE READ WRITE /db/cust.dbf 0 0 0 0 0.0 0.0 /db/system.dbf 0 0 0 0 0.0 0.0 371 0 371 0 0.2 0.0 0 371 0 371 0.0 5.7 813 0 813 0 0.3 0.0 0 813 0 813 0.0 5.5 816 0 816 0 0.3 0.0 0 816 0 816 0.0 5.3 /db/cust.dbf 0 0 0 0 0.0 0.
300 Tuning for performance About tuning Oracle databases For example, if you send 100 I/Os at the same time and each takes 10 milliseconds, the disk reports an average of 10 milliseconds of service and 490 milliseconds of queueing time. The vxstat, odmstat, and qiostat report an average of 500 milliseconds service time. About tuning Oracle databases To achieve optimal performance on your Oracle database, the database needs to be tuned to work with VxFS.
Tuning for performance About tuning Oracle databases Your Oracle Installation Guide provides detailed instructions on implementing asynchronous I/O on your system. Tuning buffer cache The UNIX buffer cache plays an important role in performance when using HFS or JFS in buffered I/O mode. When using Quick I/O, however, the database cache must be tuned as if raw devices are being used.
302 Tuning for performance About tuning HP-UX max_direct_iosz = 2097152 default_indir_size = 8192 Setting slave parameters Quick I/O and ODM provide support for kernel asynchronous I/O, eliminating the need for multiple logwriter slaves or database writer slaves. This parameter is set to by default. It is not necessary to set the DBWR_IO_SLAVES settings if you are using Quick I/O. The number of writer processes is set within DB_WRITER_PROCESSES, which performs asynchronous I/O.
Tuning for performance About tuning HP-UX asyncdsk, asyncdsk_included, and max_async_ports These parameters are used for including and configuring the asynchronous I/O driver in the HP-UX kernel, resulting in less I/O overhead and higher throughput. The parameter max_async_ports sets the maximum number of connections between user processes and the asyncdsk driver. See your Oracle documentation for the recommended value, or set max_async_ports to 1024 if a value is not recommended.
304 Tuning for performance About tuning HP-UX
Appendix A Veritas Storage Foundation for Oracle Command Line Interface This appendix includes the following topics: ■ Overview of commands ■ About the command line interface Overview of commands Veritas Storage Foundation for Oracle provides a command line interface (CLI) to many key operations also supplied from within the GUI application. The command line interface lets you incorporate command operations into scripts and other administrative processes.
306 Veritas Storage Foundation for Oracle Command Line Interface Overview of commands Warning: Unless explicitly stated, commands are not supported by Veritas Storage Foundation for Oracle RAC. Table A-1 summarizes the commands available to you from the command line. Table A-1 Veritas Storage Foundation for Oracle commands Command Description dbed_update Updates the SFDB repository in Veritas Storage Foundation for Oracle. This command is supported by Veritas Storage Foundation for Oracle RAC.
Veritas Storage Foundation for Oracle Command Line Interface Overview of commands Table A-1 Veritas Storage Foundation for Oracle commands (continued) Command Description dbed_ckptremove Removes a Storage Checkpoint for an Oracle database. This command is supported by Veritas Storage Foundation for Oracle RAC. dbed_ckptrollback This command is supported by Veritas Storage Foundation for Oracle RAC. dbed_ckptumount Rolls back an Oracle database to a Storage Checkpoint point-in-time image.
308 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Table A-1 Veritas Storage Foundation for Oracle commands (continued) Command Description Creates a snapshot image of an Oracle database by splitting the mirror volumes used by the database. You can also use This command is supported this command to resynchronize the snapshot image back by Veritas Storage to the current database. The command also allows you to Foundation for Oracle RAC.
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Updating the repository using dbed_update You can use the dbed_update command to update the repository. Any time you change the structure of the database (for example, by adding or deleting datafiles, converting PFILE to SPFILE, or converting SPFILE to PFILE), you must run dbed_update.
310 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Checking the database configuration environment using dbed_checkconfig You can use the command to verify and report on the database environment from the command line.
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface 311 write_pref_io = 65536 write_nstream = 1 write_unit_io = 65536 pref_strength = 10 buf_breakup_size = 1048576 discovered_direct_iosz = 262144 max_direct_iosz = 1048576 default_indir_size = 8192 qio_cache_enable = 0 write_throttle = 0 max_diskq = 1048576 initial_extent_size = 8 max_seqio_extent_size = 2048 max_buf_data_size = 8192 hsm_write_prealloc = 0 read_ahead = 1 inode_aging_size = 0 inode_aging_count = 0 f
312 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface To check the database configuration environment and not update the repository ◆ Use the dbed_checkconfig command with the -v and -n options as follows: $ /opt/VRTS/bin/dbed_checkconfig -S PROD -H /oracle\ /product/9i -v -n where: ■ -v lists all files. ■ -n stops the repository from being updated. Examining file system attributes. All file systems are VxFS.
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface 313 pref_strength = 10 buf_breakup_size = 1048576 discovered_direct_iosz = 262144 max_direct_iosz = 1048576 default_indir_size = 8192 qio_cache_enable = 0 write_throttle = 0 max_diskq = 1048576 initial_extent_size = 8 max_seqio_extent_size = 2048 max_buf_data_size = 8192 hsm_write_prealloc = 0 read_ahead = 1 inode_aging_size = 0 inode_aging_count = 0 fcl_maxalloc = 65075200 fcl_keeptime = 0 fcl_winterval = 3600 E
314 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface /prod_db/index01.dbf /prod_db/data1.dbf /prod_db/rolbak1.dbf /prod_db/system.dbf /prod_db/data01.dbf /prod_db/data02.dbf Total of 9 datafiles are defined to the database. Examining Oracle log modes. The database is running in archivelog mode. The database is running in automatic log archiving mode.
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface To save the database configuration environment ◆ Use the dbed_saveconfig command as follows: $ /opt/VRTS/bin/dbed_saveconfig -S PROD -H /oracle/product/9i Saving System and Oracle Information, please wait ... System configuration information saved to directory: /tmp/vxdbed.DR.
316 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Usage notes This command is supported by Veritas Storage Foundation for Oracle RAC. ■ In a Veritas Storage Foundation for Oracle environment, dbed_ckptcreate stores Storage Checkpoint information under the following directory: /etc/vx/vxdbed/$ORACLE_SID/checkpoint_dir ■ See the dbed_ckptcreate(1M) manual page for more information.
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface To create instant Storage Checkpoints ◆ Ensure that the database is online and use the dbed_ckptcreate command as follows: $ /opt/VRTS/bin/dbed_ckptcreate -S PROD \ -H /oracle/product/9i -o instant Creating instant Storage Checkpoint of database PROD. Storage Checkpoint Checkpoint_971672045 created.
318 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Usage notes Although dbed_ckptcreate is supported by Veritas Storage Foundation for Oracle RAC, this feature is not supported.
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Displaying Storage Checkpoints using dbed_ckptdisplay You can use the dbed_ckptdisplay command to display the Storage Checkpoints associated with an Oracle database from the command line. You can also use it to display fileset quota values.
320 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface To display other Storage Checkpoints ◆ Use the dbed_ckptdisplay command as follows: $ /opt/VRTS/bin/dbed_ckptdisplay -S PROD \ -H /oracle/product/9i -o other NetBackup_incr_PROD_955133480 NetBackup_full_PROD_9551329 52 NBU NBU /db01 /db01 To display other Storage Checkpoints without updating the repository ◆ Use the dbed_ckptdisplay command as follows: $ /opt/VRTS/bin/dbed_ckptdisplay -S PROD \ -H /orac
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface 321 To display all Storage Checkpoints without updating the repository ◆ Use the dbed_ckptdisplay command as follows: $ /opt/VRTS/bin/dbed_ckptdisplay -S PROD \ -H /oracle/product/9i -o all -n Checkpoint_971672042 Sun May 15 13:55:53 2005 C+R+IN Checkpoint_903937870 Fri May 13 22:51:10 2005 C+R+ON Checkpoint_901426272 Wed May 11 16:17:52 2005 P+R+ON NetBackup_incr_PROD_955133480 NetBackup_full_PROD_9551
322 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Usage notes ■ ■ ■ ■ ■ ■ ■ This command is supported by Veritas Storage Foundation for Oracle RAC. The dbed_ckptmount command is used to mount a Storage Checkpoint into the file system namespace. Mounted Storage Checkpoints appear as any other file system on the machine and can be accessed using all normal file system based commands. Storage Checkpoints can be mounted as read-only or read-write.
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Usage notes This command is supported by Veritas Storage Foundation for Oracle RAC. ■ The dbed_ckptumount command is used to unmount a mounted Storage Checkpoint from the file system namespace. Mounted Storage Checkpoints appear as any other file system on the machine and can be accessed using all normal file system based commands. When mounted Storage Checkpoints are not required, they can be unmounted.
324 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Usage notes ■ ■ ■ ■ ■ ■ The dbed_ckptpolicy command can be used only on file systems using disk layout Version 6. The VxVM volume set and VxFS Multi-Volume File System features must be enabled to use Storage Checkpoint allocation policies.
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface ■ Two MVS file systems /mvsfs/v1 and /mvsfs/v2 are used for datafiles. ■ File system /mvsfs/v1 is created on volume set mvsvset1. ■ File system /mvsfs/v2 is created on volume set mvsvset2. ■ Volume set mvsvset1 contains volumes mvsv1, mvsv2, and mvsv3. ■ Volume set mvsvset2 contains volumes mvsv4 and mvsv5.
326 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface To update a Storage Checkpoint allocation policy ◆ Use the dbed_ckptpolicy command as follows: $ /opt/VRTS/bin/dbed_ckptpolicy -S ORACLE_SID \ -n -o update -p ckpt_policy Output similar to the following is displayed: File System: /mvsfs/v2 (MVS volumes: mvsv4,mvsv5) Policy: ckpt_sample (MVS volumes: mvsv4) Please enter the volume name(s), separated by space, for the policy ckpt_sample [skip,quit]: mvsv5 Fil
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Prerequisites Usage notes ■ You must be logged on as the database administrator (typically, the user ID oracle). ■ The repository entry for the database must exist and the DBA must be the owner of all file systems to be affected. ■ See the dbed_ckptquota(1M) manual page for more information.
328 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface To display quota values for all file systems in the database ◆ Use the dbed_ckptquota command as follows: $ /opt/VRTS/bin/dbed_ckptquota -S PROD -H /ora10i \ -o display Filesystem Hardlimit Softlimit CurrentUse /ora/prod 50000 40000 136 /ora/testvol01 25000 20000 128 /ora/testvol02 50000 40000 128 /ora/testvol03 50000 40000 0 /ora/testvol04 25000 20000 128 /ora/testvol05 50000 40000
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Usage notes This command is supported by Veritas Storage Foundation for Oracle RAC. ■ The dbed_ckptrollback command rolls an Oracle database back to a specified Storage Checkpoint. You can perform a Storage Rollback for the entire database, a specific tablespace, or list of datafiles. Database rollback for the entire database requires that the database be inactive before Storage Rollback commences.
330 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface To rollback datafiles to a Storage Checkpoint ◆ Use the dbed_ckptrollback command with the -F option as follows: $ /opt/VRTS/bin/dbed_ckptrollback -S PROD -H /oracle/product/9i\ -F /share/oradata1/data01.dbf /share/oradata2/index01.dbf \ -c Checkpoint_903937870 If the Oracle database is running, you must take the datafile offline before running this command. If the datafile is online, the command will fail.
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface You can use the dbed_ckptplan command to manage the Storage Checkpoint Capacity Planning utility at the command line. Before using dbed_ckptplan to manage the Capacity Planning utility, note the following: ■ The dbed_ckptplan command is used to obtain estimates on space usage for Storage Checkpoints.
332 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Storage Foundation for Oracle RAC environment, cloning an existing database can be done on any node within the RAC database cluster. The clone database is started as a single instance on the node on which the dbed_clonedb command is executed.
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Table A-3 dbed_clonedb command options Option Description -S CLONE_SID Specifies the name of the new Oracle SID, which will be the name of the new database instance. -m MOUNT_POINT Indicates the new mount point of the Storage Checkpoint. -c CKPT_NAME Indicates the name of the Storage Checkpoint. -i Runs the command in interactive mode where you must respond to prompts by the system.
334 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Control file 'ora_control2' path not explicitly specified in init file; assuming ORACLE_HOME/dbs All redo-log files found Copying initTEST9i.ora to initNEW9.ora in /local/oracle9/1/testvol Altering db_name in initNEW9.ora Altering control file locations in initNEW9.
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Using environment-specified parameter file /local/oracle9/links/dbs/initTEST9i.ora Default Oracle parameter file found: /local/oracle9/links/dbs/initTEST9i.ora Copying /local/oracle9/links/dbs/initTEST9i.ora to /local/oracle9/1/testvol Control file 'ora_control2' path not explicitly specified in init file; assuming ORACLE_HOME/dbs All redo-log files found Copying initTEST9i.ora to initNEW9.
336 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface To delete a clone database and the Storage Checkpoint used to create it ◆ Use the dbed_clonedbcommand as follows: $ /opt/VRTS/bin/dbed_clonedb -S NEW9 -o umount -d Creating and working with snapplans using dbed_vmchecksnap A snapplan specifies snapshot scenarios for a database (such as online, instant, or offline). You can name a snapplan file whatever you choose.
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Table A-4 Snapplan parameters (continued) Parameter Value SECONDARY_HOST Specifies the name of the host where the clone database will reside. In a Veritas Storage Foundation for Oracle environment, if the primary and secondary hosts are the same, the snapshot volumes will not be deported. In Oracle RAC, SECONDARY_HOST specifies the host name of the CVM master node.
338 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Table A-4 Snapplan parameters (continued) Parameter Value SNAPSHOT_MODE online or offline or instant Specifies whether the database snapshot should be online, offline, or instant. Only online snapshot mode is supported by Veritas Storage Foundation for Oracle RAC. If the snapshot is created while the database is online, the dbed_vmsnap command will put the tablespaces into backup mode.
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Table A-4 Snapplan parameters (continued) Parameter Value ALLOW_REVERSE_RESYNC yes or no By default, reverse resynchronization is off (set equal to no). If it is set to yes, this parameter allows you to restore the original volume from a snapshot. The original database, however, must be down for this operation. In a Veritas Storage Foundation for Oracle RAC environment, this parameter must be set to no.
340 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Usage notes ■ ■ ■ ■ ■ ■ ■ This command is supported by Veritas Storage Foundation for Oracle RAC. In a Veritas Storage Foundation for Oracle RAC environment, the snapplan can be created on any node within the Oracle RAC cluster; however, the -o validate option must be run on the Veritas Volume Manager CVM master node.
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Table A-5 Options for creating a snapplan (continued) Option Description -o validate Validates each parameter in the snapplan and checks whether the snapshot volumes have been configured correctly for creating snapshots, and copies the snapplan to the repository. -o list Lists all the snapplans associated with a specific $ORACLE_SID.
342 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface SNAPSHOT_PLEX_TAG=dbed_flashsnap SNAPSHOT_VOL_PREFIX=SNAP_ ALLOW_REVERSE_RESYNC=no SNAPSHOT_MIRROR=1 To create a snapplan and set the default values in a two-host configuration ◆ Use the dbed_vmchecksnap command as follows: $ /opt/VRTS/bin/dbed_vmchecksnap -S PROD \ -H /oracle/product/9i -f snap2 -o setdefaults -t host2 Warning: This procedure does not apply to Veritas Storage Foundation for Oracle RAC.
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface To validate a snapplan for a snapshot image to be used on the primary host (single instance Oracle) ◆ Use the dbed_vmchecksnap command as follows: $ /opt/VRTS/bin/dbed_vmchecksnap -S PROD -H /oracle/product/9i \ -f snap1 -o validate PRIMARY_HOST is host1 SECONDARY_HOST is host1 The version of PRIMARY_DG-PRODdg is 110. SNAPSHOT_DG is SNAP_PRODdg SNAPSHOT_MODE is online The database is running in archivelog mode.
344 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Examining Oracle volume and disk layout for snapshot Volume prod_db on PRODdg is ready for snapshot. Original plex and DCO log for prod_db is on PRODdg01. Snapshot plex and DCO log for prod_db is on PRODdg02. SNAP_PRODdg for snapshot will include: PRODdg02 ALLOW_REVERSE_RESYNC is no The snapplan snap1 has been created.
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface To list all available snapplans for a specific Oracle database ◆ Use the dbed_vmchecksnap command as follows: $ /opt/VRTS/bin/dbed_vmchecksnap -S PROD -o list The following snapplan(s) are available for PROD: SNAP_PLAN SNAP_STATUS DB_STATUS SNAP_READY snap1 init_full - yes snap2 init_full - yes snap3 init_full - yes The command output displays all available snapplans, their snapshot status (SNAP_S
346 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface STATUS_INFO SNAP_STATUS=init_full Copying or removing a snapplan using dbed_vmchecksnap The dbed_vmchecksnap command allows you to copy or remove snapplans.
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Usage notes ■ ■ ■ ■ ■ ■ Creating and resynchronizing a database are supported by Veritas Storage Foundation for Oracle RAC. Reverse resynchronization is not supported. The dbed_vmsnap command can only be used on the primary host. In an Oracle RAC environment, the dbed_vmsnap command can only be used on the Veritas Volume Manager CVM volume.
348 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Table A-6 dbed_vmsnap command options (continued) Option Description -o Commits the reverse resynchronization changes after you reverse_resync_commit have verified that they are acceptable. Not supported by Veritas Storage Foundation for Oracle RAC. -o reverse_resync_abort Aborts reverse resynchronization and mounts the original volumes back with the file systems that are configured to use the volume.
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface To create a snaphsot image on the CVM master node (Oracle RAC) ◆ Use the dbed_vmsnap command as follows: $ /opt/VRTS/bin/dbed_vmsnap -S PROD -f snap1 -o snapshot dbed_vmsnap started at 2005-04-02 14:15:27 The database is running in archivelog mode. A snapshot of ORACLE_SID PROD is in DG SNAP_PRODdg. Snapplan snap1 is used for the snapshot. Oracle Database server is orasvr.
350 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface To resynchronize your database to a snapshot ◆ Assuming the mount point for the primary database was created and owned by the Oracle DBA user before mounting the VxFS file system, use the dbed_vmsnapcommand as follows: $ /opt/VRTS/bin/dbed_vmsnap -S PROD -f snap1 \ -o reverse_resync_begin dbed_vmsnap started at 2004-04-02 15:53:45 Database PROD (SID=PROD) is running.
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface To commit reverse resynchronization changes ◆ Use the dbed_vmsnap command as follows: Warning: Upon completion of reverse resynchronization, the content of the original database is discarded. Storage Checkpoints taken on either the original database or the clone database before or after the snapshot was created are discarded. Storage Checkpoints taken before the snapshot was created are preserved.
352 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Prerequisites ■ You must be logged in as the Oracle database administrator to use dbed_vmclonedb command. Before you can use the dbed_vmclonedb command, you must create and validate a snapplan and create a snapshot. ■ The volume snapshot must contain the entire database. ■ The system administrator must provide the database administrator with access to the necessary volumes and mount points.
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Table A-7 dbed_vmclonedb options Option Description -S ORACLE_SID For Veritas Storage Foundation for Oracle, specifies the ORACLE_SID, which is the name of the Oracle database instance, for which a snapshot image will be created. For Veritas Storage Foundation for Oracle RAC, specifies the ORACLE_SID, which is the name of the Oracle database instance where the Veritas Volume Manager CVM master node resides.
354 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Table A-7 dbed_vmclonedb options (continued) Option Description -r relocate_path Specifies the initial mount point for the snapshot image. If you are creating a clone in a single-host configuration or cloning an Oracle RAC database, -r is required. Otherwise, it is an optional argument.
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface To clone the primary database on a secondary host automatically in a two-host configuration ◆ Use the dbed_vmclonedb command as follows: $ /opt/VRTS/bin/dbed_vmclonedb -S PROD -g SNAP_PRODdg \ -o recoverdb,new_sid=NEWPROD,server_name=orasvr -f snap2 dbed_vmclonedb started at 2004-04-09 23:03:40 Mounting /clone/arch on /dev/vx/dsk/SNAP_PRODdg/SNAP_arch.
356 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface To clone the primary database manually in a single-host configuration or a RAC cluster 1 Mount the file systems. 2 Create a clone using the dbed_vmclonedb command. $ /opt/VRTS/bin/dbed_vmclonedb -S PROD -g SNAP_PRODdg \ -o mountdb,new_sid=NEWPROD -f snap1,server_name=orasvr -r /clone dbed_vmclonedb started at 2003-04-02 15:34:41 Mounting /clone/prod_db on /dev/vx/dsk/SNAP_PRODdg/SNAP_prod_db.
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface To clone the primary database manually in a two-host configuration 1 Mount the file systems. 2 Create a clone using the dbed_vmclonedb command. $ /opt/VRTS/bin/dbed_vmclonedb -S PROD -g SNAP_PRODdg \ -o mountdb,new_sid=NEWPROD,server_name=orasvr -f snap2 dbed_vmclonedb started at 2003-04-09 23:26:50 Mounting /clone/arch on /dev/vx/dsk/SNAP_PRODdg/SNAP_arch.
358 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface To shut down the clone database and unmount all snapshot file systems in a single-host configuration or in a RAC cluster ◆ Use the dbed_vmclonedb command as follows: $ /opt/VRTS/bin/dbed_vmclonedb -o umount,new_sid=NEWPROD,\ server_name=orasvr -f snap1 -r /clone dbed_vmclonedb started at 2004-04-02 15:11:22 Umounting /clone/prod_db. Umounting /clone/prod_ar.
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface 359 To restart a clone database in a single-host configuration or a RAC cluster ◆ Use the dbed_vmclonedb command as follows: $ /opt/VRTS/bin/dbed_vmclonedb -S PROD -g SNAP_PRODdg \ -o restartdb,new_sid=NEWPROD,server_name=orasvr -f snap1 -r /clone dbed_vmclonedb started at 2004-04-02 15:14:49 Mounting /clone/prod_db on /dev/vx/dsk/SNAP_PRODdg/SNAP_prod_db.
360 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Managing log files using edgetmsg2 You can use the edgetmsg2 utility to manage message log files. You can use the edgetmsg2 utility to write a message to a log file or to the console, read the log file and print to the console, and display the available log files.
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Table A-8 edgetmsg2 options (continued) Option Description -o report[,no_archive] Displays the available log files. You can specify ,no_archive to exclude log files from the utility output. -t from_time[,to_time] Reduces the length of the utility output by specifying the time range to include. This option must be used together with the -o list option. Use the following format: yyy-mm-dd HH:MM:SS.
362 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Displaying I/O mapping and statistics using vxstorage_stats You can use the vxstorage_stats command to display I/O mapping and statistics about Veritas File System files one file at a time. The statistics are recorded only for VxFS files and VxVM volumes. These statistics show I/O activity.
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface For example, to display statistics two times with a time interval of two seconds: $ /opt/VRTSdbed/bin/vxstorage_stats -s -i2 -c2 \ -f /data/system01.dbf Mapping tablespaces to disks using dbed_analyzer The dbed_analyzer command provides tablespace-to-physical disk mapping information for all the datafiles in a specified database.
364 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface To obtain storage mapping information sorted by tablespace ◆ Use the dbed_analyzercommand with the -f filenameand -o sort=tbs options: $ /opt/VRTS/bin/dbed_analyzer -S $ORACLE_SID -H $ORACLE_HOME \ -o sort=tbs -f filename Output similar to the following is displayed in the file filename: TBSNAME SYSTEM TEMP TEMP SYSAUX ITEM ITM_IDX PRODID_IDX QTY_IDX ROLL_1 ROLL_2 ORDERS ORD_IDX TY_IDX ITM_IDX ROLL_1 QTY_ID
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface 365 To obtain storage mapping information sorted by disk ◆ Use the dbed_analyzer command with the -f filename and -o sort=disk options: $ /opt/VRTS/bin/dbed_analyzer -S $ORACLE_SID -H $ORACLE_HOME -o \ sort=disk -f filename Output similar to the following is displayed in the file filename: DEVICE c3t21000020379DBD5Fd0 c3t21000020379DBD5Fd0 c3t21000020379DBD5Fd0 c3t21000020379DBD5Fd0 c3t21000020379DBD5Fd0 c3t210
366 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Prerequisites ■ An Oracle database must be up and running. ■ Run the dbed_update command before running any of the Database Dynamic Storage Tiering commands. You should also run the dbed_update command if any of the database files change. Because the Database Dynamic Storage Tiering commands retrieve database information from the repository, the repository must be up to date.
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Table A-11 367 dbdst_admin command options (continued) Option Description minclass= Minimum number of storage classes allowed in the database. Default value is 2. sweepinterval= Interval for file sweeping for file relocation. Default value is 1, which means one per day. If this value is set to 0, all scheduled sweep tasks will become unscheduled. sweeptime= Time per day for the file sweep to take place.
368 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface For example, to add a class called tier1 for database PROD, and to set up a purge interval of one, meaning that the file statistics will be gathered for one day and then summarized and purged, use the dbdst_admin command as follows: $ /opt/VRTS/bin/dbdst_admin -S PROD -o addclass=tier1:"Fast Storage",\ purgeinterval=1 Setting up storage classes for Database Dynamic Storage Tiering using dbdst_admin The dbdst
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface 369 Converting a VxFS file system to a VxFS multi-volume file system for Database Dynamic Storage Tiering using dbdst_convert To convert your existing VxFS file system to a VxFS multi-volume file system, you must convert a single volume to a volume set. When you convert to a volume set using the dbdst_convert command, the original volume will be renamed to a new volume name.
370 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface storage classes defined as PRIMARY and SECONDARY. The volumes will be assigned as follows: ■ PRIMARY storage class will contain volumes oradata_b4vset and new_vol1. ■ SECONDARY storage class will contain volume new_vol2. Classifying volumes into a storage class for Database Dynamic Storage Tiering using dbdst_classify Before creating a DST policy or manually moving data, assign classes to your volumes.
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Table A-12 dbdst_show_fs command options Option Description -S $ORACLE_SID Specifies the ORACLE_SID, which is the name of the Oracle instance. -o volume Displays the free space on volumes in each class. -m Specifies the mount point. Before displaying the free space on a storage class, review the following information: Prerequisites ■ Make sure the file system is mounted.
372 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Removing volumes from a storage class for Database Dynamic Storage Tiering using dbdst_rmvol You may need to remove a volume from a volume set. To remove a volume, use the dbdst_rmvol command. Before removing a volume, review the following information: Usage notes The database must be inactive when removing volumes from a storage class.
Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Table A-13 dbdst_file_move command options (continued) Option Description -R Removes the policy for the specified object. Before relocating a file, review the following information: Usage notes ■ Multiple partitions cannot reside on the same tablespace.
374 Veritas Storage Foundation for Oracle Command Line Interface About the command line interface Prerequisites ■ To use this command for Oracle, the ORACLE_SID environment variable must be set. ■ You must be logged in as the database administrator to use this command. Usage notes ■ The command expects to find a file named in the directory where the command is run. The mkqio.dat file contains a list of the Quick I/O files used by the database and their sizes.
Appendix B Using third-party software to back up files This appendix includes the following topics: ■ About backing up and restoring Quick I/O files using Oracle RMAN ■ About backing up and restoring Oracle Disk Manager files using Oracle RMAN ■ About backing up and restoring Quick I/O files using Legato NetWorker ■ About using backup software other than Veritas NetBackup to back up and restore ODM files About backing up and restoring Quick I/O files using Oracle RMAN Quick I/O files are treated a
376 Using third-party software to back up files About backing up and restoring Oracle Disk Manager files using Oracle RMAN Because Quick I/O files are treated as raw devices, the Quick I/O file must exist and have the necessary space preallocated to it before the file is restored using RMAN. Space can be preallocated to the file when the file is created using the qiomkfile command.
Using third-party software to back up files About backing up and restoring Quick I/O files using Legato NetWorker See the odmmkfile(1) manual page.
378 Using third-party software to back up files About using backup software other than Veritas NetBackup to back up and restore ODM files -rw-r--r-- 1 oracle dba 1048576 lrwxrwxrwx 1 oracle dba 22 Oct 20 17:39 Oct 20 17:39 .dbfile dbfile ->\ .dbfile::cdev:vxfs: The command for backing up the /db01 directory using rawasm would look like: << /db01 >> rawasm: dbfile skip: .
Appendix C Veritas Database FlashSnap status information This appendix includes the following topics: ■ Database FlashSnap snapshot status and database status Database FlashSnap snapshot status and database status The Veritas Database FlashSnap functionality provides both snapshot status information and snapshot database status information for various stages of snapplan and snapshot procedures. You can view the status information through the CLI and through the GUI.
380 Veritas Database FlashSnap status information Database FlashSnap snapshot status and database status Table C-1 Snapshot status values SNAP_STATUS Completed operations Allowed operations init_full ■ init_db ■ dbed_vmchecksnap -o validate ■ Ensure that your storage configuration has been set up correctly. -f snapplan (failed) snapshot_start ■ dbed_vmsnap -o snapshot (failed) ■ Contact your system administrator for help.
Veritas Database FlashSnap status information Database FlashSnap snapshot status and database status Table C-1 SNAP_STATUS Snapshot status values (continued) Completed operations Allowed operations reverse_resync_begin_start ■ dbed_vmsnap -o reverse_resync_begin (failed) ■ Contact Veritas support.
382 Veritas Database FlashSnap status information Database FlashSnap snapshot status and database status Table C-1 Snapshot status values (continued) SNAP_STATUS Completed operations Allowed operations recoverdb_end ■ dbed_vmclonedb -o recoverdb (successful) ■ dbed_vmclonedb -o umount umount_start ■ dbed_vmclonedb -o umount (failed) ■ Verify that your file system(s) are not busy and retry the command.
Glossary address-length pair Identifies the starting block address and the length of an extent (in file system or logical blocks). archived log mode Used to retrieve information on transactions that occur during a hot backup. asynchronous I/O A format of I/O that performs non-blocking reads and writes. This enables the system to handle multiple I/O requests simultaneously.
384 Glossary cluster A set of hosts that share a set of disks. cluster-shareable disk A disk group in which the disks are shared between more than one host. group cold backup The process of backing up a database that is not in active use. command launcher A graphical user interface (GUI) window that displays a list of tasks that can be performed by Veritas Volume Manager or other objects. Each task is listed with the object type, task (action), and a description of the task.
Glossary DB2), where data is stored in tables and generally accessed by one or more keys and Flat File Databases, where data is not generally broken up into tables and relationships. Databases generally provide tools and/or interfaces to retrieve data. datafile A physical database attribute that contains database data. An Oracle datafile can only be associated with a single database. One or more datafiles form a logical database storage unit called a tablespace. DCO See "data change object (DCO).
386 Glossary internally defined unique ID. The root disk group (rootdg) is a special private disk group disk name A Veritas Volume Manager logical or administrative name chosen for the disk, such as disk03. The term disk media name is also used to refer to the disk name. DMP See “Dynamic Multipathing.” DSS See “Decision Support Systems.
Glossary gigabyte A measure of memory or storage. A gigabyte is approximately 1,000,000,000 bytes (technically, 2 to the 30th power, or 1,073,741,824 bytes). Also GB, Gbyte, and G-byte. HFS High Performance File System. The HP-UX name for the file system derived from the 4.2 Berkeley Fast File System.
388 Glossary large file system A file system more than two gigabytes in size. VxFS, in conjunction with VxVM, supports large file systems. latency The amount of time it takes for a given piece of work to be completed. For file systems, this typically refers to the amount of time it takes a given file system operation to return to the user. Also commonly used to describe disk seek times.
Glossary NBU See “Veritas NetBackup (NBU).” node One of the hosts in a cluster. object (VxVM) An entity that is defined to and recognized internally by the Veritas Volume Manager. The VxVM objects include volumes, plexes, subdisks, disks, and disk groups. There are two types of VxVM disk objects—one for the physical aspect of the disk and the other for the logical aspect of the disk. OLTP See “Online Transaction Processing.
390 Glossary I/O and direct I/O to and from the disk device, as well as bypassing the UNIX single-writer lock behavior for most file system files. Quick I/O file A regular UNIX file that is accessed using the Quick I/O naming extension (::cdev:vxfs:). RAID A Redundant Array of Independent Disks (RAID) is a disk array set up with part of the combined storage capacity used for storing duplicate information about the data stored in that array.
Glossary snapped volume A volume whose exact image has been used to create a snapshot volume. snapshot A point-in-time image of a volume or file system that can be used as a backup. snapshot file system An exact copy of a mounted file system, at a specific point in time, that is used for online backup. A snapshot file system is not persistent and it will not survive a crash or reboot of the system. snapshot volume An exact copy of a volume, at a specific point in time.
392 Glossary tablespace In an Oracle database, an allocation of space used to hold schema objects (triggers, stored procedures, tables, etc.). A tablespace is associated with one or more datafiles. terabyte A measure of memory or storage. A terabyte is approximately 1,000,000,000,000 bytes (technically, 2 to the 40th power, or 1,000 GB). Also TB. throughput A measure of work accomplished in a given amount of time.
Index Symbols buffer cache 301 /etc/vx/vxdba/logs/ckptplan.
394 Index clone databases, creating 169, 267, 331, 351 cloning a database.
Index Database FlashSnap (continued) displaying a snapplan 258 host and storage requirements 225 options 222 Oracle RAC configuration 224 overview 38, 218, 243 planning considerations 223 removing a snapplan 258 removing a snapshot volume 280 removing a snapshotis the rest of the text in this index term supposed to be a separate index term?--mb volumesnapshot volumes removing 280 resynchronizing 279 reverse resynchronizing 276 selecting the snapshot mode 223 setting up hosts 223 single-host configuration 2
396 Index displaying (continued) Storage Checkpoints 41 tablespace 41 DMP 30 DMP-supported disk arrays 30 double buffering 77, 102 DRL 26, 52.
Index I I/O asynchronous 76 Cached Quick I/O 32, 39 direct 77 displaying Storage Mapping statistics 137 kernel asynchronous 76 load balancing 298 mapping and statistics 362 performance data 297 Quick I/O 32 sequential 33 statistics obtaining 288 improving database performance 76 incremental backups 42 initial_extent_size tunable parameter 293 K kernel asynchronous I/O 76 kernel write locks 77 L large file systems 35 support for 57 large files enabling 58 support for 35, 57 largefiles option 58 Legato Net
398 Index online transaction processing 25, 78 options largefiles and nolargefiles 35 Oracle autoextend feature 96 media recovery 175 recovery 174 Recovery Manager (RMAN) 375 Oracle configuration environment saving 314 Oracle datafile header size 80 Oracle Disk Manager 119 benefits 120 converting Quick I/O files 128 disabling 131 migrating files to 128 preparing existing databases for use with 127 restoring files using NetBackup 285, 376 setting up 125 Oracle Enterprise Manager 148 Oracle Managed Files 12
Index RAID-0 24 RAID-0+1 25 RAID-1 24–25 RAID-1+0 25 RAID-5 25, 52 choosing 51 performance 52 RAID-5 log 52 raw devices running databases on 32 rawasm directive 377 read-ahead algorithm for Cached Quick I/O 103 read_nstream 301 read_nstream tunable parameter 292 read_pref_io 301 read_pref_io tunable parameter 291 recovering using Storage Checkpoints 165 recreating data using RAID-5 25 recreating temporary tablespaces 91 redo logs 43 configuration guidelines 55 creating a file system 55 for Oracle recovery
400 Index snapshots aborting resynchronization 350 aborting reverse resynchronization 350 and FastResync 28 commiting reverse resynchronization changes 351 creating 260, 346, 348 resynchronizing 346, 349 reverse resynchronizing 346, 350 SORT_AREA_SIZE 300 space usage displaying statistics and monitoring 42 spanning 20, 23 defined 24 spare disks 29 sparse files 85, 89–90 starting Capacity Planning utility 207 statistics volume I/O 288 Storage Checkpoint Capacity Planning.
Index tunefstab file adding tuning parameters to 106 Tuning file I/O statistics 296 VxFS 289 VxFS I/O parameters 291 tuning for database performance 300 vxfs 289 VxVM 287 tuning I/O parameters 291 tuning parameters adding to tunefstab file 106 U umount command 59 unattended backups 42 unmounting a file system 60 Storage Checkpoints 41 unmounting file systems 59 upgrade from raw devices 128, 180 from UFS 178 upgrading from earlier VxFS layout versions 179 from UFS 179 using Database Dynamic Storage Tiering
402 Index vxstorage_stat command 135 vxstorage_stats 135 vxstorage_stats command 308, 362 vxtunefs command 113, 301 commands vxtunefs 106–107 vxupgrade command 180 VxVM . See Veritas Volume Manager overview 20 tuning 287 vxvmconvert 177 W workloads write-intensive 52 write_nstream tunable parameter 292 write_pref_io tunable parameter 292 write_throttle tunable parameter 295 X XOR .
