Wednesday, September 17, 2014

Error: /identity and /sysadmin won't Come up after OIM Upgrade to 11g R2 PS2

Cause: 

If we start OIM server using node manager we won't get this error, we get this error because we are setting properties only in weblogic admin console which won't take effect if we are starting server without node manager. 

Error:

<Sep 17, 2014 11:18:57 AM EDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'oracle.iam.console.identity.sysadmin.ear [Version=V2.0]' due to error weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: oracle.iam.ui.model, exact-match: false], [Extension-Name: oracle.rules, exact-match: false]..
weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: oracle.iam.ui.model, exact-match: false], [Extension-Name: oracle.rules, exact-match: false].
at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(CheckLibraryReferenceFlow.java:26)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:648)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:59)
Truncated. see log file for complete stacktrace
>
<Sep 17, 2014 11:18:57 AM EDT> <Emergency> <Deployer> <BEA-149259> <Server 'oim_server1' in cluster 'oim_Cluster' is being brought up in administration state due to failed deployments.>

Solution: 

Upgrade Process to Upgrade to R2PS2 could not take care of this and
setDomainEnv.sh was not modified as part of Upgrade Process. So it was
documented to add the UI performance parameters manually in the server
start-up params.

If these params are not getting picked up by node manager, one can
resort to editing the setDomainEnv.sh and provide these params in
EXTRA_JAVA_PROPERTIES

EXTRA_JAVA_PROPERTIES=" ${EXTRA_JAVA_PROPERTIES}
-DXL.HomeDir=${OIM_ORACLE_HOME}/server -Dscheduler.disabled=false
-Djava.security.auth.login.config=${OIM_ORACLE_HOME}/server/config/authwl.conf

-Dorg.owasp.esapi.resources=${OIM_ORACLE_HOME}/server/apps/oim.ear/APP-INF/cla
sses -Djbo.ampool.doampooling=true -Djbo.ampool.minavailablesize=1
-Djbo.ampool.maxavailablesize=120 -Djbo.recyclethreshold=60
-Djbo.ampool.timetolive=-1 -Djbo.load.components.lazily=true
-Djbo.doconnectionpooling=true -Djbo.txn.disconnect_level=1
-Djbo.connectfailover=false -Djbo.max.cursors=5
-Doracle.jdbc.implicitStatementCacheSize=5
-Doracle.jdbc.maxCachedBufferSize=19"
export EXTRA_JAVA_PROPERTIES

and check following libraries and other libraries after upgrade:


No comments:

Post a Comment

Other Posts