What is the patch number ?
Are you following all of the steps in the README ? Does the inventory exist under C:\Program Files\oracle ? Can you post the contents of the opatch log file ?
Yeah I followed the README and all prereqs and system variableas are ok. The inventory exist under C:\Program Files\Oracle.
OPatch is not generating any log file because he don't get to the point of generating it. Knowing that there is a documention explaining the oui_loc option I could look at it but I cannot find any hints about that option.
Can you pl post the output of the "set" command just before you invoke OPatch ? MOS Doc 1231223.1 indicates that the 255 error is because the wrong version of OPatch is being used. Are there multiple ORACLE_HOMEs on this server ?
CIMPATH=d:\Program Files (x86)\Proficy\Proficy CIMPLICITY\exe
CommonProgramFiles=C:\Program Files\Common Files
CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
CommonProgramW6432=C:\Program Files\Common Files
Path=E:\Oracle\Ora11203\OPatch;E:\Oracle\Ora11203\bin;C:\Program Files (x86)\M1 Licensing;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;d:\Program Files (x86)\Proficy\Proficy CIMPLICITY\exe;d:\Program Files (x86)\Proficy\Proficy CIMPLICITY\exe;E:\Oracle\Ora11203\OPatch\jlib;E:\Oracle\Ora11203\perl\bin;e:\oracle\Client11G32\bin
PIHOME=C:\Program Files (x86)\PIPC
PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 44 Stepping 2, GenuineIntel
ProgramFiles(x86)=C:\Program Files (x86)
I have only one oracle home + an oracle client on this server.
Thanks for helping me.
I cant find anything obviously wrong - pl open an SR with Support for this issue. BTW, you do not need a separate client install - the server install also includes client binaries.
Was the latest OPatch version installed correctly ?
The latest installed oracle patch is 14095820 using OPatch version 18.104.22.168.0. I will open a support ticket with MOS and see where it will lead me.
First check that your ORACLE_HOME\oui\jlib directory exists. If so, check that you have "srvm.jar" in the directory. If not, copy and paste either the directory or the file (whichever you're missing) from another 22.214.171.124 environment. I had the same problem and Support was able to recreate the issue by renaming the jlib folder, but my specific issue was the missing "srvm.jar" file. Copying one over from another system resolved that issue. If you're missing "srvm/jar", you may also want to check ORACLE_HOME\jlib for "srvm.jar", as that could be an issue, as well (it was for me).
I want to thank you because you solved my issue !
The srvm.jar file was renamed srvm.jar.old for an obscure reason... probably someone who tried to resolve the opatch error code 41 (lock on a file) by renaming the locked file instead of renaming ORACLE_HOME\OPatch\jlib\oracle.opatch.classpath.jar.
So to resume the solution was to check if ORACLE_HOME\oui\jlib\srvm.jar was there with the appropriate file name.
Mine was named srvm.jar.old. Renaming it to srvm.jar did the job.
I can use opatch properly now.
Thank you again !