用户的现场数据库出现问题:

ORA-25254: time-out in LISTEN while waiting for a message

FATAL ERROR IN TWO-TASK SERVER: error = 12152

上面这个问题直接导致了数据库 restart了

版本: 10.1.0.2

检查DUMP文件:

[@more@]

Thu Mar 25 13:16:11 2010
Errors in file e:oracleproduct10.1.0adminjkdbudumpjkdb_ora_2960.trc:
ORA-25254: time-out in LISTEN while waiting for a message
ORA-06512: at "SYS.DBMS_AQ", line 577
ORA-06512: at "SYSMAN.EMD_NOTIFICATION", line 492
ORA-06512: at line 1

Thu Mar 25 13:19:01 2010
Errors in file e:oracleproduct10.1.0adminjkdbudumpjkdb_ora_2304.trc:
ORA-25254: time-out in LISTEN while waiting for a message
ORA-06512: at "SYS.DBMS_AQ", line 577
ORA-06512: at "SYSMAN.EMD_NOTIFICATION", line 492
ORA-06512: at line 1

===============================================

Dump file e:oracleproduct10.1.0adminjkdbudumpjkdb_ora_2304.trc
Thu Mar 25 13:18:30 2010
ORACLE V10.1.0.2.0 - Production vsnsta=0
vsnsql=13 vsnxtr=3
Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
Windows Server 2003 Version V5.2 Service Pack 1
CPU : 8 - type 586, 2 Physical Cores
Process Affinity: 0x00000000
Memory (A/P) : PH:2967M/4094M, PG:4987M/5971M, VA:1247M/2047M
Instance name: jkdb

Redo thread mounted by this instance: 1

Oracle process number: 21

Windows thread id: 2304, image: ORACLE.EXE (SHAD)

*** ACTION NAME:() 2010-03-25 13:18:30.328
*** MODULE NAME:(OEM.SystemPool) 2010-03-25 13:18:30.328
*** SERVICE NAME:(jkdb) 2010-03-25 13:18:30.328
*** CLIENT ID:() 2010-03-25 13:18:30.328
*** SESSION ID:(117.12373) 2010-03-25 13:18:30.328
kwqidafp: cursor from different session
kwqidafp: cursor from different session
kwqidafp: cursor from different session
kwqidafp: cursor from different session
kwqidafp: cursor from different session
kwqidafp: cursor from different session
kwqidafp: cursor from different session
kwqidafp: cursor from different session
*** 2010-03-25 13:19:01.187
FATAL ERROR IN TWO-TASK SERVER: error = 12152
*** 2010-03-25 13:19:01.187
ksedmp: internal or fatal error
ORA-25254: time-out in LISTEN while waiting for a message
ORA-06512: at "SYS.DBMS_AQ", line 577
ORA-06512: at "SYSMAN.EMD_NOTIFICATION", line 492
ORA-06512: at line 1

==================================

就这个问题,去metalink上去查.

Server Trace Files Generated With ORA-12152 Errors [ID 357557.1]

--------------------------------------------------------------------------------

ÐÞ¸Äʱ¼ä 07-SEP-2007 ÀàÐÍ PROBLEM ״̬ MODERATED

In this Document
Symptoms
Cause
Solution
References

--------------------------------------------------------------------------------

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: 8.1.7 to 10.1
Oracle Server - Enterprise Edition - Version: 8.1.7.4 to 10.1.0.4.0
This problem can occur on any platform.

Symptoms
Server side trace files with an ORA-12152 similar to the following are generated intermittently:

*** SESSION ID:(23.28259) 2006-02-09 08:09:36.016
FATAL ERROR IN TWO-TASK SERVER: error = 12152
*** 2006-02-09 08:09:36.030
ksedmp: internal or fatal error
Current SQL statement for this session:
...
In the process state of the trace file, something like the following is seen:

SO: 38db25310, type: 4, owner: 38da1ccf8, flag: INIT/-/-/0x00
(session) trans: 0, creator: 38da1ccf8, flag: (8000041) USR/- -/-/-/-/-/-
DID: 0001-0010-0000000E, short-term DID: 0000-0000-00000000
txn branch: 0
oct: 0, prv: 0, sql: 0, psql: 392596b58, user: 173/#####
O/S info: user: #####, term: , ospid: 11711, machine: #####
program: #####@##### (TNS V1-V3)
application name: #####@##### (TNS V1-V3), hash value=0
last wait for 'SQL*Net break/reset to client' blocking sess=0x0 seq=1006 wait_time=-1
driver id=54435000, break?=1, =0
temporary object counter: 0

Cause
The client application died (or dropped the connection) before the server process could send the break/reset message back, and that prevented the server process from exiting gracefully. This caused the server trace file to be dumped.

This issue has been reported and fixed via non-published bug:3816595

Solution
Bug:3816595 is fixed in 10.2.0.1, and the fix is included in the 9.2.0.8 and 10.1.0.5 patchsets as well.

Either upgrade to a version where the problem is fixed, or simply ignore the trace files as they are quite harmless.

说明这个错误在10.1.0.5上的补丁被修复了.

解决这个问题的方法就是将数据库打上补丁