Mode in deadlock errors

[Graves, Paul]

Dear Ingres Clever People,

What is a "mode" as reported in deadlock errors ?

For example -

"mode 5" ?

[1830 , 405277A0]: Tue Jun 13 09:33:27 2000
E_DM9045_TABLE_DEADLOCK Deadlock encountered locking table ms.tp_rship
in database dbrel3 with mode 5. Resource held by session [4067 407bf040].
Requested by session [4056 405277a0].

"mode 3" ?

[1830 , 40572040]: Fri Jun 9 07:30:19 2000
E_DM9045_TABLE_DEADLOCK Deadlock encountered locking table .TABLE_ID
(14453,14949) in database dbrel3 with mode 3. Resource held by session [4067
40b9e040]. Requested by session [4056 40572040].

"mode 2" ?

[1833 , 40ADD3C0]: Thu Jun 15 16:40:39 2000
E_DM9045_TABLE_DEADLOCK Deadlock encountered locking table
ms.tp_rship_ftp in database dbrel3 with mode 2. Resource held by session
[4056 405277a0]. Requested by session [4067 40add3c0].

Any information would be appreciated.

If this fails I'll have to call CA Support and I really don't want to have
to do that !

Thanks
Paul Graves
EDS Electronic Commerce
Cheadle Cheshire UK

[Mason, Paul]

> Dear Ingres Clever People,
>
Not sure I qualify but anyway...

> What is a "mode" as reported in deadlock errors ?
>

It is the type of lock being requested by the session getting the error.

The modes are

0 = Null
1 = IS
2 = IX
3 = S
4 = SIX
5 = X

See the DBA Guide chapter on locking for explanation of what these modes are.

This information is from Expert Note US015049 (sol 201) - which I found by searching on "Deadlock" and "Mode" in the CA StarTCC system.

Hope this is useful.

Paul Mason
Any views, opinions, apparent facts and inaccuracies are mine and mine alone

[Martin Bowes]

Hi Paul,

Mode codes are:
1 = 'Intended Shared',
2 = 'Intended Exclusive',
3 = 'Shared',
4 = 'Shared Intended Exclusive',
5 = 'Exclusive'

Also be aware that the 'session [...]' construct in these messages is
slightly misleading. The first number in the [] is actually the server
Unix process_id and not its connect_id! To convert to a connect_id, simply
run csreport | grep <process_id>. The connect_id will then be displayed
for you.

Furthermore, the session number displayed may not be totally correct! Some
versions of ingres will want you to place a '1' in front of this number
before the servers will recognize it! In IPM or IIMONITOR you may even
need to convert the case to upper.

eg. Requested by session [4056 405277a0]
process_id=4056,
session_id=405277a0

get the connect_id: csreport | grep 4056

then iimonitor <connect_id>
IIMONITOR> format 1405277a0

I believe this little problem has been reported to CA and is currently up
as a DAR.

Martin Bowes
>
> Dear Ingres Clever People,

>
> What is a "mode" as reported in deadlock errors ?
>

--
Random Earthworm Jim Quote #21:
Jim - I have a cunning plan. I'll let them win!
Peter Puppy - So, not quite as cunning as I would have hoped