org.pentaho.di.core.exception.KettleStepException

2016/02/01 14:07:56 - Non PK Columns.0 - Return value KEY_SEQ can't be found in the input row. 2016/02/01 14:07:56 - Non PK Columns.0 -

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web77

  • 2016/02/01 14:07:56 - PK Columns.0 - Return value KEY_SEQ can't be found in the input row. 2016/02/01 14:07:56 - PK Columns.0 -
  • via Pentaho BI Platform Tracking by Jeff Sturm, 7 months ago
    2016/11/02 15:54:29 - Merge Join.0 - The source step to read from [EnglishSort] can't be executed in multiple (2) copies. Insert a Dummy step to resolve this situation. 2016/11/02 15:54:29 - Merge Join.0 -
  • 2016/04/20 21:01:29 - Insert / Update.0 - Error in step, asking everyone to stop because of: 2016/04/20 21:01:29 - Insert / Update.0 - 2016/04/20 21:01:29 - Insert / Update.0 - offending row : [Folio_Number String(17)], [#Beds Integer(15
  • Stack trace

    • org.pentaho.di.core.exception.KettleStepException: 2016/02/01 14:07:56 - Non PK Columns.0 - Return value KEY_SEQ can't be found in the input row. 2016/02/01 14:07:56 - Non PK Columns.0 - at org.pentaho.di.trans.steps.streamlookup.StreamLookupMeta.getFields(StreamLookupMeta.java:184) at org.pentaho.di.trans.TransMeta.getThisStepFields(TransMeta.java:2042) at org.pentaho.di.trans.TransMeta.getStepFields(TransMeta.java:1871) at org.pentaho.di.trans.TransMeta.getStepFields(TransMeta.java:1834) at org.pentaho.di.trans.TransMeta.getStepFields(TransMeta.java:1834) at org.pentaho.di.trans.TransMeta.getPrevStepFields(TransMeta.java:1940) at org.pentaho.di.trans.TransMeta.getPrevStepFields(TransMeta.java:1905) at org.pentaho.di.trans.steps.groupby.GroupBy.processRow(GroupBy.java:106) at org.pentaho.di.trans.step.RunThread.run(RunThread.java:62) at java.lang.Thread.run(Thread.java:745)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.