Tony, the trace files generally have the SQL that were invloved in the deadlock. We had a situation a while ago and we traced the SQL to a stored procedure that was issuing commit at the very last step. Putting a commit solved the situation in our case without affecting the integrity of data manipulated by the proc. see if that helps you..
Deepak --- Tony Vecchiet <[EMAIL PROTECTED]> wrote: > Occasionally we get ORA-60 in our alert log and it > generates > a trace file. Does anyone have a good method of > interpreting > the trace file and finding the root cause? > RDBMS 8.1.6.2 > thanks > > begin:vcard > n:Vecchiet;Tony > tel;fax:408.377.3153 > tel;work:408.879.4771 > x-mozilla-html:FALSE > org:Xilinx, Inc > adr:;;2100 Logic Drive;San Jose;CA;95124;USA > version:2.1 > email;internet:[EMAIL PROTECTED] > title:Manager, Oracle Database Group > x-mozilla-cpt:;14432 > fn:Tony Vecchiet > end:vcard > __________________________________________________ Do You Yahoo!? Find a job, post your resume. http://careers.yahoo.com -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Deepak Thapliyal INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
