Netbeans and JDBC drivers

try {
        String driver = "com.mysql.jdbc.Driver";
        Class.forName(driver).newInstance();
catch( Exception e ) {
        System.out.println("Failed to load the mysql driver");
        return;
     }This code works fine when run outside netbeans, ie. from the command line because my classpath includes the appropriate JDBC driver. When I use the code in netbeans it throws the exception. Why does it do this when my system classpath is set correctly?

i have exactly the same problem. none of the 4 replies here earlier than this has offered any help. will anyone who knows please help? put in another way, the question is "how do you get your j2se application to connect to a database from within netbeans using jdbc? netbeans have tutorial for a web application connecting with jdbc, but none for j2se application!!!! wonderful! i thought the philosophy was to keep simple things simple and difficult things possible, and i would have thought it should be simple for a j2se app to connect to a dbase. can anyone from netbeans probably reading this please show us how?

Similar Messages

Any difference in the dbms and jdbc drivers btw oracle 8i lite and 9i lite

Is there any significant difference between oracle 8i lite and oracle 9i lite in terms of database and jdbc drivers?
If not, it may be better off using oracle8i.

According to Oracle , 9i lite is more powerful than 8i Lite.
one thing, 8i Lite is not certified for windows 2000.
jothi

JAR files for SQLJ and JDBC drivers: what is the best practice?

starting a migration from IAS 10 to WebLogic 11g.
Apparently the jar files for SQLJ are not on the classpath by default.
java.lang.NoClassDefFoundError: sqlj/runtime/ref/DefaultContextwhich is the better practice: putting the SQLJ runtime jar into the lib subdirectory of the domain directory, or using a shared library reference? (usage of SQLJ is pretty prevalent in our apps, though we may be getting away from it)
are the Oracle JDBC drivers on the classpath by default?
if not, then the same question: put them into the lib subdirectory of the domain directory, or use a shared library reference?

I'm looking at the setDomainEnv, especially the big note at the top:
>
# WARNING: This file is created by the Configuration Wizard.
# Any changes to this script may be lost when adding extensions to this configuration.
>
and am getting squeamish about editing it...
http://www.bea-weblogic.com/how-do-i-disable-wls-automatically-adding-to-classpath.html looks like the default behaviour is for WebLogic to put $DOMAIN/lib;$WL_HOME/common/lib/ext;$WL_HOME/server/lib/ext on the classpath; there is also a reference to setting weblogic.ext.dirs= when starting weblogic (which means I set the WEBLOGIC_EXTENSION_DIRS environment variable).
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/programming/libraries.html#wp1067450 also refers at the bottom to using the domain /lib subdirectory.
so am I correct that a good practice is to just put the jars I think I will globally need into $DOMAIN/lib, rather than putting them in $WL_HOME/common/lib/ext, $WL_HOME/server/lib/ext, or fiddling with the WEBLOGIC_EXTENSION_DIRS environment variable?
Edited by: user8652010 on Feb 10, 2011 1:08 PM

Installing ODBC and JDBC drivers

I have recently downloaded JDBC drivers from the Oracle driver download page.
How do I install them?

JDBC drivers aren't generally "installed" in the standard sense. They're just JAR files-- you put them in your CLASSPATH and you're done.
For ODBC drivers, you need to install the Oracle client, then you can use the Oracle Universal Installer that's part of the client install to install the latest ODBC driver patchset.
Justin

MTS and JDBC drivers

I having trouble getting MTS to work with 8.1.5 on solaris, I think the problem might be that my clients are using the JDBC thin drivers (in classes111.zip). Should this work?

Yes, but what made me suspect JDBC was the doc says the listener sends back a "reconnect" to tell the client to reconnect to the selected dispatcher. I wasn't sure this was working, since LSNRCTL> SERVICES indicated connections going to the dispatchers but I was getting connect errors back from the JDBC library. Another odd thing is LSNRCTL> SERVICES shows two entries for my service -- both with the same name. The first has a dedicated server only, and the second has a dedicated server and dispatchers.

CLASSPATH and JDBC Drivers in a Jar File

Hi all, I am creating an application in JDev that uses JDBC to connect to a 10g database. I am deploying my application to a jar and running it on the database server using the jdk installed with the database. $ORACLE_HOME/jdk/bin I want to also use the jdbc driver installed in $ORACLE_HOME/jdbc/lib instead of including the driver in my application jar file. How can I cause my jar file to find the jdbc lib?
Can I register it directly with the DriverMannager using the file? My app knows the $ORACLE_HOME.
Or do I just include the jdbc driver in my jar?
John

I was hoping it would be that easy. But I am still having problems. Here is my setup.
export MON_JAVA="$ORACLE_HOME/jdk/bin/java -classpath /u01/app/oracle/product/10.2.0/db_1/jdbc/lib/ojdbc14.jar"
$MON_JAVA -jar PMonitor.jar -c trace
and I get this error when connecting to the database.
Exception in thread "main" java.lang.NoClassDefFoundError: oracle/jdbc/OracleDriver
I also tried the classes.jar with the same results.

Differences between Oracle JDBC Thin and Thick Drivers

If any body is looking for this information...
============================================================
I have a question concerning the Oracle JDBC thin vs. thick drivers
and how they might affect operations from an application perspective.
We're in a Solais 8/Oracle 8.1.7.2 environment. We have several
applications on several servers connecting to the Oracle database.
For redundancy, we're looking into setting up TAF (transparent
application failover). Currently, some of our apps use the Oracle
JDBC thin drivers to talk to the database, with a connection
string that like this:
 jdbc:oracle:thin:@host:port:ORACLE_SID 
