One of our 6.5 servers is getting error 614 (A row on a page x was accessed that has an illegal length of y in database z.) However, we can read the specified tables with "select * from a" and can "select into" a new table from those tables with no errors reported. DBCC checkdb and newalloc show no problems. Has anyone else seen this behaviour? We are running diagnostics on the server and raid hardware to determine if those components have problems that might be causing the 614 errors.Microsoft has stated that this error was resolved in Service Pack 3 for SQL Server 6.5. Verify that you have the service pack installed
SELECT @.@.version
6.50.258
It looks like you can get this error if your SELECT statement contains a large GROUP BY list of columns, total length > 512 bytes.|||Originally posted by achorozy
Microsoft has stated that this error was resolved in Service Pack 3 for SQL Server 6.5. Verify that you have the service pack installed
SELECT @.@.version
6.50.258
It looks like you can get this error if your SELECT statement contains a large GROUP BY list of columns, total length > 512 bytes.
------------------------
Thanks for the reply.
Our server version is 6.50.422 which is a "post SP5" version. I considered the large Group By as a possible cause, but no software changes were made prior to the first occurance of the error. I'll double check with the analyst who supports the app to make sure though.
Thanks again.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment