Reg: DB2 driver

Hi Experts,
Can anyone please let me know the driver that needs to be used for connecting to DB2 database?
Is it the same as Oracle database.
Thanks,
Prem

In other EAI tool we used the below driver for connection to DB2 database of AS400
com.ibm.as400.access.AS400JDBCDataSource
Which needs to be downlaoded and need to be deployed like other drivers (SQL,oracle)
HTH
Rajesh
Edited by: Rajesh on Jul 15, 2009 1:06 PM

Similar Messages

  • EXCEPTION_ACCESS_VIOLATION when loading DB2 driver

    Hi,
    I'm currently developing an executable jar application. I've got a problem in connecting to the DB2 server after packaging the application into a jar file. Below is the error that I encountered:
    # An unexpected error has been detected by HotSpot Virtual Machine:
    #  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d6c9a1f, pid=2296, tid=2260
    # Java VM: Java HotSpot(TM) Client VM (1.5.0_05-b05 mixed mode, sharing)
    # Problematic frame:
    # V  [jvm.dll+0x89a1f]
    # An error report file with more information is saved as hs_err_pid2296.log
    # If you would like to submit a bug report, please visit:
    #   http://java.sun.com/webapps/bugreport/crash.jsp
    #And here's the detailed log:
    ---------------  T H R E A D  ---------------
    Current thread (0x02cc7e00):  JavaThread "AWT-EventQueue-0" [_thread_in_vm, id=2260]
    siginfo: ExceptionCode=0xc0000005, reading address 0x00000000
    Registers:
    EAX=0x00000000, EBX=0x00000000, ECX=0x02d12fe8, EDX=0x00ac2d60
    ESP=0x0742f090, EBP=0x0742f0c0, ESI=0x02cc7e00, EDI=0x00ac2d58
    EIP=0x6d6c9a1f, EFLAGS=0x00010206
    Top of Stack: (sp=0x0742f090)
    0x0742f090:   02cc7ebc 02cc7ebc 26b15cf0 02cc7ebc
    0x0742f0a0:   02cc7ebc 6d68086a 6d64aa71 02cc7e00
    0x0742f0b0:   0742f0e0 6d6c62ad 02cc7e00 00ac2d58
    0x0742f0c0:   0742f0e0 1000a647 02cc7ebc 00000000
    0x0742f0d0:   100130c8 00ac2d5c 02cc7e00 26b15cf0
    0x0742f0e0:   0742f100 100039b0 02cc7ebc 00000000
    0x0742f0f0:   00000000 00000000 02cc7e00 26b15cf0
    0x0742f100:   0742f130 00ad826f 02cc7ebc 0742f144
    Instructions: (pc=0x6d6c9a1f)
    0x6d6c9a0f:   a9 00 00 00 39 5d 14 0f 84 a0 00 00 00 8b 45 0c
    0x6d6c9a1f:   ff 30 e8 2a 97 ff ff 59 50 56 8d 4d 08 e8 da c3
    Stack: [0x073f0000,0x07430000),  sp=0x0742f090,  free space=252k
    Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
    V  [jvm.dll+0x89a1f]
    C  [db2jdbc.dll+0xa647]
    C  [db2jdbc.dll+0x39b0]
    j  COM.ibm.db2.jdbc.app.DB2Driver.SQLAllocEnv([I)I+0
    j  COM.ibm.db2.jdbc.app.DB2Driver.<init>()V+628
    j  COM.ibm.db2.jdbc.app.DB2Driver.<clinit>()V+27
    v  ~StubRoutines::call_stub
    V  [jvm.dll+0x8295c]
    V  [jvm.dll+0xd752e]
    V  [jvm.dll+0x8282d]
    V  [jvm.dll+0x75a9c]
    V  [jvm.dll+0x7499d]
    V  [jvm.dll+0x9ff40]
    V  [jvm.dll+0x99269]
    C  [java.dll+0x13d8]
    j  java.lang.Class.forName0(Ljava/lang/String;ZLjava/lang/ClassLoader;)Ljava/lang/Class;+0
    j  java.lang.Class.forName(Ljava/lang/String;)Ljava/lang/Class;+5
    j  ort.cip.client.DB2Connection.connect_query(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;[Z)Lcom/jrefinery/data/XYDataset;+19
    j  ort.cip.client.ORT_Charting_Main.jButton1_ActionEvents()V+369
    j  ort.cip.client.ORT_Charting_Main.connEtoC2()V+1
    j  ort.cip.client.ORT_Charting_Main.access$5(Lort/cip/client/ORT_Charting_Main;)V+1
    j  ort.cip.client.ORT_Charting_Main$IvjEventHandler.actionPerformed(Ljava/awt/event/ActionEvent;)V+62
    j  javax.swing.AbstractButton.fireActionPerformed(Ljava/awt/event/ActionEvent;)V+84
    j  javax.swing.AbstractButton$Handler.actionPerformed(Ljava/awt/event/ActionEvent;)V+5
    j  javax.swing.DefaultButtonModel.fireActionPerformed(Ljava/awt/event/ActionEvent;)V+35
    j  javax.swing.DefaultButtonModel.setPressed(Z)V+117
    j  javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Ljava/awt/event/MouseEvent;)V+35
    j  java.awt.Component.processMouseEvent(Ljava/awt/event/MouseEvent;)V+64
    j  javax.swing.JComponent.processMouseEvent(Ljava/awt/event/MouseEvent;)V+23
    j  java.awt.Component.processEvent(Ljava/awt/AWTEvent;)V+81
    j  java.awt.Container.processEvent(Ljava/awt/AWTEvent;)V+18
    j  java.awt.Component.dispatchEventImpl(Ljava/awt/AWTEvent;)V+477
    j  java.awt.Container.dispatchEventImpl(Ljava/awt/AWTEvent;)V+42
    j  java.awt.Component.dispatchEvent(Ljava/awt/AWTEvent;)V+2
    j  java.awt.LightweightDispatcher.retargetMouseEvent(Ljava/awt/Component;ILjava/awt/event/MouseEvent;)V+304
    j  java.awt.LightweightDispatcher.processMouseEvent(Ljava/awt/event/MouseEvent;)Z+139
    j  java.awt.LightweightDispatcher.dispatchEvent(Ljava/awt/AWTEvent;)Z+50
    j  java.awt.Container.dispatchEventImpl(Ljava/awt/AWTEvent;)V+12
    j  java.awt.Window.dispatchEventImpl(Ljava/awt/AWTEvent;)V+19
    j  java.awt.Component.dispatchEvent(Ljava/awt/AWTEvent;)V+2
    j  java.awt.EventQueue.dispatchEvent(Ljava/awt/AWTEvent;)V+46
    j  java.awt.EventDispatchThread.pumpOneEventForHierarchy(ILjava/awt/Component;)Z+233
    j  java.awt.EventDispatchThread.pumpEventsForHierarchy(ILjava/awt/Conditional;Ljava/awt/Component;)V+26
    j  java.awt.EventDispatchThread.pumpEvents(ILjava/awt/Conditional;)V+4
    j  java.awt.EventDispatchThread.pumpEvents(Ljava/awt/Conditional;)V+3
    j  java.awt.EventDispatchThread.run()V+9
    v  ~StubRoutines::call_stub
    V  [jvm.dll+0x8295c]
    V  [jvm.dll+0xd752e]
    V  [jvm.dll+0x8282d]
    V  [jvm.dll+0x8258a]
    V  [jvm.dll+0x9d476]
    V  [jvm.dll+0x1042ae]
    V  [jvm.dll+0x10427c]
    C  [MSVCRT.dll+0x2a3b0]
    C  [kernel32.dll+0xb50b]
    Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
    j  COM.ibm.db2.jdbc.app.DB2Driver.SQLAllocEnv([I)I+0
    j  COM.ibm.db2.jdbc.app.DB2Driver.<init>()V+628
    j  COM.ibm.db2.jdbc.app.DB2Driver.<clinit>()V+27
    v  ~StubRoutines::call_stub
    j  java.lang.Class.forName0(Ljava/lang/String;ZLjava/lang/ClassLoader;)Ljava/lang/Class;+0
    j  java.lang.Class.forName(Ljava/lang/String;)Ljava/lang/Class;+5
    j  ort.cip.client.DB2Connection.connect_query(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;[Z)Lcom/jrefinery/data/XYDataset;+19
    j  ort.cip.client.ORT_Charting_Main.jButton1_ActionEvents()V+369
    j  ort.cip.client.ORT_Charting_Main.connEtoC2()V+1
    j  ort.cip.client.ORT_Charting_Main.access$5(Lort/cip/client/ORT_Charting_Main;)V+1
    j  ort.cip.client.ORT_Charting_Main$IvjEventHandler.actionPerformed(Ljava/awt/event/ActionEvent;)V+62
    j  javax.swing.AbstractButton.fireActionPerformed(Ljava/awt/event/ActionEvent;)V+84
    j  javax.swing.AbstractButton$Handler.actionPerformed(Ljava/awt/event/ActionEvent;)V+5
    j  javax.swing.DefaultButtonModel.fireActionPerformed(Ljava/awt/event/ActionEvent;)V+35
    j  javax.swing.DefaultButtonModel.setPressed(Z)V+117
    j  javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Ljava/awt/event/MouseEvent;)V+35
    j  java.awt.Component.processMouseEvent(Ljava/awt/event/MouseEvent;)V+64
    j  javax.swing.JComponent.processMouseEvent(Ljava/awt/event/MouseEvent;)V+23
    j  java.awt.Component.processEvent(Ljava/awt/AWTEvent;)V+81
    j  java.awt.Container.processEvent(Ljava/awt/AWTEvent;)V+18
    j  java.awt.Component.dispatchEventImpl(Ljava/awt/AWTEvent;)V+477
    j  java.awt.Container.dispatchEventImpl(Ljava/awt/AWTEvent;)V+42
    j  java.awt.Component.dispatchEvent(Ljava/awt/AWTEvent;)V+2
    j  java.awt.LightweightDispatcher.retargetMouseEvent(Ljava/awt/Component;ILjava/awt/event/MouseEvent;)V+304
    j  java.awt.LightweightDispatcher.processMouseEvent(Ljava/awt/event/MouseEvent;)Z+139
    j  java.awt.LightweightDispatcher.dispatchEvent(Ljava/awt/AWTEvent;)Z+50
    j  java.awt.Container.dispatchEventImpl(Ljava/awt/AWTEvent;)V+12
    j  java.awt.Window.dispatchEventImpl(Ljava/awt/AWTEvent;)V+19
    j  java.awt.Component.dispatchEvent(Ljava/awt/AWTEvent;)V+2
    j  java.awt.EventQueue.dispatchEvent(Ljava/awt/AWTEvent;)V+46
    j  java.awt.EventDispatchThread.pumpOneEventForHierarchy(ILjava/awt/Component;)Z+233
    j  java.awt.EventDispatchThread.pumpEventsForHierarchy(ILjava/awt/Conditional;Ljava/awt/Component;)V+26
    j  java.awt.EventDispatchThread.pumpEvents(ILjava/awt/Conditional;)V+4
    j  java.awt.EventDispatchThread.pumpEvents(Ljava/awt/Conditional;)V+3
    j  java.awt.EventDispatchThread.run()V+9
    v  ~StubRoutines::call_stub
    ---------------  P R O C E S S  ---------------
    Java Threads: ( => current thread )
      0x000352e8 JavaThread "DestroyJavaVM" [_thread_blocked, id=832]
    =>0x02cc7e00 JavaThread "AWT-EventQueue-0" [_thread_in_vm, id=2260]
      0x02cc4618 JavaThread "AWT-Shutdown" [_thread_blocked, id=848]
      0x00aa1a38 JavaThread "Java2D Disposer" daemon [_thread_blocked, id=3720]
      0x02cac008 JavaThread "AWT-Windows" daemon [_thread_in_native, id=3756]
      0x00a699f0 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=4020]
      0x00a685c8 JavaThread "CompilerThread0" daemon [_thread_blocked, id=3556]
      0x00a67860 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=880]
      0x00a62ad0 JavaThread "Finalizer" daemon [_thread_blocked, id=2364]
      0x00a615f0 JavaThread "Reference Handler" daemon [_thread_blocked, id=2796]
    Other Threads:
      0x00a5ed50 VMThread [id=2656]
      0x00a677a0 WatcherThread [id=3492]
    VM state:not at safepoint (normal execution)
    VM Mutex/Monitor currently owned by a thread: None
    Heap
    def new generation   total 576K, used 292K [0x22a80000, 0x22b20000, 0x22f60000)
      eden space 512K,  44% used [0x22a80000, 0x22ab9540, 0x22b00000)
      from space 64K,  99% used [0x22b00000, 0x22b0fd78, 0x22b10000)
      to   space 64K,   0% used [0x22b10000, 0x22b10000, 0x22b20000)
    tenured generation   total 1408K, used 1304K [0x22f60000, 0x230c0000, 0x26a80000)
       the space 1408K,  92% used [0x22f60000, 0x230a6278, 0x230a6400, 0x230c0000)
    compacting perm gen  total 8192K, used 640K [0x26a80000, 0x27280000, 0x2aa80000)
       the space 8192K,   7% used [0x26a80000, 0x26b20080, 0x26b20200, 0x27280000)
        ro space 8192K,  62% used [0x2aa80000, 0x2af8a3a0, 0x2af8a400, 0x2b280000)
        rw space 12288K,  46% used [0x2b280000, 0x2b8103d8, 0x2b810400, 0x2be80000)
    Dynamic libraries:
    0x00400000 - 0x0040c000      C:\WINDOWS\system32\java.exe
    0x7c900000 - 0x7c9b0000      C:\WINDOWS\system32\ntdll.dll
    0x7c800000 - 0x7c8f4000      C:\WINDOWS\system32\kernel32.dll
    0x77dd0000 - 0x77e6b000      C:\WINDOWS\system32\ADVAPI32.dll
    0x77e70000 - 0x77f01000      C:\WINDOWS\system32\RPCRT4.dll
    0x77c10000 - 0x77c68000      C:\WINDOWS\system32\MSVCRT.dll
    0x6d640000 - 0x6d7cc000      C:\Program Files\Java\jre1.5.0_05\bin\client\jvm.dll
    0x77d40000 - 0x77dd0000      C:\WINDOWS\system32\USER32.dll
    0x77f10000 - 0x77f56000      C:\WINDOWS\system32\GDI32.dll
    0x76b40000 - 0x76b6d000      C:\WINDOWS\system32\WINMM.dll
    0x6d280000 - 0x6d288000      C:\Program Files\Java\jre1.5.0_05\bin\hpi.dll
    0x76bf0000 - 0x76bfb000      C:\WINDOWS\system32\PSAPI.DLL
    0x6d610000 - 0x6d61c000      C:\Program Files\Java\jre1.5.0_05\bin\verify.dll
    0x6d300000 - 0x6d31d000      C:\Program Files\Java\jre1.5.0_05\bin\java.dll
    0x6d630000 - 0x6d63f000      C:\Program Files\Java\jre1.5.0_05\bin\zip.dll
    0x6d000000 - 0x6d167000      C:\Program Files\Java\jre1.5.0_05\bin\awt.dll
    0x73000000 - 0x73026000      C:\WINDOWS\system32\WINSPOOL.DRV
    0x76390000 - 0x763ad000      C:\WINDOWS\system32\IMM32.dll
    0x774e0000 - 0x7761d000      C:\WINDOWS\system32\ole32.dll
    0x5ad70000 - 0x5ada8000      C:\WINDOWS\system32\UxTheme.dll
    0x73760000 - 0x737a9000      C:\WINDOWS\system32\ddraw.dll
    0x73bc0000 - 0x73bc6000      C:\WINDOWS\system32\DCIMAN32.dll
    0x73940000 - 0x73a10000      C:\WINDOWS\system32\D3DIM700.DLL
    0x63000000 - 0x63014000      C:\WINDOWS\system32\SynTPFcs.dll
    0x77c00000 - 0x77c08000      C:\WINDOWS\system32\VERSION.dll
    0x7c9c0000 - 0x7d1d5000      C:\WINDOWS\system32\shell32.dll
    0x77f60000 - 0x77fd6000      C:\WINDOWS\system32\SHLWAPI.dll
    0x773d0000 - 0x774d2000      C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2180_x-ww_a84f1ff9\comctl32.dll
    0x5d090000 - 0x5d127000      C:\WINDOWS\system32\comctl32.dll
    0x6d240000 - 0x6d27d000      C:\Program Files\Java\jre1.5.0_05\bin\fontmanager.dll
    0x6d4c0000 - 0x6d4d3000      C:\Program Files\Java\jre1.5.0_05\bin\net.dll
    0x71ab0000 - 0x71ac7000      C:\WINDOWS\system32\WS2_32.dll
    0x71aa0000 - 0x71aa8000      C:\WINDOWS\system32\WS2HELP.dll
    0x6d4e0000 - 0x6d4e9000      C:\Program Files\Java\jre1.5.0_05\bin\nio.dll
    0x10000000 - 0x10016000      C:\Program Files\SQLLIB\bin\db2jdbc.dll
    0x6c000000 - 0x6c236000      C:\PROGRA~1\SQLLIB\BIN\DB2CLI.dll
    0x6c770000 - 0x6ca25000      C:\PROGRA~1\SQLLIB\BIN\DB2SYS.dll
    0x6e260000 - 0x6e26b000      C:\PROGRA~1\SQLLIB\BIN\DB2WINT.dll
    0x07430000 - 0x07445000      C:\PROGRA~1\SQLLIB\BIN\DB2SYSP.dll
    0x6c240000 - 0x6c4e1000      C:\PROGRA~1\SQLLIB\BIN\DB2APP.dll
    0x6c620000 - 0x6c738000      C:\PROGRA~1\SQLLIB\BIN\DB2UTIL.dll
    0x6c4f0000 - 0x6c529000      C:\PROGRA~1\SQLLIB\BIN\DB2ABIND.dll
    0x07450000 - 0x07580000      C:\PROGRA~1\SQLLIB\BIN\db2osse.dll
    0x77120000 - 0x771ac000      C:\WINDOWS\system32\OLEAUT32.dll
    0x5b860000 - 0x5b8b4000      C:\WINDOWS\system32\NETAPI32.dll
    0x07580000 - 0x0758c000      C:\PROGRA~1\SQLLIB\BIN\db2locale.dll
    0x07590000 - 0x075c8000      C:\PROGRA~1\SQLLIB\BIN\db2trcapi.dll
    VM Arguments:
    java_command: Charting.jar
    Environment Variables:
    CLASSPATH=.;C:\PROGRA~1\SQLLIB\java\db2java.zip;C:\PROGRA~1\SQLLIB\java\db2jcc.jar;C:\PROGRA~1\SQLLIB\java\sqlj.zip;C:\PROGRA~1\SQLLIB\bin;C:\PROGRA~1\SQLLIB\java\common.jar
    PATH=C:\PROGRAM FILES\THINKPAD\UTILITIES;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI Control Panel;C:\WINDOWS\Downloaded Program Files;C:\IBMTOOLS\Python22;C:\Program Files\PC-Doctor for Windows\services;C:\Program Files\IBM\Trace Facility;C:\Program Files\Personal Communications;C:\IMNnq_NT;C:\PROGRA~1\Tcl\bin;C:\PROGRA~1\SQLLIB\BIN;C:\PROGRA~1\SQLLIB\FUNCTION;C:\j2sdk1.4.2_10\bin;C:\Program Files\MySQL\MySQL Server 5.0\bin;C:\CMVC\exe;C:\CMVC\exe\bin;C:\CMVC\bin
    USERNAME=nugraha
    OS=Windows_NT
    PROCESSOR_IDENTIFIER=x86 Family 6 Model 13 Stepping 6, GenuineIntel
    ---------------  S Y S T E M  ---------------
    OS: Windows XP Build 2600 Service Pack 2
    CPU:total 1 family 6, cmov, cx8, fxsr, mmx, sse, sse2
    Memory: 4k page, physical 261040k(31956k free), swap 639216k(137944k free)
    vm_info: Java HotSpot(TM) Client VM (1.5.0_05-b05) for windows-x86, built on Aug 26 2005 15:36:02 by "java_re" with MS VC++ 6.0I found out that this error came out when the following part of the code was executed (see the one in bold):
    public static com.jrefinery.data.XYDataset connect_query(
        java.lang.String drive_SN,
        java.lang.String start_Date,
        java.lang.String end_Date,
        boolean[] checkBox_group) {
        TimeSeriesCollection collection = new TimeSeriesCollection();
        BasicTimeSeries[] param_value;
        try {
            // load the DB2 Driver
    Class.forName("COM.ibm.db2.jdbc.app.DB2Driver");
            // establish a connection to DB2
               Connection db2Conn = DriverManager.getConnection("jdbc:db2:FOXDBS_S","myID","mypass");    
            // use a statement to gather data from the database
            Statement st = db2Conn.createStatement();
            String myQuery = info_query;
            // execute the query
            ResultSet resultSet = st.executeQuery(myQuery);
            // clean up resources
            resultSet.close();
            st.close();
            db2Conn.close();
        } catch (ClassNotFoundException cnfe) {
            cnfe.printStackTrace();
        } catch (SQLException sqle) {
            sqle.printStackTrace();
        XYDataset data = collection;
        return data;
    }This code actually worked fine when I ran it from VisualAge for Java environment.
    I'm currently using J2SDK version 1.4.2_10 and J2RE version 1.4.2_10.
    Appreciate any help that you all can suggest. I've been looking for this error on the web. Seems like this has been a known and common problem but I couldn't find the working answer so far. Thank you in advance for any help.
    Chris

    Hi Russel,
    Thanks for the reply. I've executed the jar file using the -Xcheck:jni as follows:
    java -jar -Xcheck:jni Charting.jarand when I executed the function here's what appeared on the screen:
    FATAL ERROR in native method: JNI call made with exception pending
            at COM.ibm.db2.jdbc.app.DB2Driver.SQLAllocEnv(Native Method)
            at COM.ibm.db2.jdbc.app.DB2Driver.<init>(Unknown Source)
            at COM.ibm.db2.jdbc.app.DB2Driver.<clinit>(Unknown Source)
            at java.lang.Class.forName0(Native Method)
            at java.lang.Class.forName(Unknown Source)
            at ort.cip.client.DB2Connection.connect_query(DB2Connection.java:45)
            at ort.cip.client.ORT_Charting_Main.jButton1_ActionEvents(ORT_Charting_M
    ain.java:3159)
            at ort.cip.client.ORT_Charting_Main.connEtoC2(ORT_Charting_Main.java:244
            at ort.cip.client.ORT_Charting_Main.access$5(ORT_Charting_Main.java:240)
            at ort.cip.client.ORT_Charting_Main$IvjEventHandler.actionPerformed(ORT_
    Charting_Main.java:187)
            at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
            at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
            at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
            at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
            at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Sour
    ce)
            at java.awt.Component.processMouseEvent(Unknown Source)
            at javax.swing.JComponent.processMouseEvent(Unknown Source)
            at java.awt.Component.processEvent(Unknown Source)
            at java.awt.Container.processEvent(Unknown Source)
            at java.awt.Component.dispatchEventImpl(Unknown Source)
            at java.awt.Container.dispatchEventImpl(Unknown Source)
            at java.awt.Component.dispatchEvent(Unknown Source)
            at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
            at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
            at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
            at java.awt.Container.dispatchEventImpl(Unknown Source)
            at java.awt.Window.dispatchEventImpl(Unknown Source)
            at java.awt.Component.dispatchEvent(Unknown Source)
            at java.awt.EventQueue.dispatchEvent(Unknown Source)
            at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
            at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
            at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
            at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
            at java.awt.EventDispatchThread.run(Unknown Source)I recognized that the error appeared during the execution of function "forName(driver)", which is exactly what I predicted before. Strange that this function worked well when executed from the development software (before packaging it into jar file). Is there a difference in the way the program works as executable jar file and as the file in the development sofware?
    And regarding the JDBC driver, I did try another driver, which was the JDBC type 2 and 4 driver. But when I ran the application, there's an error saying that the DB2 server does not support type 2 or 4 JDBC driver. Seems like I have no other choice but to use this driver.
    Do you have any suggestion on how to make the driver work as an executable Jar file? Meanwhile, I'll try to report the bug for this driver. Thanks....

  • DB2 Driver deployment

    Hi Group,
    i want to call a db2 database from an inbound proxy.
    For that i've installed on the XI computer a IBM db2 client. Testing connection from client side succeeds.
    To make the db2 driver also usable for jdbc adapter, i've
    deployed it with "aii_af_jmsproviderlib.sda" file corresponding to the sap documentation "How To Install and Configure External Drivers for JDBC & JMS Adapters".
    To use the db2 connection with my proxy, i used
    the tool "Visual Administrator" and added in the section "Services->JDBC Connectors"  a new driver DB2 and added a db2java.zip from my local computer.
    Additional, i've created a new data source that based on my DB2 service, but i can't start it. A very big stack trace of a RMI Exception appears. (I can post it too if needed)
    When i test my db2 connection with a jdbc Adapter, following error message appears in the adapter monitoring:
    Receiver Adapter v0908 for Party '', Service 'J2E_XI3':
    Configured at 13:21:57 2005-05-30
    Processing Error: Accessing database connection 'jdbc:db2://<IP-Address>:<Port>/<DB_Name>' failed: java.sql.SQLException: No suitable driver
    Addtional information: JDBC driver 'COM.ibm.db2.jdbc.app.DB2Driver' loaded successfully, additional driver information:
    Available JDBC drivers:
    No deployed JDBC Drivers found
    To be sure, that a jdbc call works with the installed db2 client, i've created a simple test class, that does not run on the J2EE engine. The db2 call worked fine.
    For any help or hint, i would be much obliged.
    Greetings,
    Sigi

    Hi Sigi,
    This error is encountered when you have given the wrong connection parameters in your jdbc communication channel.
    Check whether the JDBC Driver and the Connection parameters are correct.Once that is correct, your problem will be solved.
    Regards
    Sunita

  • Bea type 4 db2 driver-stored procedure error

    Iam creating a connection pool in weblogic 9.2 MP2
    using bea type 4 db2 driver and excuting a stored procedure.Iam getting following error
    I enabled spy
    spy(2008/02/13 09:41:58.050)>> Driver Name = DB2
    spy(2008/02/13 09:41:58.050)>> Driver Version = 3.60.24 (023731.010811.022315)
    spy(2008/02/13 09:41:58.050)>> Database Name = DB2/MVS
    spy(2008/02/13 09:41:58.050)>> Database Version = 8.1.5
    spy(2008/02/13 09:44:11.063)>> java.sql.SQLException: [BEA][DB2 JDBC Driver][DB2]UNACCEPTABLE SQL STATEMENT ErrorCode=-84 SQL
    State=42612
    The code is using
    CALL SP03 (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
    as follows
    String sql = "CALL SP03 (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)";
    myCallableStmt = con.prepareCall(sql);
    is ther are any issues in calling stored procedure with type 4 bea db2 driver.
    connectrion pool details
    jdbc:bea:db2://server:447
    weblogic.jdbc.db2.DB2Driver
    user=user
    LocationName=server
    portNumber=447
    serverName=host
    batchPerformanceWorkaround=true
    The code is working fine with type 2 ibm driver connection pool
    Also Iam trying with ibm type 4 driver
    Iam getting following error in configuration itself
    <Feb 13, 2008 11:18:44 AM EST> <Error> <JDBC> <BEA-001112> <Test "SELECT COUNT(*) FROM
    abc.xy_def" set up for pool "DataSourceIBM" failed with exception: "com.ibm.db2.jcc.a.SqlException: DB2 SQL error: SQLCODE: -725,
    SQLSTATE: 42721, SQLERRMC: CLIENT APPLNAME;server".>
    details
    jdbc:db2://mvsavt1_vipa.corpny.csfb.com:447/server
    com.ibm.db2.jcc.DB2Driver
    user=user
    locationName=server
    portNumber=450
    drivertype=4
    Any configuration required at db2 server

    Ok, Odd. Please email this post (the code below) and the
    output of each to [email protected] and ask them to investigate
    why one driver finds the procedure and the other doesn't.
    This will get back to me officially, and then I will be able
    to enlist all the resources to debug it. Is the stored
    procedure owned by the same schema as your 'user'?
    Mohamed Rabbani P M wrote:
    Joe,
    It is the same code you gave
    BEA Driver Code
    import java.io.*;
    import java.util.*;
    import java.net.*;
    import java.sql.*;
    import weblogic.common.*;
    public class dddb2
    public static void main(String argv[])
    throws Exception
    Connection c = null;
    try
    java.util.Properties props = new java.util.Properties();
    Driver d = (Driver)Class.forName("weblogic.jdbc.db2.DB2Driver").newInstance();
    props.put("user", "user");
    props.put("password", "password");
    props.put("locationName", "dbserver");
    String URL = "jdbc:bea:db2://dbhost:447";
    c = d.connect(URL, props);
    DatabaseMetaData dm = c.getMetaData();
    System.out.println(dm.getDriverVersion());
    System.out.println("Database version is " + dm.getDatabaseProductVersion() );
    CallableStatement p = c.prepareCall("{ CALL SP03 (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) }");
    p.setInt(1,1234);
    p.setString(2,"XYZ");
    p.setString(3,"XYZ");
    p.setInt(5,1234);
    p.setString(6,"");
    p.setString(7,"XYZ");
    p.setString(9,"XYZ");
    p.setString(12,"XYZ");
    p.registerOutParameter(4,Types.INTEGER);
    p.registerOutParameter(8,Types.INTEGER);
    p.registerOutParameter(10,Types.INTEGER);
    p.registerOutParameter(11,Types.INTEGER);
    p.registerOutParameter(13,Types.INTEGER);
    p.setFetchSize(3);
    p.execute();
    catch (Exception e)
    { e.printStackTrace(); }
    finally
    { try {c.close();}catch (Exception e){} }
    IBM Driver Code
    import java.io.*;
    import java.util.*;
    import java.net.*;
    import java.sql.*;
    import weblogic.common.*;
    public class dddb2ibm
    public static void main(String argv[])
    throws Exception
    Connection c = null;
    try
    java.util.Properties props = new java.util.Properties();
    Driver d = (Driver)Class.forName("com.ibm.db2.jcc.DB2Driver").newInstance();
    props.put("user", "user");
    props.put("password", "password");
    //props.put("databaseName", "dbserver");
    String URL = "jdbc:db2://dbhost:447/dbserver";
    c = d.connect(URL, props);
    DatabaseMetaData dm = c.getMetaData();
    System.out.println(dm.getDriverVersion());
    System.out.println("Database version is " + dm.getDatabaseProductVersion() );
    CallableStatement p = c.prepareCall("{ CALL SP03 (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) }");
    p.setInt(1,1234);
    p.setString(2,"XYZ");
    p.setString(3,"XYZ");
    p.setInt(5,1234);
    p.setString(6,"");
    p.setString(7,"XYZ");
    p.setString(9,"XYZ");
    p.setString(12,"XYZ");
    p.registerOutParameter(4,Types.INTEGER);
    p.registerOutParameter(8,Types.INTEGER);
    p.registerOutParameter(10,Types.INTEGER);
    p.registerOutParameter(11,Types.INTEGER);
    p.registerOutParameter(13,Types.INTEGER);
    p.setFetchSize(3);
    p.execute();
    catch (Exception e)
    { e.printStackTrace(); }
    finally
    { try {c.close();}catch (Exception e){} }

  • XI adapter polling issue & JDBC  / DB2 driver connection timeout properties

    Hello Group,
    We have a long running issue with our XI 7.0 system running on iseries. (V5R3) The issue occuring is that our XI adapters stop polling and the only resolution is to restart the J2EE engine or to resart the adapter framework services.
    We have had several OSS messages open on this subject for over a year and are going round in circles with the a number of different SAP consultants.
    The one topic that we keep coming back to is that we are being asked to set DB2 driver connection timeout properties. We are using the toolbox driver and have upated to the latest JTopen driver, but have not managed to find any inofrmation on how to set the timeout parameter. Does anyone know where the timeout parameter set?
    Has anyone experienced polling issue like this before and how did you resolve?
    SAP referred to the SAP note 1078420 - XI/PI JDBC Adapter: Setting JDBC driver properties for DB which is for Oracle, but this will give an idea of what timeout parameters SAP are asking about.
    Extract of the note is below:-
    Symptom
    This note gives an option to set JDBC driver properties while acquiring a DB connection. When connecting to DB using JDBC adapter there are instances
    where DB connection take a long time to establish connection. Some times call made to Driver will hang permanently. Setting driver properties would resolve this problem.
    More Terms
    Connection timeout, time out, query timeout
    Cause and Prerequisites
    Solution
    In the advanced mode table section of sender channel and receiver channel configurations, we can set driver properties for each DB connection. Any
    such property would have to contain prefix 'driver:'(with out quotes) For example, for Oracle Database JDBC thin driver 10.2.0.3 version, the
    property oracle.jdbc.ReadTimeout helps to set read timeout while reading from the socket. Also for setting login time out in Oracle, we use
    oracle.net.CONNECT_TIMEOUT. To set these two properties use as follows:
    driver:oracle.jdbc.ReadTimeout 1000
    driver:oracle.net.CONNECT_TIMEOUT 1000
    (The TimeOut Driver properties like ReadTimeout and CONNECT_TIMEOUT are in milliseconds)
    Refer to your DB documentation/ JDBC driver documentation on this. Please note that properties can vary from each driver version. For instance, some
    of properties of Oracle JDBC thin Driver 10.2.0.3 properties may not be present in older version drivers. Please contact DB vendor for the complete
    list of driver properties. In addition to above, we also provide another parameter for query time out.
    sqlquerytimeout (prefix 'driver:' is not required) is the parameter that is to be used for SQL query time out. This is case-sensitive and should be
    configured as positive integer value in seconds(greater than 0).
    Any help on this would be much appreciated.
    With regards,
    Steven

    Hello,
    I am not talking about the XI timeouts. But the timeouts which can be used to get the connection timeouts for DB2/AS400 databases.
    So please provide that information.
    THanks,
    soorya

  • How to use DB2 XA driver instead of default DB2 driver

    Hi,
    I've been using the default DB2 driver (com.ibm.db2.jcc.DB2Driver) for a datasource until now. I need to switch to using an XA approved driver to handle some two phase commits. It appears Oracle has an XA driver for DB2 (weblogic.jdbcx.db2.DB2DataSource) but whenever I use it I get the following error:
    [BEA][DB2 JDBC Driver][DB2]PROGRAM NAME NULLID.DDJU360B 0X4A44424334444232 NOT FOUND IN PLAN null
    What does this error mean? How can I switch to an XA DB2 driver?
    Thanks...

    DB2 running on AIX:
    select * from sysibm.sysversions;
    7010200     2001-04-11 17:01:21.478428     WBDID04
    8020000     2005-02-01 19:55:13.083939     SYSIBM
    8020800     2007-09-08 08:16:45.496058     WBDID04
    WebLogic Server 10.3 running on Windows XP.
    Using the XA driver works fine for WebLogic Server 8.1 and the existing DB2 database. So, I'm wondering what went wrong when I upgraded to 10.3.
    The error happens on server startup when it's trying to test the connection:
    <25-May-2010 3:28:44 o'clock PM GMT-06:00> <Error> <JDBC> <BEA-001112> <Test "SELECT COUNT(*) FROM SYSIBM.SYSDUMMY1" set up for pool "csp" failed with exception: "java.sql.SQLException: [BEA][DB2 JDBC Driver][DB2]PROGRAM NAME NULLID.DDJC360B 0X4A44424334444232 NOT FOUND IN PLAN null".>
    Any ideas?

  • Annoying Assertion errors using the DB2 Driver "com.inet.drda.DRDADriver"

    I am using the "com.inet.drda.DRDADriver" DB2 Driver.
    My query works fine and returns everything ok but I get these annoying Assertion failed errors on the console.
    Any Ideas how to stop these?
    I do not have assert enabled on JBuilder.
    Thanks ... J
    Assertion v1 == 0 failed: s.v1@ca=75
    Assertion v1 == 0 failed: s.v1@fb=250
    Assertion v1 == 0 failed: s.v1@128=75
    and so on

    Prior to using the JDBC:DB2 driver I was using the JDBC:ODBC driver and there were no such errors. So the errors are related to using the db2 driver.
    All that has changed is the lines you see commented out replaced by the new driver class.
    Nothing has changed in my Database interface layer.
        //Set up DB url using a JDBC:DB2 driver and get a connection
        String url = "jdbc:inetdb2:" + host + ":" + port + "?database="+tableOwner;
        String driverClass = "com.inet.drda.DRDADriver";
        //Set up DB url using a JDBC:ODBC driver and get a connection
        //String url = "jdbc:ODBC:"+tableOwner;
        //String driverClass = "sun.jdbc.odbc.JdbcOdbc";
    Connection connection = Tools.setUpConnectionToDB(driverClass, url,username,password);
    List appletsFound = Tools.processStatement(Query, connection);I did have Asserts enabled before this but they are not enabled now because I disabled it after I was happy all my JUnit tests were passing.

  • Configuring weblogic6.1 for db2 driver

    Hi all,
    I want to access DB2 database from a servlet running on weblogic6.1.But i am unable
    to configure weblogic 6.1 for DB2 driver.Going through the documentation for configuring
    weblogic third party drivers was of no help.when i run the program i get the error
    "no suitable driver found".
    Please post suggestions on how to configure weblogic6.1 for DB2 driver.
    Thank u in advance.

    Ramesh,
    We use code like the following to successfully connect to a connection pool:
    // put the pool name into a properties,
    // in the same way that you would put "user" and "password" in the properties
    dbproperties.put("connectionPoolID", mypoolName);
    Class.forName("weblogic.jdbc.pool.Driver").newInstance();
    myconnection = DriverManager.getConnection("jdbc:weblogic:pool", dbproperties);
    It shouldn't be much different than the code you have where you get the driver
    and then connect directly. But, I do know that what we use works. Maybe the
    pool name has to be specified in the info properties, rather than in the url string.
    (that would be a simple and easy change to your code; to see if it worked.)
    Also, we have found that the CaSe of the DB2 driver name matters:
    COM.ibm.db2.jdbc.app.DB2Driver
    We also put the db2java.zip as the first item in the classpath. (I don't remember
    if that matters or not).
    Craig
    "Ramesh" <[email protected]> wrote:
    >
    Sree,
    In the weblogic 6.1 connection pool configuration i have the following
    settings:
    Name:myPool
    URL:jdbc:db2:database (database is the name of sample database in db2)
    Driver Classname:Com.ibm.db2.jdbc.app.DB2Driver
    Properties:user=db2admin;password=asits9;DatabaseName=database
    ACL name:blank
    Password:blank
    but when i select Target-Server from Targets tab of JDBC Connection Pool
    i get
    the error "Error Occured while processing your request" which is something
    java.lang.reflect.InvocationTargetException.
    in my servlet i establish the connection with the db2 database through
    the following
    codes
    Connection conn=null;
    Driver d;
    d=(Driver)Class.forName("weblogic.jdbc.pool.Driver").newInstance();
    conn=d.connect("jdbc:weblogic:pool:myPool",null);
    ramesh.
    "Sree Bodapati" <[email protected]> wrote:
    Can you show me your standalone program (or just the url, driver name
    and
    properties you use to get connection). Sometimes the url doesnt match
    up
    properly. Do you see any exceptions when the connection pool is getting
    created?
    sree
    "ramesh" <[email protected]> wrote in message
    news:[email protected]...
    Sree,
    I can access db2 from a simple standalone java application.
    but when i create connection pool in weblogic6.1,i think it is not getting
    created,bcos
    when i run the servlet i get the error "Pool connect
    failed:java.SQLException:Connection
    pool myPool does not exist" where myPool is the name of the connection
    pool
    i
    created.i have db2java.zip in my classpath.
    do i have to set some other classpaths also.
    ramesh.
    "Sree Bodapati" <[email protected]> wrote:
    Ramesh,
    If you can write a simple standalone java program to get a DB2 connection
    using the DB2 driver (without WebLogic in the picture). You will findout
    what URL and Driver name to use and what properties to pass to the
    driver.
    Specify these properties in the connection pool properties and make
    sure
    the DB2 driver is in the CLASSPATH when you boot the WebLogic server.
    sree
    "ramesh chand" <[email protected]> wrote in message
    news:[email protected]...
    Hi all,
    I want to access DB2 database from a servlet running on weblogic6.1.But
    i am
    unable
    to configure weblogic 6.1 for DB2 driver.Going through the documentation
    for
    configuring
    weblogic third party drivers was of no help.when i run the programi
    get the
    error
    "no suitable driver found".
    Please post suggestions on how to configure weblogic6.1 for DB2 driver.
    Thank u in advance.

  • DB2 Driver NET or APP?

    Hi,
    I get an error while connecting to DB2 database by using JDBC "COM.ibm.db2.jdbc.net" driver. Do you have an idea about reason of this error?
    [IBM][JDBC Driver] CLI0615E Error receiving from socket, server is not responding. SQLSTATE=08S01.
    DB2 server is working on another server (Win2000 Advanced Server) And I try to connect it from my Win2000 and using stand alone application.
    I can not use the app driver by IP and PORT...
    thanks for your reply...

    hi, we are getting the same error you got, we are trying to connect to a mainframe running db2 from a servlet running on a Websphere app server with DB2Connect installed on the same machine.
    Please can you inform us if you found a solution? did you finally use the NET or APP driver? did you need to install any special software on the db2 server? and on the client?
    thanks very much,

  • Can't load DB2 driver!

    I have a Java app I run from the command line that can access my DB2 database. However, when I put my code into Websphere as a Servlet, it won't connect. Same driver, same dbURL, same everything, but it won't connect. I'm wondering if I have to configure my webapp in the Admin Console or something. I see there is a node called JDBC driver, but I can't do anything to it, I can't open it, edit it, or anything. What am I doing wrong? Help!

    sorry i have not ur answer.
    please give me connecting string databse DB2.
    ur DB2 server on which OS. may be there driver problem?
    but plz give me connecting string

  • DB2 driver version clash

    Hello,
      I have two db2 db with different versions (7.1 and 8.1), I can only access a db2 db with driver of it's own version. I can't put both versions in XI. How do I solve this.
    Regards,
    Sanjay

    hi Sanjay,
    Normally, when you install the drivers for the latest release of any database, it is always compatible with the earlier versions.
    Atleast, that is how it is in the case of oracle, where ojdbc14.jar is used to access Oracle 9i and it is compatible with clases12.zip (for earlier versions of Oracle) also.
    I would suggest that you deploy the driver for DB2 8.1 and use it to access DB2 7.1. It might/ should work
    Regards,
    Bhavesh

  • ClassNotFoundException for DB2 Driver

    Hi everyone
    I'm trying to connect to a DB2 database from a JSP page and I'm having some problems with the classpath.
    This is how this part of my JSP looks:
    <%@ page  import = "java.util.*" %>
    <HTML>
    <BODY>
    <%try {
    Class.forName("COM.ibm.db2.jdbc.app.DB2Driver");
    } catch (Exception e) {
    %>
    Error : <%=e%>
    <% } %>
    </BODY>
    </HTML>... and I get this error:
    Error : java.lang.ClassNotFoundException: COM.ibm.db2.jdbc.app.DB2Driver
    I am using Apache Tomcat, and I have copied the db2java.zip file (which contains the DB2Driver.class file) into the MyApplication/WEB-INF/lib folder.
    As far as I know, this should be enough for that file to be in the classpath, but apparently it isn't.
    If I do
    out.println("java.class.path: " + String.valueOf(System.getProperty("java.class.path")));I get this:
    java.class.path: C:\Program Files\Apache Software Foundation\Tomcat 5.5\bin\bootstrap.jar
    ... so obviously the file isn't there.
    What am I doing wrong? Any ideas?
    Thank you very much.

    You have to copy the jar file instead of zip file (db2java.zip) into /WEB-INF/lib

  • Db2 driver

    Hi Everyone ,
    I have downloaded db2driver for jdbc. Its a zip file but i dont have any idea as what to do next. Please suggest me the next step.

    What would you do with zip files as usual?
    It might be worth reading the download page at IBM site for instructions for further steps.

  • Reg: DB2 Database growth

    Dear Friends,
    I want how do show database growth daily wise and monthly wise and Module wise?
    Like
    MM, FICO, SD, PP, QM and etc.
    How do i show DB growth? wheather any standard reports are there in SAP?
    Regards
    kesav

    > I want how do show database growth daily wise and monthly wise and Module wise?
    The "module wise" is very difficult to archive. To what would you relate a material master data? MM? SD?
    > How do i show DB growth? wheather any standard reports are there in SAP?
    Check transaction DBACOCKPIT.
    Markus

  • Kodo 3.1.2 + IBM  DB2 7.2 = No Suitable Driver?

    Hello there,
    we are trying to use Kodo 3.1.2 with DB 7.2 Fixpak 5 and higher.
    I've build an ant-script with the following snippet:
    <target name="defineSchemaKodo" if="jdo.implementierung.kodo">
    <taskdef name="mappingtool"
    classname="kodo.jdbc.ant.MappingToolTask">
    <classpath refid="build.classpath"/>
    </taskdef>
    <taskdef name="schematool"
    classname="kodo.jdbc.ant.SchemaToolTask">
    <classpath refid="build.classpath"/>
    </taskdef>
              <mappingtool action="buildSchema" schemaFile="${basedir}/package.schema">
    <classpath refid="build.classpath"/>
              <fileset dir="${model.build.dir}">
                   <include name="*.jdo" />
              </fileset>
              </mappingtool>
              <schematool action="createDB" file="${basedir}/schema.ddl">
    <classpath refid="build.classpath"/>
         <fileset dir=".">
         <include name="${basedir}/package.schema" />
         </fileset>
         </schematool>
         </target>
    The property "compile.classpath" contains db2java.jar, so the driver
    should be availiable at runtime.
    When running the script I get this stacktrace:
    defineSchemaKodo:
    [mappingtool] kodo.util.FatalDataStoreException: No suitable driver
    [mappingtool] NestedThrowables:
    [mappingtool] java.sql.SQLException: No suitable driver
    [mappingtool]      at
    kodo.jdbc.sql.SQLExceptions.getFatalDataStore(SQLExceptions.java:42)
    [mappingtool]      at
    kodo.jdbc.sql.SQLExceptions.getFatalDataStore(SQLExceptions.java:24)
    [mappingtool]      at
    kodo.jdbc.sql.DBDictionaryFactory.getDBDictionary(DBDictionaryFactory.java:61)
    [mappingtool]      at
    kodo.jdbc.conf.JDBCConfigurationImpl.getDBDictionaryInstance(JDBCConfigurationImpl.java:630)
    [mappingtool]      at
    kodo.jdbc.conf.JDBCConfigurationImpl.getConnectionFactory(JDBCConfigurationImpl.java:880)
    [mappingtool]      at
    kodo.jdbc.conf.JDBCConfigurationImpl.getDataSource(JDBCConfigurationImpl.java:970)
    [mappingtool]      at
    kodo.jdbc.conf.JDBCConfigurationImpl.getDataSource2(JDBCConfigurationImpl.java:979)
    [mappingtool]      at kodo.jdbc.schema.SchemaTool.<init>(SchemaTool.java:78)
    [mappingtool]      at
    kodo.jdbc.meta.MappingTool.newSchemaTool(MappingTool.java:269)
    [mappingtool]      at
    kodo.jdbc.meta.MappingTool.getSchemaTool(MappingTool.java:259)
    [mappingtool]      at kodo.jdbc.meta.MappingTool.run(MappingTool.java:898)
    [mappingtool]      at
    kodo.jdbc.ant.MappingToolTask.executeOn(MappingToolTask.java:175)
    [mappingtool]      at com.solarmetric.ant.TaskBase.execute(TaskBase.java:105)
    [mappingtool]      at
    org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:269)
    [mappingtool]      at org.apache.tools.ant.Task.perform(Task.java:364)
    [mappingtool]      at org.apache.tools.ant.Target.execute(Target.java:301)
    [mappingtool]      at
    org.apache.tools.ant.Target.performTasks(Target.java:328)
    [mappingtool]      at
    org.apache.tools.ant.Project.executeTarget(Project.java:1215)
    [mappingtool]      at
    org.apache.tools.ant.Project.executeTargets(Project.java:1063)
    [mappingtool]      at
    org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:569)
    [mappingtool]      at
    org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:367)
    [mappingtool]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
    Method)
    [mappingtool]      at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown
    Source)
    [mappingtool]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
    Source)
    [mappingtool]      at java.lang.reflect.Method.invoke(Unknown Source)
    [mappingtool]      at org.eclipse.ant.core.AntRunner.run(AntRunner.java:335)
    [mappingtool]      at
    org.eclipse.ui.externaltools.internal.ant.launchConfigurations.AntLaunchDelegate$1.run(AntLaunchDelegate.java:172)
    [mappingtool]      at java.lang.Thread.run(Unknown Source)
    [mappingtool] NestedThrowablesStackTrace:
    [mappingtool] java.sql.SQLException: No suitable driver
    [mappingtool]      at java.sql.DriverManager.getDriver(Unknown Source)
    [mappingtool]      at
    com.solarmetric.jdbc.PoolingDataSource.getDriver(PoolingDataSource.java:271)
    [mappingtool]      at
    com.solarmetric.jdbc.PoolingDataSource.newConnection(PoolingDataSource.java:313)
    [mappingtool]      at
    com.solarmetric.jdbc.ConnectionPoolImpl.makeConnection(ConnectionPoolImpl.java:270)
    [mappingtool]      at
    com.solarmetric.jdbc.ConnectionPoolImpl.getConnection(ConnectionPoolImpl.java:178)
    [mappingtool]      at
    com.solarmetric.jdbc.PoolingDataSource.getConnection(PoolingDataSource.java:237)
    [mappingtool]      at
    com.solarmetric.jdbc.DelegatingDataSource.getConnection(DelegatingDataSource.java:130)
    [mappingtool]      at
    com.solarmetric.jdbc.DecoratingDataSource.getConnection(DecoratingDataSource.java:81)
    [mappingtool]      at
    com.solarmetric.jdbc.DelegatingDataSource.getConnection(DelegatingDataSource.java:130)
    [mappingtool]      at
    kodo.jdbc.schema.DataSourceFactory$DefaultsDataSource.getConnection(DataSourceFactory.java:295)
    [mappingtool]      at
    kodo.jdbc.sql.DBDictionaryFactory.getDBDictionary(DBDictionaryFactory.java:56)
    [mappingtool]      at
    kodo.jdbc.conf.JDBCConfigurationImpl.getDBDictionaryInstance(JDBCConfigurationImpl.java:630)
    [mappingtool]      at
    kodo.jdbc.conf.JDBCConfigurationImpl.getConnectionFactory(JDBCConfigurationImpl.java:880)
    [mappingtool]      at
    kodo.jdbc.conf.JDBCConfigurationImpl.getDataSource(JDBCConfigurationImpl.java:970)
    [mappingtool]      at
    kodo.jdbc.conf.JDBCConfigurationImpl.getDataSource2(JDBCConfigurationImpl.java:979)
    [mappingtool]      at kodo.jdbc.schema.SchemaTool.<init>(SchemaTool.java:78)
    [mappingtool]      at
    kodo.jdbc.meta.MappingTool.newSchemaTool(MappingTool.java:269)
    [mappingtool]      at
    kodo.jdbc.meta.MappingTool.getSchemaTool(MappingTool.java:259)
    [mappingtool]      at kodo.jdbc.meta.MappingTool.run(MappingTool.java:898)
    [mappingtool]      at
    kodo.jdbc.ant.MappingToolTask.executeOn(MappingToolTask.java:175)
    [mappingtool]      at com.solarmetric.ant.TaskBase.execute(TaskBase.java:105)
    [mappingtool]      at
    org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:269)
    [mappingtool]      at org.apache.tools.ant.Task.perform(Task.java:364)
    [mappingtool]      at org.apache.tools.ant.Target.execute(Target.java:301)
    [mappingtool]      at
    org.apache.tools.ant.Target.performTasks(Target.java:328)
    [mappingtool]      at
    org.apache.tools.ant.Project.executeTarget(Project.java:1215)
    [mappingtool]      at
    org.apache.tools.ant.Project.executeTargets(Project.java:1063)
    [mappingtool]      at
    org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:569)
    [mappingtool]      at
    org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:367)
    [mappingtool]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
    Method)
    [mappingtool]      at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown
    Source)
    [mappingtool]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
    Source)
    [mappingtool]      at java.lang.reflect.Method.invoke(Unknown Source)
    [mappingtool]      at org.eclipse.ant.core.AntRunner.run(AntRunner.java:335)
    [mappingtool]      at
    org.eclipse.ui.externaltools.internal.ant.launchConfigurations.AntLaunchDelegate$1.run(AntLaunchDelegate.java:172)
    [mappingtool]      at java.lang.Thread.run(Unknown Source)
    [mappingtool] BUILD FAILED:
    E:\bl04285\workspace\CRM\jdoTemporal\build.xml:170:
    kodo.util.FatalDataStoreException: No suitable driver
    NestedThrowables:
    java.sql.SQLException: No suitable driver
    Any ideas?

    You should also try using the jcc (preferred) or the net driver which is
    more flexible in classpath and system configurations.
    The DB2 driver is very sensitive to changes due to reliance on system
    shared libraries.
    Serge Arpin wrote:
    Just a guess:
    - do you use db2 type 2 driver (jdbc:db2:dbname) or type 3
    (jdbc:db2:/server:port/dbname) ?
    If you use type 2, JUST try Type 3. I had the same symptom under WSAD with
    the DB2 v7.2.11 type 2 driver... and it worked with type 3 driver.
    (And dont forget to start the db2-type-3-driver-listener on your DB2
    server.
    Knobloch wrote:
    Hello there,
    we are trying to use Kodo 3.1.2 with DB 7.2 Fixpak 5 and higher.
    I've build an ant-script with the following snippet:
    <target name="defineSchemaKodo" if="jdo.implementierung.kodo">
    <taskdef name="mappingtool"
    classname="kodo.jdbc.ant.MappingToolTask">
    <classpath refid="build.classpath"/>
    </taskdef>
    <taskdef name="schematool"
    classname="kodo.jdbc.ant.SchemaToolTask">
    <classpath refid="build.classpath"/>
    </taskdef>
              <mappingtool action="buildSchema" schemaFile="$/package.schema">
    <classpath refid="build.classpath"/>
              <fileset dir="$">
                   <include name="*.jdo" />
              </fileset>
              </mappingtool>
              <schematool action="createDB" file="$/schema.ddl">
    <classpath refid="build.classpath"/>
         <fileset dir=".">
         <include name="$/package.schema" />
         </fileset>
         </schematool>
         </target>
    The property "compile.classpath" contains db2java.jar, so the driver
    should be availiable at runtime.
    When running the script I get this stacktrace:
    defineSchemaKodo:
    [mappingtool] kodo.util.FatalDataStoreException: No suitable driver
    [mappingtool] NestedThrowables:
    [mappingtool] java.sql.SQLException: No suitable driver
    [mappingtool]      at
    kodo.jdbc.sql.SQLExceptions.getFatalDataStore(SQLExceptions.java:42)
    [mappingtool]      at
    kodo.jdbc.sql.SQLExceptions.getFatalDataStore(SQLExceptions.java:24)
    [mappingtool]      at
    kodo.jdbc.sql.DBDictionaryFactory.getDBDictionary(DBDictionaryFactory.java:61)
    [mappingtool]      at
    kodo.jdbc.conf.JDBCConfigurationImpl.getDBDictionaryInstance(JDBCConfigurationImpl.java:630)
    [mappingtool]      at
    kodo.jdbc.conf.JDBCConfigurationImpl.getConnectionFactory(JDBCConfigurationImpl.java:880)
    [mappingtool]      at
    kodo.jdbc.conf.JDBCConfigurationImpl.getDataSource(JDBCConfigurationImpl.java:970)
    [mappingtool]      at
    kodo.jdbc.conf.JDBCConfigurationImpl.getDataSource2(JDBCConfigurationImpl.java:979)
    [mappingtool]      at kodo.jdbc.schema.SchemaTool.<init>(SchemaTool.java:78)
    [mappingtool]      at
    kodo.jdbc.meta.MappingTool.newSchemaTool(MappingTool.java:269)
    [mappingtool]      at
    kodo.jdbc.meta.MappingTool.getSchemaTool(MappingTool.java:259)
    [mappingtool]      at kodo.jdbc.meta.MappingTool.run(MappingTool.java:898)
    [mappingtool]      at
    kodo.jdbc.ant.MappingToolTask.executeOn(MappingToolTask.java:175)
    [mappingtool]      at com.solarmetric.ant.TaskBase.execute(TaskBase.java:105)
    [mappingtool]      at
    org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:269)
    [mappingtool]      at org.apache.tools.ant.Task.perform(Task.java:364)
    [mappingtool]      at org.apache.tools.ant.Target.execute(Target.java:301)
    [mappingtool]      at
    org.apache.tools.ant.Target.performTasks(Target.java:328)
    [mappingtool]      at
    org.apache.tools.ant.Project.executeTarget(Project.java:1215)
    [mappingtool]      at
    org.apache.tools.ant.Project.executeTargets(Project.java:1063)
    [mappingtool]      at
    org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:569)
    [mappingtool]      at
    org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:367)
    [mappingtool]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
    Method)
    [mappingtool]      at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown
    Source)
    [mappingtool]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
    Source)
    [mappingtool]      at java.lang.reflect.Method.invoke(Unknown Source)
    [mappingtool]      at org.eclipse.ant.core.AntRunner.run(AntRunner.java:335)
    [mappingtool]      at
    org.eclipse.ui.externaltools.internal.ant.launchConfigurations.AntLaunchDelegate$1.run(AntLaunchDelegate.java:172)
    [mappingtool]      at java.lang.Thread.run(Unknown Source)
    [mappingtool] NestedThrowablesStackTrace:
    [mappingtool] java.sql.SQLException: No suitable driver
    [mappingtool]      at java.sql.DriverManager.getDriver(Unknown Source)
    [mappingtool]      at
    com.solarmetric.jdbc.PoolingDataSource.getDriver(PoolingDataSource.java:271)
    [mappingtool]      at
    com.solarmetric.jdbc.PoolingDataSource.newConnection(PoolingDataSource.java:313)
    [mappingtool]      at
    com.solarmetric.jdbc.ConnectionPoolImpl.makeConnection(ConnectionPoolImpl.java:270)
    [mappingtool]      at
    com.solarmetric.jdbc.ConnectionPoolImpl.getConnection(ConnectionPoolImpl.java:178)
    [mappingtool]      at
    com.solarmetric.jdbc.PoolingDataSource.getConnection(PoolingDataSource.java:237)
    [mappingtool]      at
    com.solarmetric.jdbc.DelegatingDataSource.getConnection(DelegatingDataSource.java:130)
    [mappingtool]      at
    com.solarmetric.jdbc.DecoratingDataSource.getConnection(DecoratingDataSource.java:81)
    [mappingtool]      at
    com.solarmetric.jdbc.DelegatingDataSource.getConnection(DelegatingDataSource.java:130)
    [mappingtool]      at
    kodo.jdbc.schema.DataSourceFactory$DefaultsDataSource.getConnection(DataSourceFactory.java:295)
    [mappingtool]      at
    kodo.jdbc.sql.DBDictionaryFactory.getDBDictionary(DBDictionaryFactory.java:56)
    [mappingtool]      at
    kodo.jdbc.conf.JDBCConfigurationImpl.getDBDictionaryInstance(JDBCConfigurationImpl.java:630)
    [mappingtool]      at
    kodo.jdbc.conf.JDBCConfigurationImpl.getConnectionFactory(JDBCConfigurationImpl.java:880)
    [mappingtool]      at
    kodo.jdbc.conf.JDBCConfigurationImpl.getDataSource(JDBCConfigurationImpl.java:970)
    [mappingtool]      at
    kodo.jdbc.conf.JDBCConfigurationImpl.getDataSource2(JDBCConfigurationImpl.java:979)
    [mappingtool]      at kodo.jdbc.schema.SchemaTool.<init>(SchemaTool.java:78)
    [mappingtool]      at
    kodo.jdbc.meta.MappingTool.newSchemaTool(MappingTool.java:269)
    [mappingtool]      at
    kodo.jdbc.meta.MappingTool.getSchemaTool(MappingTool.java:259)
    [mappingtool]      at kodo.jdbc.meta.MappingTool.run(MappingTool.java:898)
    [mappingtool]      at
    kodo.jdbc.ant.MappingToolTask.executeOn(MappingToolTask.java:175)
    [mappingtool]      at com.solarmetric.ant.TaskBase.execute(TaskBase.java:105)
    [mappingtool]      at
    org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:269)
    [mappingtool]      at org.apache.tools.ant.Task.perform(Task.java:364)
    [mappingtool]      at org.apache.tools.ant.Target.execute(Target.java:301)
    [mappingtool]      at
    org.apache.tools.ant.Target.performTasks(Target.java:328)
    [mappingtool]      at
    org.apache.tools.ant.Project.executeTarget(Project.java:1215)
    [mappingtool]      at
    org.apache.tools.ant.Project.executeTargets(Project.java:1063)
    [mappingtool]      at
    org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:569)
    [mappingtool]      at
    org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:367)
    [mappingtool]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
    Method)
    [mappingtool]      at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown
    Source)
    [mappingtool]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
    Source)
    [mappingtool]      at java.lang.reflect.Method.invoke(Unknown Source)
    [mappingtool]      at org.eclipse.ant.core.AntRunner.run(AntRunner.java:335)
    [mappingtool]      at
    org.eclipse.ui.externaltools.internal.ant.launchConfigurations.AntLaunchDelegate$1.run(AntLaunchDelegate.java:172)
    [mappingtool]      at java.lang.Thread.run(Unknown Source)
    [mappingtool] BUILD FAILED:
    E:bl04285workspaceCRMjdoTemporalbuild.xml:170:
    kodo.util.FatalDataStoreException: No suitable driver
    NestedThrowables:
    java.sql.SQLException: No suitable driver
    Any ideas?
    Steve Kim
    [email protected]
    SolarMetric Inc.
    http://www.solarmetric.com

Maybe you are looking for