January 5, 2022 at 11:37 am
Hi,
We have started to receive the error below for a couple of months now, I have executed a number of DBCC CheckDB commands for the databases but no integrity or corruption is shown. There are no visible issues with any of the databases.
SQL Server Assertion: File: <sql\ntdbms\storeng\dfs\access\rowbucketprocessor.inl>, line=658 Failed Assertion = 'comp_setop_types(*pValueInfo, *pParamInfo) <= 0'. 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
However Microsoft suggest to enable Trace Flag 9121 in the instructions here https://support.microsoft.com/en-us/topic/kb4503417-fix-assertion-dump-occurs-when-you-select-a-view-on-a-linked-server-in-sql-server-2017-2016-or-2014-8034aeb5-5a45-a5f2-a049-f4e4389a06ad
There is no more information on this trace flag anywhere therefore I am not sure what it is actually for and any impact. The server is patched to SQL Server 2017 Enterprise CU27 so should include any past hotfixes or patches as suggested.
Does anybody have any information on trace flag 9121 or able offer any help or advice?
January 5, 2022 at 2:15 pm
My advice - reach out to Microsoft support. You pay for their support and those types of errors are things that should be covered by support.
The link you provided indicates that the problem should be fixed in CU 15 of SQL 2017 which makes me think that your problem is unrelated to the article, just similar symptoms.
Now, what I would recommend is investigating the problem. What changed that caused the problem to start? Did you install CU27 and shortly after the problem started OR was CU27 installed for a while before problems occurred? If installation of CU27 wasn't the cause, what else changed around the time the problem started? Are there any other errors in the logs (SQL and Windows) that occur around the same time? Does the problem occur when you run the same scenario as you linked (SELECTing from a view from a linked server) OR is it different steps to make the problem occur?
The above will help the Microsoft support team, and may even help you (or us) solve it without them if any of the logs have interesting data. That being said, I still recommend reaching out to Microsoft as you pay for support; might as well use it!
As for trace flag 9121, I do not have any information on that one.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
January 5, 2022 at 5:24 pm
Are you on the latest CU? If you are behind any maintenance patch, I'd put that on first before doing other work.
SQL DBA,SQL Server MVP(07, 08, 09) "It's a dog-eat-dog world, and I'm wearing Milk-Bone underwear." "Norm", on "Cheers". Also from "Cheers", from "Carla": "You need to know 3 things about Tortelli men: Tortelli men draw women like flies; Tortelli men treat women like flies; Tortelli men's brains are in their flies".
January 24, 2022 at 8:01 am
This was removed by the editor as SPAM
March 22, 2022 at 6:50 am
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.
Steps to fix SQL connection error-
Gather information for troubleshooting the error.
Step 1：Verify that the instance is running.
Step 2: Verify that the SQL Server Browser service is running.
Step 3: Verify the server name in the connection string.
Step 4: Verify the aliases on the client machines.
Greeting,
Rachel Gomez
March 22, 2022 at 8:43 am
Hi thanks for everyone's responses,
We are now running SQL Server Enterprise 2017 with CU28, I did check for corruption straight away with DBCC CHECKDB which yielded no results, that said it does appear that this may have arisen after CU27 was installed, but then cleared after CU28 was installed at the end of February. I will keep an eye on this and reach out to MS should this happen again. One of their guides suggested trace flag 9121 but I cannot find any information on that flag.
March 26, 2022 at 7:49 am
This was removed by the editor as SPAM
March 26, 2022 at 10:59 am
This was removed by the editor as SPAM
June 22, 2022 at 6:59 am
This was removed by the editor as SPAM
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply