Hitachi Vantara Pentaho Community Forums
Results 1 to 4 of 4

Thread: PDI Transform Error: 'jtds000001' could not be found

  1. #1
    Join Date
    Jan 2007
    Posts
    485

    Default PDI Transform Error: 'jtds000001' could not be found

    Hi All,

    I am having trouble with a long running transformation (notice the dates and times in the stack trace provided below..) that extracts data from Sybase, has multiple Database Joins to collect further data (again against Sybase) and a final output to a "SerializedFile' which is latter to be used in other transformations.

    The 'jtds000001' could not be found message is generated after some 15 millon records have been passed through a database join step.

    The transformation includes a 'Database Join' step is within a job, and given we have had to use "minimal" logging, we can't pin-point the records causing this problem.

    The full stack of the error is:

    2008/11/07 11:16:28 - Spoon - Starting job...
    2008/11/07 11:16:28 - subtr_etl_posgah_part1_qs - Dispatching started for transformation [subtr_etl_posgah_part1_qs]
    2008/11/12 08:33:33 - Database join cta_oper_prod 2.0 - ERROR (version 3.0.3, build 569 from 2008/04/25 12:30:04) : Because of an error, this step can't continue:
    2008/11/12 08:33:33 - Database join cta_oper_prod 2.0 - ERROR (version 3.0.3, build 569 from 2008/04/25 12:30:04) : ERROR executing query in part[OQ exec query]
    2008/11/12 08:33:33 - Database join cta_oper_prod 2.0 - ERROR (version 3.0.3, build 569 from 2008/04/25 12:30:04) : The dynamic statement 'jtds000001' could not be found. This may be due to insufficient metadata descriptors. Increase the serverwide 'number of open objects' parameter or the 'procedure cache size' parameter.

    I have no idea as to where to go about increasing the "serverwide" number of open objects parameter" or where to adjust the "procedure cache size".

    We are using PDI 3.0.3; the jdbc for Sybase that comes with PDI; on a Windows 2003 Server.

    Can anyone provide assitance?

    Thanks and regards, DMurray3

  2. #2
    DEinspanjer Guest

    Default

    That message sounds like it comes directly from Sybase. Did you search around for it to see if there are any sybase related tips?

  3. #3
    Join Date
    Nov 1999
    Posts
    9,729

    Default

    These databases validate and parse the SQL against their own catalog tables. This is a costly operation and so they store the results in memory.
    It seems you have insufficient memory on the Sybase server to keep those results in memory for a longer period of time.

  4. #4
    Join Date
    Jan 2007
    Posts
    485

    Default

    Thanks for the quick response. I'll get someone to look at the Sybase Server and/or resort to another alternative. Again many thanks... DMurray3

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.