Hello,
In my availability group, secondary replica database log file became full. Please let me know how to fix it.
November 15, 2022 at 3:15 pm
If the AG is all in sync you should just be able to Backup the log on the primary.
Then you will be able to issue a shrink file of the log in the primary and it will replicate through.
If the log file is full on the secondary - then it is also full on the primary. If neither log file can grow then your only option will be to remove that database from the AG and manually clear the log file on the primary.
If the secondary log drive is smaller than the primary log drive - and the primary was able to continue growing but the secondary was not able to grow anymore, then again - you are left with the option of removing the database from the AG.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
November 21, 2022 at 10:54 am
Hi,
just take a look, what is your logfile blocking from "shrinking"
SELECT
name AS DatabaseName,
log_reuse_wait_desc AS LogBlocking,
recovery_model_desc AS RecoveryModel
FROM sys.databases
WHERE name NOT IN ('master', 'msdb', 'model', 'tempdb', 'maintenancedb') AND log_reuse_wait_desc NOT LIKE 'NOTHING'
Good luck,
Kind regards,
Andreas
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply