Sponsored Links
Sponsored Link

sponsored links

Collapse

Announcement

Collapse
No announcement yet.

JDBC broken at v7r3, is there a way out?

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • JDBC broken at v7r3, is there a way out?

    I've got an application that uses Scott Klement's JDBCR4 code along with the SQLite JDBC driver in order to create lightweight SQLite databases which power a fleet of handheld devices. This has been in daily use since v5r3. We attempted a migration to a new Power 9 box running v7r3 last weekend, this JDBC application, along with others, no longer work. The error message indicates that the JDBC drivers have no native OS400 libraries. IBM has been zero help other than to suggest I contact the JDBC driver suppliers in order to find out how to install the drivers on the As400 with OS400 native libraries. Three different JDBC drivers no longer work; MSSQL, jTDS and SQLite.

    Long story short, we aborted the migration and reverted back to a v7r1 box, the customer is not amused now that he owns a $60k paperweight.

    One option is to load the Power 9 with v7r2 that supposedly will allow JDBC to run the way it has been. But, the point of upgrading was not to start by downgrading.

    Very frustrating to say the least. Has anyone here hit this speed bump and found a way out? Ideas welcomed?

  • #2
    I ran into a similar situation when upgrading from 7.1 to 7.3 because the default Java version went from Java 6 to Java 7 and Java 6 was no longer supported on the new release. I was using the Help Systems SEQUEL utility to communicate with a Microsoft SQL Server and using an older version (4 I think) of Microsoft's JDBC driver, which worked with Java 6 but didn't work with the newer Java versions. When I updated the JDBC driver to the latest release (6), everything started working again, although that release had separate drivers for Java 7 and Java 8 that you had to pick depending on which version of Java you were going to run on the system.

    I'm not sure if your JDBC drivers are up to date or not, but if not, it might be worth a try installing the latest version.

    Comment


    • #3
      I think there's a chance a newer Microsoft or jTDS driver might fix this, my more immediate concern is the SQlite driver. I'll poke around there to see if a newer driver might be available which might fix this.

      EDIT: I confirmed the most recent version SQLite JDBC driver does NOT resolve this issue, "no native library found for OS400".

      Comment

      sponsored links

      Collapse

      Working...
      X