April 27, 2015 at 5:05 am
Hi,
we have an sql-server agent job which runs every night and imports data from dwh into dm.
At the weekend, the jobs runs into failure and the Sql-dump delivers SqlDumpExceptionHandler: Process 65 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
Does anybody know what this descprition means?
Here are the start from the SQLDump:
2015-04-26 07:42:04.07 spid25s DoMiniDump () encountered error (0x800703E6) - Invalid access to memory location.
2015-04-26 07:42:04.09 spid25s Error: 17065, Severity: 16, State: 1.
2015-04-26 07:42:04.09 spid25s SQL Server Assertion: File: <latch.cpp>, line = 1659 Failed Assertion = '0' Attempted release of unacquired latch. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
2015-04-26 07:42:04.09 spid65 Using 'dbghelp.dll' version '4.0.5'
2015-04-26 07:42:04.10 spid65 ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\LOG\SQLDump0022.txt
2015-04-26 07:42:04.10 spid65 SqlDumpExceptionHandler: Process 65 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
2015-04-26 07:42:04.10 spid65 * *******************************************************************************
2015-04-26 07:42:04.10 spid65 *
2015-04-26 07:42:04.10 spid65 * BEGIN STACK DUMP:
2015-04-26 07:42:04.10 spid65 * 04/26/15 07:42:04 spid 65
2015-04-26 07:42:04.10 spid65 *
2015-04-26 07:42:04.10 spid65 *
2015-04-26 07:42:04.10 spid65 * Exception Address = 00000000748EE4A0 Module(MSVCR80+000000000001E4A0)
2015-04-26 07:42:04.10 spid65 * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
2015-04-26 07:42:04.10 spid65 * Access Violation occurred reading address 000000007FFFFFFB
2015-04-26 07:42:04.10 spid65 * Input Buffer 510 bytes -
2015-04-26 07:42:04.10 spid65 * And then comes a Query ....
April 27, 2015 at 6:50 am
It's a memory error. It could be pretty benign, just a momentary read/write error in memory that's not going to repeat. It could also be corrupt pages in one of your databases. I would strongly recommend running DBCC on them if you don't already do that regularly. It could also be due to hardware issues or even the OS. If you see it again and all your databases have passed their consistency checks, then I would focus on the OS and the hardware.
"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