Bundle Patch 11gR2 PS3 161018 OUD Leaves Files With Wrong Unix Rights (Doc ID 2225490.1)

Last updated on JANUARY 20, 2017

Applies to:

Oracle Unified Directory - Version 11.1.2.3.161018 to 11.1.2.3.161018 [Release 11g]
Information in this document applies to any platform.

Symptoms

OUD Bundle Patch 11gR2 PS3 11.1.2.3.161018 leaves files with wrong Unix rights

Applying patches to this version of OUD results failure:

    OPatch failed with error code 39

Example of the issue (applying Patch 25322158 on top of OUD 11.1.2.3.161018)

Patch 25322158 
Jar Action: Destination File "/u01/app/oracle/product/fmw/oud/odsm-was/odsm.ear" does not exists or is not writeable
'oracle.idm.odsm, 11.1.2.3.0': Cannot update file '/u01/app/oracle/product/fmw/oud/odsm-was/odsm.ear:odsm.war:oud.jar' with '/com/sun/dps/server/workflowelement/proxyldap/ClientConnectionCachePlugin.class'
Jar Action: Destination File "/u01/app/oracle/product/fmw/oud/odsm-was/odsm.ear" does not exists or is not writeable
'oracle.idm.odsm, 11.1.2.3.0': Cannot update file '/u01/app/oracle/product/fmw/oud/odsm-was/odsm.ear:odsm.war:oud.jar' with '/com/sun/dps/server/workflowelement/proxyldap/GenericConnectionsPool.class'
..
..
Jar Action: Destination File "/u01/app/oracle/product/fmw/oud/lib/oud.jar" does not exists or is not writeable
'oracle.idm.oud, 11.1.2.3.0': Cannot update file '/u01/app/oracle/product/fmw/oud/lib/oud.jar' with '/org/opends/server/protocols/ldap/LDAPClientConnection$2.class'
Jar Action: Destination File "/u01/app/oracle/product/fmw/oud/lib/oud.jar" does not exists or is not writeable
'oracle.idm.oud, 11.1.2.3.0': Cannot update file '/u01/app/oracle/product/fmw/oud/lib/oud.jar' with '/org/opends/server/protocols/ldap/LDAPClientConnection$TimeoutWriteByteChannel.class'

Log file location: /u01/app/oracle/product/fmw/oud/cfgtoollogs/opatch/25322158_Jan_18_2017_11_34_31/apply2017-01-18_11-34-31AM_1.log

Recommended actions: This patch requires some components to be installed in the home. Either the Oracle Home doesn't have the components or this patch is not suitable for this Oracle Home.

OPatch failed with error code 39

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