Veritas InfoScale™ 7.4.2 Installation Guide - AIX
- Section I. Planning and preparation
- Introducing Veritas InfoScale
- Licensing Veritas InfoScale
- System requirements
- Preparing to install
- Mounting the ISO image
- Setting up ssh or rsh for inter-system communications
- Obtaining installer patches
- Disabling external network connection attempts
- Verifying the systems before installation
- Setting up the private network
- Setting up shared storage
- Synchronizing time settings on cluster nodes
- Configuring LLT interconnects to use Jumbo Frames
- Planning the installation setup for SF Oracle RAC systems
- Updating the SCSI reserve ODM attribute settings for VIOS
- Section II. Installation of Veritas InfoScale
- Installing Veritas InfoScale using the installer
- Installing Veritas InfoScale using response files
- Installing Veritas Infoscale using operating system-specific methods
- Completing the post installation tasks
- Section III. Uninstallation of Veritas InfoScale
- Section IV. Installation reference
- Appendix A. Installation scripts
- Appendix B. Tunable files for installation
- About setting tunable parameters using the installer or a response file
- Setting tunables for an installation, configuration, or upgrade
- Setting tunables with no other installer-related operations
- Setting tunables with an un-integrated response file
- Preparing the tunables file
- Setting parameters for the tunables file
- Tunables value parameter definitions
- Appendix C. Troubleshooting installation issues
Planning for Oracle RAC ASM over CVM
Review the following information on storage support provided by Oracle RAC ASM:
Supported by ASM | ASM provides storage for data files, control files, online redo logs and archive log files, and backup files. Starting with Oracle RAC 11g Release 2, ASM also supports storage for OCR and voting disk. |
Not supported by ASM | Oracle RAC 11g Release 2 and later versions: ASM does not support Oracle binaries, trace files, alert logs, export files, tar files, core files, and application binaries on ASM. |
The following practices offer high availability and better performance:
Use CVM mirrored volumes with dynamic multi-pathing for creating ASM disk groups. Select external redundancy while creating ASM disk groups.
The CVM raw volumes used for ASM must be used exclusively for ASM. Do not use these volumes for any other purpose, such as creation of file systems. Creating file systems on CVM raw volumes used with ASM may cause data corruption.
Do not link the Veritas ODM library when databases are created on ASM. ODM is a disk management interface for data files that reside on the Veritas File System.
Use a minimum of two Oracle RAC ASM disk groups. Store the data files, one set of redo logs, and one set of control files on one disk group. Store the Flash Recovery Area, archive logs, and a second set of redo logs and control files on the second disk group.
For more information, see Oracle RAC's ASM best practices document.
Do not configure DMP meta nodes as ASM disks for creating ASM disk groups. Access to DMP meta nodes must be configured to take place through CVM.
Do not combine DMP with other multi-pathing software in the cluster.
Do not use coordinator disks, which are configured for I/O fencing, as ASM disks. I/O fencing disks should not be imported or used for data.
Volumes presented to a particular ASM disk group should be of the same speed and type.