OSM Deployment Of Cartridge In 7.2.2 Version Fails .
(Doc ID 1580884.1)
Last updated on APRIL 03, 2023
Applies to:
Oracle Communications Order and Service Management - Version 7.2.2 and laterInformation in this document applies to any platform.
**** Currency checked on 13-Oct-2017********
Symptoms
Deployment of cartridge fails with below error message.
com.mslv.oms.dataaccesslayer.ProxyException: ORA-20012: Order not found. order id = 11
ORA-06512: ved linje 1
Nested Exception: ORA-20012: Order not found. order id = 11
ORA-06512: ved linje 1
Nested Exception: java.sql.SQLException: ORA-20012: Order not found. order id = 11
ORA-06512: ved linje 1
at com.mslv.oms.dataaccesslayer.AbstractProxy.execute(Unknown Source)
at com.mslv.oms.handler.order.cache.jboss.JBossOrderCacheManager.a(Unknown Source)
at com.mslv.oms.handler.order.cache.jboss.JBossOrderCacheManager.b(Unknown Source)
at com.mslv.oms.handler.order.cache.jboss.JBossOrderCacheManager.getCachedOrder(Unknown Source)
at com.mslv.oms.handler.order.h.a(Unknown Source)
at com.mslv.oms.automation.plugin.AutomationEventHandlerImpl.a(Unknown Source)
at com.mslv.oms.automation.plugin.AutomationEventHandlerImpl.c(Unknown Source)
at com.mslv.oms.automation.plugin.AutomationEventHandlerImpl.processMessage(Unknown Source)
at com.mslv.oms.automation.AutomationDispatcher.onLocalMessage(Unknown Source)
at oracle.communications.ordermanagement.cluster.message.a.a(Unknown Source)
at oracle.communications.ordermanagement.cluster.message.impl.a.a(Unknown Source)
at oracle.communications.ordermanagement.cluster.message.impl.a.a(Unknown Source)
at oracle.communications.ordermanagement.cluster.impl.a.a(Unknown Source)
at oracle.communications.ordermanagement.cluster.message.ClusterMessageHandlerBean.onMessage(Unknown Source)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:583)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:486)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:388)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4659)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:4345)
at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3821)
at weblogic.jms.client.JMSSession.access$000(JMSSession.java:115)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5170)
at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
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 |
| Cause |
| Solution |