Results 1 to 6 of 6
  1. #1
    Join Date
    May 2003
    Posts
    369

    Unanswered: backups failing due to deadlock need help

    While running our backups nitely via TSM we get failures in backing up
    our database due to deadlock situation:

    Starting TSM Backup on Tue May 27 03:50:06 PDT 2003
    SQL0911N The current transaction has been rolled back because of a deadlock
    or timeout. Reason code "2". SQLSTATE=40001
    Starting TSM Backup on Tue May 27 04:05:05 PDT 2003
    SQL0902C A system error (reason code = "125") occurred. Subsequent SQL
    statements cannot be processed. SQLSTATE=58005

    How can I fix the deadlock and perform a successful backup? thanks

    scott

  2. #2
    Join Date
    Apr 2003
    Posts
    191

    Re: backups failing due to deadlock need help

    Hi Scott,

    I didn't know TSM is doing transactions in the database for backup.

    Anyway, if this really is a concurrency issue, how do you force users off and keep them away from the database?

    Consider filing a bug report with Tivoli or IBM because of that system error.

    Johann

    Originally posted by mixxalot
    While running our backups nitely via TSM we get failures in backing up
    our database due to deadlock situation:

    Starting TSM Backup on Tue May 27 03:50:06 PDT 2003
    SQL0911N The current transaction has been rolled back because of a deadlock
    or timeout. Reason code "2". SQLSTATE=40001
    Starting TSM Backup on Tue May 27 04:05:05 PDT 2003
    SQL0902C A system error (reason code = "125") occurred. Subsequent SQL
    statements cannot be processed. SQLSTATE=58005

    How can I fix the deadlock and perform a successful backup? thanks

    scott

  3. #3
    Join Date
    May 2003
    Location
    Phoenix, US
    Posts
    39

    Re: backups failing due to deadlock need help

    Hi Scott,
    I think you are taking an offline backup and it looks like there are some transactions happenning through the user connections.

    Probably you need to force the connections before you begin the offline backup OR consider changing the schedule time of the backup where there are no connections.


    Thanks
    Sateesh
    Originally posted by mixxalot
    While running our backups nitely via TSM we get failures in backing up
    our database due to deadlock situation:

    Starting TSM Backup on Tue May 27 03:50:06 PDT 2003
    SQL0911N The current transaction has been rolled back because of a deadlock
    or timeout. Reason code "2". SQLSTATE=40001
    Starting TSM Backup on Tue May 27 04:05:05 PDT 2003
    SQL0902C A system error (reason code = "125") occurred. Subsequent SQL
    statements cannot be processed. SQLSTATE=58005

    How can I fix the deadlock and perform a successful backup? thanks

    scott

  4. #4
    Join Date
    Feb 2003
    Location
    Thailand
    Posts
    42

    Re: backups failing due to deadlock need help

    I think the system isnot backup yet .maybe it do something before backup

    Originally posted by mixxalot
    While running our backups nitely via TSM we get failures in backing up
    our database due to deadlock situation:

    Starting TSM Backup on Tue May 27 03:50:06 PDT 2003
    SQL0911N The current transaction has been rolled back because of a deadlock
    or timeout. Reason code "2". SQLSTATE=40001
    Starting TSM Backup on Tue May 27 04:05:05 PDT 2003
    SQL0902C A system error (reason code = "125") occurred. Subsequent SQL
    statements cannot be processed. SQLSTATE=58005

    How can I fix the deadlock and perform a successful backup? thanks

    scott

  5. #5
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650

    Re: backups failing due to deadlock need help

    IMHO, an offline backup will not fail because of a deadlock because the first thing the offline backup does is to take and exclusive lock on the database ...

    I have seen online backup fail with deadlock when backing up databases with LOBs ....

    The possible explanation : When backing up LOB tablespaces, the backup application tries to obtain a share lock on it ... This is to ensure that the LOB values are not changed for the duration of its backup(as LOBs are not logged) ... Hence, if an application tries to take a lock not compatible with Share lock, the application fails .... The other way round should also be true ...

    HTH

    Cheers

    Sathyaram

  6. #6
    Join Date
    Jan 2003
    Posts
    1,605
    You can see the on-line backup at

    http://dbforums.com/t798777.html

    Hope this helps,
    Grofaty

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •