Websphere 6.0 DataSource, Microsoft JDBC driver

I am trying to configure a DataSource using Websphere 6.0 and Microsoft's JDBC Driver for SQL Server 2000.
I am configuring a V4 DataSource (not a V6 DataSource).
After configuring the JDBC Provider and the DataSource, the Test Connection operation generates this message:
DSRA8101E: DataSource class cannot be used as one-phase:
ClassCastException: com/microsoft/jdbc/sqlserver/SQLServerDriver incompatible with javax/sql/ConnectionPoolDataSource,
error code: NOT_A_1_PHASE_DS
How can I fix this? Is anybody using Microsoft�s JDBC driver and Websphere 6.0?

looks like it's a problem between single phase and two-phase commit drivers. They're different, of course. there are extra steps required to get SQL Server to participate in 2 phase XA.
I know how to do it in WebLogic. Not sure about WebSphere.
%

Similar Messages

  • Microsoft Jdbc driver for SQL Server memory leak

    I'm using Microsoft Jdbc driver and see there's some leak after running application for a while. I'm sure that it's from Jdbc driver because I sitch to Jtds and the issue went away. My question is is there anybody knows which web sites talk about memory leak issue in Microsoft Jdbc driver for SQL Server?
    Appreciate your help

    I'm using Microsoft Jdbc driver and see there's some leak after running application for a while. I'm sure that it's from Jdbc driver because I sitch to Jtds and the issue went away. My question is is there anybody knows which web sites talk about memory leak issue in Microsoft Jdbc driver for SQL Server?
    Appreciate your help

  • Question about load Microsoft JDBC driver for Sql server 2000

    Hello,
    I have some problem while trying load the sqlserver2000 jdbc driver
    My program is a third party application and it works with the other type 4 JDBC driver well. So I tried to use Microsoft SQL server 2000 JDBC driver instead.
    I installed JDBC driver and set up the classpath.
    My error message is:
    "Driver class 'com.microsoft.jdbc.sqlserver.SQLServerDriver' could not be loaded"
    Is above message means that my classpath setup correctly but the application could not load the class or the application could not find the jar file which containes the driver class?
    By the way, the third party application I was using to load this JDBC driver does not certified to use microsoft JDBC driver. But I don't think it matter?
    Thanks for your help
    Hui Lu

    Hello,
    I have some problem while trying load the
    sqlserver2000 jdbc driver
    My program is a third party application and it works
    with the other type 4 JDBC driver well. So I tried to
    use Microsoft SQL server 2000 JDBC driver instead.
    I installed JDBC driver and set up the classpath.
    My error message is:
    "Driver class
    'com.microsoft.jdbc.sqlserver.SQLServerDriver' could
    not be loaded"
    That is an unusual message. Presumably you did not see "NoClassDefFoundError". If you see that it means the class could not be found.
    Is above message means that my classpath setup
    correctly but the application could not load the class
    or the application could not find the jar file which
    containes the driver class?
    By the way, the third party application I was using to
    load this JDBC driver does not certified to use
    microsoft JDBC driver. But I don't think it matter?
    It could. Perhaps the app expects a certain functional level and the driver doesn't support that. And so it bails with the message that you see.
    Or it could mean that you have do something special because it has its own class path, and the driver is not in that.

  • Gor The result set is closed after switch to latest microsoft JDBC driver

    The same code works fine with the previous version of the microsoft JDBC driver, but throws
    com.microsoft.sqlserver.jdbc.SQLServerException: The result set is closed.
    for the JDBC driver 4.
    Please Help!
    Thanks.

    I found the same exception when dealing with ResultSetMetaData.
    Using the old driver (1.2.2828.100) it was possible to do something like:
    Statement s = con.createStatement();
    ResultSet r = s.executeQuery("select * from <table>");
    ResultSetMetaData m = r.getMetaData();
    r.close();
    s.close();
    int numCols = m.getColumnCount();
    But using the new driver (2.0.1803.100) it complains that the result set is closed.
    The solution was to keep the ResultSet and Statement open until after the ResultSetMetaData is no longer needed. It is somewhat inconvenient because before it was possible to have a utility method that would return a ResultSetMetaData object and not have to worry about keeping the Statement and ResultSet objects around.
    I was hoping for a speed increase for batch inserts by having the latest driver, sadly there is no performance gain.

  • Does setQueryTimeout still spawn a thread with Microsoft JDBC Driver 4.0?

    Hi,
    Does setQueryTimeout still spawn a thread with Microsoft JDBC Driver 4.0?
    This link here indicates this was fixed awhile ago:
    http://msdn.microsoft.com/en-us/sqlserver/aa937724.aspx
    However, we are using Microsoft JDBC Driver 4.0 but are noticing that a setQueryTimeout thread is being spawned (of class com.microsoft.sqlserver.jdbc.TimeoutTimer) for every query we execute.
    And, the thread seems to stay around even after the query has finished executing.
    Can anyone confirm whether this is actually fixed?
    Or, does anyone have any ideas how we can avoid having a new thread spawned for monitoring for a query timeout?
    Thanks! 

    Hi,
    Does setQueryTimeout still spawn a thread with Microsoft JDBC Driver 4.0?
    This link here indicates this was fixed awhile ago:
    http://msdn.microsoft.com/en-us/sqlserver/aa937724.aspx
    However, we are using Microsoft JDBC Driver 4.0 but are noticing that a setQueryTimeout thread is being spawned (of class com.microsoft.sqlserver.jdbc.TimeoutTimer) for every query we execute.
    And, the thread seems to stay around even after the query has finished executing.
    Can anyone confirm whether this is actually fixed?
    Or, does anyone have any ideas how we can avoid having a new thread spawned for monitoring for a query timeout?
    Thanks! 

  • Could not find Microsoft JDBC Driver ???

    Hi all,
    My program could not find the JDBC driver. Why?????
    Here is my environment:
    Platform: Win2000
    Database: Sql2000
    Tool: JBuilder enterprise (trial version)
    JDBC Driver: Microsoft JDBC driver for SQL Server 2000
    I set the CLASSPATH=.;D:\Sql200JDBCDriver\lib\msbase.jar;D:\Sql200JDBCDriver\lib\msutil.jar;D:\Sql200JDBCDriver\lib\mssqlserver.jar
    Here is my javabean:
    package test;
    import java.sql.*;
    import java.io.*;
    public class LoginBean{
    public static boolean login(String strUser, String strPass)     {
    ResultSet rs;
    try{
    System.out.println("before class.forName");//Print trapped error.
    Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
    System.out.println("After class.forName");//Print trapped error.
    java.sql.Connection theConnection = DriverManager.getConnection("jdbc:microsoft:sqlserver://localhost:8080;DataBaseName ='MyDataBase;User=sa;passowrd="); //Connect to db
    System.out.println("After get connection");//Print trapped error.
    Statement theStatement=theConnection.createStatement();
    rs=theStatement.executeQuery("SELECT username, password FROM login WHERE username= '" + strUser + "' AND password= '" + strPass + "'");
    if(rs.next()) //Fetch username of record
    return true;
    }catch(Exception e){
    System.out.println("before e.getMessage error");//Print trapped error.
    System.out.println(e.getMessage());//Print trapped error.
    System.out.println("after e.getMessage error");//Print trapped error.
    } return false;
    Here are the messages I got:
    before class.forName
    before e.getMessage error
    com.microsoft.jdbc.sqlserver.SQLServerDriver
    after e.getMessage error.
    The program never got throught the statement: Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
    What's wrong?????
    thanks in advanced.

    I guess you have a good idea what the problem is. Either the class name you have specified is wrong or the required library is not on the classpath.
    How are you setting the classpath? Are you running your application through JBuilder or through the command line?
    If it's through JBuilder then make sure that you've configured one of their tiresome "Libraries" and that your project has it in its "Required Libraries".
    Never rely on environment variables to supply the classpath - it takes very little effort to set up a classpath for each application you're developing and will ensure you're using the versions of each library that you want to. Personally I make sure I delete the classpath environment variable so there's nothing implicit hiding away.
    Hope this helps.

  • Is it supported to use Microsoft JDBC driver use in Java 7 (and 8) multithreaded applications?

    Hello everone
    is it supported to use Microsoft JDBC driver (the latest version) with Java 7 multithreaded application?
    I am planning to use standard Java 7 threads library and use separate JDBC objects per each thread, i.e. Java threads will not share any JDBC objects among them, only the thread-safe Java collections/data structures will be shared between threads (such as
    ConcurrentHashMap etc). The JDBC connections, resultsets, statements, etc will be created and dedicated per each individual thread.
    If it is supported - do you expect this design to scale-up well or am I better off using multiple but single-threaded Java/JBDC programs to access SQL Server 2012/2014 from Microsoft JDBC driver?
    Thanks
    Yuri Budilov
    Yuri Budilov Melbourne Australia

    >is it supported to use Microsoft JDBC driver (the latest version) with Java 7 multithreaded application?
    Yes, so long as:
    > Java threads will not share any JDBC objects among them,
    >do you expect this design to scale-up well or am I better off using multiple but single-threaded Java/JBDC programs >to access SQL Server 2012/2014 from Microsoft JDBC driver?
    Using threads should scale better than using processes (at least on Windows), as there is quite a bit of overhead with a process.  Each process has it's own JRE, it's own GC heap, its own threads...
    The bigger question, though, is how this scales on the SQL Server.  Your throughput may be limited by resources on your database server, and the thread's workloads may not be able to run concurrently because of locking. 
    David
    David http://blogs.msdn.com/b/dbrowne/

  • Porblem loading Microsoft JDBC Driver for SQL Server

    Hi all !!
    Well, it seems there is a naming problem for the MS Driver, when Netbeans creates server resources for the Connection Pool and the DataSource, the default name for the connection pool's datasource classname is com.microsoft.jdbc.sqlserver.SQLServerDataSource, but the actual name of the class within the driver's jar is com.microsoft.jdbcx.sqlserver.SQLServerDataSource, note the 'x' after jdbc.
    I changed this and the resource is created correctly (from the admin console, it pings to the DB server), but when I try to deploy the project, I get this error:
    RAR5038:Unexpected exception while creating resource
    RAR5117 : Failed to obtain/create connection. Reason : Class name is wrong or classpath is not set for : com.microsoft.jdbc.sqlserver.SQLServerDataSource
    RAR5114 : Error allocating connection : [Error in allocating a connection. Cause: Class name is wrong or classpath is not set for : com.microsoft.jdbc.sqlserver.SQLServerDataSource]
    WebModule[WebApplication2]java.sql.SQLException: Error in allocating a connection. Cause: Class name is wrong or classpath is not set for : com.microsoft.jdbc.sqlserver.SQLServerDataSource
    java.lang.RuntimeException: java.sql.SQLException: Error in allocating a connection. Cause: Class name is wrong or classpath is not set for : com.microsoft.jdbc.sqlserver.SQLServerDataSource
    I guess I must change the name of the classname in some other place, but I searched the admin colsole and Netbeans and failed to find where it should be.
    I'm using Netbeans 5.5 and SQL Server 200 with the MS JDBC Driver sp 3.
    Thanks in advance,
    Daniel

    Thanks for your answer !!
    Yes, the datasource classname is correct in domains.xml.
    I had the driver files copied into Appserver/lib, now I placed them also where you suggested me and restarted the server.
    Now I get a different error:
    LDR5202:Exception in EJBClassLoader
    java.io.IOException: The filename, directory or volume label are not valid:
    at java.io.WinNTFileSystem.canonicalize0(Native Method)
    at java.io.Win32FileSystem.canonicalize(Win32FileSystem.java:396)
    at java.io.File.getCanonicalPath(File.java:559)
    at com.sun.enterprise.loader.EJBClassLoader$1.run(EJBClassLoader.java:418)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sun.enterprise.loader.EJBClassLoader.findResource0(EJBClassLoader.java:391)
    at com.sun.enterprise.loader.EJBClassLoader.findResource(EJBClassLoader.java:467)
    at java.lang.ClassLoader.getResource(ClassLoader.java:977)
    at java.lang.ClassLoader.getResource(ClassLoader.java:972)
    at java.lang.ClassLoader.getResourceAsStream(ClassLoader.java:1159)
    at com.sun.enterprise.loader.EJBClassLoader.getResourceAsStream(EJBClassLoader.java:782)
    at com.sun.xml.rpc.spi.JaxRpcObjectFactory.newInstance(JaxRpcObjectFactory.java:131)
    at com.sun.enterprise.webservice.codegen.JaxRpcRICodegen.<init>(JaxRpcRICodegen.java:120)
    at com.sun.enterprise.webservice.codegen.JaxRpcCodegenFactory.getAdapter(JaxRpcCodegenFactory.java:50)
    at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:839)
    at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:580)
    at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployModule(EJBCompiler.java:413)
    at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:226)
    at com.sun.enterprise.deployment.backend.ModuleDeployer.runEJBC(ModuleDeployer.java:1189)
    at com.sun.enterprise.deployment.backend.WebModuleDeployer.deploy(WebModuleDeployer.java:179)
    at com.sun.enterprise.deployment.backend.ModuleDeployer.doRequestFinish(ModuleDeployer.java:160)
    at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:169)
    at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:95)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:871)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:266)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:739)
    at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:174)
    at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:210)
    I guess it may have something to do with any of the classpathes, there is a system or environment CP, one for the App server (with prefixes, suffixes, etc, and there is another in the Netbeans IDE tools Options....
    I also tried to debug into java.io.WinNTFileSystem.canonicalize0(Native Method) just to see the name of the file who raised the exception, but I couldn't attach the BPEL debugger, it gives me this error:
    11:57:24 Connecting to localhost:3343
    11:57:24 Unable to start a debug session : Unable to connect to localhost:3343 : Connection refused: connect
    I'm using a proxy but the system settings are set to not use the proxy for localhost addresses and so is netbeans.
    How much I miss the simplicity of the old Turbo Pascal days !!
    Thanks for your help !!
    Daniel

  • Access denial on connecting SQL server 2000 with Microsoft JDBC driver

    Hi guys,
    I am developping a BMP invoking procedures stored in a SQL server 2000 instance on the Sun RI platform. I am using the Microsoft type 4 JDBC driver.
    the connection pattern is something like
    jdbc:microsoft:sqlserver://ambassador:1433;User=sa;Password;DataBase=Forethought;SelectMethod=cursor
    An type-like "access denied" exception is raised when trying to get the connection from the DataSource object with some code similar to :
    DataSource objDS = (DataSource)objCtx.lookup("jdbc/Forethought");
    Connection objConn = ds.getConnection();
    I have realised a CMP to access the database and everything works fine.
    It seems that the SunRI tries to get the db connection with an "impersonated " user even if i have specified the user name and password in the connection string.
    Does anyone have an idea how to force the connection with SQL Server user name and password ??

    I come accorss the same problem too,
    my URL jdbc:microsoft:sqlserver://ambassador:1433;User=sa;Password=123;DatabaseName=pubs
    and the password is right.I can establish connection to SQL server 2000 by JDBC Driver Manager,the code as follow:
    Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
    Connection conn = DriverManager.getConnection
    ("jdbc:microsoft:sqlserver://localhost:1433;User=sa;Password=123");

  • Microsoft JDBC driver for SQL server 2000

    Hi Guys,
    can you share your experiences using the MS-JDBC driver ?
    How it performs and how much is it stable compared to
    other non-free products (e.g DataDirect / I.Net / ...) ?
    Is it, according to you, quite mature to be used in a
    production environment with heavy loads ?
    Many thanks
    Max

    We tried it with websphere and had some problems (I don't recall exactly what they were) but ended up going with IBMs embedded driver for our J2EE project. It seems to work very well, but, of course, you couldn't use it for just a regular java client.

  • Microsoft jdbc driver for sql server 2000 error

    I try to connect to a sql server database;
    After execution of:
    C:\Sun\Creator\bin\runide.exe -cp:a =.;"C:\Programmi\Microsoft SQL Server 2000 Driver for JDBC\lib\msbase.jar";"C:\Programmi\Microsoft SQL Server 2000 Driver for JDBC\lib\msutil.jar";"C:\Programmi\Microsoft SQL Server 2000 Driver for JDBC\lib\mssqlserver.jar"
    (where "programmi" is "Program Files" in Italian)
    I can make a connection to sql server.
    When I try to see the "tables" in database I have this error:
    [Microsoft][SQLServer 2000 Driver for JDBC]Error setting up static cursor cache
    I have tryed to found some resolution and I found only this:
    http://forum.java.sun.com/thread.jsp?thread=444136&forum=48&message=2007122
    Can you see if it apply on source of IDE and eventually correct?

    I'm using the new version and I can't update a row
    satRowSet.setDataSourceName("java:comp/env/jdbc/Northwind");
    satRowSet.setCommand("SELECT * FROM dbo.Sat");
    satModel.setWrappedData(satRowSet);
    satRowSet.setConcurrency(java.sql.ResultSet.CONCUR_UPDATABLE);
    satRowSet.setHoldability(java.sql.ResultSet.HOLD_CURSORS_OVER_COMMIT);
    satRowSet.setAutoCommit(true);
    satRowSet.setReadOnly(false);
    satRowSet.execute();
    satRowSet.next();
    try{
    this.satRowSet.absolute(1);
    this.satRowSet.updateRow();
    } catch (Exception ex) {
    this.textArea1.setValue(ex.getMessage());
    ex.printStackTrace();
    java.sql.SQLException: [Sun][SQLServer JDBC Driver]Invalid operation for the current cursor position.
         at com.sun.sql.jdbc.base.BaseExceptions.createException(Unknown Source)
         at com.sun.sql.jdbc.base.BaseExceptions.getException(Unknown Source)
         at com.sun.sql.jdbc.base.BaseResultSet.validateCursorPosition(Unknown Source)
         at com.sun.sql.jdbc.base.BaseResultSet.getString(Unknown Source)
         at com.sun.sql.rowset.JdbcRowSetXImpl.getString(JdbcRowSetXImpl.java:842)
         at com.sun.sql.rowset.JdbcRowSetXImpl.getString(JdbcRowSetXImpl.java:941)
         at untitled.Page1.setFields(Page1.java:133)
         at untitled.Page1.beforeRenderResponse(Page1.java:147)
         at com.sun.jsfcl.app.FacesBean.beforePhase(FacesBean.java:227)
         at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:192)
         at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)
         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:289)
         at java.security.AccessController.doPrivileged(Native Method)
         at javax.security.auth.Subject.doAsPrivileged(Subject.java:500)
         at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:311)
         at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:205)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:283)
         at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:102)
         at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:192)
         at java.security.AccessController.doPrivileged(Native Method)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:263)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:156)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:569)
         at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:261)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:215)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:156)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:569)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:191)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:156)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:180)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:582)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
         at com.sun.enterprise.webservice.EjbWebServiceValve.invoke(EjbWebServiceValve.java:134)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
         at com.sun.enterprise.security.web.SingleSignOn.invoke(SingleSignOn.java:254)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
         at com.sun.enterprise.web.VirtualServerValve.invoke(VirtualServerValve.java:209)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:569)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:161)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:156)
         at com.sun.enterprise.web.VirtualServerMappingValve.invoke(VirtualServerMappingValve.java:166)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:569)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:979)
         at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:211)
         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:692)
         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:647)
         at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:589)
         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:691)
         at java.lang.Thread.run(Thread.java:534)

  • DB2 and WebSphere: having trouble running the JDBC driver script

    I'm investigating WebSphere Studio Application Developer (WSAD) and want to go through one of their tutorials. They require DB2 7.1, so I installed that. There is a script in the DB2 7.1 distribution that enables the JDBC driver within WSAD. Howver, the script won't run because it says I don't have the correct permissions.
    I'm running all this on Win2K, and my userid has administrator privileges, and I installed both WSAD and DB2 under that userid.
    So, has anybody got WSAD and DB2 to work together? If so, how?
    Thanks much in advance.
    Jane Sokolow
    S1Studio tech writer

    You are suppose to run one of these two batch files:
    C:\Program Files\SQLLIB\java12\usejdbc1.bat
    C:\Program Files\SQLLIB\java12\usejdbc2.bat
    I assume that you need the second one. If you take a look inside of this batch file you'll that it is only simple copy/remove files. You should be able to do those operations with your userid. Perhaps, it is a good ideea to stop either DB2 and WSAD before running this batch file (is trying to remove two files one .dll and another .exe which could be in use ...).

  • Microsoft jdbc driver class not found error

    hello,
    i have installed jdbc driver for 2005 from microsoft. i have put sqljdbc.jar in the classpath as well as in jbuilder 2006 library. still i get the following error.
    java.lang.ClassNotFoundException: com.microsoft.jdbc.sqlserver.SQLServerDriver
    at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:164)
    at dbinfo.dbinfo.getConnection(dbinfo.java:27)
    at dbinfo.dbinfo.displayDbProperties(dbinfo.java:64)
    at dbinfo.dbinfo.main(dbinfo.java:150)
    Error Trace in getConnection() : com.microsoft.jdbc.sqlserver.SQLServerDriver
    Error: No active Connection
    what am i missing?

    i have the same problem can anyone help me in setting the classpath to the drivers. i am new to java plz help me
    thanks in advance

  • Microsoft JDBC Driver deployment error

    Hi there, I have install XI 30 and patched it till SP14, and when I try to deploy the MS JDBC Driver as per SAP instructions, I get an error stating "..same version", but the 3 options below are grayed out, so I can't select the "Update any version" option. What could be the problem?

    Hi,
    You have to select the option on the first screen where you add the SDA file in SDM, right before you press "next" for the first time....
    (Normally the options are hidden in the bottom of the screen, and must be "opened" by pressing the "up arrow" in the bottom right of the SDM screen).
    Regard
    Rolf

  • Java.lang.OutOfMemoryError (Microsoft SQL Server JDBC driver)

    Hi everyone,
    I am getting a java.lang.OutOfMemoryError when performing a simple query to a database. The query produces only one row (and will always produce only one row). However, the statement that produces the second column in the resultset is very long (>256) characters, so could that be it?
    Also, I am executing thousands of SQL statements with no difficulty. I have double-checked that I am cleaning up all of my database resources, so I don't think that this is it. Do I have to do anything else besides closing the statement and resultset?
    There is no stack trace, otherwise I would have posted it :(
    Also, as an aside - is the Microsoft JDBC driver for SQL Server the best one to use? It seems poorly supported and slow at times. Are there any alternatives?
    Thanks for your time :)
    Ben

    It is running after thousands of other queries. I'll test to see what happens if I run it by itself.
    I am closing the connection. In fact, I am running all of these statements over the same connection and simply opening and closing resultsets.
    So a bug in the driver you think?
    Thanks for the reply :)
    Ben

Maybe you are looking for