VERITAS Database Edition 3.5 for Oracle on HP-UX...

VERITAS Database Edition™ 3.5 for Oracle

®

Installation Guide

HP-UX

November 2002N09259G

Disclaimer

The information contained in this publication is subject to change without notice. VERITAS Software Corporation makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. VERITAS Software Corporation shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this manual.

Copyright

Copyright © 2001-2002 VERITAS Software Corporation. All rights reserved. VERITAS, VERITAS Software, the VERITAS logo, VERITAS Database Edition, and all other VERITAS product names and slogans are trademarks or registered trademarks of VERITAS Software Corporation in the USA and/or other countries. Other product names mentioned herein may be trademarks or registered trademarks of their respective companies.

VERITAS Software Corporation350 Ellis St.Mountain View, CA 94043 USAPhone 650–527–8000 Fax 650–527–2908 www.veritas.com

http://www.veritas.com

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i

Scope and Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i

Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii

Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v

Typographic and Symbolic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v

Notes and Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

The VRTSexplorer Diagnostic Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Other Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Chapter 1. Preinstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

General Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Obtaining a License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Using the VERITAS vLicense Web site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Using the License Key Request Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Operating System Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Patches for VERITAS Database Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Patches for VERITAS Volume Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Patches for VERITAS File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Patches for VERITAS Extension for Oracle Disk Manager . . . . . . . . . . . . . . . . . . 5

Additional Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

i

Important Preinstallation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

VERITAS Volume Manager Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Installing VxVM on HP-UX 11i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Upgrading to VxVM 3.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Configuration Decisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Disk Management Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Disabling Hot-Relocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 2. Installation and Deinstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Installation Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

VERITAS Database Edition Configuration Considerations . . . . . . . . . . . . . . . . . . . 13

VERITAS Enterprise Administrator Considerations . . . . . . . . . . . . . . . . . . . . . . . . . 14

Operating System Configuration Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Summary of VERITAS Database Edition Installation Tasks . . . . . . . . . . . . . . . . . . . . . 15

Installation Sequence Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Locating VERITAS Database Edition Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

VERITAS Database Edition Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Locations of VERITAS Database Edition Documentation . . . . . . . . . . . . . . . . . . . . . 18

Installing the VERITAS Database Edition Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Installation Background Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

JFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

September 2002 HP-UX 11i (11.11) Version 1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

VERITAS Volume Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Changes to System Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Using Asynchronous I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Mounting the CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Installing Using the installDBED Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Installing Using swinstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

ii VERITAS Database Edition for Oracle Installation Guide

Monitoring Installation Using the Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Installing the VERITAS Enterprise Administrator Client (Windows) . . . . . . . . . . . 25

Installing the VERITAS Enterprise Administrator Client (HP-UX) . . . . . . . . . . . . . 25

Unmounting the CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Verifying VERITAS Database Edition Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Deinstalling VERITAS Database Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

VERITAS Volume Manager Deinstallation Considerations . . . . . . . . . . . . . . . . . . . 27

Preparing to Deinstall VERITAS Volume Manager . . . . . . . . . . . . . . . . . . . . . . . 27

Moving VxVM Volumes to LVM Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Other Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Shutting Down VERITAS Volume Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Deinstalling VERITAS Database Edition Using the removeDBED Script . . . . . . . . 31

Chapter 3. Upgrade Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

VERITAS Volume Manager Upgrade Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Migrating VxVM Disk Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Upgrading the VERITAS Database Edition Software . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Upgrading from VERITAS Database Edition 2.1.1 or Earlier . . . . . . . . . . . . . . . . . . 41

Upgrading from VERITAS Database Edition 2.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Upgrading the Disk Group Version Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

VERITAS Volume Manager Root Disk Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Upgrading to a VxVM Root Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Chapter 4. Configuring the VERITAS Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Database Configuration Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Configuring VERITAS Database Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Setting Administrative Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Setting Up VERITAS Enterprise Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Starting VERITAS Enterprise Administrator Server . . . . . . . . . . . . . . . . . . . . . . . 49

Shutting Down VERITAS Enterprise Administrator Server . . . . . . . . . . . . . . . . 50

Starting the VERITAS Enterprise Administrator Client . . . . . . . . . . . . . . . . . . . . . . . 50

Contents iii

Adding Users to the VERITAS Enterprise Administrator Server Console Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Removing Users from the VERITAS Enterprise Administrator Server Console Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

vxtunefs Command Permissions and Cached Quick I/O . . . . . . . . . . . . . . . . . . . . . 53

Configuring VERITAS File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Upgrading the VxFS Disk Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Configuring VERITAS Volume Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Quick Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Custom Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Preventing Multipathing/Suppressing Devices from VxVM’s View . . . . . . . . . . . 62

Verifying VxVM Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Verifying the VERITAS Database Edition Installation . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Appendix A. Installation Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Sample Installation Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

iv VERITAS Database Edition for Oracle Installation Guide

Preface

VERITAS Database Edition for Oracle is an integrated set of system software enhancements and configuration guidelines that combine to help HP-UX database administrators configure a database system with high performance, availability, manageability, and reliability. This guide provides information on installing, configuring, and deinstalling the components of VERITAS Database Edition on the September 2002 HP-UX 11i (11.11) Version 1.0 release. Contact Hewlett-Packard for information on upgrading your operating system.

VERITAS Database Edition for Oracle provides the full functionality of VERITAS Volume Manager™ (VxVM™) and VERITAS File System™ (VxFS) with Quick I/O, VERITAS Extension for Oracle Disk Manager, Database FlashSnap, Storage Mapping, Storage Checkpoints, and the Storage Rollback feature.

Scope and AudienceThe VERITAS Database Edition for Oracle Installation Guide is intended for database and system administrators responsible for installing the components of VERITAS Database Edition, including:

◆ VERITAS Volume ManagerTM (VxVMTM)

◆ VERITAS File System with Quick I/OTM for Databases

◆ VERITAS Extension for Oracle Disk Manager

◆ VERITAS Database FlashSnap

◆ VERITAS Storage Mapping

◆ VxDBA Menu Utility

◆ VERITAS Database Edition GUI

◆ VERITAS Enterprise AdministratorTM (VEATM)

i

Organization

This guide assumes that the administrator has a:

◆ Basic understanding of system and database administration

◆ Working knowledge of the operating system

◆ General understanding of file systems

Organization◆ Chapter 1, “Preinstallation,” describes the licensing, product, and system

requirements for installing and using VERITAS Database Edition for Oracle.

◆ Chapter 2, “Installation and Deinstallation,” provides the installation and deinstallation procedures for VERITAS Database Edition for Oracle.

◆ Chapter 3, “Upgrade Procedures,” describes how to upgrade VERITAS Database Edition for Oracle if one or more VERITAS products are already installed on your system.

◆ Chapter 4, “Configuring the VERITAS Software,” describes how to initialize and begin using the VERITAS software included in the VERITAS Database Edition for Oracle package. In particular, this chapter discusses how to initialize VxVM using vxinstall.

◆ Appendix A, “Installation Sample Output,” shows the installation script output.

Related DocumentsThe following documents are included with VERITAS Database Edition:

◆ Release Notes provide important, up-to-date, and release-specific information for all the products licensed with this Edition. Read the Release Notes before installing or using any VERITAS products. Portable Document Format (.pdf) versions of these notes are provided on the product CD.

◆ The VERITAS Database Edition for Oracle Database Administrator’s Guide provides system and database administrators with the information and tools for using VERITAS products to configure and maintain Oracle databases with optimal performance, availability, manageability, and reliability.

◆ The VERITAS Volume Manager Administrator’s Guide describes the procedures and concepts involved with volume management and system administration using VERITAS Volume Manager. This guide includes how to take advantage of various VERITAS Volume Manager disk administration features, how to use VERITAS Volume Manager commands to create and manipulate objects, how to recover from disk failures, and how to monitor VERITAS Volume Manager performance.

ii VERITAS Database Edition for Oracle Installation Guide

Related Documents

◆ VERITAS Volume Manager User’s Guide - VERITAS Enterprise Administrator provides administrators with information on how to perform various VERITAS Volume Manager tasks through the VERITAS Enterprise Administrator (VEA) graphical user interface.

◆ The VERITAS FlashSnap Point-In-Time Copy Solutions Administrator’s Guide provides information about how to implement solutions for online backup of databases and cluster-shareable file systems, for decision support on enterprise systems, and for Storage Rollback of databases to implement fast database recovery.

◆ The VERITAS Volume Manager Migration Guide describes how to migrate from HP-UX Logical Volume Manager (LVM) to VERITAS Volume Manager (VxVM). This guide also provides instructions for converting disks and volumes managed by LVM to VxVM and discusses the terminology and graphical user interface (GUI) differences between the two volume managers.

◆ The VERITAS Volume Manager Hardware Notes provides important VERITAS Volume Manager hardware compatibility and support information.

◆ The VERITAS Volume Manager Troubleshooting Guide provides information about how to recover from hardware failure, and how to understand and deal with VxVM error messages.

◆ The VERITAS File System Administrator’s Guide provides conceptual information about VERITAS File System, describes how to use associated commands and utilities, and provides file system error message information and performance tuning guidelines. This guide also includes an appendix that describes how to perform common file system tasks with VERITAS File System and provides examples of typical VERITAS File System operations.

Preface iii

Related Documents

While not shipped with VERITAS Database Edition, the following documents provide related information if you plan to use VERITAS NetBackup to back up your databases:

◆ The VERITAS NetBackup Release Notes provide important, up-to-date, and release-specific information for VERITAS NetBackup. Reading all of the Release Notes before installing or using any VERITAS products is recommended.

◆ The VERITAS NetBackup BusinessServer Getting Started Guide explains how to install and configure VERITAS NetBackup.

◆ The VERITAS NetBackup User’s Guide explains how to use VERITAS NetBackup to back up, archive, and restore files and directories.

◆ The VERITAS NetBackup BusinesServer System Administrator’s Guide and VERITAS NetBackup DataCenter System Administrator’s Guide describe how to configure and manage the operation of VERITAS NetBackup.

◆ The VERITAS NetBackup BusinesServer Media Manager System Administrator’s Guide and VERITAS NetBackup DataCenter Media Manager System Administrator’s Guide describe how to use the extensive media management capabilities of VERITAS NetBackup.

◆ The VERITAS NetBackup for Oracle Advanced BLI Agent System Administrator’s Guide and VERITAS NetBackup for Advanced BLI Agent System Administrator’s Guide for Backups without RMAN provides information on how to configure and use the Advanced BLI Agent to perform Oracle database backups.

iv VERITAS Database Edition for Oracle Installation Guide

Conventions

Conventions

Typographic and SymbolicThe following tables explain the typographic and symbolic conventions used in this guide.

Typographic Conventions

Typeface Usage Examples

monospace Computer output, files, directories, software elements such as command options, function names, and parameters

Read tuneables from the /etc/vx/tunefstab file.

See the ls(1) manual page for more information.

monospace(bold)

User input # mount -F vxfs /h/filesys

italic New terms, book titles, emphasis, variables replaced with a name or value

See the User’s Guide for details.

The variable ncsize determines the value of...

Symbolic Conventions

Symbol Usage Examples

% C shell prompt

$ Bourne/Korn shell prompt

# Superuser (root) prompt (all shells)

SVRMGR> Oracle SQL prompt for Oracle8i and earlier.

SVRMGR> alter tablespace ts1 \begin backup;

SQL> Oracle SQL prompt for Oracle9i. SQL> alter tablespace ts1 \begin backup;

\ Continued input on the following line; you do not type this character

# mount -F vxfs \ /h/filesys

[ ] In a command synopsis, brackets indicates an optional argument

ls [ -a ]

Preface v

Getting Help

Notes and Cautions

Note A Note provides information that makes it easier to use the product or helps you avoid problems.

Caution A Caution warns you about situations that can cause data loss.

Getting Help

The VRTSexplorer Diagnostic ProgramThe VRTSexplorer program is available to assist VERITAS Customer Support engineers in diagnosing technical problems associated with VERITAS products. You can download this program from the VERITAS FTP site or install it from the VERITAS CD. For more information about the VRTSexplorer program, consult the README file located in the VRTSexplorer directory.

Instructions for downloading and installing VRTSexplorer are available in the VERITAS Database Edition for Oracle Release Notes.

Other AssistanceFor assistance with any of the VERITAS products, contact VERITAS Technical Support:

◆ U.S. and Canadian Customers: 1-800-342-0652

◆ International: +1-650-527-8555

◆ Email: [email protected]

| In a command synopsis, a vertical bar separates mutually exclusive arguments

mount [ suid | nosuid ]

blue text In Portable Document Format (.pdf) and HTML files, click on these active hyperlinks to move to the specified location

See “Using Snapshots for Database Backup” on page 97 for more information.

Symbolic Conventions

vi VERITAS Database Edition for Oracle Installation Guide

Getting Help

For license information:

◆ Phone: 1-925-931-2464


◆ Fax: 1-925-931-2487

For software updates:


For additional technical support information, such as TechNotes, product alerts, and hardware compatibility lists, visit the VERITAS Technical Support Web site at:

http://support.veritas.com

For additional information about VERITAS and VERITAS products, visit the Web site at:


Preface vii



Getting Help

viii VERITAS Database Edition for Oracle Installation Guide

Preinstallation
1 This chapter provides preinstallation information for VERITAS Database Edition for Oracle. Review the information in this chapter before installing or upgrading VERITAS products.
Topics covered in this chapter include:

◆ “General Installation Requirements” on page 1

◆ “Important Preinstallation Information” on page 7

◆ “VERITAS Volume Manager Considerations” on page 8

After reviewing the information in this chapter, see “Installation and Deinstallation” on page 13 for information on installing VERITAS Database Edition for Oracle for the first time, or see “Upgrade Procedures” on page 37 if you are already a VERITAS Database Edition for Oracle, VERITAS File System, or VERITAS Volume Manager user.

General Installation RequirementsBefore installing VERITAS Database Edition, read the following sections to make sure you understand and comply with the basic requirements of the software.

Obtaining a License KeyVERITAS Database Edition for Oracle is a licensed product. When you purchase VERITAS products, you receive a license key, which is required during installation. VERITAS Database Edition requires one license key for all the software packages included with the Edition and any optional features you may have purchased (such as the Database FlashSnap or Storage Mapping options).

If you already have an evaluation license key for VERITAS Database Edition, you need to obtain a permanent license key when you purchase the product.

Note You must obtain your license key before using this product.

1

General Installation Requirements

Using the VERITAS vLicense Web site

