4 Replies Latest reply: Apr 9, 2013 12:36 AM by Billy~Verreynne RSS

    Error report: No more data to read from socket

    1001676
      Hi,
      When i am trying to put a chuck of data into a nested table it is giving below error.

      Does anybody has any idea about how to overcome this error.Below is the information about my Oracle Version.

      Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production

      Thanks and Regards,
      Ratikanta
        • 1. Re: Error report: No more data to read from socket
          AlbertoFaenza
          Hi,

          welcome to the forum.

          Please read SQL and PL/SQL FAQ

          You did not provide enough information. Can you post sample data (CREATE TABLE and INSERT statements), the code you are executing and the error your are getting?

          Please when you post some code or output please enclose it between two lines starting with {noformat}
          {noformat}
          
          i.e.:
          {noformat}
          {noformat}
          SELECT ...
          {noformat}
          {noformat}
          
          Regards.
          Al                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    
          • 2. Re: Error report: No more data to read from socket
            Billy~Verreynne
            Sounds like an ORA-600 or ORA-7445, occurred in the Oracle server process, servicing that client session.

            The server process terminates abnormally (writing errors to the instance's alert log and trace/core dump files) - and tears down its side of the TCP socket connection. The client process then runs into a socket error when attempting to communicate with the now non-existent server process.

            The typical OCI driver error on the client is an ORA-3113 (eof on communication channel).

            You need to determine the actual Oracle client driver error, or assuming it is a ORA-3113, look on the server for the reason the server process terminated (starting with the alert log messages).
            • 3. Re: Error report: No more data to read from socket
              1001676
              Hi Bill,
              Thanks for the impromptu response. But could you please tell me the commands or the query about how to look abt the issue in server. I am running this from sql developer count.

              If any other information is required, kindly revert.

              Thanks and Regards,
              Ratikanta
              • 4. Re: Error report: No more data to read from socket
                Billy~Verreynne
                You need to talk to your DBA. There is a command line utility called adrci (Automatic Diagnostic Repository Command Interpreter) that can be used to determine the server error, and package it for Oracle Support to look at, via a SR (Service Request).

                In the case of an ORA-600/ORA-7445 error, Oracle Support/Metalink (support.oracle.com) has a troubleshooting tool that can assist you in determining the bug, and whether there are workarounds or patches available.

                Your DBA should be familiar with these.

                Alternatively, you need to try and isolate the error on your side, by changing the instructions (SQL and/or PL/SQL) you send to the server to execute. It could be that the specific combination of instructions and the data used, triggers a bug or unhandled exception.