Cause analysis of SQL net message from client event

When viewing database wait events , Find out SQL* Net message from client The longest waiting time , In fact, this is oracle Idle waiting time , As long as there is no problem with the network , You don't have to test this wait.
Here are the reference documents ：
1. For one session Come on , All the time wait The state of .
WAIT FOR IO / WAIT FOR CPU / WAIT FOR LATCH /WAIT FOR ...
You can Query v$session_wait, There is always data.
2. about Server process Come on , But after it's done with everything it needs to deal with , It goes into another WAIT, SQL* Net message from client , Waiting for the Cilent Send a message to it to deal with , And we put this wait be called ildel event, It doesn't mean real loading
3. For example , You are at work? , for instance 1：00-1：30 Checking DB state ,1:30 - 2:00 Reading document . however , Sometimes you have nothing to do , At this time, the boss asked you what you were doing , You will say , I'm waiting for the task , It's actually resting , It's equivalent to you wait for " Mission from Boss “, It's actually resting , No loading.
4. Of course, there are other situations , such as , You rest in your seat （wait for " Mission from Boss “ ） , It should have been idle Of . But after a while , Your boss came , stamp with rage ：“ I just wanted to ask you out to buy Coffee , Why did you call for a long time and no one answered “, You check , It turned out that the extension was not connected properly . In this case （wait for " Mission from Boss “ ） It's not normal . phase Corresponding Oracle The problem in the Internet is that the network is not smooth ,Client Want to send a message to Server process, It didn't work , and Server process Has always been a wait for SQL*Net message from client .
5. Conclusion , As long as the network is OK .SQL*Net message from client This wait Never mind .