Re: Help me : urgent

Sachin,

While everyone is correct that you need to solve the deadlock issue, you may not be able to solve that immediately (because app code needs to be changed). A problem that accompanies deadlocks is that a latch is held while the trace file for the deadlock is written, and this can hold up your entire database/application. A workaround is to set your max_dump_file_size to something fairly small (e.g., 100K) so that writing the trace file doesn't take so long and the latch is released sooner.

--Terry

  hi

  problem is that , Database stop respone to application Server but still it   is giving response to Toad and others things .this problem we faced two times   in production database and also Database Shutdown abort still   not worked properly and after restrarting database it;s start response to   database setver

  Problem in Alert Log file -

  Mon Jul 10 13:12:24 2006
  ORA-000060: Deadlock detected. More info in file d:\database\udump\vvvS001.TRC.

  PMON failed to acquire latch, see PMON dump   Wed Jul 12 20:43:19 2006
  ORA-000060: Deadlock detected. More info in file d:\database\udump\lotteryS002.TRC.

  PMON failed to acquire latch, see PMON dump   Wed Jul 12 20:51:15 2006
  ORA-000060: Deadlock detected. More info in file d:\database\udump\lotteryS000.TRC.

  With Regards

  Sachin Sethi

--

http://www.freelists.org/webpage/oracle-l Received on Mon Jul 17 2006 - 13:01:46 CDT