Veritas Storage Foundation and High Availability Solutions Release Notes
Veritas Storage Foundation⢠and High ... - SORT - Symantec Veritas Storage Foundation⢠and High ... - SORT - Symantec
118About Veritas Storage Foundation and High Availability SolutionsKnown issuesMultiple CFSmount resources are in a single service group theymay not all come online after a reboot (2164670)In some cases when multiple CFSmount resources are in a single service group,they all may not come online after a reboot. You will need to manually bring themonline after a reboot.WorkaroundCreate a resource dependency between the various CFSmount resources.NFS issues with VxFS Storage Checkpoints (2027492)NFS clients mounting VxFS Storage Checkpoints that are NFS-exported by SFHAcluster nodes using a Virtual IP may receive the following error message uponVirtual IP failover:Stale NFS file handleThis is a result of major numbers of VxFS Storage Checkpoints not necessarilybeing the same on all SFHA cluster nodes.Workaround: There is no workaround for this issue.Panic due to null pointer de-reference in vx_bmap_lookup()(3038285)A null pointer dereference in the vx_bmap_lookup() call can cause a panic.Workaround: Resize the file system with the fsadm command from the primarynode of the cluster.File system check daemon fails to restart after abnormaltermination (2720034)The file system check daemon (vxfsckd) fails to update the vxfsckd-pid file withthe new process ID (pid) of the vxfsckd process after abnormal termination. As aresult, the CFSfsckd agent fails to detect the status of the vxfsckd daemon.Workaround: Perform the following steps to resolve the issue on the node wherethe vxfsckd resource faults:1. Log into the node as the root user.2. Kill all vxfsckd processes:# kill -9 `ps -ef|grep vxfsckd|awk '{print $2}'`
About Veritas Storage Foundation and High Availability SolutionsKnown issues1193. Remove the vxfsckd-pid file:# rm /var/adm/cfs/vxfsckd-pid4. Bring the vxfsckd resource online:# hares -online vxfsckd_resname -sys node_nameFlashsnap clone fails under some unusual archivelogconfiguration on RAC (2846399)In a RAC environment, when using FlashSnap, the archive log destination tosnapshot must be a shared path, and must be the same across all the nodes.Additionally, all nodes must use the same archive log configuration parameter tospecify the archive log destination. Configurations similar to the following arenot supported:tpcc1.log_archive_dest_1='location=/tpcc_arch'tpcc2.log_archive_dest_2='location=/tpcc_arch'tpcc3.log_archive_dest_3='location=/tpcc_arch'Where tpcc1, tpcc2, and tpcc3 are the names of the RAC instances and /tpcc_archis the shared archive log destination.Workaround:To use FlashSnap, modify the above configuration to*.log_archive_dest_1='location=/tpcc_arch'. For example,tpcc1.log_archive_dest_1='location=/tpcc_arch'tpcc2.log_archive_dest_1='location=/tpcc_arch'tpcc3.log_archive_dest_1='location=/tpcc_arch'Veritas Storage Foundation for Oracle RAC known issuesThis section describes the Veritas Storage Foundation for Oracle RAC knownissues in 6.0.3 and 6.0.1.■■Oracle RAC issuesSF issuesOracle RAC issuesThis section lists the known issues in Oracle RAC.
- 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
- Page 87 and 88: About Veritas Storage Foundation an
- Page 89 and 90: About Veritas Storage Foundation an
- Page 91 and 92: About Veritas Storage Foundation an
- Page 93 and 94: About Veritas Storage Foundation an
- Page 95 and 96: About Veritas Storage Foundation an
- Page 97 and 98: About Veritas Storage Foundation an
- Page 99 and 100: About Veritas Storage Foundation an
- Page 101 and 102: About Veritas Storage Foundation an
- Page 103 and 104: About Veritas Storage Foundation an
- Page 105 and 106: About Veritas Storage Foundation an
- Page 107 and 108: About Veritas Storage Foundation an
- Page 109 and 110: About Veritas Storage Foundation an
- Page 111 and 112: About Veritas Storage Foundation an
- Page 113 and 114: About Veritas Storage Foundation an
- Page 115 and 116: About Veritas Storage Foundation an
- Page 117: About Veritas Storage Foundation an
- Page 121 and 122: About Veritas Storage Foundation an
- Page 123 and 124: About Veritas Storage Foundation an
- Page 125 and 126: About Veritas Storage Foundation an
- Page 127 and 128: About Veritas Storage Foundation an
- Page 129 and 130: About Veritas Storage Foundation an
- Page 131 and 132: About Veritas Storage Foundation an
- Page 133 and 134: About Veritas Storage Foundation an
- Page 135 and 136: About Veritas Storage Foundation an
- Page 137 and 138: About Veritas Storage Foundation an
- Page 139 and 140: About Veritas Storage Foundation an
- Page 141 and 142: About Veritas Storage Foundation an
- Page 143 and 144: About Veritas Storage Foundation an
- Page 145 and 146: About Veritas Storage Foundation an
- Page 147 and 148: 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: Installing the products using JumpS
- Page 161 and 162: Installing the products using JumpS
- 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: Upgrading to 6.0.3Upgrading to 6.0.
About <strong>Veritas</strong> <strong>Storage</strong> <strong>Foundation</strong> <strong>and</strong> <strong>High</strong> <strong>Availability</strong> <strong>Solutions</strong>Known issues1193. Remove the vxfsckd-pid file:# rm /var/adm/cfs/vxfsckd-pid4. Bring the vxfsckd resource online:# hares -online vxfsckd_resname -sys node_nameFlashsnap clone fails under some unusual archivelogconfiguration on RAC (2846399)In a RAC environment, when using FlashSnap, the archive log destination tosnapshot must be a shared path, <strong>and</strong> must be the same across all the nodes.Additionally, all nodes must use the same archive log configuration parameter tospecify the archive log destination. Configurations similar to the following arenot supported:tpcc1.log_archive_dest_1='location=/tpcc_arch'tpcc2.log_archive_dest_2='location=/tpcc_arch'tpcc3.log_archive_dest_3='location=/tpcc_arch'Where tpcc1, tpcc2, <strong>and</strong> tpcc3 are the names of the RAC instances <strong>and</strong> /tpcc_archis the shared archive log destination.Workaround:To use FlashSnap, modify the above configuration to*.log_archive_dest_1='location=/tpcc_arch'. For example,tpcc1.log_archive_dest_1='location=/tpcc_arch'tpcc2.log_archive_dest_1='location=/tpcc_arch'tpcc3.log_archive_dest_1='location=/tpcc_arch'<strong>Veritas</strong> <strong>Storage</strong> <strong>Foundation</strong> for Oracle RAC known issuesThis section describes the <strong>Veritas</strong> <strong>Storage</strong> <strong>Foundation</strong> for Oracle RAC knownissues in 6.0.3 <strong>and</strong> 6.0.1.■■Oracle RAC issuesSF issuesOracle RAC issuesThis section lists the known issues in Oracle RAC.
Change language