java.sql.SQLException: [Microsoft][ODBC Driver Manager] Data source name too long

Oracle Community | Amar Regatti | 6 months ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    ODI integration with FOX PRO 9.0. Help needed urgently...

    Oracle Community | 6 months ago | Amar Regatti
    java.sql.SQLException: [Microsoft][ODBC Driver Manager] Data source name too long
  2. 0

    ODI integration with FOX PRO 9.0. Help needed

    Oracle Community | 6 months ago | Amar Regatti
    java.sql.SQLException: [Microsoft][ODBC Driver Manager] Data source name too long
  3. 0

    Connecting to Microsoft Excel using Oracle Data Integrator (Data Integration)

    oracle.com | 8 months ago
    java.sql.SQLException: [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    db:: 4.42::The specified DSN contains an architecture mismatch between the Driver and Application. m3

    hivmr.com | 11 months ago
    java.sql.SQLException: [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application
  6. 0

    Lotus notes and ODI

    Oracle Community | 4 years ago | ms
    java.sql.SQLException: [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application

    10 unregistered visitors
    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

      [Microsoft][ODBC Driver Manager] Data source name too long

      at sun.jdbc.odbc.JdbcOdbc.createSQLException()
    2. sun.jdbc.odbc
      JdbcOdbcDriver.connect
      1. sun.jdbc.odbc.JdbcOdbc.createSQLException(JdbcOdbc.java:6957)
      2. sun.jdbc.odbc.JdbcOdbc.standardError(JdbcOdbc.java:7114)
      3. sun.jdbc.odbc.JdbcOdbc.SQLDriverConnect(JdbcOdbc.java:3073)
      4. sun.jdbc.odbc.JdbcOdbcConnection.initialize(JdbcOdbcConnection.java:323)
      5. sun.jdbc.odbc.JdbcOdbcDriver.connect(JdbcOdbcDriver.java:174)
      5 frames
    3. oracle.odi.jdbc
      LoginTimeoutDatasourceAdapter$ConnectionProcessor.run
      1. oracle.odi.jdbc.datasource.DriverManagerDataSource.getConnectionFromDriver(DriverManagerDataSource.java:410)
      2. oracle.odi.jdbc.datasource.DriverManagerDataSource.getConnectionFromDriver(DriverManagerDataSource.java:386)
      3. oracle.odi.jdbc.datasource.DriverManagerDataSource.getConnectionFromDriver(DriverManagerDataSource.java:353)
      4. oracle.odi.jdbc.datasource.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:332)
      5. oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter$ConnectionProcessor.run(LoginTimeoutDatasourceAdapter.java:217)
      5 frames
    4. Java RT
      Thread.run
      1. java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
      2. java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
      3. java.util.concurrent.FutureTask.run(FutureTask.java:138)
      4. java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
      5. java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      6. java.lang.Thread.run(Thread.java:662)
      6 frames