Db went to suspect in AG

  • One of my db went to suspect in secondary replica  when i checked in  events  lock_redo_blocked , how can i trouble shoot these issue .

    In sql Logs we find deadlock info at that time

     

  • Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

  • You can check for what session is blocking the redo thread with the following - depending on what is blocking, sometimes you need to kill the session that is blocking:

    SELECT 
    session_id,
    command,
    blocking_session_id,
    wait_type,
    wait_resource,
    wait_time
    FROM sys.dm_exec_requests
    WHERE command = 'DB STARTUP'

    Sue

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply