JDBC 4.0 and ojdbc14.jar

Hello everyone
i need to know abt jdbc-4.0 api tutorial and abt ojdbc14.jar tutorial which one is better ojdbc or classes12
Thanks

ojdbc14.jar is for JDK 1.4 or higher. classes12.zip
is for JDK 1.2 and 1.3.
http://www.oracle.com/technology/software/tech/java/sq
lj_jdbc/htdocs/jdbc9201.htmlYes, although only the latest version of ojdbc14.jar (10gR2, or 10.2.0.1.0) is Oracle-approved-and-supported for Java 1.5. That doesn't mean older versions don't work with newer Java, they do, at least mostly, but Oracle does not certify-and-support them. In fact, I know that the last 8.1.7 version of classes12 works very well with Java 1.4 and an 8.1.7 DB (at lease for the driver functions my company happens to use, we're pretty "plain vanilla" on that project).
For new code, you should probably be using the latest ojdbc14.jar, unless you're using an antique version of Java.

Similar Messages

  • Xdb.jar and ojdbc14.jar incompatibility ( XMLType.createXML() ) ??

    I am using the latest xdb.jar (from xdk_java_9_2_0_5_0.zip) and ojdbc14.jar
    and it appears that xdb.jar calls a method that does not exist in ojdbc14.jar.
    It happens when executing
    OPAQUE opaque = rset.getOPAQUE("value");
    XMLType xt = XMLType.createXML(opaque); // <-- here
    The exact error message is:
    java.lang.NoSuchMethodError: oracle.jdbc.internal.OracleConnection.getProtocolType()Ljava/lang/String;
         at oracle.xdb.XMLType.initConn(XMLType.java:2072)
         at oracle.xdb.XMLType.<init>(XMLType.java:903)
         at oracle.xdb.XMLType.createXML(XMLType.java:493)

    Hi,
    There are known problems with xdb.jat that is bundled with XDK 9205.
    As a workaround, you need to use an older version of xdb.jar from either XDK-9.2.0.3 or XDK-9.2.0.4 since the mentioned exception is generally thrown due to problems in xdb.jar that comes with XDK-9205.
    If you do not have any of these versions of XDK, you could use the xdb.jar that comes with the database 9.2.0.3. The xdb.jar is present in <oracle_home>/rdbms/jlib folder.
    Hope that helps.
    Shefali

  • Usage of java.sql.Timestamp with classes12.zip and ojdbc14.jar  ?

    Hi all,
    If i'm using java.sql.Timestamp with classes12 it is functioning perfectly,
    if i'm using ojdbc14 and java.sql.Timestamp it is functioning in different way and failing to do the action..
    Example : update set xxx=yy where time = my Timestamp object set in Prepared statement
    Hope to see the answer

    http://forum.java.sun.com/thread.jspa?threadID=460615&messageID=2116517
    Timestamp insert problem
    Using the "classes12.zip" file that comes with the distribution for Oracle versions 8.1.6.x and 8.1.7.x, Oracle's DATE datatype is mapped to the "java.sql.Timestamp" class. However, the "ojdbc14.jar" driver maps DATE to "java.sql.Date", and "java.sql.Date" only holds a date (without a time), whereas "java.sql.Timestamp" holds both a date and a time.

  • Oracle jdbc driver class and classes12.jar whether deprecated.?

    Hi All,
    1. In one of the post, it has been told that oracle.jdbc.driver.OracleDriver will be deprecated and also recommended to used oracle.jdbc.OracleDriver.
    According to that post, I changed the driver class name in my code as below:
    Class.forName("oracle.jdbc.OracleDriver");
    Then to check the driver name, I insert the below code:
    Enumeration<Driver> driverEnum = DriverManager.getDrivers();
    +while (driverEnum.hasMoreElements()){+
    System.out.println("driver : "driverEnum.nextElement());+
    +}+
    Below is the output:
    driver : oracle.jdbc.driver.OracleDriver@addbf1
    Even after specifying the driver class name to be used as oracle.jdbc.OracleDriver, why it is taking oracle.jdbc.driver.OracleDriver..?
    INFO : The Oracle JDBC Driver (classes12.jar) version is 10.2.0.4.0.
    2. We are using classes12.jar for developing all JDBC code. In Oracle Database 11g Release 2 (11.2.0.2.0) JDBC Drivers, there is no classes12.jar. Is this deprecated? Which jar can be used instead of classes12.jar?
    Thanks in advance.

    In Oracle Database 11g Release 2 (11.2.0.2.0) JDBC Drivers, there is no classes12.jar. Is this deprecated? Which jar can be used instead of classes12.jar?For JDBC 4.0 features ojdbc6.jar with JDK 6.0.
    For JDBC 3.0 support ojdbc 5.jar with JDK 5.0
    http://www.oracle.com/technetwork/database/enterprise-edition/jdbc-112010-090769.html

  • How to use both ojdbc14.jar and ojdbc6.jar in same weblogic domain(weblogic12C)

    Hi all,
    I 'm having issue of using both ojdbc14.jar and ojdbc6.jar in same weblogic application and same weblogic domain in weblogic 12C environment.
    how can i do that?
    i'm currently having application developed using jdk 1.6 and ojdbc6.jar, application developed using jdk 1.4 and ojdbc14.jar.both are currently installed at same domain.
    i want to use the both ojdbc14.jar and ojdbc6.jar in same domain.
    what i previously did was renaming /usr/weblogic/wls_server10.3.4/lib/ojdbc6.jar to /usr/weblogic/wls_server10.3.4/lib/ojdbc6.jar.bak and put ojdbc14.jar in the same path when i wanna use ojdbc14.jar.
    i haven't use both in same environment before, but to go live i wanna match about requirement.pls help.
    i know the way use this by having two domains, but in the same domain i could not find a solution yet.
    Please help

    Hey
    I have the similar requirement.. Did you managed to get an option of doing it? If yes, please provide some insights
    Thanks in Advance

  • Error using setTimestamp and ojdbc14 against Oracle 7.3.4

    I am having a problem setting a timestamp value against Oracle 7.3.4 and Oracle 8.0.6 databases.
    Here's the code:
    public Tester
    (String passedUsername, String passedPassword, String passedHostName, String passedPort, String passedSID)
    throws SQLException {
    // Establish a database connection
    try {
    Class.forName("oracle.jdbc.driver.OracleDriver");
    } catch (ClassNotFoundException e) { throw new SQLException("Can't find class oracle.jdbc.driver.OracleDriver"); }
    StringBuffer myStringBuffer = new StringBuffer(50);
    myStringBuffer.append("jdbc:oracle:thin:@");
    myStringBuffer.append(passedHostName);
    myStringBuffer.append(":");
    myStringBuffer.append(passedPort);
    myStringBuffer.append(":");
    myStringBuffer.append(passedSID);
    Connection myConnection = DriverManager.getConnection(myStringBuffer.toString(), passedUsername, passedPassword);
    myConnection.setAutoCommit(false);
    // Insert the test record
    PreparedStatement myPreparedStatement = null;
    try {
    myPreparedStatement = myConnection.prepareStatement("insert into test_table(date_field) values (?)");
    myPreparedStatement.setTimestamp(1, new Timestamp(System.currentTimeMillis()));
    myPreparedStatement.execute();
    } finally {
    if (myPreparedStatement != null) myPreparedStatement.close();
    Here's the error that occurs under Oracle 7.3.4:
    java.sql.SQLException: ORA-01024: invalid datatype in OCI call
         at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
         at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:289)
         at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:573)
         at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1891)
         at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:1093)
         at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:2047)
         at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1940)
         at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2709)
         at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:589)
         at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:656)
         at Tester.<init>(Tester.java:46)
         at Tester.main(Tester.java:62)
    Here's the error that occurs under Oracle 8.0.6:
    java.sql.SQLException: ORA-03115: unsupported network datatype or representation
         at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
         at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:289)
         at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:573)
         at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1891)
         at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:1093)
         at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:2047)
         at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1940)
         at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2709)
         at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:589)
         at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:656)
         at Tester.<init>(Tester.java:46)
         at Tester.main(Tester.java:62)
    Note that the table in the insert statement does not have to exist. You can even replace the statement with a garbage statement.
    The error is produced regardless.
    The code is being compiled under JDK 1.4
    I am using the latest version of the JDBC drivers (i.e. ojdbc14.jar)
    The code works fine under Oracle 8.1.7 and 9.0.1
    My code needs to access all four of these database version, sometimes concurrently, so I can only use a single driver class (i.e. I can't swap out ojdbc14.jar for classes12.zip).
    Any feedback would be appreciated!

    Hi,
    Only to say that we have the same problem like you:
    - Error ORA-01024 when connection to Oracle 8.0.1 on Sun Solaris
    - Error ORA-03115 when connection to Oracle 8.1.5 on Windows
    We are thinking about upgrading Oracle. Is it the only solution?
    Thank you

  • Oracle JDBC driver 10g and xMII

    I have a BLS that tries inserting CLOB data into Oracle 10g database. Since Oracle 8 JDBC driver does not support that (I saw other SDN messages on the same issue), I have download and copied Oracle JDBC driver for 10g
    ojdbc14.jar to
    C:\ServletExec AS\se-xMII\webapps\default\Lighthammer\WEB-INF\lib
    folder
    I restarted Servlet exec engine and I'm still seeing the same error
    that the value to be inserted is too large ( I'm inserting more than
    4000 characters but much lesser than 4 GB which CLOB column can take)
    1. I want to understand if there is something else that I need to
    change in order for xMII to pickup the new driver.
    2. Also, should I add it classpath?
    3. Looking at some Oracle notes on using capability of 10g driver for
    manipulating large data, the property SetBigStringTryClob=true should
    be set. I saw examples of some non-xMII applications setting it in their
    servers.xml. Similarly, in which file can I set this property in xMII
    to force the driver to use this feature?
    Is ServerDefaults.xml under C:\Lighthammer\Illuminator\SysConf the
    right place? Since it is not recommended to modify the configuration
    files manually rather than using admin console, I'm not sure on this
    one.
    Let me know
    Thanks

    Are you really sure this "SetBig.." thing is the solution?
    Searching for the ORA error you posted results in quite a few solutions in the way you write your SQL statement.
    Maybe changing your statement might help.
    If you don't mind can you post the SQL statement?
    Another good test would be to see if the SQL statement goes through without any errors when used from a different SQL editor.I would suggest do that first if you haven't already.

  • Ojdbc14.jar connect to 10g so slow with JRE1.5.0_05

    Our guests complained the speed is so slow that they can not stand up with this...
    So I run the tests base on JRE1.5.0_05 and ojdbc14.jar and Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
    try {
                        Class.forName("oracle.jdbc.driver.OracleDriver");
                        String url = "jdbc:oracle:thin:@//host:1521/orcl";
                        Date now = new Date();
                        Connection conn = DriverManager.getConnection(url, "user",
                                  "password");
                        System.out.println(System.currentTimeMillis() - now.getTime());
                        conn.setAutoCommit(false);
                        Statement stmt = conn.createStatement();
                        ResultSet rset = stmt
                                  .executeQuery("select BANNER from SYS.V_$VERSION");
                        while (rset.next()) {
                             System.out.println(rset.getString(1));
                        stmt.close();
                        System.out.println("Ok.");
                   } catch (Exception ex) {
                        ex.printStackTrace();
    The output is :
    4875
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
    PL/SQL Release 10.2.0.1.0 - Production
    CORE     10.2.0.1.0     Production
    TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
    NLSRTL Version 10.2.0.1.0 - Production
    Ok.
    the statement Connection conn = DriverManager.getConnection(url, "user", "password") execution time is 4875 milliseconds!!!!!
    so i switched to 9i the output is:
    0
    Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
    PL/SQL Release 9.2.0.1.0 - Production
    CORE     9.2.0.1.0     Production
    TNS for 32-bit Windows: Version 9.2.0.1.0 - Production
    NLSRTL Version 9.2.0.1.0 - Production
    Ok.
    I change the JDK version to 1.4 or 1.6 the execution time is also 0.
    I walk through the internet and finally found the solution:
    ProxySelector.setDefault(null);
    But i am still confused when it come to the same environment the same code to connect to the 9i,10g, the getConnection() method execution time is so different without the statement ProxySelector.setDefault(null). so I suspect that this is an issue to 10g not the JDK1.5.x.
    Edited by: user12084131 on 2010-9-20 上午1:46
    Edited by: user12084131 on 2010-9-20 上午1:47

    Thanks for the reply,
    One correction to the above <Corrected now in my original post>
    Its connecting to " com.bea:ServerRuntime=managed03,Name=managed03,Type=JRockitRuntime"
    Tried with previous version again, it works perfect. But i still have issue with new JRE version.
    Regards,
    Rana
    Edited by: user13387204 on 02-Oct-2010 19:01

  • Ojdbc6.jar ojdbc14.jar anamoly and a bug

    PROGRAM
    PreparedStatement ps = connection.prepareStatement( "select dob from pers", ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_UPDATABLE);
    ResultSet.getString("dob");
    Output:
    ojdbc14.jar:
    *6/1/2012 0:0:0*
    ojdbc6.jar:
    *2001-06-01 00:00:00*
    Why the difference? Is this a bug? Is there a fix? I require ojdbc6 output to be the same as ojdbc14. How can I achieve that? (Yes, I know its good to use ResultSet.getDate(...) instead of ResultSet.getString(...) etc etc but this is legacy code and there are too many occurrences for me to change all of them.)
    Edited by: 935389 on May 18, 2012 3:51 PM

    1. Get a Timestamp instead of a string.
    2. Format the string in SQL and stop relying on the JDBC to do it.I quote again from my first post,
    (Yes, I know its good to use ResultSet.getDate(...) instead of ResultSet.getString(...) etc etc but this is legacy code and there are too many occurrences for me to change all of them.)
    No. Both values are correct they are just formatted differently. And the spec says nothing about how it formats strings.Java ResultSet API does not say anything about the format but this was not caused by Java6. It was ojdbc6.jar.
    Also, the result is the same if I don't use,
    ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_UPDATABLEIt is not good to simply change format even though Oracle JDBC didn't specify any format either. Does this mean I'll have to test everything that is not specified in their spec? It is a bug.
    Edited by: 935389 on May 20, 2012 5:21 PM

  • Which ojdbc14.jar JDBC driver to use for Oracle 10g database

    When ODI is installed there seems to be an Oralce JDBC driver in place in the drivers folder (ojdbc14.jar).
    When we connect to an Oracle datastore and point to a table and use the 'reverse' function to populate the columns - it sort of works OK but does not bring back the datatypes properly. This is found to be when the Oracle table has UNICODE character datatypes NCHAR and NVARCHAR. If a table has CHAR and VARCHAR it is all OK but any table that has UNICODE datatyoe has a problem.
    Is this likely to be the JDBC driver ?
    We have tried replacing this ojdbc14.jar with the older classes12 and this, as expected, did not resolve the issue.
    We then tried replacing it with the latest 10.2.0.4 ojdbc14.jar but again no difference.
    Does anyone have any experience with Oracle JDBC drivers and what release level to use - and using against UNICODE datatypes in tables ?
    Regards

    Our problem is that when we use 'reverse' to populate the columns from a physicla table in an Oracle database - ODI is obviously 'seeing' the ORacle table and is correctly understanding the columns in the table and defining them in it's model - but wherever there is a column with a datatype in the ORacle database of NCHAR or NVARCHAR it fails to populate the datatype or the 'length' of these columns. If I manually try to specify the datatype these 2 unicode data types do NOT exist in the pull down list of datatypes.
    I see what you are asking - if these datatypes are actually defined as datatypes within the actual technology - I cant access my lab right now but will check as soon as I can. Thanks for the suggestion.

  • Pointing portal server from classes12.jar to ojdbc14.jar JDBC driver

    Hi,
         Some time ago we upgraded our portal landscape from Oracle 9.2.0.7 to Oracle 10.2.0.2. Using OSS Notes 867176 and 915079, we pointed our portal servers to use the newer and recommended ojdbc14.jar driver. This included using Config manager to  change the rdbms.driverLocation parameter to point to the new driver.
         A few months later (last week), thinking that we had our bases covered, we removed the old ORACLE_HOME, /oracle/<SID>/920_32. Upon restarting the portal we got quite a shock- it would NOT come up! The first problem was the bootstrap.properties in the /usr/sap/<SID>/JC00/j2ee/cluster/bootstrap directory which had the same dbms.driverLocation parameter pointed to the old driver in the old ORACLE_HOME. After correcting this, we ran into further problems with neither the dispatcher or the servers (2 per system) coming up. Find this curious, we ran the following unix  commands and identified more *.properties files with the same rdbms.driverLocation parameter-
    cd /usr/sap/<SID>/JC00/j2ee
    find . -name '*.properties' -exec grep -H 920_32 {} \;
    ./deploying/rdb.properties -
                rdbms.driverLocation=/usr/sap/EPP/JC00/j2ee/classes12.jar
    ./cluster/server0/cfg/kernel/ConfigurationManager.properties -
                rdbms.driverLocation=/usr/sap/EPP/JC00/j2ee/classes12.jar
    ./cluster/server0/cfg/kernel/ConfigurationManager.properties -
                rdbms.driverLocation=/usr/sap/EPP/JC00/j2ee/classes12.jar
    ./cluster/dispatcher/cfg/kernel/ConfigurationManager.properties -
                rdbms.driverLocation=/usr/sap/EPP/JC00/j2ee/classes12.jar
    ./templateconfigurator.properties -
               $=/usr/sap/EPP/JC00/j2ee/classes12.jar
    We then proceeded to manually edit each of the files to use the newer ojdbc14.jar driver. Surprisingly, it turns out that editing the ConfigurationManager properties files for the 2 servers and the dispatcher had no effect- upon recycling the portal the entire cfg/kernel directory gets wiped out and replaced.
    So what's the problem here? I don't have an issue with directories being recreated- but why is the ojdbc14.jar driver setting not being picked up from the change made for each server and dispatcher in the Configuration Manager?   I have examined all the services listed in the Configuration Manager and the Visual Administrator and can find no more references to the old ORACLE_HOME.
    Oh, incidently, curiously enough, for single portal systems, the JDBC driver is obtained from the /oracle/<SID>/102_64/jdbc/lib directory and not from the /usr/sap/<SID>/JC00/j2ee directory which is the case for portal servers involving more than 1 server.
    Hoping for help here ...
    Sincerely,
    Steven McElwee, Duke University

    right click ur project and select properties. In Java Build Path add the ojdbc14.jar in the librariies tab.
    http://www.oracle.com/technology/tech/java/sqlj_jdbc/htdocs/jdbc_faq.html
    Edited by: user7361177 on Aug 1, 2009 10:19 PM

  • Stored Proc output being truncated with latest ojdbc14 and classes12.jar

    Hello,
    I downloaded the latest ojdbc14.jar from Oracle website and used it with my Java program. I noticed a peculiar behavior. If my stored proc is returning a VARCHAR with large number of characters, the output is being truncated. This worked fine with the older ojdbc14.jar (and the older classes12.jar). It does not work properly with the new ojdbc14 and classes12.jar. Is there something that I am missing here?
    My Oracle Server version is - Oracle Database 10g Enterprise Edition Release 10.2.0.1.0.
    Below is the sample stored proc and the Java file to execute the same.
    Am I missing something here?
    CREATE OR REPLACE PROCEDURE TestOracleDriver (returnVal OUT VARCHAR2) IS
    BEGIN
    returnVal := '';
    FOR tmpVar in 1..2000
    Loop
              returnVal := returnVal || to_char(tmpVar) || ',';          
    END LOOP;
    END;
    import java.sql.*;
    import java.util.*;
    import java.util.Hashtable;
    import oracle.jdbc.driver.OracleTypes;
    public class OracleDriverTest
         public static void main(String argv[]) throws Exception
              Connection c = null;
              try
                   Driver dr = new oracle.jdbc.OracleDriver();
                   Properties props = new Properties();
                   props.put("user", "scott");
                   props.put("password", "tiger");
                   c = dr.connect("jdbc:oracle:thin:@SERVER_NAME:PORT:SID", props);
                   System.out.println("GOT A PLAIN CON" );
                   System.out.println("The driver is " + c.getMetaData().getDriverVersion() );
                   System.out.println("The DBMS is " + c.getMetaData().getDatabaseProductVersion() );
                   execute(c);
              catch (Exception e)
              e.printStackTrace();
              finally { try {c.close();} catch (Exception ign){} }
         private static String execute(Connection connection )
                   String procName = "TestOracleDriver";
                   CallableStatement cstmt=null;
                   ResultSet rs = null;
                   String returnedData = null;
                   try
                        cstmt = connection.prepareCall("{call " + procName+" (?)}");
                        cstmt.registerOutParameter(1,OracleTypes.VARCHAR);
                        cstmt.execute();
                        returnedData = cstmt.getString(1);
                        System.out.println("ProcTest ::execute --> Returned data is \n"+ returnedData);
                        return returnedData;
              catch (Exception e) {
                   System.out.println("ProcTest ::execute -->Error while executing "+procName);
                   e.printStackTrace();
                   return null;
              finally
                   try
                        connection.close();
                   catch (Exception e1)
                        System.out.println("ProcTest ::execute -->Error while closing connection ");
                             e1.printStackTrace();
                   }//end of catch
         }//end of finally
    }//End of execute method
    Regards,
    Hari
    Message was edited by:
    user553601
    Message was edited by:
    user553601

    Hari,
    If you think it is a bug, you can report it to Oracle Support via the MetaLink Web site.
    Good Luck,
    Avi.

  • Ojdbc14.jar API and Oracle Database Version

    Hi
    Im using ojdbc14.jar for accessing an oracle 10G database.
    Im trying to troubleshoot an exception -
    java.sql.SQLException: Parameter Type Conflict
    that seems to get thrown by the method -
    OraclePreparedStatament.processCompletedBindRow
    I have a couple of questions:
    1. Is the documentation/source available for ojdbc14.jar in order that I can try and find out what this method is supposed to be doing?
    2. Also, can anyone confirm if the jar Im using is the correct version of drivers for accessing a 10G database?
    3. When I go to the JDBC support center at Oracle(http://www.oracle.com/technology/docs/tech/java/sqlj_jdbc/index.html) any support documentation/APIs refer only to the Oracle db version and dont mention Java versions. Im using ojdbc14.jar which I guess is for use with Java version 1.4 onwards - how does this relate to the Oracle database versions?
    Thnaks very much in advance to anyone who can give me any suggestions on the above. This issue has stumped me for days now. Ive checked and double checked my code, and the Oracle Java types I have generated from the database, and they all seem to be fine.
    Jon

    unzip it, and look at the MANIFEST.MF file in META-INF
    If you do not know the version, you can just download appropriate one from oracle site.
    http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html

  • Differenece between ojdbc14-10.2.0.2 jar and ojdbc14

    Hi as i open ojdbc14-10.2.0.2 jar i find packages - core, jdbc,jpub,net,security,sql.
    and in ojdbc14.jar i find an extra package gss...
    whats the main difference between this 2 jars...

    Ok i got some solution for this....
    ojdbc14.jar has a OracleConnection class which has methos as prepareCall..etc
    This methods are depricated in ojdbc14-10.2.0.2 jar
    so be clear not to practice connections done by using ..... class12.jar

  • Is ojdbc14.jar the correct driver to use with Java 1.6.0 and Oracle 10?

    I have a customer using Oracle 10.2.0.3 and a JVM of 1.6.0. They are using ojdbc14.jar as their JDBC driver. I am confused because while ojdbc14.jar is listed as the driver for Oracle 10.2.0.3, it is not listed as compatible with JDK1.6.

    the 14 part means it is for Java 1.4. You should use a driver from either the ODJBC5 (Java 5) or OJDBC6 range (Java 6). All drivers are backwards compatible, so you can use the latest drivers to connect with older Oracle releases. Just don't assume that the latest one is the best one, check Google for specific problems before using a specific driver release.

Maybe you are looking for

  • Crack on display.

    my new ibook g4 display is dead.. I am consideringo on buyig an used g3 display for replacing mine. can anyone tell me if this is possible??? has anyone done it before?

  • Dynamically passing the values to search help

    hi can I pass some values dynamically to search help input field. If I select a profit centre value from a drop down in separate field it should reflect the corresponding values in search help which is cost centre input field ( i/p fields is in a col

  • Get error message when trying to display page or site in any browser...

    Problem signature:   Problem Event Name:    APPCRASH   Application Name:    Muse.exe   Application Version:    2014.3.0.1176   Application Timestamp:    54d3f16d   Fault Module Name:    KERNELBASE.dll   Fault Module Version:    6.3.9600.17278   Fault

  • Multiple Libraries Sync With iPad... Not Happening

    I have, for the past few years, successfully managed 2 different libraries, one for music, one for movies. I have a classic 160, and 3 iPod touch models (3 kids...) all can take music from the 1st library and movies from the second... but not the iPa

  • Recommended Requirements for Development Environment

    Hello, what are recomended requirements for development enviroment for WebCenter. We intend to have JDeveloper and WebLogic server with WebCenter on our developer machines and we are wondering wht would be appripriate hardwer to run all of this smoot