OSM Patch Upgrade Failed

(Doc ID 2115040.1)

Last updated on SEPTEMBER 18, 2017

Applies to:

Oracle Communications Order and Service Management - Version 7.2.2 and later
Information in this document applies to any platform.

Symptoms

The installation completed but it did not deploy oms.ear in weblogic. The following error appears in the Installer log.

 

[BasicOperation.dumpTmids():692] : {Target=OsmCluster, WebLogicTargetType=cluster, Name=oms}, targeted=true
[BasicOperation.deriveAppName():139] : appname established as: oms
<Mar 9, 2016 12:33:34 AM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, oms [archive: /customer/apps/osm/bin/oms.ear], to OsmCluster .>
java.io.IOException: [J2EE Deployment SPI:260080]Unable to define application install directory at '/tmp/oms.ear'. Directory could not be created or is a file.
at weblogic.deploy.api.internal.utils.InstallDir.<init>(InstallDir.java:60)
at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.upload(ServerConnectionImpl.java:643)

 

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