VERITAS Database Edition 3 -...

VERITAS Database Edition™ 3.5 for Oracle

®

Installation Guide

Solaris

July 2002N08870F

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 © 1999-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 94043Phone 650–527–8000Fax 650–527–2908www.veritas.com

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Scope and Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xii

Typographic and Symbolic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xii

Notes and Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

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

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

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

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

Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Important Preinstallation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

VERITAS Volume Manager Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Configuration Decisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Disk Management Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Disk Encapsulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Disabling Hot-Relocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

iii

Chapter 2. Installation and Deinstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Installation Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

VERITAS Software Configuration Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Operating System Configuration Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

VERITAS Enterprise Administrator Considerations . . . . . . . . . . . . . . . . . . . . . . . . . 10

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

Installation Sequence Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Locating VERITAS Database Edition Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

VERITAS Database Edition Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Locations of VERITAS Database Edition Documentation . . . . . . . . . . . . . . . . . . . . . 14

Installing the VERITAS Database Edition Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Loading the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Mounting the CD and Installing with Solaris Volume Management . . . . . . . . 15

Mounting the CD and Installing without Solaris Volume Management . . . . . 16

Mounting the CD and Installing Using pkgadd . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Installing the VERITAS Enterprise Administrator client (Windows) . . . . . . . . 20

Installing the VERITAS Enterprise Administrator client (Solaris) . . . . . . . . . . . 20

Installing the VRTSexplorer Diagnostic Program . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Verifying VERITAS Database Edition Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Deinstalling VERITAS Database Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

VERITAS Volume Manager Deinstallation Considerations . . . . . . . . . . . . . . . . . . . 22

Moving Volumes from an Encapsulated Root Disk . . . . . . . . . . . . . . . . . . . . . . . 22

Moving Volumes to Disk Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Shutting Down VERITAS Volume Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Deinstalling the VERITAS Database Edition Software . . . . . . . . . . . . . . . . . . . . . . . 29

Chapter 3. Upgrade Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Upgrade Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Determining If the Root Disk Is Encapsulated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Solaris and Oracle Compatibility Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

iv VERITAS Database Edition for Oracle Installation Guide

Retaining Older VERITAS Volume Manager Releases . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Upgrading the Disk Group Version Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Upgrading VERITAS Database Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Upgrading VERITAS Database Edition on Solaris 2.6, 7, 8, or 9 . . . . . . . . . . . . . . . . 35

Upgrading VERITAS Database Edition on an Encapsulated Root Disk . . . . . . . . . 36

Upgrading Earlier Solaris Releases and Database Edition . . . . . . . . . . . . . . . . . . . . . 38

Converting Quick I/O Files to Oracle Disk Manager Files . . . . . . . . . . . . . . . . . . . . 41

Upgrading from SUNWvxvm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Chapter 4. Configuring the VERITAS Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

Database Configuration Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Configuring VERITAS Database Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Setting Administrative Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Setting Up VERITAS Enterprise Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Starting VERITAS Enterprise Administrator Server . . . . . . . . . . . . . . . . . . . . . . . 47

Shutting Down VERITAS Enterprise Administrator Server . . . . . . . . . . . . . . . . 48

Starting the VERITAS Enterprise Administrator Client . . . . . . . . . . . . . . . . . . . . 48

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

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

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

Configuring VERITAS File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Configuring VERITAS Volume Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Quick Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Custom Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Preventing Multipathing/Suppressing Devices from VERITAS Volume Manager’s View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Rebooting after vxinstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Confirming that VERITAS Volume Manager Processes Are Running . . . . . . . . . . 73

Configuring VERITAS File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Contents v

Upgrading VxFS Disk Layouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Verifying Command Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Verifying the VERITAS Database Edition Installation . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Chapter 5. High Availability Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

High Availability Product Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

VERITAS Database Edition/High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

High Availability Packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Appendix A. Installation Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Sample Installation Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

vi 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 Oracle database administrators configure a database system with high performance, availability, manageability, and reliability. This guide provides information on installing, upgrading, configuring, and removing the components of VERITAS Database Edition.

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 SystemTM (VxFSTM) with Quick I/OTM for Databases and QuickLogTM

� VERITAS Extension for Oracle Disk Manager

� VERITAS Database Edition GUI

� VxDBA Menu Utility

� VERITAS Enterprise AdministratorTM (VEATM)

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

ix

Organization

OrganizationThis guide is organized as follows:

� 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 removal 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 use the VERITAS software included in the VERITAS Database Edition for Oracle package. In particular, this chapter discusses how to initialize VxVM using vxinstall.

� Chapter 5, “High Availability Products,” describes the High Availability versions of VERITAS Database Edition for Oracle and how to install them.

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

Related DocumentsThe following documents provide related information:

� Release Notes provide important, up-to-date, and release-specific information for the various products bundled with this VERITAS Edition. Reading all of the Release Notes before installing or using any VERITAS products is recommended. Portable Document Format (.pdf) and PostScript (.ps) versions of these notes are provided on the Edition 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 File System Administrator’s Guide provides conceptual information about the 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 the VERITAS File System and provides examples of typical VERITAS File System operations.

� 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

x VERITAS Database Edition for Oracle Installation Guide

Related Documents

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. The guide also provides administrators with information on how to perform various VERITAS Volume Manager tasks through the VERITAS Enterprise Administrator (VEA) graphical user interface.

� 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 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.

While not shipped with the 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.

Preface xi

Conventions

Conventions

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

Typeface Conventions

Typeface Usage Examples

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

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

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 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

# mkfs -F vxfs -o largefiles \/dev/vx/rdsk/PRODdg/db01

xii VERITAS Database Edition for Oracle Installation Guide

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 HelpFor 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, brackets indicates an optional argument

ls [ -a ]

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

mount [ suid | nosuid ]

blue text In 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

Symbol Usage Examples

Preface xiii

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:

http://www.veritas.com

xiv VERITAS Database Edition for Oracle Installation Guide

http://support.veritas.com

http://www.veritas.com

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

� “General Installation Requirements” on page 1

� “VERITAS Volume Manager Considerations” on page 6

� “Obtaining a License Key” on page 1

After reviewing the information in this chapter, see Chapter 2 for information on installing VERITAS Database Edition for Oracle for the first time, or see Chapter 3 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 for Oracle, 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, Storage Mapping, or High Availability options).

If you are upgrading from a previous version of VERITAS Database Edition and do not want any new options, you do not need to obtain a new license. However, you will need to install the license utility package, VRTSvlic.

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.

1

General Installation Requirements

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

You can obtain your license key through the VERITAS vLicense Web site or by completing a License Key Request Form.

� 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 To obtain your license key using the License Key Form, see the VERITAS Database Edition for Oracle Installation Guide or the VERITAS Storage Solutions Product License and Installation Guide.

� To obtain a license key using a 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.

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/sbin/sysdef -h

You can obtain the machine type using the following command:

# prtconf | head -5 | tail -1

2. Fax the form to VERITAS at the number shown on the form.

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 the section “Getting Help” on page xiii in the Preface.

Operating SystemVERITAS Database Edition for Oracle can only be installed on a system running Solaris 2.6, 7 (32- or 64-bit), 8 (32- or 64-bit), or 9 (32- or 64-bit). Installing this Edition on any other Solaris release will fail. If necessary, upgrade Solaris before you install the VERITAS products. See “Upgrading Earlier Solaris Releases and Database Edition” on page 38.

Release NotesRead the Release Notes for all products included with this Edition. Postscript (.ps) and Portable Document Format (.pdf) versions of the Release Notes are included on the Solaris distribution CD in the release_notes directory.

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

OracleRelease Solaris 2.6

Solaris 7 (64-bit)

Solaris 7 (32-bit)

Solaris 8(64-bit)

Solaris 8(32-bit)

8.0.6 Yes Yes Yes No No

8.1.7 Yes No Yes Yes Yes

9.0.1.1 Yes No Yes Yes Yes

9.2 Yes No Yes Yes Yes

Chapter 1, Preinstallation 3


For information about VERITAS Database Edition support for Solaris 9, see the Release Notes.

Note If you plan to use the additional Storage Mapping option, please note that the Storage Mapping feature is not supported on Solaris 2.6.

Refer to the appropriate Oracle installation guide that accompanied your Oracle software for additional preinstallation information.

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

Product Space Requirements

Package Contents Size

VRTSdbed VERITAS Database Edition for Oracle (required) 24MB

VRTSvlic VERITAS Licensing Utilities (required) 6.4MB

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

7MB

VRTSordoc VERITAS Database Edition for Oracle Documentation 17MB

VRTSvxvm VERITAS Volume Manager, Binaries (required) 82MB

VRTSvmman VERITAS Volume Manager, Manual Pages 1.1MB

VRTSvmpro Virtual Disk Management Service Provider (required for FlashSnap and VEA)

5MB

VRTSvxmsa VERITAS Mapping Services, Application Library 1MB

VRTSvmdoc VERITAS Volume Manager Documentation 6MB

VRTSvxfs VERITAS File System (required) 50MB

VRTSfsdoc VERITAS File System Documentation 1.3MB

VRTSfspro VERITAS File System Services Provider (required for VEA)

6MB



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:/usr/sbin:/opt/VRTSvxfs/sbin:/opt/VRTSdbed/bin:\:/opt/VRTSob/bin

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

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

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

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

VRTSodm VERITAS Extension for Oracle Disk Manager 3MB

VRTSob VERITAS Enterprise Administrator Service (required for FlashSnap and VEA)

27MB

VRTSobgui VERITAS Enterprise Administrator (required for VEA) 42MB

win32/VRTSobgui.msi VERITAS Enterprise Administrator for Windows® 13MB

Total space for all packages 291.8MB

Total space for required packages 162.4MB

Total space for required packages and VEA 256.4MB

Total space for required packages and FlashSnap 194.4MB

Product Space Requirements

Package Contents Size


VERITAS Volume Manager Considerations

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

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 Software Configuration Considerations” on page 9 for reboot planning issues. Refer to “Rebooting after vxinstall” on page 72 for further information.

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 (which must be slice 1). 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.

Disk EncapsulationEncapsulating VERITAS Volume Manager disks retains the data on those disks, including boot information. Following are the requirements for disk encapsulation.

� Disks to be encapsulated must have:

- The required minimum free space (one cylinder)

- Two free partitions

- An s2 slice that represents the full disk

This s2 slice cannot contain a file system and must be labeled “backup.”

� If you plan to encapsulate the boot disk, tag the swap partition as swap so that you can dump to that partition later.

Before encapsulating your boot disk, set the EEPROM variable use-nvramrc? to TRUE to take advantage of the VERITAS Volume Manager boot disk aliases to identify the mirror of the boot disk if a replacement is needed. If use-nvramrc? is set to FALSE, you will need to determine which disks are bootable yourself. Set this variable to TRUE as follows:

# eeprom use-nvramrc?=true

Note If the path to an aliased boot device is different from the path in the /devices directory, the alias does not function correctly.



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 /etc/rc2.d/S95vxvm-recover, as follows:

# 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 the installation tasks for VERITAS Database Edition for Oracle and describes how to install the product for the first time. If you already have an earlier version of any of the VERITAS products installed, see Chapter 3, “Upgrade Procedures.” This chapter also provides instructions for deinstalling VERITAS Database Edition for Oracle.

� “Installation Considerations” on page 9

� “Summary of VERITAS Database Edition Installation Tasks” on page 11

� “Locating VERITAS Database Edition Packages” on page 12

� “Installing the VERITAS Database Edition Software” on page 14

� “Verifying VERITAS Database Edition Licensing” on page 21

� “Deinstalling VERITAS Database Edition” on page 22

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

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

VERITAS Software 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. Because it is important to minimize system downtime, consideration and planning can reduce downtime to a single reboot after installing all components and modifying the Solaris kernel settings to support the Oracle database.

9

Installation Considerations

� After installing the VERITAS Volume Manager and VERITAS File System packages, a system reboot is required. Initialize VERITAS Volume Manager (using the vxinstall program) immediately after adding the VERITAS Database Edition packages and before rebooting the system. See “Configuring VERITAS Volume Manager” on page 52 for more details on VERITAS Volume Manager initialization.

Note If you do not initialize VERITAS Volume Manager immediately after adding the Edition packages and before rebooting the system, you will still need to initialize VERITAS Volume Manager at a later time.

Operating System Configuration Considerations� If patches to the Solaris operating system are required, they should be applied just

prior to installing the VERITAS products. Patches may be required to resolve Solaris 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 the patches required for VERITAS, Oracle, and SUN (Solaris) software.

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 Solaris 2.6 or higher. The VEA client is supported on Solaris 2.6 or higher, 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 Service Provider (VRTSvmpro)


Summary of VERITAS Database Edition Installation Tasks

� VERITAS File System Service Provider (VRTSfspro)

� VERITAS Database Edition Graphical User Interface for Oracle (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 Solaris.

� VERITAS Enterprise Administrator for Windows® (win32/VRTSobgui.msi)

This is the client package for Windows.

The following are minimum system recommendations for the VEA client:

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 a license key.

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

� Configuring the VERITAS software (see Chapter 4, “Installation and Deinstallation” on page 9).

Installation Sequence Summary

� The recommended installation sequence is

1. Review the Release Notes.

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

Solaris: SPARCstation 5 with 64MB memory

Windows: 100MHz Pentium with 32MB memory

Chapter 2, Installation and Deinstallation 11

Locating VERITAS Database Edition Packages

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

4. For upgrades, you need to determine if the root disk is encapsulated, since this effects which upgrade process you should use. See Chapter 3, “Upgrade Procedures” for more information.

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

Installing VERITAS Database Edition entails:

- Using the Installation menu provided on the VERITAS CD or running the installDBED script on the command line to add VERITAS Database Edition.

- Running the vxinstall program to configure VERITAS Volume Manager.

- Rebooting the system.

Locating VERITAS Database Edition PackagesVERITAS products are distributed on four CDs, CD1, CD2, CD3, and CD4. The following VERITAS Database Edition for Oracle software packages are included in the database_edition_for_oracle/pkgs directory on CD2:

� VERITAS Database Edition for Oracle packages:

- VRTSdbed: Database Edition software, including the VxDBA utility

- VRTSodm: VERITAS Extension for Oracle Disk Manager software

- VRTSorgui: VERITAS Database Edition Graphical User Interface for Oracle

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

� VERITAS Volume Manager packages:

- VRTSvxvm: Volume Manager software

- VRTSvmman: Volume Manager manual pages

- VRTSvmpro: Volume Manager Service Provider

- VRTSvmdoc: Portable Document Format (.pdf) version of Volume Manager documentation


Locating VERITAS Database Edition Packages

� VERITAS File System packages:

- VRTSvxfs: VERITAS File System software and manual pages

- VRTSfspro: VERITAS File System Service Provider

- VRTSfsdoc: Portable Document Format (.pdf) version of VERITAS File System documentation

� VERITAS Enterprise Administrator packages:

- VRTSob: VERITAS Enterprise Administrator server software

- VRTSobgui: VERITAS Enterprise Administrator client software

� VRTSvlic: VERITAS License Utilities

� VRTSvxmsa: VERITAS Mapping Services, Application Library

In addition, the following software package is included in the win32 directory on CD2:

� VRTSobgui.msi

VERITAS Database Edition Documentation

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

� VERITAS Database Edition for Oracle Installation Guide

� VERITAS Database Edition for Oracle Database Administrator’s Guide

� VERITAS Database Edition for Oracle Release Notes

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

� VERITAS Volume Manager Troubleshooting Guide

� VERITAS Volume Manager Hardware Notes

� VERITAS Volume Manager Release Notes

� VERITAS File System Administrator’s Guide

� VERITAS File System Release Notes

To view or print PDF documents, you must use Adobe Acrobat Reader.


Installing the VERITAS Database Edition Software

Locations of VERITAS Database Edition DocumentationPDF files of the following VERITAS Database Edition for Oracle documents are included in the database_edition_for_oracle/docs directory on CD2:

� dbed_ig.pdf: VERITAS Database Edition for Oracle Installation Guide

� dbed_dbag.pdf: VERITAS Database Edition for Oracle Database Administrator’s Guide

Release notes for all products included with VERITAS Database Edition for Oracle can be found in the database_edition_for_oracle/release_notes directory on CD2.

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 /opt/VRTSvxvm/docs 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 CD2 to the /opt/VRTS/doc directory 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,” for important details about initializing (where required), setting up, and using the VERITAS software shipped with VERITAS Database Edition for Oracle.

Documentation Package Contents

VRTSordoc VERITAS Database Edition documentation

VRTSvmdoc VERITAS Volume Manager documentation

VRTSfsdoc VERITAS File System documentation



Loading the SoftwareYou must have superuser (root) privileges to load the VERITAS software.

� To load the VERITAS software

Choose one of the following methods:

� If the Solaris volume management software is running on your system, mount CD2 and install the packages using the Edition installation script as described in the section “Mounting the CD and Installing with Solaris Volume Management” on page 15.

� If the Solaris volume management software is not available, mount CD2 manually and install the packages by either using the Installation menu provided on the VERITAS CD or running the Edition installation script on the command line as described in the section “Mounting the CD and Installing without Solaris Volume Management” on page 16.

� If you want to install the Edition packages manually, rather than use the installation script, mount CD2 and install the packages using the pkgadd command as described in “Mounting the CD and Installing Using pkgadd” on page 17.

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

By default, the VERITAS Database Edition installation script does not interact with the user when adding packages. You can force interactive package install behavior by supplying the -v flag to the installation script.

Mounting the CD and Installing with Solaris Volume Management

When you insert VERITAS CD2, the Solaris volume management software automatically mounts it as /cdrom/CD_name. You may install the VERITAS Database Edition for Oracle packages by either using the Installation menu provided on CD2 or running the Edition installation script on the command line.

� To install VERITAS Database Edition for Oracle with Solaris Volume Management

1. Log in as root.

2. Insert VERITAS CD2 into your system’s CD-ROM drive.

3. Install VERITAS Database Edition using the Installation menu provided on the CD. See the procedure provided in the VERITAS Storage Solution 3.5 Product License and Installation Guide, which was included with the VERITAS CDs.



or

Install VERITAS Database Edition using the command line as follows:

a. Run the installDBED script:

# /cdrom/storage_solutions_solaris_3.5cd2/ \database_edition_for_oracle/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 VERITAS Enterprise Administrator, you can skip the VRTSob, VRTSobgui, VRTSvmpro, VRTSfspro, and VRTSorgui packages. They are optional. If you plan to use the Database FlashSnap option, however, you must have a valid license and you must install VRTSob and VRTSvmpro.

If you purchased the Storage Mapping option, you need to install VRTSvxmsa. 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 46 for more information.

Mounting the CD and Installing without Solaris Volume Management

If the Solaris volume management software is not available to mount the CD automatically, you can mount the CD manually and then install the VERITAS Database Edition for Oracle packages by either using the Installation menu provided on the VERITAS CD or running the Edition installation script on the command line.

� To install VERITAS Database Edition for Oracle without Solaris Volume Management

1. Log in as root.

2. Insert VERITAS CD2 into your system’s CD-ROM drive and enter:

# mount -F hsfs -o ro /dev/dsk/c0t6d0s2 /mnt

where c0t6d0s2 is the default address for the CD-ROM drive.



3. Install VERITAS Database Edition using the Installation menu provided on the CD. See the procedure provided in the VERITAS Storage Solution 3.5 Product License and Installation Guide, which was included with the VERITAS CDs.

or

Install VERITAS Database Edition using the command line as follows:

a. Run the installDBED script:

# /mnt/storage_solutions_solaris_3.5cd2/ \database_edition_for_oracle/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 VERITAS Enterprise Administrator, you can skip the VRTSob, VRTSobgui, VRTSvmpro, VRTSfspro, and VRTSorgui packages. They are optional. If you plan to use the Database FlashSnap option, however, you must have a valid license and you must install VRTSob and VRTSvmpro.

If you purchased the Storage Mapping option, you need to install VRTSvxmsa. If you do not intend to view or print the online documentation, you can skip 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 46 for more information.

If you added the VRTSvlic and see a message that says no changes were made to the system, follow the instructions in “Mounting the CD and Installing without Solaris Volume Management” on page 16.

The system prints a series of status messages as the installation progresses. No errors should be reported and the process takes about five minutes.

Mounting the CD and Installing Using pkgadd

If you prefer, you can use the pkgadd command rather than the Installation menu provided on the CD or the installation script provided with VERITAS Database Edition to mount the CD and install the packages.

Note If you choose to install VERITAS Database Edition using pkgadd, you must manually add the appropriate patches.



� To mount the CD and install using pkgadd

1. Log in as root.


3. If you are using Solaris volume management software, go to the directory that contains the software packages:

# cd /storage_solutions_solaris_3.5cd2/ \database_edition_for_oracle/pkgs

or

If you are not using Solaris volume management software, mount the CD and go to the directory that contains the software packages as follows:

# mount -F hsfs -o ro /dev/dsk/c0t6d0s2 /mnt# cd /mnt/storage_solutions_solaris_3.5cd2/ \database_edition_for_oracle/pkgs

4. Use the pkgadd command to install the VERITAS Database Edition for Oracle software packages as follows:

# pkgadd -d . VRTSdbed VRTSvlic VRTSvxvm VRTSvxfs \VRTSodm VRTSvmman# pkgadd -a ./VRTSobadmin -d . VRTSob VRTSobgui# pkgadd -d . VRTSvmpro VRTSfspro VRTSorgui VRTSordoc \VRTSvmdoc VRTSfsdoc

Note Install the packages in the order specified to ensure proper installation (for example, you should install VRTSvxvm before VRTSvmpro; VRTSob before VRTSvmpro, VRTSfspro and VRTSorgui; and VRTSvlic before VRTSvxvm and VRTSvxfs).

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 all questions asked of you during the installation.

If you do not intend to use VERITAS Enterprise Administrator, you can skip the VRTSob, VRTSobgui, VRTSvmpro, VRTSfspro, and VRTSorgui packages. They are optional. If you plan to use FlashSnap or off-host processing, however, you must have a valid license and you must install VRTSob and VRTSvmpro.

If you purchased the Storage Mapping option, you need to install VRTSvxmsa. If you do not intend to view or print the online documentation, you can skip the VRTSordoc, VRTSfsdoc, and VRTSvmdoc packages.



Note You need to make permission changes to allow database administrators access to the /opt/VRTSdbed after using pkgadd to install VERITAS Database Edition. See “Setting Administrative Permissions” on page 46 for more information.

Adding Patches

Occasionally, patches are required for the component products of VERITAS Database Edition. Patches contain the fixes for known problems. If you install VERITAS Database Edition using installDBED, patches are added for you. However, if you choose to install the Edition using pkgadd, you need to manually add the patches after installing the Edition.

VERITAS Database Edition 3.0 for Oracle contains a patch for the VERITAS Volume Manager (VRTSvxvm) package included in this release.

You must have superuser (root) privileges to load the VERITAS software.

� To add the VRTSvxvm patch

1. If you are using Solaris volume management software, go to the directory that contains the VRTSvxvm patches.

# cd /storage_solutions_solaris_3.5cd2/ \database_edition_for_oracle/patches/patch_number

or

If you are not using Solaris volume management software, mount the CD and go to the directory that contains the VRTSvxvm patches.

# mount -F hsfs -o ro /dev/dsk/c0t6d0s2 /mnt# cd /mnt/storage_solutions_solaris_3.5cd2/ \database_edition_for_oracle/patches/patch_number

2. Install the appropriate patch using the patchadd command.

# patchadd -M patch_number

where the patch number is

3. Verify that the patch was installed.

# showrev -p | grep patch_number

112392-01



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


2. Using Windows Explorer or a DOS Command window, go to the pkgs > win32 directory 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 (Solaris)

The VEA client for Solaris is automatically installed when you install all VERITAS Database Edition for Oracle packages.

If you did not previously install the VEA client package (VRTSobgui), you may install it after you have installed the VEA server software on the UNIX server on which the database runs.

� To install the VEA client on a Solaris machine using pkgadd

1. Log in as root.

2. First, check to determine whether the VEA client package is already installed:

# pkginfo -l | grep VRTSobgui

This command will return VRTSobgui if VRTSobgui is already installed. It will return nothing if the package has not been installed.

3. To install the VEA client package for Solaris, insert VERITAS CD2 into your system’s CD-ROM drive.


Verifying VERITAS Database Edition Licensing

4. If you are using Solaris volume management software, go to the directory that contains the software packages:

# cd /cdrom/storage_solutions_solaris_3.5cd2/ \dbed_oracle_3_5_solaris/pkgs

or

If you are not using Solaris volume management software, mount the CD and go to the directory that contains the software packages as follows:

# mount -F hsfs -o ro /dev/dsk/c0t6d0s2 /mnt# cd /mnt/storage_solutions_solaris_3.5cd2/ \database_edition_for_oracle/pkgs

5. Use the pkgadd command to install the package:

# pkgadd -d . VRTSorgui

6. Press Return.

The VEA client package for Solaris is installed.

Installing 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 intall it from the VERITAS CD. For instructions on downloading VRTSexplorer from the Web or installing it from the CD, see the Release Notes.

Verifying VERITAS Database Edition LicensingAfter you install VERITAS Database Edition, you can display a list of the licensed features by entering the following command:

# /sbin/vxlicrep

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 Database Edition 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.


Deinstalling VERITAS Database Edition

Deinstalling VERITAS Database EditionBefore deinstalling the VERITAS software, review the VERITAS Volume Manager and VERITAS File System deinstallation considerations. If the root disk is encapsulated, use the procedure in “Moving Volumes from an Encapsulated Root Disk” on page 22. If the root disk is not encapsulated, use the procedure in “Moving Volumes to Disk Partitions” on page 23.

VERITAS Volume Manager Deinstallation ConsiderationsThis section describes the steps you need to take before removing VERITAS Volume Manager to preserve the contents of the volumes.

Caution Failure to follow the preparations in this section might result in unexpected behavior.

Moving Volumes from an Encapsulated Root Disk

� To deinstall VxVM if root, swap, usr, or var is a volume under Volume Manager control

1. Ensure that the rootvol, swapvol, usr, and var volumes have only one associated plex each.

The plex must be contiguous, non-striped, non-spanned, and non-sparse. To obtain this information, enter the following command:

# vxprint -ht rootvol swapvol usr var

If any of these volumes have more than one associated plex, remove the unnecessary plexes using the following command:

# vxplex -o rm dis plex_name

Note It is important that you have created the plex designated for rootvol using vxrootmir, which guarantees that the underlying subdisks start on cylinder boundaries and that partitions are created for them.

2. Run the vxunroot command:

# /etc/vx/bin/vxunroot



The vxunroot command changes the volume entries in /etc/vfstab to the underlying disk partitions for rootvol, swapvol, usr, and var. It also modifies /etc/system and prompts for a reboot so that disk partitions are mounted instead of volumes for root, swap, usr, and var.

3. Once you have changed the root, swap, usr, and var volumes, move all remaining volumes to disk partitions. You can do this using one of these procedures:

- Back up the entire system to tape and then recover from tape.

- Back up each file system individually and then recover them all after creating new file systems on disk partitions.

- Move volumes individually to disk partitions.

Continue to the next section if you choose this last option.

Moving Volumes to Disk Partitions

� To move volumes to disk partitions

1. Evacuate disks using vxdiskadm, the GUI, or the vxevac script.

Evacuation moves subdisks from the specified disks to target disks. The evacuated disks provide the initial free disk space for volumes to be moved to disk partitions.

2. Remove the evacuated disks from VERITAS Volume Manager control by entering:

# vxdg rmdisk diskname# vxdisk rm devname

3. Decide which volume to move first, and if the volume is mounted, unmount it.

4. 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 you have applied the sync command to the data on the volume.

5. Create a partition on free disk space of the same size as the volume using the format command.

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



6. Copy the data on the volume onto the newly created disk partition using a command like the following:

# dd if=/dev/vx/dsk/diskgroup/lhome of=/dev/dsk/c2t2d2s7

where c2t2d2 is the disk outside of VERITAS Volume Manager and s7 is the newly created partition.

7. Replace the entry for that volume (if present) in /etc/vfstab with an entry for the newly created partition.

8. Mount the disk partition if the corresponding volume was previously mounted.

9. Remove the volume from VERITAS Volume Manager using the command:

# vxedit -rf rm volume_name

10. Remove any disks that have become free (those having no subdisks defined on them) by removing the volumes from VERITAS Volume Manager 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 you need to remove. If the output is 0, remove the disk from VERITAS Volume Manager control as follows:

# vxdg rmdisk diskname# vxdisk rm devname

Use the free space created for adding the data from the next volume you want to remove.

11. After you successfully convert all volumes into disk partitions, reboot the system.

12. After the reboot, make sure none of the volumes are open by using the following command:

# vxprint -Aht -e v_open

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

Example

This example shows how to move the data on a volume to a disk partition. In the example, there are three disks: disk1 and disk2 are subdisks on volume vol01 and disk3 is a free disk. The data on vol01 is copied to disk3 using vxevac.



Diskgroup voldg content before the data on vol01 is copied to disk3.

# vxprint -g voldg -htDG NAME NCONFIG NLOG MINORS GROUP-IDDM NAME DEVICE TYPE PRIVLEN PUBLEN STATERV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRLRL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNKV NAME RVG KSTATE STATE LENGTH READPOL PREFPLEXUTYPEPL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WIDMODESD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICEMODESV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NMMODEDC NAME PARENTVOL LOGVOLSP NAME SNAPVOL DCO

dg voldg default default 1150001017856044.1141.hostname.veritas.com

dm disk1 c1t12d0s2 sliced 2591 17900352 -dm disk2 c1t14d0s2 sliced 2591 17899056 -dm disk3 c1t3d0s2 sliced 2591 17899056 -

v vol1 - ENABLED ACTIVE 4196448 ROUND -fsgenpl pl1 vol1 ENABLED ACTIVE 4196448 CONCAT -RWsd sd1 pl1 disk1 0 2098224 0 c1t12d0ENAsd sd2 pl1 disk2 0 2098224 2098224 c1t14d0ENA

Evacuate disk1 to disk3.

# /etc/vx/bin/vxevac -g voldg disk1 disk3# vxprint -g voldg -ht

DG NAME NCONFIG NLOG MINORS GROUP-IDDM NAME DEVICE TYPE PRIVLEN PUBLEN STATERV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRLRL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNKV NAME RVG KSTATE STATE LENGTH READPOL PREFPLEXUTYPEPL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WIDMODESD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICEMODESV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NMMODEDC NAME PARENTVOL LOGVOLSP NAME SNAPVOL DCO





v vol1 - ENABLED ACTIVE 4196448 ROUND -fsgenpl pl1 vol1 ENABLED ACTIVE 4196448 CONCAT -RWsd disk3-01 pl1 disk3 0 2098224 0 c1t3d0ENAsd sd2 pl1 disk2 0 2098224 2098224 c1t14d0ENA

Evacuate disk2 to disk3.

# /etc/vx/bin/vxevac -g voldg disk2 disk3# vxprint -g voldg -ht

DG NAME NCONFIG NLOG MINORS GROUP-IDDM NAME DEVICE TYPE PRIVLEN PUBLEN STATERV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRLRL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNKV NAME RVG KSTATE STATE LENGTH READPOL PREFPLEXUTYPEPL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WIDMODESD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICEMODESV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NMMODEDC NAME PARENTVOL LOGVOLSP NAME SNAPVOL DCO



v vol1 - ENABLED ACTIVE 4196448 ROUND -fsgenpl pl1 vol1 ENABLED ACTIVE 4196448 CONCAT -RWsd disk3-01 pl1 disk3 0 2098224 0 c1t3d0ENAsd disk3-02 pl1 disk3 2098224 2098224 2098224 c1t3d0ENA

Remove the evacuated disks from VERITAS Volume Manager control.



# vxdisk -g voldg listDEVICE TYPE DISK GROUP STATUSc1t3d0s2 sliced disk3 voldg onlinec1t12d0s2 sliced disk1 voldg onlinec1t14d0s2 sliced disk2 voldg online

# vxdg rmdisk disk1# vxdg rmdisk disk2# vxdisk rm c1t12d0# vxdisk rm c1t14d0

Verify that the evacuated disks have been removed from VERITAS Volume Manager contol.

# vxdisk -g voldg listDEVICE TYPE DISK GROUP STATUSc1t3d0s2 sliced disk3 voldg online

Check to see whether the volume you want to move first is mounted.

# mount | grep vol1/vol1 on /dev/vx/dsk/voldg/vol1read/write/setuid/log/nolargefiles/dev=12dc138 on Wed Apr 3 10:13:11 2002

Create a partition on free disk space of the same size as the volume. In this example, a 2G partition is created on disk1 (c1t12d0s1).

# formatSearching for disks...done

AVAILABLE DISK SELECTIONS: 0. c0t0d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133> /sbus@1f,0/SUNW,fas@e,8800000/sd@0,0 1. c1t3d0 <QUANTUM-ATLASIV9SCA-0808 cyl 13814 alt 2 hd 4 sec 324> /sbus@1f,0/SUNW,fas@2,8800000/sd@3,0 2. c1t9d0 <QUANTUM-ATLASIV9SCA-0808 cyl 13814 alt 2 hd 4 sec 324> /sbus@1f,0/SUNW,fas@2,8800000/sd@9,0 3. c1t10d0 <QUANTUM-ATLASIV9SCA-0808 cyl 13814 alt 2 hd 4 sec 324> /sbus@1f,0/SUNW,fas@2,8800000/sd@a,0 4. c1t11d0 <QUANTUM-ATLASIV9SCA-0808 cyl 13814 alt 2 hd 4 sec 324> /sbus@1f,0/SUNW,fas@2,8800000/sd@b,0 5. c1t12d0 <QUANTUM-ATLASIV9SCA-0808 cyl 13814 alt 2 hd 4 sec 324> /sbus@1f,0/SUNW,fas@2,8800000/sd@c,0 6. c1t14d0 <QUANTUM-ATLASIV9SCA-0808 cyl 13814 alt 2 hd 4 sec 324> /sbus@1f,0/SUNW,fas@2,8800000/sd@e,0 7. c1t15d0 <QUANTUM-ATLASIV9SCA-0808 cyl 13814 alt 2 hd 4 sec 324> /sbus@1f,0/SUNW,fas@2,8800000/sd@f,0Specify disk (enter its number): 5selecting c1t12d0[disk formatted]



FORMAT MENU: disk - select a disk type - select (define) a disk type partition - select (define) a partition table current - describe the current disk format - format and analyze the disk repair - repair a defective sector label - write label to the disk analyze - surface analysis defect - defect list management backup - search for backup labels verify - read and display labels save - save new disk/partition definitions inquiry - show vendor, product and revision volname - set 8-character volume name !<cmd> - execute <cmd>, then return quitformat> p

PARTITION MENU: 0 - change `0' partition 1 - change `1' partition 2 - change `2' partition 3 - change `3' partition 4 - change `4' partition 5 - change `5' partition 6 - change `6' partition 7 - change `7' partition select - select a predefined table modify - modify a predefined partition table name - name the current table print - display the current table label - write partition map and label to the disk !<cmd> - execute <cmd>, then return quitpartition> 1Part Tag Flag Cylinders Size Blocks 1 unassigned wm 0 0 (0/0/0) 0Enter partition id tag[unassigned]: Enter partition permission flags[wm]: Enter new starting cyl[0]: Enter partition size[0b, 0c, 0.00mb, 0.00gb]: 2.00gbpartition> lReady to label disk, continue? y

partition> pCurrent partition table (unnamed):Total disk cylinders available: 13814 + 2 (reserved cylinders)

Part Tag Flag Cylinders Size Blocks 0 unassigned wm 0 0 (0/0/0) 0 1 unassigned wm 0 - 3236 2.00GB (3237/0/0) 4195152partition> q



Copy the data on vol01 to the newly created disk partition.

# dd if=/dev/vx/dsk/voldg/vol01 of=/dev/dsk/c1t12d0s1

In the /etc/vfstab file, remove the following entry.

/dev/vx/dsk/voldg/vol1 /dev/vx/rdsk/voldg/vol1 /vol1 vxfs 4 yes rw

Replace it with an entry for the newly created partition.

/dev/dsk/c1t12d0s1 /dev/rdsk/c1t12d0s1 /vol01 vxfs 4 yes rw

Mount the disk partition.

# mount -F vxfs /dev/dsk/c1t12d0s1 /vol01

Remove vol01 from VERITAS Volume Manager.

# vxedit -rf rm /dev/vx/dsk/voldg/vol01

To complete the procedure, follow Steps 10 through 12 in the previous section, “Moving Volumes to Disk Partitions” on page 23.

Shutting Down VERITAS Volume Manager

� To shut down VERITAS Volume Manager

Enter the vxdctl and vxiod commands as follows:

# vxdctl stop# vxiod -f set 0

Deinstalling the VERITAS Database Edition SoftwareIf you need to remove the VERITAS Database Edition for Oracle software packages, use the patchrm and pkgrm commands.

� To deinstall the VERITAS Database Edition 3.5 software

1. Check for the packages installed on your system:

# pkginfo | grep VRTS

The pkginfo command shows the VERITAS Database Edition for Oracle software packages installed on your system.

2. Comment out or remove any VERITAS File System (VxFS) entries from the file system table /etc/vfstab. Failing to remove these entries could result in system boot problems later.



3. Unmount all mount points for VxFS file systems:

# umount /mount_point

4. If the VERITAS Volume Manager package (VRTSvxvm) is installed, read and follow the deinstallation procedures in the section entitled “VERITAS Volume Manager Deinstallation Considerations” on page 22.

5. Use the pkgrm command to remove the installed VERITAS Database Edition for Oracle software packages. Remove the packages in the order shown:

# pkgrm VRTSordoc VRTSfsdoc VRTSvmdoc VRTSodm \VRTSvmman VRTSvxmsa VRTSorgui VRTSfspro VRTSvmpro \VRTSobgui VRTSob VRTSvxfs VRTSvxvm VRTSvlic VRTSdbed

Note You can install multiple versions of VERITAS Volume Manager. Check the pkginfo output and, if the output shows two versions (for example VRTSvxvm and VRTSvxvm.2) remove all of the packages by replacing VRTSvxvm with VRTSvxvm.\* in the pkgrm command described above.

The pkgrm command requires confirmation to remove each package. Answer the questions that appear during removal. The system prints out a series of status messages as the removal progresses.

Note Most packages in the VERITAS Database Edition product have kernel components. In order to ensure complete removal, a system reboot is recommended after all packages have been removed.

6. To verify the removal of the packages, enter:



Upgrade Procedures
3 If you are running an earlier release of VERITAS Volume Manager, VERITAS File System, or VERITAS Database Edition, you can upgrade to the releases provided in this release of VERITAS Database Edition for Oracle using the procedures described in this chapter.

� “Upgrade Overview” on page 31

� “Solaris and Oracle Compatibility Considerations” on page 32

� “Retaining Older VERITAS Volume Manager Releases” on page 33

� “Upgrading VERITAS Database Edition” on page 34

� “Upgrading from SUNWvxvm” on page 42

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

Upgrade OverviewAll VERITAS Database Editions consist of a set of bundled VERITAS products. These packages are tested together to ensure compatibility and maximum efficiency. When installing VERITAS Database Edition on top of existing packages or upgrading from a previous version, we recommend that all packages be upgraded to the set supplied with the Edition.

Caution Upgrading incorrectly can result in data loss. Review the preinstallation requirements detailed in Chapter 1, and then read and follow the upgrade procedures in this chapter carefully.

31

Solaris and Oracle Compatibility Considerations

To upgrade, use one of the following procedures:

Determining If the Root Disk Is EncapsulatedBefore you upgrade, you also need to determine if the root disk is encapsulated by running the following command:

# df -k

If the output from this command includes a pathname that contains vx and rootvol as in /dev/vx/dsk/rootvol, then the root disk is encapsulated. See “Upgrading VERITAS Database Edition on an Encapsulated Root Disk” on page 36.

Caution You must use the procedure in “Upgrading VERITAS Database Edition on an Encapsulated Root Disk” on page 36 if you have a system with an encapsulated root disk. Be sure to use the appropriate procedure to upgrade your VERITAS software and system.

After you complete the upgrade procedure, read Chapter 4, “Configuring the VERITAS Software,” for important details about initializing (where required), setting up, and using the VERITAS software shipped with VERITAS Database Edition for Oracle.

Solaris and Oracle Compatibility ConsiderationsYou must run a version of Solaris that is compatible with the version of Oracle you are using. If you are upgrading Solaris, ensure that the version of Oracle you are using supports the new Solaris version.

To upgrade Where See

VERITAS Database Edition

On an encapsulated root disk “Upgrading VERITAS Database Edition on an Encapsulated Root Disk” on page 36.

VERITAS Database Edition

On an unencapsulated root disk “Upgrading VERITAS Database Edition on Solaris 2.6, 7, 8, or 9” on page 35.

VERITAS Database Edition and Solaris

On an encapsulated or unencapsulated root disk

“Upgrading Earlier Solaris Releases and Database Edition” on page 38.


Retaining Older VERITAS Volume Manager Releases

This chapter describes combinations of VERITAS and Solaris upgrade procedures. The details of performing an operating system upgrade are beyond the scope of this document. Refer to your Solaris documentation for this procedure.

Retaining Older VERITAS Volume Manager ReleasesIn order to retain an older version of VERITAS Volume Manager and not upgrade to the current release shipped with VERITAS Database Edition for Oracle, you must set a special environment variable before starting the upgrade procedure.

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

$ NO_VXVM_UPGRADE=yes$ export NO_VXVM_UPGRADE

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

% setenv NO_VXVM_UPGRADE yes

The installation program checks for the NO_VXVM_UPGRADE environment variable during the upgrade and displays messages similar to the following if this variable is set:

Checking existing package installation...NOTICE: Package VRTSvxvm is being skipped (NO_VXVM_UPGRADE set).NOTICE: Package VRTSvmsa is being skipped (NO_VXVM_UPGRADE set).

Note You must upgrade VERITAS Volume Manager to version 3.5 if you want to use the Database FlashSnap option.

Upgrading the Disk Group Version SeparatelyIf you plan to implement VERITAS FastResync, you must use Disk Group Version 90 or later, which is supported in VERITAS Volume Manager 3.2 and higher. However, if you choose to retain a version of VERITAS Volume Manager older than 3.2, which does not contain Disk Group Version 90 or later, upgrade your disk group version separately.

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.

Chapter 3, Upgrade Procedures 33

Upgrading VERITAS Database Edition

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

Upgrading VERITAS Database EditionYou can upgrade VERITAS Database Edition for Oracle using the standard installation program, installDBED, provided with the Edition. Because the installDBED program is also used to upgrade the VERITAS File System and VERITAS Volume Manager packages, we recommend that you perform this upgrade from single-user mode with no VxFS file systems in use.

Note If you are currently using Quick I/O on Oracle8i or lower and plan to run VERITAS Database Edition 3.5 on Oracle9i with VERITAS Extension for Oracle Disk Manager, see “Converting Quick I/O Files to Oracle Disk Manager Files” on page 41 for more details.



Upgrading VERITAS Database Edition on Solaris 2.6, 7, 8, or 9This section describes upgrading to the current VERITAS Database Edition for Oracle if you are already running Solaris 2.6, 7, 8, or 9 and do not intend to upgrade your Solaris version. If you are running SUNWvxvm, go to “Upgrading from SUNWvxvm” on page 42.

� To upgrade the VERITAS Database Edition packages

1. Unmount any mounted VxFS file systems.

2. Reboot the machine to single-user mode (using a command such as shutdown).

3. If your system has a separate /opt file system, make sure it is mounted before proceeding with installation.When the system is in single user mode, /opt is not normally mounted.

4. Load and mount the CD as described in “Loading the Software” on page 15.

5. Run the installDBED program.

If the CD is mounted with Solaris volume management, enter:


or

If the CD is mounted without Solaris volume management, enter:


Depending on your existing configuration, various messages and prompts may appear. Answer the prompts appropriately.

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

If you do not intend to use the VERITAS Enterprise Administrator, you can skip the VRTSob, VRTSobgui, VRTSvmpro, VRTSfspro, and VRTSorgui packages. They are optional.

If you plan to use FlashSnap, however, you must have a valid license and you must install VRTSob and VRTSvmpro.



Upgrading VERITAS Database Edition on an Encapsulated Root Disk

This section explains how to upgrade VERITAS Database Edition if the root disk is encapsulated. Refer to “Upgrade Overview” on page 31 to determine if upgrading the operating system is required.

Note If your root disk is not encapsulated, see “Upgrading VERITAS Database Edition on Solaris 2.6, 7, 8, or 9” on page 35.

If you are upgrading VERITAS Database Edition on a system with an encapsulated root disk, you must first remove the previous release of VERITAS Volume Manager.

Note It is important that you follow these steps in the specified order.

� To upgrade on a system with an encapsulated root disk:

1. Run the upgrade_start script to prepare the previous release of VERITAS Volume Manager for removal:

- If the CD is mounted automatically, enter:

# /cdrom/storage_solutions_solaris_3.5cd2/ \database_edition_for_oracle/scripts/upgrade_start

- If the CD is mounted manually, enter:

# /mnt/storage_solutions_solaris_3.5cd2/ \database_edition_for_oracle/scripts/upgrade_start

The upgrade_start script looks for volumes containing file systems. If certain key file systems must be converted back to using partitions, the script indicates that a reboot is necessary. If any volumes are in use, you must either unmount those volumes or reboot to single-user mode.

If any error messages are encountered during the upgrade_start, process, run the upgrade_finish script immediately to restore the system. Examine the error messages and address them accordingly. Then, run the upgrade_start script again. Do not proceed to Step 2 until upgrade_start runs without producing any errors.

2. Boot the machine to single-user mode (using a command such as shutdown).

3. Remove any existing VxVM packages.

If you have a single version of VxVM loaded, follow this sequence:

# pkgrm VRTSvmdoc VRTSvmman VRTSvmsa VRTSvxvm VRTSvmdev



or

If you have multiple versions of VxVM loaded, remove the packages using this sequence:

# pkgrm VRTSvmdoc VRTSvmman VRTSvmsa VRTSvxvm.\*

Note If you have made any additional modifications or have applied any patches, remove these before removing the VRTSvxvm package. If you are using SUNWvxvm and SUNWvxva packages, see the Sun documentation for details on how to remove SUNWvxvm and SUNWvxva patches and packages.

4. If your system has a separate /opt file system, make sure it is mounted before proceeding with installation. When the system is in single user mode, /opt is not normally mounted.

5. Remount the CD manually:



6. Run the installDBED program:



7. If VxFS file systems are commented out in the /etc/vfstab file, uncomment them.

8. If you want to disable the hot-relocation feature, comment out the vxrelocd line in the startup file /etc/rc2.d/S95vxvm-recover, as follows:

# vxrelocd root &

9. Complete the upgrade by entering:

# /mnt/storage_solutions_solaris_3.5cd2/ \database_edition_for_oracle/scripts/upgrade_finish

10. Perform a reconfiguration reboot:

# reboot -- -r

At this point, your pre-upgrade configuration should be in effect and any file systems previously defined on volumes should be defined and mounted.



11. Importing a pre-3.5 VERITAS Volume Manager disk group does not automatically upgrade the disk group version to the VxVM 3.5 level. You may need to manually upgrade each of your disk groups following a VxVM upgrade. See the chapter on administering disks in the VERITAS Volume Manager Administrator’s Guide for information on how to upgrade a disk group version.

12. Follow the instructions in “Setting Up VERITAS Enterprise Administrator” on page 47 to set up and start VEA.

Upgrading Earlier Solaris Releases and Database EditionThis section describes upgrading to the current VERITAS Database Edition for Oracle if you are not running Solaris 2.6, 7, 8, or 9 and need to upgrade your Solaris version in addition to Database Edition. If you are running SUNWvxvm, go to “Upgrading from SUNWvxvm” on page 42.

This upgrade procedure allows you to retain existing VxVM and VxFS configurations. After upgrading, you can resume using your file systems and volumes as before (without having to run vxinstall again).

Note It is important that you follow these steps in the specified order.

� To prepare to upgrade the operating system

1. Ensure that if any of the file systems /, /usr, /var, /opt, /export/home, /var/adm or /usr/kvm defined on volumes, at least one plex for each of those volumes is formed from a single subdisk that begins on a cylinder boundary.

This is necessary because part of the upgrade process involves temporarily converting file systems on volumes back to using direct disk partitions, and Solaris requires that disk partitions start on cylinder boundaries. Upgrade scripts (located in the /scripts directory on the CD) automatically convert file systems on volumes back to using regular disk partitions, as necessary. If the upgrade scripts detect any problems (such as lack of cylinder alignment), they display an explanation of the problem and the upgrade does not proceed.

2. Check to see if any VxFS File Systems are mounted using the df command. If so, unmount them by using the umountall command:

# df -F vxfs# umountall -F vxfs



Note You need to remove previous versions of VxFS prior to upgrading the operating system and the VERITAS Database Edition. You do not need to remove existing VxFS file systems, but all of them must remain unmounted throughout the upgrade process.

3. Check to see if any packages remain on the machine by entering:


If any VxFS packages, including VERITAS Quick I/O (VRTSfdd or VRTSqio) or VERITAS QuickLog (VRTSvxld or VRTSqlog) are present, remove them as shown in Step 4.

4. Remove the VxFS related packages as follows:

# pkgrm VRTSfsdoc VRTSfdd VRTSqio VRTSvxld VRTSqlog VRTSvxfs


6. Run the upgrade_start script to prepare the previous release of the Volume Manager for its removal:





The upgrade_start script looks for volumes containing file systems. If certain key file systems must be converted back to using partitions, the script indicates that a reboot is necessary. If any volumes are in use, you must either unmount those volumes or reboot to single-user mode.


8. Remove any existing VxVM packages.

If you have a single version of VxVM loaded, follow this sequence:

# pkgrm VRTSvmdoc VRTSvmman VRTSvmsa VRTSvxvm

or

If you have multiple versions of VxVM loaded, remove the packages using this sequence:



# pkgrm VRTSvmdoc VRTSvmman VRTSvmsa VRTSvxvm.\*

Note If you have made any additional modifications or have applied any patches, remove these before removing the VRTSvxvm package. If you are using SUNWvxvm and SUNWvxva packages, see the Sun documentation for details on how to remove SUNWvxvm and SUNWvxva patches and packages.

9. If you have VxFS file systems specified in the /etc/vfstab file, comment them out.

10. Shut down and halt the machine (using a command such as shutdown).

� To upgrade the operating system

1. Upgrade the operating system to Solaris 2.6, 7, 8, or 9 according to the Solaris installation documentation.

Note Instructions on upgrading the operating system are beyond the scope of this document.


� To upgrade the VERITAS Database Edition packages after upgrading the operating system


2. Remount the CD manually:



3. Run the installDBED program:





4. If you commented out VxFS File System entries in the /etc/vfstab file in step 9 of the pre-upgrade procedures, uncomment them.

5. If you want to disable the hot-relocation feature, comment out the vxrelocd line in the startup file /etc/rc2.d/S95vxvm-recover, as follows:

# vxrelocd root &

6. Complete the upgrade by entering:


7. Reboot the machine to multiuser mode (using a command such as shutdown).


8. Importing a pre-3.x VERITAS Volume Manager disk group does not automatically upgrade the disk group version to the VxVM 3.x level. You may need to manually upgrade each of your disk groups following a VxVM upgrade. See the chapter on disk tasks in the VERITAS Volume Manager Administrator’s Guide for information on how to upgrade a disk group.

9. Follow the instructions in “Setting Up VERITAS Enterprise Administrator” on page 47 to set up and start VEA.

Converting Quick I/O Files to Oracle Disk Manager FilesIf you are currently using Quick I/O and plan to run VERITAS Database Edition 3.5 on Oracle9i with VERITAS Extension for Oracle Disk Manager, you need to convert your Quick I/O files to Oracle Disk Manager files. This should be done after you upgrade VERITAS Database Edition.

Note If you are running a previous version of Oracle (Oracle8.x or lower), you cannot convert your Quick I/O files.

� To convert Quick I/O files to Oracle Disk Manager files

1. Run getdbfiles.sh to retrieve a list of all datafiles.

# qio_getdbfiles -T ora -a

The list is compiled in a file named mkqio.dat.

2. Shutdown the database.


Upgrading from SUNWvxvm

3. Run qio_convertdbfiles in the directory containing the mkqio.dat file. (This converts all Quick I/O files to Oracle Disk Manager files.)

# qio_convertdbfiles -T ora -u

4. Restart the database.

Upgrading from SUNWvxvmThis section provides instructions for upgrading SUNWvxvm.

1. Run the upgrade_start script to prepare the previous release of VERITAS Volume Manager for its removal:





The upgrade_start script looks for volumes containing file systems. If certain key file systems must be converted back to using partitions, the script will indicate that a reboot is necessary. If so, reboot the machine to single-user mode before proceeding to the next step. If any volumes are in use, you must either unmount those volumes or reboot to single-user mode.



4. Remove all SUNWvxvm and SUNWvxva patches and packages.

Refer to Sun documentation for this procedure.


6. Run the installDBED program.







7. When you see the prompt for a license key, enter the appropriate license key. The installDBED program then upgrades the VERITAS Database Edition to include the necessary packages on your system.

Depending on your existing configuration, various messages and prompts may appear. Answer the prompts appropriately.

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

If you do not intend to use the VERITAS Enterprise Administrator, you can skip the VRTSob, VRTSobgui, VRTSvmpro, VRTSfspro, and VRTSorgui packages. They are optional.

If you plan to use FlashSnap, however, you must have a valid license and you must install VRTSob and VRTSvmpro.

8. Complete the upgrade by using the upgrade_finish command:

# /cdrom/storage_solutions_solaris_3.5cd2/ \/database_edition_for_oracle/scripts/upgrade_finish

or


9. Reboot the machine to multiuser mode (using a command such as shutdown).





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

� “Database Configuration Considerations” on page 45

� “Configuring VERITAS Database Edition” on page 46

� “Configuring VERITAS Volume Manager” on page 52

� “Configuring VERITAS File System” on page 74

� “Verifying the VERITAS Database Edition Installation” on page 75

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 /etc/system file before the database will run correctly. The most critical settings are normally located in the Shared Memory and Semaphore settings in Solaris. For precise settings, consult your current Oracle installation and configuration documentation.

45

Configuring VERITAS Database Edition

The following list is an example of the changes that need to be made to the /etc/system file for Oracle, before a reboot, so you can use your database:

* start Oracle *set shmsys:shminfo_shmmax=0xffffffffset shmsys:shminfo_shmmin=1set shmsys:shminfo_shmmni=100set shmsys:shminfo_shmseg=200

set semsys:seminfo_semmap=100set semsys:seminfo_semmni=1000set semsys:seminfo_semmns=4000set semsys:seminfo_semmnu=800set semsys:seminfo_semmsl=512

* end Oracle *

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 an 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 GUI for database administration require permission changes to allow for database administrators to access these tools. The default settings at installation time for the /opt/VRTSdbed directory allow 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 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 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 (Solaris) machine. The VERITAS Enterprise Administrator (VEA) client can be installed and run on any Solaris, AIX, HP-UX, Windows NT, Windows Me, Windows 2000, or Windows 98 machine that supports the Java Runtime Environment.

The following are system recommendations for the VxDBA GUI:

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 -mNot 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 -m

Solaris SPARCstation 5 with 64M memory

Windows NT, Me, 2000, or 98

300MHz Pentium with 256M memory

Chapter 4, Configuring the VERITAS Software 47


Running

Please note that if the Oracle database is down when VERITAS Enterprise Administrator server (vxsvc) starts, the VERITAS Database Edition Graphical User Interface for Oracle provider (VRTSorgui) quits and will not start even when the database is brought back up. If you encounter this problem, you can solve it in one of two ways:

� Shut down vxsvc, start the Oracle database, and then restart vxsvc.

� Select Actions > Rescan from the VERITAS Database Edition GUI.

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 -mRunning

2. Stop the VEA server:

# /opt/VRTSob/bin/vxsvc -kDBED: Unload Database Edition Provider 3.5 successful.

3. Again verify the status of the VEA server:

# /opt/VRTSob/bin/vxsvc -mNot running

Starting the VERITAS Enterprise Administrator Client

Only 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 installing VERITAS Volume Manager and VEA and starting the server, start VEA in one of the following ways.



UNIX (Solaris)

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:

# pkginfo -l VRTSorgui

PKGINST: VRTSorgui NAME: VERITAS Database Edition Graphical User Interface for

Oracle CATEGORY: application ARCH: Sparc VERSION: 3.5 VENDOR: VERITAS Software DESC: VERITAS Database Edition Graphical User Interface for

Oracle PSTAMP: hsieh.020322155315 INSTDATE: Apr 03 2002 15:55 HOTLINE: 1-800-342-0652 EMAIL: [email protected] STATUS: completely installed FILES: 29 installed pathnames 8 shared pathnames 13 directories 4 executables 13514 blocks used (approx)PKGINST: VRTSorgui



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

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 console registry.

� To remove 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:

# pkginfo -l VRTSorgui

PKGINST: VRTSorgui NAME: VERITAS Database Edition Graphical User Interface for

Oracle CATEGORY: application ARCH: Sparc VERSION: 3.5 VENDOR: VERITAS Software DESC: VERITAS Database Edition Graphical User Interface for

Oracle PSTAMP: hsieh.020322155315 INSTDATE: Apr 03 2002 15:55 HOTLINE: 1-800-342-0652 EMAIL: [email protected] STATUS: completely installed FILES: 29 installed pathnames 8 shared pathnames 13 directories 4 executables 13514 blocks used (approx)


Configuring VERITAS File System

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

vxtunefs Command Permissions and Cached Quick I/OBy default, you must have superuser (root) privileges to use the /opt/VRTSvxfs/sbin/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/VRTSvxfs/sbin/vxtunefs# chmod 4550 /opt/VRTSvxfs/sbin/vxtunefs

Note Setting the permissions for /opt/VRTSvxfs/sbin/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/vfstab file.

The VERITAS-specific commands are described in the VxFS guides and online manual pages (see the “Related Documents” on page x in the Preface).

VERITAS File System does not require initialization.


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.

� 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:

sena0emc1

4. To start vxinstall, enter:

# vxinstall

The vxinstall command first runs the /sbin/vxlicinst command to initialize the VERITAS Volume Manager license key file. The VERITAS Database Edition for Oracle installation program automatically creates the license key required for VERITAS Volume Manager, so you do not need to enter a VERITAS Volume Manager license key.

Then, vxinstall examines all controllers that it finds attached to the system and lists them. You are asked if you want to use enclosure-based naming. If you do not want to use enclosure-based names, enter n and proceed to Step 9.

Generating list of attached enclosures....

VxVM will use the following format to name disks on the host:<enclosurename>_<diskno>

In the above format, <enclosurename> is the logical name of the enclosure to which the disk belongs. VxVM assigns default enclosure names which can be changed according to the user requirements.

Some examples would be:

hitachi0_2 - second disk detected in enclosure’hitachi0’

enggdept_2 - second disk detected in enclosure’enggdept’

dgc1_1 - first disk detected in enclosure ’dgc1’jbod_1 - first disk detected in the jbod category

For non-public loop disks (Ex. FC disks directly connected to the host or through hubs), you could choose to use the c#t#d#s# naming format.



Do you want to use enclosure based names for all disks ? [y,n,q,?] (default: y) y

5. Enter y to use enclosure-based naming system for the disks on the system. vxinstall detects and displays a list of disk arrays connected to your system.

Volume Manager InstallationMenu: VolumeManager/Install

The Volume Manager has detected the following categories of storageconnected to your system:

Enclosures: T3-01 sena0 sena1 sena3sena4 sena5

Others: others0

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

6. Enter y to assign a new name to the enclosures. This helps to identify the physical location of the enclosure.

Rename an enclosureMenu: VolumeManager/Install/Rename enclosure

Enter an enclosure name: [list,q,?] test1

Enter the name of an enclosure you wish to rename.

Enter the new name for enclosure test1: T3

The enclosure name test1 has been changed to T3

Hit RETURN to continue.

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. Press Return.

The vxinstall command displays a brief introduction to the installation process:


You will now be asked if you wish to use Quick Installation orCustom Installation. Custom Installation allows you to select



how the Volume Manager will handle the installation of each diskattached to your system.

Quick Installation examines each disk attached to your systemand attempts to create volumes to cover all disk partitions thatmight be used for file systems or for other similar purposes.

If you want to exclude any devices from being seen by VxVM or notbe multipathed by vxdmp then use the Prevent multipathing/Suppress devices from VxVM’s view option, before youchoose Custom Installation or Quick Installation.

If you do not wish to use some disks with the Volume Manager,or if you wish to reinitialize some disks, use the CustomInstallation option. Otherwise, we suggest that you use theQuick Installation option.Hit RETURN to continue.

9. Press Return.

The vxinstall command displays a menu with the following options:

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.

10. Select either 1 Quick Installation, 2 Custom Installation, or 3 Prevent Multipathing/Suppress devices from VxVM’s view to proceed with the installation.

- If you select Quick Installation, go to the section entitled “Quick Installation” on page 56.



- If you select Custom Installation, go to the section entitled “Custom Installation” on page 60.

- If you select Prevent Multipathing/Suppress devices from VxVM’s view, go to the section entitled “Preventing Multipathing/Suppressing Devices from VERITAS Volume Manager’s View” on page 66.

Note Quick Installation brings every disk attached to your system under VERITAS Volume Manager control, unless you have chosen to exclude those disks (through the disks.exclude, cntrls.exclude, or enclr.exclude file, described earlier). To prevent placing disks under VERITAS Volume Manager control, either list them in the disks.exclude file or choose the Custom Installation option (which allows you to exclude certain disks).

Quick InstallationThe Quick Installation option is the easiest to use. For each controller, Quick Installation gives you the option of either initializing or encapsulating all disks. If you want to encapsulate some disks on a given controller and initialize others, use Custom Installation instead. Encapsulation preserves existing data; initialization removes the data.

Note You cannot grow or shrink any volume associated with an encapsulated boot disk (rootvol, usr, var, opt, swapvol, etc.) because these map to a physical underlying partition on the disk and must be contiguous. Refer to Volume Manager Rootability in Chapter 3 of the VERITAS Volume Manager Administrator’s Guide.

Quick Installation lets you initialize disks in a disk array, even if valid partitions are found on those disks. Avoid selecting the initialize option for any disks containing valid data since initializing the disk removes any existing data.

With encapsulation, the /etc/vfstab file is updated to ensure that file systems previously mounted on disk partitions are mounted on volumes instead.

� To use the Quick Installation option

1. Select menu item 1 Quick Installation from the vxinstall main menu.

The vxinstall command prompts for each disk array and disk connected to your system. When a default response appears in parentheses, you can simply press Return to accept that default. At any of the vxinstall prompts, you can select q to completely abandon the initialization and start over.



Note All disks are encapsulated or initialized (according to your instructions) at the end of the vxinstall procedure. If you quit vxinstall before it enters its final phase of actually initializing or encapsulating the disks, all disks are left as they were before vxinstall started.

2. At the following prompt, indicate whether to encapsulate your boot disk (this example assumes your boot disk is named c0t3d0):

The c0t3d0 disk is your Boot Disk. You can not add it as a newdisk. If you encapsulate it, you will make your root file systemand other system areas on the Boot Disk into volumes. This isrequired if you wish to mirror your root file system or systemswap area.Encapsulate Boot Disk [y,n,q,?] (default: n)

- If you enter n, your root and other file systems are left unaltered.

- If you enter y, your boot disk is encapsulated.

At the prompt, enter a disk name for the boot disk and press Return to continue. The vxinstall program encapsulates your root file system as a volume, along with your swap device and all other disk partitions found on your boot disk. /usr, /opt, /var, and any other file systems on your boot disk are also encapsulated.

The vxinstall command lists each disk array and then asks you how to handle the disks contained in that disk array. The vxinstall program begins this process for each disk array by identifying the disk array and generating a list of its disks, as follows:


Volume Manager Quick InstallationMenu: VolumeManager/Install/QuickInstall/c1

Disk array serial number : 60020f20000005bd0000

Generating list of disks in disk array c1....

The Volume Manager has detected the following disks in disk array c1:

c1t0d0 c1t1d0 c1t2d0 c1t3d0 c1t4d0




If any disks are listed in the /etc/vx/disks.exclude file, they are listed here separately as excluded disks.

3. Press Return.

4. At the following prompt, indicate whether you want to initialize all of the disks on the disk array:

Volume Manager Quick Installation For Disk Array c1Menu:VolumeManager/Install/QuickInstall/c1

Initialize all disks on this disk array? (destroys data on thesedisks) [y,n,q,?] (default: n)

- If you enter n, vxinstall assumes that you want to encapsulate all disks on the disk array instead and displays the following:

Volume Manager will now try to encapsulate all the disks on this disk array.Disks not having valid partitions will be initialized.Hit RETURN to continue.

- If you enter y, vxinstall prompts you for confirmation and warns you that this action destroys any existing data on the disks:

Are you sure (destroys data on these disks)[y,n,q,?] (default: n)

Caution Initialization removes any existing data on the disks.

5. Press Return.

6. Enter y to continue with the disk initialization. The following message appears:

Volume Manager will now initialize all the disks on this disk array including disks having valid partitions. Hit RETURN to continue.

7. Press Return.

8. At the following prompt, indicate whether you want vxinstall to assign default disk names to all of the disks on the disk array:

Use default disk names for these disks? [y,n,q,?] (default: y)

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



The c1t0d0 disk will be given disk name disk01The c1t1d0 disk will be given disk name disk02The c1t2d0 disk will be given disk name disk03The c1t3d0 disk will be given disk name disk04


If you selected encapsulation earlier, this listing also includes a message similar to the following for each disk that can be encapsulated:

The c1t0d0 disk has been configured for encapsulation.

or a message similar to the following for empty disks to be initialized instead of encapsulated:

The c3t2d0 disk appears to be empty. Adding as a new disk.

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

Enter disk name for c1t0d0 [<name>,q,?](default: disk01)

9. For each disk, respond with the desired disk name and press Return.

10. When you have named all of the disks on the current disk array, press Return and repeat Steps 4 through 9 for the remaining disk arrays on your system.

When you complete the vxinstall procedure for all disk arrays on your system, vxinstall displays a summary of the disks you have designated for initialization (New Disk) or encapsulation (Encapsulate) on each controller:

The following is a summary of your choices.c0t5d0 New Diskc1t0d0 New Diskc1t1d0 New Diskc1t2d0 New Diskc2t2d3 New Diskc3t0d0 Encapsulatec3t1d0 Encapsulatec3t2d0 New Disk

Is this correct [y,n,q,?] (default: y)

This is your last chance to review and alter your choices for how to handle any of the disks to be placed under VERITAS Volume Manager control.

- If you enter y, vxinstall encapsulates all disks listed with Encapsulate and initializes (destroying any existing data) all disks listed with New Disk.

- If you enter n, vxinstall prompts you for the name of a disk to be removed from the list and excluded from VERITAS Volume Manager control:



Enter disk to be removed from your choices. Hit return when done. [<name>,q,?]

11. Enter the name of the disk to be removed from the list and press Return.

Repeat for each disk to be removed and then press Return once more. The vxinstall command displays an updated summary without the disks chosen for removal. If you are satisfied with the summary, enter y.

Depending on how you chose to handle your disks during the vxinstall, you may see instructions to shut down and reboot your machine. If this happens, shut down and reboot your machine immediately or at the earliest convenient opportunity. Refer to “VERITAS Software Configuration Considerations” on page 9 for reboot planning issues. Refer to “Rebooting after vxinstall” on page 72 for further information.

A reboot is necessary if any disks are to be encapsulated.

Caution Do not make any changes to your disk or file system configurations before shutting down and rebooting your system.

If a shutdown is not required, vxinstall indicates successful completion of the installation:

Installation is complete.

Custom InstallationCustom Installation allows you to control which disks you place under VERITAS Volume Manager control and how they are added. This is important if you do not want all your disks under VERITAS Volume Manager control. Custom Installation also gives you the option of initializing all disks on a disk array, encapsulating all disks on a disk array, or initializing some disks on a disk array and encapsulating others.

Note You cannot grow or shrink any volume associated with an encapsulated boot disk (rootvol, usr, var, opt, swapvol, etc.) because these map to a physical underlying partition on the disk and must be contiguous. Refer to Volume Manager Rootability in Chapter 3 of the VERITAS Volume Manager Administrator’s Guide.



� To use the Custom Installation option

1. Select item 2 Custom Installation from the vxinstall main menu.

The vxinstall command asks a series of questions for each disk array and disk it finds connected to your system. When you see a default response displayed in parentheses, you can press Return to accept that default. At any of the vxinstall prompts, you can select q to completely abandon the initialization and then start over.

Note All disks are encapsulated or initialized (according to your instructions) at the end of the vxinstall procedure. If you quit vxinstall before it initializes or encapsulates the disks, all disks are left as they were before vxinstall started.

2. At the following prompt, indicate whether to encapsulate your boot disk (this example assumes your boot disk is named c0t3d0):

The c0t3d0 disk is your Boot Disk. You can not add it as a new disk. If you encapsulate it, you will make your root file system and other system areas on the Boot Disk into volumes. This is required if you wish to mirror your root file system or system swap area.Encapsulate Boot Disk [y,n,q,?] (default: n)

- If you enter n, your root and other file systems will be left unaltered.

- If you enter y, the vxinstall command encapsulates your root file system as a volume, along with your swap device and all other disk partitions found on your boot disk. /usr, /opt, /var, and any other file systems on your boot disk are also encapsulated.

The vxinstall command lists each disk array and then asks you how to handle the disks contained on that disk array. The vxinstall program begins this process for each disk array by identifying the disk array and generating a list of its disks, as follows:

Volume Manager Custom InstallationMenu: VolumeManager/Install/Custom/c1

Disk array serial number : 60020f20000005bd0000

Generating list of disks in disk array c1....

The Volume Manager has detected the following disks in enclosure c1:

c1tod0 c1t1d0 c1t2d0 c1t3d0 c1t4d0




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

3. Press Return.

4. At the following prompt, select the option that indicates how you want the disks on this disk array to be handled:

Installation options for enclosure c1Menu: VolumeManager/Install/Custom/c11 Install all disks as pre-existing disks. (encapsulate)2 Install all disks as new disks.(discards data on disks!)3 Install one disk at a time.4 Leave these disks alone.? Display help about menu?? Display help about the menuing systemq Exit from menusSelect an operation to perform:

� To encapsulate all disks

1. Select item 1 from the menu.

The vxinstall command creates volumes to encapsulate any partitions on all disks on this controller. The command updates the /etc/vfstab file to ensure that file systems previously mounted on disk partitions are mounted as volumes instead.

2. At the following prompt, indicate whether you want default disk names to be assigned to all of the disks on the controller:



The c1t0d0 disk will be given disk name disk01The c1t0d0 disk has been configured for encapsulation.The c1t1d0 disk will be given disk name disk02The c1t1d0 disk has been configured for encapsulation.Hit RETURN to continue.

If any disks are found to be empty, the following message indicates that they are initialized instead of encapsulated:

The c3t2d0 disk appears to be empty. Adding as a new disk.

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




3. For each disk, respond with the desired disk name and press Return.

4. When you have named all of the disks on the current disk array, press Return to move on to the next disk array.

� To initialize all disks

1. Select item 2 from the main menu.

Caution Initialization removes any existing data on the disks.

All disks in this disk array are reinitialized. 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. If you are running vxinstall on new disks that have never been placed under VERITAS Volume Manager control before, choose this option so that the disks are repartitioned according to VERITAS Volume Manager specifications.

2. At the following prompt, indicate whether you want default disk names to be assigned to all of the disks on the disk array:



The c1t0d0 disk will be given disk name disk01The c1t1d0 disk will be given disk name disk02Hit RETURN to continue.

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


3. For each disk, enter the desired disk name and press Return.

4. When you have named all of the disks on the current disk array, press Return to move on to the next disk array.

� To install individual disks

1. Select item 3 from the main menu.

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



2. At the following prompt, select the option that indicates how you want this disk to be handled:

Installation options for disk c1t0d0Menu: VolumeManager/Install/Custom/c1/c1t0d0

1 Install as a pre-existing disk. (encapsulate)2 Install as a new disk.(discards data on disks!)3 Leave this disk alone.

? Display help about menu?? Display help about the menuing systemq Exit from menus


These options are similar to those in the Custom Installation main menu. Once you have selected how to handle this disk, see the instructions following step 4 on page 62.

3. Press Return to move on to the next disk. Repeat the previous step for the remaining disks on the current disk array.

4. 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 on the disk array unaltered


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

2. Repeat step 4 on page 62 for each of the remaining disk arrays on your system.

When you have completed the vxinstall procedure for all disk arrays on your system, vxinstall displays a summary of the disks you have designated for initialization (New Disk) or encapsulation (Encapsulate) on each disk array:

The following is a summary of your choices.c0t5d0 New Diskc1t0d0 New Diskc1t1d0 New Diskc1t2d0 New Diskc2t2d3 New Disk



c3t0d0 Encapsulatec3t1d0 Encapsulatec3t2d0 New Disk

Is this correct [y,n,q,?] (default: y)

This is your last chance to review and alter your choices for how to handle any of the disks to be placed under VERITAS Volume Manager control.

- If you enter y, vxinstall proceeds to encapsulate all disks listed with Encapsulate and initialize (destroying any existing data) all disks listed with New Disk.

- If you enter n, vxinstall prompts for the name of a disk to be removed from the list and excluded from VERITAS Volume Manager control:

Enter disk to be removed from your choices. Hit return whendone. [<name>,q,?]

3. Enter the name of the disk to be removed from the list and press Return.

4. Repeat for each disk to be removed and then press Return once more.

The vxinstall program displays an updated summary without the disks chosen for removal.

5. If you are now satisfied with the summary, enter y.

Depending on your input during the vxinstall procedure, you may see instructions to shut down and reboot your machine. If this happens, shut down and reboot your machine immediately or at the earliest convenient opportunity. Refer to “VERITAS Software Configuration Considerations” on page 9 for reboot planning issues. Refer to “Rebooting after vxinstall” on page 72 for further information.

Caution Do not make any changes to your disk or file system configurations before shutting down and rebooting your system.

If a shutdown is not required, vxinstall indicates successful completion of the installation:

Installation is complete.



Preventing Multipathing/Suppressing Devices from VERITAS Volume Manager’s View

This section describes how to exclude a device from dynamic multipathing or VERITAS Volume Manager control. Follow these steps to prevent multipathing or suppress devices.

� To prevent multipathing or suppress devices

1. Select item 3 Prevent multipathing/Suppress devices from VxVM’s view from the vxinstall main menu.

The following message appears:

Volume Manager InstallationMenu: VolumeManager/Install/Exclude Devices

This operation might lead to some devices being suppressed from VxVM’s view or prevent them from being multipathed by vxdmp. (This operation can be reversed using the vxdiskadm command).

Do you want to continue? [y,n,q,?] (default: n)

2. Enter y.

The following menu appears:

Volume Manager Device OperationsMenu: VolumeManager/Install/Exclude Devices

1 Suppress all paths through a controller from VxVM’s view2 Suppress a path from VxVM’s view3 Suppress disks from VxVM’s view by specifying a VID:PID combination4 Suppress all but one path to a disk5 Prevent multipathing of all disks on a controller by VxVM6 Prevent multipathing of a disk by VxVM7 Prevent multipathing of disks by specifying a VID:PIDcombination8 List currently suppressed/non-multipathed devices? Display help about menu?? Display help about the menuing systemq Exit from menus


3. Select the option for the operation you want to perform from the menu.



� To prevent VERITAS Volume Manager from using all paths through a specified controller


The following prompt appears:

Exclude controllers from VxVMMenu: VolumeManager/Install/ExcludeDevices/CTLR-VXVM

Use this operation to exclude all paths through a controller from VxVM.

This operation can be reversed using the vxdiskadm command.

You can specify a controller name at the prompt. A controller name is of the form scsi# or fscsi#, example scsi1, scsi11,fscsi2, etc. Enter ’all’ to exclude all paths on all the controllers on the host. To see the list of controllers on the system, type ’list’.

Enter a controller name:[ctlr_name,all,list,list-exclude,q,?]

2. At the prompt, enter the named controller you want to disable.

The specified controller is disabled.

3. Press Return.

� To prevent VERITAS Volume Manager from using one or more specified paths



Exclude paths from VxVMMenu: VolumeManager/Install/ExcludeDevices/PATH-VXVM

Use this operation to exclude one or more paths from VxVM.

As a result of this operation, the specified paths will be excluded from the view of VxVM. This operation can be reversed using the vxdiskadm command.

You can specify a pathname or a pattern at the prompt. Here are some path selection examples:

all:all pathsc4t2:all paths on controller 4, target 2c3t4d2:a single pathlist:list all paths on the system



Enter a pathname or pattern:[<Pattern>,all,list,list-exclude,q?]

2. At the prompt, enter the path you want to exclude from VERITAS Volume Manager control.

3. Press Return.

The specified path is excluded from VERITAS Volume Manager control.

� To prevent VERITAS Volume Manager from using one or more disks specified by a VID:PID combination



Exclude VID:PID from VxVMMenu: VolumeManager/Install/ExcludeDevices/VIDPID-VXVM

Use this operation to exclude disks returning a specified VendorID:ProductID combination from VxVM.

As a result of this operation, all disks that return VendorID:ProductID matching the specified combination will be excluded from the view of VxVM. This operation can be reversed using the vxdiskadm command.

You can specify a VendorID:ProductID pattern at the prompt. The specification can be as follows :

VID:PID where VID stands for Vendor ID PID stands for Product ID

(The command vxdmpinq in /etc/vx/diag.d can beused to obtain the Vendor ID and Product ID.)

Both VID and PID can have an optional ’*’ (asterisk) following them.If a ’*’ follows VID, it will result in the exclusion of all disks returning Vendor ID starting with VID. The same is true for Product ID as well. Both VID and PID should be non NULL. The maximum allowed length for VendorID and ProductID are 8 and 16 characters respectively.

Some examples of VID:PID specification are:

all- Exclude all disksaaa:123- Exclude all disks having VID ‘aaa’ and PID ‘123’aaa*:123- Exclude all disks having VID starting with ‘aaa’ and

PID ‘123’



aaa:123*- Exclude all disks having VID ‘aaa’ and PID startingwith ‘123’

aaa:*- Exclude all disks having VID ‘aaa’ and any PID

Enter a VID:PID combination:[<Pattern>,all,list,exclude,q,?]

2. At the prompt, enter the VID:PID combination of the disks you want to exclude from VERITAS Volume Manager control. For example, the VID:PID combination for Sun’s T3 disk array would be specified as SUN:T3.

3. Press Return.

The disks that match the VID:PID combination are excluded from VERITAS Volume Manager control.You can obtain the Vendor ID and Product ID of a disk by using the command /usr/lib/vxvm/diag.d/vxdmpinq. (This command displays the standard SCSI inquiry data returned from the disk controller.)

� To prevent VERITAS Volume Manager from defining a set of paths, or pathgroup, for a disk


Note A pathgroup specifies a set of paths that VERITAS Volume Manager should recognize as a single path. Only one path is made visible from a pathgroup.


Exclude all but one paths to a diskMenu: VolumeManager/Install/ExcludeDevices/PATHGROUP-VXVM

Use this operation to exclude all but one paths to a disk. In case of disks which are not multipathed by vxdmp, VxVM will see each path as a disk. In such cases, creating a pathgroup of all paths to the disk will ensure only one of the paths from the group is made visible to VxVM. The pathgroup can be removed using the vxdiskadm command.

Example: If c1t30d0 and c2t30d0 are paths to the same disk and both are seen by VxVM as separate disks, c1t30d0 and c2t30d0 can be put in a pathgroup that only one of these paths is visible to VxVM.

The pathgroup can be specified as a list of blank separated paths, for example, c1t30d0 c2t30d0.

Enter pathgroup: [<pattern>,list,list-exclude,q,?]



2. At the prompt, enter the name of the paths in the pathgroup you want VxVM to treat as a single path.

3. Press Return.

Note The next three options allow you to exclude devices from vxdmp.

� To prevent VERITAS Volume Manager from applying dynamic multipathing to all disks on a controller



Exclude controllers from DMPMenu: VolumeManager/Install/ExcludeDevices/CTLR-DMP

Use this operation to exclude all disks on a controller from being multipathed by vxdmp.

As a result of this operation, all disks having a path through the specified controller will be claimed in the OTHER_DISKS category and hence, not multipathed by vxdmp. This operation can be reversed using the vxdiskadm command.

You can specify a controller name at the prompt. A controller name is of the form scsi#, example scsi3, scsi11, fscsi2 etc. Enter ’all’ to exclude all paths on all the controllers on the host. To see the list of controllers on the system, type ’list’.

Enter a controller name:[<ctlr-name>,all,list,list-exclude,q,?]

2. At the prompt, enter the name of the controller you want to exclude from dynamic multipathing.

3. Press Return.

The named controller is excluded from dynamic multipathing control.

� To exclude a specified path from dynamic multipathing



Exclude paths from DMPMenu: VolumeManager/Install/ExcludeDevices/PATH-DMP



Use this operation to exclude one or more disks from vxdmp.

As a result of this operation, the disks corresponding to the specified paths will not be multipathed by VxDMP. This operation can be reversed using the vxdiskadm command.

You can specify a pathname or a pattern at the prompt. Here are some path selection examples:

all:all pathsc4t2:all paths on controller 4, target 2c3t4d2:a single pathlist:list all paths on the system

Enter a pathname or pattern:[<pattern>,all,list,list-exclude,q,?]

2. At the prompt, enter the name of the path you want to exclude from dynamic multipathing.

3. Press Return.

If a path is specified, the corresponding disks are claimed in the OTHER_DISKS category and are not multipathed.

� To prevent VERITAS Volume Manager from applying dynamic multipathing to disks specified by a VIP:PID combination



Exclude VID:PID from DMPMenu: VolumeManager/Install/ExcludeDevices/VIDPID-DMP

Use this operation to prevent vxdmp from multipathing devices returning a specific VID:PID combination.

As a result of this operation, all disks that return VID:PID matching the specified combination will be claimed in the OTHER_DISKS category(i.e. they will not be multipathed by vxdmp). This operation can be reversed using the vxdiskadm command.

You can specify a VendorID:ProductID combination at the prompt. The specification can be as follows:

VID:PID where VID stands for Vendor ID PID stands for Product ID

Both VID and PID can have an optional ’*’ (asterisk) following them.



If a ’*’ follows VID, it will result in the exclusion of all disks returning Vendor ID starting with VID. The same is true for Product ID as well. Both VID and PID should be non NULL.

Some examples of VID:PID specification are:

all- Exclude all disksaaa:123- Exclude all disks having VID ‘aaa’ and PID ‘123’aaa*:123- Exclude all disks having VID starting with ‘aaa’ and

PID ‘123’aaa:123*- Exclude all disks having VID ‘aaa’ and PID starting

with ‘123’aaa:* - Exclude all disks having VID ‘aaa’ and any PID

Enter a VID:PID combination:[<pattern>,all,list,list-exclude,q,?]

2. At the prompt, enter the VID:PID combination of the disks you want to exclude from multipathing.

3. Press Return.

All disks returning a VID:PID combination are claimed in the OTHER_DISKS category and are not multipathed.

Note If you selected option 1 through 7, you must reboot the system and then re-run vxinstall for device exclusion to take effect. After the reboot for menu item 3 Prevent Multipathing/Suppress Devices, run vxinstall again to complete the installation.

� To list suppressed and non-multipathed devices


The list of devices that have either been suppressed from VERITAS Volume Manager’s view or have been excluded from dynamic multipathing appears.

Rebooting after vxinstallAfter you decide how you want the vxinstall program to process all of the disks attached to your system, you may have to reboot the system to make changes to your disk partitioning that cannot be made while your disks are in use. The way in which you chose to handle your disks during the vxinstall session determines whether a shutdown and reboot is required. If you chose to encapsulate any disks, you must reboot.

The vxinstall command informs you if and when a shutdown and reboot is necessary. Conduct the shutdown and reboot as soon as possible.



Note The setup you choose can require several reboots. Refer to “Installation Considerations” on page 9 for reboot planning issues.

When it is necessary to shut down and reboot your system, vxinstall displays a message similar to the following:

The system now must be shut down and rebooted in order tocontinue the reconfiguration.Shutdown and reboot now [y,n,q,?] (default: n)

If this message appears, respond in either of the following ways:

� Enter y to begin an immediate shutdown.

� Enter n to cause vxinstall to exit without starting a shutdown. If you select this option, it is your responsibility to shut down and reboot as soon as possible. Refer to “VERITAS Software Configuration Considerations” on page 9 for reboot planning issues.

Caution During the next one or more reboots, you may be asked several times if you wish to continue an operation. Press the Return key at all of these prompts to accept the default answer. If you select a different answer from the default for any of these prompts, or press q, the initialization can fail.

Confirming that VERITAS Volume Manager Processes Are Running

Once VERITAS Volume Manager is installed and you have rebooted your system, use the following command to confirm that key VxVM processes (vxconfigd, vxnotify, and vxrelocd) are running:

# ps -ef | grep vx

This command displays output similar to the following:

root 458 1 80 10:23:34 ? 0:00 vxrelocd rootroot 414 1 80 10:23:06 ? 0:03 vxconfigd -k -m enableroot 478 458 39 10:23:37 ? 0:00 vxrelocd rootroot 479 478 5 10:23:37 ? 0:00 vxnotify -f -w 15

Note If you have disabled Hot-Relocation, vxrelocd and vxnotify should not be shown as running.


Configuring VERITAS File System

Configuring VERITAS File SystemAfter installing VERITAS File System, you can create a file system on a disk slice or VERITAS Volume Manager volume with the mkfs command. Before you can use this 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/vfstab file.

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

Upgrading VxFS Disk LayoutsVERITAS 3.5 file systems employ disk layout Version 5, which allows the creation of file system sizes up to 32 terabytes. File systems created on VxFS 3.5 will by default use the new disk layout, Version 5. File systems larger than 1TB, however, necessarily use an 8K block size.

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

Use the vxupgrade command to upgrade an existing VxFS disk layout to disk layout 5 while the file system remains online:

# vxupgrade -n 5 /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 or higher layout. Use the fstyp -v device command to determine the layout version of your file system.


Verifying the VERITAS Database Edition Installation

Verifying Command InstallationVERITAS File System commands and utilities are installed in four directories:

These directory locations have changed from previous versions of VERITAS Database Edition. List these directories in your PATH environment variable to make the commands accessible. See “Environment Variables” on page 5 for the correct path settings.

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. Verify the kernel components installation by loading the modules using the modload command:

# modload /usr/kernel/drv/fdd# modload /usr/kernel/drv/qlog

2. Verify that the modules loaded by entering:

# modinfo | egrep 'vxfs|fdd|kaio|qlog|odm'

The modinfo command displays information about all modules loaded on the system. If vxfs is loaded, you see an entry corresponding to vxfs, for example:

34 1025ae1c 926 - 1 todmostek (tod module for Mostek M48T59)223 78656000 10d3bd 16 1 vxfs (VxFS 3.5_REV-beta04 (SunOS 5.8))224 7876a000 8e31 229 1 fdd (VxQIO 3.5_REV-beta04 Quick I/O )225 78774000 3c3e 178 1 kaio (kernel Async I/O)225 78774000 3c3e 178 1 kaio (kernel Async I/O for 32 bit com)239 7880c000 15480 20 1 odm (VRTS ODM 3.5,REV=beta02)

/opt/VRTSvxfs/sbin contains most VxFS-specific commands

/usr/lib/fs/vxfs/bin contains additional VxFS-aware commands for manipulating files with extents

/etc/fs/vxfs contains the VxFS mount command and QuickLog commands required to mount file systems

/usr/lib/fs/vxfs contains VxFS switch-out commands, used with the -F option on file system utilities (such as fsck). See fsck(1M) for more information.


Verifying the VERITAS Database Edition Installation

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. Continue with the next step to complete the process.

3. Reboot the system, using a command such as shutdown.

Note You only need to reboot the system once for all the VERITAS Database Edition packages. When you have installed all the packages, you can reboot one time to complete the process, including loading the VERITAS File System modules. Refer to “VERITAS Software Configuration Considerations” on page 9 for reboot planning issues.


High Availability Products
5 This chapter describes the High Availability (HA) version of VERITAS Database Edition for Oracle.

� “High Availability Product Overview” on page 77

� “VERITAS Database Edition/High Availability” on page 77

High Availability Product OverviewA High Availability (HA) version of VERITAS Database Edition for Oracle is available for customers who have high system-availability requirements. The HA product lets database administrators integrate multiple servers into high availability database configurations. These configurations provide continuous services if a server system or subsystem fails and significantly reduces the down time of Oracle databases caused by a system hardware or software failure.

VERITAS Database Edition/High AvailabilityIn addition to the products contained in the standard VERITAS Database Edition for Oracle package, the HA Edition incorporates the following VERITAS products:

� VERITAS Cluster ServerTM (VCS)

� VERITAS Cluster Server (VCS) Enterprise Agent for Oracle

� VERITAS Cluster Server (VCS) Agent for QuickLog

77

VERITAS Database Edition/High Availability

High Availability Packaging� VERITAS Cluster Server (VCS) is included on CD2 and consists of the following

packages:

- VRTSperl: VERITAS Perl for VRTSvcs

- VRTSvcs: VERITAS Cluster Server

- VRTSvcsag: VERITAS Cluster Server Bundled Agents

- VRTSvcsdc: VERITAS Cluster Server Documentation

- VRTSvcsmg: VERITAS Cluster Server Messages

- VRTSvcsmn: VERITAS Cluster Server Manual Pages

- VRTSvcsw: VERITAS Cluster Server Web GUI Engine

- VRTSweb: Cluster Manager (Web Console)

- VRTSgab: VERITAS Group Membership and Atomic Broadcast

- VRTSllt: VERITAS Low Latency Transport

- VRTScscm: VERITAS Cluster Manager (Java Console)

- WindowsClusterManager: Windows version of VRTScscm

� The VERITAS Cluster Server documentation set includes Portable Document Format (.pdf) versions of:

- vcs_ig.pdf, VERITAS Cluster Server Installation Guide

- vcs_notes.pdf, VERITAS Cluster Server Release Notes

- vcs_ug.pdf, VERITAS Cluster Server User’s Guide

- vcs_adg.pdf, VERITAS Cluster Server Agent Developer’s Guide

- vcs_appnote_a3x00.pdf, Application Note for Sun StorEdge A3x00 Disk Array

- vcs_appnote_a5000.pdf, Application Note for Sun StorEdge A5000 Disk Array

- vcs_appnote_e10kdr.pdf, Application Note: Sun Enterprise 10000 Dynamic Reconfiguration

- vcs_appnote_rdc.pdf, Application Note: Replicated Data Cluster Option for VCS

- vcs_barg.pdf, VERITAS Cluster Server Bundled Agents Reference Guide

� The VERITAS Cluster Server Agent for Oracle consists of the following packages:

- VRTSvcsor: VERITAS Cluster Server Oracle Enterprise Extension

- VRTSvcsql: VERITAS Cluster Server QuickLog Agent



- vcs_oracle.pdf: Portable Document Format (.pdf) version of the VERITAS Cluster Server Enterprise Agents for Database Edition for Oracle Installation and Configuration Guide

LicensingVERITAS Database Edition/HA for Oracle requires a separate license key.

Before you install the various components of VERITAS Database Edition/HA for Oracle, obtain a VERITAS Database Edition/HA license key from VERITAS. For information on obtaining license keys, see “Obtaining a License Key” on page 1. For more VCS license information, refer to your VCS documentation.

Installing

� To install VERITAS Database Edition/HA

1. Follow the installation procedures for VERITAS Database Edition for Oracle on each HA server as outlined in Chapter 2, “Installation and Deinstallation.”

2. Follow the steps outlined in the VERITAS Cluster Server Installation Guide and the VERITAS Cluster Server User’s Guide to install the VCS software and configure the VCS HA environment.

Note When you install VCS, the installvcs utility automatically discovers and uses the VERITAS Database Edition/HA license keys on each of the systems in the cluster.

3. Follow the steps outlined in the VERITAS Cluster Server Enterprise Agents for Database Edition for Oracle Installation and Configuration Guide to install and configure the VCS Oracle Agent and VCS QuickLog agent.

Note See the VERITAS Cluster Server Enterprise Agents for Database Edition for Oracle Installation and Configuration Guide for more information.

Chapter 5, High Availability Products 79



Installation Sample Output
A This appendix provides a sample of the output from an installation of the VERITAS Database Edition for Oracle.
Note Use this example for reference only—the output for each operating system version and installation environment differs slightly.

Sample Installation OutputThe following output is an example of a VERITAS Database Edition installation on a Solaris 9 operating system.

Use the following commands to view the VERITAS Database Edition packages on the CD:

# pwd/cdrom/storage_solutions_solaris_3.5cd2/ \

database_edition_for_oracle/pkgs

# lsbin VRTSdbed VRTSfspro VRTSobgui VRTSordoc VRTSvlic VRTSvmman \

VRTSvxfs VRTSvxvmPackages VRTSfsdoc VRTSob VRTSodm VRTSorgui VRTSvmdoc VRTSvmpro \

VRTSvxmsa win32

Type the VERITAS Database Edition for Oracle installation program name to install the software:

# ./installDBED

*****************************************************************Starting installation of VERITAS Database Edition for Oracle.*****************************************************************WARNING: The optional patch 110722-01 is not installed.

The above patches may be required to support specific hardware or operating environments. See the VERITAS Database Edition for Oracle Install Guide and Release Notes for further information.

81

Sample Installation Output

Press <Return> to continue ...

The following packages need to be installedfor VERITAS Database Edition for Oracle.

VRTSdbed is RequiredVRTSvlic is Required

VRTSvxvm is Required VRTSvxfs is Required VRTSodm is Required VRTSvmman is Optional VRTSvmdoc is Optional VRTSfsdoc is Optional VRTSordoc is Optional VRTSob is Optional VRTSvmpro is Optional VRTSfspro is Optional VRTSobgui is Optional VRTSorgui is Optional

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

Type y to install the VRTSdbed package:

Installing VRTSdbed.

Processing package instance <VRTSdbed> from</mnt/database_edition_for_oracle/pkgs>

VERITAS Database Edition for Oracle(Sparc) 3.5

VERITAS Database Edition for Oracle

Copyright © 1995^2002 VERITAS Software Corporation. All rights reserved.

VERITAS, VERITAS SOFTWARE, the VERITAS logo, Business Without Interruption, VERITAS The Data Availability Company, and VERITAS Database Edition 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.

## Processing package information.



## Processing system information. 11 package pathnames are already properly installed.## Verifying disk space requirements.

Installing VERITAS Database Edition for Oracle as <VRTSdbed>

## Executing preinstall script.## Installing part 1 of 1./etc/rc3.d/S90dbed_mon/etc/vx/vxdba/grow_lock/opt/VRTS/bin/dbed_checkconfig <symbolic link>/opt/VRTS/bin/dbed_clonedb <symbolic link>/opt/VRTS/bin/dbed_saveconfig <symbolic link>/opt/VRTS/bin/dbed_update <symbolic link>

long list of files installed...

/usr/lib/vxvm/voladm.d/help/plan.create.help/usr/lib/vxvm/voladm.d/help/plan.display.help/usr/lib/vxvm/voladm.d/help/plan.main.help/usr/lib/vxvm/voladm.d/help/stat.menu.help/usr/lib/vxvm/voladm.d/help/vxdba.info/usr/sbin/vxdba <symbolic link>[ verifying class <none> ]## Executing postinstall script.

Installation of <VRTSdbed> was successful.


Press Return to set VxDBA permissions:

**** Permission Granting for VxDBA Utility ****The VxDBA utility for database administration requires permissionchanges to allow database administrators (DBAs) access to thetools. The default settings at installation time for the/opt/VRTSdbed directory allows only the root user access to thedirectory. 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 login account name for DBA user: oracle

Appendix A, Installation Sample Output 83


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


Press Return to add important licensing information:

Installing VRTSvlic.

Processing package instance <VRTSvlic> from</mnt/database_edition_for_oracle/pkgs>

VERITAS License Utilities(sparc) 3.00.005VERITAS Software Corp

VERITAS License Utilities 3.00.005Using </> as the package base directory.## Processing package information.## Processing system information. 5 package pathnames are already properly installed.## Verifying disk space requirements.

Installing VERITAS License Utilities as <VRTSvlic>

## Installing part 1 of 1./etc/vx/licenses/db/dbacoralkl.txe/etc/vx/licenses/db/dbeddb2lkl.txe/etc/vx/licenses/db/dbedemclkl.txe/etc/vx/licenses/db/dbedoralkl.txe/etc/vx/licenses/db/file_def_spc.txe


[ verifying class <none> ]## Executing postinstall script.

Installation of <VRTSvlic> was successful.


Press Return to add important licensing information:

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 2.10, Build 4Copyright (C) VERITAS Software Corp 2002. All Rights reserved.

Using VERITAS License Manager API Version 2.10, Build 4

Enter the license key to continue installing the VERITAS Database Edition for Oracle packages. Only one license key is required to install this Edition.

Please enter your license key : 1234-1234-1234-1234-1234-1234

License key installed successfully for VERITAS Database Edition for Oracle

Input License key is an Editions key..

Installing keys for point products..

License Key installed successfully for VERITAS File System

License Key installed successfully for VERITAS Volume Manager

License Key installed successfully for VERITAS Cluster Server

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


Press Return to install the VRTSvxvm package:

Installing packages ...

Installing VRTSvxvm



Processing package instance <VRTSvxvm> from</mnt/database_edition_for_oracle/pkgs>

VERITAS Volume Manager, Binaries(sparc) 3.5Copyright (C) 2001 VERITAS Software Corporation. All Rights Reserved.VERITAS, VERITAS SOFTWARE, the VERITAS logo, Business Without Interruption,VERITAS The Data Availability Company and Volume Manager are trademarks or registered trademarks of VERITAS Software Corporation in the US and/or other countries. Other product names mentioned herein may be trademarks or registered trademarks of their respective companies.

Using </> as the package base directory.## Processing package information.## Processing system information. 27 package pathnames are already properly installed.## Verifying disk space requirements.

Installing VERITAS Volume Manager, Binaries as <VRTSvxvm>

## Executing preinstall script.## Installing part 1 of 1./etc/default/vxse/etc/init.d/vras-vradmind.sh/etc/init.d/vxnm-vxnetd/etc/init.d/vxrsyncd.sh/etc/init.d/vxvm-reconfig/etc/init.d/vxvm-recover


Adding vxdmp driver for SunOS version 5.9...

Adding vxio driver for SunOS version 5.9...Adding vxspec driver for SunOS version 5.9...Adding vxspec lines to /etc/devlink.tab...Adding vxdmp lines to /etc/devlink.tab...Running /usr/sbin/devlinks -t /etc/devlink.tab ...Adding vxio vxspec vxdmp lines to /etc/system...Copy liba5k.so.2 to /etc/vx/slib/liba5k_stub.so.2Copy libg_fc.so.2 to /etc/vx/slib/libg_fc_stub.so.2Copy libsocket.so.1 to /etc/vx...Copy libnsl.so.1 to /etc/vx...Copy libintl.so.1 to /etc/vx...



Copy libdevinfo.so.1 to /etc/vx...Copy libthread.so.1 to /etc/vx...Copy libc.so.1 to /etc/vx...Copy libmp.so.2 to /etc/vx...Copy liba5k.so.2 to /etc/vx...Copy libg_fc.so.2 to /etc/vx...Copy libdevice.so.1 to /etc/vx...Copy librt.so.1 to /etc/vx...Copy libnvpair.so.1 to /etc/vx...Copy libaio.so.1 to /etc/vx...Copy libmd5.so.1 to /etc/vx...Copy libc_psr.so.1 to /etc/vx...Copy libmd5_psr.so.1 to /etc/vx...Allocating port for Volume Replicator...Volume Replicator already installedUsing port: 4145A reboot is required to activate the newly installed daemons and drivers before using any VxVM utilities. cd to / directory and execute

shutdown -g0 -y -i6

Installation of <VRTSvxvm> was successful.


Press Return to install the VRTSvxfs package:

Installing VRTSvxfs

Processing package instance <VRTSvxfs> from</mnt/database_edition_for_oracle/pkgs/>

VERITAS File System(sparc) 3.5Copyright (c) 1991 - 2001 VERITAS SOFTWARE CORP. ALL RIGHTS RESERVED. THIS SOFTWARE IS THE PROPERTY OF AND IS LICENSED BY VERITAS SOFTWARE, AND/OR ITS SUPPLIERS.## Executing checkinstall script.Using </> as the package base directory.## Processing package information.## Processing system information. 30package pathnames are already properly installed.## Verifying disk space requirements.

Installing VERITAS File System as <VRTSvxfs>



## Installing part 1 of 1./dev/fdd <symbolic link>/dev/vxportal <symbolic link>/opt/VRTS/bin/cp <symbolic link>/opt/VRTS/bin/cpio <symbolic link>/opt/VRTS/bin/df <symbolic link>/opt/VRTS/bin/ff <symbolic link>


/kernel/fs/sparcv9/vxfs/opt/VRTSvxfs/lib/sparcv9/.libvxfsutil.so/opt/VRTSvxfs/lib/sparcv9/libvxfsutil.a/opt/VRTSvxms/lib/map/sparcv9/libvxfs.so/usr/kernel/drv/sparcv9/fdd/usr/kernel/drv/sparcv9/qlog[ verifying class <s29b64> ]

## Executing postinstall script.

System configuration files modified but vxportal driver not loaded or attached.

System configuration files modified but vxportal driver not loaded or attached.

System configuration files modified but fdd driver not loaded or attached.

System configuration files modified but fdd driver not loaded or attached.

System configuration files modified but qlog driver not loaded or attached.

System configuration files modified but qlog driver not loaded or attached.

VRTSvxfs: You must reboot the system after pkgadd.

Installation of <VRTSvxfs> was successful.

*** IMPORTANT NOTICE *** This machine must now be rebooted in order to ensure sane operation. Execute shutdown -y -i6 -g0 and wait for the "Console Login:" prompt.




Press Return to install the VRTSodm package:

Installing VRTSodm

Processing package instance <VRTSodm> from</mnt/database_edition_for_oracle/pkgs>

VERITAS Oracle Disk Manager(sparc) 3.5Copyright (c) 1999 - 2001 VERITAS SOFTWARE CORP. ALL RIGHTS RESERVED. THIS SOFTWARE IS THE PROPERTY OF AND IS LICENSED BY VERITAS SOFTWARE, AND/OR ITS SUPPLIERS.Using </> as the package base directory.## Processing package information.## Processing system information. 19 package pathnames are already properly installed.## Verifying disk space requirements.

Installing VERITAS Oracle Disk Manager as <VRTSodm>

## Installing part 1 of 1.

/etc/init.d/odm/etc/rc2.d/S92odm <symbolic link>[ verifying class <all> ]/opt/VRTS/man/man1/odmmkfile.1 <symbolic link>/opt/VRTS/man/man1/odmstat.1 <symbolic link>/opt/VRTSodm/man/man1/ktrace.1


/opt/VRTSodm/kernel/fs/sparcv9/odm/opt/VRTSodm/lib/sparcv9/libodm.so <symbolic link>/opt/VRTSodm/lib/sparcv9/libodm.so.1/opt/VRTSodm/sbin/sparcv9/ktrace/usr/kernel/fs/sparcv9/odm <symbolic link>/usr/lib/sparcv9/libodm.so <symbolic link>[ verifying class <s29b64> ]## Executing postinstall script.

Installation of <VRTSodm> was successful.




Press Return to install the VRTSvxmsa package:

system VRTSvxmsa VxMS - VERITAS Mapping Service, Application Libraries.

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

Installing VRTSvxmsa

Processing package instance <VRTSvxmsa> from </mnt/database_edition_for_oracle3.5/pkgs>

VxMS - VERITAS Mapping Service, Application Libraries.(sparc) 2.1

Copyright (c) 2002 VERITAS SOFTWARE CORP. ALL RIGHTS RESERVED.THIS SOFTWARE IS THE PROPERTY OF AND IS LICENSED BY VERITAS SOFTWARE, AND/OR ITS SUPPLIERS.

Installing VxMS for Solaris 9Using </opt> as the package base directory.## Processing package information.## Processing system information.## Verifying disk space requirements.

Installing VxMS - VERITAS Mapping Service, Application Libraries. as <VRTSvxmsa>

## Installing part 1 of 1./opt/VRTSvxms/lib/.vxms.rc/opt/VRTSvxms/lib/libmap.so/opt/VRTSvxms/lib/libvfutil.so/opt/VRTSvxms/lib/map/libdisk.so <symbolic link>/opt/VRTSvxms/lib/map/librawp.so/opt/VRTSvxms/msg/VfMMsgs_C[ verifying class <none> ]Installation of <VRTSvxmsa> was successful.


Press Return to install the VRTSvmman package:



system VRTSvmman VERITAS Volume Manager, Manual Pages

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

Installing VRTSvmman

Processing package instance <VRTSvmman> from</mnt/database_edition_for_oracle/pkgs>

VERITAS Volume Manager, Manual Pages(sparc) 3.5Copyright (C) 2001 VERITAS Software Corporation. All Rights Reserved. VERITAS, VERITAS SOFTWARE, the VERITAS logo, Business Without Interruption, VERITAS The Data Availability Company and Volume Manager are trademarks or registered trademarks of VERITAS Software Corporation in the US and/or other countries. Other product names mentioned herein may be trademarks or registered trademarks of their respective companies.Using </opt> as the package base directory.## Processing package information.## Processing system information.## Verifying disk space requirements.

Installing VERITAS Volume Manager, Manual Pages as <VRTSvmman>

## Installing part 1 of 1./opt/VRTS/man/man1m/vradmin.1m/opt/VRTS/man/man1m/vrnotify.1m/opt/VRTS/man/man1m/vrport.1m/opt/VRTS/man/man1m/vxapslice.1m/opt/VRTS/man/man1m/vxassist.1m/opt/VRTS/man/man1m/vxbootsetup.1m


/opt/VRTS/man/man1m/vxconfigd.7/opt/VRTS/man/man7/vxdmp.7/opt/VRTS/man/man7/vxinfo.7/opt/VRTS/man/man7/vxio.7/opt/VRTS/man/man7/vxiod.7/opt/VRTS/man/man7/vxtrace.7[ verifying class <none> ]

Installation of <VRTSvmman> was successful.




Press Return to install the VRTSvmdoc package:

system VRTSvmdoc VERITAS Volume Manager (user documentation)


Installing VRTSvmdoc

Processing package instance <VRTSvmdoc> from</mnt/database_edition_for_oracle/pkgs>

VERITAS Volume Manager (user documentation)(sparc) 3.5Copyright (C) 2001 VERITAS Software Corporation. All Rights Reserved. VERITAS, VERITAS SOFTWARE, the VERITAS logo, Business Without Interruption, VERITAS The Data Availability Company and Volume Manager are trademarks or registered trademarks of VERITAS Software Corporation in the US and/or other countries. Other product names mentioned herein may be trademarks or registered trademarks of their respective companies.

Using </opt> as the package base directory.## Processing package information.## Processing system information.## Verifying disk space requirements.

Installing VERITAS Volume Manager (user documentation) as <VRTSvmdoc>

## Installing part 1 of 1.[ verifying class <none> ]/opt/VRTSvxvm/docs/pitc.pdf/opt/VRTSvxvm/docs/vxvm_ag.pdf/opt/VRTSvxvm/docs/vxvm_hwnotes.pdf/opt/VRTSvxvm/docs/vxvm_ig.pdf/opt/VRTSvxvm/docs/vxvm_tshoot.pdf/opt/VRTSvxvm/docs/vxvm_ug.pdf[ verifying class <PDF> ][ verifying class <PDF> ]

Installation of <VRTSvmdoc> was successful.




Press Return to install the VRTSfsdoc package:

system VRTSfsdoc VERITAS File System Documentation


Installing VRTSfsdoc

Processing package instance <VRTSfsdoc> from</mnt/database_edition_for_oracle/pkgs>

VERITAS File System Documentation(sparc) 3.5Copyright (c) 1991 - 2000 VERITAS SOFTWARE CORP. ALL RIGHTS RESERVED. THIS SOFTWARE IS THE PROPERTY OF AND IS LICENSED BY VERITAS SOFTWARE, AND/OR ITS SUPPLIERS. Using </opt> as the package base directory.## Processing package information.## Processing system information.## Verifying disk space requirements.

Installing VERITAS File System Documentation as <VRTSfsdoc>

## Installing part 1 of 1./opt/VRTSfsdoc/vxfs_ag.pdf/opt/VRTSfsdoc/vxfs_ig.pdf[ verifying class <all> ]

Installation of <VRTSfsdoc> was successful.


Press Return to install the VRTSordoc package:

system VRTSordoc VERITAS Database Edition for Oracle Documentation


Installing VRTSordoc

Processing package instance <VRTSordoc> from</mnt/database_edition_for_oracle/pkgs>



VERITAS Database Edition for Oracle Documentation(N/A) 3.5

VERITAS Database Edition for Oracle

(C) 2001 VERITAS Software Corporation. All Rights Reserved.

VERITAS is a registered trademark of VERITAS Software Corporationin the U.S. and other countries. The VERITAS logo, VERITAS StorageEdition and VERITAS Database Edition are trademarks of VERITASSoftware Corporation in the U.S. and other countries. Other product names mentioned herein may be trademarks or registered trademarks of their respective companies.

1 PostScript 2 PDF

Select the document formats to be installed (default: all) [?,??,q]:

Press Return to install all document formats (default).

[PostScript] [PDF] will be installed.## Processing package information.## Processing system information. 1 package pathname is already properly installed.## Verifying disk space requirements.

Installing VERITAS Database Edition for Oracle Documentation as <VRTSordoc>

## Installing part 1 of 1.[ verifying class <none> ]/opt/VRTSordoc/dbed_oracle_admin/dbed_dbag.pdf/opt/VRTSordoc/dbed_oracle_install/dbed_ig.pdf[ verifying class <PDF> ]

Installation of <VRTSordoc> was successful.


Press Return to install the VRTSob package:



You have the FlashSnap license. If you want to use the Database FlashSnap feature you need to install VRTSob. Do you want to install it? y

Installing VRTSob

Processing package instance <VRTSob> from</mnt/database_edition_for_oracle/pkgs>

VERITAS Enterprise Administrator Service(sparc) 3.0Copyright (c) 2000 VERITAS Software Corporation.ALL RIGHTS RESERVED.THIS SOFTWARE IS THE PROPERTY OF AND IS LICENSED BY VERITAS SOFTWARE, AND/OR ITS SUPPLIERS.## Executing checkinstall script.Checking for previous VRTSob installations...Continuing with installing VRTSob 3.0.2.257Using </opt/VRTSob> as the package base directory.## Processing package information.## Processing system information. 2 package pathnames are already properly installed.## Verifying disk space requirements.

Installing VERITAS Enterprise Administrator Service as <VRTSob>

## Executing preinstall script.## Installing part 1 of 1./opt/VRTS/man/man1m/vxalerttype.1m/opt/VRTS/man/man1m/vxobjecttype.1m/opt/VRTS/man/man1m/vxregctl.1m/opt/VRTS/man/man1m/vxsvc.1m/opt/VRTSob/README.server/opt/VRTSob/bin/alerttypes.dtd


/opt/VRTSob/providers/alertlog/alerror.1033.cat/opt/VRTSob/providers/alertlog/alertlog.so/opt/VRTSob/providers/controlpanel/controlpanel.so.1/opt/VRTSob/providers/genericlogger/libgenericlogger.so[ verifying class <none> ]## Executing postinstall script.

Installation of <VRTSob> was successful.




Press Return to install the VRTSvmpro package:

You have the FlashSnap license. If you want to use the Database FlashSnap feature you need to install VRTSvmpro. Do you want to install it? y

Installing VRTSvmpro

Processing package instance <VRTSvmpro> from</mnt/database_edition_for_oracle/pkgs>

VERITAS Volume Manager Management Services Provider(sparc) 3.5Copyright (c) 1990-2002 VERITAS Software Corporation. ALL RIGHTS RESERVED. THIS SOFTWARE IS THE PROPERTY OF AND IS LICENSED BY VERITAS SOFTWARE, AND/OR ITS SUPPLIERS.## Executing checkinstall script.Checking for previous VRTSvmpro installations... done

Using </opt> as the package base directory.## Processing package information.## Processing system information.## Verifying disk space requirements.

Installing VERITAS Volume Manager Management Services Provider as <VRTSvmpro>

## Installing part 1 of 1./opt/VRTSvmpro/config/vmprov.sh/opt/VRTSvmpro/config/vxvm.xml/opt/VRTSvmpro/extensions/VmLibResourceBundle.en.jar/opt/VRTSvmpro/extensions/VmResourceBundle.en.jar/opt/VRTSvmpro/extensions/VxSearchCE.jar/opt/VRTSvmpro/extensions/VxVmCE.jar/opt/VRTSvmpro/extensions/VxVmHelp.en.jar/opt/VRTSvmpro/extensions/VxVmOneguiResourceBundle.en.jar/opt/VRTSvmpro/extensions/VxVmVxFsResourceBundle.en.jar/opt/VRTSvmpro/vxvm/3.5/lib/vxvmprovider.so/opt/VRTSvmpro/vxvm/lib/searchprovider.so[ verifying class <none> ]## Executing postinstall script.



Adding VM provider to Enterprise Administrator Service registry file... done.Adding VM objects to VERITAS Enterprise Administrator Service... done.

To use the VM Provider you must restart the VERITAS Enterprise Administrator Service server. Refer to the man page for vxsvc(1M).

VM provider configuration installation complete.

Installation of <VRTSvmpro> was successful.


Press Return to install the VRTSfspro package:

application VRTSfspro VERITAS File System Management Services Provider


Installing VRTSfspro

Processing package instance <VRTSfspro> from</mnt/database_edition_for_oracle/pkgs>

VERITAS File System Management Services Provider(sparc) 3.5Copyright (c) 2002 VERITAS Software Corporation.ALL RIGHTS RESERVED.THIS SOFTWARE IS THE PROPERTY OF AND IS LICENSED BY VERITAS SOFTWARE, AND/OR ITS SUPPLIERS.

This package VRTSfspro will stop and restart the VERITAS Object Bus server.

Continue installation? [y,n,q,?] (default: n): y

## Executing checkinstall script.Checking for previous VRTSfspro installations... done

Using </opt> as the package base directory.## Processing package information.



## Processing system information.## Verifying disk space requirements.

Installing VERITAS File System Management Services Provider as <VRTSfspro>

## Installing part 1 of 1./opt/VRTSfspro/config/fspro.sh/opt/VRTSfspro/extensions/VxFsCE.jar/opt/VRTSfspro/extensions/VxFsHelp.en.jar/opt/VRTSfspro/extensions/VxFsOneguiResourceBundle.en.jar/opt/VRTSfspro/extensions/VxFsResourceBundle.en.jar/opt/VRTSfspro/extensions/VxFsVmLibResourceBundle.en.jar/opt/VRTSfspro/extensions/VxFsVmResourceBundle.en.jar/opt/VRTSfspro/extensions/VxSearchCE.jar/opt/VRTSfspro/lib/osfs_provider.so/opt/VRTSfspro/lib/searchprovider.so/opt/VRTSfspro/lib/vxfs_provider.so/opt/VRTSfspro/msgcats/system/IsisSkin/java/1033/osfs.1033.cat/opt/VRTSfspro/msgcats/system/IsisSkin/java/1033/vxfs.1033.cat[ verifying class <none> ]## Executing postinstall script.

Adding VRTSfspro to VERITAS Enterprise Administrator Service Registry ...done

To use the VRTSfspro you must restart the VERITAS Enterprise Administrator Service server. Refer to the man page for vxsvc(1M).

VRTSfspro configuration installation complete.

Installation of <VRTSfspro> was successful.


Press Return to install the VRTSobgui package:

application VRTSobgui VERITAS Enterprise Administrator


Installing VRTSobgui

Processing package instance <VRTSobgui> from



</mnt/database_edition_for_oracle/pkgs>

VERITAS Enterprise Administrator(sparc) 3.0Copyright (c) 2002 VERITAS Software Corporation. ALL RIGHTS RESERVED. THIS SOFTWARE IS THE PROPERTY OF AND IS LICENSED BY VERITAS SOFTWARE, AND/OR ITS SUPPLIERS.## Executing checkinstall script.Checking for previous VRTSobgui installations...Using </opt/VRTSob> as the package base directory.## Processing package information.## Processing system information. 5 package pathnames are already properly installed.## Verifying disk space requirements.

Installing VERITAS Enterprise Administrator as <VRTSobgui>

Executing preinstall script.Installing part 1 of 1./opt/VRTS/man/man1m/vea.1m/opt/VRTSob/README.client/opt/VRTSob/bin/vea/opt/VRTSob/copyright.vea/opt/VRTSob/jre.tar/opt/VRTSob/lib/OBGUI.jar/opt/VRTSob/lib/VxHelpViewer100.jar/opt/VRTSob/lib/cat/resource.jar/opt/VRTSob/lib/ci.jar/opt/VRTSob/lib/cicustom.jar/opt/VRTSob/lib/jh.jar[ verifying class <none> ]## Executing postinstall script.

Installation of <VRTSobgui> was successful.


Press Return to install the VRTSorgui package:

application VRTSorgui VERITAS Database Edition Graphical User Interface for Oracle


Installing VRTSorgui



Processing package instance <VRTSorgui> from</mnt/database_edition_for_oracle/pkgs>

VERITAS Database Edition Graphical User Interface for Oracle(Sparc) 3.5VERITAS Database Edition for Oracle

(C) 2001^2002 VERITAS Software Corporation. All Rights Reserved.

VERITAS is a registered trademark of VERITAS Software Corporationin the U.S. and other countries. The VERITAS logo, VERITAS StorageEdition and VERITAS Database Edition are trademarks of VERITASSoftware Corporation in the U.S. and other countries. Other product names mentioned herein may be trademarks or registered trademarks of their respective companies.

## Executing checkinstall script.Checking for previous VRTSorgui installations... done

## Processing package information.## Processing system information. 6package pathnames are already properly installed.## Verifying disk space requirements.

Installing VERITAS Database Edition Graphical User Interface for Oracle as <VRTSorgui>

## Installing part 1 of 1./opt/VRTS/bin/vxdbagui <symbolic link>/opt/VRTS/bin/vxdbedora.config <symbolic link>/opt/VRTS/bin/vxdbedusr <symbolic link>/opt/VRTS/bin/vxdbtok <symbolic link>/opt/VRTS/man/man1m/vxdbedusr.1m/opt/VRTSorgui/bin/vxdbagui/opt/VRTSorgui/bin/vxdbedora.config/opt/VRTSorgui/bin/vxdbedusr/opt/VRTSorgui/bin/vxdbtok/opt/VRTSorgui/inc/vxdbext.h/opt/VRTSorgui/lib/SchedUI210.jar/opt/VRTSorgui/lib/VxdbedExtension.jar/opt/VRTSorgui/lib/pv.jar/opt/VRTSorgui/lib/vxdbedora_56.so.3/opt/VRTSorgui/lib/vxdbedora_57.so.3/opt/VRTSorgui/lib/vxdbedora_58.so.3/opt/VRTSorgui/lib/vxdbedora_59.so.3



/opt/VRTSorgui/man/man1m <symbolic link>/usr/lib/vxvm/voladm.d/help/vxdbedusr.help/usr/sbin/vxdbagui <symbolic link>[ verifying class <none> ]## Executing postinstall script.

Registering Database Edition provider for Oracle with VERITAS Integration Platform

Installation of <VRTSorgui> was successful.


Press Return to complete the installation:

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

VRTSorgui VRTSobgui VRTSfspro VRTSvmpro VRTSob VRTSordoc VRTSfsdoc VRTSvmdoc VRTSvmman VRTSodm

VRTSvxmsa VRTSvxfs VRTSvxvm VRTSvlic VRTSdbed



Use the following commands to list the packages you installed from the VERITAS Database Edition for Oracle CD:

# cd /var/sadm/pkg# pkginfo -l V* | egrep "NAME|VERSION"

NAME: VERITAS Database Edition for Oracle VERSION: 3.5 NAME: VERITAS File System Documentation VERSION: 3.5 NAME: VERITAS File System Management Services Provider VERSION: 3.5 NAME: VERITAS Enterprise Administrator Service VERSION: 3.0 NAME: VERITAS Enterprise Administrator VERSION: 3.0 NAME: VERITAS Oracle Disk Manager VERSION: 3.5 NAME: VERITAS Database Edition for Oracle Documentation VERSION: 3.5 NAME: VERITAS Database Edition Graphical User Interface for

Oracle VERSION: 3.5 NAME: VERITAS Database Edition for Sybase (Solaris 2.6, 7, and

8) VERSION: 1.5 NAME: VERITAS Database Edition for Sybase Documentation VERSION: 1.5 NAME: VERITAS License Utilities VERSION: 3.00.005 NAME: VERITAS Volume Manager (user documentation) VERSION: 3.5 NAME: VERITAS Volume Manager, Manual Pages VERSION: 3.5 NAME: VERITAS Volume Manager Management Services Provider VERSION: 3.5 NAME: VERITAS File System VERSION: 3.5 NAME: VxMS - VERITAS Mapping Service, Application Libraries. VERSION: 2.1 NAME: VERITAS Volume Manager, Binaries VERSION: 3.5


Date post:	13-Mar-2018
Category:	Documents
Upload:	lamcong
View:	220 times
Download:	3 times