SQL Server File Assertion error

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

General SQL Server Forums

Data Corruption Issues

SQL Server File Assertion error

Author

Topic

asha192
Starting Member

9 Posts

Posted - 2005-11-23 : 04:35:08

Hi,

I keep getting this error

Using 'dbghelp.dll' version '4.0.5'
*Dump thread - spid = 112, PSS = 0x49b051f0, EC = 0x49b05520
*Stack Dump being sent to D:\Program Files\Microsoft SQL Server\MSSQL\log\SQLDump0576.txt

Stack Signature for the dump is 0x16F06946

SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.

Error: 3624, Severity: 20, State: 1.

DBCC gives me consistency errors with index id 0.

Restarting the sql server services and the error disappears but then reappears after 2-3 days.

All help is appreciated....

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2005-11-23 : 12:28:08

Why do you restart the server - what do you think its going to fix?

Please post the output from

DBCC CHECKDB (dbname) WITH ALL_ERRORMSGS, NO_INFOMSGS

Please also answer the following:
1) what version + SP are you using?
2) do you have a sensible backup plan that meets your business's downtime/data loss requirements? Have you practised disaster recovery?
3) are there any signs of h/w problems in the SQL errorlog or Windows event logs? (let mek now if you don't know what to look for)
4) any h/w changes recently?
5) how long have you been getting the error for?

Thanks

Paul Randal
Lead Program Manager, Microsoft SQL Server Storage Engine
(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)

asha192
Starting Member

9 Posts

Posted - 2005-11-23 : 22:47:59

Hi,

Thanks for your quick response.

DBCC CHECKDB ('Sym_BB') WITH ALL_ERRORMSGS, NO_INFOMSGS

Server: Msg 8928, Level 16, State 2, Line 1
Object ID 893246237, index ID 0: Page (3:503646) could not be processed. See other errors for details.
Server: Msg 8944, Level 16, State 1, Line 1
Table error: Object ID 893246237, index ID 0, page (3:503646), row 31. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 528 and 136.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 893246237, index ID 1. Page (3:3674) is missing a reference from previous page (3:503646). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 893246237, index ID 1. Page (3:503646) was not seen in the scan although its parent (3:184662) and previous (3:3675) refer to it. Check any previous errors.
CHECKDB found 0 allocation errors and 4 consistency errors in table 'SC_Collection' (object ID 893246237).
CHECKDB found 0 allocation errors and 4 consistency errors in database 'Sym_BB'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (Sym_BB ).

Please also answer the following:
1) what version + SP are you using?
>> SQL Server 8 with SP3a
2) do you have a sensible backup plan that meets your business's downtime/data loss requirements? Yes
Have you practised disaster recovery? Yes.
3) are there any signs of h/w problems in the SQL errorlog or Windows event logs? (let mek now if you don't know what to look for)
No signs of any h/w probles but I might not be looking at the correct things. Can you let mw know what to look for?
4) any h/w changes recently?
NO
5) how long have you been getting the error for?
1 day. But I have been getting some memory corruption issues and by restarting the services, the error would go away.

Thanks again.

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2005-11-24 : 10:53:29

Well done on the backups and practising.

One data page in the 'SC_Collection' table is corrupt. The error is saying that the metadata in a record that points to the start of the variable-length column array is pointing beyond the end of the record - this means that updates to the record will be trashing other records on the page.

The options you have for dealing with this are:
1) restore from your backups
2) run repair (which will delete the page and you'll lose that data)
3) if neither of the above suit your business requirements, try to extract as much of the data from the broken page manually and then run repair.

The h/w problems to look for are IO errors from the OS (e.g. 823 errors, timed-out IOs, disk controller errors).

Can you describe the memory corruption issues fully? Have you run full memory diagnostics?

Thanks

Paul Randal
Lead Program Manager, Microsoft SQL Server Storage Engine
(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)

asha192
Starting Member

9 Posts

Posted - 2005-11-25 : 00:59:54

Hi,

I ran into another error today. This seems to be getting on a very high priority.

Server: Msg 8928, Level 16, State 1, Line 1
Object ID 981578535, index ID 0: Page (8:387669) could not be processed. See other errors for details.
Server: Msg 8944, Level 16, State 1, Line 1
Table error: Object ID 981578535, index ID 0, page (8:387669), row 0. Test (columnOffsets->offTbl [varColumnNumber] >= priorOffset) failed. Values are 111 and 516.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 981578535, index ID 1. Page (8:387669) was not seen in the scan although its parent (1:226042) and previous (8:387668) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 981578535, index ID 1. Page (8:387670) is missing a reference from previous page (8:387669). Possible chain linkage problem.
CHECKDB found 0 allocation errors and 4 consistency errors in table 'tabname' (object ID 981578535).
CHECKDB found 0 allocation errors and 4 consistency errors in database 'dbname'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (dbname ).

This is for a different object than mentioned in my previous post.

I have a DTS job that keeps failing and gives me this error and a reindexing job that fails with the Failed Assertion = 'm_offBeginVar < m_SizeRec' errors.

I have some users also connected to the system at that time.

Thanks for all your help.

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2005-11-25 : 11:23:22

Its the same error though, just a different page.

Can you answer the questions I asked previously about h/w errors and describing the memory problem?

Thanks

Paul Randal
Lead Program Manager, Microsoft SQL Server Storage Engine
(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources