Re: Tuning deadlocks

Others have given you recommendations on eliminating the deadlocks, which is what really needs to be done. But as to the question of one DB coping quicker than the other, the database holds a latch (can't remember which one) which the deadlock trace file is being written. If max_dump_file_size is set to a large size, this can sometimes last a while. I've seen DBs where things got bad for over a minute. Shrinking the max_dump_file_size setting causes the latch to be released sooner.

Obviously avoiding the deadlocks is the long term solution.

--Terr

> I have two live databases running the same application, one of the
databases
> has deadlocks which the database seems to cope with quicker than the same
> application running on the other database. It version 8.1.7.4 and I have
> checked the init.ora including hidden parameters like LM_DD_INTERVAL
> are there any other parameters which might resolve this problem?
>
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>

--
http://www.freelists.org/webpage/oracle-l