opiino: Attach failed! error=-1 ifvp=0

"Opiino: Attach Failed! Error=-1 Ifvp=0" Written In Udump File [ID 399727.1]


Applies to:

Oracle Server - Enterprise Edition - Version: to
Oracle Net Services - Version: to
This problem can occur on any platform.
Checked for relevance on 01-MAY-2008.

There are multiple causes of this error together with solutions, so more will be added as they are discovered.


1. On a system that contains multiple databases of different versions, you might notice that one or more databases are receiving many trace files every minute (40-50 for example) generated in the $ORACLE_HOME/udump area. Each dump file might be ~500 bytes and contain the following information:
opiino: Attach failed! error=-1 ifvp=0
The listener.log file may also contain any of the following errors:

TNS-12500: TNS:listener failed to start a dedicated server process
TNS-12586: Message 12586 not found; product=network; facility=TNS
TNS-12518: TNS:listener could not hand off client connection

2. Alternatively, if there is only one database and listener version on the Server, you might only receive a database dump file in the UDUMP location containing either of the following:
opiino: Attach failed! error=-1 ifvp=0
opiino: Attach failed! error=-1 ifvp=(nil)


The Server might contain a mix of 9.2 and 10.2 databases and one of the listeners running may be a 9.2 version.


There may be instability with either the network or the front-end application / program.


1. The error is being caused by an abnormal disconnection at the network level between the client connection request and the failure of the database to allow that connection (sometimes resulting in the listener log's ORA-12500 error).
The reason for the disallowing of the connection, is due to the fact that a higher version of the Oracle Database is being serviced (Static or Dynamic) by a lower version of the Oracle TNS Listener.
This can be checked through the listener's log which shows the higher version database showing with connection errors.
2. If there is an abnormal disconnection between the client and server processes, then the Database dump error can occur.
A common cause is an abnormal termination by the physical Network or external component, such as an application or program.


To implement a possible solution, please execute the following steps:

1. For multiple mixed versions:

a) If you only have one listener running on a multiple database version machine (such as 10.2 and
9.2, for example), then use the highest version listener (10.2), started out of the highest version home (10.2),
and service both the higher and lower versions of database.

b) Alternatively, if you have more than one listener version, then have each listener service
their own versions of the databases.
Maintain a rule of "higher version listener for the same or lower version database" though.

     1) To ensure this, make sure that the listener.ora file's SID_LIST (if used) only has the databases it should
      listen for and not something higher.

    2) Also, make sure that the databases have a LOCAL_LISTENER parameter pointing to their OWN
      listener address.

2. Alternatively, if you do not have a mix of Oracle versions for the Listener or Database, then turn on SUPPORT level tracing (starting with the TNSListener) and see whether this is client or server generated. See Note:219968.1 for details on tracing.
3. Also, if the error occurs AFTER the listener has handed off the client process to the Database Server, and if there are no errors in the listener log, then this error is most likely caused by an abnormal termination and reported at the Database level. SQL*Net Server tracing would be beneficial if these errors occur frequently. Also, try and isolate the potential cause by seeing which application or client process is also experiencing terminations at the same time.

Niciun comentariu:

Trimiteți un comentariu