June 8, 2011 at 3:54 am
Hi,
A few days ago, stack dumps appeared in the errorlog after DBCC CHECKDB discovered following corruption:
DBCC generated following error:
Msg 8905, Level 16, State 1, Line 1
Extent (3:1430120) in database ID 8 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
CHECKDB found 1 allocation errors and 0 consistency errors not associated with any single object.
CHECKDB found 1 allocation errors and 0 consistency errors in database 'Staging_wild'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (Staging_wild).
After correction using DBCC CHECKDB (staging_wild, REPAIR_ALLOW_DATA_LOSS), stack dumps occur everytime an SSIS package runs. This package started to generate deadlocks and stack dumps since it was migrated from SQL2005 to SQL2008R2. On SQL2005, there were never errors reported for this package.
DBCC CHECKDB doesn’t give any errors since the correction.
We are running SQL2008R2 and have traceflags 1204 and 1222 to log deadlock informative activated.
Can somebody explain me what went wrong?
Thanks
Geert
June 8, 2011 at 4:05 am
Please don't cross post. It just wastes people's time and fragments replies
No replies to this thread please. Direct replies to http://www.sqlservercentral.com/Forums/Topic1121580-266-1.aspx
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply