JDBC-thin on Solaris 2.7, 1002 on "FOR UPDATE NOWAIT"

Has there been a patch to allow SELECT... FOR UPDATE NOWAIT
in the jdbc thin connection layer?
I have a program which runs transactions against Oracle 7.3 or
8.05, and I'm finding that it works fine on my NT workstation
against, 7.3.4....
But when I run it against oracle 8.0.5 from a Solaris 2.7 system,
I'm getting ORA-1002 errors whenever I select for update nowait.
I'm oracle has a fix for this, but I haven't seen it yet.
I did see a message about BUG 597589 posted on 02-Sep-1998.
Was this ever fixed? The BUG database makes no mention of it.
The only work-around seems to be to set autocommit, but I suspect
that will lead to deadlocks in my application, if it even works!
Has anyone else dealt with this problem?
Thanks in advance,
Kevin Fries
null

Similar Messages

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

EXTPROC_CONNECTION_DATA from JDBC thin

I'm trying to connect to a database which uses external procedure libraries for some of it's PL/SQL functions. The documentation for the library mentions adding the following to the tnsnames.ora file. Is there a way using the Oracle JDBC thin driver to specify this same information for a JDBC URL without requiring a tnsnames.ora file?
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = extproc))
(CONNECT_DATA =
(SID = PLSExtProc)
Thanks,
Paul

The DBA had not configured the server correctly. When that was done there was no change required on the client.

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

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

Oracle 8 JDBC thin driver for tomcat

Hi all,
I have tomcat3.3 installed on HP UNIX with java version "HP-UX Java C.01.18.05"
I need to connect to an oracle 8 database using a Oracle JDBC thin driver. Where can I obtain this driver? How to install and configure it for the tomcat application?
Thanks for your help.
Regards
Shriram

If you go to the link which the last person posted, http://technet.oracle.com/software/tech/java/sqlj_jdbc/content.html, there is no indication for HP-UX. The only OS it lists are NT and Solaris. Does anyone know if these versions will work on HP-UX?
Please help.
Thanks,
Sam

JDBC Thin & NLS & Linux

I wrote Java application, which uses JDBC Thin 8.1.5 and runs on
Linux. When I inserts Russian text into table, JDBC inserts some
undefined (big black boxes in SQLPLUS output) characters. Output
from same table in my Java application seems to "???".
Oracle database (8.1.5 on RedHat 6.0) created in CL8KOI8R
charset.
All environment variables are valid:
NLS_LANG=RUSSIAN_CIS.CL8KOI8R
LC_ALL=ru_RU
CLASSPATH includes path to nls_charset11.zip
Russian works fine in SQLPLUS and Perl DBD::Oracle applications
on the same machine.
What I can do?
null

Have you tried more recent JDBC versions? Several NLS issues were fixed in post 8.1.5 JDBC releases (including, I believe, a problem with Hebrew). The JDBC folks would be able to give you more specific information about where which fixes appeared.
It should be worth a try, though, to check out a newer JDBC version, particularly if you are using the thin driver.

Does oracle 8.1.6.0 jdbc thin driver support jdk1.3 and oracle 8.0.5 database ?

I have downloaded oracle 8.1.6.0 jdbc thin driver(named classes12.zip) to run with jdk1.3 to access oracle 8.0.5, but when I compile and run the jdbccheckup.java downloaded from oracle website like this:
javac -classpath d:\jdbc\classes12.zip jdbccheckup.java
(compile succeed)
java -classpath d:\jdbc\classes12.zip jdbccheckup
an error occured:
Exception in thread "main" java.lang.NoClassDefFoundError:jdbccheckup
Why??????

Try this isntead.
java -classpath d:\jdbc\classes12.zip;. jdbccheckup
an error occured:
Exception in thread "main" java.lang.NoClassDefFoundError:jdbccheckup
Why??????

JDBC thin drivers for oracle 8.0.5 for linux

I want to use Java SDK 1.2.2 and need the oracle thin drivers.
I have trouble with the 816 thin drivers connecting to the 8.0.5
server.
when using statement.executeQuery(..... I get the following
Exception.
Exception error: java.sql.SQLException: ORA-03120: two-task
conversion routine:integer overflow
I think my solution is to upgrade to a 8.1.6 server or use the
java 1.1.6 driver on the JDK1.1.6
I tried downoading the 8.1.5 enterprise server but this fails to
complete.
Can someone help me to this version on CDROM or to the JDBC thin
driver for the 8.0.5 server?
null

You must include "classes12.zip" instead of "classes111.zip".
Since "classes111.zip" is required only for Java 1
and "classes12.zip" is required for Java 2 which means from J2SE 1.2 on forward.
In adition you might need to inlcude "nls_charset12.zip" as well. Try it first without and if it is not working include it as well.
The required files can you get from the OTN.
This should help
Roger

Local oracle access with jdbc thin

hello there
it need help despratly,
im developing an applet to talk to remote oracle dbs using jdbc
thin
but i also want an applet to be able to talk to a local oracle db
on the same hardisk.
for a remote connection the follwing stringis used at my
university
static final String connect_string =
"jdbc:oracle:thin:scott/[email protected]:1521:DSC1";
but what do i subsitute for thr host as i want to access the db
on my hard disk?
i need as much help ASP, as im well behind my schedule for this
project.?
also i take it that to allow this and access to remote servers
other than the web server, the applet needs to be signed, is this
possible with jdk1.1.x compatble browsers?
yours
richard sergio marchesi
email - [email protected]
or
email - [email protected]
null

The thin driver reqiures a TCP listener to be running. If you are
using Personal Oracle for the 'local' RDBMS then it doesn't have
a listener (with the default installation). Start the listener
and you should be able to connect. You will also want a local
webserver of some sort to serve the applet to you as well, but
anything (even TinyWeb) will do for that.
null

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

Bug in Oracle JDBC thin driver 8.1.6 ?

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

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

Changes to JDBC Thin URL (: vs /)

Since 10g, the JDBC Thin URLs have been documented to take the form jdbc:oracle:thin:scott/tiger@//myhost:1521/myservicename. However the old style URLs which uses : instead of / (for example jdbc:oracle:thin:scott/tiger@myhost:1521:myservicename) continues to work even in Oracle 11g.
Do we know if the support for the old style URLs will be taken off anytime so. There is no document suggesting this, but more & more examples and documentation seem to point towards the / style strings.
One exception case is when the target database is running under Real Application Cluster environment, where-in the old style URLs doesn't work.
Thanks for your help.
Alex

Welcome to the forum!
>
Since 10g, the JDBC Thin URLs have been documented to take the form jdbc:oracle:thin:scott/tiger@//myhost:1521/myservicename. However the old style URLs which uses : instead of / (for example jdbc:oracle:thin:scott/tiger@myhost:1521:myservicename) continues to work even in Oracle 11g.
>
What does 'continues to work even in Oracle 11g' mean? The URL syntax is specific to the JDBC driver jar version being used, not the version of the database.
>
Do we know if the support for the old style URLs will be taken off anytime so. There is no document suggesting this, but more & more examples and documentation seem to point towards the / style strings.
One exception case is when the target database is running under Real Application Cluster environment, where-in the old style URLs doesn't work.
>
No one but Oracle knows.
Oracle 9i was the last version to document the old-style syntax using a colon to separate the database name.
You should use the documented syntax for the version of the JDBC driver that is being used. As you noted since 10g that has been to use the forward slash.
It is also recommended to use DataSource. That class has 'setters' to set the properties (e.g. 'setDatabaseName') and the syntax issue doesn't even arise.
Sounds like you may already have read the 'Database URLs and Database Specifiers section of the JDBC Dev Guide but for others who haven't:
http://docs.oracle.com/cd/B28359_01/java.111/b31224/urls.htm#BEIJFHHB

JDBC THIN CLIENT in V$SESSION inactive

Hello DBA's
I have too many inactive session of JDBC thin client. Please suggest can we kill them?? or any other alternative
SID SERIAL# USERNAME PROGRAM STATUS Inactive_Hours
12 74 APPS JDBC Thin Client INACTIVE 1772.69806
13 31 APPLSYSPUB JDBC Thin Client INACTIVE 1772.69806
18 62 APPS JDBC Thin Client INACTIVE 1772.69806
20 1 APPLSYSPUB JDBC Thin Client INACTIVE 952.465556
22 9 APPS JDBC Thin Client INACTIVE 1772.69806
26 55 APPS JDBC Thin Client INACTIVE 92.1361111
30 2 APPLSYSPUB JDBC Thin Client INACTIVE 1772.61361
31 7 APPS JDBC Thin Client INACTIVE 1772.69667
53 29516 APPS JDBC Thin Client INACTIVE 521.344167
54 35 APPLSYSPUB JDBC Thin Client INACTIVE 1772.69278
69 7 APPLSYSPUB JDBC Thin Client INACTIVE 1772.69278
Can we kill them or any particular check before killing them??

I am not sure how you have computed the "Inactive Time".
You need to know if the middle-tier is configured to re-connect when necessary OR whether the middle-tier process will fail at the next SQL / operation it attempts to execute. So middle-tier processes can handle a kill gracefully, others cannot.
The usernames you list indicate that this is an Oracle EBusiness Suite install. You need to identify the services on the application server that correspond to these sessions and whether they can handle a kill gracefully.
Why do you need to kill sessions ?
Hemant K Chitale

Error Code Definition for JDBC Thin driver

Would like to know where I can find the definition of error codes
for JDBC thin driver to Oracle 7 database. Right now, when I have
database errors, I get SQL execption with CODE=XXXXXX. Need to
know the definition of the error codes in order to decide whether
the application shall retry or quit or do something else. Thank
you in advance.
null

Hi,
thin client session Language is controlled by java Locale.
Based on testing code, ORA- messages are localized after the connection is successfully established. ORA- messages returned in the middle of connecting are in instance language.
So, as far as I can say, you need to catch exceptions from DriverManager.getConnection(url, info); and translate them on your own.
Once the connection is successfully returned, ORA- message language is defined by java Locale.
Tests were performed on Oracle 10gR2 (both thin driver and DB).

JDBC-thin on Solaris 2.7, 1002 on "FOR UPDATE NOWAIT"

Similar Messages

Maybe you are looking for