oracle No more data to read from socket ora-07445 [How to Solve]

This afternoon, a colleague from the original department came over and said that there was an environment that was about to go online. Occasionally, there was no more data to read from socket error. The version was Oracle, as follows:

After investigation, there are many reasons for this problem, including Oracle’s own bugs, possible configuration problems, and possible code problems. The main problems are as follows:

1. The minimum size of JDBC connection pool is 10, and the maximum size is 100. We can check the validity of the pool. This reason can be eliminated

2. It may be the cause of insufficient memory. Check the SAR history to eliminate this cause

3. It is possible to bind variable peeping problem, which can be set_ optim_ peek_ user_ Bind = false

Above reference:

For such problems, Oracle alert and trace are the first ones to be checked. According to the development feedback period, there are many dumps

There are the following types of ora-07445 in total

ORA-07445: exception encountered: core dump [pfr_ v3_ tab_ handler()+311] [SIGSEGV]

Bug10269022, executing a PL/SQL block dynamically that returns a ref cursor failures with ora-7445 [PFR]_ v3_ tab_ Handler] – superceded,

Ora-07445: exception occurred: core dump [ksuklms() + 316]

Confirmed bug 13322802, fix

ORA-07445: exception encountered: core dump [dbgrmqmqpk_ query_ pick_ key()+2033]

Confirmed bug 9390347, fix

ORA-07445: exception encountered: core dump [kocgpn2()+141] [SIGSEGV]

This error number does not find the corresponding bug record

Finally, let users upgrade to

In addition, it may be caused by the complexity of SQL. For example, if there is a with clause in SQL, and with refers to another with, it may also be solved after flattening

Similar Posts: