java.sql.SQLException: No suitable driver at kodo.jdbc.sql.SQLExceptions.getFatalDataStore(SQLExceptions.java:42) at kodo.jdbc.sql.SQLExceptions.getFatalDataStore(SQLExceptions.java:24) at kodo.jdbc.sql.DBDictionaryFactory.getDBDictionary(DBDictionaryFactory.java:61) at kodo.jdbc.conf.JDBCConfigurationImpl.getDBDictionaryInstance(JDBCConfigurationImpl.java:630) at kodo.jdbc.conf.JDBCConfigurationImpl.getConnectionFactory(JDBCConfigurationImpl.java:880) at kodo.jdbc.conf.JDBCConfigurationImpl.getDataSource(JDBCConfigurationImpl.java:970) at kodo.jdbc.conf.JDBCConfigurationImpl.getDataSource2(JDBCConfigurationImpl.java:979)

Oracle Community | 3004 | 1 decade ago
  1. 0

    Kodo 3.1.2 + IBM  DB2 7.2 = No Suitable Driver?

    Oracle Community | 1 decade ago | 3004
    java.sql.SQLException: No suitable driver at kodo.jdbc.sql.SQLExceptions.getFatalDataStore(SQLExceptions.java:42) at kodo.jdbc.sql.SQLExceptions.getFatalDataStore(SQLExceptions.java:24) at kodo.jdbc.sql.DBDictionaryFactory.getDBDictionary(DBDictionaryFactory.java:61) at kodo.jdbc.conf.JDBCConfigurationImpl.getDBDictionaryInstance(JDBCConfigurationImpl.java:630) at kodo.jdbc.conf.JDBCConfigurationImpl.getConnectionFactory(JDBCConfigurationImpl.java:880) at kodo.jdbc.conf.JDBCConfigurationImpl.getDataSource(JDBCConfigurationImpl.java:970) at kodo.jdbc.conf.JDBCConfigurationImpl.getDataSource2(JDBCConfigurationImpl.java:979)
  2. 0

    DB2 Batch Update Problem

    objectmix.com | 1 year ago
    java.sql.SQLException: Database operation failed. Update count for SQL statement was -2. Statement: INSERT INTO DB2ADMIN ANIMAL (JDOCLASS, JDOID, JDOVERSION, NAME0, PRICE) VALUES (?, ?, ?, ?, ?) at kodo.jdbc.sql.SQLExceptions.getFatalDataStore(SQLExceptions.java:42) at kodo.jdbc.sql.SQLExceptions.getFatalDataStore(SQLExceptions.java:24) at kodo.jdbc.runtime.JDBCStoreManager.flush(JDBCStoreManager.java:511) at kodo.runtime.DelegatingStoreManager.flush(DelegatingStoreManager.java:158) at kodo.runtime.PersistenceManagerImpl.flushInternal(PersistenceManagerImpl.ja= va:788) at kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl= ..java:644) at kodo.runtime.LocalManagedRuntime.commit(LocalManagedRuntime.java:69) at kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:416)
  3. 0

    When using DB2 - java.sql.SQLException : No suitable driver

    Oracle Community | 1 decade ago | 3004
    java.sql.SQLException: No suitable driver at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.(SchemaTool.java:78)
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    JDBC-ODBC on Unix (No suitable driver)

    Google Groups | 2 decades ago | DHlud
    java.sql.SQLException: No suitable driver at java.sql.DriverManager.getConnection(Compiled Code)
  6. 0

    jConnect, Sybase SQL Server, Servlets

    Google Groups | 2 decades ago | Manfred Specht
    java.sql.SQLException: No suitable driver at java.sql.DriverManager.getConnection(Compiled Code)

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.sql.SQLException

      No suitable driver at kodo.jdbc.sql.SQLExceptions.getFatalDataStore(SQLExceptions.java:42) at kodo.jdbc.sql.SQLExceptions.getFatalDataStore(SQLExceptions.java:24) at kodo.jdbc.sql.DBDictionaryFactory.getDBDictionary(DBDictionaryFactory.java:61) at kodo.jdbc.conf.JDBCConfigurationImpl.getDBDictionaryInstance(JDBCConfigurationImpl.java:630) at kodo.jdbc.conf.JDBCConfigurationImpl.getConnectionFactory(JDBCConfigurationImpl.java:880) at kodo.jdbc.conf.JDBCConfigurationImpl.getDataSource(JDBCConfigurationImpl.java:970) at kodo.jdbc.conf.JDBCConfigurationImpl.getDataSource2(JDBCConfigurationImpl.java:979)

      at kodo.jdbc.schema.SchemaTool.<init>()
    2. kodo.jdbc.schema
      SchemaTool.<init>
      1. kodo.jdbc.schema.SchemaTool.<init>(SchemaTool.java:78)
      1 frame