In a disaster recovery mode, where we would switch the database
from one server to another, the host name in the above string
would become invalid. That means we have to shut down our application
servers and restart them with an updated string.
Using the Oracle OCI (thick) driver though, allows us to connect
to a Net8 service instead of a specific server:
 jdbc:oracle:oci8:@NET8_SERVICE_NAME 
Coupled with the FAILOVER=ON option configured in Net8, it is
then possible to direct a connection from the first server to
the failover database on another server. This is exactly what
we would like to do.
My question is, from an application perspective, how is the Oracle
thick driver different from the thin driver? If everything
else is "equal" (i.e. the thick driver is compatible with the
app servers) would there be something within the the thick/OCI
driver that could limit functionality vs. the thin driver?
My understand, which obviously is sketchy, is that the thick
driver is a superset of the thin driver. If this is the case,
and for example if all database connections were handled through
a configuration file with the above OCI connection string, then
theoretically the thick driver should work.
============================================================

In the case with the Oracle, they provide a thin driver that is a 100% Java driver for client-side use without the need of an Oracle installation (maybe that's why we need to input server name and port number of the database server). This is platform indipendent, and has good performance and some features.
The OCI driver on the other hand is not java, require Oracle installation, platform dependent, performance is faster, and has a complete list of all the features.

========================================================
I hope this is what you expect.
JDBC OCI client-side driver: This is a JDBC Type 2 driver that uses Java native methods to call entrypoints in an underlying C library. That C library, called OCI (Oracle Call Interface), interacts with an Oracle database. The JDBC OCI driver requires an Oracle (7.3.4 or above) client installation (including SQL*Net v2.3 or above) and all other dependent files. The use of native methods makes the JDBC OCI driver platform specific. Oracle supports Solaris, Windows, and many other platforms. This means that the Oracle JDBC OCI driver is not appropriate for Java applets, because it depends on a C library to be preinstalled.
JDBC Thin client-side driver: This is a JDBC Type 4 driver that uses Java to connect directly to Oracle. It emulates Oracle's SQL*Net Net8 and TTC adapters using its own TCP/IP based Java socket implementation. The JDBC Thin driver does not require Oracle client software to be installed, but does require the server to be configured with a TCP/IP listener. Because it is written entirely in Java, this driver is platform-independent. The JDBC Thin driver can be downloaded into any browser as part of a Java application. (Note that if running in a client browser, that browser must allow the applet to open a Java socket connection back to the server.
JDBC Thin server-side driver: This is another JDBC Type 4 driver that uses Java to connect directly to Oracle. This driver is used internally by the JServer within the Oracle server. This driver offers the same functionality as the client-side JDBC Thin driver (above), but runs inside an Oracle database and is used to access remote databases. Because it is written entirely in Java, this driver is platform-independent. There is no difference in your code between using the Thin driver from a client application or from inside a server.
======================================================
How does one connect with the JDBC Thin Driver?
The the JDBC thin driver provides the only way to access Oracle from the Web (applets). It is smaller and faster than the OCI drivers, and doesn't require a pre-installed version of the JDBC drivers.
import java.sql.*;
class dbAccess {
public static void main (String args []) throws SQLException
DriverManager.registerDriver (new oracle.jdbc.driver.OracleDriver());
Connection conn = DriverManager.getConnection
("jdbc:oracle:thin:@qit-uq-cbiw:1526:orcl", "scott", "tiger");
// @machineName:port:SID, userid, password
Statement stmt = conn.createStatement();
ResultSet rset = stmt.executeQuery("select BANNER from SYS.V_$VERSION");
while (rset.next())
System.out.println (rset.getString(1)); // Print col 1
stmt.close();
How does one connect with the JDBC OCI Driver?
One must have Net8 (SQL*Net) installed and working before attempting to use one of the OCI drivers.
import java.sql.*;
class dbAccess {
public static void main (String args []) throws SQLException
try {
Class.forName ("oracle.jdbc.driver.OracleDriver");
} catch (ClassNotFoundException e) {
e.printStackTrace();
Connection conn = DriverManager.getConnection
("jdbc:oracle:oci8:@qit-uq-cbiw_orcl", "scott", "tiger");
// or oci7 @TNSNames_Entry, userid, password
Statement stmt = conn.createStatement();
ResultSet rset = stmt.executeQuery("select BANNER from SYS.V_$VERSION");
while (rset.next())
System.out.println (rset.getString(1)); // Print col 1
stmt.close();
=================================================================

Wow, not sure what your question was, but there sure was a lot of information there...
There really is only one case where failover occurs, and it would not normally be in a disaster recovery situation, where you define disaster recovery as the obliteration of your current server farm, network and concievably the operational support staff. This would require a rebuild of your server, network etc and isn't something done with software.
Fail over is normally used for high availablity that would take over in case of hardware server failure, or when your support staff wants to do maintenance on the primary server.
Using the thin and thick driver should have ZERO affect on a failover. Transparent failover will make the secondary server the same IP as the primary, therefore the hostname will still point to the appropriate server. If you are doing this wrong, then you will have to point all your applications to a new IP address. This should be something that you tell your management is UNACCEPTABLE in a fail-over situation, since it is almost sure to fail to fail-over.
You point out that you are providing the TNSNAME, rather than the HOSTNAME when using the thick driver. That's true within your application, but that name is resolved to either a HOSTNAME, or IP ADDRESS before it is sent to the appropriate Oracle server/instance. It is resolved using either a NAME server (same as DNS server but for Oracle), or by looking at a TNSNAMES file. Since the TNSNAMES files profilerate like rabbits within an organization you don't want a fail over that will make you find and switch all the entries, so you must come up with a fail over that does not require it.
So, the application should not be concerned with either the hostname, or the IP address changing during fail over. That makes use of the thin or thick client acceptable for fail over.
Don't know if this will help, but this shows the communication points.
THIN DRIVER
client --> dns --> server/port --> SID
THICK DRIVER
client --> names server --> dns --> server/port --> SID
client --> tnsnames --> dns --> server/port --> SID

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.

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.

SAP BI 4.0 SP2 on Linux and Postgresql Datasource via JDBC drivers

Hi,
I installed SAP BI Platform 4.0 SP2 on Redhat 5.2 and i try to access as a universe datasource a postgresql database (v8.4). But i don't know how to configure the postgresql JDBC driver on linux server.
does anyone have a step by step procedure to configure this JDBC postgresql driver on linux ?
I download this driver : http://jdbc.postgresql.org/download/postgresql-8.4-703.jdbc3.jar
I read the SAP Data Access document for SAP BI 4.0 SP2 about JDBC connexions, they talk about a SBO file located in $ROOT_DIR/sap_bobj/enterprise_xi40/dataAccess/connectionServer/jdbc , but there isn't any SBO file for postgresql database ?
Thanks in advance
JP
Edited by: Jean-Philippe ARNALOT on Oct 6, 2011 6:58 PM

Hi
I found a solution alone, this note 1347514 helps me :
My conf : Redhat 5.2 + SAP BI 4.0 SP2 + postgresql 8.4 datasource + jdbc drivers
My solution :
1) Download JDBC drivers on client side (http://jdbc.postgresql.org/download/postgresql-8.4-703.jdbc3.jar)
2) Create and export a JDBC connexion for postgresql8
3) Create and export a universe using this connexion (test a query in universe design tool tools/Querybuilder)
4) install JDBC drivers on server side, i copied the jar file in this location : $ROOT_DIR/sap_bobj/enterprise_xi40/dataAccess/connectionServer/drivers/java/postgresql-8.4-703.jdbc3.jar
5) Set your classpath in your .profile : CLASSPATH=$CLASSPATH:/export/logiciels/tes-boxi/sap_bobj/enterprise_xi40/dataAccess/connectionServer/drivers/java/postgresql-8.4-703.jdbc3.jar; export CLASSPATH
6) Source your .profile
7) Restart servers (i think restarting only webi server would be ok)
8) Open BI LaunchPad, start Webi and execute a query on postgresql universe
It Works with my configuration
Thanks for your help
JP

