OPatch Fails Installing WebCenter Portal Patch In JDeveloper (Doc ID 1388459.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle WebCenter Portal - Version 11.1.1.5.0 and later
Oracle JDeveloper - Version 11.1.1.5.0 and later
Oracle SOA Suite - Version 11.1.1.5.0 and later
Oracle Business Process Management Suite - Version 11.1.1.5.0 and later
Information in this document applies to any platform.
This note is for WebCenter Portal patches install in JDeveloper but the same behavior can occur when applying patches for other products.

Symptoms


Trying to install the WebCenter patch on the JDeveloper ORACLE_HOME on a Windows machine, the following error:

Verifying the update...
Inventory check failed: Patch ID 13432139 is NOT registered in Oracle Home inventory.
Files check OK: Files from Patch ID 13432139 are present in Oracle Home.
ApplySession ha fallado: ApplySession ha fallado en la fase de modificaci¾n del
sistema... 'Verification of patch failed: Patch is not found in the Inventory. '

OPatch intentarß restaurar el sistema...
Restaurando el directorio raÝz de Oracle...
OPatch ha podido restaurar el sistema. Consulte el archivo log y el registro de
hora de los archivos para asegurarse de que el sistema estß en el estado que tenÝa antes de aplicar el parche.
--------------------------------------------------------------------------------

The following warnings have occurred during OPatch execution:
1) OUI-67124:Inventory check failed: Patch ID 13432139 is NOT registered in Orac
le Home inventory.
--------------------------------------------------------------------------------


OPatch failed with error code = 73

 

The patch installs fine in WebCenter ORACLE_HOME.

The ORACLE_HOME is set correctly.
The Windows PATH is set correctly with the path to the correct OPatch executable.

The correct Opatch version is installed following the patch readme file:

- For standalone JDeveloper install, download opatch 11.1.0.0.0 via <BUG 5912518>  from
My Oracle Support (formerly Metalink). Please follow the instructions to install this patch.


One of the symptoms is that the product.xml file that should be created during the first run of the OPatch doesn't exist after running it.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms