Could not execute batch command.[SQL: SQL not available] -- ORACLE error ORA-03137

Products

• CA Continuous Delivery Automation - Automation Engine

Issue/Introduction

After deploying a new Automation Engine (AE) 12.3.8 and ARA Version "10.0.8+build.100008000041121. A problem comes up when a user tries to edit dynamic properties of an entity

Changing the type of the property from "static value" to "Expression" or "prompt" a error message popups in AWI in the RA prospective:  could not execute batch command.[SQL: SQL not available]

The CDA Log file contains the following Oracle error message:

=========================================================================

2022-03-08 15:09:39,161 [23(EUT0/2000/WES7BB/DE)] ERROR Ventum.Bond2.Web.Infrastructure.Widget.BaseWidget - could not execute batch command.[SQL: SQL not available]
NHibernate.Exceptions.GenericADOException: could not execute batch command.[SQL: SQL not available] ---> Oracle.DataAccess.Client.OracleException: ORA-03137: TTC-Paket in falschem Format abgelehnt: [kpoal8Check-4] [2] [1] [] [] [] [] []
   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, String procedure, IntPtr opsErrCtx, OpoSqlValCtx* pOpoSqlValCtx, Object src, Boolean bCheck)
   at Oracle.DataAccess.Client.OracleCommand.ExecuteNonQuery()
   at NHibernate.AdoNet.OracleDataClientBatchingBatcher.DoExecuteBatch(DbCommand ps)
   --- End of inner exception stack trace ---
   at NHibernate.AdoNet.OracleDataClientBatchingBatcher.DoExecuteBatch(DbCommand ps)
   at NHibernate.AdoNet.AbstractBatcher.ExecuteBatchWithTiming(DbCommand ps)
   at NHibernate.AdoNet.AbstractBatcher.ExecuteBatch()
   at NHibernate.Engine.ActionQueue.ExecuteActions()
   at NHibernate.Event.Default.AbstractFlushingEventListener.PerformExecutions(IEventSource session)
   at NHibernate.Event.Default.DefaultFlushEventListener.OnFlush(FlushEvent event)
   at NHibernate.Impl.SessionImpl.Flush()
   at NHibernate.Impl.SessionImpl.BeforeTransactionCompletion(ITransaction tx)
   at NHibernate.Transaction.AdoTransaction.Commit()
   at Ventum.Bond2.Hibernate.SessionManager.TransactionScope.Commit() in E:\Jenkins\workspace\bond_release_10\Projects\Ventum.Bond2.Services.Impl\Hibernate\TransactionScope.cs:line 56
   at Ventum.Bond2.Hibernate.SessionScopeInterceptor.Proceed(Action doInvoke, TransactionMode mode) in E:\Jenkins\workspace\bond_release_10\Projects\Ventum.Bond2.Services.Impl\Hibernate\SessionScopeInterceptor.cs:line 41
   at Ventum.Bond2.Hibernate.SessionScopeInterceptor.Intercept(IInvocation invocation) in E:\Jenkins\workspace\bond_release_10\Projects\Ventum.Bond2.Services.Impl\Hibernate\SessionScopeInterceptor.cs:line 183
   at Castle.DynamicProxy.AbstractInvocation.Proceed()
   at Ventum.Bond2.Web.Widgets.DynamicProperty.DynamicPropertyEditDetailsWidget.Edit_OnClick(Object sender, EventArgs e) in E:\Jenkins\workspace\bond_release_10\Projects\Ventum.Bond2.Web\Widgets.DynamicProperty\DynamicPropertyEditDetailsWidget.ascx.cs:line 101

=========================================================================

 

 

Cause

The Oracle Error ORA-03137 generally points on a issue related to Oracle, more particularly on problem in the communication between the Oracle client and the Oracle engine

Usually an this error is documented in the different links:

http://www.dba-oracle.com/t_ora_03137_ttc_protocol_internal_error.htm

https://support.oracle.com/epmos/faces/DocumentDisplay?parent=EXTERNAL_SEARCH&sourceId=PROBLEM&id=2267564.1&_adf.ctrl-state=3huv2x52s_4&_afrLoop=185882809367489

https://ittutorial.org/ora-03137-ttc-protocol-internal-error/

Environment

Release : 12.3.8 Component : RELEASE MANAGER 10.0.8

Resolution

The problem in this particular case was that the Oracle client 12.1 was used to communicate with an Oracle Database version 19. Both component were only partially compatible, and errors as documented abore could show up, when applying some modifications in CDA.

The Problem was solved by updating the Oracle client to version 19.