Portal App Deployments Fail - OID Entries Not Populating Correctly (Doc ID 1985784.1)

Last updated on NOVEMBER 22, 2016

Applies to:

Oracle WebCenter Portal - Version 11.1.1.8.0 and later
Information in this document applies to any platform.

Symptoms

Environment and Issue
----------------------------------
There are two WCP Custom portal applications running on a shared Webcenter portal 11.1.1.8.3/WLS10.3.6 cluster connected to OID 11.1.1.7 as JPS storage.
There are two logical applications; the first has only one deployment profile, the second has 3 deployment profiles.

Application deployments fail as application OID entries under cn=jpsroot are incompletely populated.


Steps to reproduce the error/issue
-------------------------------------------------
Here is a sequence of error events, starting from a freshly re-booted domain with neither of the applications deployed and OID is devoid of jpsroot entries for either:

1. First application deploys and works okay, OID entries for the application appear complete, no errors in either deployment or application usage.

2. Second application may deploy, but its OID entries are only partially populated and the deployment is in a failed state logging an error like:

<Feb 6, 2015 10:39:05 AM EET> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1423211944447' for task '1'. Error is: 'javax.naming.NameNotFoundException: [LDAP: error code 32 - No Such Object]; remaining name 'cn=Functions,cn=FOKTCustomerDataService_FOCustomerDataServiceSDO,cn=portalWCSDEVdomain,cn=JPSContext,cn=jpsroot''

3. After the second build fails, running the first application deployment again its (or some of its subapps) OID entries also come up populated only partially, effectively crippling that application too, logging a similar error as above.

The standard build sequence for both applications is:

a) undeploy apps
b) remove MDS partitions
c) then build and deploy apps.

It does not matter which application gets deployed first, the problem still occurs.


Error, if any, fully documented
------------------------------------------
This error occurs after deploying a second application, and then again after trying to deploy the first application again:

<Feb 6, 2015 10:39:05 AM EET> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1423211944447' for task '1'. Error is: 'javax.naming.NameNotFoundException: [LDAP: error code 32 - No Such Object]; remaining name 'cn=Functions,cn=FOKTCustomerDataService_FOCustomerDataServiceSDO,cn=portalWCSDEVdomain,cn=JPSContext,cn=jpsroot''


Business Impact
--------------------------
The applications are unusable as the deployment fails.

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