I have seen this communication break channel error in one of my database. By doing all analysis about this error. I have learned few interesting things and wants to share with you all.
First I would like to Thank Mr Roy blog. This blog was clearly explaining about commutation break channel error.
But being Oracle DBA, I want to share few more things.
As Roy. The communication break channel will occur few possibility's.
a. Network timeout between application server and database server.
b. SQL Query cross the specified timeout value from web services like tomcat Or JDBC connection.
c. Or if client JDBC Thin driver use lower version to compare the oracle version then you might need to upgrade the JDBC Thin driver.
Example. Your database running 188.8.131.52 and JDBC Thin driver use lower version then there should be some bug from Oracle. There is one patch recommended by Oracle and needs to apply into JDBC Thin from you're client site.
But based on my experience by increasing the timout value from JDBC Thin statement timeout and Apache Tomcat timeout value only help to avoid the ORA-03111 communication channel break error but this will NOT help you out the real problem.
The critical / Onair application the SQL Query execution should be < 1 min [ For example <=30 Sec ], If this query takes more than >=30 sec then you should get this error..
Please have a look your AWR , ADDM reports and find the if any SQL Query takes more than 1 min .
Please let me know if your thougts and feedback.