December 3, 2019 at 4:13 am
one of the job is getting failing with the
Command: DBCC CHECKDB TPX WITH NO_INFOMSGS, ALL_ERRORMSGS, DATA_PURITY
Msg 3314, Level 17, State 3, Server DTX002 , Line 1
During undoing of a logged operation in database 'TPX', an error occurred at log record ID (235571:128656:345). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
Msg 1823, Level 16, State 6, Server DTX002, Line 1
A database snapshot cannot be created because it failed to start.
Msg 1823, Level 16, State 7, Server DTX002, Line 1
A database snapshot cannot be created because it failed to start.
Msg 1823, Level 16, State 8, Server DTX002, Line 1
A database snapshot cannot be created because it failed to start.
Msg 7928, Level 16, State 1, Server DTX002, Line 1
The database snapshot for online checks could not be created. Either the reason is given in a previous error or one of the underlying volumes does not support sparse files or alternate streams. Attempting to get exclusive access to run checks offline.
Msg 7934, Level 16, State 1, Server DTX002, Line 1
DBCC CHECK cannot proceed on database TPX because it is a Secondary Replica and either Snapshot creation failed or the WITH TABLOCK option was specified. Secondary Replica databases cannot be exclusively locked for DBCC CHECK. Reason may have been given in previous error.
The operating system returned error 665(The requested operation could not be completed due to a file system limitation) to SQL Server during a write at offset 0x00004831b5e000 in file 'D:\MSSQL11.MSSQLSERVER\MSSQL\DATA\TPX.mdf:MSSQL_DBCC12'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
HResult 0x254, Level 21, State 1
Cannot continue the execution because the session is in the kill state.
We have sufficient disk space on the drive and files are accessable
December 3, 2019 at 12:25 pm
Have you looked at the error logs specified in this error message to find additional information?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply