My Oracle Support Banner

Patch Set Failed To Install With Error: Missing File when upgrading from 5.0.0.1 to 5.0.0.2 (Doc ID 1378079.1)

Last updated on AUGUST 16, 2019

Applies to:

Oracle Communications Service Broker - Version 5.0.0.1 and later
Information in this document applies to any platform.

Symptoms

An error is displayed when executing the upgrade script from OCSB 5.0.0.1 to 5.0.0.2 (PS1 to PS2).

On patch set installation the following error is received:

  <USER>@<HOST>:<SSU_DOMAIN_HOME>/admin_console$./script.sh  <DIR>/patchset/patch_set_ssu.jar 
  == BEGIN SCRIPT 
  File: patch_set_ssu.jar 
  Patch version: patch_set_5002_ssu 
  Make sure to backup your domain before continuing. 
  Enter path to domain: <DIR>
  javax.management.MBeanException: java.io.FileNotFoundException: 
  <SSU_DOMAIN_HOME>/modules/oracle.axia.platform.managementagent-1.0.0.0.jar (No such file or directory) 
   at 
  com.sun.jmx.mbeanserver.MBeanIntrospector.unwrapInvocationTargetException(MBeanIntrospector.java:283) 
   at 
  com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:210) 
   
   at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:120) 
   at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:262) 
   at javax.management.StandardMBean.invoke(StandardMBean.java:391) 
   at 
  com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836) 
   at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761) 
   at 
  oracle.axia.library.mbeanplayer.PatchPlayer.executeMBeanOperation(PatchPlayer.java:260) 
   at 
  oracle.axia.library.mbeanplayer.PatchPlayer.executeDomainMBean(PatchPlayer.java:232) 
   at 
  oracle.axia.library.mbeanplayer.PatchPlayer.execute(PatchPlayer.java:176) 
   at 
  oracle.axia.library.mbeanplayer.PatchPlayer.executeLocally(PatchPlayer.java:364) 
   at 
  oracle.axia.library.mbeanplayer.MBeanPlayerActivator.start(MBeanPlayerActivator.java:32) 
   at 
  org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:783) 
   at 
  org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:774) 
   at 
  org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:755) 
   at 
  org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:370) 
   at 
  org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:374) 
   at 
  org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1067) 
  ......
  == END SCRIPT 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.