aspose file tools*
The moose likes JDBC and the fly likes Strange problem cause the connection failed in close Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Databases » JDBC
Bookmark "Strange problem cause the connection failed in close" Watch "Strange problem cause the connection failed in close" New topic
Author

Strange problem cause the connection failed in close

Zee Ho
Ranch Hand

Joined: Jul 20, 2004
Posts: 128
Hi, everybody, Can any one help me on this. Now I am developed a program to scan all the record in the database, but when reading one record(which is CLob type) cause me failed in close the connection.

It throws out.

java.sql.SQLException: Protocol violation
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
at oracle.jdbc.dbaccess.DBError.check_error(DBError.java:1160)
at oracle.jdbc.ttc7.Ocommoncall.receive(Ocommoncall.java:149)
at oracle.jdbc.ttc7.TTC7Protocol.rollback(TTC7Protocol.java:488)
at oracle.jdbc.driver.OracleConnection.rollback
(OracleConnection.java:1412)
at com.core.esg.database.NonAutoCommitConnection.close
(NonAutoCommitConnection.java:169)
at com.core.esg.database.DBUtility.close(DBUtility.java:441)
at com.core.esg.sanity.grabber.ColumnsGrabber.destroy
(ColumnsGrabber.java:39)
at com.core.esg.sanity.SanityModel.destroy(SanityModel.java:422)
at com.core.esg.sanity.SanityModel.processCustomChecker
(SanityModel.java:98)
at com.core.esg.sanity.SanityModel.sanityCheck(SanityModel.java:70)
at com.core.idex.sanity.SanityRunner.main(SanityRunner.java:31)
2004-10-27 20:18:41,320 [main] [com.core.idex.sanity.SanityRunner] INFO - ----

I know when invoking the clob.length() may cause such problem, but It has already been fixed in 9.2.0.3.0(which is my current version)

I think It might cause by the encoding problem, there are some very strange characters in the record, when you select the record by sqlplus and you can see thousands of character(if you set the environment long enough your sqlplus will crash), but when I read the length using the clob.length(), it return me 150. check the record use TOAD you can
only see several characters there. copy it you will get another corrupt record. and reading such record will cause your connection fail in close(why? strange, the exception throws out when I invoke the connection.close())

pls give me some idea on how to handle with it.


SCJP 1.4<br />SCWCD 1.3<br />SCJD<br />SCBCD<br />IBM Xml Cert in progress
Bear Bibeault
Author and ninkuma
Marshal

Joined: Jan 10, 2002
Posts: 61648
    
  67

"ZeeHo",

We're pleased to have you here with us here on the Ranch, but there are a few rules that need to be followed, and one is that proper names are required. Please take a look at the JavaRanch Naming Policy and adjust your display name to match it.

In particular, your display name must be a first and a last name separated by a space character, and must not be obviously fictitious.

Thanks!
bear
Forum Bartender


[Asking smart questions] [Bear's FrontMan] [About Bear] [Books by Bear]
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Strange problem cause the connection failed in close