Hello, I found out the problem. It is the Foreign Key. The test added and deleted records in two tables, tbMaster and tbDetail. tbDetail has a FOREIGN KEY referencing a primary key in tbMaster. I traced the SQLs and found that when concurrent deletion on these two tables executing, dead lock seemed occur. I delete the Foreign key and very things is OK.
Best regards. ----- Original Message ----- From: "Koetter, Thomas Theodor" <[EMAIL PROTECTED]> To: "'Harry Cai'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Thursday, October 24, 2002 11:09 PM Subject: RE: concurrent problem on linux? Hi Harry, > -----Original Message----- [snip] > everything is OK. but when multithread were used in the test, > the sapdb database instance seemed dead. and after a LONG > TIME, i finally got a "Lock request timeout" Error info. > If I install sapdb on win2000 or solaris and run the same > test, everything is OK. Does SAPDB have concurrent promblem on Linux? Can you please give some more details? The testprogram and the table definition are very welcomed. Regards Thomas ---------------------------------------------- Dr. Thomas K�tter SAP DB, SAP Labs Berlin SAP DB is open source. Get it! www.sapdb.org _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
