JDBC Thin Server-side Driver 8.1.6

The readme.txt for the JDBC Thin driver
talks about a JDBC Thin driver for clients
and a JDBC Thin Server-side driver for
servers. Where is the Server-side driver?
In Oracle?

I believe the one from technet was created
under the Solaris environment. That is
the only difference that I know of.
null

Similar Messages

JDBC Thin vs Thick Driver

Hello,
We are looking for differences between Oracle JDBC Thin and OCI (thick) driver with respect to
1. Peformance of the Java application.
2. Maintenance and administration
3. Known issues with OCI (thick) driver which is handled by Thin or vice versa.
4. Better security
Appreciate any help on the above.
Thanks and Regards,
Vamsi Mohan Harish

1. Performance of the Java application.
The difference in driver implementation is likely to be trivial compared to other considerations (network round trip time, application design, etc). However if you are really interested then chapter 19 of 'Java Programming with Oracle JDBC' by Donald Bales (O'Reilly) has some good information on this topic. It also happens to be available online: http://www.onjava.com/pub/a/onjava/excerpt/oraclejdbc_19/index.html
Keep in mind that it is a little out of date now - you should run tests using the current versions of the drivers.
2. Maintenance and administration
The JDBC Thin driver is typically easier to update/distribute, as installation consists of copying a .jar file or two. The only case where OCI has an advantage is in the use of Oracle's naming layer for database service abstraction. Of course this assumes the database server is listening for TCP/IP and not the legacy protocols that are only supported by OCI. Failover configurations using TAF are supported by OCI only. The newer 'Fast Connection Failover' feature of 10g RAC can also run over Thin though.
3. Known issues with OCI (thick) driver which is handled by Thin or vice versa.
In my experience each has a roughly equal number of bugs. I find it easier to track them down in the Thin driver though :-)
4. Better security
The security options for the Thin driver are more limited with regard to external authentication and support for some of the Oracle Advanced Security features. However, both support the basics like encrypted connections. Chapter 23 of the JDBC driver docs goes into more depth: http://download-west.oracle.com/docs/cd/B14117_01/java.101/b10979/toc.htm
Hope this helps.
Jonathan.

SQLException - Win 98; Oracle 8i personal (8.1.5) JDBC Thin 1.2 driver

Environment:
Win 98; Oracle 8i personal (8.1.5) JDBC Thin 1.2.2 drivers
Included in classpath: e:\oracle\ora81\jdbc\lib\classes12_01.zip;e:\oracle\ora81\jdbc\lib\nls_chaset2_01.zip;
Included in path: e:\Oracle\Ora81\bin;e:\Oracle\Ora81\\jdbc\lib;
code snippet used:
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
dbconn = DriverManager.getConnection( "jdbc:oracle:thin:@127.0.0.1:1521:ORCL","scott","tiger" );
following runtime error occurs:
java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:114)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:156)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:210)
at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:251)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:224)
at java.sql.DriverManager.getConnection(DriverManager.java:457)
at java.sql.DriverManager.getConnection(DriverManager.java:137)
at OracleTest.main(OracleTest.java, Compiled Code)
Any suggestions anyone?

<BLOCKQUOTE>quote:<HR>Originally posted by Vij:
Environment:
Win 98; Oracle 8i personal (8.1.5) JDBC Thin 1.2.2 drivers
Included in classpath: e:\oracle\ora81\jdbc\lib\classes12_01.zip;e:\oracle\ora81\jdbc\lib\nls_chaset2_01.zip;
Included in path: e:\Oracle\Ora81\bin;e:\Oracle\Ora81\\jdbc\lib;
code snippet used:
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
dbconn = DriverManager.getConnection( "jdbc:oracle:thin:@127.0.0.1:1521:ORCL","scott","tiger" );
following runtime error occurs:
java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:114)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:156)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:210)
at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:251)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:224)
at java.sql.DriverManager.getConnection(DriverManager.java:457)
at java.sql.DriverManager.getConnection(DriverManager.java:137)
at OracleTest.main(OracleTest.java, Compiled Code)
Any suggestions anyone?<HR></BLOCKQUOTE>
Vij,
Assuming that Personal Oracle is up and running, you should check that the listener is running and listening on the port you are using.
You can check the status with the following command (from the DOS prompt): lsnrctl status
If the listener is not running start it with this command: lsnrctl start listener
You can also have it start automatically by modifying the registry entry LISTENER_STARTUP to "AUTO"
(HKEY_LOCAL_MACHINE\Software\ORACLE\HOME0)
Hope this helps
Thomas Risberg
null