JDBC drivers for SQL Server 2008 and PI7.0

HI,
I have deployed the JDBC drivers (sqljdbc.jar and sqljdbc4.jar) available for the SQL Server 2008 from the microsoft website as described in the how to document for deploying and configuring JDBC and JMS adapters.
I am running a JDBC to FIle(XML) scenario. When I go and see on the RWB CC monitoring, I get this error
Error during database connection to the database URL 'jdbc:sqlserver://hostname:1433;databaseName=123_Nagasatya' using the JDBC driver 'com.microsoft.sqlserver.jdbc.SQLServerDriver': 'com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:sqlserver://hostname:1433;databaseName=123_Nagasatya': UnsupportedClassVersionError: com/microsoft/sqlserver/jdbc/SQLServerDriver (Unsupported major.minor version 50.0)'
WRT to the SQL server the port 1433 is open on the host and there is no firewall on the PI server as well as the SQL Server. Both are on different machines.Any help would be greatly appreciated.
Regards.

Hi Sujan,
This is the link.
[JDBC|http://www.microsoft.com/downloads/details.aspx?familyid=c47053eb-3b64-4794-950d-81e1ec91c1ba&displaylang=en]
or
You can also use the one on the market place.
Go to http://service.sap.com/msplatforms -> SQL Server
get zip-file sqljdbc_12_hotfix.zip contains the sqljdbc.jar file.
It should work.
Please let me know if you have any questions.
Regards.

SQL Server 2000 SP3 and jdbc type 4 drivers

hi all,
Has anybody had any problems using the type 4 jdbc drivers for SQL Server2000 after you upgraded the SQL Server 2000 with the latest Service Pack SP3 ??
Please reply..
cheers,
-Jer

hi shilohcity,
i did have some problem when i updated my sql server to sp3. The driver i was using.., Atinav's aveConnect3, didn't connect and was throwing exceptions. But after contacting their tech support, they provided me with an updated version, which they had released recently, and that solved the problem. I now believe that with that support, what i paid for that driver was worth it.'cos I would've been kept waiting for the updates if i was using some free driver with poor tech support.
see these links..
http://forum.java.sun.com/thread.jsp?forum=48&thread=351239
and another one
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&threadm=e4774458.0301270610.134f9e5d%40posting.google.com&rnum=1&prev=/groups%3Fq%3DaveConnect%26hl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26selm%3De4774458.0301270610.134f9e5d%2540posting.google.com%26rnum%3D1
I do think this is some problem that could be solved by the driver vendors. the M$ 's TDS version is still a mystery as far as i know. and the driver should communicate with sql server using this TDS protocol. I dont know, may be SP3 would've introduced updates in the TDS protocol.. and the drivers should be able to support it, or new updated versions released.
It can happen in future too... M$ may change their stance anytime.. better be wise in choosing your DB Server and even be more careful while chosing JDBC drivers.
cheers,
-Jer

Appropriate JDBC drivers for 7.0 version and SP16

Hi all
we are using XI 7.0 SP 16.
what type/verion of JDBC drivers should be used for database connectivity?
while i was going through "How to install external JDBC Drivers" it was suggesting to use
Oracle 9i and Oracle 10g:
ojdbc14.jar
u2022 Microsoft SQL Server:
msbase.jar, mssqlserver.jar, msutil.jar
(in screen shots as well it was showing he was using msbase.jar, mssqlserver.jar, msutil.jar and ojdbc14.jar)
should we use both ojdbc14.jar and msbase.jar, mssqlserver.jar, msutil.jar or else one of them would be sufficient?
Is OJDBC a type 4 and type 2 driver?
Full Points are guaranteed
Regards
Bhasker

Hi,
You have to use ojdbc14.jar or classes12.zip/.jar for Oracle and msbase.jar, mssqlserver.jar, msutil.jar for Microsoft SQL Server. Thus both are required to be deployed on J2EE server.
And Oracle JDBC is a type 4 driver.
refer --> http://www.aquafold.com/docs-jdbcdrivers-oracle10g.html
Refer
SAP Note : 1078420, 831162, 941317, 1138877
Thanks
Swarup
Edited by: Swarup Sawant on Aug 4, 2008 10:25 AM

Multithreaded clients and Oracle JDBC-drivers?

Are the thin and OCI8 drivers for Oracle multithreaded? (I know they're thread safe)
I.e. Can many threads share the same Connection object (and statement objects) to do their requests without the requests being serialized to the DB?
Sun's javadoc of package java.sql says:
We require that all operations on all the java.sql objects be multi-thread safe and able to cope correctly with having several threads simultaneously calling the same object.
Some drivers may allow more concurrent execution than others. Developers can assume fully concurrent execution; if the driver requires some form of synchronization, it will provide it. The only difference visible to the developer will be that applications will run with reduced concurrency.
For example, two Statements on the same Connection can be executed concurrently and their ResultSets can be processed concurrently (from the perspective of the developer). Some drivers will provide this full concurrency. Others may execute one statement and wait until it completes before sending the next.
One specific use of multi-threading is to cancel a long running statement. This is done by using one thread to execute the statement and another to cancel it with its Statement.cancel() method.
Restated again for Oracle; Will threads run concurrently when using the same connection and statements, or will the calls be serialized?

In the connection pool, I specified:
user
password
url
In the deployment tool (Sun Java Appl. Server 8 BE Update 1), I specified the "Resource Reference" for the EJB. This leads to the following entries in sun-ejb-jar.xml:
<res-ref-name>jdbc/pdisasdb</res-ref-name>
 <jndi-name>jdbc/pdisasdb</jndi-name>
 <default-resource-principal>
 <name>myname</name>
 <password>geheim</password>
 </default-resource-principal>
</resource-ref> The strange thing is, that now it works without this entry - but I am not gaga, yesterday it doesnt...

JDBC drivers for Oracle734 on Solaris7 and JDK 1.2

Hi there,
I'm trying to JDBC to an Oracle 7.3.4 running on Solaris7 while
writing JDK 1.2.2 application. Here's the trace of what's
happenning:
Connecting to the database...Connecting...
Exception in thread "main" java.lang.UnsatisfiedLinkError:
/space/javapkg/oracle7/liboci73jdbc.so: ld.so.1:
/space/jdk1.2.2/bin/../bin/sparc/native_threads/java: fatal:
relocation error: file /space/javapkg/oracle7/liboci73jdbc.so:
symbol makeJavaString: referenced symbol not found
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1330)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1254)
at java.lang.Runtime.loadLibrary0(Runtime.java:644)
at java.lang.System.loadLibrary(System.java:815)
at oracle.jdbc.oci7.OCIDBAccess.logon(OCIDBAccess.java:149)
at
oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:103)
at
oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:148)
at java.sql.DriverManager.getConnection(DriverManager.java:515)
at java.sql.DriverManager.getConnection(DriverManager.java:175)
at JdbcCheckup.main(JdbcCheckup.java:43)
Is there a nice solution for that? Please, do not advise to
upgrade Oracle / degrade JDK: it's not my call and is out of the
question. There's an existing solution where we use $30,000
WebLogic ridiculous license just to use their JDBC drivers but
that's exactly what we want to switch from.
Sincerely,
-Evgeni
null

Yup, thanks a lot. I am ashamed. I know: "read the FAQ then
ask; read the FAQ then ask"... Eventually I'll get it :)).
Thanks again,
-Evgeni
Oracle Product Development Team wrote:
: Our 7.3.4 OCI driver doesn't work with JDK 1.2, but our 8.1.6
: release of the OCI driver will. In the meantime, you can try
our
: 8.1.6SDK thin driver if you have to stick with JDK 1.2. It
: should be compatible with your 7.3.4 database.
http://technet.oracle.com/tech/java/sqlj_jdbc/htdocs/jdbc_faq.htm
: #_1_
: Evgeni (guest) wrote:
: : Hi there,
: : I'm trying to JDBC to an Oracle 7.3.4 running on Solaris7
while
: : writing JDK 1.2.2 application. Here's the trace of what's
: : happenning:
: : Connecting to the database...Connecting...
: : Exception in thread "main" java.lang.UnsatisfiedLinkError:
: : /space/javapkg/oracle7/liboci73jdbc.so: ld.so.1:
: : /space/jdk1.2.2/bin/../bin/sparc/native_threads/java: fatal:
: : relocation error: file
/space/javapkg/oracle7/liboci73jdbc.so:
: : symbol makeJavaString: referenced symbol not found
: : at java.lang.ClassLoader$NativeLibrary.load(Native
: Method)
: : at java.lang.ClassLoader.loadLibrary0
: (ClassLoader.java:1330)
: : at java.lang.ClassLoader.loadLibrary
: (ClassLoader.java:1254)
: : at java.lang.Runtime.loadLibrary0(Runtime.java:644)
: : at java.lang.System.loadLibrary(System.java:815)
: : at oracle.jdbc.oci7.OCIDBAccess.logon
: (OCIDBAccess.java:149)
: : at
: : oracle.jdbc.driver.OracleConnection.<init>
: (OracleConnection.java:103)
: : at
oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:148)
: : at java.sql.DriverManager.getConnection
: (DriverManager.java:515)
: : at java.sql.DriverManager.getConnection
: (DriverManager.java:175)
: : at JdbcCheckup.main(JdbcCheckup.java:43)
: : Is there a nice solution for that? Please, do not advise to
: : upgrade Oracle / degrade JDK: it's not my call and is out of
: the
: : question. There's an existing solution where we use $30,000
: : WebLogic ridiculous license just to use their JDBC drivers
but
: : that's exactly what we want to switch from.
: : Sincerely,
: : -Evgeni
: Oracle Technology Network
: http://technet.oracle.com
null

Netbeans and JDBC drivers

Similar Messages

Maybe you are looking for