奇怪的错误由电热水壶

生产只有在水壶5.4开发的简单移植。
的TRAN从MSSQL中提取数据，并插入到另一个MSSQL而没有任何其他操作。
我启用复选框“为插入使用批处理更新”。
通常，它会成功运行任何错误消息。
偶尔会出现此错误和它不能被重新运行TRAN被再现。

2016/09/18 08:00:36 - tb_dim_innchangelog.0 - SQL query : SELECT 
2016/09/18 08:00:36 - tb_dim_innchangelog.0 - StatID 
2016/09/18 08:00:36 - tb_dim_innchangelog.0 - , ChainID 
2016/09/18 08:00:36 - tb_dim_innchangelog.0 - , ChainName 
2016/09/18 08:00:36 - tb_dim_innchangelog.0 - , SaleDepartID 
2016/09/18 08:00:36 - tb_dim_innchangelog.0 - , AcivmntRegion 
2016/09/18 08:00:36 - tb_dim_innchangelog.0 - , Category 
2016/09/18 08:00:36 - tb_dim_innchangelog.0 - , Stage 
2016/09/18 08:00:36 - tb_dim_innchangelog.0 - , BeginDate 
2016/09/18 08:00:36 - tb_dim_innchangelog.0 - , EndDate 
2016/09/18 08:00:36 - tb_dim_innchangelog.0 - , createtime 
2016/09/18 08:00:36 - tb_dim_innchangelog.0 - , ChainFlag 
2016/09/18 08:00:36 - tb_dim_innchangelog.0 - , LastUpdateDate 
2016/09/18 08:00:36 - tb_dim_innchangelog.0 - FROM Dim_InnChangeLog 
2016/09/18 08:00:36 - load_dim_innchangelog.0 - Prepared statement : INSERT INTO Dim_InnChangeLog (StatID, ChainID, ChainName, SaleDepartID, AcivmntRegion, Category, Stage, BeginDate, EndDate, createtime, ChainFlag, LastUpdateDate) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) 
2016/09/18 08:00:36 - tb_dim_innchangelog.0 - Finished reading query, closing connection. 
2016/09/18 08:00:36 - BussinessDW_Source - Connection to database closed! 
2016/09/18 08:00:36 - tb_dim_innchangelog.0 - 完成处理 (I=19147, O=0, R=0, W=19147, U=0, E=0 
2016/09/18 08:00:56 - load_dim_innchangelog.0 - ERROR (version 5.4.0.1-130, build 1 from 2015-06-14_12-34-55 by buildguy) : Because of an error, this step can't continue: 
2016/09/18 08:00:56 - load_dim_innchangelog.0 - ERROR (version 5.4.0.1-130, build 1 from 2015-06-14_12-34-55 by buildguy) : org.pentaho.di.core.exception.KettleDatabaseException: 
2016/09/18 08:00:56 - load_dim_innchangelog.0 - Error performing rollback on connection 
2016/09/18 08:00:56 - load_dim_innchangelog.0 - Invalid state, the Connection object is closed. 
2016/09/18 08:00:56 - load_dim_innchangelog.0 - 
2016/09/18 08:00:56 - load_dim_innchangelog.0 -  at org.pentaho.di.core.database.Database.rollback(Database.java:867) 
2016/09/18 08:00:56 - load_dim_innchangelog.0 -  at org.pentaho.di.core.database.Database.rollback(Database.java:845) 
2016/09/18 08:00:56 - load_dim_innchangelog.0 -  at org.pentaho.di.trans.steps.tableoutput.TableOutput.writeToTable(TableOutput.java:332) 
2016/09/18 08:00:56 - load_dim_innchangelog.0 -  at org.pentaho.di.trans.steps.tableoutput.TableOutput.processRow(TableOutput.java:118) 
2016/09/18 08:00:56 - load_dim_innchangelog.0 -  at org.pentaho.di.trans.step.RunThread.run(RunThread.java:62) 
2016/09/18 08:00:56 - load_dim_innchangelog.0 -  at java.lang.Thread.run(Thread.java:722) 
2016/09/18 08:00:56 - load_dim_innchangelog.0 - Caused by: java.sql.SQLException: Invalid state, the Connection object is closed. 
2016/09/18 08:00:56 - load_dim_innchangelog.0 -  at net.sourceforge.jtds.jdbc.ConnectionJDBC2.checkOpen(ConnectionJDBC2.java:1699) 
2016/09/18 08:00:56 - load_dim_innchangelog.0 -  at net.sourceforge.jtds.jdbc.ConnectionJDBC2.rollback(ConnectionJDBC2.java:2100) 
2016/09/18 08:00:56 - load_dim_innchangelog.0 -  at org.pentaho.di.core.database.Database.rollback(Database.java:858) 
2016/09/18 08:00:56 - load_dim_innchangelog.0 -  ... 5 more 
2016/09/18 08:00:56 - load_dim_innchangelog.0 - ERROR (version 5.4.0.1-130, build 1 from 2015-06-14_12-34-55 by buildguy) : Unexpected batch update error committing the database connection. 
2016/09/18 08:00:56 - load_dim_innchangelog.0 - ERROR (version 5.4.0.1-130, build 1 from 2015-06-14_12-34-55 by buildguy) : org.pentaho.di.core.exception.KettleDatabaseBatchException: 
2016/09/18 08:00:56 - load_dim_innchangelog.0 - Error updating batch 
2016/09/18 08:00:56 - load_dim_innchangelog.0 - Invalid state, the Connection object is closed. 
2016/09/18 08:00:56 - load_dim_innchangelog.0 - 
2016/09/18 08:00:56 - load_dim_innchangelog.0 -  at org.pentaho.di.core.database.Database.createKettleDatabaseBatchException(Database.java:1386) 
2016/09/18 08:00:56 - load_dim_innchangelog.0 -  at org.pentaho.di.core.database.Database.emptyAndCommit(Database.java:1378) 
2016/09/18 08:00:56 - load_dim_innchangelog.0 -  at org.pentaho.di.trans.steps.tableoutput.TableOutput.dispose(TableOutput.java:575) 
2016/09/18 08:00:56 - load_dim_innchangelog.0 -  at org.pentaho.di.trans.step.RunThread.run(RunThread.java:96) 
2016/09/18 08:00:56 - load_dim_innchangelog.0 -  at java.lang.Thread.run(Thread.java:722) 
2016/09/18 08:00:56 - load_dim_innchangelog.0 - Caused by: java.sql.SQLException: Invalid state, the Connection object is closed. 
2016/09/18 08:00:56 - load_dim_innchangelog.0 -  at net.sourceforge.jtds.jdbc.TdsCore.checkOpen(TdsCore.java:452) 
2016/09/18 08:00:56 - load_dim_innchangelog.0 -  at net.sourceforge.jtds.jdbc.TdsCore.clearResponseQueue(TdsCore.java:727) 
2016/09/18 08:00:56 - load_dim_innchangelog.0 -  at net.sourceforge.jtds.jdbc.JtdsStatement.initialize(JtdsStatement.java:645) 
2016/09/18 08:00:56 - load_dim_innchangelog.0 -  at net.sourceforge.jtds.jdbc.JtdsStatement.executeBatch(JtdsStatement.java:908) 
2016/09/18 08:00:56 - load_dim_innchangelog.0 -  at org.pentaho.di.core.database.Database.emptyAndCommit(Database.java:1362) 
2016/09/18 08:00:56 - load_dim_innchangelog.0 -  ... 3 more 
2016/09/18 08:00:56 - tf_dim_innchangelog - ERROR (version 5.4.0.1-130, build 1 from 2015-06-14_12-34-55 by buildguy) : 错误被检测到! 
2016/09/18 08:00:56 - load_dim_innchangelog.0 - ERROR (version 5.4.0.1-130, build 1 from 2015-06-14_12-34-55 by buildguy) : Unexpected error rolling back the database connection. 
2016/09/18 08:00:56 - load_dim_innchangelog.0 - ERROR (version 5.4.0.1-130, build 1 from 2015-06-14_12-34-55 by buildguy) : org.pentaho.di.core.exception.KettleDatabaseException: 
2016/09/18 08:00:56 - load_dim_innchangelog.0 - Error performing rollback on connection 
2016/09/18 08:00:56 - load_dim_innchangelog.0 - Invalid state, the Connection object is closed. 
2016/09/18 08:00:56 - load_dim_innchangelog.0 - 
2016/09/18 08:00:56 - load_dim_innchangelog.0 -  at org.pentaho.di.core.database.Database.rollback(Database.java:867) 
2016/09/18 08:00:56 - load_dim_innchangelog.0 -  at org.pentaho.di.core.database.Database.rollback(Database.java:845) 
2016/09/18 08:00:56 - load_dim_innchangelog.0 -  at org.pentaho.di.trans.steps.tableoutput.TableOutput.dispose(TableOutput.java:610) 
2016/09/18 08:00:56 - load_dim_innchangelog.0 -  at org.pentaho.di.trans.step.RunThread.run(RunThread.java:96) 
2016/09/18 08:00:56 - load_dim_innchangelog.0 -  at java.lang.Thread.run(Thread.java:722) 
2016/09/18 08:00:56 - load_dim_innchangelog.0 - Caused by: java.sql.SQLException: Invalid state, the Connection object is closed. 
2016/09/18 08:00:56 - load_dim_innchangelog.0 -  at net.sourceforge.jtds.jdbc.ConnectionJDBC2.checkOpen(ConnectionJDBC2.java:1699) 
2016/09/18 08:00:56 - load_dim_innchangelog.0 -  at net.sourceforge.jtds.jdbc.ConnectionJDBC2.rollback(ConnectionJDBC2.java:2100) 
2016/09/18 08:00:56 - load_dim_innchangelog.0 -  at org.pentaho.di.core.database.Database.rollback(Database.java:858) 
2016/09/18 08:00:56 - load_dim_innchangelog.0 -  ... 4 more 
2016/09/18 08:00:56 - load_dim_innchangelog.0 - 完成处理 (I=0, O=15000, R=18000, W=15000, U=0, E=1 
2016/09/18 08:00:56 - Logging - New database connection defined 
2016/09/18 08:00:56 - Logging - Attempting to find connection in Named Datasources 
2016/09/18 08:00:56 - Logging - Unable to find datasource in Named Datasources. Finally will try to attempt connecting using class 
2016/09/18 08:00:56 - Logging - Connected to database. 
2016/09/18 08:00:56 - Logging - Auto commit off

来源

2016-09-18 Janus

请检查您的数据库连接。您的数据库连接极有可能非常低。尝试降低输出的提交大小并重新运行ktr。 – Rishu

这是一个错误MSSQL，不是一个真正的水壶错误。不知道你的环境很难确定，但如果我不得不猜测我认为你的MSSQL配置可能关闭。也许使用批次花费的时间太长了，连接本身就会超时？检查保持活着的设置？我敢肯定，你正在推动一些接近门槛的东西，它正在死亡。

祝你好运！

来源

2016-09-22 16:02:37 Codex

感谢Codex。有关如何找出根路线的更多建议？谢谢.... – Janus

当然，我会在水壶和后端看你的连接池。如果您想获得更多帮助，请发布更多信息。 – Codex

这里实际的错误是：

"Unexpected batch update error committing the database connection."

从其中一个值（例如，试图插入过大的一个数字一个数字字段）不正确的数据格式，这可能结果，...但也可以发生，我可以找到没有明显的理由。

如果你只是想避免错误，请尝试禁用对表输出的步骤“进行插入使用批处理更新”复选框，如步骤可能开始处理相同的数据非常清楚没有它。注意：这将是一个性能权衡，所以谨慎操作:)

来源

2017-01-30 00:52:51 Megadest

欢迎来到堆栈溢出！我建议你[参观]（http://stackoverflow.com/tour）。 –

谢谢@StephenRauch。我曾经是一位匿名用户，刚刚决定加入......任何具体的你想提醒我，因为我不认为我违反了规则或类似的东西？... – Megadest

奇怪的错误由电热水壶

回答

相关问题