JDBC JApplet server-side transaction?

Is it possible to make a JApplet do a server-side transaction to SQL server?
When accessing an Applet via a web browser, the sql transaction is client side right? Making it slower?

Jepot wrote:
What i mean is when an applet is being run or opened, the pc or computer who is opening it is the one who will be requesting for a connection to the SQL server. What i want to know is if it is possible to set transaction/connection local to the server or server side and not by the client.
Example scenario is i have a server which have a web server and a SQL server, it has an applet that reads sql data from the sql server and displays it. So when a client access the page that contains the applet, java (on the client side) will load the applet and will get sql data from the server, so by this method the applet is getting or transacting sql client-side.Well stop worrying about this. As I told already told you, you are mistaken about how this all works.
The SQL is always executed in SQL Server. Period. Applet or Servlet doesn't matter.
You shouldn't use JDBC code in an Applet for the reasons I gave before, the rest is just you inventing your own terminology.

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

Oracle server side jdbc thin driver throws ORA-01017

We upgraded our database to 11.2.0.1 from 9.2.0.6.
When we try to connect to an external database from Oracle JVM using server side jdbc thin driver, it throws invalid user id/password error.
The below test code simulates the issue and is not working on the upgraded instance. The same code is working in fine in other 11.2.0.1 instances. It worked fine before upgrade. In all cases, we are connecting to the same target database instance which is also in 11.2.0.1. It fails only on this database.
SEC_CASE_SENSITIVE_LOGON is set to false.
Any inputs will be highly appreciated.
Code:_
create or replace and compile java source named TestConn as
import java.sql.SQLException;
import oracle.jdbc.OracleDriver;
import oracle.jdbc.OracleConnection;
import java.sql.DriverManager;
public class TestConn {
 public static String runTest() {
 String msg = "Start";
 OracleConnection tempOC = null;
 try {
 String pUrl = "jdbc:oracle:thin:@dev:1521:dev";
 String pUser = "tst_user";
 String pPwd = "dummy";
 DriverManager.registerDriver (new oracle.jdbc.OracleDriver());
 tempOC = (OracleConnection)DriverManager.getConnection(pUrl, pUser, pPwd);
msg = "Success";
} catch (SQLException sqle) {
 System.out.println(sqle.toString());
 sqle.printStackTrace();
 msg = "Failure";
 return msg;
CREATE OR REPLACE FUNCTION test_conn RETURN VARCHAR2
AS LANGUAGE JAVA
NAME 'TestConn.runTest() return java.lang.String';
set serverout on
declare
c varchar2(4000);
begin
dbms_java.set_output(5000);
c:=test_conn();
dbms_output.put_line(c);
end;
/ Error Message_
java.sql.SQLException: ORA-01017: invalid username/password; logon denied
java.sql.SQLException: ORA-01017: invalid username/password; logon denied
 at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:439)
 at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:388)
 at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:381)
 at oracle.jdbc.driver.T4CTTIfun.processError(T4CTTIfun.java:564)
 at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthenticate.java:431)
 at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:436)
 at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186)
 at oracle.jdbc.driver.T4CTTIoauthenticate.doOAUTH(T4CTTIoauthenticate.java:366)
 at oracle.jdbc.driver.T4CTTIoauthenticate.doOAUTH(T4CTTIoauthenticate.java)
 at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:359)
 at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java)
 at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:221)
 at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
 at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java)
 at java.sql.DriverManager.getConnection(DriverManager.java)
 at java.sql.DriverManager.getConnection(DriverManager.java)
 at TestConn.runTest(TESTCONN:22) Edited by: sskumar on Mar 6, 2011 1:12 PM

At the time our issue was resolved, the bug was not published. And, I was told, there was no information in metalink about the isue. I am not sure whether they published some thing in the last few weeks.
This is what resolved our issue.
Step 1: alter system set java_jit_enabled=FALSE;
Step 2: Try your test case. If it is the same issue as ours, your test case will be successful. If it succeeds, Go to step 3. If it does not succeed, it is a different issue.
Step 3: alter system set java_jit_enabled=TRUE;
Step 4: Run your test case. If it is the same issue, it is expected to fail. Go to Step 5 in case of failure.
Step 5: Delete all rows from table java$mc$
Step 6: Restart the database
Step 7: Run your test case. It is expected to be successful.

