Сидел проверял алертлог и увидел постоянно вываливающиеся ошибки
Цитата: ORA-00060: Deadlock detected. More info in file /opt/oracle/admin/udump/matrixco_ora_1738.trc
глядим в этот трэйс и видим следюющее
Цитата: Oracle9i Enterprise Edition Release 9.2.0.8.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production
ORACLE_HOME = /opt/oracle/product/9ir2
System name: Linux
Node name: proliant
Release: 2.6.5-7.244-bigsmp
Version: #1 SMP Mon Dec 12 18:32:25 UTC 2005
Machine: i686
Instance name: matrixco
Redo thread mounted by this instance: 1
Oracle process number: 250
Unix process pid: 1738, image: oracle@proliant (TNS V1-V3)
*** 2007-06-29 11:29:58.273
*** SESSION ID:(239.4871) 2007-06-29 11:29:58.250
DEADLOCK DETECTED ( ORA-00060 )
The following deadlock is not an ORACLE error. It is a
deadlock due to user error in the design of an application
or from issuing incorrect ad-hoc SQL. The following
information may aid in determining the deadlock:
Deadlock graph:
---------Blocker(s)-------- ---------Waiter(s)---------
Resource Name process session holds waits process session holds waits
TX-0006002b-0005f893 250 239 X 247 235 X
TX-0007000f-00060e91 247 235 X 250 239 X
session 239: DID 0001-00FA-0000000C session 235: DID 0001-00F7-0000001A
session 235: DID 0001-00F7-0000001A session 239: DID 0001-00FA-0000000C
Rows waited on:
Session 235: obj - rowid = 0000542E - AAAFQuAA8AAAzMPAAJ
(dictionary objn - 21550, file - 60, block - 209679, slot - 9)
Session 239: obj - rowid = 0000542E - AAAFQuAA8AAAzMPAAC
(dictionary objn - 21550, file - 60, block - 209679, slot - 2)
Information on the OTHER waiting sessions:
Session 235:
pid=247 serial=12308 audsid=15718490 user: 3315/SUPERMAG
O/S info: user: SYSTEM, term: DUO, ospid: 816:2016, machine: MATRIX-UFA\DUO
program: Sm.Post.Server.exe
application name: Sm.Post.Server.exe, hash value=0
Current SQL Statement:
DELETE FROM SMOBJECTCHANGE WHERE OBJTYPE = 'PT' AND OBJID = :b1
End of information on OTHER waiting sessions.
Current SQL statement for this session:
DELETE FROM SMOBJECTCHANGE WHERE OBJTYPE = 'PT' AND OBJID = :b1
----- PL/SQL Call Stack -----
object line object
handle number name
0x8028b6b0 883 package body SUPERMAG.POST
0x80290340 2 SUPERMAG.SMPOSTPACKAGESCHANGE
0x8023b074 9 procedure SUPERMAG.SMPOSTDONEVP
0x802425c8 1 anonymous block
===================================================
PROCESS STATE
-------------
Process global information:
process: 0x7a530f2c, call: 0x8a79fbec, xact: 0x7f51d3a4, curses: 0x7a5d98b8, usrses: 0x7a5d98b8
Я так понимаю, это проблемы в процедурах обработки очереди почтовых пакетов.
Счастливые пользователи почтового модуля версии 1.025 СП3 подтвердите у всех это или нет.