Novacura-clients getting ORA-12570

Flow Classic
1

Since a week our Novacura-clients are getting ‘Connection request timed out’-messages during normal working hours. In some periods system works well and in some periods almost all flow-clients get this message. Regular IFS-client that uses same Oracle-DB does not have this problem, IFS-system still responds when Flow-system has the time-outs.

I can see in logging some Time measurement exceptions like below

2025-08-28 02:45:45,966 - Time measurement exception

Oracle.ManagedDataAccess.Client.OracleException (0x80004005): ORA-12570: Network Session: Unexpected packet read error —> OracleInternal.Network.NetworkException (0x80004005): ORA-12570: Network Session: Unexpected packet read error —> System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

at System.Net.Sockets.Socket.Receive(Byte buffer, Int32 offset, Int32 size, SocketFlags socketFlags)

at OracleInternal.Network.ReaderStream.Read(OraBuf OB)

at OracleInternal.Network.ReaderStream.Read(OraBuf OB)

at OracleInternal.TTC.OraBufReader.GetDataFromNetwork()

at OracleInternal.TTC.OraBufReader.Read(Boolean bIgnoreData)

at OracleInternal.TTC.MarshallingEngine.UnmarshalUB1(Boolean bIgnoreData)

at OracleInternal.TTC.TTCExecuteSql.ReceiveExecuteResponse(Accessor& defineAccessors, Accessor bindAccessors, Boolean bHasReturningParams, SQLMetaData& sqlMetaData, SqlStatementType statementType, Int64 noOfRowsFetchedLastTime, Int32 noOfRowsToFetch, Int32& noOfRowsFetched, Int64& queryId, Int32 longFetchSize, Int64 initialLOBFetchSize, Int64 scnFromExecution, Boolean bAllInputBinds, Int32 arrayBindCount, DataUnmarshaller& dataUnmarshaller, MarshalBindParameterValueHelper& marshalBindParamsHelper, Int64& rowsAffectedByArrayBind, Boolean bDefineDone, Boolean& bMoreThanOneRowAffectedByDmlWithRetClause, List`1& implicitRSList, Boolean bLOBArrayFetchRequired)

at NovaCura.Flow.Connector.Database.ErrorTranslator.TranslateException(DatabaseType databaseType, Exception exception, Boolean throwException)

at NovaCura.Flow.Connector.Database.DatabaseConnectionParameters.Connect(String userEmptyOrNull, String passwordEmptyOrNull, String flowUserId, String runAs, String accessToken)

at NovaCura.Flow.Connector.DatabaseConnectorTask.InternalExecute(IReadOnlyDictionary`2 input, String userName, String password, IEnumerable`1 taskAuthorization, ITreasurer treasurer, IPackingKit packingKit, ITableTrinketFactory tableFactory, TimeMeasurement executeTimeMeasurementOrNull)

at NovaCura.Flow.Connector.DatabaseConnectorTask.Execute(IReadOnlyDictionary`2 input, String userName, String password, IEnumerable`1 taskAuthorization, ITreasurer treasurer, IPackingKit packingKit, ITableTrinketFactory tableFactory, TimeMeasurement timeMeasurement)

at NovaCura.Flow.Server.SharedServices.ConnectorTaskService.<>c__DisplayClass18_1.b__1(TimeMeasurement t)

at NovaCura.Framework.Diagnostic.RootTimeMeasurement.Measure[T](Func`2 func)

Attached logging for today.

Can you help to solve this issue?

We are running on Flow server 6.12.3.38865

Thanks for your help,

Jos

2

Hi,

Do you have flow installed on prem (not cloud hosted)?
As you indicate, it does sound like time outs. Do you have some performance logs of the server where flow is running? Thinking if processor or memory starvation.

It could also be that it is a pl sql query that just now started to take longer than 60 sec or what the timeout is, but if it happens more randomly across different workflows it sounds more likley to be on the server.

Would also be interesting to run the same query in a pl tool at the same time flow times out, just to see that its not the query itself.

Some ideas at least

3

Hi,

thanks for update, but on prem server Cpu is only 3% and memory 43%.

Do you know answer on below?

- Connection Timeout and Command Timeout are Connector settings. In flow, you connect a machine task to a Connector. Does it mean we can get a time-out on every machine-task within a flow?

- Does the flow quit when the first time-out appears or will it continue with next machine tasks?

Does command Timeout mean total processing time of 1 machine-task or 1 flow?

Greetings,

Jos

4
  • Yes. But although you can set the timeout on the db connector, other things might time out (IIS etc). So there are limits.
  • it quits (and roll back the non executed step normally)
  • I think machine task (but no promises). I think its nomally 90 seconds per machine task and aound 10 minutes for the entire flow.