Execution of ARA V5 Workflow in ARA does not trigger Job in AE, ARA User not able to see monitor Workflow button
search cancel

Execution of ARA V5 Workflow in ARA does not trigger Job in AE, ARA User not able to see monitor Workflow button


Article ID: 87503


Updated On:


CA Automic Workload Automation - Automation Engine


Affects Release version(s): 5

Error Message :

The ARA user can execute a workflow in ARA V5, however, it not being triggered in AE.  In addition, the ARA User is unable to see the monitor workflow button in ARA V5.

The issue is seen after experiencing a problem with ARA's database and messages similar to those below are generated.

2017-10-04 13:06:02,202 [55-RM.JobQueue] [AUT_PRD/100] ERROR RM.JobProcessor - Error handling job #7821731 NHibernate.TransactionException: Begin failed with SQL exception ---> Oracle.DataAccess.Client.OracleException: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor at Oracle.DataAccess.Client.OracleException.HandleErrorHelper(Int32 errCode, OracleConnection conn, IntPtr opsErrCtx, OpoSqlValCtx* pOpoSqlValCtx, Object src, String procedure, Boolean bCheck, Int32 isRecoverable) at Oracle.DataAccess.Client.OracleException.HandleError(Int32 errCode, OracleConnection conn, IntPtr opsErrCtx, Object src) at Oracle.DataAccess.Client.OracleConnection.Open() at NHibernate.Connection.DriverConnectionProvider.GetConnection() at Ventum.Bond2.Hibernate.HibernateConnectionProvider.GetConnection() at NHibernate.AdoNet.ConnectionManager.GetConnection() at NHibernate.Transaction.AdoTransaction.Begin(IsolationLevel isolationLevel) --- End of inner exception stack trace --- at NHibernate.Transaction.AdoTransaction.Begin(IsolationLevel isolationLevel) at NHibernate.Impl.SessionImpl.BeginTransaction(IsolationLevel isolationLevel) at Ventum.Bond2.Hibernate.SessionManager.OpenTransactionScope(Nullable`1 isolationLevel) at _dynamic_Ventum.Bond2.Hibernate.SessionManager.OpenTransactionScope(Object , Object[] ) at Spring.Reflection.Dynamic.SafeMethod.Invoke(Object target, Object[] arguments) at Spring.Aop.Framework.DynamicMethodInvocation.InvokeJoinpoint() at Ventum.Bond2.Infrastructure.ExceptionLoggingAdvice.InvokeUnderLog(IMethodInvocation invocation, ILog log) at CompositionAopProxy_238419c1f54f451ab86d695362f7bd7a.OpenTransactionScope(Nullable`1 isolationLevel) at Ventum.Common.Utils.SessionUtils.OpenTransactionScopeAndLock[TObjectForLock](ISessionManager sessionManager, Object idToLock, LockMode lockMode, Nullable`1 isolation) at Ventum.Bond2.LoadBalancing.TaskExecutors.JobMasterProcessor.TryLockAndProcessJob(Int64 jobId) at Ventum.Bond2.LoadBalancing.TaskExecutors.JobMasterProcessor.ProcessJob(Int64 jobId) 2017-10-04 13:06:02,295 [60-RM.JobQueue] [AUT_PRD/100] ERROR Ventum.Bond2.Hibernate.SessionManager - Entering OpenTransactionScope

Once the DBA corrects the TNS settings, the error message will no longer be present in ARA's log.

However, when a workflow is executed, nothing happens in the Automation Engine (AE) and the monitor button in ARA is not available.



OS Version: N/A


Cause type:
Root Cause: When the TSK table (task table) in ARA's Database fills up with a lot of tasks, the ARA system is not able to process the tasks on time.


Update to a fix version listed below or a newer version if available.

Fixed in ARA 6.7.8 and is compatible with Automation Engine versions 11.2, 12.0 and 12.1 and above.


Fix Status: Released

Fix Version(s):
ARA 6.7.8 - Available

Additional Information

Workaround :
  1. Stop all of the IIS instances
  2. Run the statement below:
DELETE (select * from TskFlag f INNER JOIN Tsk t on f.TaskId=t.Id where t.Type=99); 
DELETE Tsk where Type=99;