0% found this document useful (0 votes)
93 views7 pages

Document 1312225.1

Uploaded by

ajfernandezt
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
93 views7 pages

Document 1312225.1

Uploaded by

ajfernandezt
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

22/11/24, 14:13 Document 1312225.

1
Copy right (c) 2024, Oracle. A ll rights reserv ed. Oracle Confidential.

Things to Consider Before Upgrading to 11.2.0.2 Grid Infrastructure/ASM (Doc ID 1312225.1)

In this Document

Purpose
Scope
Details
Validate Existing Clusterware
Patch Pre-upgrade Clusterware Home
Rolling Upgrade Related:
Start OUI to Install GI 11.2.0.2
Patch 11.2.0.2 GI Before Executing rootupgrade.sh
Execute rootupgrade.sh from new GRID_HOME
Patch 11.2.0.2 GI After Executed rootupgrade.sh
Miscellaneous
References

APPLIES TO:

Oracle Cloud Infrastructure - Database Service - Version N/A and later


Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.

PURPOSE

This document is to list known issues to avoid, areas to consider to have smooth upgrade to 11gR2 Grid Infrastructure.

SCOPE

This document is intended for Oracle Clusterware Administrators and Oracle Support engineers.

For Exadata, refer to the following note for details:

note 1315926.1 - 11.2.0.1 to 11.2.0.2 Database Upgrade on Exadata Database Machine

DETAILS

11.2.0.2 is a full release, any pre-11.2 Oracle Clusterware (CRS) can be upgraded to 11.2.0.2 directly; also started from
11gR2, in-place patchset upgrade is not supported, any patchset must be installed into a new HOME (out-of-place
upgrade).

Validate Existing Cluste rware

Before starting OUI to install 11.2.0.2 Grid Infrastructure (GI in short), verify existing environments with the following to
eliminate the chance of hitting known issues.

The 11.2.0.2 GI owner must be the same as the existing clusterware owner (crs owner for pre-11.2 or GI owner for
11.2.0.1) to avoid the issue in Document 1067606.1

ASMCA may fail due to non-default ASM instance names or different username for CRS and ASM in pre-11.2, refer
to Document 1113073.1 for details.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1fxc8yfoo_511&id=1312225.1 1/7
22/11/24, 14:13 Document 1312225.1
Avoid to set any OS user's home directory or ORACLE_BASE to /opt/oracle in order to avoid Bug:10362257. This is
explained in Document 1281913.1

Unset Oracle related environment variables especially ORA_CRS_HOME before starting OUI or before executing any
root script for both root and grid user. For details, refer to Document 952925.1 - NETCA & ASMCA Fail during
Upgrade of CRS/ASM to Grid Infrastructure 11gR2

The output of the following CVU command should be free of errors, refer to Section "Start OUI" for known CVU
issues, refer to Document 986822.1 for instructions how to enable CVU tracing.

$INSTALL_DIR/runcluvfy.sh stage -pre crsinst -n <node1>,<node2>,<node3>.. -verbose

The IP addresses for the public and private networks should not be in a link local subnet (169.254.*.*) and should
be in unrelated, separate subnets to avoid the issue in Document 1062682.1. Refer to Document 1054902.1 Section
"G. Basics of Subnet" for more information on subnet.

The output of "ifconfig" for the private network adapter and the cluster_interconnect part of the "oifcfg getif"
command output should be consistent in regards to the network adapter name and the subnet.

Public/VIP network information should be consistent to avoid the issue documented in Document 1296579.1 - PRVF-
10205 : The VIPs do not all share the same subnet.

The length of GI owner uid should be less than 7 digits in order to avoid the issue documented in Document
10379703.8

OS should meet basic version requirement to avoid issues in the following note. Refer to
http://www.oracle.com/pls/db112/portal.portal_db?selected=11 for a list of installation document.

Document 983713.1 - HP-UX: 11gR2 runInstaller Fails with "An internal error
occurred within cluster verification framework"

<Documentnote 1085154.1> - Solaris: 11gR2 runInstaller Fails with "An internal


error occurred within cluster verification framework"

Document 986657.1 - AIX: runInstaller Warns INS-13001 while CLUVFY Reports


"Reference data is not available for verifying prerequisites on this operating system
distribution"

The CSS parameter "diagwait" ("crsctl get css diagwait") should either be unset(output shows "Configuration
parameter diagwait is not defined") or set to a small value (13 or less) to avoid issue in Document 1102283.1 -
11gR2 rootupgrade.sh Fails as cssvfupgd Can not Upgrade Voting Disk

Output of "ocrcheck" should be clean to avoid issue in Document 1093014.1

On AIX, rootpre.sh should finish successfully with no "Text file busy" messages before starting OUI to avoid the issue
in Document 1053055.1 - 11gR2 rootupgrade.sh Fails as "Symbol ras_arg_t (number 8) is not exported from
dependent module libttsh11.so". Output of rootpre.sh is saved in /tmp/rootpre.out_${TIMESTAMP}.

On Windows, network adapter should not have invalid netmask to avoid issue in Document 1252334.1 - Grid
Infrastructure Configuration Fails as MDNSD can not Register on Network Adapter with Invalid Mask 0.0.0.0

ASM init.ora/pfile/spfile should not have parameters like SGA_TARGET, SGA_MAX_SIZE, SHARED_POOL_SIZE, and
LARGE_POOL_SIZE to avoid "ORA-00600 ksxpmprp1" error.

Patch Pre -upgrade Cluste rware Home

Rolling Upgrade Related:

The following issues may be encountered during a rolling ASM upgrade (migration). These issues will not happen when
performing a non rolling upgrade.

To perform non rolling upgrade, stop pre-upgrade CRS/GI on all nodes, install new GI(i.e. 11.2.0.2) on all nodes and then
execute rootupgrade.sh on one node at a time sequentially. If new GI is installed when pre-upgrade clusterware stack is up,

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1fxc8yfoo_511&id=1312225.1 2/7
22/11/24, 14:13 Document 1312225.1
either execute config.sh from new GI_HOME/crs/config or remove and reinstall when pre-upgrade clusterware stack is
down.

Unpublished Bug:9413827 and Bug:9706490, the solution is to apply 11.2.0.1.2 Patch:9706490 to the 11.2.0.1 GI
home before starting 11.2.0.2 GI OUI, for more details refer to Document 1274629.1

Unpublished Bug:9329767, it happens only when upgrading from pre-11.2 to 11.2.0.1 or from 11.2.0.1 to higher
version (i.e.11.2.0.2). It could happen on any node and when it happens, ASM fails to start with ORA-00600
[kjbmmchkinteg:from]. The bug is fixed in patch 12652740 which needs to be applied to 11.2.0.1 home.

Unpublished Bug:10229886 - ASM rolling upgrade to 11.2.0.2 could fail as lmd process fails to start with ORA-7445
[kernel_vsyscall] / ORA-7445 [SKGXPIVRCV] / ORA-7445 [GSIGNAL], fixed in 11.2.0.3

@Call stack of bug 10229886/10321596:


@ gsignal abort assert_fail skgxp_assert skgxpivrcv skgxpvrcv ksxpqrcvb ..

Bug:9941757 - Upgrade from 11.2.0.1 ASM INSTANCES FAILED TO START with error "ORA-15163: cluster not in
rolling downgrade" after restart of GI on all nodes but before rootupgrade.sh finishs on last nodes, fixed in 11.2.0.3
and workaround is to:

- Log in as sysasm on a node that is already upgraded to 11.2.0.2 and execute: alter
system start rolling migration to '11.2.0.1.0';
- Start 11.2.0.1 ASM on the problematic node, preferably via crsctl
- Upgrade ASM to 11.2.0.2 on the problem node (ex: through rootupgrade.sh script)
- Confirm all ASM instances are running 11.2.0.2
- If rolling upgrade is still in progress, run 'alter system stop rolling migration'
on any ASM instance.

Other Issues:

Bug:12414722 closed as duplicate of Bug:3841387 "ASM or DB fails to start when Upgrading from 10.1", the solution
is to apply Patch:9632335 to 10.1 ASM and DB home. Refer to Document 948456.1 for details of the problem.

Start OUI to Install GI 11.2.0.2

OUI calls CVU to check most components relevant for the clusterware installation, for common 11gR2 GI OUI errors and
explanations/solutions, refer to note 1056713.1; to turn on debugging for OUI, refer to note 1056322.1

Below is a list of various OUI and CVU errors/warnings and explanations/solutions.

Document 887471.1 - PRVF-4664 PRVF-4657: Found inconsistent name resolution entries for SCAN name

Document 1210863.1 - Device Checks for ASM Fails with PRVF-5150: Path ORCL:<diskname> is not a valid path,
Bug:10026970 is fixed in 11.2.0.3

Document 1058576.1 - PRVF-4178 Reported from CLUVFY

Document 1267569.1 - PRVF-5449 : Check of Voting Disk location "ORCL:<diskname>(ORCL:<diskname>)" failed

Document 1233505.1 - Checklist for PRVF-10037 : Failed to retrieve storage type for xx on node xx

Document 1271996.1 - 11.2.0.2 Grid Install Fails with SEVERE: [FATAL] [INS-13013], and PRVF-5640 or a Warning
in "Task resolv.conf Integrity"

Document 1135933.1 - PRVF-4195 Reported while Executing "cluvfy comp ocr"

Document 1051763.1 - INS-20802 PRVF-4172 Reported after Successful Upgrade to 11gR2 Grid Infrastructure

Document 1061025.1 - PRVF-4125 Reported from CLUVFY

Document 1056195.1 - INS-20702 Reported during 11gR2 Installation on getSharedPartitionListCVU

Document 948382.1 - INS-08109 While Trying to Install Grid Infrastructure

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1fxc8yfoo_511&id=1312225.1 3/7
22/11/24, 14:13 Document 1312225.1
Document 970166.1 - INS-20702 "checkFreeDiskSpace" Reported During 11gR2 Installation

Document 1056693.1 - How to Configure NTP or Windows Time to Resolve CLUVFY Error PRVF-5436 PRVF-9652

Document 974481.1 - INS-20802 PRVF-9802 PRVF-5184 PRVF-5186 Reported after Successful Upgrade to 11gR2
Grid Infrastructure

Patch 11.2.0.2 GI Be fore Exe cuting rootupgrade .sh

GI bundle patches/PSUs are accumulative and contain fixes to the most critical issues, it is recommended to apply the latest
available bundle patch/PSU to avoid: 1). known issues that may prevent the root script from succeeding. 2). known issues
that are not particular to the upgrade but could happen while the clusterware is being upgraded.

To apply patches to the 11.2.0.2 GI home before the rootupgrade.sh script is executed, only run the "opatch napply"
command. For example, to apply PSU 2, as grid user execute the following on all nodes:

$ <11.2.0.2GI_HOME>/OPatch/opatch napply -oh <11.2.0.2GI_HOME> -local


<UNZIPPED_PATCH_LOCATION>/12311357
$ <11.2.0.2GI_HOME>/OPatch/opatch napply -oh <11.2.0.2GI_HOME> -local
<UNZIPPED_PATCH_LOCATION>/11724916

One of the top issues that causes the rootupgrade.sh script to fail in 11.2.0.2 is multicast not working for group
230.0.1.0, Patch:9974223 introduces support for the additional group 224.0.0.251 and has been included in bundle 1
and above, refer to Document 1212703.1 for more details. Patch:9974223 may cause issue on AIX, refer to
Document 1329597.1 for solutions.

The failure to start HAIP may cause the rootupgrade.sh script to fail, Bug:11077756 will allow the script to continue
even if HAIP fails to start, the fix has been included in bundle 2 and above. For more issues in the HAIP area, refer
to Document 1210883.1 for more details.

Failure to install Oracle Kernel Service could cause the rootupgrade.sh script to fail, for details, refer to Document
1265276.1 - ACFS-9327 ACFS-9121 ACFS-9310: ADVM/ACFS installation failed

ora.crf resource may fail to start on Solaris with "CRS-2674: Start of 'ora.crf' on '<nodename>' failed", refer to
Document 1289922.1 for details

Watch out root script output for "Configure Oracle Grid Infrastructure for a Cluster ... failed", if it shows up, it means
that the root script has failed and corrective action is needed, refer to Document 969254.1 for details.

Exe cute rootupgrade .sh from ne w GRID_HOM E

When switching to the root user in order to execute rootupgrade.sh, "su -" or "su - root" provides the full root environment,
while sudo, pbrun, "su root" or "su" or similar facilities don't always do the same. It is recommended to execute
rootupgrade.sh with full root environment to avoid issues documented in the following notes:

Document 1315203.1 - ACFS Drivers Fail To Install During Root.Sh Execution Of 11.2.0.2 GI Standalone On AIX

Document 1235944.1 - 11gR2 root.sh Fails as crsd.bin Does not Come up due to Wrong ulimit

Document 1259874.1 - root.sh Fails as the ora.asm resource is not ONLINE or PROTL-16 due to Wrong umask

Document 1141963.1 - 11gR2 rootupgrade.sh Fails as Environment Variable PATH Points to Wrong crsctl First

If rootupgrade.sh fails, refer to Document 1050908.1 and Document 1053970.1 for troubleshooting steps.

Patch 11.2.0.2 GI Afte r Exe cute d rootupgrade .sh

Here's a list of known critical issues that are affecting GI 11.2.0.2, many of them have been fixed by latest PSU.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1fxc8yfoo_511&id=1312225.1 4/7
22/11/24, 14:13 Document 1312225.1
Bug:10299006 and Bug:11877079 - Many Connections From oraagent.bin to ASM or Database Instance, refer to
Document 1287496.1 for details.

Bug:11871469 - ORAAGENT CHECK TASK IS TIMING OUT WHICH IS FORCING THE AGENT TO ABORT AND EXIT,
fixed in 11.2.0.3, 12.1 and one-off Patch:12347844 exists

Bug:10034417 - OHASD.BIN TAKING 95-100% CPU ON AN IDLE SYSTEM, fixed 11.2.0.2 Bundle2, 11.2.0.3

Bug:10374874 - RBAL GOT UNRESPONSIVE WAITING FOR A RESPONSE FROM OCSSD, fixed in 11.2.0.3, one-off
patches exist

Bug:10131381 - PROCESS PERSISTS AFTER INSTANCE SHUTDOWN, fixed in 11.2.0.2 Bundle1, 11.2.0.3

Bug:10119895 - PSU2 9655006 DOESN'T UPDATE /ETC/INIT.D/OHASD, refer to Document 1257924.1 for details.

Bug:9336825 - Repeated error "CRS-2332:Error pushing GPnP profile to


"mdns:service:gpnp._tcp.local.://<HOSTNAME1>:<PORT>/agent=gpnpd,cname=crs,host=
<HOSTNAME1>,pid=17182/gpnpd h:<HOSTNAME1> c:crs"" in clusterware alert<nodename>.log, fixed in 11.2.0.2
bundle2, 11.2.0.3

Bug:9897335 - Instance alert.log Flooded With "NOTE: [emcrsp.bin@<HOSTNAME1> (TNS V1-V3) 3159] opening
OCR file", refer to Document 1307063.1 for details.

Bug:10105195 - CSSD FAILED TO START WITH CLSGPNP_CALL_AGAIN ERRORS, refer to note 1212543.1 for details.

Bug:9234660 - High oraagent/orarootagent/crsd.bin resource usage, refer to Document 1062676.1 for details

Bug:10056593 - Failed to add (property/value):('OLD_OCR_ID/'-1') for checkpoint:ROOTCRS_OLDHOMEINFO.Error


code is 256, fixed in 11.2.0.3, the warning is ignorable

Bug:10011084 - Undefined subroutine &main::read_file called at crspatch.pm, refer to Document 1268390.1 for
details.

Bug:10190153 - ORA.CTSSD AND ORA.CRSD GOES OFFLINE AFTER KILL GIPC ON CRS MASTER, fixed in 11.2.0.2
Bundle3, 11.2.0.3

Bug:9795321 - Solaris: Wrong MTU Size for VIP or HAIP, refer to Document 1290585.1 for details

Bug:10371451 - CSSD aborting from thread GMClientListener, refer to Document 1306137.1 - "ocssd.bin Fails to
Start: clssgmPeerListener: connected to 1 of 3" for details

Bug:11807012 - oraagent.bin exits after check timed out, refer to Document 1323679.1 for details

For known issues that affect each bundle, refer to Document 1272288.1 - 11.2.0.2.X Grid Infrastructure Bundle Known
Issues

M isce llane ous

Bug:10205230 - ORA-600 or Data Corruption possible during shutdown normal/transactional/immediate of RAC instances in
a rolling fashion, refer to Document 1318986.1 for details

Bug:10121931 - DBCA CONFIGURE DATABASE OPTION DISABLED IF 11201 DATABASE PRESENT, refer to Document
10121931.8 for more details, one-off patches exist

Bug:11069614 - RDBMS INSTANCE CRASH DUE TO SLOW REAP OF GIPC MESSAGES ON CMT SYSTEMS, refer to Document
1287709.1 - "ocssd.bin High CPU Usage and Instance Crashes With ORA-29770" for details

Refer to Document 1179474.1 for 11.2.0.2 Patch Set Availability and Known Issues

Refer to Document 948456.1 for Known Issues Between Pre-11.2 Database and 11gR2 Grid Infrastructure

Refer to Document 810394.1 for RAC and Oracle Clusterware Starter Kit and Best Practices
Scalability RAC Community

To discuss this topic further with Oracle experts and industry peers, we encourage you to review, join or start a discussion
in the My Oracle Support Scalability RAC Community.
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1fxc8yfoo_511&id=1312225.1 5/7
22/11/24, 14:13 Document 1312225.1

REFERENCES
BUG:9795321 - MTU SIZE FOR VIP UNDER 11GR2 GRID INFRASTRUCTURE

NOTE:1212703.1 - Grid Infrastructure Startup During Patching, Install or Upgrade May Fail Due to Multicasting Requirement
NOTE:1233505.1 - Checklist for PRVF-10037 : Failed to retrieve storage type for xx on
NOTE:1287709.1 - ocssd.bin High CPU Usage, Instance Crashes With ORA-29702 or ORA-29770 or ORA-29701 With
"gipcWait failed with 16"
BUG:10105195 - PROC-32 ACCESSING OCR; CRS DOES NOT COME UP ON NODE
BUG:10119895 - PSU2 9655006 DOESN'T UPDATE /ETC/INIT.D/OHASD AND /ETC/INIT.D/INIT.OHASD PROPERL
NOTE:1051763.1 - INS-20802 PRVF-4172 Reported after Successful Upgrade to 11gR2 Grid Infrastructure

BUG:10056593 - LNX64-112020-UD: FAIL TO ADD OLD_OCR_ID PROPERTY FOR ROOTCRS_OLDHOMEINFO


NOTE:1289922.1 - Resource ora.crf Fails to Start in 11.2.0.2
NOTE:1235944.1 - AIX: 11gR2 root.sh Fails as crsd.bin Does not Come up
NOTE:1274629.1 - Pre-requisite for 11.2.0.1 to 11.2.0.2 ASM Rolling Upgrade
NOTE:1281913.1 - root Script (root.sh or rootupgrade.sh) Fails if ORACLE_BASE is set to /opt/oracle
NOTE:1257924.1 - Grid Infrastructure Patch Does not Update Files in $GRID_HOME/crs/sbs Including init.ohasd..
NOTE:1259874.1 - root.sh Fails as the ora.asm resource is not ONLINE or PROTL-16 Reports
NOTE:1287496.1 - Many Connections From oraagent.bin to ASM or Database Instance (Likely ORA-00020)

NOTE:1252334.1 - Grid Infrastructure Configuration Fails as MDNSD can not Register on Network Adapter with Invalid Mask
0.0.0.0

NOTE:1323679.1 - oraagent.bin Exits After Check Timed Out


NOTE:969254.1 - How to Proceed from Failed Upgrade to 11gR2 Grid Infrastructure on Linux/Unix
NOTE:1265276.1 - ACFS-9327 ACFS-9121 ACFS-9310: ADVM/ACFS installation failed
NOTE:1267569.1 - Linux: PRVF-5449 : Check of Voting Disk location "ORCL:(ORCL:)" failed
NOTE:1306137.1 - ocssd.bin Fails to Start: clssgmPeerListener: connected to 1 of 3
NOTE:1307063.1 - Instance alert.log Flooded With "NOTE: [emcrsp.bin@ (TNS V1-V3) 3159] opening OCR file"
NOTE:1315203.1 - ACFS Drivers Fail To Install During Root.Sh Execution Of 11.2.0.2 GI Standalone On Aix
NOTE:1315926.1 - 11.2.0.1 to 11.2.0.2 Database Upgrade on Exadata Database Machine
BUG:3841387 - RACGIMON DOESN'T DUMP TRACE

NOTE:970166.1 - INS-20702 "checkFreeDiskSpace" Reported During 11gR2 Installation

NOTE:1210883.1 - Grid Infrastructure Redundant Interconnect and ora.cluster_interconnect.haip


NOTE:1212543.1 - CSSD FAILED TO START WITH CLSGPNP_CALL_AGAIN ERRORS

NOTE:983713.1 - HP-UX: 11gR2 runInstaller Fails with "An internal error occurred within cluster verification framework"
NOTE:986657.1 - AIX: 11gR2 runInstaller Warns INS-13001 while CLUVFY Reports "Reference data is not available for
verifying prerequisites on this operating system distribution"
NOTE:986822.1 - How to Debug CVU / Collect CVU Trace Generated by RUNCLUVFY.SH

NOTE:952925.1 - NETCA & ASMCA Fail during Upgrade of CRS/ASM to Grid Infrastructure 11gR2 if ORA_CRS_HOME is Set
BUG:11871469 - ORAAGENT CHECK TASK IS TIMING OUT WHICH IS FORCING THE AGENT TO ABORT AND EXIT
NOTE:1056322.1 - Troubleshoot Grid Infrastructure/RAC Database installer/runInstaller Issues
NOTE:1050908.1 - Troubleshoot Grid Infrastructure Startup Issues
NOTE:1056693.1 - How to Configure NTP or Windows Time for Oracle Clusterware
NOTE:1058576.1 - PRVF-4178 Reported from CLUVFY
NOTE:1061025.1 - PRVF-4125 Reported from CLUVFY
NOTE:1062676.1 - ORAAGENT or ORAROOTAGENT High Resource (CPU, Memory etc) Usage
NOTE:1062682.1 - GI rootupgrade.sh Fails due to Wrong Private Network Configuration
NOTE:1056713.1 - TOP Note: Solutions for Typical Grid Infrastructure/RAC Database runInstaller/DBCA for RAC Issues
NOTE:1114533.1 - Bugs fixed in Oracle 11.2.0.x DB Bundle Patches for Microsoft Windows Platform

BUG:10299006 - AFTER 11.2.0.2 UPGRADE, ORAAGENT.BIN CONNECTS TO DATABASE WITH TOO MANY SESSIONS
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1fxc8yfoo_511&id=1312225.1 6/7
22/11/24, 14:13 Document 1312225.1
BUG:10362257 - PERMISSION PROBLEMS RUNNING ROOT SCRIPT IF ORACLE_BASE IS IN /OPT/ORACLE

BUG:10374874 - RBAL GOT UNRESPONSIVE WAITING FOR A RESPONSE FROM OCSSD


BUG:11069614 - RDBMS INSTANCE CRASH DUE TO SLOW REAP OF GIPC MESSAGES ON CMT SYSTEMS
NOTE:1056195.1 - INS-20702 Reported during 11gR2 Installation on getSharedPartitionListCVU
NOTE:1054902.1 - How to Validate Network and Name Resolution Setup for the Clusterware and RAC
NOTE:1067606.1 - CRS-2674 Failed to start ora.cssd during rootupgrade.sh

NOTE:10121931.8 - Bug 10121931 - DBCA configure database option is disabled if an 11.2.0.1 database present
NOTE:10379703.8 - Bug 10379703 - Grid install error if users Unix UID over 6 digits long
NOTE:1053055.1 - HACMP: 11gR2 rootupgrade.sh Fails as "Symbol ras_arg_t (number 8) is not exported from dependent
module libttsh11.so
NOTE:1053970.1 - Troubleshooting 11.2 or 12.1 Grid Infrastructure root.sh Issues
NOTE:1093014.1 - Failed OCR Upgrade To 11.2 Due to OCRMIRROR Corruption
NOTE:1102283.1 - 11gR2 rootupgrade.sh Fails as cssvfupgd Can not Upgrade Voting Disk
NOTE:1113073.1 - ASMCA Fails When Upgrading to 11.2 due to Different ASM/CRS User or Non-default ASM Name
NOTE:974481.1 - INS-20802 PRVF-9802 PRVF-5184 PRVF-5186 After Successful Upgrade to 11gR2 Grid Infrastructure
BUG:11877079 - HUNDREDS OF ORAAGENT.BIN@HOSTNAME SESSSIONS IN 11.2.0.2 DATABASE
NOTE:1135933.1 - PRVF-4195 Reported while Executing "cluvfy comp ocr"
NOTE:1141963.1 - 11gR2 rootupgrade.sh Fails as Environment Variable PATH Points to Wrong CRS Home
NOTE:1318986.1 - ORA-600 or Data Corruption Possible During Shutdown Normal/Transactional/Immediate of RAC
Instances in a Rolling Fashion
NOTE:1179474.1 - 11.2.0.2 Patch Set - Availability and Known Issues
NOTE:1210863.1 - Device Checks for ASM Fails with PRVF-5150: Path ORCL: is not a valid path
NOTE:887471.1 - PRVF-4664 PRVF-4657: Found inconsistent name resolution entries for SCAN name
NOTE:948382.1 - INS-08109 Unexpected error occurred While Validating Inputs At State 'nodeSelectionPage'
NOTE:1290585.1 - Solaris: Wrong MTU Size for VIP or HAIP
NOTE:1296579.1 - PRVF-10205 : The VIPs do not all share the same subnetwork
NOTE:948456.1 - Pre 11.2 Database Issues in 11gR2 Grid Infrastructure Environment
NOTE:810394.1 - RAC and Oracle Clusterware Best Practices and Starter Kit (Platform Independent)
NOTE:1272288.1 - 11.2.0.2.X Grid Infrastructure Bundle/PSU Known Issues
NOTE:1329597.1 - AIX: rootupgrade.sh Fails With "Undefined subroutine &main::isASMRunning called at
/ocw/grid/crs/install/rootcrs.pl"
NOTE:1268390.1 - roothas.pl -patch or rootcrs.pl -patch Fails with 'Undefined subroutine'
NOTE:1271996.1 - 11.2 Grid Install Fails with SEVERE: [FATAL] [INS-13013], and PRVF-5640 or a Warning in "Task
resolv.conf Integrity"

Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1fxc8yfoo_511&id=1312225.1 7/7

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy