"mike" <hillmw@charter.net> wrote in
news:1121267376.820348.183150@g43g2000cwa.googlegr oups.com:

> I have no idea what to do with this.
>
> When I used: desc dbms_rowid using TOAD I got a package body window
> loaded and when pressed execute procedure I got a series of "set
> parameters" one of which was "rowid_info" defined below.
>
> How do I use this to solve my problem: deadlocks
>
> DECLARE
> ROWID_IN ROWID;
> ROWID_TYPE NUMBER;
> OBJECT_NUMBER NUMBER;
> RELATIVE_FNO NUMBER;
> BLOCK_NUMBER NUMBER;
> ROW_NUMBER NUMBER;
>
> BEGIN
> ROWID_IN := NULL;
> ROWID_TYPE := NULL;
> OBJECT_NUMBER := NULL;
> RELATIVE_FNO := NULL;
> BLOCK_NUMBER := NULL;
> ROW_NUMBER := NULL;
>
> SYS.DBMS_ROWID.ROWID_INFO ( ROWID_IN, ROWID_TYPE, OBJECT_NUMBER,
> RELATIVE_FNO, BLOCK_NUMBER, ROW_NUMBER );
> COMMIT;
> END;
>

Deadlocks are caused by poorly coded applications.
By using the information in the trace/dump files,
you should be able to identify which object(s)
are involved. From there you should be able to
determine where in the application the conflict
occurs. From there the application needs to be
changed so two different pieces of code don't
fight over the same object at the same time.