Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Simulation data flow stops abruptly with an error

SA-90950

Summary



The Simulation data flow stops abruptly with an error after processing 110 thousand of 800 thousand records. 


Error Messages



(tor$QueueBasedDataFlowExecutor) ERROR   - Unable to queue record for 5 minutes for processing in data flow. Retrying. Processing thread dump:
Thread[DataFlow-ParallelRun-Sim_Issue_F:477, Access group: [ABC:ReadOnly],5,main]
java.net.SocketInputStream.socketRead0(Native Method)
java.net.SocketInputStream.read(SocketInputStream.java:152)
java.net.SocketInputStream.read(SocketInputStream.java:122)
java.net.ManagedSocketInputStreamAPSIHighPerformanceNew.read(ManagedSocketInputStreamAPSIHighPerformanceNew.java:100)
org.postgresql.core.VisibleBufferedInputStream.readMore(VisibleBufferedInputStream.java:140)
org.postgresql.core.VisibleBufferedInputStream.ensureBytes(VisibleBufferedInputStream.java:109)
org.postgresql.core.VisibleBufferedInputStream.read(VisibleBufferedInputStream.java:67)
org.postgresql.core.PGStream.receiveChar(PGStream.java:288)
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1962)
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:300)
org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:428)
org.postgresql.jdbc.PgStatement.execute(PgStatement.java:354)
org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:169)
org.postgresql.jdbc.PgPreparedStatement.execute(PgPreparedStatement.java:158)
org.apache.tomcat.dbcp.dbcp2.DelegatingPreparedStatement.execute(DelegatingPreparedStatement.java:197)
org.apache.tomcat.dbcp.dbcp2.DelegatingPreparedStatement.execute(DelegatingPreparedStatement.java:197)
com.pega.pegarules.data.internal.store.DatabasePreparedStatementImpl.execute(DatabasePreparedStatementImpl.java:560)
com.pega.pegarules.data.internal.access.ListSpec.list(ListSpec.java:404)
com.pega.pegarules.data.internal.access.DBQueryExecutor.executeRDB(DBQueryExecutor.java:114)
com.pega.pegarules.data.internal.access.DBQueryExecutor.executeRDB(DBQueryExecutor.java:66)
com.pega.pegarules.data.internal.access.DatabaseImpl.executeRDB(DatabaseImpl.java:2962)
com.pega.pegarules.data.internal.access.DatabaseImpl.executeRDB(DatabaseImpl.java:2942)
com.pegarules.generated.pzExecuteIHLoadSQL_071027_yw6kP9MJrs5AO4JnNyFuxg.pzExecuteIHLoadSQL07_10_27(pzExecuteIHLoadSQL_071027_yw6kP9MJrs5AO4JnNyFuxg.java:139)



Steps to Reproduce



Run the Simulation data flow.


Root Cause



A defect or configuration issue in the operating environment. Records present in the Interaction History (IH) association table were inserted. The primary database (after database crash) did not run the statistics on the IH Fact table.


Resolution

Make the following change to the operating environment:
  1. Truncate the pr_data_ih_association IH Association table after taking backup
  2. Archive or purge the pr_data_ih_fact IH Fact table as per businees needs
  3. Run analysis or statistics on both the pr_data_ih_association and pr_data_ih_fact tables


 

Published December 20, 2019 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us