SQL Server Performance Forum – Threads Archive
Truncate log job failed with 3023 & 3013 err msgI have a job which run at 2am every day to truncate log file.
The job contains simple BACKUP LOG ‘dbname’ WITH TRUNCATE_ONLY
DBCC SHRINKFILE(2,1,TRUNCATEONLY) This is the first time the job failed with the following error. Server: Msg 3023, Level 16, State 3, Line 1
Backup and file manipulation operations (such as ALTER DATABASE ADD FILE) on a database must be serialized. Reissue the statement after the current backup or file manipulation operation is completed.
Server: Msg 3013, Level 16, State 1, Line 1
BACKUP LOG is terminating abnormally.
I am wondering what is wrong with this database.
3023 means, It thinks there is some concurrent database operation going on that is blocking the ALTER DATABASE, because it is unable to acquire the database lock. Please check what all processes are running at that particular time. We had faced this problem earlier but it worked after a re-start. Though I would also like to know the reasons.
Reissue the operation after the conflicting operation has completed. If a shrink operation fails, reissue the shrink command with the TRUNCATE_ONLY option after the backup completes.