Veritas Storage Foundation and High Availability Solutions Release Notes

More documents

Recommendations

Info

120About Veritas Storage Foundation and High Availability SolutionsKnown issuesOracle Grid Infrastructure installation may fail with internal driver errorThe Oracle Grid Infrastructure installation may fail with the following error:[INS-20702] Unexpected Internal driver errorWorkaround:Perform one of the following steps depending on the type of installer you use forthe installation:■Script-based installerExport the OUI_ARGS environment variable, before you run the SF installationprogram:export OUI_ARGS=-ignoreInternalDriverErrorFor more information, see the Oracle Metalink document: 970166.1■Web-based installerWhen you run the Web-based installer, in the EntertheargumentstobepassedtotheOracleinstaller text box, enter the value -ignoreInternalDriverError.For more information, see the Veritas Storage Foundation for Oracle RACInstallation and Configuration Guide.During installation or system startup, Oracle Grid Infrastructure may failto startAfter successful installation of Oracle RAC 11g Release 2 Grid Infrastructure,while executing the root.sh script, ohasd may fail to start. Similarly, duringsystem startup, Oracle Grid Infrastructure may fail to start though the VCS enginelogs may indicate that the cssd resource started Oracle Grid Infrastructuresuccessfully.The following message may be displayed on running the strace command:# /usr/bin/strace -ftt -p pid_of_ohasd.bin14:05:33.527288 open("/var/tmp/.oracle/npohasd",O_WRONLY For possible causes and workarounds, see the Oracle Metalink document: 1069182.1Enabling ODM in Oracle RAC 11 Release 2 installations causes errors(1913013)Enabling ODM in Oracle RAC 11 Release 2 installations causes the following error:'ODM ERROR V-41-4-1-253-12 Not enough space'Oracle instance may also crash with same error.
About Veritas Storage Foundation and High Availability SolutionsKnown issues121The error is observed if the DISM (Dynamic Intimate Shared memory) feature isenabled. In Solaris, the Oracle database uses DISM if it is available on the system,and if the value of the sga_max_size initialization parameter is larger than thesize required for all SGA components combined.Workaround:Make sure that the file ORACLE_HOME/bin/oradism is owned by theroot user with "execute" and "setuid" permissions. If the problem persists aftercorrecting the permissions, uncomment the sga_max_size and memory_targetinit.ora parameters.Oracle VIP Configuration Assistant fails with an error message (1182220)During Oracle RAC 10g Release 2 installation, the VIP Configuration Assistantmay fail with the following error message:The given interface(s), "" is not public.Public interfaces should be used to configure virtual IPs.This message appears only when the VIP is not from the regular public IP range(for example, 200.).Workaround: Invoke the vipca utility manually as the superuser.# export DISPLAY=nebula:0.0# $CRS_HOME/bin/vipcaOracle Cluster Verification utility displays a warning messageDuring the final stage of Oracle RAC 10g Release 2 installation, you may receivea warning message with the Oracle Cluster Verification utility.For example:Utility============================================================OUI-25031: Some of the configuration assistants failed. It isstrongly recommended that you retry the configurationassistants at this time. Not successfully running any "Recommended" assistants means your system will not be correctlyconfigured.1. Check the Details panel on the Configuration Assistant Screento see the errors resulting in the failures.2. Fix the errors causing these failures.3. Select the failed assistants and click the 'Retry' buttonto retry them.============================================================
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:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70: About Veritas Storage Foundation an
Page 119: 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 163 and 164: Chapter4Upgrading to 6.0.3This chap
Page 165 and 166: Upgrading to 6.0.3Upgrading to 6.0.
Page 171 and 172:
Upgrading to 6.0.3Upgrading to 6.0.
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?