Oracle Sql Error 17410 Sqlstate Null
log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn sql error 17008 sqlstate 99999 more about Stack Overflow the company Business Learn more about hiring developers or posting
Sql Error: 17008, Sqlstate: 08003
ads with us Database Administrators Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is a question sql error 0 sqlstate null hibernate and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute: Sign up Here's how it works: Anybody can sql error: 17410, sqlstate: 08000 ask a question Anybody can answer The best answers are voted up and rise to the top oracle: No more data to read from socket up vote 3 down vote favorite 1 We are using Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 and we have an error on a query that gives us the error Error: No more data to read from socket SQLState: null ErrorCode: 17410 The query
No More Data To Read From Socket Oracle 11g
is similar to the following select * from ( select ... from table inner join left outer join left outer join inner join where string1='value1' and string2='value2' ) where rownum > 500 and rownum < 510 If I try to remove the final where statement the query runs fine. Also if I try to "reduce" the rownum filter to a lower level of records the query runs fine: where rownum<10 Searching on internet I have found that it could be caused by the parameter "cursor_sharing" to "similar" that seems buggy on some version of oracle. I tried to set it to "exact" but unfortunately I have the same error. I was wondering if the retrieved data of a select statement may have a limit in bytes in oracle10g but I haven't found anything. I have found a limit on oracle8i but nothing to oracle10g. We have the same problem executing the query on different client (dbvisualizer, squirrel) and on oracle console. oracle-10g share|improve this question asked Nov 9 '11 at 9:43 egesuato migrated from serverfault.com Nov 9 '11 at 16:02 This question came from our site for system and network administrators. 1 "No more data to read from socket" usually me
Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.
messages, then lists general JDBC error messages and TTC error messages that the Oracle JDBC drivers can return. The appendix is organized as follows: https://docs.oracle.com/cd/B10501_01/java.920/a96654/ermesap.htm General Structure of JDBC Error Messages General JDBC Messages TTC Messages Each of the two message lists is first sorted by ORA number, and then alphabetically. For general information about processing JDBC exceptions, see "Processing SQL Exceptions". General Structure of JDBC Error Messages The general JDBC error message structure allows runtime information to be appended to the end of sql error a message, following a colon, as follows: : For example, a "closed statement" error might be output as follows: Closed Statement:next This indicates that the exception was thrown during a call to the next() method (of a result set object). In some cases, the user can find the same information in a stack trace. General JDBC Messages This section 0 sqlstate null lists general JDBC error messages, first sorted by ORA number, and then alphabetically. JDBC Messages Sorted by ORA Number ORA Number Message ORA-17001 Internal Error ORA-17002 Io exception ORA-17003 Invalid column index ORA-17004 Invalid column type ORA-17005 Unsupported column type ORA-17006 Invalid column name ORA-17007 Invalid dynamic column ORA-17008 Closed Connection ORA-17009 Closed Statement ORA-17010 Closed Resultset ORA-17011 Exhausted Resultset ORA-17012 Parameter Type Conflict ORA-17014 ResultSet.next was not called ORA-17015 Statement was cancelled ORA-17016 Statement timed out ORA-17017 Cursor already initialized ORA-17018 Invalid cursor ORA-17019 Can only describe a query ORA-17020 Invalid row prefetch ORA-17021 Missing defines ORA-17022 Missing defines at index ORA-17023 Unsupported feature ORA-17024 No data read ORA-17025 Error in defines.isNull () ORA-17026 Numeric Overflow ORA-17027 Stream has already been closed ORA-17028 Can not do new defines until the current ResultSet is closed ORA-17029 setReadOnly: Read-only connections not supported ORA-17030 READ_COMMITTED and SERIALIZABLE are the only valid transaction levels ORA-17031 setAutoClose: Only support auto close mode on ORA-17032 cannot set row prefetch to zero ORA-17033 Malformed SQL92 string at position ORA-17034 Non