Veritas Storage Foundation and High Availability Solutions Release Notes
Veritas Storage Foundation⢠and High ... - SORT - Symantec Veritas Storage Foundation⢠and High ... - SORT - Symantec
36About Veritas Storage Foundation and High Availability SolutionsFixed issuesTable 1-9Fixedissues3030663Veritas Storage Foundation for Databases (SFDB) tools 6.0.3 fixedissuesDescriptiondbed_vmclonedb does not read pfile supplied by -p'pfile_modification_file' option.Veritas Cluster Server fixed issuesThis section describes the Veritas Cluster Server software limitations in 6.0.3.Veritas Cluster Server: issues fixed in 6.0.3Table 1-10describes the incidents that are fixed in Veritas Cluster Server in 6.0.3.Table 1-10Fixedissues3025931301396230139402980002297974529675362964772294115529376732861253Veritas Cluster Server 6.0.3 fixed issuesDescriptionSometimes gab module does not get loaded after system reboot automatically.We have to remove the driver manually and add it back to make it work.Monitor fails to detect DB2 resource online for DB2 version 10.1.If DB2 is installed in NON-MPP mode and UseDB2Start attribute is set to 0,we still use db2start command to start the DB2 process instead of usingdb2gcf command.High availability support for logical domain when control domain is downwith multiple I/O domains in Oracle VM (OVM) for SPARC environment.MultiNICA is unable to detect Network connectivity lost.MonitorProgram of Application does not work correctly with C shell of Userenvironment.If you take an NFSRestart resource offline, the NFSRestart agent mayunexpectedly stop NFS processes in a local container Zones.Group is not marked offline on faulted cluster in a GCO environment aftera cluster failure is declared.AMF driver panics the machine when amfstat is executed.In vxfen driver log statement, jeopardy membership is printed as garbage.
About Veritas Storage Foundation and High Availability SolutionsFixed issues37Table 1-10Fixedissues2848009284800527376532736627Veritas Cluster Server 6.0.3 fixed issues (continued)DescriptionAMF panicks the machine when an Agent is exiting.VCS SMF service goes into maintenance state on a two-node cluster.Incorrect descriptions about the RVGPrimary online script .REMOTE CLUSTER STATE remains in INIT state and Icmp heartbeat statusis UNKNOWN.Veritas Storage Foundation and High Availability fixed issuesFor fixed issues of Veritas Storage Foundation and High Availability in this release,see Veritas Storage Foundation fixed issues and Veritas Cluster Server fixed issues.Veritas Storage Foundation for Oracle RAC 6.0.3 fixed issuesThere are no issues fixed in SF Oracle RAC 6.0.3.Veritas Storage Foundation Cluster File System High Availability fixedissuesThis section describes the Veritas Storage Foundation Cluster File System HighAvailability fixed issues in 6.0.3.Veritas Storage Foundation Cluster File System HighAvailability: issues fixed in 6.0.3Table 1-11 describes the Veritas Storage Foundation Cluster File System fixedissues in 6.0.3.Table 1-11Fixedissues297769729427762923867Veritas Storage Foundation Cluster File System High Availability6.0.3 fixed issuesDescriptionvx_idetach generated kernel core dump while filestore replication is running.Mount fails when volumes in vset is not ready.Internal test hits an assert "f:xted_set_msg_pri1:1".
- 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: About Veritas Storage Foundation an
- Page 17 and 18: About Veritas Storage Foundation an
- Page 19 and 20: About Veritas Storage Foundation an
- Page 21 and 22: About Veritas Storage Foundation an
- Page 23 and 24: About Veritas Storage Foundation an
- Page 25 and 26: About Veritas Storage Foundation an
- Page 27 and 28: About Veritas Storage Foundation an
- Page 29 and 30: About Veritas Storage Foundation an
- Page 31 and 32: About Veritas Storage Foundation an
- Page 33 and 34: About Veritas Storage Foundation an
- Page 35: About Veritas Storage Foundation an
- Page 39 and 40: About Veritas Storage Foundation an
- Page 41 and 42: About Veritas Storage Foundation an
- Page 43 and 44: About Veritas Storage Foundation an
- Page 45 and 46: About Veritas Storage Foundation an
- Page 47 and 48: About Veritas Storage Foundation an
- Page 49 and 50: About Veritas Storage Foundation an
- Page 51 and 52: About Veritas Storage Foundation an
- Page 53 and 54: About Veritas Storage Foundation an
- Page 55 and 56: About Veritas Storage Foundation an
- Page 57 and 58: About Veritas Storage Foundation an
- Page 59 and 60: About Veritas Storage Foundation an
- Page 61 and 62: About Veritas Storage Foundation an
- Page 63 and 64: About Veritas Storage Foundation an
- Page 65 and 66: About Veritas Storage Foundation an
- Page 67 and 68: About Veritas Storage Foundation an
- Page 69 and 70: About Veritas Storage Foundation an
- Page 71 and 72: About Veritas Storage Foundation an
- Page 73 and 74: About Veritas Storage Foundation an
- Page 75 and 76: About Veritas Storage Foundation an
- Page 77 and 78: About Veritas Storage Foundation an
- Page 79 and 80: About Veritas Storage Foundation an
- Page 81 and 82: About Veritas Storage Foundation an
- Page 83 and 84: About Veritas Storage Foundation an
- Page 85 and 86: About Veritas Storage Foundation an
36About <strong>Veritas</strong> <strong>Storage</strong> <strong>Foundation</strong> <strong>and</strong> <strong>High</strong> <strong>Availability</strong> <strong>Solutions</strong>Fixed issuesTable 1-9Fixedissues3030663<strong>Veritas</strong> <strong>Storage</strong> <strong>Foundation</strong> for Databases (SFDB) tools 6.0.3 fixedissuesDescriptiondbed_vmclonedb does not read pfile supplied by -p'pfile_modification_file' option.<strong>Veritas</strong> Cluster Server fixed issuesThis section describes the <strong>Veritas</strong> Cluster Server software limitations in 6.0.3.<strong>Veritas</strong> Cluster Server: issues fixed in 6.0.3Table 1-10describes the incidents that are fixed in <strong>Veritas</strong> Cluster Server in 6.0.3.Table 1-10Fixedissues3025931301396230139402980002297974529675362964772294115529376732861253<strong>Veritas</strong> Cluster Server 6.0.3 fixed issuesDescriptionSometimes gab module does not get loaded after system reboot automatically.We have to remove the driver manually <strong>and</strong> add it back to make it work.Monitor fails to detect DB2 resource online for DB2 version 10.1.If DB2 is installed in NON-MPP mode <strong>and</strong> UseDB2Start attribute is set to 0,we still use db2start comm<strong>and</strong> to start the DB2 process instead of usingdb2gcf comm<strong>and</strong>.<strong>High</strong> availability support for logical domain when control domain is downwith multiple I/O domains in Oracle VM (OVM) for SPARC environment.MultiNICA is unable to detect Network connectivity lost.MonitorProgram of Application does not work correctly with C shell of Userenvironment.If you take an NFSRestart resource offline, the NFSRestart agent mayunexpectedly stop NFS processes in a local container Zones.Group is not marked offline on faulted cluster in a GCO environment aftera cluster failure is declared.AMF driver panics the machine when amfstat is executed.In vxfen driver log statement, jeopardy membership is printed as garbage.
Change language