Share via

AlwaysOn - We have a background session on our secondary server stuck at 'db startup' since our last failover

  • Article

Question

Saturday, June 3, 2017 9:55 AM

Hi,

Since our last failover, we have on our secondary server background sessions active for all of our synchronized databases. These sessions seems to be stuck at 'db startup' command. Any idea why and what to do with this?

I don't know if it's related but we ran a DBCC CHECKDB and when the job tried to check one of these databases stuck at 'db startup' command, our DBCC failed!  Error message:

DBCC CHECKDB (DatabaseName) executed by LOGIN found 0 errors and repaired 0 errors. Elapsed time: 10 hours 20 minutes 23 seconds.  Internal database snapshot has split point LSN = 0001e8b8:000a46a8:0008 and first LSN = 0001e8b8:0009cc80:0001.

Thank you all!

All replies (6)

Monday, June 5, 2017 6:48 AM

I do not think CHECKDB is issue as it did not found any issue and completed successfully. What is state of databases as of now

select name,state_desc, * from sys.databases

Can you also post SQL Server errorlog of Primary replica

Cheers,

Shashank

Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

My TechNet Wiki Articles
MVP

Tuesday, June 6, 2017 9:04 PM

All the databases are ONLINE.

Wednesday, June 7, 2017 3:06 AM

All the databases are ONLINE.

So what is the issue here ? I also asked for errorlogs ?

Cheers,

Shashank

Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

My TechNet Wiki Articles
MVP

Wednesday, June 7, 2017 4:01 PM

db_startup is the redo thread. The problem is documented here:

https://blogs.msdn.microsoft.com/alwaysonpro/2015/01/06/troubleshooting-redo-queue-build-up-data-latency-issues-on-alwayson-readable-secondary-replicas-using-the-wait_info-extended-event/

I find that I need to kill the blocking user process. This blog post will help you to identify the problem processes.

Tuesday, March 26, 2019 2:24 PM

Hello, I am having exactly same issue as described. SQL Server 2014 EE, with AOAG.
All databases on secondary replica, except system ones, have a background process running on them with DB STARTUP command.

I could not find the troubleshooting page indicated here.

Thanks for any help.-

Tuesday, March 26, 2019 2:28 PM

Here is the article in its new location.

https://techcommunity.microsoft.com/t5/SQL-Server-Support/Troubleshooting-REDO-queue-build-up-data-latency-issues-on/ba-p/318488

don't be concerned about the db_startup process. It is the process which applies the commands to the replica database. In some circumstances this process may be blocked. You may need to kill the blocking process.