Home » Developer & Programmer » JDeveloper, Java & XML » Io exception: SO Exception was generated
Io exception: SO Exception was generated [message #471569] Mon, 16 August 2010 03:43 Go to next message
rikslovein
Messages: 3
Registered: August 2010
Junior Member
Hi,

I've written a simple PingDB program which gives the exception given below:


java.sql.SQLException: Io exception: SO Exception was generated

The code written is :


Class.forName("oracle.jdbc.driver.OracleDriver");
conn = DriverManager.getConnection("jdbc:oracle:thin:@(PMASTI.WORLD=(DESCRIPTION=(SDU=32768)(enable=broken)(LOAD_BALANCE=yes)(ADDRESS=(PROTOCOL = TCP)(HOST=<name_of_primary_host>)(PORT=1525))" +
"(ADDRESS=(PROTOCOL=TCP)(HOST=<name_of_sec_host>)(PORT=1525))(CONNECT_DATA=(SERVICE_NAME=PMASTI))))", uname, passwd);

Any solutions?

Thanks in advance...

regards...
Re: Io exception: SO Exception was generated [message #471578 is a reply to message #471569] Mon, 16 August 2010 04:01 Go to previous messageGo to next message
Michel Cadot
Messages: 59299
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Insufficient data to compute.

Post more details of your error.

Regards
Michel
Re: Io exception: SO Exception was generated [message #471583 is a reply to message #471578] Mon, 16 August 2010 04:09 Go to previous messageGo to next message
rikslovein
Messages: 3
Registered: August 2010
Junior Member
Here is the complete stack trace I'm getting from the code...

java.sql.SQLException: Io exception: SO Exception was generated
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:333)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:404)
at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:468)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:314)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at com.pkg.productfinder.core.PingDB.main(PingDB.java:14)

where Line 14 in PingDB is the code I've posted above...

I do not have any other logs from oracle side as it's the dedicated server...

Thanks for your reply...

Regards
Re: Io exception: SO Exception was generated [message #471593 is a reply to message #471583] Mon, 16 August 2010 04:22 Go to previous messageGo to next message
Michel Cadot
Messages: 59299
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
But we still have not the original Oracle error.

Regards
Michel
Re: Io exception: SO Exception was generated [message #471716 is a reply to message #471593] Tue, 17 August 2010 00:14 Go to previous messageGo to next message
rikslovein
Messages: 3
Registered: August 2010
Junior Member
Ok.... Here I go again...
Finally I solved the issue: Instead of using the connection URL given above I've used the Service Format. Like, ("jdbc:oracle:thin:@//" + pmHost + ":1525" + "/" + dbName, userName, password).

But, I've few query regarding this:
1> When should I go for SID format and when should I go for Service Format? Because, now I've two hosts out of which one works with SID format and other one works with Service format.
2> As you can see above, the URL uses load balancing, providing just one of the two servers in the URL(the Service Format URL) am I be benefited with load balancing? If no, how can I take the advantage of it using Service Format?
3> Sometimes, my host gives me this: ORA-00257: archiver error. Connect internal only, until freed. What does this mean? and how can I solve this?

Hope I'm clear this time.

Regards.
Re: Io exception: SO Exception was generated [message #471727 is a reply to message #471716] Tue, 17 August 2010 01:12 Go to previous message
Michel Cadot
Messages: 59299
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
3/

ORA-00257: archiver error. Connect internal only, until freed.
 *Cause:  The archiver process received an error while trying to archive
         a redo log.  If the problem is not resolved soon, the database
         will stop executing transactions. The most likely cause of this
         message is the destination device is out of space to store the
         redo log file.
 *Action:  Check archiver trace file for a detailed description
          of the problem. Also verify that the
         device specified in the initialization parameter
         ARCHIVE_LOG_DEST is set up properly for archiving.


Regards
Michel
Previous Topic: problem in dbms_XMLDom
Next Topic: ORA-29532 when using Callablestatement.execute()
Goto Forum:
  


Current Time: Thu Oct 02 13:02:39 CDT 2014

Total time taken to generate the page: 0.12725 seconds