tNetezzaInput to tNetezzaOutput Err on commit size = input or 0 input

One Star

tNetezzaInput to tNetezzaOutput Err on commit size = input or 0 input

Environment: v4.1.2 TIS RedHat 64 with nzJDBC.jar (also tried nzJDBC3.jar)
I believe this is a Talend bug regarding the tNetezzaInput/Output components. The tOracleInput and tOracleOutput components work just fine with the same two scenarios I've described below:
First, I'm getting the error below when I have a simple input to output data flow and the commit size equals the total number of rows in the input source:
Exception in component tNetezzaOutput_1
org.netezza.error.NzSQLException: ERROR: Transaction rolled back by client
at org.netezza.internal.QueryExecutor.getNextResult(QueryExecutor.java:276)
at org.netezza.internal.QueryExecutor.execute(QueryExecutor.java:73)
at org.netezza.sql.NzConnection.execute(NzConnection.java:2620)
at org.netezza.sql.NzStatement._execute(NzStatement.java:848)
at org.netezza.sql.NzStatement._executeUpdate(NzStatement.java:859)
at org.netezza.sql.NzPreparedStatament.executeBatch(NzPreparedStatament.java:1017)
at core.copy_of_jb_datedim_loadcore_0_1.Copy_of_JB_DateDim_LoadCore.tNetezzaInput_1Process(Copy_of_JB_DateDim_LoadCore.java:4153)
at core.copy_of_jb_datedim_loadcore_0_1.Copy_of_JB_DateDim_LoadCore.tNetezzaRow_7Process(Copy_of_JB_DateDim_LoadCore.java:1056)
at core.copy_of_jb_datedim_loadcore_0_1.Copy_of_JB_DateDim_LoadCore.tNetezzaConnection_4Process(Copy_of_JB_DateDim_LoadCore.java:953)
at core.copy_of_jb_datedim_loadcore_0_1.Copy_of_JB_DateDim_LoadCore.tLibraryLoad_1Process(Copy_of_JB_DateDim_LoadCore.java:840)
at core.copy_of_jb_datedim_loadcore_0_1.Copy_of_JB_DateDim_LoadCore.runJobInTOS(Copy_of_JB_DateDim_LoadCore.java:7059)
at core.copy_of_jb_datedim_loadcore_0_1.Copy_of_JB_DateDim_LoadCore.main(Copy_of_JB_DateDim_LoadCore.java:6826)
Job Copy_of_JB_DateDim_LoadCore ended at 17:54 24/03/2011.
------------------------------------------------------------------------------------
Second, I'm getting the error below when my input source has zero rows:
------------------------------------------------------------------------------------
Exception in component tNetezzaOutput_1
org.netezza.error.NzSQLException: failed to create external table for bulk load
at org.netezza.sql.NzPreparedStatament.executeBatch(NzPreparedStatament.java:1006)
at core.copy_of_jb_datedim_loadcore_0_1.Copy_of_JB_DateDim_LoadCore.tNetezzaInput_1Process(Copy_of_JB_DateDim_LoadCore.java:4153)
at core.copy_of_jb_datedim_loadcore_0_1.Copy_of_JB_DateDim_LoadCore.tNetezzaRow_7Process(Copy_of_JB_DateDim_LoadCore.java:1056)
at core.copy_of_jb_datedim_loadcore_0_1.Copy_of_JB_DateDim_LoadCore.tNetezzaConnection_4Process(Copy_of_JB_DateDim_LoadCore.java:953)
at core.copy_of_jb_datedim_loadcore_0_1.Copy_of_JB_DateDim_LoadCore.tLibraryLoad_1Process(Copy_of_JB_DateDim_LoadCore.java:840)
at core.copy_of_jb_datedim_loadcore_0_1.Copy_of_JB_DateDim_LoadCore.runJobInTOS(Copy_of_JB_DateDim_LoadCore.java:7059)
at core.copy_of_jb_datedim_loadcore_0_1.Copy_of_JB_DateDim_LoadCore.main(Copy_of_JB_DateDim_LoadCore.java:6826)
Job Copy_of_JB_DateDim_LoadCore ended at 17:56 24/03/2011.
===================================================
One Star

Re: tNetezzaInput to tNetezzaOutput Err on commit size = input or 0 input

The error is thrown when the prepared statement is executed with no values. We have opened a support ticket for this.
Employee

Re: tNetezzaInput to tNetezzaOutput Err on commit size = input or 0 input

Hello llinares,
Thank you for opening the bug and for the feedback on the forum.
Best,
Pcoffre.
One Star

Re: tNetezzaInput to tNetezzaOutput Err on commit size = input or 0 input

The bugtracker # is 0020584
Employee

Re: tNetezzaInput to tNetezzaOutput Err on commit size = input or 0 input

Hello llinares,
What was the solution here for your issue?
Can you share please here for other user?
Thanks,
One Star

Re: tNetezzaInput to tNetezzaOutput Err on commit size = input or 0 input

any update?
One Star

Re: tNetezzaInput to tNetezzaOutput Err on commit size = input or 0 input

Guys, any update on this ?