Applet which uses the JDBC Thin driver

My applet is running from Internet Explorer(Windows NT 4.0) and uses the JDBC
Thin Driver to connect to database. The code complies with J2SDK1.4.0-beta3 and
JDBC 2.0. I am getting following error:java.lang.NoClassDefFoundError:
oracle/jdbc/driver/oracleDriver at applet.button_actionPerformed...
Can anybody help?
help urgently needed...
Best regards and thanks in advance

AFAIK the Oracle drivers still don't work with JDK 1.4, switch to 1.31 and they should be fine.

Similar Messages

Sql_trace does not work for Java app using Oracle JDBC thin driver

Hi,
I'm using Oracle 8.1.7. I enabled sql trace at instance level by setting sql_trace and timed_statistics to true in init.ora. I restarted the db instance. I wrote a stand-alone java application which used Oracle JDBC thin driver(classes12.zip) to make a connection to my db instance, do some select statements, and close the connection. There were no trace files generated in the folder specified by udump_dest variable. However, if I used sqlplus or dba studio, I saw trace files generated. Has anyone got Oracle sql trace work for JDBC calls from java apps.
Thanks in advance!

Hi,
I'm using Oracle 8.1.7. I enabled sql trace at instance level by setting sql_trace and timed_statistics to true in init.ora. I restarted the db instance. I wrote a stand-alone java application which used Oracle JDBC thin driver(classes12.zip) to make a connection to my db instance, do some select statements, and close the connection. There were no trace files generated in the folder specified by udump_dest variable. However, if I used sqlplus or dba studio, I saw trace files generated. Has anyone got Oracle sql trace work for JDBC calls from java apps.
Thanks in advance!

Using Oracle JDBC Thin Driver

We are trying to use the Oracle supplied JDBC thin driver directly from within a jar file we add for our application.
The classes in the jar file directly connect to an oracle database via the thin driver.
The problem we've encountered is that if the JDBC Connection object is held in memory, after some time, the connection times out for no reason.
Is there some restriction with weblogic in connecting directly to database from a class file and then caching the connection reference? It almost seems as if weblogic is severing the connections.
thank you,
BJ

Stefan,
You are right, although I would recommend just having the
TestConnectionOnReserve= true and the testTableName set. Refresh Minutes
becomes kind of redundent when you set these values.
TestConnsOnReserve allows the server to verify if a connection that the
client/application has requested is good , otherwise it recreates this
connection and gives it to the client/application.
hth
sree
"Stefan" <[email protected]> wrote in message
news:[email protected]...
Hi Sree,
If instead a WL connection pool would be used this issue could be solved
using
"Refresh Period" and TestTableName right? In this case the connection would
be
alive as long as WL server is up. As a bonus we would have an automatic
reconnection
after an Oracle server reboot?
thanks, stefan
"Sree Bodapati" <[email protected]> wrote:
Hi BJ,
When you get connection directly using the Oracle thin driver, this is
for
sure your database timing out the connection when no activity is detected
for sometime. You should consult with your DBA to ensure this timeout
is set
to a higher value at the server or ensure you dont hold on to theconnection
for long durations or ensure you handle this situation by triggering
a
generic oracle process so that you periodically keep the connection busy
to
ensure that the database does not close it.
This shouldnt be anything to do with WebLogic as you dont seem to be
using
WebLogic connection pool.
hth
sree
"BJ Choi" <bongjin.choi@neoforma> wrote in message
news:[email protected]...
We are trying to use the Oracle supplied JDBC thin driver directly from
within a jar file we add for our application.
The classes in the jar file directly connect to an oracle database via
the
thin driver.
The problem we've encountered is that if the JDBC Connection object is
held
in memory, after some time, the connection times out for no reason.
Is there some restriction with weblogic in connecting directly to database
from a class file and then caching the connection reference? It almost
seems
as if weblogic is severing the connections.
thank you,
BJ

