SQL * Net message from client event Cause Analysis

SQL * Net message from client event Cause Analysis Today, my colleague runs Program , Modify the table content, but the running half is always suspended. query the database to see what is waiting, query v $ session_waitselect S. Sid,
S. Serial #,
S. username,
S. status,
S. machine,
S. program,
S. module,
A. SQL _text
From v $ session s,
V $ sqlarea
Where S. username is not null
And S. SQL _address = A. Address saw the colleague's session hanging there. SQL * Net Message From Client The longest waiting time is actually the free waiting time of Oracle. As long as there is no problem with the network, you do not need to evaluate this wait. Later, my colleague modified the program and passed it. He did not respond because he executed a large query. The following is a reference document: 1. For a session, it is in the wait status every moment.
Wait for IO/Wait for CPU/Wait for latch/wait...
You can query v $ session_wait. There is always data.

2. for server process, after processing all the things to be processed, it enters another wait,SQL*Net Message From ClientWait for the cilent to send the information for processing, and we call this wait ildel event, which does not mean the real loading

3. For example, you are at work. For example, you are checking the database status from to, and you are reading the document from. However, sometimes you have nothing to do. When the boss asks you what you are doing, you will say that I am waiting for the task. In fact, I am resting, which is equivalent to your wait for "task.FromThe boss ", in fact, is resting, that is, there is no loading.

4. of course, there are other situations. For example, you should have idle to take a rest in your seat (wait for "task from boss. However, after a while, your boss ran around and burst into a storm: "I just wanted to ask you to go out to buy a coffee, but no one answered the call after half a day." You checked it and it turned out that the extension was not answered. In this case (wait for "task from boss") is not normal. In Oracle, the network is poor. client wants to send a message to server process. The result is unsuccessful, server process is always wait for SQL * net message from client .
5. conclusion: as long as the network is okay. SQL * net message from client do not worry about this wait.