VERITAS Storage Foundation 4.1 for Oracle Administrator’s Guide HP-UX 11i v2 Manufacturing Part Number: 5991-1292 September 2005 Edition 1 Printed in the United States © Copyright 2005 - 2006 Hewlett-Packard Development Company L.P.
Legal Notices 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 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix How This Guide is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerelease 8 September 2005, 8:55am Volume Resynchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Dirty Region Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 SmartSync Recovery Accelerator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Volume Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerelease 8 September 2005, 8:55am Quotas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Cluster Functionality (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 VERITAS Storage Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 VERITAS Extension for Oracle Disk Manager . . . . . . . . . . . . . . . . . . .
Prerelease 8 September 2005, 8:55am Controlling Fragmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Types of Fragmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Monitoring Fragmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Defragmenting a File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerelease 8 September 2005, 8:55am Chapter 4. Using VERITAS Cached Quick I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Understanding Cached Quick I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 How Cached Quick I/O Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 How Cached Quick I/O Improves Database Performance . . . . . . . . . . . . . . . . . . . . . . . . .
Prerelease 8 September 2005, 8:55am Setting Up VERITAS Extension for Oracle Disk Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Oracle 10g . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Oracle9i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Preparing Existing Database Storage for Oracle Disk Manager . . . . . . . . . . . . . . . . .
Prerelease 8 September 2005, 8:55am Converting From Raw Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Chapter 8. Using Storage Checkpoints and Storage Rollback . . . . . . . . . . . . . . . . . . . . . . . . 145 Using Storage Checkpoints and Storage Rollback for Backup and Restore . . . . . . . . . . . . . 146 Understanding Storage Checkpoints and Storage Rollback . . . . . . . . . . . . . . . . . . . . . . .
Prerelease 8 September 2005, 8:55am How VERITAS Database FlashSnap Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Typical Problems Database FlashSnap Solves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Database FlashSnap Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Using Database FlashSnap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerelease 8 September 2005, 8:55am Restarting a Clone Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 Recreating Oracle tempfiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Resynchronizing the Snapshot to Your Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 Resynchronizing Your Database to the Snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerelease 8 September 2005, 8:55am Using Volume Manager FlashSnap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 Removing a Clone Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 Removing a VM FlashSnap Clone Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 Removing a Storage Checkpoint Clone Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerelease 8 September 2005, 8:55am Aborting the Reverse Resychronization Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303 Viewing the Snapplan Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 Maintaining Your System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 Rescanning the Database Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerelease 8 September 2005, 8:55am Managing Storage Checkpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 Creating Storage Checkpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 Displaying Storage Checkpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337 Mounting Storage Checkpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerelease 8 September 2005, 8:55am Tuning VxFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390 Monitoring Free Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390 Monitoring Fragmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390 Tuning VxFS I/O Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerelease 8 September 2005, 8:55am Saving the Oracle Configuration Environment Using dbed_saveconfig . . . . . . . . . . . . . 417 Creating Storage Checkpoints Using dbed_ckptcreate . . . . . . . . . . . . . . . . . . . . . . . . . . 419 Displaying Storage Checkpoints Using dbed_ckptdisplay . . . . . . . . . . . . . . . . . . . . . . . 421 Scheduling Storage Checkpoints Using dbed_ckptcreate and cron . . . . . . . . . . . . . . 423 Scheduling Storage Checkpoint Creation in a cron Job . . . . . . . . . . .
Prerelease 8 September 2005, 8:55am Mapping Tablespaces to Disks Using dbed_analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476 Identifying VxFS Files to Convert to Quick I/O Using qio_getdbfiles . . . . . . . . . . . . . . 478 Converting VxFS Files to Quick I/O Using qio_convertdbfiles . . . . . . . . . . . . . . . . . . . . 479 Recreating Quick I/O Files Using qio_recreate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481 Appendix B.
Prerelease 8 September 2005, 8:55am Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VERITAS Storage Foundation for Oracle 1 This chapter provides an overview of the features, components, and database-related functionality of VERITAS Storage Foundation for Oracle.
Prerelease 8 September 2005, 8:54am VERITAS Storage Foundation for Oracle VERITAS Storage Foundation for Oracle Standard Edition/Enterprise Edition There are two versions of this product: ◆ VERITAS Storage Foundation for Oracle Standard Edition ◆ VERITAS Storage Foundation for Oracle Enterprise Edition The Enterprise Edition contains everything in the Standard Edition plus Storage Mapping, Database FlashSnap, Storage Checkpoints, and Storage Rollback.
VERITAS Storage Foundation for Oracle ◆ Prerelease 8 September 2005, 8:54am VERITAS Storage Mapping Storage Mapping, a feature of the Enterprise Edition, lets you take full advantage of Oracle storage mapping to map datafiles to physical devices and display storage object I/O statistics. Oracle’s file mapping (I/O topology) feature was introduced beginning with Oracle9i Release 2.
Prerelease 8 September 2005, 8:54am ◆ VERITAS Storage Foundation for Oracle VERITAS Extension for Oracle Disk Manager VERITAS Extension for Oracle Disk Manager is a custom storage interface designed specifically for Oracle9i and 10g. Oracle Disk Manager allows Oracle9i and 10g to improve performance and manageability system bandwidth through an improved Application Programming Interface (API) that contains advanced kernel support for file I/O.
VERITAS Volume Manager Prerelease 8 September 2005, 8:54am VERITAS Volume Manager Databases require their storage media to be robust and resilient to failure. It is vital to protect against hardware and disk failures and to maximize performance using all the available hardware resources. Using a volume manager provides this necessary resilience and eases the task of management. A volume manager can help you manage hundreds of disk devices and makes spanning, striping, and mirroring easy.
Prerelease 8 September 2005, 8:54am VERITAS Volume Manager ◆ Storage Expert—helps diagnose configuration problems with VxVM. ◆ Cluster Volume Manager (CVM)—separately licensed, optional feature that allows you to use VxVM in a cluster environment. ◆ 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.
VERITAS Volume Manager Prerelease 8 September 2005, 8:54am You can move a disk group and its components as a unit from one host to another host. For example, you can move volumes and file systems that belong to the same database and are created within one disk group as a unit. You must configure a given volume from disks belonging to one disk group. In releases before VERITAS Storage Foundation 4.0 for Oracle, the default disk group was rootdg.
Prerelease 8 September 2005, 8:54am VERITAS Volume Manager Striping (RAID-0) Striping is a technique of mapping data so that the data is interleaved among multiple physical disks. Data is allocated in equal-sized units (called stripe units) that are interleaved between the disks. Each stripe unit is a set of contiguous blocks on a disk. A stripe consists of the set of stripe units at the same position across all columns. A column is a set of one or more subdisks within a striped plex.
VERITAS Volume Manager Prerelease 8 September 2005, 8:54am For databases that support online transaction processing (OLTP) workloads, we recommend either mirrored-stripe or striped-mirror volumes to improve database performance and reliability. For highest availability, we recommend striped-mirror volumes (RAID 1+0). RAID-5 (Striping with Parity) RAID-5 provides data redundancy through the use of parity (a calculated value that the system uses to reconstruct data after a failure).
Prerelease 8 September 2005, 8:54am VERITAS Volume Manager take a long time. You can significantly reduce resynchronization time by using Dirty Region Logging (DRL) for mirrored volumes or by making sure that RAID-5 volumes have valid RAID-5 logs. However, using logs can slightly reduce the database write performance. For most database configurations, we recommend using dirty region logs or the RAID-5 logs when mirrored or RAID-5 volumes are used.
VERITAS Volume Manager Prerelease 8 September 2005, 8:54am Volume Snapshots A volume snapshot is a point-in-time image of a volume.
Prerelease 8 September 2005, 8:54am VERITAS Volume Manager Persistent FastResync Non-persistent FastResync has been augmented by the introduction of persistent FastResync. Unlike non-persistent FastResync, Persistent FastResync keeps the 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.
VERITAS Volume Manager Prerelease 8 September 2005, 8:54am VxVM detects I/O failures on volumes and relocates the affected portions to disks designated as spare disks or free space within the disk group. VxVM then reconstructs the volumes that existed before the failure and makes them redundant and accessible again. The hot-relocation feature is enabled by default and is recommended for most database configurations.
Prerelease 8 September 2005, 8:54am VERITAS Volume Manager Storage Expert components include a set of rule scripts and a rules engine. The rules engine runs the scripts and produces ASCII output, which is organized and archived by Storage Expert’s report generator. This output contains information about areas of VxVM configuration that do not meet the set criteria. By default, output is sent to the screen, but you can redirect it to a file using standard UNIX redirection.
VERITAS Database FlashSnap Prerelease 8 September 2005, 8:54am VERITAS Database FlashSnap VERITAS Database FlashSnap is a feature included with VERITAS Storage Foundation for Oracle Enterprise Edition. It is also a separately licensed option available with VERITAS Storage Foundation for Oracle Standard Edition. VERITAS Database FlashSnap offers a flexible and efficient means of managing business-critical data.
Prerelease 8 September 2005, 8:54am VERITAS File System VERITAS File System VERITAS File System (referred to as VxFS) is an extent-based, intent logging file system intended for use in UNIX environments that deal with large volumes of data and that require high file system performance, availability, and manageability. VxFS also provides enhancements that make file systems more viable in database environments.
VERITAS File System Prerelease 8 September 2005, 8:54am 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.
Prerelease 8 September 2005, 8:54am VERITAS File System Defragmentation Utility 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.
VERITAS File System Prerelease 8 September 2005, 8:54am The QoSS option is built on the multi-volume support technology introduced in this release. Using QoSS, you can map more than one device to a single file system. You can then configure policies that automatically relocate files from one device to another, or relocate files by running file relocation commands.
Prerelease 8 September 2005, 8:54am VERITAS File System The Storage Rollback facility can then be used for rolling back the file system image to the point in time when the Storage Checkpoints were taken. In addition, 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.
VERITAS File System Prerelease 8 September 2005, 8:54am 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. For details on using VxFS quotas, see the VERITAS File System Administrator’s Guide.
Prerelease 8 September 2005, 8:54am VERITAS Storage Mapping VERITAS Storage Mapping VERITAS Storage Mapping is a feature included with VERITAS Storage Foundation for Oracle Enterprise Edition. VERITAS has defined and implemented a library called VERITAS Federated Mapping Service (VxMS) that provides a mapping interface to VxFS file systems, VxVM volumes, and physical disks.
VERITAS Extension for Oracle Disk Manager Prerelease 8 September 2005, 8:54am VERITAS Extension for Oracle Disk Manager VERITAS Extension for Oracle Disk Manager is a custom storage interface defined by Oracle Corporation beginning with Oracle9i. Oracle Disk Manager allows Oracle9i to exploit system bandwidth through an improved Application Programming Interface (API) that contains advanced kernel support for file I/O.
Prerelease 8 September 2005, 8:54am VERITAS VxDBA Menu Utility VERITAS VxDBA Menu Utility The VxDBA menu utility helps you manage the storage used by databases.
VERITAS Storage Foundation for Oracle Graphical User Interface Prerelease 8 September 2005, 8:54am VERITAS Storage Foundation for Oracle Graphical User Interface An alternative to the command line interface, the VERITAS Storage Foundation for Oracle GUI allows you to manage the storage used by databases. You can use the GUI to: ◆ Display database, tablespace, datafile, and file system information and manage the database state. ◆ Create, display, mount, unmount, and remove Storage Checkpoints.
Prerelease 8 September 2005, 8:54am VERITAS NetBackup (Optional) VERITAS NetBackup (Optional) VERITAS NetBackup provides backup, archive, and restore capabilities for database files and directories contained on client systems in a client-server network. NetBackup server software resides on platforms that manage physical backup storage devices. The NetBackup server provides robotic control, media management, error handling, scheduling, and a repository of all client backup images.
VERITAS Storage Foundation/High Availability for Oracle (Optional) Prerelease 8 September 2005, 8:54am VERITAS Storage Foundation/High Availability for Oracle (Optional) VERITAS Storage Foundation/High Availability (HA) (VCS) for Oracle lets database administrators integrate multiple servers into high availability database configurations that can significantly reduce the down time of Oracle databases caused by a system hardware or software failure.
Prerelease 8 September 2005, 8:54am Chapter 1, VERITAS Storage Foundation for Oracle VERITAS Storage Foundation/High Availability for Oracle (Optional) 47
VERITAS Storage Foundation/High Availability for Oracle (Optional) 48 Prerelease 8 September 2005, 8:54am VERITAS Storage Foundation for Oracle Administrator’s Guide
Preface VERITAS Storage Foundation for Oracle, formerly known as VERITAS Database Edition for Oracle, is an integrated set of system software enhancements and configuration guidelines that combine to help Oracle database administrators configure a database system with high performance, availability, manageability, and reliability. How This Guide is Organized This guide is organized as follows: Chapters in This Guide Chapter Description Chapter .
Prerelease 8 September 2005, 8:54am How This Guide is Organized Chapters in This Guide Chapter Description Chapter . “Using Storage Checkpoints Discusses how to use Storage Checkpoint and Storage Rollback. and Storage Rollback” on page 162 Chapter . “Using the Space Capacity Planning Utility for Storage Checkpoints” on page 184 Discusses how to use the Storage Checkpoint Capacity Planning utility to plan space for Storage Checkpoints. Chapter .
Related Documentation Prerelease 8 September 2005, 8:54am Related Documentation The following guides, along with the online help, comprise the VERITAS Storage Foundation for Oracle documentation set: Guides in VERITAS Storage Foundation for Oracle Documentation Set Guide Title Filename VERITAS Storage Foundation Release Notes sf_notes.pdf VERITAS Storage Foundation Installation Guide sf_install.pdf VERITAS Storage Foundation for Oracle Administrator’s Guide sf_ora_admin.
Prerelease 8 September 2005, 8:54am Conventions Conventions Typographical and Symbolic The following tables explain the typographical and symbolic conventions used throughout the guides: Typeface Conventions Typeface Usage Examples monospace Computer output, files, directories, software elements such as command options, function names, and parameters Read tunables from the /etc/vx/tunefstab file.
Technical Support Prerelease 8 September 2005, 8:54am Symbolic Conventions Symbol Usage Examples | In a command synopsis, a vertical bar separates mutually exclusive arguments mount [ suid | nosuid ] blue text In PDF and HTML files, click on these See “Using Snapshots for Database Backup” on active hyperlinks to move to the specified page 97 for more information. location Notes and Cautions Note A Note provides information that makes it easier to use the product or helps you avoid problems.
Prerelease 8 September 2005, 8:54am Documentation Feedback Documentation Feedback Your feedback on product documentation is important to us. Send suggestions for improvements and reports on errors or omissions to sfuadocs@veritas.com. Include the title and part number of the document (located in the lower left corner of the title page), and chapter and section titles of the text on which you are reporting. Our goal is to ensure customer satisfaction by providing effective, quality documentation.
2 Setting Up Databases This chapter describes how to use VERITAS Volume Manager and VERITAS File System to set up optimal system configurations for Oracle Databases.
Setting Up a New Database Prerelease 8 September 2005, 8:54am Setting Up a New Database VERITAS Storage Foundation for Oracle contains a combination of performance, management, and high availability features. This section provides an overview of the steps to follow if you are using VERITAS Storage Foundation for Oracle to set up a new database. ▼ To set up a new database using VERITAS Storage Foundation for Oracle 1.
Prerelease 8 September 2005, 8:54am Setting Up a New Database configuration after your database files have been converted. See the VERITAS Volume Manager’s Administrator’s Guide for detailed information about VxVM’s online relayout feature. b. If you are using Oracle8i, convert all database files to Quick I/O files. See “Converting Oracle Files to Quick I/O Files” on page 94. For Oracle9i, you simply need to link the ODM library. See “Setting Up VERITAS Extension for Oracle Disk Manager” on page 130.
Setting Up a Disk Group Prerelease 8 September 2005, 8:54am Setting Up a Disk Group Before creating file systems for a database, set up a disk group for each database. A disk group lets you group disks, volumes, file systems, and files that are relevant to a single database into a logical collection for easy administration.
Prerelease 8 September 2005, 8:54am Creating a Disk Group for a Database Creating a Disk Group for a Database You can use the vxdg command or the graphical user interface (GUI) to create a new disk group. A disk group must contain at least one disk at the time it is created. You also have the option to create a shared disk group for use in a cluster environment. Disks must be placed in disk groups before they can be used by VxVM.
Creating a Disk Group for a Database Prerelease 8 September 2005, 8:54am # /opt/VRTS/bin/vxdg init PRODddg PRODdg01= Example To create a disk group named PRODdg on a raw disk partition, where the disk name PRODdg01 references the disk within the disk group: # /opt/VRTS/bin/vxdg init PRODdg PRODdg01=Disk_0 ▼ To create a new disk group using the GUI 1. Select the Disk Groups folder. 2. Select Actions > New Disk Group. The New Disk Group wizard welcome appears. 3.
Prerelease 8 September 2005, 8:54am Creating a Disk Group for a Database 8. Click None, if you do not want to organize the disk group. Otherwise, click any of the other organization categories under Organize Disk Group By to create an ISP disk group (refer to Organizing Disk Groups). 9. If you choose an organization principle other than None, the Specify Pool Names screen appears. Specify the names for the Data pool and the Clone pool and click Next.
Adding Disks to a Disk Group Prerelease 8 September 2005, 8:54am Adding Disks to a Disk Group When a disk group is first created, it contains only a single disk. You may need to add more disks to the disk group. This section describes how to add disks to a disk group using the vxdg command or the GUI. If you have many disks to add to the disk group, it is easier to use the vxdg command.
Prerelease 8 September 2005, 8:54am 4. Adding Disks to a Disk Group Complete the Add Disk to Dynamic Group wizard as follows: Disk group name: From the pull-down menu, select the group you want to add the disk to. To add the disk to a new disk group, click the New disk group button and enter the name of the new disk group in the dialog box. Available disks: Move the disk to be added from Available disks to Selected disks. Selected disks: 5.
Selecting a Volume Layout Prerelease 8 September 2005, 8:54am Selecting a Volume Layout VERITAS Volume Manager offers a variety of layouts that allow you to configure your database to meet performance and availability requirements. The proper selection of volume layouts provides optimal performance for the database workload. An important factor in database performance is the tablespace placement on the disks. Disk I/O is one of the most important determining factors of your database’s performance.
Prerelease 8 September 2005, 8:54am Selecting a Volume Layout Volume Configuration Guidelines Follow these guidelines when selecting volume layouts: ◆ redo logs - Put the redo logs on a file system created on a striped and mirrored (RAID-0+1) volume separate from the user tablespaces or data files. Stripe multiple devices to create larger volumes if needed. Use mirroring to improve reliability. Do not use VxVM RAID-5 for redo logs.
Creating a Volume Prerelease 8 September 2005, 8:54am Creating a Volume VERITAS Volume Manager uses logical volumes to organize and manage disk space. A volume is made up of portions of one or more physical disks, so it does not have the limitations of a physical disk. For databases where the data storage needs to be resilient and the data layout needs to be optimized for maximum performance, we recommend using VxVM.
Prerelease 8 September 2005, 8:54am ▼ Creating a Volume To create a volume using the GUI 1. Under Disk Groups under the selected host in the left pane, click on the disk group to be used to create the volume. 2. Choose Actions > New Volume. You are asked if you want Volume Manager to select the disks to use or if you want to select them manually. 3. Select Manually select disks to use with this volume, then click Next. 4. The Select Disks to use for Volume screen appears.
Creating a Volume 9. Prerelease 8 September 2005, 8:54am ◆ RAID-5 ◆ Mirrored Select the required options Option Notes Mirror Info: ◆ To mirror the volume, select Mirrored. In the Total Number of Mirrors field, enter the total number of mirrors for the volume. Note Concatenated mirrored volumes are mirrored by default. Initialize zero: ◆ No layered volumes: ◆ Enable FastResync ◆ Enable logging To clear the volume before enabling it for general use, select Initialize Zero.
Prerelease 8 September 2005, 8:54am Creating a Volume Set Creating a Volume Set Volume Sets enable the use of the Multi-Volume Support feature with VERITAS File System (VxFS). It is also possible to use the VERITAS Enterprise Administrator (VEA) to create and administer volumes sets. For more information, see the VEA online help. Note For details regarding usage of the vxvset command, see the vxvset(1M) manual page. Note Most VxVM commands require superuser or equivalent privileges.
Creating a Volume Set Prerelease 8 September 2005, 8:54am For example, to create a volume set named myvset that contains the volume vol1, in the disk group mydg, you would use the following command: # /opt/VRTS/bin/vxvset -g mydg -t vxfs make myvset vol1 Note For further details on Creating a Volume Set, please refer to the VERITAS Volume Manager Administrator’s Guide.
Prerelease 8 September 2005, 8:54am Adding a Volume to a Volume Set Adding a Volume to a Volume Set Having created a volume set containing a single volume, you can use the following command to add further volumes to the volume set: # /opt/VRTS/bin/vxvset [-g diskgroup] [-f] addvol volset volume For example, to add the volume vol2, to the volume set myvset, use the following command: # /opt/VRTS/bin/vxvset -g mydg addvol myvset vol2 Caution The -f (force) option must be specified if the volume being add
File System Creation Guidelines Prerelease 8 September 2005, 8:54am File System Creation Guidelines Follow these guidelines when creating VxFS file systems: ◆ To take advantage of Quick I/O, online administration, fast recovery of the VxFS file system, and superior reliability features, select vxfs as the file system type. ◆ Specify the maximum log size when creating file systems for databases.
Prerelease 8 September 2005, 8:54am Creating a VxFS File System Creating a VxFS File System Always specify vxfs as the file system type to take advantage of the Quick I/O, Storage Rollback, online administration, fast recovery of the VxFS file system, and superior reliability features. The GUI lets you add a file system on a new volume during the volume creation process.
Creating a VxFS File System Prerelease 8 September 2005, 8:54am Example To create a VxFS file system that supports files larger than 2GB 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.
Prerelease 8 September 2005, 8:54am Mount Options: Creating a VxFS File System ◆ ◆ ◆ ◆ ◆ ◆ 4. Enter the mount point for the file system, if you want the file system mounted at system startup. Select the Create mount point checkbox if you want the system to create the mount point if it does not already exist. Select the Read only and Honor setuid checkboxes, as required.
Creating a VxFS File System Caution Prerelease 8 September 2005, 8:54am 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. Multi-volume Support The multi-volume support feature enabled by Version 6 disk layout allows several volumes to be represented by a single logical object, known as a volume set.
Prerelease 8 September 2005, 8:54am Mounting a File System Mounting a File System After creating a VxFS file system, mount the file system using the mount command. By default, the mount command tries to enable Quick I/O. If Quick I/O is not installed or licensed, no error messages are displayed unless you explicitly specify the -o qio mount option. If necessary, you can turn the Quick I/O option off at mount time or you can remount the file system with the -o noqio option.
Mounting a File System Prerelease 8 September 2005, 8:54am Example To mount a file system named /db01 that supports large files on volume /dev/vx/dsk/PRODdg/db01: # mkdir /db01 # chown oracle:dba /db01 # /usr/sbin/mount -F vxfs -o largefiles /dev/vx/dsk \ /PRODdg/db01/db01 If you would like /db01 to be mounted automatically after rebooting, add an entry for it in /etc/fstab as follows: /dev/vx/dsk/PRODdg/db01/db01 ▼ 72 vxfs largefiles,qio 0 2 To mount a file system on an existing volume using the
Prerelease 8 September 2005, 8:54am ▼ Mounting a File System To mount any file system using the GUI 1. Select the file system to be mounted. 2. Choose Actions > Mount File System. 3. Complete the Mount File System dialog box as follows: FS Type: Select the file system type. Mount Options: ◆ ◆ ◆ ◆ ◆ 4. If you want the system to use the mount options defined in the system table, check Mount using options in the file system table.
Unmounting a File System Prerelease 8 September 2005, 8:54am Unmounting a File System If you no longer need to access the data in a file system, you can unmount the file system using the umount command. Prerequisites ◆ A file system must exist and be mounted in order to be unmounted. Usage Notes ▼ ◆ See the umount(1M) manual page for more information on mounting file systems. ◆ You cannot unmount a file system that is in use. To unmount a file system using the command line 1.
Prerelease 8 September 2005, 8:54am Unmounting a File System Example To verify that the file system /db01 is not in use and then unmount the file system: # fuser -c /db01 /db01: # umount /db01 ▼ To unmount a file system on a volume using the GUI 1. Select the volume containing the file system to be unmounted. 2. Choose Actions > File System > Unmount File System. 3. Click Yes in the Unmount File System dialog box to confirm that you want to unmount the file system. 4.
Understanding Fragmentation Prerelease 8 September 2005, 8:54am Understanding Fragmentation When free resources are initially allocated to files in a VERITAS file system, they are aligned in the most efficient order possible to provide optimal performance. 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.
Prerelease 8 September 2005, 8:54am Understanding Fragmentation Monitoring Fragmentation You can monitor fragmentation in VxFS by running reports that describe fragmentation levels. Use the fsadm command to run reports on directory fragmentation and extent fragmentation. The df command, which reports on file system free space, also provides information useful in monitoring fragmentation. Use the following commands to report fragmentation information: ◆ fsadm -D, which reports on directory fragmentation.
Understanding Fragmentation -r Prerelease 8 September 2005, 8:54am Specifies the pathname of the raw device to read to determine file layout and fragmentation. This option is used when fsadm cannot determine the raw device. Usage Notes ◆ If you specify -d and -e, directory reorganization is always completed first. ◆ If you use both -D and -E with the -d and -e options, the fragmentation reports are produced both before and after reorganization.
Prerelease 8 September 2005, 8:54am ▼ Understanding Fragmentation To defragment a file system on a volume using the GUI 1. Select the volume containing the file system to be defragmented. 2. Choose Actions > File System > Defrag File System. 3. Select Yes in the displayed dialog box.
Resizing a File System Prerelease 8 September 2005, 8:54am Resizing a File System If you need to extend or shrink a VxFS file system, you can use the fsadm command. If a VxFS file system requires more space, you can use this procedure to extend the size of the file system. If a VxFS File System is too large and you need the space elsewhere, you can use this procedure to shrink the file system.
Prerelease 8 September 2005, 8:54am Resizing a File System Resizing a File System and the Underlying Volume The vxresize command offers the advantage of automatically resizing certain types of file systems as well as the underlying volume. Prerequisites ◆ You must know the new desired size of the file system. ◆ In some situations, you must first unmount the file system before resizing it.
Resizing a File System Prerelease 8 September 2005, 8:54am Growing a File System Automatically Using VxDBA Monitoring Agent You can use the VxDBA Monitoring Agent to monitor file system space, and when the space usage reaches a configured threshold value, a predefined action script automatically grows the file system. See “Managing File System Space” on page 375 for more information.
3 Using VERITAS Quick I/O VERITAS Quick I/O is a VxFS feature included in VERITAS Storage Foundation for Oracle that lets applications access preallocated VxFS files as raw character devices. Quick I/O provides the administrative benefits of running databases on file systems without the performance degradation typically associated with running databases on file systems or raw devices. This chapter describes how to set up and use Quick I/O.
Understanding Quick I/O Prerelease 8 September 2005, 8:54am Understanding Quick I/O How Quick I/O Works VERITAS Quick I/O supports direct I/O and allows databases to access regular files on a VxFS file system as raw character devices.
Prerelease 8 September 2005, 8:54am Understanding Quick I/O Avoiding Kernel Write Locks When database I/O is performed using the write() system call, each system call acquires and releases a write lock inside the kernel. This lock prevents multiple simultaneous write operations on the same file. Because database systems usually implement their own locking to manage concurrent access to files, per file writer locks unnecessarily serialize I/O operations.
Understanding Quick I/O Prerelease 8 September 2005, 8:54am Whenever an application opens an existing VxFS file with the extension ::cdev:vxfs: (cdev being an acronym for character device), the file is treated as if it were a raw device. For example, if the file temp01 is a regular VxFS file, then an application can access temp01 as a raw character device by opening it with the name: .temp01::cdev:vxfs: Note We recommend reserving the ::cdev:vxfs: extension only for Quick I/O files.
Prerelease 8 September 2005, 8:54am Understanding Quick I/O 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 88 for more information.
Creating Database Files as Quick I/O Files Using qiomkfile Prerelease 8 September 2005, 8:54am Creating Database Files as Quick I/O Files Using qiomkfile The best way to preallocate space for database files and to make them accessible using the Quick I/O interface is to use the qiomkfile command. You can use the qiomkfile command to create Quick I/O files for either temporary or permanent tablespaces. Prerequisites ◆ You can create Quick I/O files only on VxFS file systems.
Prerelease 8 September 2005, 8:54am Creating Database Files as Quick I/O Files Using qiomkfile Usage Notes ▼ ◆ The qiomkfile command creates two files: a regular file with preallocated, contiguous space, and a file that is a symbolic link pointing to the Quick I/O name extension. ◆ See the qiomkfile(1M) manual page for more information. To create a database file as a Quick I/O file using qiomkfile 1.
Preallocating Space for Quick I/O Files Using the setext Command Prerelease 8 September 2005, 8:54am Preallocating Space for Quick I/O Files Using the setext Command As an alternative to using the qiomkfile command, you can also use the VxFS setext command to preallocate space for database files. Prerequisites ◆ The setext command requires superuser (root) privileges.
Prerelease 8 September 2005, 8:54am Preallocating Space for Quick I/O Files Using the setext Command Example To access the mount point /db01, create a datafile, preallocate the space, and change the permissions: # # # # # # # cd /db01 touch .dbfile /opt/VRTS/bin/setext -r 100M -f noreserve -f chgsize .dbfile ln -s .dbfile::cdev:vxfs: dbfile chown oracle .dbfile chgrp dba .dbfile chmod 660 .
Accessing Regular VxFS Files as Quick I/O Files Prerelease 8 September 2005, 8:54am 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).
Prerelease 8 September 2005, 8:54am Converting Oracle Files to Quick I/O Files Converting Oracle Files to Quick I/O Files Special commands, available in the /opt/VRTSdbed/bin directory, are provided to assist you in converting an existing database to use Quick I/O. You can use the qio_getdbfiles command to extract a list of file names from the database system tables and the qio_convertdbfiles command to convert this list of database files to use Quick I/O.
Converting Oracle Files to Quick I/O Files Prerelease 8 September 2005, 8:54am -h Displays a help message. -i Creates the extra links for all datafiles and log files in the /dev directory to support SAP’s brbackup. -T Lets you specify the type of database as ora. Specify this option only in environments where the type of database is ambiguous (for example, when multiple types of database environment variables, such as $ORACLE_SID, SYBASE, DSQUERY, and $DB2INSTANCE are present on a server).
Prerelease 8 September 2005, 8:54am ▼ 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.
Converting Oracle Files to Quick I/O Files Prerelease 8 September 2005, 8:54am Run the qio_convertdbfiles command (with no options specified) to rename the file filename to .filename and creates a symbolic link to .filename with the Quick I/O extension. By default, the symbolic link uses a relative path name. The qio_convertdbfiles script exits and prints an error message if any of the database files are not on a VxFS file system. If this happens, you must remove any non-VxFS files from the mkqio.
Prerelease 8 September 2005, 8:54am Understanding Sparse Files Understanding Sparse Files Support for sparse files lets applications store information (in inodes) to identify data blocks that have only zeroes, so that only blocks containing non-zero data have to be allocated on disk. For example, if a file is 10KB, it typically means that there are blocks on disk covering the whole 10KB. Assume that you always want the first 9K to be zeroes.
Handling Oracle Temporary Tablespaces and Quick I/O Prerelease 8 September 2005, 8:54am Handling Oracle Temporary Tablespaces and Quick I/O You can create a new temporary tablespace using Quick I/O files. However, you cannot convert existing temporary tablespaces using regular files to Quick I/O with the qio_getdbfiles command on Oracle9i. By default, qio_getdbfiles skips any tablespaces marked TEMPORARY because they can be sparse, which means that not all blocks in the file are allocated.
Prerelease 8 September 2005, 8:54am 3. Handling Oracle Temporary Tablespaces and Quick I/O Create a new temporary tablespace using the create tablespace or create temporary tablespace command. To use the create tablespace command: $ sqlplus /nolog SQL> connect / as sysdba; SQL> create tablespace tablespace_name \ datafile '/mount_point/filename.
Handling Oracle Temporary Tablespaces and Quick I/O Prerelease 8 September 2005, 8:54am SQL> connect / as dba; SQL> create temporary tablespace tempts \ tempfile '/db01/temp01.dbf' \ size 100M reuse; Tablespace created.
Prerelease 8 September 2005, 8:54am Displaying Quick I/O Status and File Attributes Displaying Quick I/O Status and File Attributes You can obtain and display information about Quick I/O status and file attributes using various options of the ls command. Options ▼ -al Lists all files on a file system, including Quick I/O files and their links. -lL Shows if Quick I/O was successfully installed and enabled. -alL Shows how a Quick I/O file name is resolved to that of a raw device.
Displaying Quick I/O Status and File Attributes ▼ Prerelease 8 September 2005, 8:54am To show a Quick I/O file resolved to a raw device Use the ls command with the file names as follows: $ ls -alL filename .filename Example To show how the Quick I/O file name dbfile is resolved to that of a raw device: $ ls -alL d* .d* crw-r--r-1 oracle dba -rw-r--r-1 oracle dba 102 237 0x000004 Oct 2 13:42 dbfile 104890368 Oct 2 13:42 .
Prerelease 8 September 2005, 8:54am 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.
Extending a Quick I/O File ▼ Prerelease 8 September 2005, 8:54am To extend a Quick I/O File 1. If required, ensure the underlying storage device is large enough to contain a larger VxFS file system (see the vxassist(1M) manual page for more information), and resize the VxFS file system using fsadm command: # /opt/VRTS/bin/fsadm -b newsize /mount_point where: 2.
Prerelease 8 September 2005, 8:54am Using Oracle’s AUTOEXTEND With Quick I/O Files Using Oracle’s AUTOEXTEND With Quick I/O Files Oracle supports an automatic extend feature that automatically grows a database file by a prespecified amount, up to a prespecified maximum size. For regular file system files, AUTOEXTEND works transparently, provided the underlying file system has enough space. For example, suppose the current size of a database file emp.
Using Oracle’s AUTOEXTEND With Quick I/O Files -r Prerelease 8 September 2005, 8:54am Increases the file to a specified size to allow Oracle tablespace resizing. Usage Notes ◆ ▼ You can grow underlying VxFS file systems online (provided the underlying disk or volume can be extended) using the fsadm command. See the fsadm_vxfs(1M) manual page for more information.
Prerelease 8 September 2005, 8:54am Disabling Quick I/O Disabling Quick I/O If you need to disable the Quick I/O feature, you first need to convert any Quick I/O files back to regular VxFS files. Then, remount the VxFS file system using a special mount option. Prerequisites ◆ ▼ The file system you are planning to remount must be located in the /etc/filesystems file. To disable Quick I/O 1. If the database is running, shut it down. 2.
Disabling Quick I/O 108 Prerelease 8 September 2005, 8:54am VERITAS Storage Foundation for Oracle Administrator’s Guide
4 Using VERITAS 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. Cached Quick I/O also supports features that support buffering behavior, such as file system read-ahead. This chapter describes how to enable and use Cached Quick I/O for enhanced performance.
Understanding Cached Quick I/O Prerelease 8 September 2005, 8:54am Understanding Cached Quick I/O How Cached Quick I/O Works Cached Quick I/O is a specialized external caching mechanism specifically suitable to 32-bit ports of the Oracle server. Cached Quick I/O can be used on 64-bit ports of the Oracle server, but the benefits are not as great.
Prerelease 8 September 2005, 8:54am Understanding Cached Quick I/O You can automate the enabling and disabling of Cached Quick I/O on a per-file basis using scripts, allowing the same job that produces reports to tune the file system behavior and make the best use of system resources. You can specify different sets of files for different jobs to maximize file system and database performance.
Enabling Cached Quick I/O on the File System Prerelease 8 September 2005, 8:54am Enabling Cached Quick I/O on the File System Cached Quick I/O depends on VERITAS Quick I/O running as an underlying system enhancement in order to function correctly. Follow the procedures listed here to ensure that you have the correct setup to use Cached Quick I/O successfully. Prerequisites ◆ You must have permission to change file system behavior using the vxtunefs command to enable or disable Cached Quick I/O.
Prerelease 8 September 2005, 8:54am Enabling Cached Quick I/O on the File System # /sbin/fs/vxfs4.1/vxtunefs -s -o qio_cache_enable=1 /mount_point 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. This command enables caching for all the Quick I/O files on this file system.
Enabling Cached Quick I/O on the File System Prerelease 8 September 2005, 8:54am 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. For information on how to add tuning parameters, see the tunefstab(4) manual page. Note vxtunefs can specify a mount point or a block device; tunefstab must always specify a block device only.
Prerelease 8 September 2005, 8:54am Enabling Cached Quick I/O on the File System 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 max_diskq = 1048576 initial_extent_size
Determining Candidates for Cached Quick I/O Prerelease 8 September 2005, 8:54am Determining Candidates for Cached Quick I/O Determining which files can benefit from Cached Quick I/O is an iterative process that varies with each application. For this reason, you may need to complete the following steps more than once to determine the best possible candidates for Cached Quick I/O. Prerequisites ◆ You must enable Cached Quick I/O for the file systems.
Prerelease 8 September 2005, 8:54am Determining Candidates for Cached Quick I/O Analyzing I/O Statistics The output of the qiostat command is the primary source of information to use in deciding whether to enable or disable Cached Quick I/O on specific files. Statistics are printed in two lines per object.
Determining Candidates for Cached Quick I/O Prerelease 8 September 2005, 8:54am Based on these two factors, /db01/stk.dbf is a prime candidate for Cached Quick I/O. For more information on enabling and disabling Cached Quick I/O at the file level, see “Enabling and Disabling Cached Quick I/O for Individual Files” on page 120.
Prerelease 8 September 2005, 8:54am Enabling and Disabling Cached Quick I/O for Individual Files Enabling and Disabling Cached Quick I/O for Individual Files After using qiostat or other analysis tools to determine the appropriate files for Cached Quick I/O, you need to disable Cached Quick I/O for those individual files that do not benefit from caching using the qioadmin command.
Enabling and Disabling Cached Quick I/O for Individual Files ▼ Prerelease 8 September 2005, 8:54am 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 Example Running qiostat shows the cache hit ratio for the file /db01/system.dbf reaches a level that would benefit from caching. To enable Cached Quick I/O for the file /db01/system.
Prerelease 8 September 2005, 8:54am Enabling and Disabling Cached Quick I/O for Individual Files stk.dbf,ON Determining Individual File Settings for Cached Quick I/O Using qioadmin You can determine whether Cached Quick I/O is enabled or disabled for individual files by displaying the file’s cache advisory setting using the qioadmin command. Note To verify caching, always check the setting of the flag qio_cache_enable using vxtunefs, along with the individual cache advisories for each file.
Enabling and Disabling Cached Quick I/O for Individual Files 122 Prerelease 8 September 2005, 8:54am VERITAS Storage Foundation for Oracle Administrator’s Guide
Using VERITAS Extension for Oracle Disk Manager 5 VERITAS Extension for Oracle Disk Manager is specifically designed for Oracle9i or later to enhance file management and disk I/O throughput. The features of Oracle Disk Manager are best suited for databases that reside in a file system contained in VERITAS File System. Oracle Disk Manager allows Oracle9i or later users to improve database throughput for I/O intensive workloads with special I/O optimization.
Understanding Oracle Disk Manager Prerelease 8 September 2005, 8:54am Understanding Oracle Disk Manager Database administrators can choose the datafile type used with the Oracle product. Historically, choosing between file system files and raw devices was based on manageability and performance. The exception to this is a database intended for use with Oracle Parallel Server, which requires raw devices on most platforms.
Prerelease 8 September 2005, 8:54am Understanding Oracle Disk Manager How Oracle Disk Manager Improves Database Performance Oracle Disk Manager improves database I/O performance to VxFS file systems by: ◆ 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 Supporting
Understanding Oracle Disk Manager Prerelease 8 September 2005, 8:54am Supporting Many Concurrent I/Os in One System Call When performing asynchronous I/O, an Oracle process may try to issue additional I/O requests while collecting completed I/Os, or it may try to wait for particular I/O requests synchronously, as it can do no other work until the I/O is completed. The Oracle process may also try to issue requests to different files.
Prerelease 8 September 2005, 8:54am Oracle Disk Manager and Oracle Managed Files Oracle Disk Manager and Oracle Managed Files Oracle9i or later offers a feature known as Oracle Managed Files (OMF). OMFs manage datafile attributes such as file names, file location, storage attributes, and whether or not the file is in use by the database. OMF is only supported for databases that reside in file systems. OMF functionality is greatly enhanced by Oracle Disk Manager.
Oracle Disk Manager and Oracle Managed Files Prerelease 8 September 2005, 8:54am Example The following example shows the init.ora contents and the command for starting the database instance. To simplify Oracle UNDO management, the new Oracle9i or later init.ora parameter UNDO_MANAGEMENT is set to AUTO. This is known as System-Managed Undo. $ cat initPROD.
Prerelease 8 September 2005, 8:54am Oracle Disk Manager and Oracle Managed Files SQL> create tablespace EMP_TABLE DATAFILE AUTOEXTEND ON MAXSIZE \ 500M; A tablespace is created. SQL> ALTER SYSTEM SET DB_CREATE_FILE_DEST = ’/PROD/EMP_INDEX’; The system is altered. SQL> create tablespace EMP_INDEX DATAFILE AUTOEXTEND ON MAXSIZE \ 100M; A tablespace is created.
Setting Up VERITAS Extension for Oracle Disk Manager Prerelease 8 September 2005, 8:54am Setting Up VERITAS Extension for Oracle Disk Manager VERITAS Extension for Oracle Disk Manager is part of VERITAS Storage Foundation for Oracle. VERITAS Extension for Oracle Disk Manager is enabled once VERITAS Storage Foundation for Oracle and Oracle9i or later are installed, and the VERITAS Extension for Oracle Disk Manager library is linked to the library in the {ORACLE_HOME}/lib directory.
Prerelease 8 September 2005, 8:54am Setting Up VERITAS Extension for Oracle Disk Manager When the system and instance are configured correctly, the Oracle Disk Manager feature is used, by default, for accessing any database storage.
Preparing Existing Database Storage for Oracle Disk Manager Prerelease 8 September 2005, 8:54am Preparing Existing Database Storage for Oracle Disk Manager Non-Quick I/O files in a VxFS file system work with Oracle Disk Manager without any changes. The files are found and identified for Oracle Disk Manager I/O by default. To take full advantage of Oracle Disk Manager datafiles, files should not be fragmented. See “Understanding Fragmentation” on page 76 for information on defragmenting a file.
Prerelease 8 September 2005, 8:54am 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.
Verifying that Oracle Disk Manager is Configured Prerelease 8 September 2005, 8:54am Verifying that Oracle Disk Manager is Configured To verify the configuration of the Oracle Disk Manager, make sure the following Prerequisites are satisfied. Prerequisites ▼ ◆ The VRTSdbed license must be valid. ◆ The VRTSodm package must be installed. ◆ /opt/VRTSodm/lib/libodm.sl must exist. ◆ If you are using Oracle9i, $ORACLE_HOME/lib/libodm9.sl is linked to /opt/VRTSodm/lib/libodm.
Prerelease 8 September 2005, 8:54am Verifying that Oracle Disk Manager is Configured For Oracle 10g # cmp $ORACLE_HOME/lib/libodm10.sl /opt/VRTSodm/lib/libodm.sl # echo $? 0 For Oracle9i # cmp $ORACLE_HOME/lib/libodm9.sl /opt/VRTSodm/lib/libodm.sl # echo $? 0 Note You can also use the dbed_checkconfig command, which is installed with VERITAS Storage Foundation for Oracle to check these conditions.
Disabling the Oracle Disk Manager Feature Prerelease 8 September 2005, 8:54am Disabling the Oracle Disk Manager Feature Because the Oracle Disk Manager feature uses regular files, you can access these files as regular VxFS files as soon as the feature is disabled. Note To convert to VxFS with Quick I/O, disable the Oracle Disk Manager using the steps below. Then, see “Converting Oracle Files to Quick I/O Files” on page 94 for more information.
6 Using Storage Mapping Storage mapping is included with VERITAS Storage Foundation for Oracle Enterprise Edition. Storage mapping enables you to map datafiles to physical devices. You may obtain and view detailed storage topology information using the vxstorage_stats and dbed_analyzer commands or the VERITAS Storage Foundation for Oracle GUI. You may also use the Oracle Enterprise Manager to access storage mapping information.
Understanding Storage Mapping Prerelease 8 September 2005, 8:55am Understanding Storage Mapping Access to mapping information is important since it allows for a detailed understanding of the storage hierarchy in which files reside, information that is critical for effectively evaluating I/O performance. Mapping files to their underlying device is straightforward when datafiles are created directly on a raw device.
Prerelease 8 September 2005, 8:55am Verifying VERITAS Storage Mapping Setup Verifying VERITAS Storage Mapping Setup Before using the VERITAS Storage Mapping option, verify that the features are set up correctly. ▼ 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.
Using vxstorage_stats Prerelease 8 September 2005, 8:55am Using vxstorage_stats The vxstorage_stats command displays detailed storage mapping information and I/O statistics about an individual VxFS file. The mapping information and I/O statistics are recorded only for VxFS files and VxVM volumes. In vxstorage_stats command output, I/O topology information appears first followed by summary statistics for each object.
Prerelease 8 September 2005, 8:55am Using vxstorage_stats Note For file type (fi), the SIZE column is number of bytes, and for volume (v), plex (pl), sub-disk (sd), and physical disk (da), the SIZE column is in 512-byte blocks. Stripe sizes are given in sectors.
Using dbed_analyzer Prerelease 8 September 2005, 8:55am Using dbed_analyzer Effectively performing a parallel backup requires an understanding of which tablespaces reside on which disks. If two tablespaces reside on the same disk, for example, backing them up in parallel will not reduce their downtime. The dbed_analyzer command provides tablespace-to-physical disk mapping information for all the datafiles in a specified tablespace, list of tablespaces, or an entire database.
Prerelease 8 September 2005, 8:55am Using dbed_analyzer Output similar to the following is displayed in the file tbsfile: TBSNAME SIZE(sectors) DATAFILE SYSTEM TEMP TEMP SYSAUX ITEM ITM_IDX PRODID_IDX QTY_IDX ROLL_1 ROLL_2 ORDERS ORD_IDX QTY_IDX ITM_IDX ROLL_1 QTY_IDX ROLL_2 ITEM ▼ DEVICE /usr1/oracle/rw/DATA/PROD.dbf /usr1/oracle/rw/DATA/temp_20000 /usr1/oracle/rw/DATA/temp_20001 /usr1/oracle/rw/DATA/sysaux.
Using dbed_analyzer c3t21000020379DBD5Fd0 c3t21000020379DBD5Fd0 c3t21000020379DBD5Fd0 c3t21000020379DBD5Fd0 c3t21000020379DBD5Fd0 c3t21000020379DBD5Fd0 c3t21000020379DBD5Fd0 c3t21000020379DBD5Fd0 c3t21000020379DBD5Fd0 c3t21000020379DBD5Fd0 c3t21000020379DBD5Fd0 c3t21000020379DBD5Fd0 c3t21000020379DBD5Fd0 c3t21000020379DBD5Fd0 144 Prerelease 8 September 2005, 8:55am ITEM /usr1/oracle/rw/DATA/item_1000 ITM_IDX /usr1/oracle/rw/DATA/itm_idx_2000 PRODID_IDX /usr1/oracle/rw/DATA/prodid_idx_3000 QTY_IDX /usr1/or
Prerelease 8 September 2005, 8:55am Viewing Storage Mapping Topology and I/O Statistics Using the GUI Viewing Storage Mapping Topology and I/O Statistics Using the GUI ▼ To view Oracle daatafile storage mapping topology using the GUI 1. Start the GUI and connect to the desired host. 2. Expand the Oracle Databases icon in the object tree and then expand the desired database. 3. Select one of the following methods to generate datafile statistics. ◆ From the menu bar, select Datafiles > Topology.
Viewing Storage Mapping Topology and I/O Statistics Using the GUI Prerelease 8 September 2005, 8:55am 7. The Display accumulated data checkbox is checked by default. 8. The Time Elapsed (in minutes) displays the amount of time it took to sample the data. The progress status bar displays the percentage of sampling that is being completed. 9. After successful completion, a Confirmation dialog is displayed, indicating that the data was successfully collected for the specified time.
Prerelease 8 September 2005, 8:55am 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 Oracle9i release 2 or later. libvxoramap_64.
Oracle File Mapping (ORAMAP) Prerelease 8 September 2005, 8:55am A mapping subelement component describes the link between an element and the next element in the I/O stack. The subelement component contains the subelement number, size, the element name for the subelement, and the element offset. Subelement components are exported to the user through v$map_subelement. These four types of mapping components completely describe the mapping information for an Oracle instance.
Prerelease 8 September 2005, 8:55am Oracle File Mapping (ORAMAP) Verifying Oracle File Mapping Setup ▼ To verify that $ORACLE_HOME is set up for Oracle file mapping (ORAMAP) 1. Enter: # cd $ORACLE_HOME/rdbms/filemap/bin # ls –l -r-xr-x--- 1 root system 900616 Apr 08 19:16 fmputl -r-sr-xr-x 1 root system 14614 Apr 08 19:16 fmputlhp 2. 3. Verify that: ◆ fmputlhp is owned by root and that the setud bit is set. ◆ The permissions for fmputlhp are set to -r-sr-xr-x.
Oracle File Mapping (ORAMAP) Prerelease 8 September 2005, 8:55am Note If you want storage mapping to be enabled whenever you start up an instance, set the file_mapping initialization parameter to true in the init.ora file. Accessing Dynamic Performance Views ▼ 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.
Prerelease 8 September 2005, 8:55am 5 Oracle File Mapping (ORAMAP) fv.file_name, lpad(' ', 4 * (level - 1)) || \ el.elem_name elem_name, el.elem_size, el.elem_type, \ el.elem_descr 6 from 7 v$map_subelement sb, v$map_element el, fv, 8 (select unique elem_idx from v$map_file_io_stack io, fv 9 where io.file_map_idx = fv.file_map_idx) fs 10 where el.elem_idx = sb.child_idx 11 and fs.elem_idx = el.elem_idx 12 start with sb.
Oracle File Mapping (ORAMAP) Prerelease 8 September 2005, 8:55am 7. In the right pane, click the Storage Layout tab. 8. Expand the objects to display their storage layout. Note Within the Oracle Enterprise Manager Console, you can point to an object on the screen and a description of the object is displayed in a pop-up field. If an object name or path appears truncated, point to it and the pop-up field will display the full object name and path.
Prerelease 8 September 2005, 8:55am Configuring Arrays for Storage Mapping and Statistics Configuring Arrays for Storage Mapping and Statistics VERITAS Storage Foundation for Oracle provides “deep” mapping information and performance statistics for supported storage arrays. Deep mapping information consists of identifying the physical disks that comprise each LUN and the hardware RAID information for the LUNs. Note To use deep mapping, you must have Oracle 9.2.0.3. or later installed.
Converting Existing Database Configurations to VxFS 7 You can convert existing database configurations to VERITAS Volume Manager and VERITAS File System. This chapter describes how to convert LVM volume groups to VxVM disk groups and how to migrate HFS file systems, earlier version layouts, and raw devices to current VxFS file systems.
Prerelease 8 September 2005, 8:55am Converting LVM Volume Groups to VxVM Disk Groups Converting LVM Volume Groups to VxVM Disk Groups If you are currently using VxFS file systems for your database and the file systems are mounted on LVM volumes, you can convert these LVM volume groups to VxVM disk groups in place. VERITAS Volume Manager provides an interactive, menu-driven utility, vxvmconvert.
Converting From HFS to VxFS With Quick I/O Prerelease 8 September 2005, 8:55am Converting From HFS to VxFS With Quick I/O If you are currently using HFS file systems, you can use the following procedure to upgrade each file system used by the database to a VxFS file system with Quick I/O. ▼ 156 To convert an HFS file system to VxFS with Quick I/O 1. Shut down the database. 2. Create a backup of the HFS file system. 3. Unmount the HFS file system. 4.
Prerelease 8 September 2005, 8:55am Converting From HFS to VxFS For Oracle Disk Manager Converting From HFS to VxFS For Oracle Disk Manager If you are currently using HFS file systems, you can use the following procedure to upgrade each file system used by the database to a VxFS file system. You can then use the Oracle Disk Manager feature. Caution Do not upgrade your root file system to VxFS.
Upgrading From JFS, OnlineJFS, and Earlier VxFS Version Layouts Prerelease 8 September 2005, 8:55am Upgrading From JFS, OnlineJFS, and Earlier VxFS Version Layouts Prerequisites ◆ Perform a full backup of the file system before upgrading to a new disk layout. 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.
Prerelease 8 September 2005, 8:55am ▼ Upgrading From JFS, OnlineJFS, and Earlier VxFS Version Layouts To use Oracle Disk Manager after upgrading the file system disk layout to Version 4, 5, or 6 Simply use the files. Because ODM uses regular files, no setup is required.
Converting From Raw Devices Prerelease 8 September 2005, 8:55am Converting From Raw Devices If the database is currently using raw disks or volumes, use one of the following procedures to use VxFS with the Quick I/O feature or Oracle Disk Manager. Note The procedure provided assumes the database runs on a single file system after the upgrade. ▼ To convert from raw devices to VxFS with Quick I/O 1.
Prerelease 8 September 2005, 8:55am Converting From Raw Devices SQL> alter database open; SQL> exit ▼ 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. Use the procedure described in “Creating a VxFS File System” on page 67 to create a new VxFS file system. You can create more file systems based on your performance and availability requirements. 2. Shut down the database. 3.
Using Storage Checkpoints and Storage Rollback 8 The VERITAS Storage Checkpoint feature is available with the Enterprise Edition as part of the VERITAS File System package and is used for the efficient backup and recovery of Oracle databases. Storage Checkpoints can also be mounted, allowing regular file system operations to be performed. This chapter describes what Storage Checkpoints and storage rollback are and how to make use of these technologies through VERITAS Storage Foundation for Oracle.
Prerelease 8 September 2005, 8:55am Using Storage Checkpoints and Storage Rollback for Backup and Restore Using Storage Checkpoints and Storage Rollback for Backup and Restore VERITAS Storage Foundation for Oracle provides a Storage Checkpoint facility that is similar to the snapshot file system mechanism; however, a Storage Checkpoint persists after a system reboot.
Using Storage Checkpoints and Storage Rollback for Backup and Restore Prerelease 8 September 2005, 8:55am on the primary file system, the Storage Checkpoint gradually fills with the original data copied from the primary file system, and less and less of the block map in the Storage Checkpoint points back to blocks on the primary file system. Storage Rollback restores a database, a tablespace, or datafiles on the primary file systems to the point-in-time image created during a Storage Checkpoint.
Prerelease 8 September 2005, 8:55am Determining Space Requirements for Storage Checkpoints Determining Space Requirements for Storage Checkpoints To support Block-level Incremental (BLI) Backup and storage rollback, the file systems need extra disk space to store the Storage Checkpoints. The extra space needed depends on how the Storage Checkpoints are used.
Determining Space Requirements for Storage Checkpoints Prerelease 8 September 2005, 8:55am 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.
Prerelease 8 September 2005, 8:55am Performance of Storage Checkpoints Performance of Storage Checkpoints VERITAS File System attempts to optimize the read and write access performance on both the Storage Checkpoint and the primary file system. Reads from a Storage Checkpoint typically perform at nearly the throughput of reads from a normal VxFS file system, allowing backups to proceed at the full speed of the VxFS file system.
Storage Checkpoint Allocation Policies Prerelease 8 September 2005, 8:55am Storage Checkpoint Allocation Policies VERITAS File System provides Multi-Volume File Systems (MVS) when used in conjunction with the Volumes Set feature in VERITAS Volume Manager. A volume set is a container for multiple different volumes. MVS enables creation of a single file system over multiple volumes, each volume with properties of its own. This helps administrators specify which data goes on which volume types.
Prerelease 8 September 2005, 8:55am Storage Checkpoint Allocation Policies ◆ Storage checkpoint allocation policy requires VxVM Volume Set and VxFS Multi-Volume File Systems features to be enabled. These features are included in the Enterprise Edition of Storage Foundation. Refer to the Multi-Volume File System chapter in the VERITAS File System Administrator's Guide, for creating Volume Sets and MVS file systems for the primary file systems used by the database datafiles.
Storage Checkpoint Allocation Policies Prerelease 8 September 2005, 8:55am Creating a Storage Checkpoint Allocation policy ▼ 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.
Prerelease 8 September 2005, 8:55am Storage Checkpoint Allocation Policies Note dbed_ckptcreate command automaticlly assigns the policies when the storage checkpoint is created. ▼ To assign an allocation policy to an existing Storage Checkpoint The following procedure uses dbed_ckptpolicy to assign an allocation policy to an existing Storage Checkpoint. This example uses PROD as the database name and Checkpoint_1096060202 as a sample Storage Checkpoint. 1.
Storage Checkpoint Allocation Policies Prerelease 8 September 2005, 8:55am ----------------------------Checkpoint_1096060122 /mvsfs/v2 Checkpoint_1096060122 /mvsfs/v1 ----------ckpt_data ckpt_data ---------------ckpt_metadata ckpt_metadata Displaying a Storage Checkpoint Allocation policy ▼ 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.
Prerelease 8 September 2005, 8:55am ▼ Storage Checkpoint Allocation Policies 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.
Storage Checkpoint Allocation Policies Prerelease 8 September 2005, 8:55am Note You are prompted to enter any new volumes to which you would want to assign the Storage Checkpoint allocation policy.
Prerelease 8 September 2005, 8:55am Storage Checkpoint Allocation Policies where new_vol is the name of the newly added volume and 2g is the size of the volume. 7. Verify the new volume in the file system.
Backing Up and Recovering the Database Using Storage Checkpoints Prerelease 8 September 2005, 8:55am Backing Up and Recovering the Database Using Storage Checkpoints Storage Checkpoints can be created by specifying one of the following options: online, offline, or instant. To create a Storage Checkpoint with the online option, the database should be online and you must enable ARCHIVELOG mode for the database. For the offline option, the database should be offline.
Prerelease 8 September 2005, 8:55am Backing Up and Recovering the Database Using Storage Checkpoints $ /opt/VRTS/bin/dbed_ckptmount -S PROD \ -c Checkpoint_903937870 -m /tmp/ckpt_ro Note If the specified mount point directory does not exist, then dbed_ckptmount creates it before mounting the Storage Checkpoint, as long as the Oracle DBA user has permission to create it. 2. Examine the content of the Storage Checkpoint: $ ls -l /tmp/ckpt_ro/dbvol_82/dbinst1 drwxr-xr-x 3 oracle dba 1024 Nov 11 2000 .
Backing Up and Recovering the Database Using Storage Checkpoints Prerelease 8 September 2005, 8:55am Backing Up Using a Storage Checkpoint You can back up a database by creating a Storage Checkpoint using the dbed_ckptcreate command, mount the Storage Checkpoint as read-only using the dbed_ckptmount command, and then back it up using tools such as tar or cpio. Usage Notes ◆ ▼ See the dbed_ckptcreate(1M), dbed_ckptmount(1M), tar(1), and cpio(1) manual pages for more information.
Prerelease 8 September 2005, 8:55am Backing Up and Recovering the Database Using Storage Checkpoints roll back an entire database, a tablespace, or a single database file. Rolling back to or restoring from any Storage Checkpoint is generally very fast because only the changed data blocks need to be restored.
Backing Up and Recovering the Database Using Storage Checkpoints Prerelease 8 September 2005, 8:55am Note For more information on storage rollback and recovering to Storage Checkpoints, see “Rolling Back the Database to a Storage Checkpoint” on page 360, “Rolling Back a Tablespace to a Storage Checkpoint” on page 363, and “Rolling Back Datafiles to a Storage Checkpoint” on page 368.
Prerelease 8 September 2005, 8:55am Guidelines for Oracle Recovery Guidelines for Oracle Recovery For optimal Oracle recovery, follow these guidelines: ◆ Back up all control files before Storage Rollback in case the subsequent Oracle recovery is not successful. Oracle recommends that you keep at least two copies of the control files for each Oracle database and that you store the copies on different disks.
Guidelines for Oracle Recovery Prerelease 8 September 2005, 8:55am Note After rolling back the database (including control files and redo logs) to a Storage Checkpoint, you need to recover the Oracle database instance. Rolling the database forward is not supported; that is, you cannot apply archived redo logs.
Prerelease 8 September 2005, 8:55am Using the VxDBA Utility or GUI to Perform Storage Checkpoint-Related Operations Using the VxDBA Utility or GUI to Perform Storage Checkpoint-Related Operations Use the VxDBA utility or GUI to create Storage Checkpoints and then roll back an entire database, a single tablespace, or any set of datafiles using any of the previously created Storage Checkpoints.
Using the Space Capacity Planning Utility for Storage Checkpoints 9 The VERITAS Space Capacity Planning utility for Storage Checkpoints is one of the operations available from the VERITAS Storage Foundation graphical user interface (GUI) and VxDBA utility menus. This chapter describes how to use Storage Checkpoint Capacity Planning using the VxDBA utility and to plan for adequate file system space needed for Storage Checkpoints.
Prerelease 8 September 2005, 8:55am Planning File System Space for Storage Checkpoints Planning File System Space for Storage Checkpoints VxFS file systems need extra disk space to store Storage Checkpoints. Because VxFS can remove Storage Checkpoints when a file system runs out of space, it is important to ensure that you have adequate space for Storage Checkpoints.
Starting the Storage Checkpoint Capacity Planning Utility Prerelease 8 September 2005, 8:55am Starting the Storage Checkpoint Capacity Planning Utility The Storage Checkpoint Capacity Planning utility operations can be run by the Oracle Database Administrator (typically, the user ID oracle) of the database instance. Prerequisites ◆ You must have the appropriate permissions to run the VxDBA utility. The VxDBA utility requires permission changes to allow database administrators to access it.
Prerelease 8 September 2005, 8:55am Starting the Storage Checkpoint Capacity Planning Utility VxDBA starts up and displays the main menu.
Creating Capacity Planning Schedules Prerelease 8 September 2005, 8:55am Creating Capacity Planning Schedules The VERITAS Storage Foundation GUI and the Storage Checkpoint Capacity Planning utility prompt you through the entire schedule-creation process. Prerequisites ◆ You must have the appropriate permissions to create and execute a cron job to create Capacity Planning schedules. For more information on setting up and using cron, see the cron(1) and crontab(1) manual pages.
Prerelease 8 September 2005, 8:55am 2.
Creating Capacity Planning Schedules Prerelease 8 September 2005, 8:55am Example To create a Quick Planning Schedule, type 1 on the Create Capacity Planning Schedules menu: ---------------------------------------VxDBA: Create Quick Planning Schedule ---------------------------------------NOTICE: To correctly create schedule on current database instance, you must have up-to-date tablespace information stored in VxDBA's database.
Prerelease 8 September 2005, 8:55am Displaying Capacity Planning Schedules Displaying Capacity Planning Schedules Use the GUI, the VxDBA utility, or the Storage Checkpoint Capacity Planning utility to display all the Capacity Planning schedules you created.
Displaying File System Space Usage Information Prerelease 8 September 2005, 8:55am Displaying File System Space Usage Information Use the GUI, the VxDBA utility, or 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.
Prerelease 8 September 2005, 8:55am 2.
Displaying File System Space Usage Information Prerelease 8 September 2005, 8:55am Example To display VxFS file system and Storage Checkpoint space-usage information for the current database instance, type 1 on the Display Space Usage Information menu: File System (1K block) FS Size --------------------------------------/db01 10.0GB Storage Checkpoint -----------------------Planning_00001_956765641 Planning_00001_956762040 Planning_00001_956758441 Used Avail -------- -------5.3GB 4.
Prerelease 8 September 2005, 8:55am Removing Capacity Planning Schedules Removing Capacity Planning Schedules Use the GUI, the VxDBA utility, or the Storage Checkpoint Capacity Planning utility to remove Capacity Planning schedules at any time. You do not need to wait until the expiration date that you supplied when creating a schedule.
Removing Capacity Planning Schedules Prerelease 8 September 2005, 8:55am Example To remove the Quick Planning Schedule you created in “Creating Capacity Planning Schedules” on page 188, type 4 on the Storage Checkpoint Capacity Planning menu: ------------------------------------------VxDBA: Remove Capacity Planning Schedules ------------------------------------------ID Start Date End Date Schedule Summary -- ----------- ---------- ---------------------------------------1 2001-12-15 2001-12-15 Daily at 1 a
Using Database FlashSnap for Backup and Off-Host Processing 10 This chapter describes how to use VERITAS Database FlashSnap to create a point-in-time copy of a database for backup and off-host processing. Database FlashSnap allows you to make backup copies of your volumes online with minimal interruption to users. VERITAS Database FlashSnap is included with VERITAS Storage Foundation Enterprise Edition.
How VERITAS Database FlashSnap Works Prerelease 8 September 2005, 8:55am How VERITAS Database FlashSnap Works You can use VERITAS Database FlashSnap to implement point-in-time copy solutions for enterprise databases. Database FlashSnap offers you a flexible way to efficiently manage multiple point-in-time copies of your data, and reduce resource contention on your business-critical servers.
Prerelease 8 September 2005, 8:55am How VERITAS Database FlashSnap Works Database FlashSnap Applications The following are typical applications of VERITAS Database FlashSnap: ◆ Database Backup and Restore: Enterprises require 24/7 online data availability. They cannot afford the downtime involved in backing up critical data offline.
How VERITAS Database FlashSnap Works Prerelease 8 September 2005, 8:55am specifies snapshot options that will be used when creating a snapshot image (such as whether the snapshot mode will be online, offline, or instant). For further details, see “Creating a Snapplan (dbed_vmchecksnap)” on page 222. After creating the snapplan, the database administrator must validate it to ensure that it is correct. During validation the snapplan is copied to the repository before using it to create a snapshot.
Prerelease 8 September 2005, 8:55am How VERITAS Database FlashSnap Works 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. The snapshot image can be brought up on the same host running the primary database or on a secondary host. All of these commands can be executed by the Oracle database administrator and do not require superuser (root) privileges.
Planning Considerations Prerelease 8 September 2005, 8:55am Planning Considerations Before using Database FlashSnap, you must first determine your intended application. You will then need to make the following decisions: ◆ Which snapshot mode is appropriate: online, offline, or instant? ◆ Will you need one or two hosts? Selecting the Snapshot Mode If your purpose is to use the snapshot for backup or to recover the database after logical errors have occurred, choose the online option.
Prerelease 8 September 2005, 8:55am Preparing Hosts and Storage for Database FlashSnap Preparing Hosts and Storage for Database FlashSnap Setting Up Hosts Database FlashSnap requires sufficient VERITAS Volume Manager disk space, and can be used on the same host that the database resides on (the primary host) or on a secondary host. Setting up a storage configuration for Database FlashSnap operations is a system administrator’s responsibility and requires superuser (root) privileges.
Preparing Hosts and Storage for Database FlashSnap Prerelease 8 September 2005, 8:55am For off-host processing applications, both the primary and secondary hosts need to share the storage in which the snapshot database is created. Both the primary and secondary hosts must be able to access the disks containing the snapshot volumes.
Prerelease 8 September 2005, 8:55am Preparing Hosts and Storage for Database FlashSnap ◆ The same version of Oracle is installed on both hosts the Oracle binaries and datafiles are on different volumes and disks. ◆ The UNIX login for the database user and group must be the same on both hosts. ◆ You have a VERITAS Storage Foundation 4.1 for Oracle Enterprise Edition license on both hosts.
Preparing Hosts and Storage for Database FlashSnap Prerelease 8 September 2005, 8:55am ◆ Snapshot mirrors and their associated DCO logs should be on different disks than the original mirror plexes, and should be configured correctly for creating snapshots by the system administrator. ◆ When creating a snapshot mirror, create the snapshot on a separate controller and separate disks from the primary volume. ◆ Allocate separate volumes for archive logs.
Prerelease 8 September 2005, 8:55am Preparing Hosts and Storage for Database FlashSnap Note For enabling persistent FastResync on a volume in VxVM 4.1, either from the command line or from within a script, use the vxsnap prepare command as described above. 2. To verify that FastResync is enabled on the volume, use the vxprint command: # vxprint -g diskgroup -F%fastresync volume_name This returns on if FastResync is on. Otherwise, it returns off. 3.
Preparing Hosts and Storage for Database FlashSnap Prerelease 8 September 2005, 8:55am Example The following example shows the steps involved in creating a snapshot mirror for the volume data_vol belonging to the disk group PRODdg.
Prerelease 8 September 2005, 8:55am Preparing Hosts and Storage for Database FlashSnap sd PRODdg01-01 data_vol_dcl-01 ENABLED 560 pl data_vol_dcl-02 data_vol_dcl DISABLED 560 sd PRODdg02-02 data_vol_dcl-02 ENABLED 560 0 0 DCOSNP - - - Identify that the specified plex is in the SNAPDONE state. In this example, it is data_vol-02. The snapshot mirror is now ready to be used. Upgrading Existing Volumes to Use VERITAS Volume Manager 4.
Preparing Hosts and Storage for Database FlashSnap Prerelease 8 September 2005, 8:55am If persistent FastResync was enabled on the volume before the snapshot was taken, the data in the snapshot plexes is quickly resynchronized from the original volume. If persistent FastResync was not enabled, a full resynchronization is performed. 4. Use the following command to turn off persistent FastResync for the volume: # vxvol [-g diskgroup] set fastresync=off volume 5.
Prerelease 8 September 2005, 8:55am Preparing Hosts and Storage for Database FlashSnap Example In this example, the volume, data_vol, is upgraded to make use of VxVM 4.1 features. Upgrade the disk group, PRODdg. # vxdg upgrade PRODdg Remove the DRL plexes or subdisks, belonging to an earlier version of VxVM, from the volume to be upgraded. # vxassist -g PRODdg remove log data_vol logtype=drl Reattach any snapshot volume back to the primary volume to be upgraded.
Preparing Hosts and Storage for Database FlashSnap Prerelease 8 September 2005, 8:55am # vxprint -g PRODdg pl data_vol-03 sd PRODdg02-01 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 4194304 ENABLED 4194304 0 - - - ENABLED ENABLED ENABLED
Prerelease 8 September 2005, 8:55am pl sd dc v pl sd pl sd 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 Preparing Hosts and Storage for Database FlashSnap ENABLED ENABLED ENABLED ENABLED ENABLED DISABLED ENABLED 4194304 4194304 560 560 560 560 560 Chapter 10, Using Database FlashSnap for Backup and Off-Host Processing 0 0 0 SNAPDONE ACTIVE ACTIVE DCOS
Preparing Hosts and Storage for Database FlashSnap Prerelease 8 September 2005, 8:55am Upgrading from VERITAS Database Edition 3.5 for Oracle with Database FlashSnap In this release of VERITAS Storage Foundation for Oracle, Database FlashSnap does not support snapshots of vxdbavol and ORACLE_HOME. If you have upgraded from VERITAS Database Edition 3.
Prerelease 8 September 2005, 8:55am Summary of Database Snapshot Steps 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. Three types of snapshots can be created: online, offline, or instant. If the SNAPSHOT_MODE specified in the snapplan is set to online, dbed_vmsnap first puts the tablespaces to be snapshot into backup mode.
Summary of Database Snapshot Steps Prerelease 8 September 2005, 8:55am The snapplan contains detailed database and volume configuration information that is needed for snapshot creation and resynchronization. You can modify the snapplan template with a text editor. The dbed_vmchecksnap command can also be used to: - List all snapplans associated with a specific ORACLE_SID (dbed_vmchecksnap -o list). - Remove the snapplan from the VxDBA repository (dbed_vmchecksnap -o remove -f SNAPPLAN).
Prerelease 8 September 2005, 8:55am Summary of Database Snapshot Steps Prerequisites for Creating a Snapshot of your Database Chapter 10, Using Database FlashSnap for Backup and Off-Host Processing 217
Summary of Database Snapshot Steps Prerelease 8 September 2005, 8:55am There are many actions you can take after creating a snapshot of your database using Database FlashSnap. You can create a clone of the database for backup and off-host processing purposes. You can resynchronize the snapshot volumes with the primary database. In the event of primary database failure, you can recover it by reverse resynchronizing the snapshot volumes.
Prerelease 8 September 2005, 8:55am Summary of Database Snapshot Steps Actions you can perform after Creating a Snapshot of your Database Chapter 10, Using Database FlashSnap for Backup and Off-Host Processing 219
Creating a Snapplan (dbed_vmchecksnap) Prerelease 8 September 2005, 8:55am Creating a Snapplan (dbed_vmchecksnap) The dbed_vmchecksnap command creates a snapplan that dbed_vmsnap uses to create a snapshot of an Oracle database. The snapplan specifies snapshot scenarios (such as online, offline, or instant). You can name a snapplan file whatever you choose. Each entry in the snapplan file is a line in parameter=argument format.
Prerelease 8 September 2005, 8:55am Creating a Snapplan (dbed_vmchecksnap) 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.
Creating a Snapplan (dbed_vmchecksnap) Prerelease 8 September 2005, 8:55am When you first run dbed_vmchecksnap, use the -o setdefaults option to create a snapplan using default values for variables. You may then edit the file manually to set the variables for different snapshot scenarios. Note You cannot access Database FlashSnap commands (dbed_vmchecksnap, dbed_vmsnap, and dbed_vmclonedb) with the VxDBA menu utility.
Prerelease 8 September 2005, 8:55am ▼ Creating a Snapplan (dbed_vmchecksnap) To create a snapplan 1. Change directories to the working directory you want to store your snapplan in. $ cd /working_directory 2. Create a snapplan with default values using the dbed_vmchecksnap command: $ /opt/VRTS/bin/dbed_vmchecksnap -S ORACLE_SID \ -H ORACLE_HOME -f SNAPPLAN -o setdefaults -t host_name \ [-p PLEX_TAG] 3. Open the snapplan file in a text editor and modify it as needed.
Creating a Snapplan (dbed_vmchecksnap) Prerelease 8 September 2005, 8:55am $ cd /export/snap_dir $ /opt/VRTS/bin/dbed_vmchecksnap -S PROD \ -H /oracle/product/9i -f snap2 -o setdefaults -t host2 Snapplan snap2 for PROD. ===================================================== SNAPSHOT_VERSION=4.
Prerelease 8 September 2005, 8:55am Creating a Snapplan (dbed_vmchecksnap) Creating Multi-mirror Snapshots To make Database Snapshots highly available, the snapped snapshot volume should contain more than one mirror. This makes the snapshot volumes available even if one of the mirrors gets disabled. Snapshot volumes can be mounted and the entire database snapshot is usable even if one of the mirror gets disabled. The multi-mirror snapshots are enabled via SNAPSHOT_MIRROR= in the snapplan.
Creating a Snapplan (dbed_vmchecksnap) Prerelease 8 September 2005, 8:55am Establishing a Mandatory Archive Destination When cloning a database using Database FlashSnap (see “Cloning a Database (dbed_vmclonedb)” on page 244 for details), the Oracle database must have at least one mandatory archive destination, otherwise dbed_vmchecksnap results in this error message: SFORA dbed_vmchecksnap ERROR V-81-5677 Could not find a mandatory, primary and valid archive destination for database PROD.
Prerelease 8 September 2005, 8:55am Validating a Snapplan (dbed_vmchecksnap) Validating a Snapplan (dbed_vmchecksnap) After creating a snapplan, the next steps are to validate the snapplan parameters and check whether the snapshot volumes have been configured correctly for creating snapshots. If validation is successful, the snapplan is copied to the repository. The snapplan is validated using the dbed_vmchecksnap command with the -o validate option.
Validating a Snapplan (dbed_vmchecksnap) Prerelease 8 September 2005, 8:55am Example In the following example, a snapplan, snap1, is validated for a snapshot image in a single-host configuration. The primary host is host1 and the working directory is /export/snap_dir. $ cd /export/snap_dir $ /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.
Prerelease 8 September 2005, 8:55am Validating a Snapplan (dbed_vmchecksnap) SNAPSHOT_DG is SNAP_PRODdg SNAPSHOT_MODE is online The database is running in archivelog mode. ARCHIVELOG_DEST is /mytest/arch SNAPSHOT_PLAN_FOR is database SNAPSHOT_ARCHIVE_LOG is yes ARCHIVELOG_DEST=/mytest/arch is mount on /dev/vx/dsk/PRODdg/arch. Examining Oracle volume and disk layout for snapshot. Volume arch on PRODdg is ready for snapshot. Original plex and DCO log for arch is on PRODdg01.
Displaying, Copying, and Removing a Snapplan (dbed_vmchecksnap) Prerelease 8 September 2005, 8:55am Displaying, Copying, and Removing a Snapplan (dbed_vmchecksnap) This section explains how to list all snapplans for a specific Oracle database, display a snapplan file, and copy and remove snapplans. Usage Notes ▼ ◆ If the local snapplan is updated or modified, you must re-validate it. ◆ If the database schema or disk group is modified, you must revalidate.
Prerelease 8 September 2005, 8:55am Displaying, Copying, and Removing a Snapplan (dbed_vmchecksnap) SNAPSHOT_VERSION=4.
Displaying, Copying, and Removing a Snapplan (dbed_vmchecksnap) Prerelease 8 September 2005, 8:55am $ /opt/VRTS/bin/dbed_vmchecksnap -S ORACLE_SID -f\ SNAPPLAN -o remove Example In the following example, the snapplan, snap1, is removed from the VxDBA repository. $ /opt/VRTS/bin/dbed_vmchecksnap -S PROD -f snap1 -o remove The snapplan snap1 has been removed.
Prerelease 8 September 2005, 8:55am Creating a Snapshot (dbed_vmsnap) Creating a Snapshot (dbed_vmsnap) The dbed_vmsnap command creates a snapshot of an Oracle database by splitting the mirror volumes used by the database into a snapshot database. You can use the snapshot image on either the same host as the database or on a secondary host provided storage is shared by the two hosts. The snapshot image created by dbed_vmsnap is a frozen image of an Oracle database’s datafiles.
Creating a Snapshot (dbed_vmsnap) Prerelease 8 September 2005, 8:55am 2. If SNAPSHOT_MODE is set to offline in the snapplan, shut down the database. 3. Create the snapshot image using the command: $ /opt/VRTS/bin/dbed_vmsnap -S ORACLE_SID -f SNAPPLAN \ -o snapshot 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.
Prerelease 8 September 2005, 8:55am Creating a Snapshot (dbed_vmsnap) If -r is used in dbed_vmclonedb, make sure is created and owned by Oracle DBA. Otherwise, the following mount points need to be created and owned by Oracle DBA: /prod_db. /prod_ar. dbed_vmsnap ended at 2004-04-02 14:16:11 Example In this example, a snapshot image of the primary database, PROD, is created for a two-host configuration.
Backing Up the Database from Snapshot Volumes (dbed_vmclonedb) Prerelease 8 September 2005, 8:55am Backing Up the Database from Snapshot Volumes (dbed_vmclonedb) Snapshots are most commonly used as a source for backing up a database. The advantage of using snapshot volumes is that the backup will not contest the I/O bandwidth of the physical devices.
Prerelease 8 September 2005, 8:55am Backing Up the Database from Snapshot Volumes (dbed_vmclonedb) 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 Chapter 10, Using Database FlashSnap for Backup and Off-Host Processing 237
Backing Up the Database from Snapshot Volumes (dbed_vmclonedb) Prerelease 8 September 2005, 8:55am The following figure, “Example System Configuration for Database Backup on a Secondary Host” on page 240shows a typical configuration when snapshot volumes are used on a secondary host.
Prerelease 8 September 2005, 8:55am Backing Up the Database from Snapshot Volumes (dbed_vmclonedb) 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 complete the steps in “Summary of Database Snapshot Steps” on page 216, “Validating a Snapplan (dbed_vmchecksnap)” on page 229, and “Creating a Snapshot (dbed_vmsnap)” on page 235. ◆ The volume snapshot must contain the entire database.
Backing Up the Database from Snapshot Volumes (dbed_vmclonedb) Prerelease 8 September 2005, 8:55am Example In this example, snapshot volumes are mounted. $ /opt/VRTS/bin/dbed_vmclonedb -S PROD -g SNAP_PRODdg \ -o mount,new_SID=NEWPROD -f snap1 -r /clone/single dbed_vmclonedb started at 2004-04-02 15:35:41 Mounting /clone/single/prod_db on /dev/vx/dsk/SNAP_PRODdg/SNAP_prod_db. Mounting /clone/single/prod_ar on /dev/vx/dsk/SNAP_PRODdg/SNAP_prod_ar.
Prerelease 8 September 2005, 8:55am Backing Up the Database from Snapshot Volumes (dbed_vmclonedb) Note If you use the Oracle online backup method, you must also backup all the archived log files in order to do a complete restore and recovery of the database. Restoring from Backup Backup copies are used to restore volumes lost due to disk failure, or data destroyed due to human error.
Cloning a Database (dbed_vmclonedb) Prerelease 8 September 2005, 8:55am Cloning a Database (dbed_vmclonedb) This section explains how to create a clone database using the snapshot volumes. You can use snapshots of a primary database to create a clone of the database at a given point in time.
Prerelease 8 September 2005, 8:55am Cloning a Database (dbed_vmclonedb) ◆ Before you can use the dbed_vmclonedb command with the -r relocate_path option (which specifies the initial mount point for the snapshot image), the system administrator must create the mount point and then change the owner to the Oracle database administrator. ◆ If SNAPSHOT_MODE is set to offline or instant, a two-host configuration is required and -r relocate_path is not allowed.
Cloning a Database (dbed_vmclonedb) Prerelease 8 September 2005, 8:55am $ /opt/VRTS/bin/dbed_vmclonedb -S PROD -g SNAP_PRODdg \ -o mountdb,new_sid=NEWPROD -f snap1 -r /clone dbed_vmclonedb started at 2004-04-02 15:34:41 Mounting /clone/prod_db on /dev/vx/dsk/SNAP_PRODdg/SNAP_prod_db. Mounting /clone/prod_ar on /dev/vx/dsk/SNAP_PRODdg/SNAP_prod_ar. All redo-log files found. Database NEWPROD (SID=NEWPROD) is in recovery mode.
Prerelease 8 September 2005, 8:55am Cloning a Database (dbed_vmclonedb) The snapshot status has been updated. dbed_vmclonedb ended at 2004-04-09 23:34:35 ▼ To clone the database automatically Use the dbed_vmclonedb command as follows: $ /opt/VRTS/bin/dbed_vmclonedb -S ORACLE_SID -g snap_dg \ -o recoverdb,new_sid=new_sid[,vxdbavol=vol_name] -f SNAPPLAN \ [-H ORACLE_HOME] [-r relocate_path] Where: ◆ ORACLE_SID is the name of the Oracle database used to create the snapshot.
Cloning a Database (dbed_vmclonedb) Prerelease 8 September 2005, 8:55am Example In the following example, a clone of the primary database is automatically created on a secondary host. $ /opt/VRTS/bin/dbed_vmclonedb -S PROD -g SNAP_PRODdg \ -o recoverdb,new_sid=NEWPROD,vxdbavol=SNAP_arch -f snap2 dbed_vmclonedb started at 2004-04-09 23:03:40 Mounting /clone/arch on /dev/vx/dsk/SNAP_PRODdg/SNAP_arch. Mounting /clone/prod_db on /dev/vx/dsk/SNAP_PRODdg/SNAP_prod_db. All redo-log files found.
Prerelease 8 September 2005, 8:55am Cloning a Database (dbed_vmclonedb) Example In this example, the clone database is shut down, file systems are unmounted, and the snapshot disk group is deported for a clone on a secondary host (a two-host configuration). $ /opt/VRTS/bin/dbed_vmclonedb -o umount,new_sid=NEWPROD \ -f snap2 dbed_vmclonedb started at 2004-04-09 23:09:21 NOTICE: Umounting /clone/arch. NOTICE: Umounting /clone/prod_db.
Cloning a Database (dbed_vmclonedb) Prerelease 8 September 2005, 8:55am Example In this example, the clone database is re-started on the secondary host (a two-host configuration). $ /opt/VRTS/bin/dbed_vmclonedb -S PROD -g SNAP_PRODdg \ -o restartdb,new_sid=NEWPROD,vxdbavol=SNAP_arch -f snap2 dbed_vmclonedb started at 2003-04-09 23:03:40 Mounting /clone/arch on /dev/vx/dsk/SNAP_PRODdg/SNAP_arch. Mounting /clone/prod_db on /dev/vx/dsk/SNAP_PRODdg/SNAP_prod_db. Oracle instance NEWPROD successfully started.
Prerelease 8 September 2005, 8:55am Cloning a Database (dbed_vmclonedb) -- Commands to add tempfiles to temporary tablespaces. -- Online tempfiles have complete space information. -- Other tempfiles may require adjustment. ALTER TABLESPACE TEMP ADD TEMPFILE '/clone_path/temp01.dbf' SIZE 4194304 REUSE AUTOEXTEND ON NEXT 1048576 MAXSIZE 33554432 ; ALTER TABLESPACE TEMP ADD TEMPFILE '/clone_path/temp02.dbf' REUSE; ALTER DATABASE TEMPFILE '/clone_path2/temp02.dbf' OFFLINE; 4.
Resynchronizing the Snapshot to Your Database Prerelease 8 September 2005, 8:55am Resynchronizing the Snapshot to Your Database When you have finished using a clone database or want to refresh it, you can resynchronize it with the original database. This is also known as refreshing the snapshot volume or merging the split snapshot image back to the current database image. After resynchronizing, the snapshot can be retaken for backup or decision-support purposes.
Prerelease 8 September 2005, 8:55am Resynchronizing the Snapshot to Your Database $ /opt/VRTS/bin/dbed_vmsnap -S ORACLE_SID -f SNAPPLAN -o resync For information on resynchronizing the snapshot using the GUI, see “Using the VERITAS Storage Foundation for Oracle Graphical User Interface” on page 265. Example In this example, the snapshot image is resynchronized with the primary database.
Resynchronizing Your Database to the Snapshot Prerelease 8 September 2005, 8:55am Resynchronizing Your Database to the Snapshot If your database becomes corrupted, you can use reverse resynchronization to recover the database from a clone. The reverse resynchronization feature of VERITAS Database FlashSnap enables you to resynchronize the primary database or volume with a clone database or snapshot volume. Reverse resynchronization requires the primary database to be offline so that it remains unchanged.
Prerelease 8 September 2005, 8:55am ▼ Resynchronizing Your Database to the Snapshot To begin reverse resynchronization The -o reverse_resync_begin option of the dbed_vmsnap command imports the disk group that was deported from the secondary host (in a two-host configuration) and joins it back to the original disk group.
Resynchronizing Your Database to the Snapshot ▼ Prerelease 8 September 2005, 8:55am To abort reverse resynchronization 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. This operation is only allowed after -o reverse_resync_begin has been executed and cannot be used after reverse resynchronization has been committed (-o reverse_resync_commit).
Prerelease 8 September 2005, 8:55am Resynchronizing Your Database to the Snapshot -o reverse_resync_abort 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.
Removing a Snapshot Volume Prerelease 8 September 2005, 8:55am Removing a Snapshot Volume If a snapshot volume is no longer needed, you can remove it and free up the disk space for other uses by using the vxedit rm command. Prerequisites ▼ ◆ You must be logged in as root. ◆ If the volume is on a mounted file system, you must unmount it before removing the volume. To remove a snapplan and snapshot volume 1. To remove the snapshot and free up the storage used by it: If the snapshot has been taken: a.
Prerelease 8 September 2005, 8:55am Using Database FlashSnap in an HA Environment Using Database FlashSnap in an HA Environment VERITAS Storage Foundation 4.1 for Oracle supports FlashSnap in the HA environment.
Using Database FlashSnap in an HA Environment 258 Prerelease 8 September 2005, 8:55am VERITAS Storage Foundation for Oracle Administrator’s Guide
Prerelease 8 September 2005, 8:55am Using Database FlashSnap in an HA Environment Chapter 10, Using Database FlashSnap for Backup and Off-Host Processing 259
Using VERITAS NetBackup for Database Backup 11 VERITAS NetBackup™ is a separately licensed product and is not included with VERITAS Storage Foundation for Oracle. The information included here is for reference only. For information about using third-party software for backing up files, see “Using Third-Party Software to Back Up Files” on page 496.
Prerelease 8 September 2005, 8:55am Using VERITAS NetBackup for Backup and Restore 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) database backups. VERITAS NetBackup lets you back up and restore database files and directories. You can set up schedules for automatic, unattended, online, and offline database backup, as well as full or incremental backup.
Using VERITAS NetBackup to Backup and Restore Quick I/O Files Prerelease 8 September 2005, 8:55am Using VERITAS NetBackup to Backup and Restore Quick I/O Files The information in this section assumes that you are not using NetBackup for Oracle to back up and restore Quick I/O files. If you are using NetBackup for Oracle, instead refer to “Using Oracle RMAN to Back Up and Restore Quick I/O Files” on page 497. VERITAS NetBackup does not follow symbolic links when backing up files.
Prerelease 8 September 2005, 8:55am Using VERITAS NetBackup to Backup and Restore Quick I/O Files Note The Oracle backup and restore utility cannot be used to back up and restore Quick I/O files. Note 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.
Using VERITAS NetBackup to Back Up and Restore Oracle Disk Manager Files Prerelease 8 September 2005, 8:55am Using VERITAS NetBackup to Back Up and Restore Oracle Disk Manager Files Oracle allocates Oracle Disk Manager files with contiguous extent layouts for good database performance. When you back up your database using VERITAS NetBackup, extent attributes are backed up automatically. When you restore database files they are allocated using these extent attributes.
Using the VERITAS Storage Foundation for Oracle Graphical User Interface 12 You can access VERITAS Storage Foundation for Oracle, VERITAS Volume Manager, and VERITAS File System functions through the VERITAS Storage Foundation for Oracle graphical user interface (GUI). This chapter describes only how to use the GUI to perform various storage management tasks for your Oracle database.
VERITAS Storage Foundation for Oracle GUI Prerelease 8 September 2005, 8:55am VERITAS Storage Foundation for Oracle GUI The graphical user interface (GUI) allows you to perform storage management duties for Oracle, such as monitoring the database, using Storage Checkpoints and Storage Rollback, and file system space planning. This chapter describes the components of the GUI. Note The GUI uses VxDBA to perform many actions.
Prerelease 8 September 2005, 8:55am VERITAS Storage Foundation for Oracle GUI There are multiple sections within the GUI. The following list describes the sections shown in the graphic, which depicts the Main Window: ◆ Menu Bar - allows you to perform various VxDBA operations. The options in the Menu Bar will vary according to the object in the object tree that you have selected. Note To access online help from the Menu Bar, click Help > Contents.
VERITAS Storage Foundation for Oracle GUI 268 Prerelease 8 September 2005, 8:55am Term Definition Drag Slide the mouse while pressing a mouse button.
Prerelease 8 September 2005, 8:55am Overview of GUI Functions Overview of GUI Functions The GUI allows you to perform many storage management tasks for Oracle. This section offers an overview of those tasks. The tasks that you can perform dynamically from the main menu bar and pop-up menu depend on what is highlighted on the object tree. For example, if you have the Oracle database highlighted in the tree, you can open a database instance from the Oracle menu.
Overview of GUI Functions ◆ Prerelease 8 September 2005, 8:55am Monitoring Agent administration You can use the GUI to set up, configure, start, and stop a monitoring agent, which can be used to send alarm notifications and automatically grow file systems when space usage exceeds user-defined thresholds. Prerequisites ◆ 270 Before running the GUI, you must have appropriate permission to access the GUI. You must make permission changes to allow database administrators to access these tools.
Prerelease 8 September 2005, 8:55am VERITAS Enterprise Administrator Service VERITAS Enterprise Administrator Service To use the VERITAS Storage Foundation for Oracle GUI, VERITAS Enterprise Administrator (VEA) Service must be running on the server. The VEA Service is started when you install the software. Occasionally, you may need to manually start or stop the service or add users to the VEA Service console registry.
VERITAS Enterprise Administrator Service Prerelease 8 September 2005, 8:55am -A grants the user root access. -f allows the user to be a user other than the /opt/VRTSdbed owner. -n indicates the name of the user that will be added or removed. For example, to add a database administrator with the name “oracle” as a user with root privileges, enter the following: # /opt/VRTS/bin/vxdbedusr -a user -A -f -n oracle 3. To add a user without root privileges, use the vxdbedusr command as follows.
Prerelease 8 September 2005, 8:55am VERITAS Enterprise Administrator Service # /opt/VRTS/bin/vxdbedusr -r user -n user_name where -r removes the user from the registry. For example, to remove the user “oracle,” enter the following: # /opt/VRTS/bin/vxdbedusr -r user -n oracle 3. To remove a group, use the vxdbedusr command as follows. # /opt/VRTS/bin/vxdbedusr -r group -n group_name where -r removes the user group from the registry.
VERITAS Enterprise Administrator Service Prerelease 8 September 2005, 8:55am Shutting Down the VERITAS Enterprise Administrator Service Although the VEA Service should remain running, you may need to shut it down manually. ▼ To manually shut down VERITAS Enterprise Administrator Service 1. Verify the status of the VEA Service: # /opt/VRTS/bin/vxsvcctrl status Current state of server : RUNNING 2.
Prerelease 8 September 2005, 8:55am Opening and Closing the VERITAS Storage Foundation for Oracle GUI Opening and Closing the VERITAS Storage Foundation for Oracle GUI You can run the GUI from a Windows or UNIX client machine. You must have the client software installed before you can use the GUI. Prerequisites ◆ Use the /opt/VRTS/bin/vxdbedusr utility to create login names for anyone (other than root) who needs to run the GUI. To run /opt/VRTS/bin/vxdbedusr, you must have superuser (root) privileges.
Opening and Closing the VERITAS Storage Foundation for Oracle GUI Prerelease 8 September 2005, 8:55am Opening the VERITAS Storage Foundation for Oracle GUI from a UNIX Client ▼ To start the VERITAS Storage Foundation for Oracle GUI from a UNIX client 1. From an open terminal window, type /opt/VRTSob/bin/vea and press Enter. Note You can run this command only from root. 2. In the Connection pop-up window, enter the host name for the server to which you are connecting and press the Tab key. 3.
Prerelease 8 September 2005, 8:55am Starting an Oracle Database Instance Starting an Oracle Database Instance You can start an Oracle database instance or a cloned Oracle database instance from the GUI. You must know the UNIX user name and password of the database owner. The steps to restart an Oracle database instance are the same. ▼ To start an Oracle database instance or a cloned Oracle database instance 1. Click the Oracle databases icon in the object tree.
Starting an Oracle Snapshot Database Instance Prerelease 8 September 2005, 8:55am Starting an Oracle Snapshot Database Instance If you created a snapshot using the Database FlashSnap feature, you can start an Oracle snapshot database instance from the secondary host via the GUI. This is the equivalent of cloning the database from the primary host. You must know the UNIX user name and password of the database owner and there must be an existing snapshot.
Prerelease 8 September 2005, 8:55am Starting an Oracle Snapshot Database Instance Note To start an on-host snapshot database, the Relocate path is required. To start an off-host snapshot database, the VxDBA volume name field is required. You can obtain this information by viewing the details after you create a snapshot. If you did not retain the information from the snapshot creation, you can use the dbed_vmchecksnap command or use View Log via the GUI to retrieve the information.
Shutting Down an Oracle Database Instance Prerelease 8 September 2005, 8:55am Shutting Down an Oracle Database Instance The GUI lets you shut down an Oracle database instance. For example, you must shut down the database to perform a Storage Rollback of an entire database. ▼ To shut down an Oracle database instance 1. Click the actual Oracle database in the object tree. (You may need to expand the tree view to find the icon.) 2. Select one of the following methods to stop the database.
Prerelease 8 September 2005, 8:55am ◆ Shutting Down an Oracle Database Instance Abort Use this option to shut down the Oracle database instance instantaneously by aborting the database’s instance. Use this option with extreme caution and only when normal or immediate shutdown does not work, you experience problems when starting the instance, or you need to shut down the instance instantaneously.
Creating Clone Database Prerelease 8 September 2005, 8:55am Creating Clone Database The Create Clone Database wizard guides you through the process of creating a clone of the database using either Storage Checkpoints or Volume Manager Flashsnap. Cloning the database helps you perform operations without affecting your production database. Prerequisites ◆ ▼ The Oracle database must have at least one mandatory archive destination.
Prerelease 8 September 2005, 8:55am Creating Clone Database If you choose to clone the database using an existing Storage Checkpoint, you must select a Storage Checkpoint from the drop-down list. Click Create Clone Database. Click Next. 4. When restarting a Storage Checkpoint clone database that is already created, make sure you check the Restart Database option or you would be starting a new Storage Checkpoint clone database.
Creating Clone Database Prerelease 8 September 2005, 8:55am Creating a Clone Database with a new snapplan ▼ To create a Clone Database with a new snapplan 1. Confirm the Oracle SID. This is a read-only field. 2. Enter the following values: ◆ Full path of the snapplan file ◆ Name of the secondary host ◆ Snapshot plex tag 3. Click Next to continue. The Validate/Modify Snapplan screen is displayed with default values set. 4. If needed, modify any incorrect settings.
Prerelease 8 September 2005, 8:55am Creating Clone Database Original plex and DCO log for ORACLE1 is on PRODdg02. Snapshot plex and DCO log for ORACLE1 is on PRODdg01. Volume oracon on PRODdg is ready for snapshot. Original plex and DCO log for oracon is on PRODdg02. Snapshot plex and DCO log for oracon is on PRODdg01. SNAP_PRODdg for snapshot will include: PRODdg01 ALLOW_REVERSE_RESYNC is yes The snapplan sp3 has been created. 6. In the Create Snapshot dialog, verify the snapplan location.
Creating Clone Database Prerelease 8 September 2005, 8:55am 11. Click OK to continue. You can now use the snapshot as a database backup. Note You will need this information when you start your snapshot database. 12. The Startup Snapshot Database dialog is displayed. In the “connect as” section, confirm the local host name and enter the Oracle home information. Then, enter your UNIX user name and password. Caution Make sure that the VEA service is running on the secondary host.
Prerelease 8 September 2005, 8:55am Creating Clone Database ◆ If you select a snapplan with INIT_FULL status, the Create Snapshot dialog is displayed. Follow the steps from step 6 on page 285 in the “Creating a Clone Database with a new snapplan” on page 284 section. ◆ If you select a snapplan with SNAPSHOT_END status displays the Startup Snapshot Database dialog is displayed. Follow the steps from step 12 on page 286 in the “Creating a Clone Database with a new snapplan” on page 284section.
Removing a Clone Database Prerelease 8 September 2005, 8:55am Removing a Clone Database In releases prior to 4.1, for removing a cloned database you were required to go through separate menus to shut down and unmount clone databases. VERITAS Storage Foundation for Oracle 4.1, provides the Remove Clone Database wizard, that can be accessed from the database instance node. The Remove Clone Database wizard helps in shutting down and unmounting the clone database.
Prerelease 8 September 2005, 8:55am Removing a Clone Database 4. Click the Remove Clone Database button. 5. In the Confirmation dialog, click Yes to proceed with removing the clone database. Removing a Storage Checkpoint Clone Database Removing a Storage Checkpoint clone database allows you to unmount the clone database. It also gives you the option to remove the checkpoint. 1. In the object tree, click a clone database that was created using a Storage Checkpoint.
Using the Monitoring Agent Prerelease 8 September 2005, 8:55am Using the Monitoring Agent You can use a Monitoring Agent to manage and monitor VxFS file systems, Oracle tablespaces, and datafile space usage. The Monitoring Agent monitors the file system space, and when the space usage reaches a configured threshold value, a predefined action script grows the file system automatically. The agent can be enabled at boot-time.
Prerelease 8 September 2005, 8:55am Using the Monitoring Agent also specify the space monitoring and alarm information for each file system, tablespace, and datafile. You can edit these files manually to change settings, and then restart the Monitoring Agent. The Monitoring Agent uses the /etc/vx/vxdba/$ORACLE_SID/include file to check that all files are up-to-date and are being monitored. This file is created by VERITAS Storage Foundation for Oracle and should not be edited.
Using the Monitoring Agent Prerelease 8 September 2005, 8:55am Enable / Disable the Monitoring Agent at Boot-Time 4. Optionally, if you would like to set up the Monitoring Agent to become enabled at boot-time, right click the Monitoring Agent in the object tree and select Enabled at Boot Time. or If you would like to set up the Monitoring Agent to become disabled at boot-time, right click the Monitoring Agent in the object tree and select Disabled at Boot Time. 5. Enter your root password.
Prerelease 8 September 2005, 8:55am 3. Using the Monitoring Agent Enter your root password. Then click OK. If the Monitoring Agent was successfully stopped, you will receive a confirmation message. Click OK to continue. Viewing or Changing Monitoring Agent Values You can view the settings of your active Monitoring Agent. You also have the option to change the default values of the Monitoring Agent, if needed.
Managing Storage Checkpoints Prerelease 8 September 2005, 8:55am Managing Storage Checkpoints A Storage Checkpoint is like an online backup of a database that contains a point-in-time database image. Storage Checkpoints can later be used to restore the image of a datafile, a tablespace, or the entire database to any earlier state recorded by the Storage Checkpoints.
Prerelease 8 September 2005, 8:55am ◆ Managing Storage Checkpoints From the menu bar, select Storage Checkpoints > Create Storage Checkpoint. or ◆ Right click the Storage Checkpoints icon to bring up a pop-up menu. Then, click Create Storage Checkpoint. The Create a Storage Checkpoint wizard is displayed. 3. Verify the Oracle SID, which is the Oracle System Identifier, for which you are creating the Storage Checkpoint. This is a read-only field. 4. Select one of the following options: 5.
Managing Storage Checkpoints Prerelease 8 September 2005, 8:55am Note The file system quota information is only available for disk layout version 6. Mounting a Storage Checkpoint You can mount and write to Storage Checkpoints just as you can do with any file system. See “Using Storage Checkpoints and Storage Rollback for Backup and Restore” on page 163 for more information. ▼ To mount a Storage Checkpoint 1. Click a specific Storage Checkpoint in the object tree.
Prerelease 8 September 2005, 8:55am Managing Storage Checkpoints Note When you select the Read/Write option, the GUI creates an identical Storage Checkpoint with the same name plus a wr001 suffix, where 001 is a sequential number. The GUI mounts the new Storage Checkpoint and leaves the original Storage Checkpoint unmounted. This allows you to roll back to the original Storage Checkpoint. 6. Click Mount to mount the Storage Checkpoint. 7.
Managing Storage Checkpoints Prerelease 8 September 2005, 8:55am Removing a Storage Checkpoint Occasionally, you may need to manually remove Storage Checkpoints that are no longer needed. For example, you can remove a Storage Checkpoint on a file system to free up needed space. Prerequisites ◆ ▼ Before you can remove a mounted Storage Checkpoint, you must first unmount it. To remove a Storage Checkpoint 1. Click a specific Storage Checkpoint in the object tree.
Prerelease 8 September 2005, 8:55am Managing Storage Checkpoints Storage Checkpoints can only be used to roll back files that are damaged due to a software error or a human error (for example, accidental deletion of a table). Because Storage Checkpoints reside on the same physical disks as the primary file system, when a file is corrupted due to a media failure, the file on the Storage Checkpoints will not be available either. In this case, you need to restore files from a tape backup.
Managing Storage Checkpoints Prerelease 8 September 2005, 8:55am The Rollback a Storage Checkpoint wizard is displayed. 4. Verify that you are rolling back to the correct Storage Checkpoint and click Next to continue. If you selected the wrong Storage Checkpoint, click Cancel. The information on this screen is read-only. 5. On the second screen, use the drop-down menu to select the appropriate buffer size in the Rollback Buffer Size field. The default buffer size is 128K.
Prerelease 8 September 2005, 8:55am Managing Storage Checkpoints Rolling back a tablespace is used for complete recovery of the tablespace. It is not designed for point-in-time (incomplete) tablespace recovery, which is more complicated and requires interaction with Oracle Customer Support. The tablespace point-in-time recovery requires using a clone database. See “Creating Clone Database” on page 282 for more information.
Managing Storage Checkpoints Prerelease 8 September 2005, 8:55am 7. Click the Rollback a Tablespace button to indicate that you are rolling back the tablespace to the Storage Checkpoint. 8. Click Next to continue. Select the tablespace, or tablespaces, you would like to roll back by clicking the appropriate checkbox in the Tablespace list. 9. Click Roll Back to continue. 10. If the Storage Rollback was successful, you will receive a confirmation message. Click OK to continue. 11.
Prerelease 8 September 2005, 8:55am Managing Storage Checkpoints The Rollback a Storage Checkpoint wizard is displayed. 4. Verify that you are rolling back to the correct Storage Checkpoint and click Next to continue. If you selected the wrong Storage Checkpoint, click Cancel. The information on this screen is read-only. 5. On the second screen, use the drop-down menu to select the appropriate buffer size in the Rollback Buffer Size field. The default buffer size is 128K.
Managing Storage Checkpoints Prerelease 8 September 2005, 8:55am Prerequisites ◆ You must enable the Monitoring Agent to use the Storage Checkpoint policy. Creating a Storage Checkpoint Policy ▼ To create a Storage Checkpoint policy 1. Click the Storage Checkpoints icon in the object tree. (You may need to expand the tree view to find the icon.) 2. Select one of the following methods to create a Storage Checkpoint policy. Right click the Storage Checkpoint icon to bring up a pop-up menu.
Prerelease 8 September 2005, 8:55am Managing Storage Checkpoints Disabling a Storage Checkpoint Policy ▼ To disable a Storage Checkpoint policy 1. Click the Storage Checkpoints icon in the object tree. (You may need to expand the tree view to find the icon.) 2. Select one of the following methods to disable a Storage Checkpoint policy. Right click the Storage Checkpoint icon to bring up a pop-up menu. Then, click Policy. The Storage Checkpoint Policy window is displayed. 3.
Managing Snapshots with Database FlashSnap Prerelease 8 September 2005, 8:55am Managing Snapshots with Database FlashSnap With VERITAS Database FlashSnap, you can create a point-in-time copy of a database for backup and off-host processing. For more information, see “Using Database FlashSnap for Backup and Off-Host Processing” on page 197. From the GUI, you can create snapshots of your database using snapplans. You can also resynchronize snapshots to your database and your database to a snapshot.
Prerelease 8 September 2005, 8:55am ▼ Managing Snapshots with Database FlashSnap To create a snapplan 1. Click the Snapplans icon in the object tree. (You may need to expand the tree view to find the icon.) 2. Select one of the following methods to create a snapshot plan. ◆ From the menu bar, select Snapplans > Create Snapplan. or ◆ Right click the Snapshot Plans icon to bring up a pop-up menu. Then click Create Snapplan. The Create Snapplan wizard is then displayed. 3. Confirm the Oracle SID.
Managing Snapshots with Database FlashSnap Prerelease 8 September 2005, 8:55am SNAPSHOT_DG is SNAP_PRODdg SNAPSHOT_MODE is online The database is running in archivelog mode. ARCHIVELOG_DEST is /prod_db SNAPSHOT_PLAN_FOR is database SNAPSHOT_ARCHIVE_LOG is yes ARCHIVELOG_DEST=/prod_db is mount on /dev/vx/dsk/PRODdg/ORACLE1. Examining Oracle volume and disk layout for snapshot. Volume ORACLE1 on PRODdg is ready for snapshot. Original plex and DCO log for ORACLE1 is on PRODdg02.
Prerelease 8 September 2005, 8:55am ▼ Managing Snapshots with Database FlashSnap To validate or modify a snapplan 1. Click a specific snapplan in the object tree. (You may need to expand the tree view to find the icon.) 2. Select one of the following methods to validate or modify a snapshot plan. ◆ From the menu bar, select Snapplan > Modify/Validate Snapplan. or ◆ Right click the snapplan to bring up a pop-up menu. Then click Modify/Validate Snapplan.
Managing Snapshots with Database FlashSnap Prerelease 8 September 2005, 8:55am SNAPSHOT_PLAN_FOR is database SNAPSHOT_ARCHIVE_LOG is yes ARCHIVELOG_DEST=/prod_db is mount on /dev/vx/dsk/PRODdg/ORACLE1. Examining Oracle volume and disk layout for snapshot. Volume ORACLE1 on PRODdg is ready for snapshot. Original plex and DCO log for ORACLE1 is on PRODdg02. Snapshot plex and DCO log for ORACLE1 is on PRODdg01. Volume oracon on PRODdg is ready for snapshot.
Prerelease 8 September 2005, 8:55am Managing Snapshots with Database FlashSnap If the snapplan was successfully removed, you will receive a confirmation message similar to the following: Successfully removed snapplan: sp1 4. Click the Show details checkbox to view the actions taken. You should see information similar to the following: The snapplan has been removed. Click OK to continue.
Managing Snapshots with Database FlashSnap Prerelease 8 September 2005, 8:55am Note Force snapshot creation 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.
Prerelease 8 September 2005, 8:55am Managing Snapshots with Database FlashSnap Prerequisites ▼ ◆ Make sure you have enough disk space to create a clone database on your system. ◆ You must have an existing snapshot. To create a clone database with a snapshot 1. Click the Oracle icon in the object tree. (You may need to expand the tree view to find the icon.) 2. Select one of the following methods to start the snapshot database.
Managing Snapshots with Database FlashSnap Prerelease 8 September 2005, 8:55am If the snapshot database was successfully started, you will receive a confirmation message. Click OK to continue. Resynchronizing a Snapshot to a Database Resynchronizing a snapshot to a database will refresh the snapshot so that it contains the most recent changes made to your production database. Prerequisites ◆ You must be logged in as the Oracle database administrator.
Prerelease 8 September 2005, 8:55am Managing Snapshots with Database FlashSnap Resynchronizing a Database to a Snapshot Resynchronizing your database to a snapshot, also known as reverse resynchronization, reverts your database to a snapshot. Use this option if your database becomes corrupted and you need to restore your database to a previous point-in-time. Prerequisites ◆ You must be logged in as the Oracle primary database administrator.
Managing Snapshots with Database FlashSnap ◆ Prerelease 8 September 2005, 8:55am Brings up the database snapshot image as the primary database. Note The primary database must be offline to perform this action. 6. If the begin action was successful, you will receive a confirmation message. Click Show details to see the actions completed. When you are through, click OK to continue. 7. Again, click the snapplan on which you want to perform the reverse resynchronization. 8.
Prerelease 8 September 2005, 8:55am ▼ Managing Snapshots with Database FlashSnap To abort the reverse resynchronization operation 1. Click the snapplan for which the reverse resynchronization was begun. 2. Select one of the following methods to resynchronize the database to a snapshot. ◆ From the menu bar, select Snapplan > Reverse Resync Snapshot. or ◆ Right click the snapplan to bring up a pop-up menu. Then click Reverse Resync Snapshot. The Reverse Resync wizard is displayed. 3.
Managing Snapshots with Database FlashSnap Prerelease 8 September 2005, 8:55am or ◆ Right click the snapplan to bring up a pop-up menu. Then click View Log. A pop-up window appears displaying the path of the Snapplan and the Log. The information displayed is similar to the following output: SNAPSHOT_VERSION=4.
Prerelease 8 September 2005, 8:55am Maintaining Your System Configuration Maintaining Your System Configuration VERITAS Storage Foundation for Oracle maintains a repository that stores the pertinent information needed to display configuration information. This repository is located at /etc/vx/vxdba/$ORACLE_SID. When the database configuration changes, the information stored in the repository may not be up-to-date.
Maintaining Your System Configuration ◆ 3. Prerelease 8 September 2005, 8:55am Right click the Tablespaces icon to bring up a pop-up menu. Then click Rescan. If the refresh was successful, you will receive a confirmation message. Click OK to continue. Viewing Oracle Datafile Topology VERITAS Storage Foundation 4.1 for Oracle provides an enhanced Topology display option. The Topology display represents Storage Mapping as a balanced tree. Objects such as files, directories, volumes, plexes etc.
Prerelease 8 September 2005, 8:55am ▼ Maintaining Your System Configuration To view the topology of a Datafile 1. Click a datafile in the object tree. (You may need to expand the tree view to find the icon.) 2. Select one of the following methods to generate datafile statistics. ◆ From the menu bar, select Datafiles > Topology. or ◆ 3. Right click the datafile to bring up a pop-up menu. Then click Topology. The storage Topology is displayed.
Maintaining Your System Configuration Prerelease 8 September 2005, 8:55am Note The Get Statistics button remains disabled until you fill in the above two fields. 5. The Total Sampling Period (in hours) displays the time used to perform the sampling of the data. 6. The Display accumulated data checkbox is checked by default. 7. The Time Elapsed (in minutes) displays the amount of time it took to sample the data. The progress status bar displays the percentage of sampling that is being completed. 8.
Prerelease 8 September 2005, 8:55am Maintaining Your System Configuration Prerequisites ◆ Files you want to convert must be regular datafiles on VxFS file systems or links that point to regular VxFS files. Usage Notes ◆ ▼ Converting existing datafiles to be Quick I/O files may not be the optimal thing to do if these files are fragmented. To convert Oracle datafiles to Quick I/O files 1. Shut down the database from the GUI. 2. Click a datafile in the object tree.
Maintaining Your System Configuration 3. Prerelease 8 September 2005, 8:55am Select one of the following methods to generate datafile statistics. ◆ From the menu bar, select Datafiles > Conversion. or ◆ 4. Right click the Quick I/O file to bring up a pop-up menu. Then click Conversion. At the prompt, click Yes to convert the Quick I/O files to a regular datafile. If the Quick I/O file was successfully converted to a regular datafile, you will receive a confirmation message.
Prerelease 8 September 2005, 8:55am ▼ Maintaining Your System Configuration To scan the system configuration of a database 1. Click the Oracle database in the object tree. (You may need to expand the tree view to find the icon.) 2. Select one of the following methods to view the database configuration information. ◆ From the menu bar, select Oracle > Check System Configuration. or ◆ 3. Right click the database to bring up a pop-up menu. Then click Check System Configuration.
Maintaining Your System Configuration Prerelease 8 September 2005, 8:55am pref_strength = 20 buf_breakup_size = 262144 discovered_direct_iosz = 262144 max_direct_iosz = 2097152 default_indir_size = 8192 qio_cache_enable = 0 write_throttle = 127232 max_diskq = 2097152 initial_extent_size = 8 max_seqio_extent_size = 2048 max_buf_data_size = 8192 hsm_write_prealloc = 0 Examining Oracle volume and file system layout. NOTICE: Data for database TEST9i is contained in one volume group.
Prerelease 8 September 2005, 8:55am Maintaining Your System Configuration Saving the System Configuration You can save the System Configuration only when using VERITAS Storage Foundation for Oracle Enterprise Edition. ▼ To save the system configuration of a database 1. Click the Oracle database in the object tree. (You may need to expand the tree view to find the icon.) 2. Select one of the following methods to view the database configuration information.
Maintaining Your System Configuration 328 Prerelease 8 September 2005, 8:55am VERITAS Storage Foundation for Oracle Administrator’s Guide
13 Using the VxDBA Utility This chapter describes how to use the VxDBA utility to support administrative tasks for Oracle database management. This is the last release of Storage Foundation for Oracle to support the VxDBA utility.
Overview of the VxDBA Menus Prerelease 8 September 2005, 8:55am Overview of the VxDBA Menus VxDBA Main Menu The VxDBA utility main menu provides access to the following operations: VERITAS Storage Foundation for Oracle(ORACLE_SID 'PROD') Menu: Database Main 1 2 3 4 5 6 Database Administration Display Database/VxDBA Information Storage Checkpoint Administration Storage Rollback Administration Monitoring Agent Administration Storage Checkpoint Capacity Planning ? q x Display Help About the Current Menu
Prerelease 8 September 2005, 8:55am ◆ Overview of the VxDBA Menus 2 - Display Database/VxDBA Information Use this menu to display information about various aspects of your database environment, as well as examine and save configuration information for database recovery.
Overview of the VxDBA Menus ◆ Prerelease 8 September 2005, 8:55am ◆ Set Number of Storage Rollback Threads ◆ Set Buffer Size for Storage Rollback ◆ Show Backup Control File List 5 - Monitoring Agent Administration Use this menu to monitor and manage key aspects of your database environment. The primary function of VxDBA’s Monitoring Agent is to monitor space usage of your database file systems, tablespaces, and datafiles.
Prerelease 8 September 2005, 8:55am ◆ Overview of the VxDBA Menus x - Exit From VxDBA Utility This menu option exits the VxDBA utility. VxDBA Submenu Operations Most of the operations available from the VxDBA submenus are run as the Oracle database administrative user (typically, user ID oracle), which allows the VxDBA utility permission to connect directly to the database and gather information from the system catalog.
Starting VxDBA Prerelease 8 September 2005, 8:55am Starting VxDBA Most VxDBA utility operations can be run by the Oracle Database Administrator (typically, the user ID oracle) of the database instance. Some VxDBA utility operations, like many of the file system space management operations, require superuser (root) privileges. VxDBA prompts you for the root password when required. Prerequisites Before running VxDBA, you must: ▼ ◆ If you are using SPFile, run the dbed_update command.
Prerelease 8 September 2005, 8:55am ▼ Starting VxDBA To start VxDBA 1. Before starting VxDBA, run the command dbed_update at least once to create or update the VxDBA repository. 2. To start VxDBA, enter the following command at the administrative prompt: $ /opt/VRTSdbed/bin/dbed_vxdba VxDBA starts up and displays the main menu containing the available operations.
Using VxDBA to Perform Administrative Operations Prerelease 8 September 2005, 8:55am Using VxDBA to Perform Administrative Operations The rest of this chapter details the administrative operations available through the VxDBA utility. Managing Your Database Use the Database Administration menu to perform basic database operations.
Prerelease 8 September 2005, 8:55am Using VxDBA to Perform Administrative Operations Starting Up a Database Instance The VERITAS Storage Foundation for Oracle software package includes adaptable scripts that are run automatically when starting the database using the VxDBA utility. You can modify these scripts to run other tools and applications or to start and stop other services before and/or after database startup.
Using VxDBA to Perform Administrative Operations Prerelease 8 September 2005, 8:55am Shutting Down a Database Instance The VERITAS Storage Foundation for Oracle software package includes adaptable scripts that are automatically run when stopping the database using the VxDBA utility. You can modify these scripts to run other tools and applications or to start and stop other services before and/or after database shutdown.
Prerelease 8 September 2005, 8:55am Using VxDBA to Perform Administrative Operations Shutdown NORMAL. Use this menu option to shut down the Oracle instance in normal situations. When this operation is selected, no new database connections are allowed. Oracle waits for all currently connected users to disconnect from the database, and then closes and dismounts the database before shutting down the instance. The next database startup does not require an instance recovery. Shutdown TRANSACTIONAL.
Using VxDBA to Perform Administrative Operations Prerelease 8 September 2005, 8:55am After the Oracle instance is shut down, VxDBA displays the Database Administration menu. Displaying Database/VxDBA Information Use the Display Database/VxDBA Information menu option to display information about various aspects of your database environment.
Prerelease 8 September 2005, 8:55am Using VxDBA to Perform Administrative Operations Save Volume/File System/Database Configuration. Use this menu option to save important system hardware, operating system, kernel tunables, database layout and control files, volume and file system configuration, packaging, and license information.
Using VxDBA to Perform Administrative Operations Prerelease 8 September 2005, 8:55am Displaying and Updating Tablespace Information Use the Display/Update Tablespace Information menu option to display the list of tablespaces of an Oracle instance and their associated datafiles. This menu option is also available on the Database Administration menu.
Prerelease 8 September 2005, 8:55am Using VxDBA to Perform Administrative Operations This operation displays a screen similar to the following: ----------------------------------------------------------VxDBA: Display Datafile/File System Information - PROD ----------------------------------------------------------Database Status # File Systems # Tablespaces # Datafiles : : : : File System ----------------------/db01 /db01 /db01 /db01 ONLINE 1 4 4 File File Type Name ------------ ----------------------
Using VxDBA to Perform Administrative Operations Prerelease 8 September 2005, 8:55am This operation displays a screen similar to the following: VERITAS Storage Foundation for Oracle (ORACLE_SID 'PROD') Menu: Display VxDBA/Database Configuration Files 1 2 3 4 5 6 7 8 9 Database Pre-Startup Script Database Post-Startup Script Database Pre-Shutdown Script Database Post-Shutdown Script VxDBA Settings File VxDBA Monitoring Agent Configuration File Oratab File (missing) Oracle Listener Oracle Configuration Fi
Prerelease 8 September 2005, 8:55am Using VxDBA to Perform Administrative Operations # chmod 4550 /usr/sbin/vxdisk This operation displays a screen similar to the following: ------------------------------------------------------------VxDBA: Examine Volume/File System/Database Configuration ------------------------------------------------------------ORACLE_SID : PROD ORACLE_HOME : /local/oracle/links Database Status : ONLINE # File Systems : 1 # Tablespaces : 1 # Datafiles : 1 Examining file system attrib
Using VxDBA to Perform Administrative Operations ◆ Prerelease 8 September 2005, 8:55am License information This option creates a collection of files under a directory you specified. Copy these files to off-host, online storage to assist you in a disaster recovery situation. Note Only users with superuser (root) privileges can perform this operation. Note Depending on the configuration and size of your system, this menu option can create sizable files.
Prerelease 8 September 2005, 8:55am Using VxDBA to Perform Administrative Operations Managing Storage Checkpoints Use the Storage Checkpoint Administration menu option to create, display, mount, unmount, and remove Storage Checkpoints. A Storage Checkpoint can be considered an online database backup that contains a point-in-time database image.
Using VxDBA to Perform Administrative Operations Prerelease 8 September 2005, 8:55am Mount Storage Checkpoints. Use this menu option to mount a Storage Checkpoint into the file system namespace. Mounted Storage Checkpoints appear as any other file system on the machine, and you can access mounted Storage Checkpoints using all normal file system-based commands. Unmount Storage Checkpoints. Use this menu option to unmount a mounted Storage Checkpoint. Remove Storage Checkpoints.
Prerelease 8 September 2005, 8:55am Using VxDBA to Perform Administrative Operations Create New Storage Checkpoints displays a screen similar to the following: ---------------------------------------------------VxDBA: Create New Storage Checkpoints - PROD ---------------------------------------------------NOTICE: To correctly create a Storage Checkpoint, you must have up-to-date tablespace information stored in VxDBA's database.
Using VxDBA to Perform Administrative Operations Prerelease 8 September 2005, 8:55am Backing up include file and list of file system for VxDBA in /etc/vx/vxdba/PROD/checkpoint_dir/Checkpoint_971672042 Do you want to display the instance's Storage Checkpoints? [y,n,q,?] (default: y) y Displaying Storage Checkpoints This operation displays the list of Storage Checkpoints created by the VxDBA utility on the file systems used by the Oracle instance.
Prerelease 8 September 2005, 8:55am ◆ Using VxDBA to Perform Administrative Operations You are in the middle of creating a new Storage Checkpoint and the database or system crashes. When the system or database is back online, VxDBA detects that not all of the file systems used by the database contain the named Storage Checkpoint. You should consider deleting partial Storage Checkpoints that are a result of a database or system crash, and create a new Storage Checkpoint.
Using VxDBA to Perform Administrative Operations Prerelease 8 September 2005, 8:55am Display Storage Checkpoints displays a screen similar to the following: -----------------------------------------------------VxDBA: Display Storage Checkpoints - PROD -----------------------------------------------------Storage Checkpoint ------------------------------Checkpoint_971672042 Checkpoint_903937870 Checkpoint_901426272 Creation Time Status -------------------------- -----Sun Mar 9 13:55:53 2003 C+R Fri Apr 18
Prerelease 8 September 2005, 8:55am Using VxDBA to Perform Administrative Operations Mount Storage Checkpoints displays a screen similar to the following: ---------------------------------------------------VxDBA: Mount Storage Checkpoints - PROD ---------------------------------------------------# -1 2 3 Storage Checkpoint -----------------------------Checkpoint_971672042 Checkpoint_903937870 Checkpoint_901426272 Creation Time -------------------------Sun Mar 9 13:55:53 2003 Fri May 13 22:51:10 2003 We
Using VxDBA to Perform Administrative Operations Prerelease 8 September 2005, 8:55am You must supply a mount point for the Storage Checkpoint. You can create a new directory for the mount point, or use an existing directory. If you use an existing directory, the directory must be empty. Enter a mount point for the writable Storage Checkpoint: /wckpt Mounting Storage Checkpoint Checkpoint_971672042 under /wckpt.
Prerelease 8 September 2005, 8:55am Using VxDBA to Perform Administrative Operations Unmounting Storage Checkpoints This operation lets you unmount a previously mounted Storage Checkpoint.
Using VxDBA to Perform Administrative Operations Prerelease 8 September 2005, 8:55am Removing Storage Checkpoints This operation removes Storage Checkpoints that are no longer needed. For example, you can remove a Storage Checkpoint on a file system to free up needed space.
Prerelease 8 September 2005, 8:55am Using VxDBA to Perform Administrative Operations Note When you remove Storage Checkpoints created by NetBackup, remember to restart the backup schedule. Also remember that NetBackup needs two Storage Checkpoints to perform an incremental backup. If you remove Storage Checkpoints needed for incremental backups, NetBackup will perform a full backup instead of an incremental backup.
Using VxDBA to Perform Administrative Operations Prerelease 8 September 2005, 8:55am Storage Checkpoints can only be used to roll back files that are damaged due to a software error or a human error (for example, accidental deletion of a table). Because Storage Checkpoints reside on the same physical disks as the primary file system, when a file is corrupted due to a media failure, the file on the Storage Checkpoints will not be available either. In this case, you need to restore files from a tape backup.
Prerelease 8 September 2005, 8:55am Using VxDBA to Perform Administrative Operations Roll Back the Database to a Storage Checkpoint displays a screen similar to the following: -------------------------------------------------------------VxDBA: Roll Back the Database to a Storage Checkpoint - PROD -------------------------------------------------------------ORACLE_SID ORACLE_HOME Database Status # File Systems # Tablespaces # Datafiles : : : : : : PROD /usr1/oracle ORA-01034: ORACLE not available 1 4 4
Using VxDBA to Perform Administrative Operations Prerelease 8 September 2005, 8:55am Do you want to roll back the database to Fri May 13 22:51:10 2003? [y,n,q,?] (default: n) y The database has been rolled back to a Storage Checkpoint dated Fri Apr 11 15:13:13 2003 You must follow the recovery procedure described in the Oracle documentation before you can use the database. Press to continue... VxDBA first displays a list of Storage Checkpoints for selection.
Prerelease 8 September 2005, 8:55am Using VxDBA to Perform Administrative Operations Rolling Back a Tablespace to a Storage Checkpoint If a tablespace is corrupted or removed due to a software error or a human mistake, this operation rolls back all of the files of the tablespace to a Storage Checkpoint. Note Rolling back a tablespace is used for complete recovery of the tablespace.
Using VxDBA to Perform Administrative Operations Prerelease 8 September 2005, 8:55am VxDBA prompts you for a tablespace name, and then displays a list of Storage Checkpoints: From the following list, select the by the tablespace, to roll back the Back Files to a Storage Checkpoint’ roll back a single file or a set of # -1 2 Storage Checkpoint -----------------------------Checkpoint_903937870 Checkpoint_901426272 Storage Checkpoint, used files to. Use the ’Roll option if you only plan to files.
Prerelease 8 September 2005, 8:55am ▼ Using VxDBA to Perform Administrative Operations If the database is online Roll Back a Tablespace to a Storage Checkpoint displays a screen similar to the following: --------------------------------------------------------------VxDBA: Roll Back a Tablespace to a Storage Checkpoint - PROD --------------------------------------------------------------ORACLE_SID ORACLE_HOME : PROD : /usr1/oracle Database Status # File Systems # Tablespaces # Datafiles : : : : ONLINE
Using VxDBA to Perform Administrative Operations Prerelease 8 September 2005, 8:55am VxDBA prompts you for a tablespace name, and then displays a list of Storage Checkpoints: From the following list, select the by the tablespace, to roll back the Back Files to a Storage Checkpoint’ roll back a single file or a set of # -1 2 Storage Checkpoint -----------------------------Checkpoint_903937870 Checkpoint_901426272 Storage Checkpoint, used files to. Use the ’Roll option if you only plan to files.
Prerelease 8 September 2005, 8:55am Using VxDBA to Perform Administrative Operations Rolling Back Datafiles to a Storage Checkpoint This operation rolls back database files to a Storage Checkpoint. You can also use this operation to roll back more than one tablespace. Specify the list of files for Storage Rollback in a list file, or enter the list of files one by one.
Using VxDBA to Perform Administrative Operations Prerelease 8 September 2005, 8:55am From the following list, select the Storage Checkpoint to roll back the files to. # -1 2 Storage Checkpoint -----------------------------Checkpoint_903937870 Checkpoint_901426272 Creation Time -------------------------Fri May 13 22:51:10 2003 Wed May 11 16:17:52 2003 Status -----C+R P+R Enter a Storage Checkpoint number [,q,?] 1 The following information may be required for Oracle recovery procedures.
Prerelease 8 September 2005, 8:55am ▼ Using VxDBA to Perform Administrative Operations If the database is online Roll Back Files to a Storage Checkpoint displays a screen similar to the following: -------------------------------------------------------VxDBA: Roll Back Files to a Storage Checkpoint - PROD -------------------------------------------------------ORACLE_SID ORACLE_HOME : PROD : /usr1/oracle Database Status # File Systems # Tablespaces # Datafiles : : : : ONLINE 1 4 4 WARNING: Oracle inst
Using VxDBA to Perform Administrative Operations Prerelease 8 September 2005, 8:55am Enter a Storage Checkpoint number [,q,?] 1 The following information may be required for Oracle recovery procedures. Times reflect the real begin and end times for Oracle tablespaces being in hot-backup mode.
Prerelease 8 September 2005, 8:55am Using VxDBA to Perform Administrative Operations Setting the Number of Storage Rollback Threads This operation lets you configure the number of threads used when rolling back an Oracle datafile. Performance is a critical factor when rolling a file back to a Storage Checkpoint. By default, 8 lightweight threads are used to partition up and recover a datafile.
Using VxDBA to Perform Administrative Operations Prerelease 8 September 2005, 8:55am Setting the Buffer Size for Storage Rollback This operation lets you configure the buffer size used for Storage Rollback. As with setting the number of Storage Rollback threads, the buffer size configured for reads and writes when rolling back an Oracle datafile can also affect performance. By default, a 128K read/write buffer is used.
Prerelease 8 September 2005, 8:55am Using VxDBA to Perform Administrative Operations Showing the Backup Control File List This operation displays the list of control files that VxDBA has backed up each time you create a Storage Checkpoint using VxDBA.
Using VxDBA to Perform Administrative Operations Prerelease 8 September 2005, 8:55am intends to perform. If it is determined that a backup control file is required for recovery, it can be copied from the directory location shown in the Backup Control File field of the above display.
Prerelease 8 September 2005, 8:55am ◆ Using VxDBA to Perform Administrative Operations Amount is either a percentage or a value in megabytes by which to grow file systems when the Grow Threshold is reached or exceeded The VxDBA Monitoring Agent operations are driven from the following files: ◆ /opt/VRTSdbed/lib/dbed_mon_config.base ◆ /etc/vx/vxdba/$ORACLE_SID/dbed_mon_config.$ORACLE_SID ◆ /etc/vx/vxdba/$ORACLE_SID/dbed_mon_fslist.$ORACLE_SID ◆ /etc/vx/vxdba/$ORACLE_SID/dbed_mon_oralist.
Using VxDBA to Perform Administrative Operations Prerelease 8 September 2005, 8:55am Monitoring Agent is looking for potential removal candidates. A Storage Checkpoint must have an entry in the /etc/vx/vxdba/$ORACLE_SID/checkpoint_dir directory before it is considered owned by the database. This is done automatically by the provided VxDBA and dbed_ckpt create utilities and ensures that, if multiple databases share the same file system(s), the policy for one database does not affect another.
Prerelease 8 September 2005, 8:55am Using VxDBA to Perform Administrative Operations Enable/Disable/Modify Space Alarm Settings Use this menu option to control the Monitoring Agent activity and modify the current space alarm settings on the file systems used by the Oracle instance. Displaying File System Space Usage This operation displays the space usage of the file system and the Storage Checkpoints used by the Oracle instance.
Using VxDBA to Perform Administrative Operations Prerelease 8 September 2005, 8:55am In this example, the space used by Checkpoint_901426272 is less than 1 MB, which means the Storage Checkpoint does not contain many data blocks. This means that the database has not modified many distinct data blocks since this Storage Checkpoint was created. Another Storage Checkpoint may have been created after this one, with all subsequent changes going to the new Storage Checkpoint.
Prerelease 8 September 2005, 8:55am Using VxDBA to Perform Administrative Operations After you start the VxDBA Monitoring agent, Display File System Space Alarm Settings displays the list of file systems and the space alarm status: ------------------------------------------------------------VxDBA: Display File System Space Alarm Settings - PROD ------------------------------------------------------------- ORACLE_SID ORACLE_HOME : PROD : /usr1/oracle Database Status # Tablespaces :4 # Datafiles :4 : O
Using VxDBA to Perform Administrative Operations Prerelease 8 September 2005, 8:55am Enabling, Disabling, or Modifying Space Alarm Settings When the file system runs out of space, VxFS automatically removes Storage Checkpoints to free up space. This could happen when Oracle is processing update transactions such that original data blocks are saved in the Storage Checkpoints.
Prerelease 8 September 2005, 8:55am Using VxDBA to Perform Administrative Operations After you enter the root password, Enable/Disable/Modify Space Alarm Settings displays a screen similar to the following: VERITAS Storage Foundation for Oracle (ORACLE_SID 'PROD') Menu: Enable/Disable/Modify Space Alarm Settings Database Status # File Systems # Tablespaces # Datafiles : : : : ORA-01031: insufficient privileges (1) (4) (4) 1 2 3 4 5 Enable or Disable Boot-Time Start of Monitoring Agent Set Monitoring/
Using VxDBA to Perform Administrative Operations Prerelease 8 September 2005, 8:55am Set Monitoring/Expansion Policy for All File Systems. Use this menu option to configure the monitoring and expansion policy for all file systems. You are prompted for the Warning Threshold for space usage, the Grow Threshold for space usage, and the Amount as a percentage or a value in megabytes by which to grow the file system.
Prerelease 8 September 2005, 8:55am Using VxDBA to Perform Administrative Operations This operation displays a screen similar to the following: VERITAS Storage Foundation for Oracle (ORACLE_SID 'PROD') Menu: Oracle Tablespace/Datafile Space Administration Database Status # File Systems # Tablespaces # Datafiles : : : : ONLINE 1 4 4 1 2 3 Display Oracle Tablespace/Datafile Space Usage Display Oracle Tablespace/Datafile Space Alarm Settings Enable/Disable/Modify Space Alarm Settings ? q x Display Hel
Using VxDBA to Perform Administrative Operations Prerelease 8 September 2005, 8:55am Display Oracle Tablespace/Datafile Space Usage displays a screen similar to the following: --------------------------------------------------------------VxDBA: Display OracleTablespace/Datafile Space Usage - PROD --------------------------------------------------------------ORACLE_SID ORACLE_HOME Database Status # File Systems # Tablespaces # Datafiles TABLESPACE TOT_MB ---------- -----SYSTEM 5033 TSTAB 52 TSIDX 1000 TST
Prerelease 8 September 2005, 8:55am Using VxDBA to Perform Administrative Operations Displaying Oracle Tablespace/Datafile Space Alarm Settings This operation displays the information about the space alarm settings defined for the Oracle tablespaces and datafiles. The space alarm relies on the VxDBA Monitoring Agent. The agent daemon processes must be running first. If the agent daemons are not running, a message is displayed asking you to start the agent daemons.
Using VxDBA to Perform Administrative Operations Prerelease 8 September 2005, 8:55am Once you start the VxDBA Monitoring agent, Display Oracle Tablespace/Datafile / Space Alarm Settings displays the list of tablespaces and datafiles and the space alarm status: ------------------------------------------------------------VxDBA: Display Oracle Tablespace/Datafile Space Alarm Settings ------------------------------------------------------------- ORACLE_SID ORACLE_HOME Database Status # File Systems # Tables
Prerelease 8 September 2005, 8:55am Using VxDBA to Perform Administrative Operations Enabling, Disabling, or Modifying Oracle Space Alarm Settings Enabling the Oracle space alarm allows VxDBA to monitor tablespace and datafile space usage. The warning is sent to the log file /var/log/dbed_mon/dbed_mon.logfile.$ORACLE_SID Note Only users with superuser (root) privileges can perform this operation.
Using VxDBA to Perform Administrative Operations Prerelease 8 September 2005, 8:55am After you enter the root password, Enable/Disable/Modify Space Alarm Settings displays a screen similar to the following: VERITAS Storage Foundation for Oracle (ORACLE_SID 'PROD') Menu: Enable/Disable/Modify Space Alarm Settings Database Status : # File Systems # Tablespaces # Datafiles 1 2 3 ORA-01034: insufficient privileges : (1) : (4) : (4) Enable or Disable Boot-Time Start of Monitoring Agent Set Monitoring/Expan
Prerelease 8 September 2005, 8:55am Using VxDBA to Perform Administrative Operations Set Monitoring Policy Per Oracle Tablespaces. Use this menu option to configure the monitoring policy for a particular Oracle tablespace. After displaying the current policy per Oracle tablespace, the program asks if you want to change the policies and then prompts you for the new values for the Warning Threshold. Note The expansion of Oracle Tablespaces is not currently supported.
Using VxDBA to Perform Administrative Operations Prerelease 8 September 2005, 8:55am When the configuration file is modified, restart the Monitoring Agent for the changes to take effect. This operation displays a screen similar to the following: ------------------------------------------------------------VxDBA: Configure Monitoring Agent Options - PROD ------------------------------------------------------------You will now be prompted to modify current VxDBA Monitoring Agent settings.
Prerelease 8 September 2005, 8:55am Using VxDBA to Perform Administrative Operations NOTICE: Default setting for DEF_GROW is 90. Do you want to change the setting for DEF_GROW [y,n,q,?] (default: n) NOTICE: Default setting for DEF_GROWBY is 0%. Do you want to change the setting for DEF_GROWBY [y,n,q,?] (default: n) n NOTICE: Default setting for DEF_ORA_WARN is 85. Do you want to change the setting for DEF_ORA_WARN [y,n,q,?] (default: n) n WARNING: No default setting for LOGPATH variable.
Using VxDBA to Perform Administrative Operations Prerelease 8 September 2005, 8:55am WARNING: No default setting for FSSTATSPATH variable. Do you want to change the setting for FSSTATSPATH [y,n,q,?] (default: n) n NOTICE: Default setting for ORASTATS is 0. Do you want to change the setting for ORASTATS [y,n,q,?] (default: n) Enter new setting for ORASTATS [current 0] : 1800 Changing variable ORASTATS from 0 to 1800 WARNING: No default setting for ORA_STATSPATH variable.
Prerelease 8 September 2005, 8:55am Using VxDBA to Perform Administrative Operations Configuring Statistics Collection Use the Configure Statistics Collection menu to collect file system and Oracle tablespace and datafile space usage statistics.
Using VxDBA to Perform Administrative Operations Prerelease 8 September 2005, 8:55am Graph and Print Statistics. Use this menu operation to display or print the collected statistics. If you try to print and the PRINTER environment variable is not set, you will have to supply a printer name. If you try to create a graph and the DISPLAY environment variable is not set, you will have to supply a machine display name. Graphing statistics depend on access to an X-windows system.
Prerelease 8 September 2005, 8:55am Using VxDBA to Perform Administrative Operations This operation displays a screen similar to the following: ------------------------------------------------------------VxDBA: Graph and Print Statistics - PROD ------------------------------------------------------------Log file containing file system statistics is available. Log file containing Oracle statistics is available.
Using VxDBA to Perform Administrative Operations Prerelease 8 September 2005, 8:55am Enter a display name for graph display [,q,?] abbey:0.0 DISPLAY set to abbey:0.0. Found a statistics file at /var/log/dbed_mon/dbed_mon.fs_stats.PROD Do you want to supply another file name? [,n,q,?] n Validating file format of /var/log/dbed_mon/dbed_mon.fs_stats.PROD Setting temp directory to /tmp/.stats Saving all output files for later use.
Prerelease 8 September 2005, 8:55am Using VxDBA to Perform Administrative Operations Starting and Stopping the Monitoring Agent Note Only users with superuser (root) privileges can perform this operation. The Start/Stop Monitoring Agent operation first checks to see if you are logged in as root.
Using VxDBA to Perform Administrative Operations Prerelease 8 September 2005, 8:55am Start Monitoring Agent. Use this menu option to start the monitoring activity of the VxDBA Monitoring Agent. Stop Monitoring Agent. Use this menu option to stop the monitoring activity of the VxDBA Monitoring Agent. Note VxDBA keeps a record of the Monitoring Agent process ID.
Prerelease 8 September 2005, 8:55am Chapter 13, Using the VxDBA Utility Using VxDBA to Perform Administrative Operations 397
Using VxDBA to Perform Administrative Operations 398 Prerelease 8 September 2005, 8:55am VERITAS Storage Foundation for Oracle Administrator’s Guide
Prerelease 8 September 2005, 8:55am Chapter 13, Using the VxDBA Utility Using VxDBA to Perform Administrative Operations 399
Using VxDBA to Perform Administrative Operations 400 Prerelease 8 September 2005, 8:55am VERITAS Storage Foundation for Oracle Administrator’s Guide
14 Tuning for Performance This chapter provides tuning tips that you can use to improve database performance.
Tuning VxVM Prerelease 8 September 2005, 8:55am Tuning VxVM VERITAS Volume Manager (VxVM) is tuned for most configurations ranging from small systems to larger servers. On smaller systems with less than a hundred drives, tuning should not be necessary and VERITAS Volume Manager should be capable of adopting reasonable defaults for all configuration parameters.
Prerelease 8 September 2005, 8:55am TYP vol vol vol vol vol NAME READ blop 0 foobarvol 0 rootvol 73017 swapvol 13197 testvol 0 Tuning VxVM WRITE 0 0 181735 20252 0 READ 0 0 718528 105569 0 WRITE 0 0 1114227 162009 0 READ 0.0 0.0 26.8 25.8 0.0 WRITE 0.0 0.0 27.9 397.0 0.
Tuning VxFS Prerelease 8 September 2005, 8:55am Tuning VxFS VERITAS File System provides a set of tuning options to optimize file system performance for different application workloads. VxFS provides a set of tunable I/O parameters that control some of its behavior. These I/O parameters help the file system adjust to striped or RAID-5 volumes that could yield performance far superior to a single disk.
Prerelease 8 September 2005, 8:55am ◆ Tuning VxFS More than 5 percent of the total file system size available as free extents that are 64 or more blocks in length A badly fragmented file system will have one or more of the following characteristics: ◆ More than 5 percent of free space in extents that are less than 8 blocks in length ◆ More than 50 percent of free space in extents that are less than 64 blocks in length ◆ Less than 5 percent of the total file system size available as free extents that
Tuning VxFS Prerelease 8 September 2005, 8:55am Tunable VxFS I/O Parameters read_pref_io The preferred read request size. The file system uses this parameter in conjunction with the read_nstream value to determine how much data to read ahead. The default value is 64K. 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.
Prerelease 8 September 2005, 8:55am initial_extent_ size Tuning VxFS 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.
Tuning VxFS Prerelease 8 September 2005, 8:55am max_seqio_extent_ Increases or decreases the maximum size of an extent. When the file size 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.
Prerelease 8 September 2005, 8:55am write_throttle Tuning VxFS 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. This behavior occurs because the file system is creating dirty pages (in-memory updates) faster than they can be asynchronously flushed to disk without slowing system performance.
Tuning VxFS Prerelease 8 September 2005, 8:55am 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.
Prerelease 8 September 2005, 8:55am Tuning VxFS 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. After clearing the statistics, let the database run for a while during a typical database workload period.
Tuning VxFS Prerelease 8 September 2005, 8:55am ◆ Average time spent on read and write operations The following is an example of odmstat output: # /opt/VRTS/bin/odmstat -i 5 /mnt/odmfile* OPERATIONS FILE BLOCKS AVG TIME(ms) FILE NAME READ WRITE READ WRITE READ Mon May 11 16:21:10 2015 /db/cust.dbf 0 /db/system.dbf 0 Mon May 11 16:21:15 2015 /db/cust.dbf 371 /db/system.dbf 0 0 371 371 Mon May 11 16:21:20 2015 /db/cust.dbf 813 /db/system.dbf 0 0 813 813 0 0 0 0 0 0 0 0.0 0.0 0.0 0.0 0 371 0.
Prerelease 8 September 2005, 8:55am Tuning Oracle Databases Tuning Oracle Databases To achieve optimal performance on your Oracle database, the database needs to be tuned to work with VxFS. This section describes some of the Oracle parameters that you can tune to improve your Oracle database performance when using Quick I/O. Sequential Table Scans Quick I/O performs all I/O as direct I/O.
Tuning Oracle Databases Prerelease 8 September 2005, 8:55am bypasses the file system cache to improve database performance. Memory pages normally allocated to the file system cache can be allocated to the database buffer cache (SGA). With Oracle9i, you can adjust the SGA size without shutting down the database. Setting Oracle Block Reads During Sequential Scans The DB_FILE_MULTIBLOCK_READ_COUNT parameter specifies the maximum number of blocks Oracle reads in one I/O operation during a sequential scan.
Prerelease 8 September 2005, 8:55am Tuning Oracle Databases Configuring Memory Allocation Never configure Oracle to make use of more memory than is physically available on the system. Oracle may have to compete with other processes for system memory resources, and all of these potential processes must be considered when sizing and allocating memory. In the ideal configuration, a system that is dedicated to Oracle simplifies the tuning and monitoring issues and ensures best performance.
Tuning HP-UX Prerelease 8 September 2005, 8:55am Tuning HP-UX To achieve optimal performance using Quick I/O, certain HP-UX parameters need to be tuned. Changing these parameters requires modifying the HP-UX kernel settings, rebuilding the kernel, and rebooting the system. See the HP-UX System Administration Tasks manual for the detailed procedure on how to reconfigure the HP-UX kernel.
Prerelease 8 September 2005, 8:55am Tuning HP-UX nproc This parameter sets the maximum number of processes. The nproc parameter may need to be set higher for a large database. See your HP-UX and Oracle documentation for the recommended value. maxuproc This parameter sets the maximum number of processes a non-root user can create in parallel. The maxuproc parameter may need to be set higher for a large database. See your HP-UX and Oracle documentation for the recommended value.
VERITAS Storage Foundation for Oracle Command Line Interface A VERITAS Storage Foundation for Oracle provides a command line interface (CLI) to many key operations also supplied from within the VxDBA utility menus and VERITAS Storage Foundation GUI application. The command line interface lets you incorporate command operations into scripts and other administrative processes. VERITAS Storage Foundation for Oracle also provides commands specific to the Database FlashSnap feature.
Prerelease 8 September 2005, 8:55am Overview of Commands Overview of Commands All VERITAS Storage Foundation for Oracle commands supported in the command line interface are located in the /opt/VRTS/bin directory. Exceptions are the Quick I/O commands, vxstorage_stats, and edgetmsg2, which are located in /opt/VRTSdbed/bin. Online manual pages are located in the /opt/VRTS/man directory.
Overview of Commands Prerelease 8 September 2005, 8:55am VERITAS Storage Foundation for Oracle Commands Command Description dbed_ckptdisplay Displays Storage Checkpoints for an Oracle database. Performs the same operation from the command line, as Storage Checkpoint Administration > Display Storage Checkpoints in the VxDBA utility menus. Performs the same operation from the command line, as Storage Checkpoint > Properties in the GUI. (Clicking on Storage Checkpoint alone lists all Storage Checkpoints.
Prerelease 8 September 2005, 8:55am Overview of Commands VERITAS Storage Foundation for Oracle Commands Command Description dbed_ckptrollback Rolls back an Oracle database to a Storage Checkpoint point-in-time image. Performs the same Storage Rollback operation from the command line, as the database Storage Rollback operation available in the VxDBA utility Storage Rollback Administration menu.
Overview of Commands Prerelease 8 September 2005, 8:55am VERITAS Storage Foundation for Oracle Commands Command Description dbed_vmchecksnap Creates a snapplan that the dbed_vmsnap command uses to create a volume snapshot of an Oracle database. The snapplan specifies snapshot scenarios (such as online or offline; database, tablespaces, or tables, and so forth). This option is not available through the VxDBA utility menu or the GUI at this time.
Prerelease 8 September 2005, 8:55am Overview of Commands VERITAS Storage Foundation for Oracle Commands Command Description vxstorage_stats Displays storage object I/O statistics. This option is not available through the VxDBA utility menu. Performs the same operation from the command line, as the options within Datafiles > Topology Statistics... in the GUI.
Examples of Using the Command Line Interface Prerelease 8 September 2005, 8:55am Examples of Using the Command Line Interface This section provides examples for using the VERITAS Storage Foundation for Oracle command line interface to perform administrative operations. For more detailed information about the commands and their syntax and available options, see the individual manual pages.
Prerelease 8 September 2005, 8:55am Examples of Using the Command Line Interface Checking Oracle Configuration Environment Using dbed_checkconfig You can use the VERITAS Storage Foundation for Oracle dbed_checkconfig command to verify and report on an Oracle environment from the command line. Prerequisites ◆ You must be logged on as the database administrator (typically, the user ID oracle).
Examples of Using the Command Line Interface Prerelease 8 September 2005, 8:55am Filesystem i/o parameters for /prod_db 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 = 0 write_throttle = 0 max_diskq = 1048576 initial_extent_size = 8 max_seqio_extent_size = 2048 max_buf_data_size = 8192 h
Prerelease 8 September 2005, 8:55am Examples of Using the Command Line Interface Examining Oracle automatic extension of datafiles. Total of 0 datafiles are configured to auto extend. 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.
Examples of Using the Command Line Interface Prerelease 8 September 2005, 8:55am 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 = 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 in
Prerelease 8 September 2005, 8:55am Examples of Using the Command Line Interface Total of 0 datafiles are configured to auto extend. The following datafiles are not configured to autoextend: /prod_db/deflt.dbf /prod_db/temp.dbf /prod_db/index02.dbf /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.
Examples of Using the Command Line Interface Prerelease 8 September 2005, 8:55am Saving the Oracle Configuration Environment Using dbed_saveconfig You can use the VERITAS Storage Foundation for Oracle dbed_saveconfig command to save configuration information on Oracle, VERITAS products, and system hardware from the command line. Prerequisites ◆ You must be logged on as the database administrator (typically, the user ID oracle).
Prerelease 8 September 2005, 8:55am Examples of Using the Command Line Interface Creating Storage Checkpoints Using dbed_ckptcreate You can use the VERITAS Storage Foundation for Oracle dbed_ckptcreate command to create a Storage Checkpoint from the command line. Storage Checkpoints can be either online, offline, or instant. By default, Storage Checkpoints are offline. If online is specified, the database is put into hot-backup mode when the Storage Checkpoint is created.
Examples of Using the Command Line Interface ▼ Prerelease 8 September 2005, 8:55am To create Storage Checkpoints while the database is offline 1. Use the dbed_ckptcreate command as follows: $ /opt/VRTS/bin/dbed_ckptcreate -S PROD \ -H /oracle/product/9i -o offline Creating offline Storage Checkpoint of database PROD. Storage Checkpoint Checkpoint_971672044 created. Note The default option is online.
Prerelease 8 September 2005, 8:55am Examples of Using the Command Line Interface Displaying Storage Checkpoints Using dbed_ckptdisplay You can use the VERITAS Storage Foundation for Oracle 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. Prerequisites ◆ You may be logged in as either the database administrator or root.
Examples of Using the Command Line Interface ▼ Prerelease 8 September 2005, 8:55am To display other Storage Checkpoints without updating the VxDBA repository Use the dbed_ckptdisplay command as follows: $ /opt/VRTS/bin/dbed_ckptdisplay -H /oracle/product/9i -o other NetBackup_incr_PROD_955133480 NetBackup_full_PROD_955132952 ▼ -S PROD \ -n NBU /db01 NBU /db01 To display all Storage Checkpoints Use the dbed_ckptdisplay command as follows: $ /opt/VRTS/bin/dbed_ckptdisplay -H /oracle/product/9i -o all Che
Prerelease 8 September 2005, 8:55am Examples of Using the Command Line Interface Scheduling Storage Checkpoints Using dbed_ckptcreate and cron You can use the VERITAS Storage Foundation for Oracle dbed_ckptcreate command to schedule Storage Checkpoint creation in a cron job or other administrative script. Prerequisites ◆ You must be logged on as the database administrator (typically, the user ID oracle).
Examples of Using the Command Line Interface Prerelease 8 September 2005, 8:55am Scheduling Storage Checkpoint Creation in a cron Job ◆ To create a Storage Checkpoint twice a day, at 5:00 a.m. and 7:00 p.m., every Monday through Friday, include the following entry in your crontab file: 0 5,19 * * 1-5 /opt/VRTS/bin/dbed_ckptcreate -S PROD \ -H /oracle/product/9i -o instant ◆ To create a Storage Checkpoint at 11:30 p.m.
Prerelease 8 September 2005, 8:55am Examples of Using the Command Line Interface Mounting Storage Checkpoints Using dbed_ckptmount You can use the VERITAS Storage Foundation for Oracle dbed_ckptmount command to mount a Storage Checkpoint for an Oracle database from the command line. Prerequisites ◆ You may be logged in as either the database administrator or root. Usage Notes ▼ ◆ The dbed_ckptmount command is used to mount a Storage Checkpoint into the file system namespace.
Examples of Using the Command Line Interface Prerelease 8 September 2005, 8:55am Unmounting Storage Checkpoints Using dbed_ckptumount You can use the VERITAS Storage Foundation for Oracle dbed_ckptumount command to unmount a Storage Checkpoint for an Oracle database from the command line. Prerequisites ◆ You may be logged in as either the database administrator or root. Usage Notes ▼ ◆ The dbed_ckptumount command is used to unmount a mounted Storage Checkpoint from the file system namespace.
Prerelease 8 September 2005, 8:55am Examples of Using the Command Line Interface Creating and Working with Storage Checkpoint Allocation Policies Using dbed_ckptpolicy You can use the VERITAS Storage Foundation for Oracle dbed_ckptpolicy command to create and administer Storage Checkpoint allocation policies for Multi-Volume File Systems (MVSs). Storage Checkpoint allocation policies specify a list of volumes and the order in which to allocate data to them.
Examples of Using the Command Line Interface ◆ Prerelease 8 September 2005, 8:55am Volume set mvsvset2 contains volumes mvsv4 and mvsv5.
Prerelease 8 September 2005, 8:55am ▼ Examples of Using 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 File System: /mvsfs/v
Examples of Using the Command Line Interface Prerelease 8 September 2005, 8:55am Administering Storage Checkpoint Quotas dbed_ckptquota You can use the VERITAS Storage Foundation for Oracle dbed_ckptquota command to administer file system quotas for Storage Checkpoint for an Oracle database from the command line. Prerequisites ◆ You must be logged on as the database administrator (typically, the user ID oracle).
Prerelease 8 September 2005, 8:55am /ora/testvol04 /ora/testvol05 Examples of Using the Command Line Interface 25000 50000 20000 40000 128 128 Note CurrentUse displays the number of filesystem blocks currently used by all Storage Checkpoints in the filesystem. If there are no Storage Checkpoints, or if quotas have been disabled, CurrentUse will display 0.
Examples of Using the Command Line Interface Prerelease 8 September 2005, 8:55am Performing Storage Rollback Using dbed_ckptrollback You can use the VERITAS Storage Foundation for Oracle dbed_ckptrollback command to rollback an Oracle database to a Storage Checkpoint. Prerequisites ◆ You may be logged in as either the database administrator or root. Usage Notes ◆ The dbed_ckptrollback rolls an Oracle database back to a specified Storage Checkpoint.
Prerelease 8 September 2005, 8:55am ▼ Examples of Using 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 Note 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.
Examples of Using the Command Line Interface Prerelease 8 September 2005, 8:55am Removing Storage Checkpoints Using dbed_ckptremove You can use the VERITAS Storage Foundation for Oracle dbed_ckptremove command to remove a Storage Checkpoint for an Oracle database at the command line. Prerequisites ◆ You may be logged in as either the database administrator or root.
Prerelease 8 September 2005, 8:55am Examples of Using the Command Line Interface Managing Capacity Planning Utility Using dbed_ckptplan You can use the VERITAS Storage Foundation for Oracle dbed_ckptplan command to manage the Storage Checkpoint Capacity Planning Utility at the command line. Usage Notes ▼ ◆ The dbed_ckptplan command is used to obtain estimates on space usage for Storage Checkpoints.
Examples of Using the Command Line Interface Prerelease 8 September 2005, 8:55am Cloning the Oracle Instance Using dbed_clonedb You can use the VERITAS Storage Foundation for Oracle dbed_clonedb command to clone an Oracle instance using a Storage Checkpoint. Cloning an existing database using a Storage Checkpoint must be done on the same host.
Prerelease 8 September 2005, 8:55am Examples of Using the Command Line Interface Options ▼ -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. The default mode is non-interactive.
Examples of Using the Command Line Interface Prerelease 8 September 2005, 8:55am in /local/oracle9/1/testvol Altering db_name in initNEW9.ora Altering control file locations in initNEW9.
Prerelease 8 September 2005, 8:55am Examples of Using the Command Line Interface /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.ora in /local/oracle9/1/testvol Altering db_name in initNEW9.ora Altering control file locations in initNEW9.
Examples of Using the Command Line Interface Prerelease 8 September 2005, 8:55am Creating and Working with Snapplans Using dbed_vmchecksnap A snapplan specifies snapshot scenarios for an Oracle database (such as online, instant, or offline). You can name a snapplan file whatever you choose. You can use the dbed_vmchecksnap -o setdefaults option to create the snapplan and set default values for the parameters. You may then modify the snapplan file using a text editor.
Prerelease 8 September 2005, 8:55am Examples of Using the Command Line Interface Parameter Value ARCHIVELOG_DEST Specifies the full path of the archive logs. There are several archive log destinations that can be used for database recovery if you are multiplexing the archive logs. You must specify which archive log destination to use. It is recommended that you have the archive log destination on a separate volume if SNAPSHOT_ARCHIVE_LOG is yes.
Examples of Using the Command Line Interface Prerelease 8 September 2005, 8:55am Parameter Value SNAPSHOT_VOL_PREFIX Specifies the snapshot volume prefix. Use this variable to specify a prefix for the snapshot volumes split from the primary disk group. A volume name cannot be more than 32 characters. 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.
Prerelease 8 September 2005, 8:55am Examples of Using the Command Line Interface ◆ See the dbed_vmchecksnap(1M) online manual page for more information. ◆ If the SNAPSHOT_MODE for the database is set to online, the primary and secondary hosts can be the same. If the SNAPSHOT_MODE is set to offline or instant, the primary and secondary hosts must be different. Options ▼ -S Specifies the ORACLE_SID, which is the name of the Oracle database, for which a snapshot image will be created.
Examples of Using the Command Line Interface Prerelease 8 September 2005, 8:55am PRIMARY_HOST=host1 SECONDARY_HOST=host1 PRIMARY_DG=PRODdg SNAPSHOT_DG=SNAP_PRODdg ORACLE_SID=PROD 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 ▼ To create a snapplan and set the default values in a two-host configuration Use the dbed_vmchecksnap command as follows: $ /opt/
Prerelease 8 September 2005, 8:55am ▼ Examples of Using the Command Line Interface To validate a snapplan for a snapshot image to be used on the primary host 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.
Examples of Using the Command Line Interface Prerelease 8 September 2005, 8:55am The version of PRIMARY_DG-PRODdg is 110. SNAPSHOT_DG is SNAP_PRODdg SNAPSHOT_MODE is online The database is running in archivelog mode. ARCHIVELOG_DEST is /mytest/arch SNAPSHOT_PLAN_FOR is database SNAPSHOT_ARCHIVE_LOG is yes ARCHIVELOG_DEST=/mytest/arch is mount on /dev/vx/dsk/PRODdg/arch. Examining Oracle volume and disk layout for snapshot. Volume prod_db on PRODdg is ready for snapshot.
Prerelease 8 September 2005, 8:55am Examples of Using the Command Line Interface Note The command output displays all available snapplans, their snapshot status (SNAP_STATUS), database status (DB_STATUS), and whether a snapshot may be taken (SNAP_READY). For explanations of the various statuses that may appear for SNAP_STATUS and DB_STATUS, refer to “VERITAS Database FlashSnap Status Information” on page 501.
Examples of Using the Command Line Interface ▼ Prerelease 8 September 2005, 8:55am To remove a snapplan Use the dbed_vmchecksnap command as follows: $ /opt/VRTS/bin/dbed_vmchecksnap -S PROD -f snap1 -o remove The snapplan snap1 has been removed from VxDBA repository.
Prerelease 8 September 2005, 8:55am Examples of Using the Command Line Interface Creating, Resynchronizing, or Reverse Resynchronizing a Snapshot Database Using dbed_vmsnap You can use the VERITAS Storage Foundation for Oracle dbed_vmsnap command to create a snapshot image of an Oracle database. The snapshot can be used locally or on another host that is physically attached to the shared storage. You can also resynchronize the snapshot image back to the primary database.
Examples of Using the Command Line Interface ▼ Prerelease 8 September 2005, 8:55am -o reverse_resync_commit Commits the reverse resynchronization changes after you have verified that they are acceptable. -o reverse_resync_abort Aborts reverse resynchronization and mounts the original volumes back with the file systems that are configured to use the volume.
Prerelease 8 September 2005, 8:55am Examples of Using the Command Line Interface Use the dbed_vmsnap command 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. dbed_vmsnap ended at 2004-04-02 15:54:29 ▼ To abort resynchronizing your database to a snapshot This option is only allowed when reverse_resync_begin has been run. It is not allowed if reverse_resync_commit has been executed.
Examples of Using the Command Line Interface Prerelease 8 September 2005, 8:55am Creating or Shutting Down a Clone Database Using dbed_vmclonedb You can use the VERITAS Storage Foundation for Oracle dbed_vmclonedb command to create or shutdown a clone database on either the primary or secondary host using snapshot volumes from the primary host. Prerequisites ◆ You must be logged in as the Oracle database administrator to use dbed_vmclonedb command.
Prerelease 8 September 2005, 8:55am Examples of Using the Command Line Interface Options -S ORACLE_SID Specifies the ORACLE_SID, which is the name of the Oracle database, for which a snapshot image will be created. -g snap_dg Specifies the name of the disk group that contains all snapshot volumes. -o mount Mounts the file systems so you can use them to do a backup. -o mountdb Starts the database to allow manual database recovery. -o recoverdb Automatically recovers the database.
Examples of Using the Command Line Interface -r relocate_path Prerelease 8 September 2005, 8:55am Specifies the initial mount point for the snapshot image. If you are creating a clone in a single-host configuration, -r is required. Otherwise, it is an optional argument. If -r relocate_path is used when cloning a database, it will also be required for running -o update_status and -o umount. Note Do not use -r relocate_path if the SNAPSHOT_MODE parameter is set to instant or offline.
Prerelease 8 September 2005, 8:55am ▼ Examples of Using the Command Line Interface To clone a database manually In a single-host configuration: To mount file systems and create a clone of the primary database on the same host as the primary database without recovering the clone database, use the dbed_vmclonedb command as follows.
Examples of Using the Command Line Interface Prerelease 8 September 2005, 8:55am Database NEWPROD (SID=NEWPROD) is in recovery mode. If the database NEWPROD is recovered manually, you must run dbed_vmclonedb -o update_status to change the snapshot status. dbed_vmclonedb ended at 2004-04-02 15:34:59 Recover the database manually.
Prerelease 8 September 2005, 8:55am Examples of Using the Command Line Interface To start the clone database on the same host as the primary database, use the dbed_vmclonedb command as follows: $ /opt/VRTS/bin/dbed_vmclonedb -S PROD -g SNAP_PRODdg \ -o restartdb,new_sid=NEWPROD -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. Mounting /clone/prod_ar on /dev/vx/dsk/SNAP_PRODdg/SNAP_prod_ar.
Examples of Using the Command Line Interface Prerelease 8 September 2005, 8:55am Creating or Validating the Snapplan Using dbed_vmchecksnap You can use the VERITAS Storage Foundation for Oracle dbed_vmchecksnap command to create or validate a snapplan from the command line. You can also use the command to check the storage to make sure it is configured appropriately for the Database FlashSnap feature. Note You must have the VERITAS Database FlashSnap license installed in order to use this command.
Prerelease 8 September 2005, 8:55am Examples of Using the Command Line Interface Options ▼ -S Specifies the ORACLE_SID, which is the name of the Oracle database, for which a snapshot image will be created. -H Specifies the Oracle home directory that corresponds to the ORACLE_SID. -f snapplan Indicates the name of the snapplan that you are creating. -o setdefaults Creates a default snapplan. This option can be used with the -o validate option to validate that the configuration is correct.
Examples of Using the Command Line Interface Prerelease 8 September 2005, 8:55am SNAPSHOT_VOL_PREFIX=SNAP_ ▼ To validate a snapplan Use the dbed_vmchecksnap command as follows: $ dbed_vmchecksnap -S PROD -H /oracle/product/8.1.6 -o validate \ -f snapplan Examining the validation of parameter setting in snapplan for the database instance PROD. PRIMARY_HOST is host1 SECONDARY_HOST is host2 The version of PRODdg is 90. SNAPSHOT_DG is SNAP_PRODdg. Examining Oracle volume and disk layout for snapshot.
Prerelease 8 September 2005, 8:55am Examples of Using the Command Line Interface SNAP_PRODdg for snapshot will include: PRODdg04 PRODdg05 Appendix A, VERITAS Storage Foundation for Oracle Command Line Interface 473
Examples of Using the Command Line Interface Prerelease 8 September 2005, 8:55am Creating or Resynchronizing a Snapshot Using dbed_vmsnap You can use the VERITAS Storage Foundation for Oracle dbed_vmsnap command to create a snapshot image of an Oracle database, tablespaces, or tables. The snapshot can be used locally or on another host that is physically attached to the shared storage. You can also resynchronize the snapshot image back to the original database.
Prerelease 8 September 2005, 8:55am Examples of Using the Command Line Interface If -r is used in dbed_vmclonedb, make sure is created and owned by Oracle DBA. Otherwise, the following mount points need to be created and owned by Oracle DBA: /prod_db. /prod_ar.
Examples of Using the Command Line Interface Prerelease 8 September 2005, 8:55am Creating or Shutting Down a Clone Database Using dbed_vmclonedb You can use the VERITAS Storage Foundation for Oracle dbed_vmclonedb command to create or shutdown a clone database on either the primary or secondary host using snapshot volumes from the primary host.
Prerelease 8 September 2005, 8:55am -o new_sid= Examples of Using the Command Line Interface Specifies the new ORACLE_SID for the snapshot image. This is a required argument. -o vxdbavol= Specifies the VxDBA repository volume name. This is an optional argument, unless you are creating the clone on a secondary host. -r Indicates the initial mount point for the snapshot image. This is an optional argument.
Examples of Using the Command Line Interface ▼ Prerelease 8 September 2005, 8:55am To create and recover a clone database on a secondary host Use the dbed_vmclonedb command as follows: $ dbed_vmclonedb -S PROD -g SNAP_PRODdg -o \ recoverdb,new_sid=NEWPROD,vxdbavol=SNAP_vxdba01 dbed_vmclonedb started at 2002-03-11 12:36:46 Mounting /prod_db on /dev/vx/dsk/SNAP_PRODdg/SNAP_ORACLE1. Mounting /prod_ar on /dev/vx/dsk/SNAP_PRODdg/SNAP_prod_ar.
Prerelease 8 September 2005, 8:55am ▼ Examples of Using the Command Line Interface To shutdown and unmount a clone database on the same host Use the dbed_vmclonedb command as follows: $ dbed_vmclonedb -o umount,new_sid=NEW_815 -r /snapdb dbed_vmclonedb started at 2002-03-11 12:49:09 Oracle instance successfully shut down. Umounting /snapdb/share/oradata1_815. Umounting /snapdb/share/oradata2_815. Umounting /snapdb/share/oradata3_815. Umounting /snapdb/share/archivelog_815.
Examples of Using the Command Line Interface Prerelease 8 September 2005, 8:55am Removing dbed_vmsnap or dbed_vmclonedb Changes (if a failure occurs) Using dbed_vmsnapundo If the dbed_vmsnap or dbed_vmclonedb command fails during an operation, you can use dbed_vmsnapundo to restore the system to the SNAPREADY state. If dbed_vmsnap failed, dbed_vmsnapundo imports the disk group and tries to snapback the data volumes. If dbed_vmclonedb failed, dbed_vmsnapundo will deport the disk group again.
Prerelease 8 September 2005, 8:55am ▼ Examples of Using the Command Line Interface -l snaplog Specifies the snaplog file name. -o new_sid Indicates the ORACLE_SID used for the snapshot image. Use this option if the dbed_vmclonedb command failed.
Examples of Using the Command Line Interface Prerelease 8 September 2005, 8:55am Using Snapplans A snapplan specifies snapshot scenarios for an Oracle database (such as online or offline, and so forth). The user specifies the name of the snapplan. You can use the dbed_vmchecksnap -o setdefaults option to create the snapplan and set the default values of the parameters.
Prerelease 8 September 2005, 8:55am Examples of Using the Command Line Interface Parameter Value SNAPSHOT_ARCHIVE_LOG yes or no Specifies whether to create a snapshot of the archive log volumes. Specify yes to split the archive log volume mirrors and deport them to the secondary host. When using the Oracle remote archive log destination feature to send the archive logs to the secondary host, you can specify no to save some space.
Examples of Using the Command Line Interface Prerelease 8 September 2005, 8:55am 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. Prerequisites ◆ You must be logged in as the Database Administrator or root to use this command.
Prerelease 8 September 2005, 8:55am ▼ Examples of Using the Command Line Interface To print a message Use the edgetmsg2 command as follows: $ /opt/VRTSdbed/bin/edgetmsg2 [-s set_num] [-M msgid[:severity]] \ [-f msg_catalog] [-v severity] [-p] [-m value] \ [“default format string” [args]] ▼ To read a message log file Use the edgetmsg2 command as follows: $ /opt/VRTSdbed/bin/edgetmsg2 -o list[,suppress_time] \ -S ORACLE_SID | [-f logfile] \ [-v severity] [-t from_time,to_time] Output similar to the follo
Examples of Using the Command Line Interface Prerelease 8 September 2005, 8:55am Prerequisites ◆ You may be logged in as either the database administrator or root. Usage Notes ◆ The -m option displays the I/O topology for the specified file. ◆ The -s option displays the file statistics for the specified file. ◆ The -c count option specifies the number of times to display statistics. ◆ The -i interval option specifies the interval frequency for displaying updated I/O statistics.
Prerelease 8 September 2005, 8:55am Examples of Using the Command Line Interface Note For file type (fi), the SIZE column is number of bytes, and for volume (v), plex (pl), sub-disk (sd), and physical disk (da), the SIZE column is in 512-byte blocks. Stripe sizes are given in sectors. ▼ To display the entire I/O mapping and statistics for each I/O stack Use the vxstorage_stats command with the -m and -s options as follows: $ /opt/VRTS/bin/vxstorage_stats -m -s -f /data/system01.
Examples of Using the Command Line Interface Prerelease 8 September 2005, 8:55am 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. In addition, dbed_analyzer provides information about the percentage of disk space being used by a tablespace. Because the dbed_analyzer command output can be long, it is written to a file for easier viewing.
Prerelease 8 September 2005, 8:55am QTY_IDX ITM_IDX ROLL_1 QTY_IDX ROLL_2 ITEM ▼ Examples of Using the Command Line Interface /usr1/oracle/rw/DATA/qty_idx_7001 /usr1/oracle/rw/DATA/itm_idx_2001 /usr1/oracle/rw/DATA/roll_1_5001 /usr1/oracle/rw/DATA/qty_idx_7002 /usr1/oracle/rw/DATA/roll_2_6001 /usr1/oracle/rw/DATA/item_1001 c3t21000020379DBD5Fd0 c3t21000020379DBD5Fd0 c3t21000020379DBD5Fd0 c3t21000020379DBD5Fd0 c3t21000020379DBD5Fd0 c3t21000020379DBD5Fd0 1024016 1024016 1024016 1024016 1024016 4096016 T
Examples of Using the Command Line Interface Prerelease 8 September 2005, 8:55am Identifying VxFS Files to Convert to Quick I/O Using qio_getdbfiles You can use the qio_getdbfiles command to identify VxFS files before converting them to Quick I/O files. Only VxFS files may be converted to Quick I/O. The qio_getdbfiles command queries the database and gathers a list of datafiles to be converted to Quick I/O. The command requires direct access to the database.
Prerelease 8 September 2005, 8:55am Examples of Using the Command Line Interface The qio_convertdbfiles command converts regular files or symbolic links that point to regular files on VxFS file systems to Quick I/O. The qio_convertdbfiles command converts only those files listed in the mkqio.dat file to Quick I/O. The mkqio.dat file is created by running qio_getdbfiles. It can also be created manually. Prerequisites ◆ To use this command for Oracle, the ORACLE_SID environment variable must be set.
Examples of Using the Command Line Interface ▼ Prerelease 8 September 2005, 8:55am To convert VxFS files to Quick I/O files 1. After running the qio_getdbfiles command, shut down the database: Caution 2. Running qio_convertdbfiles with any option except -f while the database is up and running can cause severe problems for your database, including data loss and corruption. Make sure the database is shut down before running the qio_convertdbfiles command.
Prerelease 8 September 2005, 8:55am Examples of Using the Command Line Interface $ ls -alL d* .d* -rw-r--r-- 1 oracle dba 104857600 May 2 13:42 .dbfile crw-r--r-- 1 oracle dba 45,1 May 3 12:18 dbfile $ ls -al d* .d* -rw-r--r-- 1 oracle dba 104857600 May 2 14:42 .dbfile lrwxrwxrwx 1 oracle dba 19 May 3 12:18 dbfile -> .dbfile::cdev:vxfs: The qio_convertdbfiles command renames the file dbfile to .dbfile and creates a symbolic link to .dbfile with the Quick I/O extension.
Examples of Using the Command Line Interface ◆ ◆ ▼ Prerelease 8 September 2005, 8:55am The qio_recreate command follows these rules in recreating Quick I/O files when a database is recovered: ◆ If a Quick I/O file (.file::cdev:vxfs:) is missing, then qio_recreate recreates it. ◆ If both a symbolic link (file) and its associated Quick I/O file (.file::cdev:vxfs:) are missing, qio_recreate recreates both the symbolic link and the Quick I/O file.
Prerelease 8 September 2005, 8:55am Examples of Using the Command Line Interface Appendix A, VERITAS Storage Foundation for Oracle Command Line Interface 495
B Using Third-Party Software to Back Up Files Using third-party software to back up VERITAS Quick I/O files or Oracle Disk Manager files requires special consideration and handling. This appendix discusses these issues. For information about backing up files using VERITAS NetBackup, refer to “Using VERITAS NetBackup for Database Backup” on page 260.
Prerelease 8 September 2005, 8:55am Using Oracle RMAN to Back Up and Restore Quick I/O Files Using Oracle RMAN to Back Up and Restore Quick I/O Files Quick I/O files are treated as raw devices by Oracle and Recovery Manager (RMAN) and must be backed up and restored the same way as raw devices. A Quick I/O file consists of two components: a regular file with space allocated to it and a link pointing to the Quick I/O interface for the file.
Using Oracle RMAN to Back Up and Restore Oracle Disk Manager Files Prerelease 8 September 2005, 8:55am Using Oracle RMAN to Back Up and Restore Oracle Disk Manager Files Oracle allocates Oracle Disk Manager files with contiguous extent layouts for good database performance. When you restore database files they are allocated using these extent attributes. If you are using Oracle RMAN's conventional backup method with any backup software, datafiles are also restored with the proper extent layouts.
Prerelease 8 September 2005, 8:55am Using Legato NetWorker to Back Up and Restore Quick I/O Files Using Legato NetWorker to Back Up and Restore Quick I/O Files When Quick I/O files are created using the command qiomkfile, a hidden file with storage space allocated to it and a link are created. The link points to the Quick I/O interface of the hidden file. Using qiomkfile ensures that the space for the file is allocated in a contiguous manner, which typically improves performance.
Using Backup Software Other than VERITAS NetBackup to Back Up and Restore ODM Files Prerelease 8 September Using Backup Software Other than VERITAS NetBackup to Back Up and Restore ODM Files If you are using backup software other than VERITAS NetBackup, ensure that it can back up and restore VxFS extent attributes. This is important because restored Oracle Disk Manager (ODM) files rely on proper extent layouts for best performance.
VERITAS Database FlashSnap Status Information C 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. For more information about Database FlashSnap command line functionality, see “VERITAS Storage Foundation for Oracle Command Line Interface” on page 418.
Obtaining Database FlashSnap Snapshot Status and Database Status Using the CLI Prerelease 8 September 2005, 8:55am Obtaining Database FlashSnap Snapshot Status and Database Status Using the CLI You can obtain both the snapshot status and the database status from the command line using thedbed_vmchecksnap command with the -o list option. The snapshot status and database status information may also appear in error messages.
Prerelease 8 September 2005, 8:55am SNAP_STATUS snapshot_end Obtaining Database FlashSnap Snapshot Status and Database Status Using the CLI Completed Operations ◆ ◆ dbed_vmsnap -o snapshot (successful) dbed_vmsnap -o reverse_resync_abort (successful) Allowed Operations ◆ dbed_vmsnap -o resync ◆ dbed_vmsnap -o reverse_resync_begin ◆ dbed_vmclonedb -o mount|mountdb|recoverdb Contact your system administrator for help.
Obtaining Database FlashSnap Snapshot Status and Database Status Using the CLI SNAP_STATUS Completed Operations Prerelease 8 September 2005, 8:55am Allowed Operations Recover the snapshot database manually, then run dbed_vmclonedb -o update_status mountdb_start ◆ dbed_vmclonedb -o mountdb (failed) ◆ mountdb_end ◆ dbed_vmclonedb -o mountdb (successful) ◆ dbed_vmclonedb -o update_status ◆ dbed_vmclonedb -o umount recoverdb_start ◆ dbed_vmclonedb -o recoverdb (failed) ◆ Recover the snapshot
Prerelease 8 September 2005, 8:55am Obtaining Database FlashSnap Snapshot Status and Database Status Using the CLI Database Status Details To view snapshot status information from the command line, use thedbed_vmchecksnap command with the -o list option to list all available snapplans for a specified database. Database status information is displayed in the command output under the column heading DB_STATUS.
Obtaining Database FlashSnap Snapshot Status and Database Status from the GUI Prerelease 8 September 2005, 8:55am Obtaining Database FlashSnap Snapshot Status and Database Status from the GUI You can obtain both the snapshot status and the snapshot database status from the GUI. The tables in this section provide detailed information regarding the various status values.
Prerelease 8 September 2005, 8:55am Obtaining Database FlashSnap Snapshot Status and Database Status from the GUI Snapshot Status (as seen in the Snapplan State field) Completed Operations resync_start ◆ reverse_resync_begin_start ◆ reverse_resync_begin_end ◆ Resync Snapshot (failed) Reverse Resync Snapshot with the begin option (failed) Reverse Resync Snapshot with the begin option (successful) Allowed Operations ◆ ◆ ◆ ◆ reverse_resync_abort_start ◆ reverse_resync_abort_end ◆ Reverse R
Obtaining Database FlashSnap Snapshot Status and Database Status from the GUI Snapshot Status (as seen in the Snapplan State field) Completed Operations mountdb_end ◆ dbed_vmclonedb -o mountdb command from the CLI was successful Prerelease 8 September 2005, 8:55am Allowed Operations ◆ ◆ Umount Database FlashSnap dbed_vmclonedb -o update_status command from the CLI Note This option is not supported in the GUI. Note This option is not supported in the GUI.
Prerelease 8 September 2005, 8:55am Obtaining Database FlashSnap Snapshot Status and Database Status from the GUI Snapshot Database Status Details To view snapshot database status information from the GUI, click on a specific snapplan in the object tree. The database status can be seen on the right side of the window in the Database Status field.
Accessibility and VERITAS Storage Foundation for Oracle D VERITAS products meet federal accessibility requirements for software as defined in Section 508 of the Rehabilitation Act: http://www.access-board.gov/508.htm VERITAS Storage Foundation for Oracle Graphical User Interface (GUI) inherits the font size and color settings from the operating system it is running on. Keyboard shortcuts are available for all major GUI operations and menu items.
Prerelease 8 September 2005, 8:55am Keyboard Navigation and Shortcuts in VERITAS Storage Foundation for Oracle Keyboard Navigation and Shortcuts in VERITAS Storage Foundation for Oracle All program functions and menu items are accessible using the keyboard exclusively. VERITAS Storage Foundation for Oracle uses standard operating system navigation keys and keyboard shortcuts.
Keyboard Navigation and Shortcuts in VERITAS Storage Foundation for Oracle Prerelease 8 September 2005, 8:55am VEA Additions to Microsoft Keyboard Conventions Convention Mnemonic Accelerator Number of Items in History N ALT+ N Rescan R None Set to defaults S ALT+ S Remember Password R ALT+ R Password P ALT+P Username U ALT+ U VEA Help Additions to Microsoft Keyboard Conventions 512 Convention Mnemonic Accelerator Find in Topic..
Prerelease 8 September 2005, 8:55am Keyboard Navigation and Shortcuts in VERITAS Storage Foundation for Oracle General Keyboard Navigation Within the GUI You can navigate and use VERITAS Storage Foundation for Oracle with only the keyboard. In the GUI, the current active tree or table has a dark blue highlight, and the current active tab, radio button, or checkbox is enclosed within a rectangle formed by dotted lines. These areas are said to have focus and will respond to commands.
Keyboard Navigation and Shortcuts in VERITAS Storage Foundation for Oracle Prerelease 8 September 2005, 8:55am Tabbed Dialog Boxes Some dialog boxes use tabbed pages to subcategorize groups of many options. Each tabbed page contains different groups of controls. Use Tab to move the focus between tabs within a dialog box. Typing the mnemonic for a tab also moves the focus to the tab and displays its page of controls.
Prerelease 8 September 2005, 8:55am Keyboard Shortcuts Keyboard Shortcuts All menu items can be selected by using accelerator or mnemonic keyboard shortcuts. An accelerator is a key combination that provides shortcut access to a GUI function. A mnemonic (sometimes referred to as a “hot key”) is a single-key equivalent (used in combination with the ALT key) for selecting GUI components such as menu items. The mnemonic “hot key” letter is underlined in the GUI.
Keyboard Shortcuts Prerelease 8 September 2005, 8:55am Keyboard Navigation The following table lists some of the keys frequently used to navigate with the keyboard: Keyboard Navigation Keyboard Input Result TAB Move forward between panes in the active Console window. SHIFT+TAB Move backwards between panes in the active Console window. SHIFT+ Move up one item in the tree view. UP ARROW 516 SHIFT+DOWN ARROW Move down one item in the tree view.
Prerelease 8 September 2005, 8:55am Menu Hot Keys Menu Hot Keys The following table lists the hot keys associated with the different menus: Menu Hot Keys Action Keyboard Input File ALT+F to open the menu, then: Tools ◆ C– Display the connection dialog window ◆ D-Display the disconnection dialog window ◆ r–Display the properties of the connected host ◆ u–Page setup for print ◆ w–Print preview ◆ P–Print the page ◆ x –Exit ALT+T to open the menu, then: ◆ P–Set the display preferences ◆
Menu Hot Keys Prerelease 8 September 2005, 8:55am Menu Hot Keys Action Keyboard Input Oracle Databases ALT+ O to open the menu, then: Oracle Database Monitoring Agent Snapplans 518 ◆ S– Start up the database ◆ D– Shut down the database ◆ C–Storage Checkpoint capacity planning ◆ C–Create capacity planning schedule ◆ R–Report Capacity Planning space usage ◆ p–Duplicate Database ◆ o–Resync Repository ◆ h– Check System configuration ◆ a– Save system configuration ◆ R–Rescan Oracle da
Prerelease 8 September 2005, 8:55am Menu Hot Keys Menu Hot Keys Action Keyboard Input Snapplan ALT+ S to open menu, then: Storage Checkpoints Storage Checkpoint Tablespaces ◆ M–Modify/Validate a snapplan ◆ R–Remove a Snapplan ◆ C–Create a snapshot using snapplan ◆ y–Resync a snapshot ◆ v–Reverse Resync a snapshot ◆ L–View log for the Snapplan ALT+S to open menu, then: ◆ C–Create a Storage Checkpoint ◆ S–Create a Storage Checkpoint schedule ◆ P–Create a Storage Checkpoint policy ◆
Support for Accessibility Settings and Assistive Technologies Prerelease 8 September 2005, 8:55am Support for Accessibility Settings and Assistive Technologies VERITAS software responds to operating system accessibility settings. VERITAS products are compatible with Microsoft's accessibility utilities.
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. autoextend An Oracle feature that automatically grows a database file by a prespecified size, up to a prespecified maximum size.
Prerelease 8 September 2005, 8:55am boot disk A disk used for booting an operating system. buffered I/O A mode of I/O operation (where I/O is any operation, program, or device that transfers data to or from a computer) that first transfers data into the Operating System buffer cache. cache Any memory used to reduce the time required to respond to an I/O request. The read cache holds data in anticipation that it will be requested by a client.
Prerelease 8 September 2005, 8:55am control file An Oracle control file specifies the physical structure of an Oracle database, including such things as the database name, names and locations of the datafiles and redo log files, and the timestamp of when the database was created. When you start an Oracle database, the control file is used to identify the database instance name redo log files that must be opened for transaction recording and recovery and datafiles where data is stored.
Prerelease 8 September 2005, 8:55am device file A block- or character-special file located in the /dev directory representing a device. device name The name of a device file. It represents a device. The c#t#d# syntax identifies the controller, target address, and disk. direct I/O An unbuffered form of I/O that bypasses the kernel’s buffering of data. With direct I/O, data is transferred directly between the disk and the user application.
Prerelease 8 September 2005, 8:55am 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.” Dynamic Multipathing Dynamic Multipathing (DMP) is a VERITAS Volume Manager feature that allows the use of multiple paths to the same storage device for load balancing and redundancy.
Prerelease 8 September 2005, 8:55am file system block The fundamental minimum size of allocation in a file system. fileset A collection of files within a file system. fixed extent size An extent attribute associated with overriding the default allocation policy of the file system. fragmentation Storage of data in non-contiguous areas on disk. As files are updated, new data is stored in available free space, which may not be contiguous.
Prerelease 8 September 2005, 8:55am inode list An inode is an on-disk data structure in the file system that defines everything about the file, except its name. Inodes contain information such as user and group ownership, access mode (permissions), access time, file size, file type, and the block map for the data contents of the file. Each inode is identified by a unique inode number in the file system where it resides. The inode number is used to find the inode in the inode list for the file system.
Prerelease 8 September 2005, 8:55am 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. load balancing The tuning of a computer system, network tuning, or disk subsystem in order to more evenly distribute the data and/or processing across available resources.
Prerelease 8 September 2005, 8:55am mirror A duplicate copy of a volume and the data therein (in the form of an ordered collection of subdisks). Each mirror is one copy of the volume with which the mirror is associated. The terms mirror and plex can be used synonymously. mirroring A layout technique that mirrors the contents of a volume onto multiple plexes. Each plex duplicates the data stored on the volume, but the plexes themselves may have different layouts.
Prerelease 8 September 2005, 8:55am Online Transaction Processing A type of system designed to support transaction-oriented applications. OLTP systems are designed to respond immediately to user requests and each request is considered to be a single transaction. Requests can involve adding, retrieving, updating or removing data. paging The transfer of program segments (pages) into and out of memory. Although paging is the primary mechanism for virtual memory, excessive paging is not desirable.
Prerelease 8 September 2005, 8:55am 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. This makes it possible to regenerate the data if a disk failure occurs. redo log files Redo log files record transactions pending on a database. If a failure prevents data from being permanently written to datafiles, changes can be obtained from the redo log files.
Prerelease 8 September 2005, 8:55am single threading The processing of one transaction to completion before starting the next. slave node A node that is not designated as a master node. snapped file system A file system whose exact image has been used to create a snapshot file system. 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.
Prerelease 8 September 2005, 8:55am stripe A set of stripe units that occupy the same positions across a series of columns in a multi-disk layout. stripe unit Equally sized areas that are allocated alternately on the subdisks (within columns) of each striped plex. In an array, this is a set of logically contiguous blocks that exist on each disk before allocations are made from the next disk in the array. A stripe unit may also be referred to as a stripe element.
Prerelease 8 September 2005, 8:55am throughput A measure of work accomplished in a given amount of time. For file systems, this typically refers to the number of I/O operations in a given period of time. unbuffered I/O I/O that bypasses the file system cache for the purpose of increasing I/O performance (also known as direct I/O). VERITAS Enterprise Administrator Application that is required to access graphical user interface (GUI) functionality.
Prerelease 8 September 2005, 8:55am VFR See “VERITAS File Replicator (VFR).” VVR See “VERITAS Volume Replicator (VVR).” VxDBA A VERITAS Storage Foundation for Oracle menu-driven utility or graphical user interface (GUI) that helps you manage your database environment. vxfs or VxFS The acronym for VERITAS File System. vxvm or VxVM The acronym for VERITAS Volume Manager.
Prerelease 8 September 2005, 8:55am 536 VERITAS Storage Foundation for Oracle Administrator’s Guide
Index Symbols $ORACLE_HOME 328 $ORACLE_SID 328 availability, using mirroring for 9 B backing up using NetBackup 28 using Storage Checkpoints 159 using Storage Checkpoints and Storage Rollback 146 backing up a database 222 backups control file listing 360 balancing I/O load 397 benefits of Quick I/O 66 BLI Backup.
Prerelease 8 September 2005, 8:56am dbed_ckptplan command 435 displaying schedules 174 displaying space usage 175 log file 168, 178 managing 435 overview 168 removing schedules 178 starting 169 changing file sizes 70 Checkpoints. See Storage Checkpoints chgrp command 72 chmod command 95 chown command 72, 95 clone databases creating 228, 452 restarting 233 shutting down 232, 452 unmounting file systems 232 clone databases, creating 436 cloning a database.
Prerelease 8 September 2005, 8:56am crontab file 423 cross-platform data sharing 20 customizing Cached Quick I/O 102 D daemon, VxDBA Monitoring Agent 366, 373 data change object 13 data dictionary 306 data redundancy 9 data warehousing 10 database backup using BLI Backup 28 management 251, 315 specifying type for Quick I/O 76, 77 status 328 tuning 399, 402 Database Administration menu 322 database files displaying 327, 329 restoring using Storage Checkpoints 354 Database FlashSnap applications 183 backing u
Prerelease 8 September 2005, 8:56am using the GUI 61 deleting Storage Checkpoints 285, 343 determining if Quick I/O installed and enabled 84 device interface 15 direct I/O 67, 399, 512, 514 direct-write, copy-behind 93 Dirty Region Logging 11 dirty region logging 11, 41 dirty volumes 11 disabling file system space alarm 369 disabling Cached Quick I/O for a file 102 disabling qio_cache_enable flag 96 disabling Quick I/O 90 discovered_direct_iosize tunable parameter 392 disk arrays 8 DMP-supported 15 disk gro
Prerelease 8 September 2005, 8:56am space allocation 70 file fragmentation, reporting on 77 file locks, during Storage Rollback 287, 346 file system requirements 28 file system block 516 file system locking 67 File System Space Alarm Administration menu 363 file systems configuration guidelines 48 creating using the command line 49 using the GUI 50 disabling space alarm for 369 displaying 327, 329 enabling space alarm for 368, 375 growing automatically 64, 361 growing to accommodate Quick I/O files 86 incre
Prerelease 8 September 2005, 8:56am K mkqio.dat file 78, 79, 90 mkqio.
Prerelease 8 September 2005, 8:56am Oracle datafile header size 70 Oracle Disk Manager 105 benefits 106 converting Quick I/O files 115 disabling 118 migrating files to 115 preparing existing databases for use with 114 restoring files using NetBackup 249, 485 setting up 112 working with OMF 109 Oracle Enterprise Manager 133 Oracle Managed Files 109 working with Oracle Disk Manager 109 Oracle tempfiles recreating 234 overview of Quick I/O 18 P parallel data transfer, using striping for 9 parallel Storage Roll
Prerelease 8 September 2005, 8:56am R RAID 8 RAID-0 9 RAID-0+1 9 RAID-1 9 RAID-1+0 10 RAID-5 10, 41 choosing 40 performance 41 RAID-5 log 41 raw devices ,unning databases on 18 rawasm directive 486 read_nstream 400 read_nstream tunable parameter 392 read_pref_io 400 read_pref_io tunable parameter 392 read-ahead algorithm, for Cached Quick I/O 93 RECOVER DATABASE UNTIL 165 recovering using Storage Checkpoints 159 recreating data using RAID-5 10 recreating temporary tablespaces 81 redo logs 28 configuration g
Prerelease 8 September 2005, 8:56am shutdown methods 324 shutdown.post.base 324 shutdown.pre.
Prerelease 8 September 2005, 8:56am Storage Mapping, overview 24 Storage Rollback 146, 432 buffer size used for 359 defined 22 of databases, tablespaces, or datafiles 26, 27 overview 21 parallel 348, 351, 353, 355, 357 restoring files, tablespaces, or databases 286, 344 threads used to 358 Storage Rollback Administration menu 286, 344 stripe unit sizes choosing 40 stripe units 9 striping 6, 9 defined 9 striping and mirroring data 9, 10 support for large files 21 symbolic links advantages and disadvantages 7
Prerelease 8 September 2005, 8:56am cluster functionality cross-platfrom data sharing 20 defragmentation utility 20 fast file system 19 multi-volume support 21 online administration utilities 20 overview 18 quality of storage service 21 quotas 23 resizing utility 20 support for large file systems 21 VERITAS Storage Foundation, license 28 VERITAS Volume Manager 6 and RAID 8 objects 7 overview 6 VERITAS Volume Replicator 16 volume layouts 8 changing 10 concatenation 9 mirrored-stripe 9 mirroring 9 RAID-5 10 s
Prerelease 8 September 2005, 8:56am 538 VERITAS Storage Foundation for Oracle Administrator’s Guide