You can obtain your license key through the VERITAS vLicense Web site. To use the Web site, you need your customer number, order number, and serial number.

▼ To obtain a license key using the Web site

1. Use a web browser to access the VERITAS vLicense Web site.

http://vlicense.veritas.com

2. Create a new login using your customer number, order number, and serial number.

If you already have an account, you can simply log in.

3. Follow the instructions on the Web site.

You should receive your license key shortly. After receiving your license key, you can install the product.

Note For more information, see the VERITAS Storage Solutions Product License and Installation Guide.

Using the License Key Request Form

You should have received a License Key Request Form when you purchased this product. If you do not have a License Key Request Form, contact your sales channel to purchase one.

▼ To obtain a license key using the License Key Request Form

1. Complete the License Key Request Form.

The License Key Request Form requires you to provide your system’s host ID and machine type. You can obtain the host ID using the following command:

# /usr/bin/uname -i

You can obtain the machine type using the following command:

# /usr/bin/uname -m

2. Fax or email the form to VERITAS.


◆ Fax: 1-925-931-2487

VERITAS will send you a license key by return fax or email.

2 VERITAS Database Edition for Oracle Installation Guide

http://vlicense.veritas.com


During installation, you are prompted for the license key. If the software is already installed and you are upgrading or replacing an evaluation license with a permanent license, follow the instructions that accompany the license key to replace the old license with the new one.

Note Make a note of your license key somewhere other than on the computer, so that the key is available if the system becomes unbootable or requires reinstallation.

If you have any questions about licensing, contact VERITAS at one of the phone numbers listed in “Getting Help” on page vi in the Preface.

