This discussion is archived
0 Replies Latest reply: Mar 1, 2012 6:49 AM by 921136 RSS

O2A Solution, OSM 7.0.3 -Submit Revision Order - Getting a database error

921136 Newbie
Currently Being Moderated
Hello,

we have created a custom SOM Cartridge for VoIP Orders which is called by O2A LF (CommunicationsProvisioningFulfillmentOrderPIP). We are trying to reproduce the following scenario.

We submit a salesorder that has verbCode SIMULATE_FAIL_VOIP_SERVICEBUNDLE_FAULT. We enhance Control Map in the above mentioned Custom VoIP Cartridge.

Fallout simulates successfully. Then we submit a new salesorder with process Verb Code, a significant data change (e.g. Password, Number, etc..) and Revision Number 2 . Amendment Order is created successfully at COM and SOM and redo Task of CommunicationsProvisioningFulfillmentOrderPIP Cartridge is happening to SOM. This creates a new VoIP Order at SOM actual provisioning but during the CommunicationsProvisioningFulfillmentOrderPIP update after VoIP order completion we are getting the following error...

<AdminServer> <ExecuteThread: '12' for queue: 'oms.automation'> <oms-automation> <> <> <1330609363640> <BEA-010213> <Message-Driven EJB: CommunicationsServicesProvisioningOrderUpdateSITask.CommunicationsServicesProvisioningOrderUpdateBeanMDB's transaction was rolled back. The transaction details are: Xid=BEA1-663E3AB4D830560E5D6A(9023958),Status=Rolled back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds left=60,XAServerResourceInfo[WLStore_osm_domain_oms_jms_store]=(ServerResourceInfo[WLStore_osm_domain_oms_jms_store]=(state=rolledback,assigned=AdminServer),xar=WLStore_osm_domain_oms_jms_store31156775,re-Registered = false),NonXAServerResourceInfo[WL_JDBC_LLR_POOL.oms_pool]=(ServerResourceInfo[WL_JDBC_LLR_POOL.oms_pool]=(state=rolledback,assigned=AdminServer),nonXAResource=JDBC LLR, pool=oms_pool, table=WL_LLR_ADMINSERVER),SCInfo[osm_domain+AdminServer]=(state=rolledback),properties=({weblogic.transaction.nonXAResource=WL_JDBC_LLR_POOL.oms_pool, weblogic.jdbc=t3://192.168.5.112:17001, weblogic.jdbc.llr=oms_pool}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=AdminServer+192.168.5.112:17001+osm_domain+t3+, XAResources={WLStore_osm_domain_oms_jms_store, WLStore_osm_domain_oss_jms_store, WSATGatewayRM_AdminServer_osm_domain, WLStore_osm_domain__WLS_AdminServer},NonXAResources={})],CoordinatorURL=AdminServer+192.168.5.112:17001+osm_domain+t3+).>

java.sql.SQLException: ORA-20502: Automation context not found.
ORA-06512: at "ORDERMGMT.OM_AUTOMATION_PKG", line 85
ORA-06512: at line 1

     at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
     at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:206)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:413)
     at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1034)
     at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:191)
     at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:950)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1223)
     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3386)
     at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3487)
     at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:3858)
     at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1374)
     at weblogic.jdbc.wrapper.PreparedStatement.execute(PreparedStatement.java:98)
     at com.mslv.oms.dataaccesslayer.CallableProxy.executeStatement(Unknown Source)

####<Mar 1, 2012 3:42:48 PM EET> <Error> <oms> <john-1d006c4d54> <AdminServer> <ExecuteThread: '12' for queue: 'oms.automation'> <oms-automation> <BEA1-66673AB4D830560E5D6A> <> <1330609368781> <BEA-000000> <plugin.InnerEarExternalReceiverDispatcher: Fail to find the automationContext for the JMS message due to
com.mslv.oms.automation.AutomationException: Fail to find the automationContext for the JMS message due to
     at oracle.communications.ordermanagement.automation.plugin.AbstractExternalReceiverDispatcher.a(Unknown Source)
     at oracle.communications.ordermanagement.automation.plugin.InnerEarExternalReceiverDispatcher.a(Unknown Source)
com.mslv.oms.dataaccesslayer.ProxyException: ORA-20502: Automation context not found.

If you have any experience about the above error pls help us to understand and resolve this.

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points