Storage Foundation for Oracle® RAC 7.4.1 Configuration and Upgrade Guide - Solaris
- Section I. Configuring SF Oracle RAC
- Preparing to configure SF Oracle RAC
- Configuring SF Oracle RAC using the script-based installer
- Configuring the SF Oracle RAC components using the script-based installer
- Configuring the SF Oracle RAC cluster
- Configuring SF Oracle RAC in secure mode
- Configuring a secure cluster node by node
- Configuring the SF Oracle RAC cluster
- Setting up disk-based I/O fencing using installer
- Setting up server-based I/O fencing using installer
- Configuring the SF Oracle RAC components using the script-based installer
- Performing an automated SF Oracle RAC configuration
- Section II. Post-installation and configuration tasks
- Verifying the installation
- Performing additional post-installation and configuration tasks
- Section III. Upgrade of SF Oracle RAC
- Planning to upgrade SF Oracle RAC
- Performing a full upgrade of SF Oracle RAC using the product installer
- Performing an automated full upgrade of SF Oracle RAC using response files
- Performing a phased upgrade of SF Oracle RAC
- Performing a phased upgrade of SF Oracle RAC from version 6.2.1 and later release
- Performing a rolling upgrade of SF Oracle RAC
- Upgrading SF Oracle RAC using Live Upgrade or Boot Environment upgrade
- Performing post-upgrade tasks
- Section IV. Installation and upgrade of Oracle RAC
- Before installing Oracle RAC
- Preparing to install Oracle RAC using the SF Oracle RAC installer or manually
- Creating users and groups for Oracle RAC
- Creating storage for OCR and voting disk
- Configuring private IP addresses for Oracle RAC 11.2.0.1
- Configuring private IP addresses for Oracle RAC 11.2.0.2 and later versions
- Installing Oracle RAC
- Performing an automated Oracle RAC installation
- Performing Oracle RAC post-installation tasks
- Configuring the CSSD resource
- Relinking the SF Oracle RAC libraries with Oracle RAC
- Configuring VCS service groups for Oracle RAC
- Upgrading Oracle RAC
- Before installing Oracle RAC
- Section V. Adding and removing nodes
- Adding a node to SF Oracle RAC clusters
- Adding a node to a cluster using the Veritas InfoScale installer
- Adding the node to a cluster manually
- Setting up the node to run in secure mode
- Configuring server-based fencing on the new node
- Preparing the new node manually for installing Oracle RAC
- Adding a node to the cluster using the SF Oracle RAC response file
- Configuring private IP addresses for Oracle RAC 11.2.0.2 and later versions on the new node
- Removing a node from SF Oracle RAC clusters
- Adding a node to SF Oracle RAC clusters
- Section VI. Configuration of disaster recovery environments
- Configuring disaster recovery environments
- Configuring disaster recovery environments
- Section VII. Installation reference
- Appendix A. Installation scripts
- Appendix B. Tunable files for installation
- Appendix C. Sample installation and configuration values
- SF Oracle RAC worksheet
- Appendix D. Configuration files
- Sample configuration files
- Sample configuration files for CP server
- Appendix E. Configuring the secure shell or the remote shell for communications
- Appendix F. Automatic Storage Management
- Appendix G. Creating a test database
- Appendix H. High availability agent information
- About agents
- CVMCluster agent
- CVMVxconfigd agent
- CVMVolDg agent
- CFSMount agent
- CFSfsckd agent
- PrivNIC agent
- MultiPrivNIC agent
- CSSD agent
- VCS agents for Oracle
- Oracle agent functions
- Resource type definition for the Oracle agent
- Resource type definition for the Netlsnr agent
- Resource type definition for the ASMDG agent
- Oracle agent functions
- CRSResource agent
- Appendix I. SF Oracle RAC deployment scenarios
- Configuration diagrams for setting up server-based I/O fencing
Tunables value parameter definitions
When you create a tunables file for the installer you can only use the parameters in the following list.
Prior to making any updates to the tunables, refer to the Storage Foundation Cluster File System High Availability Administrator's Guide for detailed information on product tunable ranges and recommendations.
Table: Supported tunable parameters describes the supported tunable parameters that can be specified in a tunables file.
Table: Supported tunable parameters
Tunable | Description |
---|---|
autoreminor | (Veritas Volume Manager) Enable reminoring in case of conflicts during disk group import. |
autostartvolumes | (Veritas Volume Manager) Enable the automatic recovery of volumes. |
dmp_cache_open | (Dynamic Multi-Pathing) Whether the first open on a device performed by an array support library (ASL) is cached. |
dmp_daemon_count | (Dynamic Multi-Pathing) The number of kernel threads for DMP administrative tasks. |
dmp_delayq_interval | (Dynamic Multi-Pathing) The time interval for which DMP delays the error processing if the device is busy. |
dmp_fast_recovery | (Dynamic Multi-Pathing) Whether DMP should attempt to obtain SCSI error information directly from the HBA interface. This tunable must be set after Dynamic Multi-Pathing is started. |
dmp_health_time | (Dynamic Multi-Pathing) The time in seconds for which a path must stay healthy. |
dmp_log_level | (Dynamic Multi-Pathing) The level of detail to which DMP console messages are displayed. |
dmp_low_impact_probe | (Dynamic Multi-Pathing) Whether the low impact path probing feature is enabled. |
dmp_lun_retry_timeout | (Dynamic Multi-Pathing) The retry period for handling transient errors. |
dmp_monitor_fabric | (Dynamic Multi-Pathing) Whether the Event Source daemon (vxesd) uses the Storage Networking Industry Association (SNIA) HBA API. This tunable must be set after Dynamic Multi-Pathing is started. |
dmp_monitor_ownership | (Dynamic Multi-Pathing) Whether the dynamic change in LUN ownership is monitored. |
dmp_native_multipathing | (Dynamic Multi-Pathing) Whether DMP will intercept the I/Os directly on the raw OS paths or not. |
dmp_native_support | (Dynamic Multi-Pathing) Whether DMP does multi-pathing for native devices. |
dmp_path_age | (Dynamic Multi-Pathing) The time for which an intermittently failing path needs to be monitored before DMP marks it as healthy. |
dmp_pathswitch_blks_shift | (Dynamic Multi-Pathing) The default number of contiguous I/O blocks sent along a DMP path to an array before switching to the next available path. |
dmp_probe_idle_lun | (Dynamic Multi-Pathing) Whether the path restoration kernel thread probes idle LUNs. |
dmp_probe_threshold | (Dynamic Multi-Pathing) The number of paths will be probed by the restore daemon. |
dmp_restore_cycles | (Dynamic Multi-Pathing) The number of cycles between running the check_all policy when the restore policy is check_periodic. |
dmp_restore_interval | (Dynamic Multi-Pathing) The time interval in seconds the restore daemon analyzes the condition of paths. |
dmp_restore_policy | (Dynamic Multi-Pathing) The policy used by DMP path restoration thread. |
dmp_restore_state | (Dynamic Multi-Pathing) Whether kernel thread for DMP path restoration is started. |
dmp_retry_count | (Dynamic Multi-Pathing) The number of times a path reports a path busy error consecutively before DMP marks the path as failed. |
dmp_scsi_timeout | (Dynamic Multi-Pathing) The timeout value for any SCSI command sent via DMP. |
dmp_sfg_threshold | (Dynamic Multi-Pathing) The status of the subpaths failover group (SFG) feature. |
dmp_stat_interval | (Dynamic Multi-Pathing) The time interval between gathering DMP statistics. |
fssmartmovethreshold | (Veritas Volume Manager) The file system usage threshold for SmartMove (percent). This tunable must be set after Veritas Volume Manager is started. |
max_diskq | (Veritas File System) Specifies the maximum disk queue generated by a single file. The installer can only set the system default value of max_diskq. Refer to the tunefstab(4) manual page for setting this tunable for a specified block device. |
read_ahead | (Veritas File System) The 0 value disables read ahead functionality, the 1 value (default) retains traditional sequential read ahead behavior, and the 2 value enables enhanced read ahead for all reads. The installer can only set the system default value of read_ahead. Refer to the tunefstab(4) manual page for setting this tunable for a specified block device. |
read_nstream | (Veritas File System) The number of parallel read requests of size read_pref_io that can be outstanding at one time. The installer can only set the system default value of read_nstream. Refer to the tunefstab(4) manual page for setting this tunable for a specified block device. |
read_pref_io | (Veritas File System) The preferred read request size. The installer can only set the system default value of read_pref_io. Refer to the tunefstab(4) manual page for setting this tunable for a specified block device. |
reclaim_on_delete_start_time | (Veritas Volume Manager) Time of day to start reclamation for deleted volumes. This tunable must be set after Veritas Volume Manager is started. |
reclaim_on_delete_wait_period | (Veritas Volume Manager) Days to wait before starting reclamation for deleted volumes. This tunable must be set after Veritas Volume Manager is started. |
same_key_for_alldgs | (Veritas Volume Manager) Use the same fencing key for all disk groups. This tunable must be set after Veritas Volume Manager is started. |
sharedminorstart | (Veritas Volume Manager) Start of range to use for minor numbers for shared disk groups. This tunable must be set after Veritas Volume Manager is started. |
storage_connectivity | (Veritas Volume Manager) The CVM storage connectivity type. This tunable must be set after Veritas Volume Manager is started. |
usefssmartmove | (Veritas Volume Manager) Configure SmartMove feature (all, thinonly, none). This tunable must be set after Veritas Volume Manager is started. |
vol_cmpres_enabled | (Veritas Volume Manager) Allow enabling compression for Volume Replicator. |
vol_cmpres_threads | (Veritas Volume Manager) Maximum number of compression threads for Volume Replicator. |
vol_default_iodelay | (Veritas Volume Manager) Time to pause between I/O requests from VxVM utilities (10ms units). This tunable requires a system reboot to take effect. |
vol_fmr_logsz | (Veritas Volume Manager) Maximum size of bitmap Fast Mirror Resync uses to track changed blocks (KBytes). This tunable requires a system reboot to take effect. |
vol_max_adminio_poolsz | (Veritas Volume Manager) Maximum amount of memory used by VxVM admin I/O's (bytes). This tunable requires a system reboot to take effect. |
vol_max_nmpool_sz | (Veritas Volume Manager) Maximum name pool size (bytes). |
vol_max_rdback_sz | (Veritas Volume Manager) Storage Record readback pool maximum (bytes). |
vol_max_wrspool_sz | (Veritas Volume Manager) Maximum memory used in clustered version of Volume Replicator . |
vol_maxio | (Veritas Volume Manager) Maximum size of logical VxVM I/O operations (kBytes). This tunable requires a system reboot to take effect. |
vol_maxioctl | (Veritas Volume Manager) Maximum size of data passed into the VxVM ioctl calls (bytes). This tunable requires a system reboot to take effect. |
vol_maxparallelio | (Veritas Volume Manager) Number of I/O operations vxconfigd can request at one time. This tunable requires a system reboot to take effect. |
vol_maxspecialio | (Veritas Volume Manager) Maximum size of a VxVM I/O operation issued by an ioctl call (kBytes). This tunable requires a system reboot to take effect. |
vol_min_lowmem_sz | (Veritas Volume Manager) Low water mark for memory (bytes). |
vol_nm_hb_timeout | (Veritas Volume Manager) Volume Replicator timeout value (ticks). |
vol_rvio_maxpool_sz | (Veritas Volume Manager) Maximum memory requested by Volume Replicator (bytes). |
vol_stats_enable | (Veritas Volume Manager) Enable VxVM I/O stat collection. |
vol_subdisk_num | (Veritas Volume Manager) Maximum number of subdisks attached to a single VxVM plex. This tunable requires a system reboot to take effect. |
voldrl_max_drtregs | (Veritas Volume Manager) Maximum number of dirty VxVM regions. This tunable requires a system reboot to take effect. |
voldrl_max_seq_dirty | (Veritas Volume Manager) Maximum number of dirty regions in sequential mode. This tunable requires a system reboot to take effect. |
voldrl_min_regionsz | (Veritas Volume Manager) Minimum size of a VxVM Dirty Region Logging (DRL) region (kBytes). This tunable requires a system reboot to take effect. |
voldrl_volumemax_drtregs | (Veritas Volume Manager) Max per volume dirty regions in log-plex DRL. |
voldrl_volumemax_drtregs_20 | (Veritas Volume Manager) Max per volume dirty regions in DCO version 20. |
voldrl_dirty_regions | (Veritas Volume Manager) Number of regions cached for DCO version 30. |
voliomem_chunk_size | (Veritas Volume Manager) Size of VxVM memory allocation requests (bytes). This tunable requires a system reboot to take effect. |
voliomem_maxpool_sz | (Veritas Volume Manager) Maximum amount of memory used by VxVM (bytes). This tunable requires a system reboot to take effect. |
voliot_errbuf_dflt | (Veritas Volume Manager) Size of a VxVM error trace buffer (bytes). This tunable requires a system reboot to take effect. |
voliot_iobuf_limit | (Veritas Volume Manager) Maximum total size of all VxVM I/O trace buffers (bytes). This tunable requires a system reboot to take effect. |
voliot_iobuf_max | (Veritas Volume Manager) Maximum size of a VxVM I/O trace buffer (bytes). This tunable requires a system reboot to take effect. |
voliot_max_open | (Veritas Volume Manager) Maximum number of VxVM trace channels available for vxtrace commands. This tunable requires a system reboot to take effect. |
volpagemod_max_memsz | (Veritas Volume Manager) Maximum paging module memory used by Instant Snapshots (Kbytes). |
volraid_rsrtransmax | (Veritas Volume Manager) Maximum number of VxVM RAID-5 transient reconstruct operations in parallel. This tunable requires a system reboot to take effect. |
vxfs_ninode | (Veritas File System) Number of entries in the VxFS inode table. This tunable requires a system reboot to take effect. |
write_nstream | (Veritas File System) The number of parallel write requests of size write_pref_io that can be outstanding at one time. The installer can only set the system default value of write_nstream. Refer to the tunefstab(4) manual page for setting this tunable for a specified block device. |
write_pref_io | (Veritas File System) The preferred write request size. The installer can only set the system default value of write_pref_io. Refer to the tunefstab(4) manual page for setting this tunable for a specified block device. |