Veritas Storage Foundation and High Availability Solutions Release Notes

More documents

Recommendations

Info

98About Veritas Storage Foundation and High Availability SolutionsKnown issuesWorkaround: Unmount the file system manually from global zone and then haltthe zone. For VxFS, use following commands to unmount the file system fromglobal zone.To unmount when VxFSMountLock is 1umount -o mntunlock=VCS /To forcefully unmount when VxFSMountLock is 1:# umount -f -o mntunlock=VCS /To unmount when VxFSMountLock is 0:# umount /To forcefully unmount when VxFSMountLock is 0:# umount -f /To halt the zone, use following command:# zoneadm -z haltPrevention of Concurrency Violation (PCV) is not supported for applicationsrunning in a container [2536037]For an application running in a container, VCS uses a similar functionality as ifthat resource is not registered to IMF. Hence, there is no IMF control to take aresource offline. When the same resource goes online on multiple nodes, agentdetects and reports to engine. Engine uses the offline monitor to take the resourceoffline. Hence, even though there is a time lag before the detection of the sameresource coming online on multiple nodes at the same time, VCS takes the resourceoffline.PCV does not function for an application running inside a local Zone on SolarisWorkaround: No workaround.For IPv6 configuration, the MultiNICA Agent is unable to detect loss ofnetwork connectivity (2979745)While monitoring the Network Interface Cards (NIC) configured with the MultiNICAResource, if the NIC is not able to ping the Network Hosts, the Agent tries to pingthe broadcast address to check whether the NIC is healthy. The agent uses thepacket count of the NIC to check if the network is reachable. But the packet countmay increase even due to the NIC replying to itself rather than the replies fromthe systems in the network. Thus, Veritas Cluster Server (VCS) may incorrectlyreport the NIC as healthy. This issue exists only for IPv6 addresses.
About Veritas Storage Foundation and High Availability SolutionsKnown issues99Workaround:There is no workaround for this issue.Issues related to the VCS database agentsHealth check monitoring is not supported for Oracle database 11g R1 and11g R2 [1985055]Health check monitoring is not supported for Oracle database 11g R1 and 11g R2.Workaround: Set MonitorOption attribute for Oracle resource to 0.Health check monitoring does not work with VCS agent for Oracle [2101432]The health check monitoring in Oracle agent for VCS does not work due toincompatibility of the health check APIs provided by Oracle.Workaround: Disable health check monitoring by setting the MonitorOptionattribute to 0 (zero).Intentional Offline does not work for VCS agent for Oracle [1805719]Due to issues with health check monitoring, Intentional Offline does not work forVCS agent for Oracle.The ASMInstAgent does not support having pfile/spfile for the ASM Instanceon the ASM diskgroupsThe ASMInstAgent does not support having pfile/spfile for the ASM Instance onthe ASM diskgroups.Workaround:Have a copy of the pfile/spfile in the default $GRID_HOME/dbs directory to makesure that this would be picked up during the ASM Instance startup.VCS agent for ASM: Health check monitoring is not supported for ASMInstagentThe ASMInst agent does not support health check monitoring.Workaround: Set the MonitorOption attribute to 0.NOFAILOVER action specified for certain Oracle errorsThe Veritas High Availability agent for Oracle provides enhanced handling ofOracle errors encountered during detailed monitoring. The agent uses the referencefile oraerror.dat, which consists of a list of Oracle errors and the actions to betaken.
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 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48: About Veritas Storage Foundation an
Page 97: About Veritas Storage Foundation an
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

Create successful ePaper yourself

Delete template?

Save as template?