Hitachi Vantara Pentaho Community Forums
Results 1 to 2 of 2

Thread: Database Connection Issues OUTPUT/ WRITING ONLY

  1. #1
    Join Date
    Sep 2014
    Posts
    173

    Default Database Connection Issues OUTPUT/ WRITING ONLY

    Hey there ---

    Weird error that's cropped up lately.

    Our data warehouse is a remote database (different continent) running SQL Server 2012.
    I actually USE the client SQL Sever Management Studio 17 to interact with this database.

    I also use SSIS for some scripts (yes, the horror) -- but anyway their GUI kept tying to use some invalid SQL Sever 2012 data tools by default. I actually had Microsoft SQL Sever 2012 and 2016 and 2017 installed on my computer. I'm not sure if these "applications" are different that the Management studio client, to be honest. I have no actual databases on my computer.

    SOOOO --- I uninstalled Microsoft SQL Sever 2012 on my computer. That's the only real change on my end. The SSIS GUI started working just fine then.

    BUT NOW, ... It seems Pentaho PDI is having issues simply WRITING (edit: Actually reading too, my mistake) to our remote SQL Server 2012 database. This error ONLY OCCURS on table writing tasks to SQL Server. (Actually wait it's reading, too).

    It also ONLY OCCURS SOMETIMES, but across many different scripts. This has never happened before. But it's also not consistent.

    I still have the required .jar file of course. The error looks like this:

    ERROR (version 7.1.0.0-12, build 1 from 2017-05-16 17.18.02 by buildguy) : An error occurred intialising this step:
    2019/03/07 14:24:32 - Table output.2 - Error occurred while trying to connect to the database
    2019/03/07 14:24:32 - Table output.2 -
    2019/03/07 14:24:32 - Table output.2 - Error connecting to database: (using class net.sourceforge.jtds.jdbc.Driver)
    2019/03/07 14:24:32 - Table output.2 - Unable to get information from SQL Server: myfakedatabase.mycompany.com
    2019/03/07 14:24:32 - Table output.2 - ERROR (version 7.1.0.0-12, build 1 from 2017-05-16 17.18.02 by buildguy) : Error initializing step [Table output]
    2019/03/07 14:24:32 - tr_smonkeyFactSurvey - ERROR (version 7.1.0.0-12, build 1 from 2017-05-16 17.18.02 by buildguy) : Step [Table output.2] failed to initialize!
    2019/03/07 14:24:32 - Table output.2 - ERROR (version 7.1.0.0-12, build 1 from 2017-05-16 17.18.02 by buildguy) : Unexpected error rolling back the database connection.
    2019/03/07 14:24:32 - Table output.2 - ERROR (version 7.1.0.0-12, build 1 from 2017-05-16 17.18.02 by buildguy) : org.pentaho.di.core.exception.KettleDatabaseException:
    2019/03/07 14:24:32 - Table output.2 - Unable to get database metadata from this database connection
    2019/03/07 14:24:32 - Table output.2 - at java.lang.Thread.run (null:-1)
    2019/03/07 14:24:32 - Table output.2 - at org.pentaho.di.job.entries.job.JobEntryJobRunner.run (JobEntryJobRunner.java:69)
    2019/03/07 14:24:32 - Table output.2 - at org.pentaho.di.job.Job.execute (Job.java:609)
    2019/03/07 14:24:32 - Table output.2 - at org.pentaho.di.job.Job.execute (Job.java:865)
    2019/03/07 14:24:32 - Table output.2 - at org.pentaho.di.job.Job.execute (Job.java:865)
    2019/03/07 14:24:32 - Table output.2 - at org.pentaho.di.job.Job.execute (Job.java:724)
    2019/03/07 14:24:32 - Table output.2 - at org.pentaho.di.job.entries.trans.JobEntryTrans.execute (JobEntryTrans.java:1152)
    2019/03/07 14:24:32 - Table output.2 - at org.pentaho.di.trans.Trans.execute (Trans.java:627)
    2019/03/07 14:24:32 - Table output.2 - at org.pentaho.di.trans.Trans.prepareExecution (Trans.java:1128)
    2019/03/07 14:24:32 - Table output.2 - at org.pentaho.di.trans.steps.tableoutput.TableOutput.dispose (TableOutput.java:621)
    2019/03/07 14:24:32 - Table output.2 - at org.pentaho.di.core.database.Database.rollback (Database.java:880)
    2019/03/07 14:24:32 - Table output.2 - at org.pentaho.di.core.database.Database.rollback (Database.java:888)
    2019/03/07 14:24:32 - Table output.2 - at org.pentaho.di.core.database.Database.getDatabaseMetaData (Database.java:2917)
    2019/03/07 14:24:32 - Table output.2 -
    2019/03/07 14:24:32 - Table output.2 - at org.pentaho.di.core.database.Database.getDatabaseMetaData(Database.java:2919)
    2019/03/07 14:24:32 - Table output.2 - at org.pentaho.di.core.database.Database.rollback(Database.java:888)
    2019/03/07 14:24:32 - Table output.2 - at org.pentaho.di.core.database.Database.rollback(Database.java:880)
    2019/03/07 14:24:32 - Table output.2 - at org.pentaho.di.trans.steps.tableoutput.TableOutput.dispose(TableOutput.java:621)
    2019/03/07 14:24:32 - Table output.2 - at org.pentaho.di.trans.Trans.prepareExecution(Trans.java:1128)
    2019/03/07 14:24:32 - Table output.2 - at org.pentaho.di.trans.Trans.execute(Trans.java:627)
    2019/03/07 14:24:32 - Table output.2 - at org.pentaho.di.job.entries.trans.JobEntryTrans.execute(JobEntryTrans.java:1152)
    2019/03/07 14:24:32 - Table output.2 - at org.pentaho.di.job.Job.execute(Job.java:724) 2019/03/07 14:24:32 - Table output.2 - at org.pentaho.di.job.Job.execute(Job.java:865)
    The drivers I think I have installed here are sqljdbc4.jar and jtds-1.2.5.jar ---- one of those probably is for SQL Server. I have unrelated Oracle and MySQL drivers as well.

    Again nothing changed on the Pentaho setup side, which makes this odd. I only removed SQL Sever 2012 from MY COMPUTER (and it's SDK tools I think) -- but I still have this for SQL Sever 2017 and client.

    But Pentaho doesn't require SQL Sever -- the client or install or anything in any case, right?

    Perhaps this is database latency in general. Or a changed database setting (though this is unlikely as we currently are backfilling a missing DBA).

    Does any have any idea on how to troubleshoot here?

    I may try running these scripts from a close machine (that's on the same continent) to test for some latency problems but I'm not sure.
    Last edited by cool_runnings; 03-07-2019 at 05:02 PM.

  2. #2
    Join Date
    Sep 2014
    Posts
    173

    Default

    Hmm ... tough one. Seems to be working fine for now but --- it was in-out all last night and all afternoon. Honestly it could be "inter-continental" connection issues which hasn't happened in months. Wish we had better monitoring for network connectivity and stuff like that. Does anyone use monitoring programs for such things?

    Maybe outside the scope of Pentaho PDI but would be interesting. Still .... it's only our data warehouse database and not external sources (various cloud applications) -- that link is separate from the internet at large I suppose.

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 - 2017 Pentaho Corporation. All Rights Reserved.