Change expired password using oracle jdbc thin driver

Hello,
I have a java program that uses the oracle jdbc thin driver (ojdbc6 - version 11.2.0.3) for database connection. My question is if I have any possibility to change an expired password (java.sql.SQLException: ORA-28001: the password has expired) using the thin driver - NOT OCI?

No - the thin driver doesn't have any password management features.

Problem in connecting to database using oracle jdbc thin driver

hi
i am trying to connect to a database using oracle thin driver.
i am getting following error:
java.sql.sqlexception:Io exception: the network adapter could not establish the connection
Io exception: the network adapter could not establish the connection
the connection string has the property of using a dedicated server
for this reason i have put USE_DEDICATED_SERVER=ON in sqlnet.ora file...
we did not face this problem while connecting to other databases which do not have the property of dedicated server in their connection string in tnsnames.ora file.
please suggest a solution for this.
thanks and regards,
asif

If you are using the thin driver, sqlnet.ora does not come into play. None of Oracle networking does. That is one of the great things about using the thin driver, no need to have the client installed.
That error is due to incorrect connection info you are supplying or the machine you are connection from can't ping the machine it is trying to connect to.

Issue in handling UTF8 characters using Oracle JDBC thin driver in Linux

We have a standalone Java application which reads values from one table and inserts the same into another table. The value in the source table is "Türkiye Is Bankasi Gayrettepe Subesi" and the same value after inserting into the target table becomes "Tï¿½rkiye Is Bankasi Gayrettepe Subesi" (ü is getting converted to ï¿½).
The same works fine if we run the application in Windows.

Thanks again for looking into this. Please find the answers below
1.What character set do you use in the database? (see NLS_CHARACTERSET and NLS_NCHAR_CHARACTERSET in the view NLS_DATABASE_PARAMETERS).
- Both of them are UTF8
2. What is the type of the column storing that string? (e.g. VARCHAR2, NVARCHAR2, an object type, ...)
- Varchar2
3. Source binary value (for "Türkiye Is Bankasi Gayrettepe Subesi")
is
Typ=1 Len=36:
54,fc,72,6b,69,79,65,20,49,73,20,42,61,6e,6b,61,73,69,20,47,61,79,72,65,74,74,65,70,65,20,53,75,62,65,73,69
Target binary value (for "Tï¿½rkiye Is Bankasi Gayrettepe Subesi")
is
Typ=1 Len=38: 54,ef,bf,bd,72,6b,69,79,65,20,49,73,20,42,61,6e,6b,61,73,69,20,47,61,79,72,65,74,74,65,70,65,20,53,75,62,65,73,69

Using JDBC-thin driver

Hello,
I am using CMSDK on a propretary software, after the upgrade to version 9.0.3, it seems that the API uses by default the OCI driver and it looks for the db url from the domain url when starting the IFS service.
The problem with that is the JDBC-OCI driver character encoding of utf-8 charaters in C which transforms the characters in an unwanted form (I use arabic characters in input and get garbage stored in the database).
Is there a way to make CMSDK uses the jdbc-thin driver instead of jdbc-oci driver?
I hope so, and I would like to know how to do it.
Thanks in advance.
Amin AZZI
AAcom AlgÃ©rie.
Algiers/Algeria

Hello everybody,
I could finally use the JDBC-THIN driver by directly changing the IFS.SERVICE.JDBC.DriverType property in the database repository to thin (by default it is oci8).
Since there are three different services configurations someone must change the correct one.
Amine.

Connection error to 9i database using JDBC thin driver

When trying to connect to a new 9i database using the JDBC thin driver, I received the following error:
java.sql.SQLException: ORA-00600: internal error code, arguments: [ttcgcshnd-1], [0], [], [], [], [], [], []
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java)
at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java)
at oracle.jdbc.ttc7.Oall7.receive(Oall7.java)
at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java)
at oracle.jdbc.ttc7.TTC7Protocol.fetch(TTC7Protocol.java)
at oracle.jdbc.driver.OracleStatement.doExecuteQuery(OracleStatement.java)
at oracle.jdbc.driver.OracleStatement.doExecute(OracleStatement.java)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java)
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java)
at oracle.jdbc.driver.OracleDatabaseMetaData.getTables(OracleDatabaseMetaData.java)
I have no problem with my code connecting to an Oracle 8 database, just 9i.
I'm trying to debug in Visual Cafe (JDK 1.1.7) and have both the classes111.zip and the nls_charset11.zip in my CLASSPATH.
Any suggestions would be appreciated. Thanks

If you're using 8i 8.1.7.1 or 8i 8.1.7.0 thin JDBC drivers on NT, then you can get them to connect to 9i by applying the 8i 8.1.7.1 Patch available at:
http://technet.oracle.com/software/tech/java/sqlj_jdbc/htdocs/solsoft.html
You might have to register/login first.
Basically, it's just a case of replacing a class already in your classes111.zip or classes12.zip with the class in the patch.
Took me a while to find this, but it worked first time after patching. Hope this helps.

Problem using JDBC Thin driver with Oracle 8i Personal Edition

Hi all, I have an issue I have been unable to figure out. In order to make my code as portable as possible I am using the JDBC thin driver to access my database. I have been able to connect to an instance of Oracle 8i on a Sun box by hardcoding the following string into getConnection() call:
conn = DriverManager.getConnection("jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(COMMUNITY=tcp.world)(PROTOCOL=TCP)(Host=<myhostname>)(Port=1521))(ADDRESS=(COMMUNITY=tcp.w orld)(PROTOCOL=TCP)(Host = <myhostname>)(Port = 1526)))(CONNECT_DATA = (SID = <mysidname>)))", <myuser>, <mypassword>);
My problem is that I cannot figure out what string to use to connect to my local instance of Oracle 8i Personal. I used the following string (the sid I got from the looking at the init.ora file):
conn = DriverManager.getConnection("jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(COMMUNITY=tcp.world)(PROTOCOL=TCP)(Host=localhost)(Port=1521))(ADDRESS=(COMMUNITY=tcp.world)(PRO TOCOL=TCP)(Host = localhost)(Port = 1526)))(CONNECT_DATA = (SID = orcl)))", "scott", "tiger");
That didn't work, so I took the only entry found in my tnsnames.ora file in as:
conn = DriverManager.getConnection("jdbc:oracle:thin:@(DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0)))(CONNECT_DATA = (SID = PLSExtProc)(PRESENTATION = RO)))", "scott", "tiger");
I am not knowing what is wrong, but that didn't work neither. Any suggestions would be highly appreciated.
Thanks....
null

try this:
conn = DriverManager.getConnection("jdbc:oracle:thin:scott/tiger:@hostname:1521:sid");
or use system/manager as username/passward
null

JDBC Thin-Driver and Oracle Stored Procedure

I've got a Oracle stored procedure which returns a Oracle record.
How can I retrieve the record in java using the JDBC Thin-Driver ?
Record:
TYPE messagerec IS RECORD
(log_level VARCHAR(2), timestamp VARCHAR2(19), text VARCHAR2(200));

Using PL/SQL BOOLEAN, RECORD Types, and TABLE Types:
Oracle SQLJ and JDBC do not support calling arguments or return values of the
PL/SQL BOOLEAN type or RECORD types. Also, when using the Thin driver, they
do not support calling arguments or return values of PL/SQL TABLE types (known
as indexed-by tables). TABLE types are supported for the OCI driver.
Check the following guide,
http://otn.oracle.com/tech/java/sqlj_jdbc/pdf/a96655.pdf

JDBC thin driver pads CHAR col to byte size when NLS_LENGTH_SEMANTICS=CHAR

We're using an Oracle 9.2 database with the database character set specified as AL32UTF8 with NLS_LENGTH_SEMANTICS set to CHAR. I've reproduced this problem with both the "classes12.zip" and "ojdbc14.jar" available with the Oracle 9.2 client installation.
The problem occurs with the JDBC thin driver. The problem does not occur with the JDBC OCI driver (nor SQL*Plus 9.2).
There are 2 relatively simply workarounds: use the OCI driver or convert CHAR columns to VARCHAR2 columns. I'm mostly curious as to whether there is some kind of setting for the thin driver to circumvent this problem, or if this is actually expected behavior. We're not that familiar with the NLS_LENGTH_SEMANTICS setting.
Consider a table as follows:
create table my_table (status CHAR(1));
If I describe the table it correctly shows the column using CHAR semantics.
STATUS CHAR(1 CHAR)
Given the AL32UTF8, this means that 4 bytes of storage are reserved for this column.
If I insert a single ASCII character in this table (for example "A") then read it back using the JDBC thin driver, I get the string "A " - the letter A followed by 3 spaces. In other words, the thin driver appears to have padded the value to its BYTE length. The OCI driver and SQL*Plus do not pad the value.
I understand that CHAR columns are normally blank padded when the data size is shorter than the defined column length, but I think that with NLS_LENGTH_SEMANTICS=CHAR, the padding should be based on the length of the column in chars, not in bytes.
Can anyone shed some light on this issue?
Thanks in advance,
Tim

Update:
I guess I should mention we're using Java 2 SDK 1.4.1_01 on Windows XP with an Oracle 9.2 database on Windows 2000.

SSL connection with JDBC thin driver

I am attempting to connect to an instance of Oracle 10.2 using the JDBC thin driver with SSL. I want to use the encryption feature of SSL only, but I can not perform the getConnection on the DataSource without running into an exception. According the JDBC docs, the SSL encryption feature is new for the 10.2 release of the JDBC thin driver, but I have seen no working examples. See http://download.oracle.com/docs/cd/B19306_01/java.102/b14355/overvw.htm#CHDIHFBD
I am using ojdbc14.jar on Java 5.0 using a standalone application, and it fails with an IOException (The network adapter could not establish the connection) (Error code 17002). I even enabled tracing using the ojdbc-g.jar to try to figure out what the REAL problem is, but it was not helpful at determining a root cause. I changed the driver type from "thin" to "oci" (and installed Oracle Instant client for my test machine) and the connection works just fine using the same tnsnames file, the same wallet, and the same cipher suite. From the Java perspective the only thing that changed was four characters -> "thin" became "oci". I am still using password based authentication as I understand that the authentication part of SSL is not supported in the thin driver on 10.2
Can anyone verify that the SSL encryption works with JDBC thin as advertised? (not the Oracle Net encryption, but rather the one described in Chapter 11 of the JDBC Developer's Guide. See http://download.oracle.com/docs/cd/B19306_01/java.102/b14355/sslthin.htm#CHDFEICG
I really would prefer to avoid using the OCI driver because of its dependencies on the native platform. Is there something special with how the users are created or how the JDBC API should be used? I am setting what I think to be appropriate parameters (oracle.net.wallet_location, oracle.net.cipher_suites) all to no avail. Does anyone have a working example they can provide?

1) I would suggest posting this question over in the JDBC forum. The folks over there are far more likely to be able to help you.
2) When you do post this question over there, I would strongly suggest posting some sample code/ configuration scripts so that folks can reproduce your problem on their local machines. That tends to make it far easier to debug the problem and/or to notice if you've missed a step.
Justin

Web Logic 6.1 JDBC Pooling with the Oracle Thin Driver

Hi,
We're slowly getting through a WebLogic 4.5.1 to 6.1 conversion for a small application
at my company. Initially, we had trouble getting the Oracle thin driver working.
We've finally cracked this nut. Now we're trying to get pooling working, and
cannot find an example of doing this with the Oracle thin driver.
Would anyone be able to provide:
1. the portion of the config.xml that pertains to building a connection pool using
the Oracle thin driver
2. the two lines of code for loading the driver and getting a connection from
this pool
i.e.
Driver d = (Driver)Class.forName("weblogic.jdbc.pool.Driver").newInstance();
Connection c = d.connect("jdbc:weblogic:pool:myPool", null);
Thanks very much!
Jeff Ryan
The Hartford

"Jeff Ryan" <[email protected]> wrote:
>
1. the portion of the config.xml that pertains to building a connection
pool using
the Oracle thin driver
You don't usually edit the config.xml unless it is absolutely necessar. Instead,
you can config the pool in the GUI admin console, quite easily. After you successfully
configed the pool in the console, it is written into the config.xml file for you.
Only thing special when config the pool is the name of the driver and the url.
url: jdbc:oracle:thin@dbhost:dbport:dbinstance
driver: oracle.jdbc.driver.OracleDriver
If you prefer, you can also config the pool from the command line. It is detailed
in the "Weblogic Server Command-line Interface Reference".
2. the two lines of code for loading the driver and getting a connection
from
this pool
i.e.
Driver d = (Driver)Class.forName("weblogic.jdbc.pool.Driver").newInstance();
Connection c = d.connect("jdbc:weblogic:pool:myPool", null);
Again, you don't use the connection directly. Instead, you use "Data Source".
Data source in weblogic is just a connection object factory associated with a
JNDI name. You can therefore lookup the data source with the JNDI name and from
the data source object, you get the connectin object. No need to explicitly load
the driver class.
There are plenty of example codes available in the weblogic examples installed
with 6.1, that uses the data source.
Charles

JDBC Thin Driver 8.17 Release 2

Is the Oracle Direct Driver (JDBC Thin Driver 8.17 Release 2) compatible with other oracle versions like 8.15 and 8.16? Is it backward compatible to older releases. I have tried it and it does work, but I want to make sure there are no known problems going backwards because we have several versions in our shop.
Thanks
Brian

Rong Lu (guest) wrote:
: I am using Oracle JDBC thin driver 8.0.5.0.0 to query Oracle
: 8.0.5 via SQL net. The problem I met is every time I try to
: retrieve data for varchar2 (over 2k), it get truncated and
only
: return the first 2k without throwing any warning or exception.
: I tried getString(), getAsciiStream() and getBinaryStream(),
and
: the results are still the same. The SQL Net works fine, since
it
: successfully returns over 2k varchar2 type data when programing
: with PERL.
check the following oracle jdbc faq link :
http://technet.oracle.com/tech/java/sqlj_jdbc/htdocs/jdbc_faq.htm
#_36_
null

JDBC thin Driver 8.0.X Limit 2k for varchar2?

I am using Oracle JDBC thin driver 8.0.5.0.0 to query Oracle
8.0.5 via SQL net. The problem I met is every time I try to
retrieve data for varchar2 (over 2k), it get truncated and only
return the first 2k without throwing any warning or exception.
I tried getString(), getAsciiStream() and getBinaryStream(), and
the results are still the same. The SQL Net works fine, since it
successfully returns over 2k varchar2 type data when programing
with PERL.
null

Rong Lu (guest) wrote:
: I am using Oracle JDBC thin driver 8.0.5.0.0 to query Oracle
: 8.0.5 via SQL net. The problem I met is every time I try to
: retrieve data for varchar2 (over 2k), it get truncated and
only
: return the first 2k without throwing any warning or exception.
: I tried getString(), getAsciiStream() and getBinaryStream(),
and
: the results are still the same. The SQL Net works fine, since
it
: successfully returns over 2k varchar2 type data when programing
: with PERL.
check the following oracle jdbc faq link :
http://technet.oracle.com/tech/java/sqlj_jdbc/htdocs/jdbc_faq.htm
#_36_
null

Applet which uses the JDBC Thin driver

Similar Messages

Maybe you are looking for