Type of JDBC Drivers

I use two methods to connect to oracle database.
1. through a JNDI datasouce. that is connect program connect to database through a app/web server.
2. directly from program through a OracleDataSource.
please tell me what type of driver these two are? plz give me a description?
which one is suppose to be better?

hi sree,
Can u send me the Database URL which u mentioned when u r creating the JNDI name web/app server?
For example : Type 4 driver url
"jdbc:oracle:thin:@localhost:1521:orasrv","username","password"
then only its possible to tell which type of driver u r using.
bye.. siva
Message was edited by:
siva_forums

Similar Messages

  • Type 4 jdbc drivers

    hi
    I want to know that weblogic 7 support type 4 jdbc drivers for oracle
    kindly reply me
    Punee jain

    This isn't a JDBC question. It's a weblogic question.
    I'm sure Bea has some documentation on that on their website
    Thomas

  • Good DB2 type 4 jdbc drivers?

    Hi
    Any recommendation on reliable and good DB2 type 4 jdbc drivers. Thanks
    Jia

    Hi Pat,
    We are using jt400.jar to connect to our AS/400 systems.
    I hope you might have seen , how to configure JDBC drivers document.
    In Communication channel you have to use :
    jdbc:as400://servername/
    Thanks,
    raj.

  • Any suggestions for type 4 JDBC drivers for MSSQL

    I am currently using odbc-jdbc bridge for MSSQL 7.0 and I am considerring using a Type 4 driver so that my app can be ported anywhere. Any sugesstion for a FREE type4 JDBC driver for MSSQL 7.0 ??
    I have heard microsoft has released one for MSSQL 2K but I am not sure if it can be used with 7.0.

    you can check that at :
    http://industry.java.sun.com/products/jdbc/drivers

  • Weblogic 8.1 Type 4 JDBC Drivers for Sybase

    Hi Everyone,
    I get the following exception when I switch from the Sybase JConnect driver to the Weblogic type 4 driver. The exception disappears when I remove the "sdaahadr.." from the stored procedure call. However, the stored procedure executes a raiserror which does not come back to the java code. So there are actually 2 problems.
    Any help would be appreciated.
    Thanks,
    Eddie Baue
    [BEA][Sybase JDBC Driver]The stored procedure call could not be made as a language event, due to the presence of one or more output-only parameters. It is recommended that parameter markers be used for all stored procedure arguments.
    The code follows:
    Driver sybase_driver =
    (Driver)Class.forName("weblogic.jdbc.sybase.SybaseDriver").newInstance();
    Properties prop = new Properties();
    prop.put("DatabaseName", "***");
    prop.setProperty("User","***");
    prop.setProperty("Password","***");
    prop.setProperty("SelectMethod","cursor");
    conn = sybase_driver.connect("jdbc:bea:sybase://xsd00z09:3035", prop);
    String sql = "{call sdaahadr..pr_adr_wh_get_issuer_name (?, ?, ?, ?)}";
    long issuer_id = 753211710;
    Statement stmt = null;
    ResultSet rs = null;
    CallableStatement call_stmt = null;
    call_stmt = conn.prepareCall(sql);
    call_stmt.setLong(1, issuer_id);
    call_stmt.registerOutParameter(2, Types.VARCHAR);
    call_stmt.registerOutParameter(3, Types.VARCHAR);
    call_stmt.registerOutParameter(4, Types.VARCHAR);
    call_stmt.execute();

    Chandra Sekhar Ghosh Dastidar wrote:
    I am having similar problem with SQL Server 2000 on WL 8.1 SP3, which does not recognise RAISERROR thrown from the Stored Procedure.
    Any help in this regard?
    Do I need to pass error code through the OUT parameter?Hi. Could you show me the procedure and the jdbc code to process it?
    thanks
    Joe

  • [WebLogic Sybase Type 4 JDBC Drivers] set ANSINULL off

    Hi,
    I am having some issues with the Weblogic JDBC Driver for sybase and the ANSINULL functionality.
    It appears that the stored procedures from a third party whose system we are trying to integrate with do ot function properly due to the fact that Weblogic will turn the ANSINULL handelling on.
    I have been reading that we need to run the command 'set ANSINULL off' before we run the stored procedure. Only problem is that the stored procedure is wrapped up in the Spring framework and I see no oppotunity to run this.
    Also readin I've found that the DataDirect connector for Sybase will accept in the URL a string 'InitializationString=set ANSINULL off;' I have tried to set this and it appears to make no difference to the result.
    So I was wondering if this InitializationString works with the weblogic driver?
    Or is there another way I can globaly set ANSINULL off for the Sybase connection. (we also have a number of Oracle connections that are working fine)
    Thanks in advance for any advice
    IV

    Ian Vellosa wrote:
    Hi,
    I am having some issues with the Weblogic JDBC Driver for sybase and the ANSINULL functionality.
    It appears that the stored procedures from a third party whose system we are trying to integrate with do ot function properly due to the fact that Weblogic will turn the ANSINULL handelling on.
    I have been reading that we need to run the command 'set ANSINULL off' before we run the stored procedure. Only problem is that the stored procedure is wrapped up in the Spring framework and I see no oppotunity to run this.
    Also readin I've found that the DataDirect connector for Sybase will accept in the URL a string 'InitializationString=set ANSINULL off;' I have tried to set this and it appears to make no difference to the result.
    So I was wondering if this InitializationString works with the weblogic driver?
    Or is there another way I can globaly set ANSINULL off for the Sybase connection. (we also have a number of Oracle connections that are working fine)
    Thanks in advance for any advice
    IVHi. What version of WebLogic? IN recent ones we have a pool property 'initSQL'
    which you can set. We will run whatever SQL you give, on every pool connection
    when it is created. That would do it.

  • StatementTimeout support for  WebLogic Type 4 JDBC Drivers for Sybase

    All,
    I am using the StatementTimeout property to limit the statement processing time for my data source.
    It seems to be working for all other connection pools except Sybase.
    The property documentation lists that it depends on support by underlying Driver.
    Please confirm if the StatementTimeout prperty is supported by BEA's Type 4 Sybase Driver. In am using WLS 10.3
    Thanks
    Edited by: Sudheer Prabhala on Aug 30, 2012 2:39 AM

    Yes. file a support request with Oracle.

  • Differences between type -1,type-2,type-3,type-4 jdbc drivers ?

    in what situations they will use?

    Try google
    Here are a couple of answers
    http://www.geekinterview.com/question_details/17263
    http://en.wikipedia.org/wiki/JDBC_type_2_driver
    rykk

  • When I get a date field value using the Oracle thin (type 4) JDBC driver...

    ....in 'DD-MMM-YY' format from an Oracle 8i database and pass it in to the java.util.Date() constructor, I get a IllegalArgumentException. This error doesn't occur when I use the type 2 driver, so it is apparently a driver-specific thing. It happens on both Win32 and Linux.
    Has anyone seen this before? Is there a newer version of the Oracle thin (i.e., type 4) driver than is listed here?
    http://web77-02.us.oracle.com/software/tech/java/sqlj_jdbc/content.html
    Thanks,
    Tom
    [email protected]

    Yup, that original post didn't make much sense, did it? Let's try again.
    I've got an EJB app that runs on WebLogic 6.0 (on Solaris in production, on Win2K for development) and accesses an Oracle 8i database. This app currently uses the Oracle type 2 JDBC drivers. All is well.
    So I wanted to see how it would run on Linux. I've got a Redhat 7.1 box handy, so I installed the JDK and WL6.0 and slapped the ear file on there. Problem! Can't deploy because there are no Oracle drivers on this machine!
    Makes sense. So I started looking around, and it seems installing Oracle on a RH 7.1 box involves patching glibc and other such nastiness. So let's just try the type 4 JDBC driver - no glibc patch, no shared object libraries, just good 'ol pure Java talking to Oracle on port 1521.
    Once I had the URLs and whatnot set up, the app connected to the DB just fine, created the connection pool, read some data, etc. But when my app read a date from the DB and instantiates a new java.util.Date object, I got an IllegalArgumentException - i.e., the date can't be parsed.
    "Hmm... that's odd", I thought, so back I went to my trusty Win2K machine, modified my configuration files to use the type 4 driver and - same error! So I switched back to the type 2 driver - and everything works fine, Dates and all. Hmmm.....
    As you correctly state, that Date constructor is deprecated and I should use DateFormats and GregorianCalendars and whatnot instead.
    But has anyone seen this weird behavior before - code that works fine on a type 2 driver starts throwing exceptions when used with a type 4 driver? Anyone have any solutions?
    Thanks much,
    Tom

  • Free jdbc drivers type 3 or type 4

    are there any (totally)free jdbc drivers(type 3 or 4) for MsAccess out there?

    are there any (totally)free jdbc drivers(type 3 or 4)
    for MsAccess out there?There can't be any type 4. MS Access doesn't work like that.
    Basically any proxy driver would seem to be a type 3 - so RmiJdbc is one....
    http://solutions.objectweb.org/#database

  • 3rd Party Access 2000 JDBC Drivers

    Wondering if anyone can recommend or rate any 3rd party MS Access JDBC drivers - I am running an app using Tomcat 4.0.2, on Windows 2K, currently using the JDBC/ODBC bridge from Sun, looking for something a little more specific and reliable for my app - company willing to spend the $$ to get something good.
    Thanks!
    Geoff

    hi Geoff ,
    I would recommend you the aveconnect driver from Atinav. It is a type 3 driver, and is a reliable and nice implementation. We have been using it for quite some time now and our developers here have seen it to be quite efficient and good.
    this url may help you..
    http://www.atinav.com/products/aveconnect/MSAccess.htm
    they provide a 30 day trial, and was worth a buy..
    hope that helps,
    -Jer

  • Difference between Oracle9i 9.2.0.3 and Oracle9i 9.2.0.4 JDBC Drivers

    Hi everybody,
    Can you tell me what is Difference between Oracle9i 9.2.0.3 and Oracle9i 9.2.0.4 JDBC Drivers briefly?
    In my application I am using Oracle9i 9.2.0.3 JDBC Drivers. But it is not supported when I retrieved Data with junk character from CLOB.because of IO Exception it showing Bigger type length than Maximum
    if i used Oracle9i 9.2.0.4 JDBC Drivers it is working properly.
    I am using WAS 4.0.3 , JDK1.3 and Oracle 9.0.
    Shall I use Oracle9i 9.2.0.4 in my application and I want to know it will create any new problem in my application or not ?
    please Reply me ASAP.
    i am waiting for your reply
    thanks a lot
    bye
    Message was edited by:
    paulusazapakcom

    Can you tell me what is Difference between Oracle9i
    9.2.0.3 and Oracle9i 9.2.0.4 JDBC Drivers briefly?Search the Oracle site. That should tell if there are any differences at all. I would assume that there would be some bug fixes.
    please Reply me ASAP.
    i am waiting for your replySuch lines are better avoided.

  • Oracle.sql.* with JDBC drivers 8.0.5

    the oracle.sql package is not included in my JDBC driver file classes111.zip given for oracle data server version 8.0.5.
    I would like to use the oracle STRUCT and ARRAY type for calling PL/SQL stored procedures taking STRUCT objects in arguments.
    Are the JDBC drivers 8.1.* compatible with the oracle data server 8.0.5 (if I only use the STRUCT or ARRAY types)? Is it a way for passing ARRAY of VARCHAR2 values to PL/SQL stored procedure with the oracle 8.0.5 JDBC driver?
    thanks

    Unfortunately, these classes (oracle.sql.STRUCT and oracle.sql.ARRAY) are not compatible to 8.0 database. There is server format changes between 8.1 and 8.0, and JDBC driver only supports the 8.1 format.
    Please upgrade your database to 8i.

  • Oracle JDBC Drivers

    We are extracting blobs from an 8.05 database. The following statement works only with an older driver for a version I'm not sure whar it is(size is 1419KB, date is 11/3/00 at 9:25AM).
    Nothing special in the sql just extracting the column.
    pBlob = (oracle.sql.BLOB)rset.getObject(1);
    This works fine with the above mentioned driver. All other drivers I have tested 8.15 for 8i, 8.05, 7.34, 8.04, etc. all give the network datatype unsupported error at this statement. I tried the various examples but they were for the oci8 drivers and did not work with thin.
    We use the thin(type 4) driver.
    Do the new drivers not support the BLOB type for thin?
    Does anyone know which driver version and database that the one I described is from?
    Thanks.

    user452131,
    Yes, there are differences between the Oracle 8i JDBC drivers and the Oracle 9i JDBC drivers.
    If you haven't already done so, I suggest perusing the following Web page:
    http://www.oracle.com/technology/tech/java/sqlj_jdbc/index.html
    Good Luck,
    Avi.

  • JDBC Drivers compatability between Oracle and IBM WSAD 5.1.1

    I am using a DataAccessObject pattern. I discovered you can speed up your procesing with SELECT statments us using an OraclePreparedStatment and setting defineColumnType; thereby reducing the number of trips the SQL is sent to the database.
    Here is the code:
    ((OraclePreparedStatement)ps).defineColumnType(1, Types.BIGINT);'ps' is a PreparedStatement.
    However, at runtime, I am getting a class cast exception for the below reason. I am using WASD version 5.1.1. I was not aware IBM was using any specific classes in the JDBC drivers.
    [2005-05-23 15:36:59,855][Servlet.Engine.Transports : 2][ERROR][{TDAO}{getTWebInfos}{APP0000}{Unknown Contained Application Exception}{External Message:com/ibm/ws/rsadapter/jdbc/WSJdbcPreparedStatement incompatible with oracle/jdbc/OraclePreparedStatement}]
    {TDAO}{getTWebInfos}{APP0000}{Unknown Contained Application Exception}{External Message:com/ibm/ws/rsadapter/jdbc/WSJdbcPreparedStatement incompatible with oracle/jdbc/OraclePreparedStatement}
         at java.lang.Throwable.(Throwable.java)Could someone please explain this to me? Any help would be greatly appreciated.

    I'm not an WSAD expert to be honest, but it's quite possible they are using their own wrappers. Check out what calls you can make on their ps wrapper or more likely conn wrapper - they may have some type of getWrappedConnection functionality as other vendor(s) do in which case you can, eg, cast the connection to OracleConnection and go from there.

Maybe you are looking for