Hitachi Vantara Pentaho Community Forums
Results 1 to 3 of 3

Thread: Force COMMITs on SQL tables?

  1. #1

    Default Force COMMITs on SQL tables?

    Hiya,

    Is there a way I can force an COMMIT on a SQL table? I am trying to do the following:

    1. Obtain data through a series of webservice calls...
    2. Create a record in a log table for an entry (Step: Combination Lookup/Update)
    3. Update my dimension table with the primary key from the previous step (Step: Dimension Lookup/Update)
    4. Write the remaining attributes to record created in step 2 (Step: Update)


    When I hit the last step, I get the following error:

    2009/06/26 18:20:35 - org.pentaho.di.trans.steps.update.Update - ERROR (version 4.0.0-M1, build 1 from 2009-06-24 17.28.38 by kbarlo00) : org.pentaho.di.core.exception.KettleDatabaseException:
    2009/06/26 18:20:35 - org.pentaho.di.trans.steps.update.Update - ERROR (version 4.0.0-M1, build 1 from 2009-06-24 17.28.38 by kbarlo00) : Entry to update with following key could not be found: [1]
    2009/06/26 18:20:35 - org.pentaho.di.trans.steps.update.Update - ERROR (version 4.0.0-M1, build 1 from 2009-06-24 17.28.38 by kbarlo00) :
    2009/06/26 18:20:35 - org.pentaho.di.trans.steps.update.Update - ERROR (version 4.0.0-M1, build 1 from 2009-06-24 17.28.38 by kbarlo00) : at org.pentaho.di.trans.steps.update.Update.lookupValues(Update.java:118)
    2009/06/26 18:20:35 - org.pentaho.di.trans.steps.update.Update - ERROR (version 4.0.0-M1, build 1 from 2009-06-24 17.28.38 by kbarlo00) : at org.pentaho.di.trans.steps.update.Update.processRow(Update.java:291)
    2009/06/26 18:20:35 - org.pentaho.di.trans.steps.update.Update - ERROR (version 4.0.0-M1, build 1 from 2009-06-24 17.28.38 by kbarlo00) : at org.pentaho.di.trans.step.BaseStep.runStepThread(BaseStep.java:2846)
    2009/06/26 18:20:35 - org.pentaho.di.trans.steps.update.Update - ERROR (version 4.0.0-M1, build 1 from 2009-06-24 17.28.38 by kbarlo00) : at org.pentaho.di.trans.steps.update.Update.run(Update.java:514)
    However, after the process crashes, a row with that primary key does exist in my COMBINATION table which leads me to believe that the INSERT just hasn't been commited yet. Is there anyway I can force this?

    Thanks.

    Keith

  2. #2

    Default

    Hi,

    do you switched transformation in a transactionnal mode?
    You have an option available in the transformation settings that allow you to open ONE conenction for each database used within your transformation.


    Rgds

    Samatar
    Samatar

  3. #3

    Default

    Thanks - that seemed to work.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Privacy Policy | Legal Notices | Safe Harbor Privacy Policy

Copyright © 2005 - 2019 Hitachi Vantara Corporation. All Rights Reserved.