4 edited tags
| link
3 edited tags
| link
2 SQL is a query language, the database product is called SQL Server
source | link

Missing log block for availability database in SQL Server 2016

I've recently begun receiving alerts like this one:

Always On Availability Groups transport has detected a missing log block for availability database "myDb". LSN of last applied log block is (xxxx:xxxxxxx:x). Log scan will be restarted to fix the issue. This is an informational message only. No user action is required.

According to this article, it should have been fixed in SQL Server 2016 SP2 CU 2. My environment is SQL Server 2016 SP2 CU7, so I don't understand why I'm seeing this. Anyone here knows what could be causing it or if anything is actionable, aside from opening an MS support ticket?

Missing log block for availability database in SQL 2016

I've recently begun receiving alerts like this one:

Always On Availability Groups transport has detected a missing log block for availability database "myDb". LSN of last applied log block is (xxxx:xxxxxxx:x). Log scan will be restarted to fix the issue. This is an informational message only. No user action is required.

According to this article, it should have been fixed in SQL 2016 SP2 CU 2. My environment is 2016 SP2 CU7, so I don't understand why I'm seeing this. Anyone here knows what could be causing it or if anything is actionable, aside from opening an MS support ticket?

Missing log block for availability database in SQL Server 2016

I've recently begun receiving alerts like this one:

Always On Availability Groups transport has detected a missing log block for availability database "myDb". LSN of last applied log block is (xxxx:xxxxxxx:x). Log scan will be restarted to fix the issue. This is an informational message only. No user action is required.

According to this article, it should have been fixed in SQL Server 2016 SP2 CU 2. My environment is SQL Server 2016 SP2 CU7, so I don't understand why I'm seeing this. Anyone here knows what could be causing it or if anything is actionable, aside from opening an MS support ticket?

1
source | link