Veritas Storage Foundation and High Availability Solutions Release Notes

More documents

Recommendations

Info

50About Veritas Storage Foundation and High Availability SolutionsKnown issuesContinuous trespass loop when a CLARiiON LUN is mapped toa different host than its snapshot (2761567)If a CLARiiON LUN is mapped to a different host than its snapshot, a trespass onone of them could cause a trespass on the other. This behavior could result in aloop for these LUNs, as DMP tries to fail back the LUNs if the primary paths areavailable.Workaround:To avoid this issue, turn off the dmp_monitor_ownership tunable:# vxdmpadm settune dmp_monitor_ownership=offAfter excluding devices managed by PowerPath from VxVM,the devices still show as DMP devices (2494632)The issue happens after EMC PowerPath is installed and all devices are underPowerPath control. If you want to maintain the devices under PowerPath control,you use the following command to exclude the device that is managed byPowerPath from VxVM:# vxdmpadm exclude dmpnodename=PowerPath_device _nameAfter system reboot, the PowerPath device still shows as a DMP device, althoughthe device is managed by EMC PowerPath.Workaround:This issue is seen only during the first bootup discovery after reboot. To resolvethe issue, manually trigger DMP device discovery:# vxdisk scandisksThe system may hang with Solaris 11 SRU1 (2876211)When running Solaris 11 SRU1, the system may hang due to an Oracle bug. TheOracle Bug ID is 7105131 deadman panic.Workaround: SRU1 for Solaris 11 should be updated to SRU2a. The bug is fixedin SRU2a: Oracle Solaris 11 Support Repository Updates (SRU) Index (Doc ID1372094.1)System panics because dmp_signal_event() called psignal()with incorrect vxesd proc pointer (3041167)On Solaris 11 SPARC SRU1, system panics after executing the vxrecover operationon the master node.
About Veritas Storage Foundation and High Availability SolutionsKnown issues51Workaround:There is no workaround for this issue in 6.0.3.Veritas Storage Foundation known issuesThis section describes the Veritas Storage Foundation known issues in 6.0.3 and6.0.1.■■■■■Veritas Storage Foundation known issuesVeritas Volume Manager known issuesVeritas File System known issuesReplication known issuesVeritas Storage Foundation for Databases (SFDB) tools known issuesVeritas Storage Foundation known issuesThis section describes the known issues in this release of Veritas StorageFoundation (SF).Some dbed DST commands do not work correctly in non-POSIX locales(2138030)Some dbed DST commands do not work correctly in non-POSIX locale settings.Workaround:Set the environment variable LANG=C systemwide in the /etc/profile file.In an IPv6 environment, db2icrt and db2idrop commands return asegmentation fault error during instance creation and instance removal(1602444)When using IBM DB2 db2icrt command to create a DB2 database instance on apure IPv6 environment, the db2icrt command returns segmentation fault errormessage. 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 isremoved 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
Page 1 and 2: Veritas Storage Foundationand High
Page 3 and 4: Symantec Corporation350 Ellis Stree
Page 5 and 6: ■■■■■■■Hardware infor
Page 7 and 8: ContentsTechnical Support .........
Page 9 and 10: Contents9Chapter 4 Upgrading to 6.0
Page 11 and 12: Chapter1About Veritas StorageFounda
Page 13 and 14: About Veritas Storage Foundation an
Page 49: About Veritas Storage Foundation an
Page 101 and 102:
About Veritas Storage Foundation an
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Chapter2Installing the products for
Page 151 and 152:
Installing the products for the fir
Page 153 and 154:
Installing the products for the fir
Page 155 and 156:
Chapter3Installing the productsusin
Page 157 and 158:
Installing the products using JumpS
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Chapter4Upgrading to 6.0.3This chap
Page 165 and 166:
Upgrading to 6.0.3Upgrading to 6.0.
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Upgrading to 6.0.3Verifying softwar
Page 195 and 196:
Chapter5Uninstalling version 6.0.3T
Page 197 and 198:
Uninstalling version 6.0.3Rolling b
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
AppendixAConfiguring VCS to managea
Page 223 and 224:
Configuring VCS to manage a Logical
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
show all

Veritas Storage Foundation and High Availability Solutions Release Notes

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?