Insert data 32K into a column of type LONG using the oracle server side jdbc driver

Hi,
I need to insert data of more than 32k into a
column of type LONG.
I use the following code:
String s = "larger then 32K";
PreparedStatement pstmt = dbcon.prepareStatement(
"INSERT INTO TEST (LO) VALUES (?)");
pstmt.setCharacterStream(1, new StringReader(s), s.length());
pstmt.executeUpdate();
dbcon.commit();
If I use the "standard" oracle thin client driver from classes_12.zip ("jdbc:oracle:thin:@kn7:1521:kn7a") every thing is working fine. But if I use the oracle server side jdbc driver ("jdbc:default:connection:") I get the exception java.sql.SQLException:
Datasize larger then max. datasize for this type: oracle.jdbc.kprb.KprbDBStatement@50f4f46c
even if the string s exceeds a length of 32767 bytes.
I'm afraid it has something to do with the 32K limitation in PL/SQL but in fact we do not use any PL/SQL code in this case.
What can we do? Using LOB's is not an option because we have client software written in 3rd party 4gl language that is unable to handle LOB's.
Any idea would be appreciated.
Thomas Stiegler
null

In rdbms 8.1.7 "relnotes" folder, there is a "Readme_JDBC.txt" file (on win nt) stating
Known Problems/Limitations In This Release
<entries 1 through 3 omiited for brevity >
4. The Server-side Internal Driver has the following limitation:
- Data access for LONG and LONG RAW types is limited to 32K of
data.

Bug in Oracle JDBC thin driver (parameter order)

[ I'd preferably send this to some Oracle support email but I
can't find any on both www.oracle.com and www.technet.com. ]
The following program illustrates bug I found in JDBC Oracle thin
driver.
* Synopsis:
The parameters of prepared statement (I tested SELECT's and
UPDATE's) are bound in the reverse order.
If one do:
PreparedStatement p = connection.prepareStatement(
"SELECT field FROM table WHERE first = ? and second = ?");
and then bind parameter 1 to "a" and parameter to "b":
p.setString(1, "a");
p.setString(2, "b");
then executing p yields the same results as executing
SELECT field FROM table WHERE first = "b" and second = "a"
although it should be equivalent to
SELECT field FROM table WHERE first = "a" and second = "b"
The bug is present only in "thin" Oracle JDBC driver. Changing
driver to "oci8" solves the problem.
* Version and platform info:
I detected the bug using Oracle 8.0.5 server for Linux.
According to $ORACLE_HOME/jdbc/README.doc that is
Oracle JDBC Drivers release 8.0.5.0.0 (Production Release)
* The program below:
The program below illustrates the bug by creating dummy two
column table, inserting the row into it and then selecting
the contents using prepared statement. Those operations
are performed on both good (oci8) and bad (thin) connections,
the results can be compared.
You may need to change SID, listener port and account data
in getConnecton calls.
Sample program output:
$ javac ShowBug.java; java ShowBug
Output for both connections should be the same
--------------- thin Driver ---------------
[ Non parametrized query: ]
aaa
[ The same - parametrized (should give one row): ]
[ The same - with buggy reversed order (should give no answers):
aaa
--------------- oci8 driver ---------------
[ Non parametrized query: ]
aaa
[ The same - parametrized (should give one row): ]
aaa
[ The same - with buggy reversed order (should give no answers):
--------------- The end ---------------
* The program itself
import java.sql.*;
class ShowBug
public static void main (String args [])
throws SQLException
// Load the Oracle JDBC driver
DriverManager.registerDriver(new
oracle.jdbc.driver.OracleDriver());
System.out.println("Output for both connections should be the
same");
Connection buggyConnection
= DriverManager.getConnection
("jdbc:oracle:thin:@localhost:1521:ORACLE",
"scott", "tiger");
process("thin Driver", buggyConnection);
Connection goodConnection
= DriverManager.getConnection ("jdbc:oracle:oci8:",
"scott", "tiger");
process("oci8 driver", goodConnection);
System.out.println("--------------- The end ---------------");
public static void process(String title, Connection conn)
throws SQLException
System.out.println("--------------- " + title + "
Statement stmt = conn.createStatement ();
stmt.execute(
"CREATE TABLE bug (id VARCHAR(10), val VARCHAR(10))");
stmt.executeUpdate(
"INSERT INTO bug VALUES('aaa', 'bbb')");
System.out.println("[ Non parametrized query: ]");
ResultSet rset = stmt.executeQuery(
"select id from bug where id = 'aaa' and val = 'bbb'");
while (rset.next ())
System.out.println (rset.getString (1));
System.out.println("[ The same - parametrized (should give one
row): ]");
PreparedStatement prep = conn.prepareStatement(
"select id from bug where id = ? and val = ?");
prep.setString(1, "aaa");
prep.setString(2, "bbb");
rset = prep.executeQuery();
while (rset.next ())
System.out.println (rset.getString (1));
System.out.println("[ The same - with buggy reversed order
(should give no answers): ]");
prep = conn.prepareStatement(
"select id from bug where id = ? and val = ?");
prep.setString(1, "bbb");
prep.setString(2, "aaa");
rset = prep.executeQuery();
while (rset.next ())
System.out.println (rset.getString (1));
stmt.execute("DROP TABLE bug");
null

Horea
In the ejb-jar.xml, in the method a cursor is closed, set <trans-attribute>
to "Never".
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name></ejb-name>
<method-name></method-name>
</method>
<trans-attribute>Never</trans-attribute>
</container-transaction>
</assembly-descriptor>
Deepak
Horea Raducan wrote:
Is there a known bug in Oracle JDBC thin driver version 8.1.6 that would
prevent it from closing the open cursors ?
Thank you,
Horea

JDBC thin driver for oracle 7.1.3

Hi,
we r using Oracle 7.1.3. i would like to know where i can get the
thin driver for java compatible with the oracle version 7.1.3 so
that i need not install an oracle client in the clients pc.
thanks
veera
null

Jay (guest) wrote:
: BUBBA (guest) wrote:
: : Veera Nagendran (guest) wrote:
: : : Hi,
: : : we r using Oracle 7.1.3. i would like to know where i can
: get
: : the
: : : thin driver for java compatible with the oracle version
: 7.1.3
: : so
: : : that i need not install an oracle client in the clients pc.
: : : thanks
: : : veera
: : Thedatabase you're using went out of support over 2 years
ago.
: : oracle doesn't provide jdbc drivers for anything less than
: : supported version 7.3.4.
: So why does Oracle make this claim
: "The Thin driver does not require Oracle software on the client
: side. It connects to any Oracle database of version 7.2.x and
: higher. The driver requires a TCP/IP listener on the server
: side. " ???
: Jay
re-read my earlier reply -- the comment was :
Thedatabase you're using went out of support over 2 years
ago. oracle doesn't provide jdbc drivers for anything less
than the minimum supported version ---> 7.3.4.At no time did i refer to the client s/w being required !!
also it was not tested against unsupported version of the
rdbms ...
also rdbms 7.1.3 isn't y2k compliant.
use it at your own risk..
what "claim" are you saying oracle made ??
null

JDBC thin 8.0.4 connect to Server 8.0.5?

Oracle:
I have a test application (not an applet) that executes correctly
connecting to an Oracle Server 7.X database using Oracle's JDBC
thin drivers. But when I try to connect to an Oracle Server
8.0.5 database, I receive an Oracle error:
ORA-01034: ORACLE not available
The environment for successful application execution is:
Oracle Server 7.X with a TCP Listener on Port 1521
Client workstation NT 4.0
SQL*Net Client is installed (N/A since we're using jdbc thin?)
Java 1.1.1
Oracle JDBC Thin Driver Release 8.0.4
Classes111.zip (7/10/98; 383,256 bytes)
The environment for the un-successful execution is:
Oracle Server 8.0.5 with a TCP Listener on Port 1521
Client workstation NT 4.0
SQL*Net8 Client is installed (N/A since we're using jdbc thin?)
Java 1.1.1
Oracle JDBC Thin Driver Release 8.0.4
Classes111.zip (7/10/98; 383,256 bytes)
Everything else is identical; the only difference is the Oracle
server (7.x vs 8.0.5). The jdbc drivers were downloaded from the
OTN web site. I've reviewed the jdbc documentation available and
reviewed other threads. Is the jdbc thin driver release 8.0.4
compatible with Oracle Server 8.0.5? Is there a more recent
release of Oracle's jdbc thin driver not published on the OTN web
site? Is there something else I should be looking at?
After successful test as an application, I will be testing this
as an applet. As an applet connecting to Server 7.x, it also
works correctly. I have not yet tried the applet connecting to
Server 8.0.5.
Thank you in advance,
Ed Vinarski
5/19/99
null

<BLOCKQUOTE>quote:<HR>Originally posted by Edward Vinarski ([email protected]):
Oracle:
I have a test application (not an applet) that executes correctly
connecting to an Oracle Server 7.X database using Oracle's JDBC
thin drivers. But when I try to connect to an Oracle Server
8.0.5 database, I receive an Oracle error:
ORA-01034: ORACLE not available
The environment for successful application execution is:
Oracle Server 7.X with a TCP Listener on Port 1521
Client workstation NT 4.0
SQL*Net Client is installed (N/A since we're using jdbc thin?)
Java 1.1.1
Oracle JDBC Thin Driver Release 8.0.4
Classes111.zip (7/10/98; 383,256 bytes)
The environment for the un-successful execution is:
Oracle Server 8.0.5 with a TCP Listener on Port 1521
Client workstation NT 4.0
SQL*Net8 Client is installed (N/A since we're using jdbc thin?)
Java 1.1.1
Oracle JDBC Thin Driver Release 8.0.4
Classes111.zip (7/10/98; 383,256 bytes)
Everything else is identical; the only difference is the Oracle
server (7.x vs 8.0.5). The jdbc drivers were downloaded from the
OTN web site. I've reviewed the jdbc documentation available and
reviewed other threads. Is the jdbc thin driver release 8.0.4
compatible with Oracle Server 8.0.5? Is there a more recent
release of Oracle's jdbc thin driver not published on the OTN web
site? Is there something else I should be looking at?
After successful test as an application, I will be testing this
as an applet. As an applet connecting to Server 7.x, it also
works correctly. I have not yet tried the applet connecting to
Server 8.0.5.
Thank you in advance,
Ed Vinarski
5/19/99<HR></BLOCKQUOTE>
Net8 introduces the notion of service name and dbname. I think the version of thin JDBC you are using expect a sid name. Do a lsnrctl serv and find out your sid name and pass it to the connect string for JDBC.
null

RMS installation error: JDBC-thin client oracle/jdbc/driver/T2CConnection.getLibraryVersionNumber()

Trying to Install RMS application 13.2.2 and I get past the pre-installation checks and when I get to the Data Source details and enter the data source details with the check box checked to validate the schema/Test Data Source I get the following error:
Error Connecting to database URL jdbc:oracle:oci:@rmsdbtst as user rms13 java.lang.Exception:UnsatisfiedLinkError encountered when using the Oracle driver. Please check that the library path is set up properly or switch to the JDBC thin client oracle/jdbc/driver/T2CConnection.getLibraryVersioNumber()
Checks performed:
RMS Application code location and directory contents:
[oracle@test-rms-app application]$ pwd
/binary_files/STAGING_DIR/rms/application
[oracle@test-rms-app application]$ ls -ltr
total 144
-rw-r--r-- 1 oracle oinstall   272 Dec 7 2010 version.properties
-rw-r--r-- 1 oracle oinstall   405 Jan 16 2011 expected-object-counts.properties
-rw-r--r-- 1 oracle oinstall   892 May 13 2011 ant.install.properties.sample
-rw-r--r-- 1 oracle oinstall 64004 Jun 6 2011 build.xml
drwxr-xr-x 9 oracle oinstall 4096 Jun 16 2011 rms13
drwxr-xr-x 3 oracle oinstall 4096 Jun 16 2011 installer-resources
drwxr-xr-x 3 oracle oinstall 4096 Jun 16 2011 antinstall
drwxr-xr-x 2 oracle oinstall 4096 Jun 16 2011 ant-ext
drwxr-xr-x 5 oracle oinstall 4096 Jun 16 2011 ant
-rw-r--r-- 1 oracle oinstall 11324 Dec 18 09:18 antinstall-config.xml.ORIG
-rwxr-xr-x 1 oracle oinstall 4249 Dec 18 10:01 install.sh
drwxr-xr-x 4 oracle oinstall 4096 Dec 18 10:06 common
-rw-r--r-- 1 oracle oinstall 16244 Dec 19 10:37 antinstall-config.xml
-rw-r--r-- 1 oracle oinstall   689 Dec 19 10:37 ant.install.log
[oracle@test-rms-app application]$
Application installation:
[oracle@test-rms-app application]$ ./install.sh
THIS IS the driver directory
Verified $ORACLE_SID.
Verified SQL*Plus exists.
Verified write permissions.
Verified formsweb.cfg read permissions.
Verified Registry.dat read permissions.
Verified Java version 1.4.2.x or greater. Java version - 1.6.0
Verified Tk2Motif.rgb settings.
Verified frmcmp_batch.sh status.
WARNING: Oracle Enterprise Linux not detected. Some components may not install properly.
Verified $DISPLAY - 172.16.129.82:0.0.
This installer will ask for your "My Oracle Support" credentials.
Preparing installer. This may take a few moments.
Your internet connection type is: NONE
Integrating My Oracle Support into the product installer workflow...
     [move] Moving 1 file to /binary_files/STAGING_DIR/rms/application
Installer preparation complete.
MW_HOME=/u01/app/oracle/Middleware/NewMiddleware1034
ORACLE_HOME=/u01/app/oracle/Middleware/NewMiddleware1034/as_1
ORACLE_INSTANCE=/u01/app/oracle/Middleware/NewMiddleware1034/asinst_1
DOMAIN_HOME=/u01/app/oracle/Middleware/NewMiddleware1034/user_projects/domains/rmsClassDomain
WLS_INSTANCE=WLS_FORMS
ORACLE_SID=rmsdbtst
JAVA_HOME=/u01/app/oracle/jrockit-jdk1.6.0_45-R28.2.7-4.1.0
Launching installer...
To make sure I have connectivity from the app server to the database (on a database server) here are the steps followed:
[oracle@test-rms-app application]$ tnsping rmsdbtst
TNS Ping Utility for Linux: Version 11.1.0.7.0 - Production on 19-DEC-2013 10:41:40
Copyright (c) 1997, 2008, Oracle. All rights reserved.
Used parameter files:
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = test-rms-db.vonmaur.vmc)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SID = rmsdbtst)))
OK (0 msec)
[oracle@test-rms-app application]$
[oracle@test-rms-app application]$ sqlplus rms13@rmsdbtst
SQL*Plus: Release 11.1.0.7.0 - Production on Thu Dec 19 10:46:18 2013
Copyright (c) 1982, 2008, Oracle. All rights reserved.
Enter password:
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@test-rms-app application]$
[oracle@test-rms-app application]$ ping test-rms-db
PING test-rms-db.vonmaur.vmc (192.168.1.140) 56(84) bytes of data.
64 bytes from test-rms-db.vonmaur.vmc (192.168.1.140): icmp_seq=1 ttl=64 time=0.599 ms
64 bytes from test-rms-db.vonmaur.vmc (192.168.1.140): icmp_seq=2 ttl=64 time=0.168 ms
64 bytes from test-rms-db.vonmaur.vmc (192.168.1.140): icmp_seq=3 ttl=64 time=0.132 ms
64 bytes from test-rms-db.vonmaur.vmc (192.168.1.140): icmp_seq=4 ttl=64 time=0.158 ms
64 bytes from test-rms-db.vonmaur.vmc (192.168.1.140): icmp_seq=5 ttl=64 time=0.135 ms
--- test-rms-db.vonmaur.vmc ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4001ms
rtt min/avg/max/mdev = 0.132/0.238/0.599/0.181 ms
[oracle@test-rms-app application]$
[oracle@test-rms-app application]$ uname -a
Linux test-rms-app.vonmaur.vmc 2.6.18-128.el5 #1 SMP Wed Jan 21 08:45:05 EST 2009 x86_64 x86_64 x86_64 GNU/Linux
[oracle@test-rms-app application]$
[oracle@test-rms-app application]$ cat /etc/*-release
Enterprise Linux Enterprise Linux Server release 5.3 (Carthage)
Red Hat Enterprise Linux Server release 5.3 (Tikanga)
[oracle@test-rms-app application]$
The database is created and all the batch file scripts have been successfully deployed. Now working on the application server. The Weblogic server is installed and 11g forms and reports are installed successfully.
Any help would be helpful.
Thanks,
Ram.

Please check MOS Notes:
FAQ: RWMS 13.2 Installation and Configuration (Doc ID 1307639.1)

JDBC server-side Default connection doesn't work

Hi folks
I am using Oracle 8.1.6 Personal Edition on Windows 2000 with JDK 1.2.2.
I can't connect to the database using the server side jdbc driver. Following is a simple program.
==============================================
import java.io.*;
import oracle.jdbc.driver.*;
class JdbcCheckup
public static void main (String args []) throws SQLException, IOException
// Load the Oracle JDBC driver
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver ());
Connection conn =
new oracle.jdbc.driver.OracleDriver ().defaultConnection ();
// Create a statement
Statement stmt = conn.createStatement ();
// Do the SQL "Hello World" thing
ResultSet rset = stmt.executeQuery ("SELECT 'Hello World' FROM dual");
while (rset.next ())
System.out.println (rset.getString (1));
System.out.println ("Your JDBC installation is correct."); }
==============================================
When I run it I get the following error...
Exception in thread "main" java.sql.SQLException: No suitable driver at java.sql.DriverManager.getConnection(DriverManager.java:477) at java.sql.DriverManager.getConnection(DriverManager.java:159) at oracle.jdbc.driver.OracleDriver.defaultConnection
(OracleDriver.java:2
65)
at JdbcCheckup.main(JdbcCheckup.java, Compiled Code)
All my PATH and CLASSPATH variables are pointing to the correct places. I wonder why JServer/JVM is not giving me the connection.
Thanks a bunch.
Govind
null

Hi,
Try using the complete database URL address in this manner:
import java.io.*;
import java.sql.*;
class JdbcCheckup
public static void main (String args [])
try {
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
Connection conn = DriverManager.getConnection("jdbc:oracle:thin:@<server_name>:1521:<database_sid>",
"<user_name>",
"<password>");
// Create a statement
Statement stmt = conn.createStatement ();
// Do the SQL "Hello World" thing
ResultSet rset = stmt.executeQuery ("SELECT 'Hello World' FROM dual");
while (rset.next ())
System.out.println (rset.getString (1));
System.out.println ("Your JDBC installation is correct.");
} catch (Exception e) {
e.printStackTrace();
}

Reading CLOB data using jdbc thin driver

Hi,
When I try reading data for a CLOB column using thin jdbc driver, I get the following error message
"Exception: ORA-06550: line 1, column 22:
PLS-00302: component 'GETCHUNKSIZE' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored".
This error message is displayed when the call is made to get the character stream from the Clob object.
Do I need to any server side setup before I can access CLOB data from the database?
thanks.
Puru Balakrishnan

I updated to the latest jdbc drivers, 816classes12b.zip, and the problem went away.
null

About jdbc-thin driver

I download oracle jdbc-thin driver to access oracle database
server,but it doesn't support unicode,why and how to resolve it?
thanks!!
null

Actually, the usage of the client-side and of the server-side thin driver is the same: the URL in both cases is specified in the same way.
The only difference is that you do not need to register the server-side Oracle JDBC driver with the Driver manager (though it will be a no-op if you do it).
When you want to run code in the server that executes in a particular session, you will use the server-side (or kprb) driver that gives you the connection associated with your session.
You have to use the server-side thin driver to establish a connection to a different database - something that is not the connection associated with your database
session.
Server-side thin driver connections can be used with JDBC as well as with SQLJ code.
null

Jdbc oracle jdbc-thin driver subname

I am working on Windows 2000 environment, using oracle8i 8.1.7 JDBC-Thin driver for use with JDK 1.2.x. The oralce8i 8.1.7 database is on another linux box. I can access the linux box through its ip address, but not by its hostname since it's not accessiable by the dns server. In my code, in the JDBCUrl, I used ip address instead of the hostname, e.g. "jdbc:oracle:thin:@10.0.113.108:1521:ora1". But I got the error like: "java.sql.SQLException: Io exception: The Network Adapter could not establish the connection". If I add a entry in my working machine's hosts file to map the hostname, I can fix the problem. But I don't know if this is the solution, or there is other better solutions.
Thanks
null

Using a hosts file entry is a common solution for problem where the dns lookup does not contain an entry for a RDBMS server platform.
The real solution is to resolve this issue :
"where the dns lookup does not contain an entry for a RDBMS server platform."

JDBC Thin Server-side Driver 8.1.6

Similar Messages

Maybe you are looking for