Traces Written Containing ' opiino: Attach failed! error=-1 ifvp=0000000000000000' [ID 1214775.1] | |||||
| |||||
수정 날짜 24-NOV-2010 유형 PROBLEM 상태 MODERATED |
In this Document
Symptoms
Cause
Solution
This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review. |
Applies to:
Oracle Net Services - Version: 10.2.0.1 to 10.2.0.4.0 - Release: 10.2 to 10.2Information in this document applies to any platform.
Symptoms
Comments
--------
=== ODM Issue Clarification ===
Traces are written regularly in the user_dump_dest containing just the error 'opiino: Attach failed! error=-1 ifvp=0000000000000000'.
The application running against this database is EBS 11.5.1.0.2 and, when EBS is stopped, the traces do not appear. SQL*Net tracing shows that the connections producing the traces are JDBC connections.
Cause
The exact cause of this was not determined but it is likely that some client connections were not closing cleanly.
Solution
The traces can be stopped by setting the following parameters:
listener.ora:
INBOUND_CONNECT_TIMEOUT_PROD = 120
sqlnet.ora
SQLNET.INBOUND_CONNECT_TIMEOUT = 120
SQLNET.SEND_TIMEOUT = 120
SQLNET.RECV_TIMEOUT = 120
However setting these can cause some EBS connections to fail with TNS-12537, TNS-12560, TNS-507.
The traces were finally stopped by applying ATG.6 to EBS.
관련 자료 제품
|
'ORACLE > TroubleShooting' 카테고리의 다른 글
ORA-4031 unable to allocate … shared memory 오라클(Oracle) (0) | 2011.11.14 |
---|---|
ORA-4031 진단 (0) | 2011.11.14 |
"opiino: Attach failed! error=-1 ifvp=0" (0) | 2011.09.26 |
How to Disable Asynch_io on HP to Avoid Ioctl Async_config Error Errno = 1 (0) | 2011.07.04 |
ora 4031 에러 처리 방안 (0) | 2011.06.02 |