Hitachi Vantara Pentaho Community Forums
Results 1 to 3 of 3

Thread: The tablename is not defined - Error

  1. #1
    Join Date
    Apr 2009
    Posts
    12

    Default The tablename is not defined - Error

    I recieve The tablename is not defined error with simple TAB file import transformation. The transformation is feeding the same table in two databases. When I run to one DB works fine, second DB causes issue. I'm able to runtransformation to other tables in 2nd DB.

    Anyone know what this error means? What to look at? Thansk

    2009/06/19 12:53:47 - PROD_LKP_ATTRIBUTES.0 - ERROR (version 3.1.0, build 826 from 2009/04/09 09:51:09) : Because of an error, this step can't continue:
    2009/06/19 12:53:47 - LKP_ATTRIBUTES.0 - Found data row: [ 40003], [001|002|000], [Demographics], [Education], [null], [Some college], [ 02], [ 03], [PROD_SURVEY_RESPONSE], [q23], [q23], [ 03], [Y]
    2009/06/19 12:53:47 - PROD_LKP_ATTRIBUTES.0 - ERROR (version 3.1.0, build 826 from 2009/04/09 09:51:09) : org.pentaho.di.core.exception.KettleStepException:
    2009/06/19 12:53:47 - PROD_LKP_ATTRIBUTES.0 - ERROR (version 3.1.0, build 826 from 2009/04/09 09:51:09) : The tablename is not defined (empty)
    2009/06/19 12:53:47 - PROD_LKP_ATTRIBUTES.0 - ERROR (version 3.1.0, build 826 from 2009/04/09 09:51:09) :
    2009/06/19 12:53:47 - PROD_LKP_ATTRIBUTES.0 - ERROR (version 3.1.0, build 826 from 2009/04/09 09:51:09) : at org.pentaho.di.trans.steps.tableoutput.TableOutput.writeToTable(TableOutput.java:197)
    2009/06/19 12:53:47 - PROD_LKP_ATTRIBUTES.0 - ERROR (version 3.1.0, build 826 from 2009/04/09 09:51:09) : at org.pentaho.di.trans.steps.tableoutput.TableOutput.processRow(TableOutput.java:78)
    2009/06/19 12:53:47 - PROD_LKP_ATTRIBUTES.0 - ERROR (version 3.1.0, build 826 from 2009/04/09 09:51:09) : at org.pentaho.di.trans.step.BaseStep.runStepThread(BaseStep.java:2664)
    2009/06/19 12:53:47 - PROD_LKP_ATTRIBUTES.0 - ERROR (version 3.1.0, build 826 from 2009/04/09 09:51:09) : at org.pentaho.di.trans.steps.tableoutput.TableOutput.run(TableOutput.java:630)

  2. #2
    Join Date
    Dec 2009
    Posts
    1

    Default how did this resolve?

    hey there, did you find a resolution to this problem? i ran into something similar using an ETL tool. i basically just started from scratch using what i believe to be same settings and somehow it magically worked.

  3. #3
    Join Date
    Apr 2008
    Posts
    4,696

    Default

    Some DBs are very sensitive on the case of words...

    iKPI is different from IKPI in some DBs, as such, if you don't have the quote all in DB option turned on, it may not work.

    PostgreSQL is one that I have had experience with this on...

Tags for this Thread

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.