Here is the scenario on of the test servers. The transaction log is full. The database is in AG. Its SQL Server 2016 enterprise edition instance.
SQL Server Alert System: 'Error 9002 Log File Full' occurred on \\Server1
> The ldf file growth was limited to 100GB. There is lot of disk space available on drive though.
> DBCC SQLPERF(LOGSPACE); -- shows 100% usage
> Checked the recovery model and log reuse description from DMVs. it was Full and waiting ACTIVE transaction.
> dbcc loginfo --shows all VLFS are active i.e. status =2
> Taken consecutive 3 log backup and tried to check if there VLF status will change. nothing changed.
> I tried to increased the log file size using TSQL to 110GB. SQL still throws me an error message repeatedly
Msg 9002, Level 17, State 4, Line 3
The transaction log for database 'db1' is full due to 'ACTIVE_TRANSACTION'.
> I see multiple block chains as well.
Did anyone come across this situation? How to solve it without KILLing any sessions or restarting SQL Server ?