Tuesday, August 02, 2011

OPatch failed with error code = 255 and 14

Hi,

       If any one try to apply opath in your obiee server mchine please make which option choosed while installing obiee11g in your mechine.please make sure if have installed OBIEE11g ,windows server 2008 server 64 bit mechine , enterprice or software only installation option. don't install simple installation ...Opatch won't work.

Ex:
The Opatch error like below one,
************************
java.lang.UnsatisfiedLinkError: Can't load library: E:/OBIEE11G/Oracle_BI1/oui/lib/win32/oraInstaller.dll
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1657)
at java.lang.Runtime.load0(Runtime.java:770)
at java.lang.System.load(System.java:1004)
at oracle.sysman.oii.oiip.osd.win32.OiipwWin32NativeCalls.loadNativeLib(OiipwWin32NativeCalls.java:1509)
at oracle.sysman.oii.oiip.osd.win32.OiipwWin32NativeCalls.<clinit>(OiipwWin32NativeCalls.java:50)
at oracle.sysman.oii.oiip.oiipg.OiipgEnvironment.getEnv(OiipgEnvironment.java:211)
at oracle.sysman.oii.oiix.OiixEnvironmentOps.getEnv(OiixEnvironmentOps.java:53)
at oracle.opatch.OUIReplacer.getEnv(OUIReplacer.java:374)
at oracle.opatch.CmdLineParser.parse(CmdLineParser.java:995)
at oracle.opatch.OPatchSession.main(OPatchSession.java:1240)
at oracle.opatch.OPatch.main(OPatch.java:630)
Solution Satement:
===========
The error appears while running the OPATCH utility because, you have performed SIMPLE install on your 64 bit Windows server 2008 OS.
When a simple install is used a 32 bit JDK is used during install even though the win64 installer is used. This is because the WLS is installed by default with 32 bit JDK.
The only workaround to get rid of this issue is to download a JDK for 64 bit and use it to run opatch. Once done,
run opatch with -jdk option:
>opatch lsinventory -jdk <64 bit jdk location>
and OPATCH should work fine.
Please apply the patch using the OPATCH utility as mentioned in the patch readme.

For your Reference :
===============


- When searched the knowledge base found that the above error shows up when,
Customer uses SIMPLE install on their 64 bit Windows server 2008 OS.
When a simple install is used a 32 bit JDK is used during install even though the win64 installer is used.
This is because the WLS is installed by default with 32 bit JDK.
Please refer to,
Oracle note: Doc ID 1265807.1 (Error: "java.lang.UnsatisfiedLinkError: Can't Load Library: E:/OBIEE11G/Oracle_BI1/oui/lib/win32/oraInstaller.dll" Installing OBIEE 11g on 64-Bit Windows)
- When checked with the customer, got to know that they have also performed a SIMPLE install on their 64 bit Windows server 2008 platform.
- The only workaround here is to download a JDK for 64 bit and use it to run opatch. Once done,
run opatch with -jdk option:
>opatch lsinventory -jdk <64 bit jdk location>
and OPATCH should work fine.
Please apply the patch using the OPATCH utility as mentioned in the patch readme.
Thanks and Regards,

Deva

1 comment:

  1. OPatch failed with error code = 255 on Windows x64 in Azure. Within Azure cloud we recognized that windows file exporer deal with zip-files in a restricted mode (for IT-security). Batch files, Perl - and Python scripts were not shown or extracting when zip files are opend. If one upload and extracting an Oracle patch as a zip-file than "dangerous" files were not extracted. If we want to update $ORACLE_HOME/OPatch with latest patch and perform $ORACLE_HOME/OPatch/opatch lsinventory we got error 255. So we decided to use another zip tool (7z.exe in our case) and then all works fine.

    ReplyDelete