Batch Mode setting for database writer

oldforum

• July 16, 2007 00:00

• Answered

Follow

Hi,
I am facing an issue while setting the Batch Mode property to 'true' for db output table component in an Clover ETL graph.
The issue is that after setting this property if any error occurs while writing to db , the error is ignored and execution continues.Moreover the error is not even logged in the log files.

• 

  oldforum

  • July 16, 2007 08:23

  0

  Comment actions Permalink

  Hi !
  
  You may combine batch mode with max-errors. Also, if you connect your DBOutputTable to any writer/component, those rows which were rejected by DB are sent to output port 0 - if it is connected. This way, you can capture error rows and process them further.
  
  David
• 

  elouan

  • December 20, 2007 08:49

  0

  Comment actions Permalink

  Hello,
  is there a method to put in a file all the errors from the database with a dboutput ?
• 

  avackova

  • December 20, 2007 09:38

  0

  Comment actions Permalink

  As written above connect writer node to 0 (zero) output port of DBOutputTable and set maxErros = -1
• 

  avackova

  • December 20, 2007 09:42

  0

  Comment actions Permalink

  I'm sorry, I've written wrong answer above: when maxErrors is set -1 errors are completely ignores, even not logged. To send error records to output, maxErrors has to be greater then 0. If you want only to log errors, set maxErrors greater then expected number of errors.
• 

  elouan

  • December 20, 2007 14:43

  0

  Comment actions Permalink

  Thank you for your answer, do you know if one of the new version implement the infinite number of rows ?
  Because I saw that it can't be over 1 000 000 000 ? (it's not a problem for me but maybe for others it will be)
• 

  avackova

  • December 21, 2007 07:52

  0

  Comment actions Permalink

  I don't thing that infinite number of errors could be useful, because, usually, only small per cent or records are wrong and not loaded to database. Another case is when all records are wrong and then, probably, user would like to stop after first error to correct query.

Please sign in to leave a comment.