Operational Defect Database
BugZero found this defect 1308 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Microsoft SQL Server | 10936563
KB4039089 - FIX: EXCEPTION_ACCESS_VIOLATION error when you execute the sys.sp_MScdc_capture_job stored procedure in SQL Server - Microsoft Support
Last update date:
7/21/2023
Affected products:
SQL Server 2016 Developer - duplicate (do not use)
SQL Server 2016 Enterprise - duplicate (do not use)
SQL Server 2016 Enterprise Core - duplicate (do not use)
SQL Server 2016 Standard - duplicate (do not use)
SQL Server 2016 Service Pack 1
SQL Server 2017 on Windows (all editions)
SQL Server 2017 on Linux (all editions)
SQL Server 2014 Developer - duplicate (do not use)
SQL Server 2014 Enterprise - duplicate (do not use)
SQL Server 2014 Enterprise Core - duplicate (do not use)
SQL Server 2014 Standard - duplicate (do not use)
Affected releases:
build lower than 14.0.3006.16
Fixed releases:
14.0.3006.16
Description:
Symptoms
Consider the following scenario: Assume that you have partitioned tables in Microsoft SQL Server and they are part of Change Data Capture (CDC) or Transactional Replication. You switch-in or switch-out partition from these tables. After partition switch when you perform Data Manipulation Language (DML) operations, you may notice that an EXCEPTION_ACCESS_VIOLATION occurs and a memory dump file is generated. Date/Time ***Stack Dump being sent to FilePath\FileNameDate/Time SqlDumpExceptionHandler: Process ProcessID generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.Date/Time * *******************************************************************************Date/Time * Date/Time * BEGIN STACK DUMP:Date/Time * Date/Time * Date/Time *Date/Time * Date/Time * Exception Address = 000007FEE724BD80 Module(sqllang+00000000015BBD80)Date/Time * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATIONDate/Time * Access Violation occurred reading address 000000000000002ADate/Time * Input Buffer 70 bytes Date/Time * sys.sp_MScdc_capture_jobDate/Time * Date/Time ***Stack Dump being sent to FilePath\FileNameDate/Time SqlDumpExceptionHandler: Process PID generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.Date/Time * *******************************************************************************Date/Time *Date/Time * BEGIN STACK DUMP:Date/Time * Date/TimeSPIDDate/Time *Date/Time *Date/Time * Exception Address = 000007FEE9D26640 Module(sqllang+0000000001586640)Date/Time * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATIONDate/Time *Access Violation occurred reading address 000000000000002ADate/Time * Input Buffer 109 bytes -Date/Time * 16 00 00 00 12 00 00 00 02 00 00 00 00 00 00 00 00 00Date/Time * s p _ r e p 01 00 00 00 0b 00 73 00 70 00 5f 00 72 00 65 00 70 00Date/Time * l c m d s & ô 6c 00 63 00 6d 00 64 00 73 00 00 00 00 00 26 04 04 f4Date/Time * & & ÿ 01 00 00 00 00 26 04 04 00 00 00 00 00 00 26 04 04 ffDate/Time * ÿÿÿ ¥ & ff ff ff 00 00 a5 0a 00 00 00 00 00 26 04 04 8f 13 00Date/Time * & & ¡ 00 00 00 26 04 04 00 00 00 00 00 00 26 04 04 20 a1 07Date/Time * 00 If you run the following query against destination table then you may notice that the is_replicated column's value will be marked as '1' for non-clustered index which is not correct. select index_id, partition_number, * from sys.system_internals_partition_columns pc with(nolock) JOIN sys.partitions p with(nolock) ON p.partition_id = pc.partition_id where p.object_id = object_id ('PartitionTable') order by 2
Resolution
This issue is fixed in the following cumulative updates for SQL Server: Cumulative Update 1 for SQL Server 2017 Cumulative Update 5 for SQL Server 2016 SP1 Cumulative Update 8 for SQL Server 2014 SP2
