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 | 13315613
KB4538275 - FIX: Database initialization may fail by using automatic seeding in SQL Server 2017 - Microsoft Support
Last update date:
6/2/2022
Affected products:
SQL Server 2017 on Linux
Affected releases:
build lower than 14.0.3281.6
Fixed releases:
14.0.3281.6
Description:
Symptoms
Assume that you use SQL Server 2017. When you try to initialize multiple databases in a SQL Server Always On availability group (AG) by using automatic seeding, you notice that seeding for some databases may fail, and need to retry on one or more secondary replicas.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Resolution
This issue is fixed in the following cumulative update for SQL Server: Cumulative Update 19 for SQL Server 2017 About cumulative updates for SQL Server: Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server: Latest cumulative update for SQL Server 2017 Note When you use the fix, the corresponding pacemaker package must be applied in order for SQL Server on Linux to work correctly.
Workaround
To work around this issue, you can retry, use backup or use restore for initialization.
References
Learn about the terminology that Microsoft uses to describe software updates.
