SQL Server Alert System: 'Severity 023' and 'Severity 020' with Transactional Replication

By -

This is not so much a question just a post about the resolution I came to since and I was unable to find anything online about it.

I had a SQL Server host failure, had to migrate to a new host and bring over the SQL Server VM from backups. Once the SQL Server was back online, I restored each database from a backup drive that was still working properly. Shortly after it was all brought back online, I started receiving the errors below:

SQL Server Alert System: 'Severity 023' DESCRIPTION: "An error occurred while processing the log for database 'DBName'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log."

SQL Server Alert System: 'Severity 020' DESCRIPTION: A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.

I found all sorts of posts online saying to rebuild my log after setting my DB to emergency mode or restoring from backup. The odd thing was the DB was still up and running properly with no issues on our website.

Come to find out that all I had to do was fix my replication publications. Since the replication was not working, the Log file was increasing in size and SQL Server could not access the log file for whatever it was trying to do.

So I just right clicked on each publication that was failing > Generate Scripts > click on Drop and then Create so I have both sets of scripts. Now my errors are gone. Wish it was something I would have looked at to begin with!



from Recent Questions - Stack Overflow https://ift.tt/2Tf2EaS
https://ift.tt/eA8V8J

Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more