Veritas InfoScale™ 7.0 Release Notes - Solaris
- About this document
- Important release information
- About the Veritas InfoScale product suite
- Licensing Veritas InfoScale
- About Symantec Operations Readiness Tools
- Changes introduced in 7.0
- Licensing changes for InfoScale 7.0
- Changes related to installation and upgrade
- System requirements
- Fixed Issues
- Known Issues
- Issues related to installation and upgrade
- Storage Foundation known issues
- Dynamic Multi-Pathing known issues
- Veritas Volume Manager known issues
- Virtualization known issues
- Veritas File System known issues
- Replication known issues
- Cluster Server known issues
- Operational issues for VCS
- Issues related to the VCS engine
- Issues related to the bundled agents
- Issues related to the VCS database agents
- Issues related to the agent framework
- Issues related to Intelligent Monitoring Framework (IMF)
- Issues related to global clusters
- Issues related to the Cluster Manager (Java Console)
- VCS Cluster Configuration wizard issues
- LLT known issues
- I/O fencing known issues
- GAB known issues
- Operational issues for VCS
- Storage Foundation and High Availability known issues
- Storage Foundation Cluster File System High Availability known issues
- Storage Foundation for Oracle RAC known issues
- Oracle RAC known issues
- Storage Foundation Oracle RAC issues
- Storage Foundation for Databases (SFDB) tools known issues
- Storage Foundation for Sybase ASE CE known issues
- Issues related to installation and upgrade
- Software Limitations
- Storage Foundation software limitations
- Dynamic Multi-Pathing software limitations
- Veritas Volume Manager software limitations
- Veritas File System software limitations
- SmartIO software limitations
- Dynamic Multi-Pathing software limitations
- Replication software limitations
- Cluster Server software limitations
- Limitations related to bundled agents
- Limitations related to VCS engine
- Cluster configuration wizard limitations
- Limitations related to the VCS database agents
- Cluster Manager (Java console) limitations
- Limitations related to I/O fencing
- Limitations related to bundled agents
- Storage Foundation Cluster File System High Availability software limitations
- Storage Foundation for Oracle RAC software limitations
- Storage Foundation for Databases (SFDB) tools software limitations
- Storage Foundation for Sybase ASE CE software limitations
- Storage Foundation software limitations
- Documentation
vxdmpraw creates raw devices for the whole disk, which causes problems on Oracle ASM 11.2.0.4 [3738639]
Oracle recommends working with partitions and using them for Automatic Storage Management (ASM).
The vxdmpraw utility allows and creates raw devices for the whole dmp device and changes permission and ownership of dmp devices to Oracle user or group. This results in Oracle ASM discovering the whole disk as a "CANDIDATE" disk.
This leads to the following issues while creating ASM diskgroup using the whole disk:
The disk used for ASM diskgroup doesn't show ASM tags on the vxdisk list.
ASM alert log shows below errors:
On discovery: Device or resource busy On creating diskgroup: failed to update diskgroup resource ora.DATA1.dg
Workaround:
To avoid issues, create partition prior to create raw devices for DMP and remove raw devices of the whole disk before ASM discovery. See the following steps and the example:
- Create a primary partition on the disk with entire space:
# fdisk /dev/vx/dmp/ibm_shark0_10
- Use the vxdmpraw command to enable DMP devices:
# /etc/vx/bin/vxdmpraw enable oracle dba 765 ibm_shark0_10
- Remove the raw device for the whole disk:
# ls -l /dev/vx/dmp |grep ibm_shark0_10$
brwxrw-r-x 1 grid oinstall 201, 368 Mar 6 15:43 ibm_shark0_10
# raw -qa |grep 368
/dev/raw/raw17: bound to major 201, minor 368
# raw /dev/raw/raw17 0 0
Note:
In this example, for making changes persistent in system reboot, remove the raw17 from
/etc/vx/.vxdmprawdev
. - Use ASM diskstring as '/dev/raw/*'(default), and discover all available disks:
SQL> select name,path,header_status from v$asm_disk;
NAME PATH HEADER_STATU ----- ------ -------------- /dev/raw/raw18 CANDIDATE
- Create ASM diskgroup with raw device of partition:
SQL> create diskgroup DATA10 external redundancy disk '/dev/raw/raw18';
If you use ASM_DISKSTRING with /dev/vx/dmp/*, then change the permission and owner for the whole disk to prevent ASM from discovering it.
# chmod 600 /dev/vx/dmp/ibm_shark0_10
# chown root:root /dev/vx/dmp/ibm_shark0_10