Sybase *deadlock victim* rollback bug??? 
Author Message
 Sybase *deadlock victim* rollback bug???

We are experiencing a problem (bug?) where upon Sybase seeing a deadlock
and choosing the deadlock victim to terminate, doesn't seem to rollback
the deadlock victim's command that was being executed.  Below is a
step by step of what is happening along with the version of Sybase we
are running and the Sybase errorlog showing the deadlock situation.

 1. Executing a CREATE INDEX against the # temp table

 2. Detecting a deadlock condition on this process (error # 1205), where
    this process was chosen as a deadlock victim and *presumably* the index
    creation is rolled back

 3. After detecting the deadlock, we immediately reissue the CREATE INDEX
    command, whereupon we get an "index already exists" error on that
    temp table!

Sybase tech support has not been able to help us at all. We can't
get an answer as to what happens when a CREATE INDEX command is
killed by Sybase. Is it rolled back? Is there a bug that prevents
this from happening? Is this what happens under System X or XI?

Other than telling us to upgrade to System XI ( which we will when
we have a moment and are sure System 11.5 is stable )!

Regards,
Bryan Althaus

==============================================================================

SQL Server/4.9.2/EBF 4660/HP9000/800/HP-UX 8.0/1/OPT/Wed Mar 22 06:32:50 PST
1995
=============================================================================

<< Sybase errorlog >>

00: 97/11/02 21:20:30.45 server: Deadlock Id 2 detected
Deadlock Id 2 detected. 2 deadlock chain(s) involved.

Process 8 was executing a  command at line 1.
Process 9 was executing a CREATE INDEX command at line 1.
Process 9 was waiting for a 'shared page' lock on page 30 of the 'sysindexes'
table in database 2 but process 8 already held a 'exclusive page' lock on it.
Process 8 was waiting for a 'exclusive page' lock on page 28 of the
'sysindexes' table in database 2 but process 9 already held a 'shared page'
lock on it.

Process 8 was executing a  command at line 1.
Process 9 was executing a CREATE INDEX command at line 1.
Process 9 was waiting for a 'shared page' lock on page 30 of the 'sysindexes'
table in database 2 but process 8 already held a 'exclusive page' lock on it.
Process 8 was waiting for a 'exclusive page' lock on page 28 of the
'sysindexes' table in database 2 but process 9 already held a 'shared page'
lock on it.

Process 9 encountered multiple deadlocks.
Process 9 was chosen as the victim. End of deadlock information.

<<  End of Sybase errorlog >>



Mon, 24 Apr 2000 03:00:00 GMT
 
 [ 1 post ] 

 Relevant Pages 

1. Deadlock situtation (deadlock victim) - help needed!!

2. Deadlock Victim

3. Deadlock Victim ODBC Error

4. I am a deadlock victim!!!!

5. Deadlock Victim Problem

6. Choosing deadlock victim

7. Deadlock Victim/Performance

8. Deadlock Victim

9. Deadlock Victim Error

10. deadlock victim

11. sp_cursorclose/ deadlock victim

12. Deadlock Victim Concurrency Issue


 
Powered by phpBB® Forum Software