Troubleshooting
Problem
Schedule_PurgeService fails with Error occured in online purging process.
Symptom
Gentran Integration Suite, all versions.
MySQL database
Scheduled Purge service fails with error "Error occured in online purging process"
This problem could occur after a BP has looped and created large numbers of rows in the database tables.
error in wf log:-
ERROR 000110011401 WORKFLOW.WORKFLOW.ERR_SQLException191 WorkFlowContext .persist() caught SQLException while attempting to persist data
SQL Error Code: 1206
SQL State: HY000
java.sql.SQLException: The total number of locks exceeds the lock table size
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2975)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1600)
at com.mysql.jdbc.ServerPreparedStatement.serverExecute(ServerPreparedStatement.java:1129)
at com.mysql.jdbc.ServerPreparedStatement.executeInternal(ServerPreparedStatement.java:681)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1368)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1283)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1268)
at com.sterlingcommerce.woodstock.workflow.WorkFlowContext.doArchive(WorkFlowContext.java:5073)
at com.sterlingcommerce.woodstock.workflow.WorkFlowContext.persist(WorkFlowContext.java:4305)
at com.sterlingcommerce.woodstock.workflow.WorkFlowContext.persist(WorkFlowContext.java:3729)
at com.sterlingcommerce.woodstock.workflow.engine.WEHelper.dispatch(WEHelper.java:1262)
at com.sterlingcommerce.woodstock.workflow.engine.WEHelper.dispatch(WEHelper.java:1104)
at com.sterlingcommerce.woodstock.workflow.engine.WorkFlowEngineRMIImpl.dispatch(WorkFlowEngineRMIImpl.java:964)
at com.sterlingcommerce.woodstock.workflow.Dispatcher.run(Dispatcher.java:72)
at java.lang.Thread.run(Thread.java:810)
Resolving The Problem
1. Stop GIS.
2. Take a backup of the Mysql folder.
3. Use notepad to modify the file \mysql\data\my.cnf.in
Make a note of the value in the “innodb_buffer_pool_size” parameter.
Change that parameter to 512M
Save the file.
4. Run \bin\setupfiles
5. Start GIS.
6. Run the purge process (it could run for a long time).
7. If the purge still fails, repeat steps 1, 3, 4, 5 and 6 with an increased value.
8. Stop GIS
9. Change the “innodb_buffer_pool_size” parameter back to the original value
9. Run \bin\setupfiles
10. Start GIS
11. Run the purge process to confirm it works OK.
Historical Number
NFX9025
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21555131