Scope:
Enterprise Manager Grid Control - Version: 10.2.0.2 to 10.2.0.4
Sun Solaris SPARC (64-bit)
Solaris Operating System (SPARC) (64-bit)
Can effect any Opatch patching on Solaris SPARC 64 Bit
Issue:
While upgrading Enterprise Manager Grid Control 10.2.0.2 to 10.2.0.4, I faced an interesting issue which I later realized is, though not documented as one, a bug of the OPatch utility.
As a prereq of the upgrade, one needs to apply the patch 4329444 to the repository database. But on applying the patch through the OPatch utility, the session fails with the message:
Apply Session failed: ApplySession failed to prepare the system. OUI-67020:Interim Patch '4329444' is not applicable to OH '/oracle/grid/db10g'... Platforms not compatible
OPatch detects Platform ID 453 while this patch supports the following platforms: [ 23: Sun SPARC Solaris (64-BIT), ]
System intact, OPatch will not attempt to restore the system
So here OPatch stops being smart, and fails to recognize the Platform ID correctly as 23 and instead it picks 453.
Solution:
Before running OPatch, set the OPATCH_PLATFORM_ID environment variable to 23 by the following command
export OPATCH_PLATFORM_ID=23And OPatch is smart again!
Looks like it's been a long time, but great post; thanks for that info!
ReplyDeleteIn my case, the problem was on a Linux machine. The server is running RHEL5 64-bit. The real issue there is that OPatch compares the Platform ID to the ARU_ID stored in $ORACLE_HOME/inventory/ContentsXML/oraclehomeproperties.xml. On this server, that XML file contained the ARU designated for a 32-bit Linux system, not a 64-bit. I knew I had the right patch, so I just changed that env variable you pointed out here. Worked beautifully after that!
I opened an SR with Oracle asking where that info comes from (because it obviously isn't from uname); haven't heard back from them yet.
Amrita, thanks so much for this article! I was able to apply OPatch.
ReplyDelete