My Oracle Support Banner

Exception Raised On Activation Task In OSM-ASAP Interaction "ORA-20502: Automation context not found" (Doc ID 1347206.1)

Last updated on JULY 10, 2018

Applies to:

Oracle Communications Design Studio - Version 3.1.3 and later
Information in this document applies to any platform.

Symptoms

Using the activation task in OSM-ASAP interaction of Design Studio, the exception below occurs if both managed servers of the cluster architecture are active. If only one node is running we don’t see this exception. In the first case, although the exception occurs, the ASAP interaction works fine.

The problem occurred when we started using "activation task", a Design Studio component.

The error message in a log:

java.sql.SQLException: ORA-20502: Automation context not found.
ORA-06512: at "ORDERMGMT2.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)
at com.mslv.oms.dataaccesslayer.a.execute(Unknown Source)
at com.mslv.oms.dataaccesslayer.CallableProxy.execute(Unknown Source)
at com.mslv.oms.automation.plugin.AutomationDispatcherImpl.getClusterRequestContext(Unknown Source)
at oracle.communications.ordermanagement.cluster.message.ClusterMessageHandlerBean.onMessage(Unknown Source)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466)
at weblogic.ejb.container.internal.MDListener.run(MDListener.java:744)
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
References


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