Operating SystemVERITAS Database Edition for Oracle requires the September 2002 HP-UX 11i (11.11) Version 1.0 release for HP 9000/* servers. Installing this Edition on any other HP-UX release will fail. If necessary, upgrade to the September 2002 HP-UX 11i (11.11) Version 1.0 release before you install the VERITAS products.

▼ To verify that the operating system is September 2002 HP-UX 11i (11.11) Version 1.0

Enter the swlist command as follows:

# swlist | grep HPUXBaseAuxHPUXBaseAux B.11.11.0209 HP-UX Base OS Auxiliary

If you do not have the correct HP-UX version, see your Hewlett-Packard documentation for instructions on how to install or upgrade to September 2002 HP-UX 11i (11.11) Version 1.0.

Note You must have JFS installed on your system prior to installing the VERITAS software.

Note VxVM is part of the operating system (OS), and may have already been installed on your system. If VxVM is on your system, you still need to install the patches listed in “Operating System Patches” on page 4.

Chapter 1, Preinstallation 3


Operating System PatchesFor the most up-to-date patch information, see TechNote 250499 at http://seer.support.veritas.com/docs/250499.htm.

Patches for VERITAS Database Edition

Before you can install VERITAS Database Edition, it is necessary that you have the September 2002 HP-UX 11i (11.11) Version 1.0 release installed on your system. Contact HP for information on how to obtain this release.

Patches for VERITAS Volume Manager

The following table shows the patches required for VERITAS Volume Manager, and indicates which patches are required and which are optional. The optional patches enhance VxVM’s functionality, but VxVM can be run without them. It is recommended that you install all patches.

HP-UX Operating System Patches for VERITAS Volume Manager

Patch Number Description Required/Recommended

PHKL_27563 SCSI IO Subsystem Cumulative Patch Recommended

PHKL_27096 Patch for the VxVM rootability changes to HP-UX Kernel

Required (needed for successful VxVM 3.5 installation)

PHKL_27177 VxVM boot support changes for OS bootloader

Recommended

PHKL_27971 VxVM Kernel Cumulative Patch Required

PHCO_27100 Patch for VxVM rootability changes to HFS mkfs command

Recommended

PHCO_27101 Patch for VxVM rootability changes to mkboot command


PHCO_27243 or PHCO_27209

Patch for VxVM rootability changes to the insf command


PHCO_27099 Patch for VxVM rootability changes to LVM commands

Recommended

PHCO_27103 Patch for VxVM rootability changes to /sbin/pre_init_rc

Recommended

PHCO_27185 ioinitrc(iM) patch Recommended

PHCO_27972 VxVM Command Cumulative Patch Required


http://seer.support.veritas.com/docs/250499.htm



Note Currently, the required VxVM rootability patches are installed by default with the September 2002 HP-UX 11i (11.11) Version 1.0 release.

Patches for VERITAS File System

The following table shows the patch required for VERITAS File System:

Patches for VERITAS Extension for Oracle Disk Manager

The following table shows the patch required for VERITAS Extension for Oracle Disk Manager.

Additional Patches

If any problems requiring a patch fix develop subsequent to the release, you can find the information online at the HP IT Resource Center Web site:

http://ITresourcecenter.hp.com

Select individual patches to search the Patch Database. Select HP-UX Patches, then select 11.11 as the OS version and search for the product keyword to get a list of patches.

HP-UX Operating System Patches for VERITAS File System


PHKL_26761 Required only for the operation of the vx_ninode tunable parameter. The vx_ninode parameter specifies the maximum number of inodes available in the VxFS in-memory inode cache. If not explicitly specified, the value of vx_ninode is based on how much physical memory is available on the system. See the VERITAS File System Administrator’s Guide for more information.

Recommended

HP-UX Operating System Patches for VERITAS Extension for Oracle Disk Manager


PHKL_27800 This HP patch addresses various bug fixes made for Oracle Disk Manager.

Required for VERITAS Extension for Oracle Disk Manager functionality.


http://itresourcecenter.hp.com


Alternatively, VERITAS regularly updates information regarding mandatory and optional patches provided for its products. You can check for the latest VERITAS Database Edition for Oracle patch information on the VERITAS Technical Support Web site:

1. In your Web browser, specify http://support.veritas.com.

2. Select Patches and Updates, located on the left side of the window.

3. From the “Patches and Updates Product List,” select Editions > Database Edition for Oracle.

By default, all VERITAS Database Edition documentation appears in the list.

4. Use the Patches and Updates Filter Wizard to refine your search:

- Keyword: Optionally, enter a keyword to narrow your search.

- Select a File Type: From the drop-down list, select “Patch.”

- Select a Language: Optionally, select the language in which the document was written.

- Select a Version: Select the version of the your Edition software.

- Select a Platform: Select HP-UX as the platform.

5. Select Find Files to search for patches and updates.

If a patch is available, you will then be able to select it from a list for downloading.

Release NotesRead the Release Notes for all products included with this Edition. Portable Document Format (.pdf) versions of the VERITAS Database Edition for Oracle Release Notes, VERITAS Volume Manager Release Notes, and the VERITAS File System Release Notes are included on the VERITAS Storage Solutions 3.5 for HP-UX CD1 in the database_edition_for_oracle/release_notes directory.



Important Preinstallation Information

Important Preinstallation InformationThe following table identifies the supported Oracle and HP-UX combinations for VERITAS Database Edition:

Disk SpaceBefore installing the software, confirm that there is sufficient disk space on the target systems. The following table shows the suggested minimum space requirements for each package:

Oracle Version September 2002 HP-UX 11i (11.11) Version 1.0 release, 64-bit

8.0.x (32- and 64-bit) Yes

8.1.7 (32- and 64-bit) Yes

9.0.1 (9i Release 1) 64-bit Yes

9.2 (9i Release 2) 64-bit Yes

Package Contents Size

VRTSdbed VERITAS Database Edition Utilities (required)) 11MB

VRTSvlic VERITAS Licensing Utilities (required) 6MB

VRTSorgui VERITAS Database Edition Graphical User Interface (required for VEA)

4MB

VRTSordoc VERITAS Database Edition for Oracle Documentation 2MB

VRTSvxvm Base VERITAS Volume Manager 3.5 for HP-UX (required)

41MB

VRTSvmpro VERITAS Volume Manager Management Services Provider (required for VEA)

7MB

VRTSvmdoc VERITAS Volume Manager Documentation 6MB

VRTSvxfs VERITAS File System with CFS Support (required) 20MB

VRTSfspro VERITAS File System Management Services Provider (required for VEA)

5MB

VRTSfsdoc VERITAS File System Documentation 1MB

VRTSodm VERITAS Extension for Oracle Disk Manager (required) 1MB

VRTSvxmsa VERITAS Federated Mapping Services 1MB


VERITAS Volume Manager Considerations

Environment VariablesMost of the commands used in the installation are in the /sbin or /usr/sbin directory However, there are additional variables needed in order to use the VERITAS Database Edition product after installation. Add the following directories to your PATH environment variable:

◆ If you are using Bourne or Korn shell (sh or ksh), use the commands:

$ PATH=$PATH:/opt/VRTS/bin:/sbin:/usr/sbin:/opt/VRTSob/bin$ MANPATH=$MANPATH:/opt/VRTS/man:/usr/share/man$ export PATH MANPATH

◆ If you are using a C shell (csh or tcsh), use the commands:

% set path = ($path /opt/VRTS/bin /sbin /usr/sbin \/opt/VRTSob/bin)

% setenv MANPATH /usr/share/man:/opt/VRTS/man:$MANPATH

VERITAS Volume Manager ConsiderationsReview the following Volume Manager-related items before installing or upgrading VERITAS Database Edition for Oracle.

Installing VxVM on HP-UX 11i VxVM is part of the Operating System (OS), and is installed by default on every new OE installation. In the September 2002 HP-UX 11i (11.11) Version 1.0 release, you have the option of selecting VxVM for the root disk when installing using the HP Ignite-UX installation software. If you choose this option, the root disk group will be initialized by the Ignite-UX installation process, and there will be no need to run the vxinstall script.

VRTSob VERITAS Enterprise Administrator Service (required for VEA)

20MB

VRTSobgui VERITAS Enterprise Administrator (required for VEA) 58MB

VRTSobgui.msi VERITAS Enterprise Administrator for Windows® (client installation only)

13MB

Total space for all packages on the server 196MB

Total space for required packages 79MB

Package Contents Size



If you have an LVM disk as your root disk, or if you are upgrading from a previous version of VxVM, you can use the vxcp_lvmroot(1M) command to create a VxVM root disk. The VxVM root disk can then replace or co-exist with your LVM disk (that is, you can boot from either the LVM or the VxVM root disk).

If you choose to be rooted from LVM disks and want to bring up VxVM, then you need to run vxinstall to initialize VxVM. You can also use the vxvmconvert utility to convert LVM volumes to VxVM volumes.



Upgrading to VxVM 3.5Your upgrade to VxVM 3.5 will fall into one of the following categories:

◆ VxVM Controlling the Root Disk

Upgrade of an existing HP-UX 11i system to VxVM rootability can be accomplished in conjunction with the September 2002 HP-UX 11i (11.11) Version 1.0 release or by using the vxcp_lvmroot(1M) command to clone the LVM root disk.

◆ VxVM Not Controlling the Root Disk

If your system is running under HP-UX 11.0 or earlier, you must first upgrade your operating system.

The upgrade procedure allows you to retain your existing VxVM configuration without running the vxinstall script. After upgrading, you can resume using VxVM with the same configuration as before.

Note On importing a 3.0, 3.1, or 3.2 VxVM disk group (any disk group version prior to version 90), you are given the option to upgrade the disk group version to the VxVM 3.5 level. Each VxVM 3.5 disk group can also be manually upgraded following the VxVM upgrade. See “Upgrading the Disk Group Version Separately” on page 43 for more information.

Configuration DecisionsBefore initializing VERITAS Volume Manager, make sure you are aware of the contents of each disk. During the initialization process, you must decide the following:

◆ Do you want to place all or just some of the disks on the system under VERITAS Volume Manager control?

◆ Do you want to place the system’s boot disk under VERITAS Volume Manager control? (This is necessary in a one-disk system.)

◆ When you place disks under VERITAS Volume Manager control, do you want to preserve data in any or all existing file systems and partitions through encapsulation?

◆ For each disk, do you want to choose whether to encapsulate, initialize, or leave the disk alone (Custom Installation)? Alternatively, do you want to either encapsulate or initialize all disks on a controller together (Quick Installation)?

Note After the above steps have been completed, reboot the system to properly initialize VERITAS Volume Manager. Until you reboot, the software initialization is not complete. Refer to “VERITAS Database Edition Configuration Considerations” on page 13 for reboot planning issues.



Disk Management RequirementsDisks to be managed by VERITAS Volume Manager must have two free partitions and a small amount of free space (one cylinder). The free space must be at the beginning or end of the disk and must not belong to a partition. This space is used for storing disk group configurations and a disk label that enables VERITAS Volume Manager to identify the disk, even if it is moved to a different address, controller, or host. VERITAS Volume Manager allocates approximately one cylinder (512K) from each disk for the disk group configurations and the disk label. This space is sufficient to handle normal disk group configurations for up to approximately 100 disks. (If you have a larger configuration and need to increase the private region size, see the vxdg(1M) and vxdisk(1M) manual pages.)

The boot disk is a special case. If no other space is available, VERITAS Volume Manager attempts to allocate space usually reserved for swap by shrinking the swap partition. This process is known as swap relocation and, if necessary, happens automatically during boot disk encapsulation. Although swap relocation can provide the free space required, it does not eliminate the need for two free partitions.

Note While it is possible to put disks with no free space under VERITAS Volume Manager control, this is only used as a migration strategy. Many VxVM capabilities based on disk identity are available only for disks with the required free space. See the vxdisk(1M) manual page for information on the nopriv disk type.

Disabling Hot-RelocationThe hot-relocation feature detects disk failure automatically, notifies you of the nature of the failure, attempts to relocate any affected subdisks that are redundant, and initiates recovery procedures.

The hot-relocation feature is enabled by default and it is recommended that you leave it on. However, if you need to disable it for some reason (for example, you do not want the free space on some of your disks used for relocation), you can do so by preventing the vxrelocd daemon from starting during system startup. Disable hot-relocation only after you install the VERITAS Volume Manager packages.



▼ To disable hot-relocation

1. Comment out the vxrelocd line in the startup file /sbin/rc2.d/S096vxvm-recover, as follows:

# nohup vxrelocd root &

2. After editing the file, you can kill the vxrelocd process or reboot the system.

Note If you disable hot-relocation, you are not notified by electronic mail of any failures that occur. This is because vxrelocd is responsible for notifying the system administrator of failures.

For more information on hot-relocation and vxrelocd, refer to the VERITAS Volume Manager Administrator’s Guide and the vxrelocd(1M) manual page.


Installation and Deinstallation
2 This chapter provides an overview of VERITAS Database Edition for Oracle installation tasks and describes how to install the product for the first time. This chapter also provides instructions for deinstalling and upgrading VERITAS Database Edition for Oracle.

◆ “Installation Considerations” on page 13

◆ “Summary of VERITAS Database Edition Installation Tasks” on page 15

◆ “Locating VERITAS Database Edition Packages” on page 16

◆ “Installing the VERITAS Database Edition Software” on page 18

◆ “Verifying VERITAS Database Edition Licensing” on page 26

◆ “Deinstalling VERITAS Database Edition” on page 27

The VERITAS Database Edition for Oracle software uses the swinstall utility of HP-UX. For additional information on using swinstall, see the documentation published by the Hewlett-Packard Company that accompanied your HP system.

Installation ConsiderationsVERITAS software and operating system installation considerations are described in the following sections.

VERITAS Database Edition Configuration Considerations◆ When installing major operating system components, such as VERITAS Database

Edition for Oracle, at least one system reboot is required. The reboot installs new kernel components and updates device entries. Modify the HP kernel settings to support the Oracle database before installing all VERITAS Database Edition components because installing either VERITAS Volume Manager or VERITAS File System (or both) requires a system reboot.

13

Installation Considerations

◆ After installing the VERITAS Database Edition packages, you must reboot the system and then initialize VERITAS Volume Manager (using the vxinstall program). See “Configuring VERITAS Volume Manager” on page 55 for more details on VERITAS Volume Manager initialization.

VERITAS Enterprise Administrator ConsiderationsVERITAS Enterprise Administrator (VEA) is required to access the graphical user interface (GUI) for VERITAS Database Edition, VERITAS Volume Manager, and VERITAS File System. You can use the GUI to administer disks, volumes, file systems, and VERITAS Database Edition on local or remote machines.

VEA has a client/server architecture. The VEA server is supported on HP-UX 11.11 and the VEA client is supported on HP-UX 11.11, Windows NT, Windows Me, Windows 2000, and Windows 98.

The following software must be installed and running to be administered by VEA:

◆ VERITAS Volume Manager

◆ VERITAS File System

◆ VERITAS Database Edition

To use VEA, the following packages need to be installed and running on the server:

◆ VERITAS Enterprise Administrator Service (VRTSob)

◆ VERITAS Volume Manager Management Services Provider (VRTSvmpro)

◆ VERITAS File System Management Services Provider(VRTSfspro)

◆ VERITAS Database Edition Graphical User Interface (VRTSorgui)

In addition, one of the following packages needs to be installed and running on the client:

◆ VERITAS Enterprise Administrator (VRTSobgui)

This is the client package for HP-UX.

◆ VERITAS Enterprise Administrator for Windows® (VRTSobgui.msi)

This is the client package for Windows.

The following are minimum system recommendations for the VEA client:

HP-UX: HP-UX 11i (11.11) 9000/* (64-bit)

Windows: 100MHz Pentium with 32MB memory

14

Summary of VERITAS Database Edition Installation Tasks

Operating System Configuration Considerations◆ If patches to the HP operating system are required, they should be applied just prior

to installing the VERITAS products. Patches may be required to resolve HP kernel, product performance, or other issues.

◆ The system should be in a quiescent state before adding patches.

Note See product Release Notes for last minute information on patches required for VERITAS, Oracle, and HP software.

Summary of VERITAS Database Edition Installation TasksInstallation of VERITAS Database Edition for Oracle consists of the following tasks:

◆ Reviewing preinstallation requirements (see Chapter 1, “Preinstallation” on page 1) and making any necessary modifications.

◆ Obtaining the necessary license key.

◆ Installing or upgrading the VERITAS Database Edition for Oracle software packages.

◆ Configuring the VERITAS software (see Chapter 4, “Configuring the VERITAS Software” on page 47).

Alternatively, you can use the Installation Menu on the VERITAS Storage Solutions 3.5 for HP-UX CD. For more information, see the VERITAS Storage Solutions Product License and Installation Guide. The VERITAS Storage Solutions Product License and Installation Guide is included in the VERITAS packages.

Installation Sequence Summary

▼ The recommended installation sequence is

1. Review the Release Notes.

2. Add HP operating system patches. Refer to the Release Notes for specific software patch information.

3. Modify the /stand/system file and include any settings required by your database software or other products. See “VERITAS Database Edition Configuration Considerations” on page 13 for more information.

Chapter 2, Installation and Deinstallation 15

Locating VERITAS Database Edition Packages

4. For upgrades, you need to determine if the root disk is encapsulated, since this effects which upgrade process you should use. See Chapter 4, “Configuring the VERITAS Software” on page 47, for more information.

5. For new installations, install VERITAS Database Edition as described in “Installing the VERITAS Database Edition Software” on page 18.

Installing VERITAS Database Edition entails the following:

- Running the installDBED script to add the VERITAS Database Edition product.

- Rebooting the system.

- Running the vxinstall program to configure the VERITAS Volume Manager.

Locating VERITAS Database Edition PackagesVERITAS products are distributed on two VERITAS Storage Solutions 3.5 for HP-UX CDs: CD1 and CD2. The following VERITAS Database Edition for Oracle packages are included in the database_edition_for_oracle/pkgs directory on CD1:

◆ VERITAS Database Edition for Oracle packages:

- VRTSdbed: VERITAS Database Edition software, including the VxDBA utility

- VRTSodm: VERITAS Extension for Oracle Disk Manager software

- VRTSorgui: VERITAS Database Edition for Oracle Graphical User Interface for Oracle

- VRTSordoc: Portable Document Format (.pdf) versions of VERITAS Database Edition documentation

◆ VERITAS Volume Manager packages:

- VRTSvxvm: Base VERITAS Volume Manager 3.5 for HP-UX

- VRTSvmpro: VERITAS Volume Manager Management Services Provider

- VRTSvmdoc: Portable Document Format (.pdf) versions of the VERITAS Volume Manager software documentation

◆ VERITAS File System packages:

- VRTSvxfs: VERITAS File System with CFS Support

- VRTSfspro: VERITAS File System Management Services Provider

- VRTSfsdoc: Portable Document Format (.pdf) versions of the VERITAS File System software documentation

◆ VRTSvlic: VERITAS License Utilities

16

Locating VERITAS Database Edition Packages

◆ VRTSvxmsa: VERITAS Federated Mapping Services

◆ VERITAS Enterprise Administrator packages

- VRTSob: VERITAS Enterprise Administrator Services

- VRTSobgui: VERITAS Enterprise Administrator

- VRTSobgui.msi: VERITAS Enterprise Administrator for Windows®

VERITAS Database Edition DocumentationVERITAS no longer ships hardcopy documentation with its products. Adobe Portable Document Format (.pdf) files are supplied with VERITAS Database Edition for Oracle:

◆ In the database_edition_for_oracle/release_notes directory:

- dbed_notes.pdf: VERITAS Database Edition for Oracle Release Notes

- vxvm_notes.pdf: VERITAS Volume Manager Release Notes

- vxfs_notes.pdf: VERITAS File System Release Notes

◆ In the database_edition_for_oracle/docs directory:

- VERITAS Database Edition for Oracle Installation Guide

- VERITAS Database Edition for Oracle Database Administrator’s Guide

- VERITAS Volume Manager Administrator’s Guide

- VERITAS Volume Manager User’s Guide - VERITAS Enterprise Administrator

- VERITAS Volume Manager Troubleshooting Guide

- VERITAS Volume Manager Hardware Notes

- VERITAS FlashSnap Point-In-Time Copy Solutions Administrator’s Guide

- VERITAS Volume Manager Migration Guide

- VERITAS Volume Manager Installation Guide

- VERITAS File System Administrator’s Guide

- VERITAS File System Installation Guide

To view or print Portable Document Format (.pdf) documents, you must use Adobe Acrobat Reader.


Installing the VERITAS Database Edition Software

Locations of VERITAS Database Edition DocumentationRelease Notes for all products included with VERITAS Database Edition for Oracle can be found in the database_edition_for_oracle/release_notes directory on CD1.

If you are installing the documentation packages, the /opt directory must exist and be writable. Documentation packages for VERITAS Database Edition and VERITAS File System are installed in the /opt directory. VERITAS Volume Manager documentation is installed in the /usr/share/doc/vxvm directory. Each package contains the documentation for its respective product.

Because product Release Notes are not installed by any packages, VERITAS recommends that you copy them from CD1 to a directory on your system so that they are available for future reference.

Installing the VERITAS Database Edition SoftwareThis section describes how to install the VERITAS Database Edition for Oracle software packages for the first time.

After you complete the installation procedure, read Chapter 4, “Configuring the VERITAS Software” on page 47 for important details about initializing, setting up, and using the VERITAS software shipped with the VERITAS Database Edition for Oracle.

Alternatively, you can use the Installation Menu on the VERITAS Storage Solutions 3.5 for HP-UX CD. For more information, see the VERITAS Storage Solutions Product License and Installation Guide. The VERITAS Storage Solutions Product License and Installation Guide is included in the VERITAS packaging.

Note Only users with superuser (root) privileges can install the VERITAS products.

Documentation Package Contents

VRTSordoc VERITAS Database Edition documentation

VRTSvmdoc VERITAS Volume Manager documentation

VRTSfsdoc VERITAS File System Documentation

18


Installation Background Information

JFS

VERITAS Database Edition 3.5 for Oracle requires JFS to be on the system before attempting to install. JFS is part of the HP-UX 11i (11.11) operating environment.

▼ To ensure that JFS is installed

Use the swlist command as follows:

# swlist -l product JFSJFS B.11.11 The Base VxFS File System

September 2002 HP-UX 11i (11.11) Version 1.0

VERITAS Database Edition for Oracle requires the September 2002 HP-UX 11i (11.11) Version 1.0 release for HP 9000/* servers. Installing this Edition on any other HP-UX release will fail. If necessary, upgrade to the September 2002 HP-UX 11i (11.11) Version 1.0 release before you install the VERITAS products.

▼ To verify that the operating system is September 2002 HP-UX 11i (11.11) Version 1.0

Enter the swlist command as follows:

# swlist | grep HPUXBaseAuxHPUXBaseAux B.11.11.0209 HP-UX Base OS Auxiliary

If you do not have the correct HP-UX version, see your Hewlett-Packard documentation for instructions on how to install or upgrade to September 2002 HP-UX 11i (11.11) Version 1.0.

VERITAS Volume Manager

If you have the September 2002 HP-UX 11i (11.11) Version 1.0 release, VERITAS Volume Manager may be installed on your system.

▼ To check if VERITAS Volume Manager is installed on your system

Use the swlist command as follows:

# swlist -l bundle -l product | grep Base-VXVMBase-VXVM B.03.50.5 Base VERITAS Volume Manager Bundle 3.5Base-VXVM.VRTSvxvm 3.5m Base VERITAS Volume Manager 3.5 for HP-Base-VXVM.VRTSvmdoc 3.5m VERITAS Volume Manager DocumentationBase-VXVM.VRTSfspro 3.5-ga08 VERITAS File System Management Services



Base-VXVM.VRTSvmpro 3.5m VERITAS Volume Manager Management ServiBase-VXVM.VRTSobgui 3.0.2.261a VERITAS Enterprise AdministratorBase-VXVM.VRTSob 3.0.2.261a VERITAS Enterprise Administrator ServicBase-VXVM.VRTSvlic 3.00.007e VERITAS License Utilities

Changes to System Configuration File

The VERITAS Database Edition for Oracle installation makes changes to the /stand/system file and rebuilds the kernel with this file. If you used a system configuration file other than /stand/system to configure your current kernel, you must copy your configuration changes to /stand/system. Otherwise, the kernel built by the installation does not include your changes.

Using Asynchronous I/O

If you did not use raw devices for your database, it is likely that your system was not configured to perform asynchronous I/O. VERITAS Database Edition for Oracle supports asynchronous I/O on Quick I/O files and Oracle Disk Manager files.

For the Oracle database to take advantage of the asynchronous I/O capability offered by Database Edition, you must create the following device:

/dev/async

Refer to your Oracle installation guide for instructions on how to create this device.

Caution There are system and database configuration requirements that must be met before enabling asynchronous I/O. To make sure your environment meets those requirements, see your Oracle documentation.

For more information on asynchronous I/O with Quick I/O, refer to Oracle8i Administrator’s Reference Release 3 (8.1.7) for HP 9000 Series HP-UX (Part Number A85346-01).

For more information on asynchronous I/O with Oracle Disk Manager, refer to Oracle9i Administrator’s Reference Release 1 (9.0.1) for UNIX Systems (Part Number A90347-02).

20


Mounting the CD

1. Create a mount point directory, /cdrom, if it does not exist. The directory must have read/write permissions.

2. Determine the block device file for the CD-ROM drive:

# ioscan -fnC disk

Here is the partial listing of the sample output provided by the above ioscan command:

Make a note of the device file as it applies to your system.

3. Run the following commands to start PFS (Portable File System):

# nohup pfs_mountd &# nohup pfsd &

4. Mount the CD-ROM by entering:

# /usr/sbin/pfs_mount -t rrip /dev/dsk/c#t#d# /cdrom

where /c#t#d# is the location of the drive.

Installing Using the installDBED ScriptInstall VERITAS Database Edition for Oracle packages using installDBED. The installDBED script uses the swinstall utility, the standard method for adding new system software on an HP-UX server.

Before installing, make sure you have all required patches installed on your system. See “Operating System Patches” on page 4 for more information.

Class I H/W Path Driver S/W State H/W Type Description=============================================================disk 1 10/0.1.0 sdisk CLAIMED DEVICE SEAGATE ST318404LC

/dev/dsk/c3t5d0 /dev/rdsk/c3t1d0

...list of installed disks...

disk 11 10/0.6.0 sdisk CLAIMED DEVICE TOSHIBA CD-ROM XM-5401TA

/dev/dsk/c5t2d0 /dev/rdsk/c5t2d0disk 12 10/0.5.0 sdisk CLAIMED DEVICE PIONEER DVD-ROM

DVD-30/dev/dsk/c3t2d0 /dev/rdsk/c3t2d0



Installation of VERITAS Volume Manager or VERITAS File System automatically reboots the system.

HP-UX patches PHKL_27971 and PHCO_27972 are installed automatically when you install VERITAS Database Edition using installDBED.

Note When you install VERITAS Database Edition, a symbolic link to VxDBA is created in the /opt/VRTS/bin directory, linking /opt/VRTS/bin/vxdba_ora to /opt/VRTSdbed/bin/vxdba.

Note The Edition installation script ensures package compatibility, proper licensing, and is the recommended method for installation.

▼ To install VERITAS Database Edition using installDBED

1. Make sure that you have applied any required VERITAS patches. For more information, go to http://seer.support.veritas.com/docs/250499.htm.

2. Go to the /cdrom mount point:

# cd /cdrom/database_edition_for_oracle

Note The VERITAS Database Edition software is located on CD1.

3. Type the VERITAS Database Edition for Oracle installation program name to begin installing the software:

# ./installDBED

The system prints out a series of status messages as the installation progresses and prompts you for any required information, such as the license key. Answer any questions asked of you during the installation. (Appendix A provides sample output from the installation program.)

- If you do not intend to use the VERITAS Database Edition GUI, you can skip the VRTSobgui and VRTSorgui packages. They are optional.

- If you do not intend to use FlashSnap, you can skip the VRTSvmpro and VRTSfspro packages. They are optional.

- If you do not intend to use Storage Mapping, you can skip the VRTSvxmsa package. It is optional.

- If you do not intend to view or print the online documentation, you can omit the VRTSordoc, VRTSfsdoc, and VRTSvmdoc packages.

22




Note If you choose not to make permission changes to allow database administrators access to the /opt/VRTSdbed directory during installation, you can do so at a later time. See “Setting Administrative Permissions” on page 48 for more information.

4. The system automatically reboots after installation. If, for some reason, the system is not rebooted, you will need to do so manually.

5. After the system has been rebooted, enable the VxFS full feature license by entering:

# /sbin/fs/vxfs3.5/vxenablef -e full

6. You may need to initialize VERITAS Volume Manager using the vxinstall command. See “Configuring VERITAS Volume Manager” on page 55 for information on initializing VERITAS Volume Manager.

Installing Using swinstallIf you are installing the VERITAS Database Edition for Oracle packages using the HP-UX swinstall utility directly instead of with the installDBED script, you must follow a specific installation order. Installing the packages in the specified order ensures that all of the required components are installed correctly and all of their features are enabled.

Before installing, make sure you have all required patches installed on your system. See “Operating System Patches” on page 4 for more information.

Installation of VERITAS Volume Manager or VERITAS File System automatically reboots the system.

HP-UX patches PHKL_27971 and PHCO_27972 are installed automatically when you install the VERITAS Volume Manager package (VRTSvxvm).

Note When you install VERITAS Database Edition, a symbolic link to VxDBA is created in the /opt/VRTS/bin directory, linking /opt/VRTS/bin/vxdba_ora to /opt/VRTSdbed/bin/vxdba.

▼ To install VERITAS Database Edition using swinstall

1. Make sure that you have applied any required VERITAS patches. For more information, go to http://seer.support.veritas.com/docs/250499.htm.

2. Go to the /cdrom mount point:

# cd /cdrom/database_edition_for_oracle/pkgs





Note The VERITAS Database Edition software is located on CD1.

3. Install the following packages in the order shown:

# swinstall -x autoreboot=true -x mount_all_filesystems=false \-s ‘pwd‘ VRTSdbed VRTSvlic VRTSodm VRTSob VRTSobgui VRTSorgui \VRTSvmpro VRTSfspro VRTSordoc VRTSvmdoc VRTSfsdoc VRTSvxvm \VRTSvxfs VRTSvxmsa

Caution If you are not installing VERITAS Volume Manager (VRTSvxvm) because it is already installed on your system, you must install HP-UX patches PHKL_27971 and PHCO_27972.

The system prints out a series of status messages as the installation progresses. (Appendix A provides sample output from the installation program.)

- If you do not intend to use the VERITAS Database Edition GUI, you can skip the VRTSobgui and VRTSorgui packages. They are optional.

- If you do not intend to use FlashSnap, you can skip the VRTSvmpro and VRTSfspro packages. They are optional.

- If you do not intend to use Storage Mapping, you can skip the VRTSvxmsa package. It is optional.

- If you do not intend to view or print the online documentation, you can omit the VRTSordoc, VRTSfsdoc, and VRTSvmdoc packages.

Note If you choose not to make permission changes to allow database administrators access to the /opt/VRTSdbed directory during installation, you can do so at a later time. See “Setting Administrative Permissions” on page 48 for more information.

4. The system automatically reboots after installation. If, for some reason, the system is not rebooted, you will need to do so manually.

5. After the system is rebooted, install the Edition product license by entering the following command and supplying a license key at the prompt:

# /opt/VRTS/bin/vxlicinst

6. Enable the VxFS full feature license by entering:

# /opt/VRTS/bin/vxenablef -e full

You must repeat this step every time you install a new license.

24


7. You may need to initialize VERITAS Volume Manager using the vxinstall command. See “Configuring VERITAS Volume Manager” on page 55 for information on initializing VERITAS Volume Manager.

Monitoring Installation Using the Log FileYou can monitor the installation process for warnings and notes. If any errors occur halting or preventing installation, the log file /var/adm/sw/swagent.log contains this information. See the Managing HP-UX with SD-UX Guide for more information.

Installing the VERITAS Enterprise Administrator Client (Windows)

If you plan to run the VEA client from a Windows machine, install the optional Windows package after you have installed the VEA server software on the UNIX server on which the database runs.

Note If you plan to install the GUI client on Windows NT 4.0, Windows Installer must be upgraded to version 2.0. For more information about upgrading Windows Installer, visit http://www.microsoft.com. If you are using Windows NT 4.0, it is also recommended that you use Windows NT 4.0 Service Pack 6.

▼ To install the VEA client on a Windows machine

1. Insert the CD containing VERITAS Database Edition for Oracle.

2. Using Windows Explorer or a DOS Command window, go to the top level /win32 directory on CD1 and execute the VRTSobgui.msi program with Windows installer.

3. Follow the instructions presented by the VRTSobgui.msi program.

Installing the VERITAS Enterprise Administrator Client (HP-UX)

If you plan to run the VEA client from a UNIX machine, install the optional package on the client machine after you have installed the VEA server software on the UNIX server on which the database runs.

Note The VEA client may already be installed on your system as part of the September 2002 HP-UX 11i (11.11) Version 1.0 release.


http://www.microsoft.com



Verifying VERITAS Database Edition Licensing

▼ To install the VEA client on an HP-UX machine using swinstall

1. Log in as root.

2. Determine whether the VEA client is already installed:

# swlist -l product | grep VRTSobguiVRTSobgui 3.0.2.261a VERITAS Enterprise Administrator

3. Insert the CD into the CD-ROM drive and use the swinstall command:

# swinstall -s \/cdrom/database_edition_for_oracle/pkgs/VRTSobgui

Unmounting the CDAfter installing the software, unmount the CD.

▼ To unmount the CD

Use the pfs_umount command as follows:

# pfs_umount /dev/dsk/c#t#d#

where /c#t#d# is the location of the drive.

Verifying VERITAS Database Edition LicensingAfter you install VERITAS Database Edition, you can display a list of the licensed features.

▼ To display the licensed VERITAS features

Use the vxlicrep command as follows:

# /opt/VRTS/bin/vxlicrep

A list of features is displayed.

If you are upgrading from a previous version of VERITAS Database Edition and you have not purchased any new VERITAS Database Edition options, your existing license will continue to work. However, you must install VRTSvlic, the new license utility package. VRTSvlic is installed automatically if you install VERITAS Database Edition using the installDBED installation script.

26

Deinstalling VERITAS Database Edition


VERITAS Volume Manager Deinstallation ConsiderationsBefore deinstalling the VERITAS Volume Manager software, you must backup your data, move data out of VxVM control, and stop VERITAS Volume Manager.

Caution If you try to deinstall VERITAS Volume Manager without doing the following preparatory steps, you could lose data and leave your system in an uncertain state.

Preparing to Deinstall VERITAS Volume Manager

If you need to deinstall the VERITAS Volume Manager product licensed in the Edition package, you must complete the following preparations before you perform the deinstallation:

Note Because reorganizing your system in preparation for deinstalling VERITAS Volume Manager software is complicated, it is important to do a full system backup before beginning.

◆ All file systems and other applications that use volume devices must be modified to use the underlying disks or logical volumes.

◆ Any file systems that have been created since the VERITAS Volume Manager was installed must be made accessible through a disk or LVM logical volume.

◆ All data from any volumes that were created from multiple regions of , including striped or spanned volumes, must be moved onto a single disk or appropriate LVM logical volume.

◆ Any mirror copies of file systems and other databases must be removed so that only one copy remains.

◆ If any volume contains more than one plex (mirror), remove all but one plex.

To display a list of all volumes, use the command:

# vxprint -Ath

To remove a plex, use the command:

# vxplex -o rm dis plex_name



◆ If any remaining plex has more than one subdisk, consolidate those subdisks into a single subdisk. A simple way to do this is to use the commands:

# vxassist mirror volume_name layout=contig# vxplex -o rm dis plex_name

Note This operation does not work if you do not have sufficient space on another disk.

◆ Modify /etc/fstab to mount all file systems using a partition or logical volume instead of a VxVM volume. Update /etc/fstab for volumes that are not on rootdg.

Moving VxVM Volumes to LVM Disks

To remove VERITAS Volume Manager, you must move all the VxVM volumes to LVM disks. You can do this in one of the following ways:

◆ Create LVM volumes and move the data from each VxVM volume to an LVM volume one at a time. This procedure is described in this section.

◆ Back up the data from each VxVM volume, then remove the VxVM volumes and disk groups, use the vxdiskunsetup(1M) command to decommission the disks, put the disks under LVM control, create LVM logical volumes of the same size as the VxVM volumes, and restore the data from the backup.

◆ If you have raw data that is not on a file system, you can do a full backup of the raw data, then remove VxVM, then recover the backup.

▼ To move VxVM volumes onto logical volumes

1. Evacuate as many disks as possible in one of the following ways:

- Select Remove a disk from the vxdiskadm utility and follow the prompts.

- Use the vxevac script.

- Use the GUI.

Note For more information on these methods, please see the VERITAS Volume Manager Administrator’s Guide.

2. Remove the evacuated disks from VERITAS Volume Manager control using the following commands:

# vxdg rmdisk diskname# vxdisk rm devname

28


3. Decide which volume to move first. If the volume to be moved is mounted, unmount it.

If the volume is being used as a raw partition for database applications, make sure that the application is not updating the volume and that data on the volume is synchronized.

4. Create an LVM logical volume equal to the same size as the VxVM volume on the free disk space.

If there is not enough free space for the logical volume, a new disk must be added to the system for the first volume that is removed. Subsequent volumes can use the free space generated by the removal of this volume.

5. Copy the data from the volume onto the newly created LVM logical volume using a command such as the following:

# dd if=/dev/vx/dsk/logical_volume \of=/dev/logical_volume_group/logical_volume

6. Replace the entry for that volume (if present) in /etc/fstab with an entry for the newly created partition or LVM logical volume.

7. Mount the LVM logical volume, if the corresponding volume was previously mounted.

8. Remove the volume from VxVM control using the command:

# vxedit -rf rm volume

9. Remove any disks that have become free (have no subdisks defined on them) by removing volumes from VxVM control. To check if there are still some subdisks remaining on a particular disk, use the command:

# vxprint -F “%sd num” diskname

If the output is not 0, there are still some subdisks on this disk that will be removed subsequently. If the output is 0, remove the disk from VERITAS Volume Manager control as follows:

# vxdg rmdisk diskname# vxdisk rm devname

10. The free space now created can be used for copying the data in the next volume to be removed.



11. After all volumes have been successfully converted, reboot the system.

After reboot, verify that no open volumes remain with the following command:

# vxprint -Aht -e v_open

If any volumes remain open, repeat the steps listed above.

Other Considerations

If VxVM must be removed, complete the following preparations before the deinstallation:

◆ Modify all file systems and other applications using volume devices so you can use the underlying disks or logical volumes.

◆ Make file systems created since VxVM was installed accessible through a disk or LVM logical volume.

◆ Move all data from volumes created from multiple regions of storage, including striped or spanned volumes, onto a single disk or appropriate LVM logical volume.

◆ Remove all but one copy of file systems and other databases.

◆ Remove all but one plex from volumes that contain multiple plexes (mirrors).

To display a list of all volumes, use the command:

# vxprint -Ath

To remove a plex, use the command:

# vxplex -o rm dis plex_name

◆ If a remaining plex contains multiple subdisks, consolidate the subdisks into a single subdisk using the commands:

# vxassist mirror volume_name layout=contig# vxplex -o rm dis plex_name

Note Sufficient space on another disk is required for this operation to complete.

◆ Modify /etc/fstab to mount all file systems using a partition or logical volume instead of a VxVM volume. Update /etc/fstab for volumes that are not on rootdg.

30


Shutting Down VERITAS Volume Manager

Before you can remove the VERITAS Volume Manager software, you must shut down VERITAS Volume Manager.

Note If you remove VERITAS Volume Manager without first shutting down, package removal is incomplete, and your system is left in an uncertain state.

▼ To shut down VERITAS Volume Manager

Use the vxdctl and vxiod commands as follows:

# vxdctl stop# vxiod -f set 0

Deinstalling VERITAS Database Edition Using the removeDBED Script

The removeDBED script removes VERITAS Database Edition for Oracle software and reboots the system to remove the functionality from the kernel.

▼ To remove the Edition software

Use the removeDBED script as follows:

# /opt/VRTSdbed/bin/removeDBED***********************************************************Starting removal of VERITAS Database Edition for Oracle.

***********************************************************

The following packages are already installed on the system:

VRTSdbedVRTSfsdocVRTSobVRTSobguiVRTSodmVRTSordocVRTSvmdocVRTSvxmsaVRTSfsproVRTSorguiVRTSvmproVRTSvlicVRTSvxfsVRTSvxvm



Do you want to remove installed Database Edition packages? [y,n,?,q] y

WARNING: The VRTSvxfs VRTSvxvm packages will be removed.These packages force a system reboot after removing.

Enter 'y' to continue the removal of all installed packages.Enter 'n' to skip the removal of VRTSvxfs VRTSvxvm packages.Enter 'q' to exit.

Continue? [y,n,?,q] y

Removing packages ...

======= 09/24/02 09:56:03 PDT BEGIN swremove SESSION(non-interactive) (jobid=target_machine-0745)

* Session started for user "root@target_machine".

* Beginning Selection* Target connection succeeded for "target_machine:/".* Software selections:

VRTSfspro.FSPRO-PRG,l=/,r=3.5-ga08,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.5-ga08,fa=HP-UX_B.11.11_32/64

VRTSorgui.GUI_PROVIDER,l=/,r=3.5,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.5,fa=HP-UX_B.11.11_32/64

VRTSvmpro.VMPRO-PRG,l=/opt/VRTSvmpro,r=3.5m,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.5m,fa=HP-UX_B.11.11_32/64* Selection succeeded.

* Beginning Analysis* Session selections have been saved in the file"/.sw/sessions/swremove.last".* "target_machine:/": There will be no attempt to mountfilesystems that appear in the filesystem table.

* Analysis succeeded.

* Beginning Execution* The execution phase succeeded for "target_machine:/".* Execution succeeded.

32


NOTE: More information may be found in the agent logfile usingthe command "swjob -a log target_machine-0745 @target_machine:/".

===== 09/24/02 09:56:25 PDT END swremove SESSION (non-interactive)(jobid=target_machine-0745)

======= 09/24/02 09:56:25 PDT BEGIN swremove SESSION(non-interactive) (jobid=target_machine-0746)


* Beginning Selection* Target connection succeeded for "target_machine:/".

WARNING: The software specified contains a kernel fileset. It willbe necessary to reconfigure the kernel and reboot thesystem to remove the functionality from the kernel.* Software selections:

VRTSdbed.DBED,l=/,r=3.5,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.5,fa=HP-UX_B.11.11_32/64

VRTSfsdoc.VXFS-DOC,l=/,r=3.5-ga12,v=VERITAS,fr=3.5-ga12,fa=HP-UX_B.11.11_64

VRTSob.VEAS-FILESET,l=/,r=3.0.2.261a,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.0.2.261a,fa=HP-UX_B.11.11_32/64

VRTSobgui.VEA-FILESET,l=/,r=3.0.2.261a,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.0.2.261a,fa=HP-UX_B.11.11_32/64

VRTSodm.ODM-KRN,l=/,r=3.5-ga10,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.5-ga10,fa=HP-UX_B.11.11_64

VRTSodm.ODM-MAN,l=/,r=3.5-ga10,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.5-ga10,fa=HP-UX_B.11.11_32/64

VRTSodm.ODM-RUN,l=/,r=3.5-ga10,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.5-ga10,fa=HP-UX_B.11.11_32/64

VRTSordoc.ORDOC,l=/,r=3.5,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.5,fa=HP-UX_B.11.11_32/64

VRTSvlic.VLIC-RUN,l=/,r=3.00.007g,a=HP-UX_B.11.00_32/64,v=VERITAS,fr=3.00.007g,fa=HP-UX_B.11.00_32/64



VRTSvmdoc.VXVM-DOC,l=/,r=3.5m,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.5m,fa=HP-UX_B.11.11_32/64

VRTSvxfs.VXFS-ENG-A-MAN,l=/,r=3.5-ga12,a=HP-UX_B.11.11_64,v=VERITAS,fr=3.5-ga12,fa=HP-UX_B.11.11_64

VRTSvxfs.VXFS-KRN,l=/,r=3.5-ga12,a=HP-UX_B.11.11_64,v=VERITAS,fr=3.5-ga12,fa=HP-UX_B.11.11_64

VRTSvxfs.VXFS-KRN2,l=/,r=3.5-ga12,a=HP-UX_B.11.11_64,v=VERITAS,fr=3.5-ga12,fa=HP-UX_B.11.11_64

VRTSvxfs.VXFS-PRG,l=/,r=3.5-ga12,a=HP-UX_B.11.11_64,v=VERITAS,fr=3.5-ga12,fa=HP-UX_B.11.11_64

VRTSvxfs.VXFS-RUN,l=/,r=3.5-ga12,a=HP-UX_B.11.11_64,v=VERITAS,fr=3.5-ga12,fa=HP-UX_B.11.11_64

VRTSvxmsa.admin,l=/,r=2.1-REV=2002.09.17,a=HP-UX_B.11.11VRTSvxmsa.libraries,l=/,r=2.1-REV=2002.09.17,a=HP-UX_B.11.11VRTSvxmsa.logging,l=/,r=2.1-REV=2002.09.17,a=HP-UX_B.11.11VRTSvxmsa.plugins,l=/,r=2.1-REV=2002.09.17,a=HP-UX_B.11.11

VRTSvxvm.VXMS,l=/,r=3.5m,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.5m,fa=HP-UX_B.11.11_32/64

VRTSvxvm.VXVM-ENG-A-MAN,l=/,r=3.5m,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.5m,fa=HP-UX_B.11.11_32/64

VRTSvxvm.VXVM-HELP,l=/,r=3.5m,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.5m,fa=HP-UX_B.11.11_32/64

VRTSvxvm.VXVM-KRN,l=/,r=3.5m,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.5m,fa=HP-UX_B.11.11_64

VRTSvxvm.VXVM-RUN,l=/,r=3.5m,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.5m,fa=HP-UX_B.11.11_32/64

* Selection succeeded.

* Beginning Analysis* Session selections have been saved in the file"/.sw/sessions/swremove.last".* "target_machine:/": There will be no attempt to mountfilesystems that appear in the filesystem table.

* Analysis succeeded.

* Beginning Execution* The execution phase succeeded for "target_machine:/".

34


* Execution succeeded.


===== 09/24/02 09:58:59 PDT END swremove SESSION (non-interactive)(jobid=target_machine-0746)

*** FINAL System shutdown message from root@target_machine ***

System going down IMMEDIATELY



36

Upgrade Procedures
3 This chapter provides an overview of VERITAS Database Edition for Oracle upgrade tasks and describes how to upgrade VERITAS Database Edition for Oracle if one or more VERITAS products are already installed on your system.

◆ “VERITAS Volume Manager Upgrade Considerations” on page 37

◆ “Upgrading the VERITAS Database Edition Software” on page 41

◆ “VERITAS Volume Manager Root Disk Options” on page 44

The VERITAS Database Edition for Oracle software uses the swinstall utility of HP-UX. For additional information on using swinstall, see the documentation published by the Hewlett-Packard Company that accompanied your HP system.

VERITAS Volume Manager Upgrade ConsiderationsIf you are upgrading from VERITAS Database Edition 2.1.1 or earlier, you must first upgrade your operating system to the September 2002 HP-UX 11i (11.11) Version 1.0 release. Contact Hewlett-Packard for information on upgrading your operating system.

If you are running VERITAS Database Edition or a version of VERITAS Volume Manager on HP-UX 11.0, you will need to migrate your VxVM disk groups. The upgrade procedure allows you to retain your existing HP-UX 11.0 VxVM configuration. After upgrading, you can resume using VxVM on the same host with an upgraded operating system without running the vxinstall procedure.

Note The following procedure describes how to migrate VxVM disk groups between different versions of the HP-UX operating System and assumes that the VxVM disk groups being migrated are already using VxVM 3.1, not VxVM 3.0.

If you need to upgrade VxVM 3.0 disk groups to VxVM 3.1 disk groups, refer to Installing Veritas Volume Manager for HP-UX on HP-UX 11i. The manual is available at the HP documentation web site: http://www.docs.hp.com. Search using the phrase “VERITAS Volume Manager.”

37

http://www.docs.hp.com

VERITAS Volume Manager Upgrade Considerations

Migrating VxVM Disk Groups

Caution You do not need to perform these steps if you are upgrading from VERITAS Database Edition 2.1.2 or later. Only perform these steps if you are upgrading your HP-UX operating system from 11.0 to the September 2002 HP-UX 11i (11.11) Version 1.0 release.

▼ To migrate VxVM disk groups to the September 2002 HP-UX 11i (11.11) Version 1.0 release

1. Print the current VxVM configuration into a file, and then copy the file to a system that is not the VxVM server being upgraded. Use the following command to print the configuration to a file:

# vxprint -mh > /file1

2. Copy the current license key files to a system that is not the VxVM server being upgraded. The VERITAS license key files are in the /etc/vx/elm directory and have a .lic extension.

3. Print the current license key configuration into a file, then copy the file to a system that is not the VxVM server being upgraded. Use the following command to print the configuration to a file:

# vxlicense -p > /vxlicense1.out

4. Unmount all file systems mounted on VxVM volumes using the umount(1M) command or the Volume Manager Storage Administrator (VMSA) graphical user interface (GUI). For example:

# umount /vxvm_vol1# umount /vxvm_vol2

5. Copy the lines in /etc/fstab that mount the VxVM file systems into a file on a system other than the VxVM server that is being upgraded.

6. Stop VxVM using the following command:

# vxdctl stop

7. Remove VxVM, and any other VRTS products on the HP-UX 11.0 machine (such as VRTSlic, VRTSvmdoc, and VRTSvmsa), and any patch bundles (such as VRTSvxvm_310_01 or VRTSvxvm_310_02), using the swremove command:

# swremove -x autoreboot=true VRTSvxvm ...

The host will now reboot.

38


At this time, the host can be upgraded to the September 2002 HP-UX 11i (11.11) Version 1.0 release with no impact to the VxVM disk groups. After operating system is upgraded, continue with step 8 to bring the VxVM disk groups online on the HP-UX host.

8. Ensure that the HP-UX 11i host recognizes the external disk array that was being used on the HP-UX 11.0 host for VxVM disks. Use the following command to determine which disks the HP-UX 11i host recognizes:

# ioscan -fnC disk | more

If the host does not recognize the disk array that was used on HP-UX 11.0 for the VxVM disks, do not continue. The host must be able to recognize the disk array before continuing with this procedure.

9. When the system comes up, bring the system to single-user mode using the following command:

# init S

Do not run vxinstall after the system reboots.

10. When prompted, enter the password and press Return to continue.

11. Remove installation files that were created when you loaded VxVM but are no longer needed using the following command:

# rm -f /etc/vx/reconfig.d/state.d/install-db

12. After removing the installation files, start VxVM I/O daemons using the following command:

# vxiod set 10

13. Start the VxVM configuration daemon, vxconfigd, in disabled mode using the following command:

# vxconfigd -m disable

14. Initialize vxconfigd using the following command:

# vxdctl init

15. Initialize the VxVM dynamic multipathing (DMP) subsystem using the following command:

# vxdctl initdmp

Chapter 3, Upgrade Procedures 39


16. Enable vxconfigd using the following command:

# vxdctl enable

17. Put VxVM lines copied in step 5 back into /etc/fstab.

18. Start the volumes using the following command:

# vxrecover -s

19. Mount the volumes on the host using the following command:

# mountall

20. List the current VxVM configuration to a file, for example, file2.

# vxprint -hm > /file2

21. Compare file1 that was created in step 1 and file2 to ensure that all of the previously existing volumes have been found.

22. Enter the license key that was saved in the vxlicense1.out file in step 3 by using the following command:

# vxlicense -c

You are prompted to enter the license key.

23. Save the new license key configuration:

# vxlicense -p > /vxlicense2.out

24. Compare vxlicense1.out and vxlicense2.out to ensure that all the licenses have been installed.

25. Check to see that the license key files are in the /etc/vx/elm directory (see step 2).

40

Upgrading the VERITAS Database Edition Software

Upgrading the VERITAS Database Edition SoftwareBefore attempting to upgrade VERITAS Database Edition, you must manually remove the following packages:

◆ VRTSqio - VERITAS Quick I/O

◆ Any previous version(s) of VRTSvxfs

After removing these packages, reboot the system and follow the appropriate upgrade steps.

Note Any time you install or remove the VRTSqio, VRTSvxfs, and VRTSvxvm packages, you must perform a system reboot.

If you have VERITAS Volume Manager 3.1 or 3.2 installed on your system, you can choose to automatically upgrade it to VERITAS Volume Manager 3.5 when installing this release of VERITAS Database Edition.

If, however, you want to upgrade from an earlier beta release of VERITAS Database Edition 3.5 to this release, which includes VERITAS Volume Manager 3.5m, you must first remove the earlier VERITAS Volume Manager 3.5 release manually.

Upgrading from VERITAS Database Edition 2.1.1 or EarlierIf you are upgrading to VERITAS Database Edition 3.5 from VERITAS Database Edition 2.1.1, you must first upgrade your operating system to the September 2002 HP-UX 11i (11.11) Version 1.0 release.

See your Hewlett-Packard documentation for instructions on how to install or upgrade to the appropriate HP-UX version.

Caution If you are running an earlier release of VxVM, VERITAS Foundation Suite, or VERITAS Database Edition, you must remove the software packages before upgrading your system and installing the latest version of VERITAS Database Edition.

See the VERITAS or HP documentation that accompanied your product or products for upgrade and deinstallation information.

After you have upgraded your operating system to the September 2002 HP-UX 11i (11.11) Version 1.0 release, follow the installation procedures from “Installing the VERITAS Database Edition Software” on page 18.



Upgrading from VERITAS Database Edition 2.1.2

▼ To upgrade to VERITAS Database Edition 3.5 from VERITAS Database Edition 2.1.2 using the removeDBED script

1. Make sure your system is backed up completely before upgrading to VERITAS Database Edition 3.5.

2. Remove the VERITAS Database Edition software using the remove script.

# /usr/sbin/removeDBED

Note See “Deinstalling VERITAS Database Edition” on page 27 for more information

3. Reboot the system.

4. Follow the installation procedures from “Installing the VERITAS Database Edition Software” on page 18.

▼ To upgrade to VERITAS Database Edition 3.5 from VERITAS Database Edition 2.1.2 using swremove

1. Make sure your system is backed up completely before upgrading to VERITAS Database Edition 3.5.

2. Remove the VERITAS Database Edition software packages and HP VERITAS Volume Manager using the swremove command.

# swremove -x mount_all_filesystems=false -x autoreboot=true \VRTSqio VRTSdbed VRTSordoc VRTSlic

Note This step automatically reboots the system.

3. Follow the installation procedures from “Installing the VERITAS Database Edition Software” on page 18.

42


Upgrading the Disk Group Version SeparatelyYou may need to manually upgrade a disk group version to 90. You will need to upgrade the disk group version separately if:

◆ You plan to implement VERITAS Database FlashSnap or VERITAS FastResync.

◆ If you import a disk group from a version of VxVM earlier than 3.2.

Note You cannot return to an older disk group version once you have upgraded.

▼ To determine the disk group version you are using

Use the vxdg list command as follows:

# vxdg -q list diskgroup | grep version

where the -q option means no header is printed describing output fields.

Example

To determine the disk group version on PRODdg:

# vxdg -q list PRODdg | grep versionversion: 90

▼ To upgrade the disk group version you are using

Use the vxdg upgrade command as follows:

# vxdg -T diskgroup_version upgrade diskgroup

where the -T option means upgrading the disk group to a specific version.

Example

To upgrade the disk group to version 90 on PRODdg:

# vxdg -T 90 upgrade PRODdg


VERITAS Volume Manager Root Disk Options

VERITAS Volume Manager Root Disk OptionsWith the release of VxVM 3.5, you have the option of placing your root disk under VxVM control. If you are performing a fresh installation of the September 2002 HP-UX 11i (11.11) Version 1.0 release, meaning that you were not running a prior release, you can convert your root disk using Ignite-UX. However, if you are a current HP-UX user, and you are performing an upgrade from a prior release of HP-UX, or if you are a current HP-UX user running a prior release of VxVM, you cannot invoke Ignite-UX to convert your system to be VxVM rootable. You must use the following procedure to achieve VxVM rootability by cloning your LVM root disk using the vxcp_lvmroot(1M) command.

Upgrading to a VxVM Root DiskUse the following procedure to upgrade your current LVM root disk to VxVM by cloning your LVM root disk using the vxcp_lvmroot(1M) command.

▼ To upgrade to a VxVM root disk

1. Upgrade your system to the September 2002 HP-UX 11i (11.11) Version 1.0 release, if your current version of HP-UX or VxVM is not already at this level.

2. Select the disk to be used as your new VxVM root disk. It is recommended that you use a disk physically located on the server. If this is currently an LVM disk, then it must be removed from LVM control. If you have two spare disks, and you want to set up a mirrored root disk, make sure that the second disk is also free from LVM control.

3. While booted on the your LVM root disk, invoke the vxcp_lvmroot command to clone the LVM root disk to the disk(s) you have designated to be the new VxVM root disk(s). In the following examples, c1t0d0 and c2t0d0 are used for the target VxVM root disk and the (optional) root mirror.

# /etc/vx/bin/vxcp_lvmroot -v c1t0d0

or, for a mirrored root:

# /etc/vx/bin/vxcp_lvmroot -v -m c2t0d0 c1t0d0

The -v option is highly recommended. The cloning of the root disk is a lengthy operation, and the -v option gives a time-stamped progress indication as each volume is copied, and other major events.

Note The vxcp_lvmroot command checks the OS level and will not proceed unless the OS level is at the September 2002 HP-UX 11i (11.11) Version 1.0 release.

44


4. You can use the setboot(1M) command to save the hardware path of the new VxVM root disk in the system NVRAM. The disk hardware paths can be found using the command:

# ioscan -kfnC disk

5. Reboot from your new VxVM root disk. If you created a mirrored root disk, then there is nothing more to do. The LVM root disk can now safely co-exist with your VxVM root disk, giving you an emergency backup boot target.

6. Optionally, you can convert your original LVM root disk into a mirror of your VxVM root disk using the following commands:

# /etc/vx/bin/vxdestroy_lvmroot -v c2t0d0# /etc/vx/bin/vxrootmir -v c2t0d0

Once this operation is complete, you will be running on a completely mirrored VxVM root disk.

7. If you later choose to return to an LVM root, you can use the vxres_lvmroot(1M) command to restore the LVM root disk.



46

Configuring the VERITAS Software
4 This chapter covers important details about initializing (where required), setting up, and verifying the VERITAS software licensed with the VERITAS Database Edition for Oracle.
Topics covered in this document include:

◆ “Configuring VERITAS Database Edition” on page 48

◆ “Configuring VERITAS File System” on page 53

◆ “Configuring VERITAS Volume Manager” on page 55

◆ “Verifying the VERITAS Database Edition Installation” on page 64

Database Configuration ConsiderationsMost relational database management system (RDBMS) software requires operating system parameters to be set prior to operation. The Oracle database requires modifications to kernel settings in the /stand/system file before the database will run correctly. The most critical settings are normally located in the Shared Memory and Semaphore settings HP-UX. For precise settings, consult your current Oracle installation and configuration documentation.

The following list is an example of the changes that need to be made to the /stand/system file for Oracle, follow by a kernel rebuild and a reboot, (a kernel rebuild may or may not be necessary, depending on the parameters being changed) so you can use your database:

semmni 2048semmns 2048shmmax 0X120000000shmmni 800shmseg 120

47

Configuring VERITAS Database Edition

Configuring VERITAS Database EditionOnce you install and initialize all of the VERITAS software, you can take advantage of the various storage management features to ease the task of system and database administration. For detailed information on how to use the VERITAS products in a Oracle database environment, see the VERITAS Database Edition for Oracle Database Administrator’s Guide

The VxDBA utility is a menu-driven application that allows you to perform administrative tasks for Oracle database management. You can also perform the same administrative tasks using the VERITAS Database Edition graphical user interface (GUI).

Setting Administrative PermissionsThe VxDBA utility and the VERITAS Database Edition GUI require permission changes to allow for database administrators to access these tools. The default settings at installation time for the /opt/VRTSdbed directory allows only the root login to access the directory. You are asked during the installation process if you want to allow database administrators access to the VxDBA utility. If you did not make the permission changes to allow database administrator access to the /opt/VRTSdbed directory during installation, you can do so at a later time.

▼ To allow the user “oracle” access to the VxDBA utility and the VERITAS Database Edition GUI

Use the chown and chmod commands, as follows:

# chown oracle /opt/VRTSdbed# chmod 500 /opt/VRTSdbed

▼ To allow users in the group “dba” access to the VxDBA utility and the VERITAS Database Edition GUI

Use the chgrp and chmod commands, as follows:

# chgrp dba /opt/VRTSdbed# chmod 550 /opt/VRTSdbed



Setting Up VERITAS Enterprise AdministratorVERITAS Database Edition must be installed and run on a UNIX (HP-UX) machine. The VERITAS Enterprise Administrator (VEA) client can be installed and run on any HP-UX, Windows NT, Windows Me, Windows 2000, or Windows 98 machine that supports the Java Runtime Environment.

The following are system recommendations for VERITAS Enterprise Administrator:

Starting VERITAS Enterprise Administrator Server

If you included the VEA server packages when installing VERITAS Database Edition, the VEA server (VRTSob) is started automatically. However, you may need to start the server manually if it gets shut down.

▼ To manually start VERITAS Enterprise Administrator server

1. Verify the status of the VEA server:

# /opt/VRTSob/bin/vxsvc -mCurrent state of server : NOT RUNNING

2. Start the VEA server:

# /opt/VRTSob/bin/vxsvc# DBED: Initiallizing Database Edition Provider 3.5DBED: Initialization successful. Interface:{1a510152-1dd2-11b2-902c-080020cf51fc}

3. Verify the status of the VEA server again:

# /opt/VRTSob/bin/vxsvc -mCurrent state of server : RUNNING

Note Please note that if the Oracle database is down when VERITAS Enterprise Administrator server (vxsvc) starts, and is then brought back up while the GUI is running, the GUI will display the database as down until you do the following:

Select Actions > Rescan from the GUI menu.

HP-UX HP-UX 11.11 9000/* (64-bit)

Windows NT, Me, 2000, or 98

300MHz Pentium with 256MB memory

Chapter 4, Configuring the VERITAS Software 49


Shutting Down VERITAS Enterprise Administrator Server

Although the VEA server should remain running, you may need to shut it down manually.

▼ To manually shut down VERITAS Enterprise Administrator server

1. Verify the status of the VEA server:

# /opt/VRTSob/bin/vxsvc -mCurrent state of server : RUNNING

2. Stop the VEA server:

# /opt/VRTSob/bin/vxsvc -kRequest is in process...Server is shutting down.DBED: Successfully unloaded the Database Edition Provider 3.5.Server was shutdown sucessfully.

3. Again verify the status of the VEA server:

# /opt/VRTSob/bin/vxsvc -mCurrent state of server : NOT RUNNING

Starting the VERITAS Enterprise Administrator ClientOnly users with appropriate privileges can run VEA. VEA can administer the local machine or a remote machine. However, VERITAS Volume Manager and the VEA server must be installed on the machine to be administered. The VERITAS Volume Manager vxconfigd daemon and the VEA server must be running on the machine to be administered.

After you have installed the appropriate VERITAS packages, and VEA is running on the server, you can start the VEA client.

UNIX (HP-UX)

▼ To administer the local UNIX machine

Use the following command:

# /opt/VRTSob/bin/vea



▼ To administer a remote UNIX machine

Use the following command:

# /opt/VRTSob/bin/vea remote_machine_name

Windows

▼ To administer a remote UNIX machine

Select Start > Programs > VERITAS Enterprise Administrator.

Adding Users to the VERITAS Enterprise Administrator Server Console Registry

You may want to add users to the VEA server console registry to allow access to the interface to users other than root.

▼ To add users other than root to the VERITAS Enterprise Administrator server console registry

1. Make sure that the optional VERITAS Database Edition GUI package was installed.

# swlist -l product | grep VRTSorguiVRTSorgui 3.5 VERITAS Database Edition Graphical User

2. Use the vxdbedusr command to add a group or user.

# /opt/VRTSorgui/bin/vxdbedusr -a <user or group> \<user_name or group_name>

where -a adds a user or user group to the registry.

For example, to add “oracle” as a user, enter the following:

# vxdbedusr -a user oracle

The following output appears:

Successfully added 'oracle' into registry

/opt/VRTSob/bin/vxsvc is still running. You need to shutdown and re-start /opt/VRTSob/bin/vxsvc to refresh the changes.

Shutdown and re-start /opt/VRTSob/bin/vxsvc now ...[y,n,q,?] (default: y)

3. Enter Y or press Return to shut down and restart.



Removing Users from the VERITAS Enterprise Administrator Server Console Registry

You may need to restrict access to the VEA server console registry. You can remove users or user groups from the registry if they have been previously added.

Note You cannot remove root from the VEA server console registry.

▼ To remove users other than root from the VERITAS Enterprise Administrator server console registry

1. Make sure that the optional VERITAS Database Edition GUI package was installed.

# swlist -l product | grep VRTSorguiVRTSorgui 3.5 VERITAS Database Edition Graphical User

2. Use the vxdbedusr command to remove a group or user.

# /opt/VRTSorgui/bin/vxdbedusr -r <user or group> \<user_name or group_name>

where -r removes a user or user group from the registry.

For example, to remove the user “oracle,” enter the following:

# /opt/VRTSorgui/bin/vxdbedusr -r user oracle

The following output appears:

Successfully removed 'oracle' from registry

/opt/VRTSob/bin/vxsvc is still running. You need to shutdown and re-start /opt/VRTSob/bin/vxsvc to refresh the changes.

Shutdown and re-start /opt/VRTSob/bin/vxsvc now ...[y,n,q,?] (default: y)

3. Enter Y or press Return to shut down and restart.


Configuring VERITAS File System

vxtunefs Command Permissions and Cached Quick I/OBy default, you must have superuser (root) privileges to use the /opt/VRTS/bin/vxtunefs command. The vxtunefs command is a tool that lets you change caching policies to enable Cached Quick I/O and change other file system options. Database administrators can be granted permission to change default file system behavior in order to enable and disable Cached Quick I/O. The system administrator must change the vxtunefs executable permissions as follows:

# chown root:dba /opt/VRTS/bin/vxtunefs# chmod 4550 /opt/VRTS/bin/vxtunefs

Note Setting the permissions for /opt/VRTS/bin/vxtunefs to 4550 allows all users in the dba group to use the vxtunefs command to modify caching behavior for Quick I/O files.

Configuring VERITAS File SystemAfter licensing VxFS, you can create a VERITAS File System on a disk or a volume with the mkfs command. Before you can use a file system, you must mount it with the mount command. You can unmount the file system later with the umount command. A file system can be automatically mounted at system boot time if you add an entry for it in the /etc/fstab file.

The VERITAS-specific commands are described in the VxFS guides and online manual pages. See Appendix A, “VERITAS File System Quick Reference,” in the VERITAS File System Administrator’s Guide for examples of the most common VxFS operating procedures.

VERITAS File System does not require initialization.

If you need to upgrade a disk layout, see “Upgrading the VxFS Disk Layout” on page 53 for more information.

Upgrading the VxFS Disk LayoutIn the Version 4 disk layout, VxFS introduced a new inode block map organization for indirect extents known as typed extents. Each entry in the block map has a typed descriptor record containing a type, offset, starting block, and number of blocks. For more information, see the VERITAS File System Administrator’s Guide.


Configuring VERITAS File System

The default disk layout for VxFS is Version 4. VxFS 3.5 supports the following disk layouts:

◆ Version 2 file system disk layout (with quotas or without quotas)

◆ Version 3 file system disk layout

◆ Version 4 file system disk layout

Note You can mount Version 2 and 3 disk layouts; however, all file systems are created with Version 4 disk layout.

This release is the last to support the VxFS Version 2 and Version 3 disk layouts. You can still mount these older disk layout versions, however, you cannot create them using the VERITAS mkfs command. You should begin upgrading any Version 2 or Version 3 disk layout file systems to Version 4 for them to be usable on future releases of VxFS.

▼ To determine the file system layout

Use the fstyp command as follows:

# fstyp -v device

The output from the fstyp command shows something similar to the following:

vxfsversion: 4f-bsize: 1024f_blocks: 592444...

In the above example output, “version 4” means Version 4 file system disk layout.

▼ To upgrade a file system to disk layout Version 4 while the file system is online

Use the vxupgrade command as follows:

# vxupgrade -n 4 /mount_point

See the vxupgrade(1M) and fsadm(1M) manual pages for more information on upgrading VxFS file systems.

Note To use the Storage Checkpoint, Storage Rollback, cluster file system, and BLI Backup features, the database must be on VxFS file systems using a Version 4 disk layout.


Configuring VERITAS Volume Manager

Configuring VERITAS Volume ManagerAfter you have completed the package installation, and before using the VERITAS Volume Manager software, you must initialize VERITAS Volume Manager using the vxinstall command. This section describes how to initialize VERITAS Volume Manager using vxinstall.

After installing and initializing VxVM, you use the VxVM commands to manage your online disk storage. VERITAS Volume Manager commands are described in the VERITAS Volume Manager documentation set and online manual pages. See the VERITAS Volume Manager Administrator’s Guide for examples of the most common VxVM operating procedures.

You must have superuser (root) privileges to initialize and install VERITAS Volume Manager.

vxinstall places all specified disks under VERITAS Volume Manager control. These disks are automatically placed in the default disk group, rootdg. To place some of your disks in another disk group, use vxinstall to initialize at least one disk into rootdg and then use the GUI or the vxdiskadm program to place additional disks in other disk groups. See the VERITAS Volume Manager documentation set for information on how to create other disk groups for your disks.

Disks that are not initially placed under VERITAS Volume Manager control by the vxinstall command can be added later using the GUI or the vxdiskadm command. However, you must place at least one disk under VERITAS Volume Manager control with vxinstall before you can add disks using other utilities or interfaces.

Note At least one disk must remain in rootdg at all times while VxVM is running.

Note You only need to run vxinstall once. If you are upgrading from a previous version of VERITAS Volume Manager, then do not run vxinstall again.

▼ To initialize VERITAS Volume Manager

1. Log in as root.

2. Identify controllers, disks, and enclosures to exclude from being configured as VxVM devices by the vxinstall and vxdiskadm utilities. If there are no devices to exclude, continue to Step 4.

3. To exclude one or more disks from VERITAS Volume Manager control, create or edit the /etc/vx/disks.exclude file and add the names of those disks to the file.



The vxinstall command ignores any disks listed in this file and leaves them untouched. The following is an example of the contents of the disks.exclude file:

c0t1d0

Similarly, you can exclude all disks on certain controllers. Create or edit the /etc/vx/cntrls.exclude file and add the name of the controller. The following is an example of the contents of the cntrls.exclude file:

c0c1

Similarly, you can exclude all disks in specific enclosures. Create or edit the /etc/vx/enclr.exclude file and add the name of the enclosures. The following is an example of the contents of the enclr.exclude file:

enc2enc3

4. (Optional) To exclude disks that are being used by LVM volumes, add all disks in the volume group to the /etc/vx/disks.exclude file.

# for i in ‘vgdisplay -v uservg | egrep dsk | awk ’{print $3}’‘# do# basename $i# done

5. After you have excluded any controllers, disks, or enclosures, run vxinstall.

# vxinstall

The vxinstall program examines all controllers attached to the system and lists them. You are asked if you want to use enclosure-based naming.

6. If you do not want to use enclosure-based naming, enter n and proceed to step 8.

If you want to use enclosure-based naming, enter y. vxinstall detects and displays a list of disk arays connected to your system.

Enter y to assign a new name to the enclosures. This helps to identify their physical locations. Enclosure names cannot exceed 25 characters in length. Enter the name of the enclosure that you want to rename, and then enter its new name.

7. Enter y at the following prompt to rename more enclosures or n to continue with the installation.

Do you wish to rename more enclosures ? [y,n,q,?] (default: n) n



8. If you selected n in the previous step, vxinstall displays a brief introduction to the initialization process. Press return to continue.

The following menu is displayed:

1 Quick Installation 2 Custom Installation3 Prevent multipathing/Suppress devices from VxVM’s view

? Display help about menu ?? Display help about menuing system q Exit from menus

Select an operation to perform:

- 1 Quick Installation uses default options for installation.

- 2 Custom Installation allows you to control whether and how each disk will be brought under VERITAS Volume Manager control.

- 3 Prevent multipathing/Suppress devices from VxVM’s view excludes devices from VERITAS Volume Manager control or prevents them from being multipathed by DMP.

- ? displays a help file describing the current operation or menu choices.

- ?? displays general information about using the vxinstall program.

- q exits from the current operation, or from the vxinstall program.

9. Select either 1 for Quick Installation, 2 for Custom Installation, or 3 for Prevent multipathing/Suppress devices from VxVM’s view.

“Quick Installation” uses default options and brings every disk on your system under VxVM control, except for disks under LVM control (including your root/boot disk) and disks listed in the exclude files. If you choose “Quick Installation,” go to “Quick Installation” on page 58.

“Custom Installation” lets you control whether and how each disk will be brought under VxVM control. If you choose “Customer Installation,” go to “Custom Installation” on page 59.

“Prevent multipathing/Suppress devices from VxVM’s view” lets you exclude a device that is under VxVM or dynamic multipathing control. If you choose “Prevent multipathing/Suppress devices from VxVM’s view,” go to “Preventing Multipathing/Suppressing Devices from VxVM’s View” on page 62.



Quick InstallationThe Quick Installation option is the easiest to use. For each controller, Quick Installation gives you the option of initializing all disks. If you only want to initialize some disks on a given controller, use Custom Installation instead. (See “Custom Installation” on page 59.)

Quick Installation lets you initialize disks in a disk array, even if valid data exist on those disks. Avoid selecting the initialize option for any disks that contain valid data.

Quick Installation brings every disk attached to your system under VERITAS Volume Manager control, unless you have chosen to exclude those disks. Disks could be chosen for exclusion either through, or by using the interface for suppressing devices as described earlier. If you have any disks on your system that you do not want placed under VxVM control, either exclude them using the /etc/vx/disks.exclude, /etc/vx/ntrls.exclude, or /etc/vx/enclr.exclude files, the option “Prevent multipathing/Suppress devices from VxVM’s view” in vxinstall, or the Custom Installation option (which allows you to leave certain disks alone).

▼ To use the Quick Installation option

1. If you have not already done so, select 1 for Quick Installation from the vxinstall main menu.

Note vxinstall shows default responses in parentheses; to choose the default, press Return. You can quit the initialization at any time by typing q at any of the vxinstall prompts. Disks are initialized at the end of the vxinstall procedure. If you quit vxinstall before it initializes the disks, all disks are left as they were before vxinstall was started.

2. vxinstall prompts for each disk array and asks you how to handle the disks contained in that disk array. vxinstall begins this process for each disk array by identifying the disk array and generating a list of its disks.

If any disks are listed in the /etc/vx/dsks.exclude, /etc/vx/cntrls.exclude, or /etc/vx/enclr.exclude files, they are listed here separately as excluded disks.

Caution Initializing a disk destroys all data on that disk.

Press return to continue.

3. You are then asked if you want to initialize all of the disks on the disk array.

- Enter y to have vxinstall automatically assign and list default disk names for each disk.



- Enter n to have vxinstall prompt you for a disk name for each disk on the disk array individually. For each disk, respond with the desired disk name and press return.

4. Indicate whether you want default disk names to be assigned to all of the disks on the disk array.

- If you enter y, vxinstall automatically assigns and lists default disk names for each disk.

- If you enter n, vxinstall prompts you for a disk name for each disk on the disk array individually.

5. If you selected n in the previous step, respond with the desired disk name for each disk and press return.

6. When all of the disks on the current disk array have been named, press return and repeat steps 4 and 5 for the remaining controllers on your system.

After you have finished naming all of your disks for each disk array, a summary of your choices is displayed.

Caution This is your last chance to review and alter your choices.

- Enter y to continue with initialization.

- Enter n to revise your choices.

Depending on your input during initialization, you may be requested to shut down and reboot your machine. If this happens, shut down and reboot immediately or at your earliest convenience.

Custom Installation Custom Installation lets you control which disks are added to VxVM control and how they are added. This is important if you do not want all of your disks under VxVM control. Custom Installation also gives you the option of initializing all disks or some disks on a controller.

Note the following disk initialization issues with Custom Installation:

◆ Custom Installation does not allow you to initialize disks on an controller if LVM logical volumes are found on those disks. Avoid selecting the initialize option for any disks containing valid data.

◆ Custom Installation allows you to initialize disks in a disk array, even if valid data exists on those disks. Avoid selecting the initialize option for any disks that contain valid data.



▼ To use the Custom Installation option

1. If you have not already done so, select 2 for Custom Installation from the vxinstall main menu.


2. vxinstall asks you how to handle the disks contained on each disk array. vxinstall begins this process for each disk array by identifying the controller and generating a list of its disks.

Note If any disks are listed in the /etc/vx/disks.exclude, /etc/vx/cntrls.exclude or /etc/vx/enclr.exclude files, they are listed here separately as excluded disks.

3. Press return to continue. The following menu is displayed.

Installation options for enclosure enc0 Menu: VolumeManager/Install/Custom/enc0 1 Install all disks as new disks. (discards data on disks!) 2 Install one disk at a time. 3 Leave these disks alone. ? Display help about menu ?? Display help about the menuing system q Exit from menus


Caution Choosing option 1 to initialize all disks on the controller can result in loss of data. If you choose option 1, all disks on the controller are reinitialized: this destroys all data and partitions on each disk and each disk makes it available as free space for allocating new volumes or mirrors of existing volumes. If you are running the vxinstall program on new disks that have never been placed under VERTAS Volume Manager control before, choose this option.



4. Indicate how you want the disks on the disk array to be handled.

❖ To initialize all disks in the disk array, select 1.

Caution Initializing a disk destroys all data on the disk.

All disks in the disk array are initialized. this destroys all data and partitions on each disk and makes the disk available as free space for allocating new volumes, or mirrors of existing volumes.

Indicate whether you want default disk names to be assigned to all of the disks in the disk array.

- If you enter y, vxinstall automatically assigns and lists default disk names for each disk.

- If you enter n, vxinstall prompts you for a disk name for each disk on the controller.

For each disk, enter the desired disk name and press return.

When all of the disks in the current disk array have been named, press return to move on to the next disk array.

❖ To install one disk at a time, select 2.

Each disk is handled separately and you are prompted for information on a per-disk basis. This allows you to install a disk as a pre-existing disk, install it as a new disk, or leave it alone.

At the prompt, indicate how you want the disk to be handled.

Options 1 and 2 let you initialize the disk or to omit it from installation.

Repeat this step for all disks on the current disk array.

When all of the disks on the current disk array have been named, press return to move on to the next disk array.

❖ To leave all disks in the disk array unaltered, select 3.

No changes are made to the disks and they are not placed under VxVM control. If applications are currently using these disks and you do not want to upgrade these applications to use VxVM, use this option to ensure that your applications continue to use the disks without modification.

5. Repeat step 4 on page 61 for each remaining disk array on your system.



6. After you have finished naming all of your disks for each disk array, a summary of your choices is displayed.

Caution This is your last chance to review and alter your choices.

- Enter y to continue with initialization.

- Enter n to revise your choices.

Depending on your input during initialization, you may be requested to shut down and reboot your machine. If this happens, shut down and reboot immediately or at your earliest convenience.

Preventing Multipathing/Suppressing Devices from VxVM’s View

1. If you have not already done so, select 3 for Preventing Multipathing from the vxinstall main menu.


2. Press return to continue. The following menu is displayed.

Volume Manager Device OperationsMenu: VolumeManager/Install/Exclude Devices

1 Suppress all paths through a controller from VxVM’s view 2 Suppress a path from VxVM’s view 3 Suppress disks from VxVM’s view by specifying a VID:PID

combination 4 Suppress all but one path to a disk 5 Prevent multipathing of all disks on a controller by VxVM 6 Prevent multipathing of a disk by VxVM 7 Prevent multipathing of disks by specifying a VID:PID

combination 8 List currently suppressed/non-multipathed devices ? Display help about menu ?? Display help about the menuing system q Exit from menus




The following list briefly summarizes each operation. Additional explanatory information about each operation is displayed when you enter a choice, and you are always given the opportunity to exit from the menu before executing the choice.

- Option 1 prevents VxVM from using all paths through a specified controller. The specified controller is disabled.

- Option 2 prevents VxVM from using one or more specified paths. The specified path is excluded from VxVM control

- Option 3 prevents VxVM from using one or more disks specified by a VID:PID combination, where VID stands for a Vendor ID, and PID stands for Product ID. (The command /etc/vx/diag.d/vxdmping can be used to obtain these IDs. This command displays the standard SCSI inquiry data returned from the disk controller.)

For example, the VID:PID combination for an ACME Z1 disk array would be specified as ACME:Z1.

- Option 4 prevents VxVM from defining a set of paths, or pathgroup, for disks that are not multipathed by VxVM. (A pathgroup specifies a set of paths that VxVM should recognize as a single path. Only one path is made visible from a pathgroup.)

- Option 5 excludes devices by preventing VxVM from applying dynamic multipathing (DMP) to all disks on a controller. The controller you name is excluded from DMP control.

- Option 6 excludes a specified path from dynamic multipathing. For the path you specify, the corresponding disks are claimed in the OTHER_DISKS category and are not multipathed.

- Option 7 excludes devices by preventing VxVM from applying dynamic multipathing to disks specified by a VID:PID combination. All disks returning a VID:PID combination are claimed in the OTHER_DISKS category and are not multipathed.

- Option 8 lists devices that have either been suppressed from the view of VxVM, or that have been excluded from dynamic multipathing.

Note If you select any one of options 1 through 7, you must reboot the system for Device Exclusion to take effect, and then re-run vxinstall.


Verifying the VERITAS Database Edition Installation

Verifying VxVM InitializationAfter VERITAS Volume Manager has been successfully initialized, you can verify that the VxVM processes are running.

▼ To confirm that key VxVM processes are running

Use the ps command as follows:

# ps -ef | grep vx

The output should include the following VxVM processes:

◆ vxiod

◆ vxnotify

◆ vxrelocd

◆ vxconfigd

Verifying the VERITAS Database Edition InstallationTo verify the VERITAS Database Edition installation, you can look at the VERITAS File System kernel component and administrative utilities.

▼ To verify the VERITAS Database Edition installation

1. Use the lsdev command as follows:

# lsdev -d fddCharacter Block Driver Class15 0 fdd pseudo

The fdd driver is used by the Quick I/O and Oracle Disk Manager features.

2. Verify that the modules loaded by entering:

# ps -ef | egrep "vx|odm|vxfs|fdd"root 704 1 0 Sep 29 ? 0:00 /sbin/sh - /etc/vx/bin/vxrelocd rootroot 37 0 0 Sep 28 ? 33:35 vxfsdroot 73 0 0 Sep 28 ? 0:07 vxiodroot 299 1 0 Sep 29 ? 0:03 /usr/sbin/vxconfigd -k -m enableroot 726 704 0 Sep 29 ? 0:00 vxnotify -f -w 15root 608 0 0 Sep 29 console 0:00 vxodmdroot 709 705 0 Sep 29 ? 0:00 vxnotifyroot 1436 1 0 Sep 29 ? 0:00 /usr/sbin/fddi4subagtroot 19701 19621 1 17:14:46 pts/tc 0:00 egrep vx|odm|vxfs|fdd



Note If the file system module is not loaded, this indicates you are replacing an existing kernel component with another one having the same name and links. Reboot the system, using a command such as shutdown, to complete the process.

Use the swlist command to verify that the VERITAS Database Edition for Oracle packages are installed:

# swlist | egrep "VRTS|VERITAS”

Note Use this example for reference only—the output for each operating system version and installation environment differs slightly.

If you installed all the packages available on the VERITAS Storage Solutions 3.5 for HP-UX CD, the output for the swlist command shows the following packages:

VRTSdbed 3.5 VERITAS Database Edition UtilitiesVRTSfsdoc 3.5-ga12 VERITAS File System DocumentationVRTSfspro 3.5-ga08 VERITAS File System Management

ServicesVRTSob 3.0.2.261a VERITAS Enterprise Administrator

ServiceVRTSobgui 3.0.2.261a VERITAS Enterprise AdministratorVRTSodm 3.5-ga10 VERITAS Oracle Disk ManagerVRTSordoc 3.5 VERITAS Database Edition for Oracle

DocumentationVRTSorgui 3.5 VERITAS Database Edition Graphical

User InterfaceVRTSvlic 3.00.007g VERITAS License UtilitiesVRTSvmdoc 3.5m VERITAS Volume Manager DocumentationVRTSvmpro 3.5m VERITAS Volume Manager Management

Services ProviderVRTSvxfs 3.5-ga12 VERITAS File System with CFS SupportVRTSvxmsa 2.1-REV=2002.09.17 VxMS Application Deployment PackageVRTSvxvm 3.5m Base VERITAS Volume Manager 3.5 for

HP-UX


Installation Sample Output
A This appendix provides a sample of the output from an installation of the VERITAS Database Edition for Oracle.

Sample Installation OutputThe following output is an example of a VERITAS Database Edition installation on a September 2002 HP-UX 11i (11.11) Version 1.0 release.

# cd /cdrom/database_edition_for_oracle# ./installDBED *****************************************************************Starting installation of VERITAS Database Edition for Oracle.*****************************************************************

The following packages need to be installed for VERITAS DatabaseEdition for Oracle.

VRTSdbed is RequiredVRTSvlic is RequiredVRTSvxfs is RequiredVRTSvxvm is RequiredVRTSodm is RequiredVRTSob is OptionalVRTSobgui is OptionalVRTSorgui is OptionalVRTSvmpro is OptionalVRTSfspro is OptionalVRTSordoc is OptionalVRTSvmdoc is OptionalVRTSfsdoc is OptionalVRTSvxmsa is Optional

67

Sample Installation Output


Installing VRTSdbed VRTSvlic.

======= 09/24/02 01:16:35 PDT BEGIN swinstall SESSION(non-interactive) (jobid=target_machine-0742)


* Beginning Selection* Target connection succeeded for "target_machine:/".* Source connection succeeded for"target_machine:/tmp/dbed_oracle_3_5_hpux/./pkgs".

* Source: /tmp/dbed_oracle_3_5_hpux/./pkgs* Targets: target_machine:/* Software selections:

VRTSdbed.DBED,r=3.5,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.5,fa=HP-UX_B.11.11_32/64

VRTSvlic.VLIC-RUN,r=3.00.007g,a=HP-UX_B.11.00_32/64,v=VERITAS,fr=3.00.007g,fa=HP-UX_B.11.00_32/64

* Selection succeeded.

* Beginning Analysis and Execution* Session selections have been saved in the file"/.sw/sessions/swinstall.last".

* "target_machine:/": There will be no attempt to mountfilesystems that appear in the filesystem table.

* The execution phase succeeded for "target_machine:/".* Analysis and Execution succeeded.


==== 09/24/02 01:17:02 PDT END swinstall SESSION (non-interactive)(jobid=target_machine-0742)

Press <Return> to continue ...

**** Permission Granting for VxDBA Utility ****The VxDBA utility for database administration requires permissionchanges to allow database administrators (DBAs) access to the tools. The default settings at installation time for the/opt/VRTSdbed directory allows only the root user access to the



directory. Would you like to change permissions to allow a DBA ora group of DBAs access to the VxDBA tools?

Add single user access? [y,n,?,q] yEnter the login name of the DBA: oracle

Add group access? [y,n,?,q] yEnter group name for DBA users: dba

You do not have a Database Edition license installed.

Do you want to add a license key for this product? [y,n,?,q] y

VERITAS License Manager vxlicinst utility version 3.00.007Copyright (C) VERITAS Software Corp 2002. All Rights reserved.

Enter your license key : 1234-1234-1234-1234-1234-123

License key successfully installed for VERITAS Database Edition forOracleLicense key successfully installed for VERITAS File SystemLicense key successfully installed for VERITAS Volume ManagerLicense key successfully installed for VERITAS Mapping Services

Checking existing package installation ...

The version of VRTSdbed currently installed is up-to-date - skipping


The version of VRTSvlic currently installed is up-to-date - skipping


Installing packages ...

VRTSob.VEAS-FILESET 3.0.2.261a VERITAS Enterprise AdministratorService Fileset

You have the FlashSnap license. If you want to use the DatabaseFlashSnap feature you need to install VRTSob. Do you want to installit? [y,n,?,q] y

VRTSobgui.VEA-FILESET 3.0.2.261a VERITAS Enterprise AdministratorFileset

This package is optional. Install? [y,n,?,q] y

Appendix A, Installation Sample Output 69


VRTSorgui.GUI_PROVIDER3.5 Database Edition Graphical UserInterface


VRTSvmpro.VMPRO-PRG 3.5m VERITAS Volume Manager ManagementServices Provider

You have the FlashSnap license. If you want to use the DatabaseFlashSnap feature you need to install VRTSvmpro. Do you want toinstall it? [y,n,?,q] y

VRTSfspro.FSPRO-PRG 3.5-ga08 VERITAS File System ManagementServices Provider


VRTSordoc.ORDOC 3.5 VERITAS Database Edition forOracle Documentation


VRTSvmdoc.VXVM-DOC 3.5m VERITAS Volume ManagerDocumentation


VRTSfsdoc.VXFS-DOC 3.5-ga12 VERITAS File SystemDocumentation


VRTSvxmsa.admin VERITAS Federated MappingService

VRTSvxmsa.libraries VxMS libraries VRTSvxmsa.logging VxMS logging VRTSvxmsa.plugins VxMS plugins

You have the Storage Mapping license. If you want to use the OracleFile Mapping feature you need to install VRTSvxmsa.Do you want to install it? [y,n,?,q] y

The VRTSvxfs VRTSvxvm packages will be installed as part of thecomplete VERITAS Database Edition for Oracle suite. These packagesforce a system reboot after installation.




======= 09/24/02 01:18:36 PDT BEGIN swinstall SESSION(non-interactive) (jobid=target_machine-0743)


* Beginning Selection* Target connection succeeded for "target_machine:/".* Source connection succeeded for"target_machine:/tmp/dbed_oracle_3_5_hpux/./pkgs".

NOTE: The software "VRTSvxfs" was successfully marked, but it depends on the following software items which could not befound in the source. However, these items may already be inthe target. This will be checked during the Analysis Phase:PHKL_27800.CORE2-KRN,fa=HP-UX_B.11.11_64PHKL_27800.CORE2-KRN,fa=HP-UX_B.11.11_64PHKL_27800.CORE2-KRN,fa=HP-UX_B.11.11_64PHKL_27800.CORE2-KRN,fa=HP-UX_B.11.11_64PHKL_27800.CORE2-KRN,fa=HP-UX_B.11.11_64

NOTE: The software "VRTSvxvm" was successfully marked, but itdepends on the following software items which could not befound in the source. However, these items may already be inthe target. This will be checked during the Analysis Phase:PHCO_27209.UX-CORE,fa=HP-UX_B.11.11_32/64PHCO_27101.KERN-RUN,fa=HP-UX_B.11.11_32/64PHCO_27101.UX-CORE,fa=HP-UX_B.11.11_32/64PHKL_27096.CORE2-KRN,fa=HP-UX_B.11.11_64PHKL_27096.CORE2-KRN,fa=HP-UX_B.11.11_64PHCO_27209.UX-CORE,fa=HP-UX_B.11.11_32/64PHCO_27101.KERN-RUN,fa=HP-UX_B.11.11_32/64PHCO_27101.UX-CORE,fa=HP-UX_B.11.11_32/64

WARNING: The software specified contains a kernel fileset. Itwill be necessary to reconfigure and reboot the system tomake the kernel software functional.

* Source: /tmp/dbed_oracle_3_5_hpux/./pkgs* Targets: target_machine:/* Software selections:

+ VRTSdbed.DBED,r=3.5,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.5,fa=HP-UX_B.11.11_32/64

VRTSfsdoc.VXFS-DOC,r=3.5-ga12,v=VERITAS,fr=3.5-ga12,fa=HP-UX_B.11.11_64

VRTSfspro.FSPRO-PRG,r=3.5-ga08,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.5-ga08,fa=HP-UX_B.11.11_32/64



VRTSob.VEAS-FILESET,r=3.0.2.261a,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.0.2.261a,fa=HP-UX_B.11.11_32/64

VRTSobgui.VEA-FILESET,r=3.0.2.261a,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.0.2.261a,fa=HP-UX_B.11.11_32/64

VRTSodm.ODM-KRN,r=3.5-ga10,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.5-ga10,fa=HP-UX_B.11.11_64

VRTSodm.ODM-MAN,r=3.5-ga10,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.5-ga10,fa=HP-UX_B.11.11_32/64

VRTSodm.ODM-RUN,r=3.5-ga10,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.5-ga10,fa=HP-UX_B.11.11_32/64

VRTSordoc.ORDOC,r=3.5,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.5,fa=HP-UX_B.11.11_32/64

VRTSorgui.GUI_PROVIDER,r=3.5,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.5,fa=HP-UX_B.11.11_32/64

VRTSvmdoc.VXVM-DOC,r=3.5m,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.5m,fa=HP-UX_B.11.11_32/64

VRTSvmpro.VMPRO-PRG,r=3.5m,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.5m,fa=HP-UX_B.11.11_32/64

VRTSvxfs.VXFS-ENG-A-MAN,r=3.5-ga12,a=HP-UX_B.11.11_64,v=VERITAS,fr=3.5-ga12,fa=HP-UX_B.11.11_64

VRTSvxfs.VXFS-KRN,r=3.5-ga12,a=HP-UX_B.11.11_64,v=VERITAS,fr=3.5-ga12,fa=HP-UX_B.11.11_64

VRTSvxfs.VXFS-KRN2,r=3.5-ga12,a=HP-UX_B.11.11_64,v=VERITAS,fr=3.5-ga12,fa=HP-UX_B.11.11_64

VRTSvxfs.VXFS-PRG,r=3.5-ga12,a=HP-UX_B.11.11_64,v=VERITAS,fr=3.5-ga12,fa=HP-UX_B.11.11_64

VRTSvxfs.VXFS-RUN,r=3.5-ga12,a=HP-UX_B.11.11_64,v=VERITAS,fr=3.5-ga12,fa=HP-UX_B.11.11_64

VRTSvxmsa.admin,r=2.1-REV=2002.09.17,a=HP-UX_B.11.11VRTSvxmsa.libraries,r=2.1-REV=2002.09.17,a=HP-UX_B.11.11VRTSvxmsa.logging,r=2.1-REV=2002.09.17,a=HP-UX_B.11.11VRTSvxmsa.plugins,r=2.1-REV=2002.09.17,a=HP-UX_B.11.11



VRTSvxvm.VXMS,r=3.5m,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.5m,fa=HP-UX_B.11.11_32/64

VRTSvxvm.VXVM-ENG-A-MAN,r=3.5m,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.5m,fa=HP-UX_B.11.11_32/64

VRTSvxvm.VXVM-HELP,r=3.5m,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.5m,fa=HP-UX_B.11.11_32/64

VRTSvxvm.VXVM-KRN,r=3.5m,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.5m,fa=HP-UX_B.11.11_64

VRTSvxvm.VXVM-RUN,r=3.5m,a=HP-UX_B.11.11_32/64,v=VERITAS,fr=3.5m,fa=HP-UX_B.11.11_32/64

* A "+" indicates an automatic selection due to dependencyor the automatic selection of a patch or reference bundle.* Selection succeeded.

* Beginning Analysis and Execution* Session selections have been saved in the file"/.sw/sessions/swinstall.last".

* "target_machine:/": There will be no attempt to mountfilesystems that appear in the filesystem table.

* "target_machine:/": 1 filesets have the selectedrevision already installed.

* Analysis and Execution succeeded.


==== 09/24/02 01:23:38 PDT END swinstall SESSION (non-interactive)(jobid=target_machine-0743)

Completed Installation of VERITAS Database Edition for Oracle. Thefollowing packages were installed:

VRTSdbedVRTSvlicVRTSvxfsVRTSvxvmVRTSodmVRTSobVRTSobguiVRTSorguiVRTSvmpro



VRTSfsproVRTSordocVRTSvmdocVRTSfsdocVRTSvxmsa

Use the swlist command to verify that the VERITAS Database Edition for Oracle packages are installed:

# swlist | egrep "VRTS|VERITAS”


If you installed all the packages available on the VERITAS Storage Solutions 3.5 for HP-UX CD1, the output for the swlist command shows the following packages:

VRTSdbed 3.5 VERITAS Database Edition UtilitiesVRTSfsdoc 3.5-ga12 VERITAS File System DocumentationVRTSfspro 3.5-ga08 VERITAS File System Management

ServicesVRTSob 3.0.2.261a VERITAS Enterprise Administrator

ServiceVRTSobgui 3.0.2.261a VERITAS Enterprise AdministratorVRTSodm 3.5-ga10 VERITAS Oracle Disk ManagerVRTSordoc 3.5 VERITAS Database Edition for Oracle

DocumentationVRTSorgui 3.5 VERITAS Database Edition Graphical

User InterfaceVRTSvlic 3.00.007g VERITAS License UtilitiesVRTSvmdoc 3.5m VERITAS Volume Manager DocumentationVRTSvmpro 3.5m VERITAS Volume Manager Management

Services ProviderVRTSvxfs 3.5-ga12 VERITAS File System with CFS SupportVRTSvxmsa 2.1-REV=2002.09.17 VxMS Application Deployment PackageVRTSvxvm 3.5m Base VERITAS Volume Manager 3.5 for

HP-UX


VERITAS Database Edition 3.5 for Oracle on HP-UX...

Documents

Transcript of VERITAS Database Edition 3.5 for Oracle on HP-UX...