Veritas Storage Foundation and High Availability Solutions Release Notes

52About Veritas Storage Foundation and High Availability SolutionsKnown issues$ {DB2DIR?}/instance/db2isrv -remove -s DB2_${INSTNAME?} 2> /dev/nullDBI1070IProgram 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, thenIBM will provide a hotfix for this segmentation problem.At this time, you can communicate in a dual-stack to avoid the segmentation faulterror 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-v6Or127.0.0.1 swlx20-v6.punipv6.com127.0.0.1 is the IPv4 loopback address.swlx20-v6 and swlx20-v6.punipv6.com are the IPv6 hostnames.Boot fails after installing or removing SF packages from a Solaris 9 systemto a remote Solaris 10 system (1747640)The following issue occurs if you install or remove a Storage Foundation packageor patch from a Sparc Solaris 9 system to a remote Solaris 10 system, using the-R rootpath option of the pkgadd, patchadd, pkgrm or patchrm commands.Generally, when you install or remove a SF package on a Solaris 10 system, thepackage scripts update the boot archive. However if the local system is Solaris 9and the remote system is Solaris 10, the scripts fail to update the boot archive onthe Solaris 10 system.Note: The boot archive is synchronized correctly when you upgrade SF usingSolaris Live Upgrade.Workaround:The workaround is to manually clear the boot archive when you boot the alternate.The SUN boot process detects that the boot archive is out sync and displaysinstructions for how to correct the situation.For example: