Hello Markus
So, the database is waiting for a lock release.
But what can cause this datatbase state ?
Can you advice me some DB parameters to change ?
Are there some parameters to unlock tables automaticly ?
Or should I change something in my procedure and trigger code ?
Dusan Kolesar
Helsinska 19
040 13 Kosice
Slovakia
e-mail primary : [EMAIL PROTECTED]
e-mail alternative : [EMAIL PROTECTED]
ICQ# : 160507424
On Tue, 14 Mar 2006 14:20:54 +0100, Döhr, Markus ICC-H
<[EMAIL PROTECTED]> wrote:
my database has freezed again.
See attachement for x_cons output.
Can you describe me what does it mean ?
Where should I search for problem ?
ID UKT UNIX TASK APPL Current Timeout Region Wait
tid type pid state priority cnt try item
T135 7 -1 User 3992* Vwait 0 0 252
36171(s)
T136 7 -1 User 968* Vwait 0 0 251
36171(s)
T139 7 -1 User 3544* Vwait 0 0 252
36171(s)
T140 7 -1 User 97304* Vwait 0 0 46
36171(s)
The database is waiting for a lock release. All of those application PIDs
are waiting for the item 36171.
Unfortunately I don't know how to find out via command line what exactly
this lock is.
Anyone of the development can give a hint here?
Greetz,
SIEGENIA-AUBI KG
Informationswesen
i.A.
Markus Döhr
SAP-CC/BC, SAPDB-DBA
Tel.: +49 6503 917-152
Fax: +49 6503 917-7152
E-Mail: [EMAIL PROTECTED]
Internet: http://www.siegenia-aubi.com
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
