I've a probleme to understand the behaviour of SAP 7.4 with locks. Using the database, I have a kind of dead lock, not detected by the server.
When I have a look to LOCKS, LOCK_HOLDER, and LOCK_REQUESTOR (I can send the whole files for more details), I can see things like this :
*LOCKS* SESSION;TRANSCOUNT;PROCESS;USERNAME;DATE;TIME;TERMID;LASTWRITE;LOCKMODE;LOCKSTATE;APPLPROCESS;APPLNODE;OWNER;TABLENAME;TABLEID;ROWIDLENGTH;ROWIDHEX;ROWID 81197; 5504;14;TEST;2003-12-09;16:06:36; java; 90;row_exclusive;?;0;localhost;TEST;SV_COMMANDE;000000000000050A;6;00C86556881100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000; 81197; 5504;14;TEST;2003-12-09;16:06:36; java; 90;row_exclusive;write;0;localhost;TEST;SV_MVT_VALQUAL;000000000000055C;6;00C87303987300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000; 81197; 5504;14;TEST;2003-12-09;16:06:36; java; 90;row_exclusive;write;0;localhost;TEST;SV_MOUVEMENT;00000000000007F1;6;00C87300710500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000; 81166; 5490;13;TEST;2003-12-09;15:17:39; java; 90;tab_share;temp;0;localhost;TEST;SV_FRACT;00000000000007FD;0;?;? 81166; 5490;13;TEST;2003-12-09;15:17:39; java; 90;row_exclusive;write;0;localhost;TEST;SV_FRACT;00000000000007FD;6;00C86285065700000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000; 81166; 5490;13;TEST;2003-12-09;15:17:39; java; 90;row_exclusive;write;0;localhost;TEST;SV_FRACT;00000000000007FD;6;00C86285065800000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000; 81166; 5490;13;TEST;2003-12-09;15:17:39; java; 90;row_exclusive;write;0;localhost;TEST;SV_FRACT;00000000000007FD;6;00C86285065900000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000;
*LOCK_REQUESTOR* SESSION;TRANSCOUNT;PROCESS;USERNAME;DATE;TIME;TERMID;REQTIMEOUT;LASTWRITE;REQMODE;REQSTATE;APPLPROCESS;APPLNODE;OWNER;TABLENAME;TABLEID;ROWIDLENGTH;ROWIDHEX;ROWID 81197; 5504;14;TEST;2003-12-09;16:06:36; java; 4490; 510;row_exclusive;write;0;localhost;TEST;SV_FRACT;00000000000007FD;6;00C86563438100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000; 81166; 5490;13;TEST;2003-12-09;15:17:39; java; 4490; 510;tab_share;temp;0;localhost;TEST;SV_MOUVEMENT;00000000000007F1;0;?;?
I'm connected with Isolation Level 1. According to the documentation, I don't understand why there are some "tab_share" locks.
I also notice that the date and time for each leack are the date and time of the initial connection (and so, they aren't very useful).
Thanks for help
Philippe
-- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
