Veritas InfoScale™ 7.4.2 Release Notes - Solaris
- Introduction
- Requirements
- Changes introduced in 7.4.2
- Fixed issues
- Limitations
- Storage Foundation software limitations
- Dynamic Multi-Pathing software limitations
- Veritas Volume Manager software limitations
- Veritas File System software limitations
- SmartIO software limitations
- Replication software limitations
- Cluster Server software limitations
- Limitations related to bundled agents
- Limitations related to VCS engine
- Veritas cluster configuration wizard limitations
- Limitations related to the VCS database agents
- Cluster Manager (Java console) limitations
- Limitations related to LLT
- 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 software limitations
- Known issues
- Issues related to installation and upgrade
- Storage Foundation known issues
- Dynamic Multi-Pathing known issues
- Veritas Volume Manager 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
- Issues related to installation and upgrade
In an IPv6 environment, db2icrt and db2idrop commands return a segmentation fault error during instance creation and instance removal (1602444)
When using IBM DB2 db2icrt command to create a DB2 database instance on a pure IPv6 environment, the db2icrt command returns segmentation fault error message. For example:
$ /opt/ibm/db2/V9.5/instance/db2icrt -a server -u db2fen1 db2inst1 /opt/ibm/db2/V9.5/instance/db2iutil: line 4700: 26182 Segmentation fault $ {DB2DIR?}/instance/db2isrv -addfcm -i ${INSTNAME?}
The db2idrop command also returns segmentation fault, but the instance is removed successfully after the db2idrop command is issued. For example:
$ /opt/ibm/db2/V9.5/instance/db2idrop db2inst1 /opt/ibm/db2/V9.5/instance/db2iutil: line 3599: 7350 Segmentation fault $ {DB2DIR?}/instance/db2isrv -remove -s DB2_${INSTNAME?} 2> /dev/null DBI1070I Program db2idrop completed successfully.
This happens on DB2 9.1, 9.5, and 9.7.
This issue has been identified as an IBM issue. Once IBM has fixed this issue, then IBM will provide a hotfix for this segmentation problem.
At this time, you can communicate in a dual-stack to avoid the segmentation fault error message until IBM provides a hotfix.
To communicate in a dual-stack environment
- Add an IPv6 hostname as an IPv4 loopback address to the
/etc/hosts
file. For example:127.0.0.1 swlx20-v6
Or
127.0.0.1 swlx20-v6.punipv6.com
127.0.0.1
is the IPv4 loopback address.swlx20-v6
andswlx20-v6.punipv6.com
are the IPv6 hostnames.