DBCC CHECKDB ERRORS

Greetings
Long standing problem with 100 inconsistencies which range across COSP,COEP & GLPCA. (data changes too fast in our system to consider a restore).
We need to identify and remove these errors before we change collations.
The only option offered by DBCC is "repair_allow_data_loss" which I definitely don't want to do.
Is there a way out of this?
Thanks in great anticipation!

Hello,
with these prerequisite (no restore and no repair) you can only pray for a no-dataloss solution.
As you worked with the database while it is corrupt (not recommended) you have only two ways out of it (maybe):
1) do a dbcc with repair_allow_data_loss and live with the logical inconsistencies
    If the DBCC cannot repair the database you have to do a homogenous system
    copy with R3load to export as much data as possible.
2) restore the database from a know good backup and apply transactionlogs until
    now. When you use a old DB backup, which is not corrupt and all your TA
    backups are accessible and not corrupt, you will end up with a current and
    not corrupt database. If you don't have a non-corrupt DB backup or only one of
    the TA backups is damaged, see option 1).
As database corruptions are caused by faulty hardware, you should do an extensive check on your hardware. Ask your hardware vendor to assists you during these checks. You have to do this check before you attempt to restore or repair or even use the database on this hardware. When you keep using this faulty hardware you will encounter more and more corruptions in more and more tables over the time.
Regards
Clas

Similar Messages

DBCC CHECKDB found 4 consistency error in the database

One of the pages has been overwritten. It is index I'd 1 which is the clustered index. The clustered index contains the underlying data, so you must restore it.
What recovery model is the data as using, and how do your backups look? Do you clean backups without corruption in them? Do you all of the log backups since that good backup?

Our database has encounter some issues that is running on SQL server 2005.
As I have read, the first steps to fix any corruption is run 'DBCC CHECKDB with ALL_ERRORMSGS, NO_INFOMSGS' and I do same. Here is the output of DBCC CHECKDB: Msg 8928, Level 16, State 1, Line 1Object ID 1429580131, index ID 1, partition ID 72057598907908096, alloc unit ID 72057598960730112 (type In-row data): Page (1:235150) could not be processed. See other errors for details.Msg 8941, Level 16, State 2, Line 1Table error: Object ID 1429580131, index ID 1, partition ID 72057598907908096, alloc unit ID 72057598960730112 (type In-row data), page (1:235150). Test (sorted [i].offset

DBCC CHECKDB Failed

Hello,
I am getting below Error while Running DBCC checkdb on sql 2008 database
DBCC results for 'WSS_Content_QA_Test'.
Msg 8921, Level 16, State 1, Line 1
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
CHECKALLOC found 0 allocation errors and 0 consistency errors in database 'WSS_Content_QA_Test'.
I tried to run dbcc after getting logical i\o error in sql error log and verified chkdsk ran fine with out error on Disk where sql file place.

Hello,
My suggestion is to restore from backup, if the database has important data. Based on the name the database has it seems it was created just for testing purposes.
The following support article exist for this error when SQL Server 2005/2008/2008 R2 are involved.
https://support.microsoft.com/kb/960791?wa=wsignin1.0
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

DBCC CHECKDB

I'm trying to implement DB integrity check on a restored copy of the database.
1) Full backup prod databases on server A.
2) Restore prod backups to server B <~ test restores of the backups.
3) Plan to implement DB Integrity check on server B. <~ in progress.
So I have all the SP ready that will run through all databases and it's dumping the results of DB Integrity check to a table. The results had 3 distinct error codes - 2593, 8997 and 8989. It appears to me, 8989 is the summary.
Well, thankfully, I do not have any errors so far - CHECKDB found 0 allocation errors and 0 consistency errors in database 'DBxxx'.
My question is, if I want to automate this process (have the job email me when there's an issue), how do I accomplish that? Do I look for error 8989 or some error code? I guess I'm trying to find out how to find the problem / trigger point to execute sending
of email.
Thanks.

Hello,
Please have a look at TechNet Script Center "DBCC CheckDB with queryable result":
http://gallery.technet.microsoft.com/scriptcenter/59bc1fb6-68de-4624-b338-83dd5461da25
In this way you can atomized the analysis of the result to e.g. send an e-mail alert.
Olaf Helper
[ Blog] [ Xing] [ MVP]

DBCC CHECKDB - repair_allow_data_loss

Hi,
I'm facing a problem at SQL2000 with R34.7.
In fact very big one because all the backups available have this error!
Anyone could please advise something to correct this errors?
The log... from DBCC CHECKDB (SID) with no infomsgs...
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4605848) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4608952) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4613352) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4615744) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4618896) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4620016) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4622912) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4623160) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4625960) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4627952) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4628872) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4629752) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4651008) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4654704) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4655080) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4657664) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4664192) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4666176) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4670096) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4670584) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4674544) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4675784) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4682288) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4685960) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4691688) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4692160) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4697312) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4703816) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4712152) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4714472) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4717352) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4719792) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4720416) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4728152) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4730488) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4736304) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4736560) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4742320) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4743896) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4745464) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4747056) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4747776) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4749240) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4754584) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4756608) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4757792) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4760840) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4764896) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4769520) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4772960) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:4774752) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:48220), slot 12, text ID 725687730176 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:48220), slot 13, text ID 725687795712 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:48220), slot 20, text ID 725687861248 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:48220), slot 21, text ID 725687926784 is not referenced.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (4:1433228), slot 0, text ID 725687795712 is referenced by page (1:48220), slot 13, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (4:1433229), slot 0, text ID 725687926784 is referenced by page (1:48220), slot 21, but was not seen in the scan.
Server: Msg 2575, Level 16, State 1, Line 1
IAM page (1:3264025) is pointed to by the next pointer of IAM page (1:214455) object ID 395148453 index ID 2 but was not detected in thscan.
Server: Msg 2575, Level 16, State 1, Line 1
IAM page (4:582493) is pointed to by the next pointer of IAM page (1:2586641) object ID 395148453 index ID 2 but was not detected in the scan.
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (4:582493) is pointed to by the previous pointer of IAM page (1:214455) object ID 395148453 index ID 2 but was not detected in the scan.
CHECKDB found 51 allocation errors and 0 consistency errors not associated with any single object.
CHECKDB found 0 allocation errors and 6 consistency errors in table 'sysindexes' (object ID 2).
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (4:1258423) is pointed to by the previous pointer of IAM page (1:2559592) object ID 395148453 index ID 2 but was not detected in the scan.
CHECKDB found 4 allocation errors and 0 consistency errors in table 'ACCTIT' (object ID 395148453).
CHECKDB found 55 allocation errors and 6 consistency errors in database 'CCP'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (CCP ).
Can anyone advise please.
Thanks in advance.
Cheers

RogerM wrote:>
> Hi,
>
> I'm facing a problem at SQL2000 with R34.7.
> In fact very big one because all the backups available have this error!
>
> Anyone could please advise something to correct this errors?
>
> The log... from DBCC CHECKDB (SID) with no infomsgs...
>
> Server: Msg 8905, Level 16, State 1, Line 1
> Extent (1:4605848) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
>
> CHECKDB found 51 allocation errors and 0 consistency errors not associated with any single object.
> CHECKDB found 0 allocation errors and 6 consistency errors in table 'sysindexes' (object ID 2).
> Server: Msg 2576, Level 16, State 1, Line 1
> IAM page (4:1258423) is pointed to by the previous pointer of IAM page (1:2559592) object ID 395148453 index ID 2 but was not detected in the scan.
> CHECKDB found 4 allocation errors and 0 consistency errors in table 'ACCTIT' (object ID 395148453).
> CHECKDB found 55 allocation errors and 6 consistency errors in database 'CCP'.
> repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (CCP ).
>
DON'T do repair_allow_data_loss unless the support team tells you exaclty to do that.
Open a support message at SAP (BC-DB-MSS) right away and have this issue analyzed.
regards,
Lars

Please interpret the DBCC CHECKDB output and suggest how much my db is corrupt

Hi All,
DBCC CHECKDB on my database in simple recovery model failed. Please find the error message below. I copied the backup and restored on
a test server and ran DBCC CHECKDB with repair_allow_data_loss. Below bold lines was the one got repaired. Does ths caused any loss of user data. Kindly suggest.
Repair: The Clustered index successfully rebuilt for the object "sys.sysobjvalues" in database "****".
Repair: The page (1:629823) has been deallocated from object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data).
Executing the query "DBCC CHECKDB(N'****') WITH NO_INFOMSGS
" failed with the following error: "Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -3212797581117423616 (type Unknown), page (40634:1181196049). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.
Incorrect PFS free space information for page (1:160) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 95_PCT_FULL, actual value 50_PCT_FULL.
Incorrect PFS free space information for page (1:3427) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 80_PCT_FULL, actual value 95_PCT_FULL.
Incorrect PFS free space information for page (1:22426) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 100_PCT_FULL, actual value 50_PCT_FULL.
Incorrect PFS free space information for page (1:26439) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 50_PCT_FULL, actual value 100_PCT_FULL.
Incorrect PFS free space information for page (1:27700) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 95_PCT_FULL, actual value 100_PCT_FULL.
Incorrect PFS free space information for page (1:27701) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 80_PCT_FULL, actual value 95_PCT_FULL.
Object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data): Page
(1:629823)could not be processed. See other errors for details.
CHECKDB found 0 allocation errors and 1 consistency errors not associated with any single object.
CHECKDB found 0 allocation errors and 7 consistency errors in table 'sys.sysobjvalues' (object ID 60).
CHECKDB found 0 allocation errors and 8 consistency errors in database '****'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (****).
Thanks Lakshmana Y

Actually there might be a way I am not sure how much accurate that would be but. Lakshman you can run dbcc checkdb repair_allow_data_loss with begin transaction and commit transaction
Begin transaction
dbcc checkdb('db_name', REPAIR_ALLOW_DATA_LOSS)
--Commit--Rollback
Before giving rollback you can check how much data you would loose. Dont give commit. A more better approach would be take backup of database with continue_after_error( I know this might and might not work, just giving you options) restore on different
server with again continue_after_error and then run repair allow data loss there and see how much data you would loose. Also not constraints would also be removed after doing repair
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Log job output to file - information missing? dbcc checkdb

Hello
Not sure where to put this question.. feel free to move it if necessary.
I have a job which runs DBCC CHECKDB WITH PHYSICAL_ONLY on every database on the instance which is read_write. Problem is that I want to get the output of the result to make sure that every database is actually performing this command. When viewing normal
history by right clicking the job and select "view history" I get cut off information due to the lack of space allowed (1000 chars default I think).
So I tried to log it to table and view it by msdb.dbo.sp_help_jobsteplog but the information here does not cover all databases as well.. So then I tried to log it to a file. But I get the same information there, and not all databases are logged.
So I start to wonder if the dbcc checkdb job does not get executed on the other databases?? If I look in the Current SQL Server Logs I only see that DBCC CHECKDB WITH PHYSICAL_ONLY executed on the same databases that is listed in my output file.
What can I do? the instance contains over 400 databases but only approximately 70 is logged as doing a dbcc checkdb.
This is my command:
SET NOCOUNT ON
EXEC sp_MSforeachdb @command1='
IF NOT(SELECT DATABASEPROPERTYEX(''?'',''Updateability''))=''READ_ONLY''
BEGIN
DBCC CHECKDB (?) WITH PHYSICAL_ONLY
END'

There is a known issue with sp_MSforeachdb where under heavy load the procedure can actually miss databases with no errors. That can be the case in your environment. Aaron Bertrand wrote about the issue and solutions for the problems in the article:
Making a more reliable and flexible sp_MSforeachdb.
Ana Mihalj

DBCC CHECKDB failure, SQL 2012, There is insufficient system memory in resource pool 'internal' to run this query.

Hey, guys!
Tried to find an answer, but nothing works for me.
So on one of servers when I am trying to run DBCC CHECKDB throws two errors
Msg 8921, Level 16, State 1, Line 1
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
Msg 701, Level 17, State 123, Line 1
There is insufficient system memory in resource pool 'internal' to run this query.
This is a VM hosted on Hyper-V server 2012 R2. VM has Windows Server 2012 R2 and SQL Server 2012 Std. VM had 8 GB of RAM, I increased it to 12GB (static, not dynamic), also I increased paging file size in Windows and size of TEMPDB also recreated TEMPDB.
I also tried to restore the Database, which throws an error from another server. On that server DBCC CHECKDB works fine, but it didn't help - I still receive the same error. Can you suggest, please?

Hi,
I agree with you. It is probably a memory issue. First, we need to verify if it is an OS memory issue or caused by SQL Server itself.
Need to use Performance Monitor:
SQLServer:Memory
Memory
Dynamic Management Views:
sys.dm_os_sys_info
sys.dm_exec_query_memory_grants
1. Use performance monitor to check OS memory: available memory(MB) and monitor the OS memory status before the query and when running the query. If it does not change, I can exclude the OS memory factor. Then, I can conclude
this memory issue was caused by SQL Server internal. Also, check if there is Memory leak on your system.
2. Use the below script in SQL Server Management Studio and Result to Text.
while(1=1)
begin
print getdate()
print '*****sys.dm_exec_query_memory_grants******'
select * from sys.dm_exec_query_memory_grants
print 'DBCC memorystatus'
dbcc memorystatus
waitfor delay '00:00:01'
end
Then, check SQLServer:Memory-Granted Workspace Memory (KB) when the issue occurs which specifies the total amount of memory currently granted to executing processes, such as hash, sort, bulk copy, and index creation operations.
And compared with the information got in
sys.dm_exec_query_memory_grants.
3. In addition, use sys.dm_os_sys_info
to identify bpool_commit_target and bpool_commited.
In SQL Server 2012, the columns have been renamed as
committed_target_kb and committed_kb.
committed_kb represents the committed memory in kilobytes (KB) in the memory manager. Does not include reserved memory in the memory manager.
committed_target_kb represents the amount of memory, in kilobytes (KB), that can be consumed by SQL Server memory manager. The target amount is calculated using a variety of
inputs like:
the current state of the system including its load
the memory requested by current processes
the amount of memory installed on the computer
configuration parameters
If committed_target_kb is larger than
committed_kb, the memory manager will try to obtain additional memory. If
committed_target_kb is smaller than committed_kb, the memory manager will try to shrink the amount of memory committed. The
committed_target_kb always includes stolen and reserved memory.
MSSQLSERVER_701
http://msdn.microsoft.com/en-us/library/aa337311.aspx
An in-depth look at SQL Server Memory–Part 3
http://blogs.msdn.com/b/sqljourney/archive/2013/11/02/10402729.aspx
INF: Using DBCC MEMORYSTATUS to Monitor SQL Server Memory Usage
http://support.microsoft.com/kb/271624/en-us
Hope it helps.
Tracy Cai
TechNet Community Support

Using Powershell to execute DBCC CheckDB from SQL Agent.

So, I have a weird situation that I think is tied tot he resource group and powershell, but I am having trouble determining if it is that or not. I run DBCC CheckDB using a resource pool and a secondary account. The account has permissions to do the work
and if I log onto the server and run the procedure locally it runs fine in the resource pool configuration. However, when I kick it from the SQL Agent job using the powershell step, it only does checkDB on the first 3 system databases and then stops once it
hits a user database. I am not seeing any errors or messages, it just stops. I ran profiler and I see it do the work, get to the first user database, issues this statement from DBCC, then just stops, and the job ends.
SELECT @BlobEater = CheckIndex (ROWSET_COLUMN_FACT_BLOB)
FROM { IRowset 0xD0936A7902000000 }
GROUP BY ROWSET_COLUMN_FACT_KEY
>> WITH ORDER BY
  ROWSET_COLUMN_FACT_KEY,
  ROWSET_COLUMN_SLOT_ID,
  ROWSET_COLUMN_COMBINED_ID,
  ROWSET_COLUMN_FACT_BLOB
OPTION (ORDER GROUP)
I am not doing anything special in my code that would limit which databases to process. As I said earlier, executing the call to the procedure from a query window runs as expected and processes all of the databases.
Here is the Agent Code calling powershell:
[string] $DayOfWeek = ""
$DayOfWeek = (get-date).DayOfWeek.ToString()
$DayOfWeek
if ($DayOfWeek -eq 'Sunday')
invoke-sqlcmd -database sysadm -serverinstance HQIOSQLDEV01\DEV01 "exec ConsistencyCheck.upConsistencyCheck NULL, 'N', 'Y', 'N', 'N', 'N'"
else
invoke-sqlcmd -database sysadm -serverinstance HQIOSQLDEV01\DEV01 "exec ConsistencyCheck.upConsistencyCheck NULL, 'Y', 'N', 'N', 'N', 'N'"
John M. Couch

There are 3 additional databases. The last known good is today as I am able to execute the procedure via query window just fine. It is only when executed from a SQL Agent job as above that it stops after only doing the System Databases. The largest database
is 130GB in size, with the largest table being 62 GB.
-- Create Procedures
raiserror('Creating Procedure ''%s''', 0, 1, '[ConsistencyCheck].[upConsistencyCheck]')
go
/*==============================================================================
Procedure: upConsistencyCheck
Schema: ConsistencyCheck
Database: SysAdm
Owner: dbo
Application: dbo
Inputs: Catalogue : nvarchar(128) : NULL = All Databases
Physical Only : nchar(1) : Y/N, NULL = N
Data Purity : nchar(1) : Y/N, NULL = N
No Index : nchar(1) : Y/N, NULL = N
Extended Logical Checks : nchar(1) : Y/N, NULL = N
Table Lock : nchar(1) : Y/N, NULL = N
Outputs: (0 = Success, !=0 = failure)
Result Set: N/A
Usage: declare @ii_Rc int
,@invc_Catalogue nvarchar(128)
,@inc_PhysicalOnly nchar(1)
,@inc_DataPurity nchar(1)
,@inc_NoIndex nchar(1)
,@inc_ExtendedLogicalChecks nchar(1)
,@inc_TabLock nchar(1)
select @invc_Catalogue = NULL
,@inc_PhysicalOnly = 'Y'
,@inc_DataPurity = 'N'
,@inc_NoIndex = 'N'
,@inc_ExtendedLogicalChecks = 'N'
,@inc_TabLock = 'N'
exec @ii_Rc = ConsistencyCheck.upConsistencyCheck @invc_Catalogue
, @inc_PhysicalOnly
, @inc_DataPurity
, @inc_NoIndex
, @inc_ExtendedLogicalChecks
, @inc_TabLock
print 'Return Code: ' + convert(varchar, @ii_Rc)
Description: This Procedure is used to run DBCC CheckDB on 1 or all Databases
on the existing instance.
Version: 1.00.00
Compatability: SQL Server 2008 (100)
Created By: John M. Couch
Created On: 04-26-2012
================================================================================
Notes
1. Some logic was taken directly from Ola Hallengren's Maintenance Script.
http://ola.hallengren.com
================================================================================
History: (Format)
When Who Version Code Tag What
04-26-2012 John Couch 1.00.00 (None) Initial Revision
==============================================================================*/
alter procedure ConsistencyCheck.upConsistencyCheck (@invc_Catalogue nvarchar(128)
,@inc_PhysicalOnly nchar(1)
,@inc_DataPurity nchar(1)
,@inc_NoIndex nchar(1)
,@inc_ExtendedLogicalChecks nchar(1)
,@inc_TabLock nchar(1)) as
/*==============================================================================
Variable Declarations & Temporary Tables
==============================================================================*/
declare @li_Rc int = 0
,@lnvc_ExecutedBy nvarchar(128) = user_name()
,@ldt_ExecutedOn datetime = getdate()
,@lnvc_Catalogue nvarchar(128) = @invc_Catalogue
,@lnc_PhysicalOnly nchar(1) = coalesce(@inc_PhysicalOnly, 'N')
,@lnc_DataPurity nchar(1) = coalesce(@inc_DataPurity, 'N')
,@lnc_NoIndex nchar(1) = coalesce(@inc_NoIndex, 'N')
,@lnc_ExtendedLogicalChecks nchar(1) = coalesce(@inc_ExtendedLogicalChecks, 'N')
,@lnc_TabLock nchar(1) = coalesce(@inc_TabLock, 'N')
,@lnvc_Instance nvarchar(128) = cast(serverproperty('ServerName') as nvarchar)
,@lnvc_Version nvarchar(40) = cast(serverproperty('ProductVersion') as nvarchar)
,@lnvc_Edition nvarchar(40) = cast(serverproperty('Edition') as nvarchar)
,@li_Compatibility int
,@ldt_CreateDate datetime
,@lnvc_UserAccess nvarchar(35)
,@lnvc_StateDescription nvarchar(35)
,@lnvc_PageVerifyOption nvarchar(35)
,@lti_IsReadOnly tinyint
,@lti_IsInStandBy tinyint
,@lnvc_Recipients nvarchar(2000) = '[email protected]'
,@lnvc_Subject nvarchar(128)
,@lnvc_ErrorMessage nvarchar(4000)
,@lnvc_SQL nvarchar(max)
,@lnvc_ManualSQL nvarchar(max)
,@lnvc_Query nvarchar(2048)
,@li_ConsistencyCheckID int
,@ldt_ExecutionStart datetime
,@ldt_ExecutionFinish datetime
declare @ltbl_Catalogue table (Catalogue sysname
,CompatibilityLevel int
,CreateDate datetime
,UserAccess nvarchar(35) -- MULTI_USER, SINGLE_USER, RESTRICTED_USER
,StateDescription nvarchar(35) -- ONLINE, RESTORING, RECOVERING, RECOVERY_PENDING, SUSPECT, EMERGENCY, OFFLINE
,PageVerifyOption nvarchar(35) -- NONE, TORN_PAGE_DETECTION, CHECKSUM
,IsReadOnly tinyint
,IsInStandBy tinyint
,IsAutoShrink tinyint
,IsAutoClose tinyint
,Flag bit default 0)
create table #ltbl_Output (Error int,
Level int,
State int,
MessageText nvarchar(max),
RepairLevel nvarchar(30),
Status int,
DBID smallint,
ObjectID int,
IndexID smallint,
PartitionID bigint,
AllocunitID bigint,
[File] int,
Page int,
Slot int,
RefFile int,
RefPage int,
RefSlot int,
Allocation int)
/*==============================================================================
Initialize Environment
==============================================================================*/
set nocount on
set quoted_identifier on
/*==============================================================================
Parameter Validation
==============================================================================*/
-- Configure Alert Mail Subject Line
set @lnvc_Subject = 'Check consistency parameter validation error occurred on ' + cast(@@servername as nvarchar)
if @lnc_PhysicalOnly not in ('Y','N')
begin
set @lnvc_ErrorMessage = N'The value for parameter @inc_PhysicalOnly is not supported.' + char(13) + char(10) + ' '
set @li_Rc = -1
end
if @lnc_DataPurity not in ('Y','N') and @li_Rc = 0
begin
set @lnvc_ErrorMessage = N'The value for parameter @inc_DataPurity is not supported.' + char(13) + char(10) + ' '
set @li_Rc = -1
end
if @lnc_NoIndex not in ('Y','N') and @li_Rc = 0
begin
set @lnvc_ErrorMessage = N'The value for parameter @inc_NoIndex is not supported.' + char(13) + char(10) + ' '
set @li_Rc = -1
end
if @lnc_ExtendedLogicalChecks not in ('Y','N') and @li_Rc = 0
begin
set @lnvc_ErrorMessage = N'The value for parameter @inc_ExtendedLogicalChecks is not supported.' + char(13) + char(10) + ' '
set @li_Rc = -1
end
if @lnc_TabLock not in ('Y','N') and @li_Rc = 0
begin
set @lnvc_ErrorMessage = N'The value for parameter @inc_TabLock is not supported.' + char(13) + char(10) + ' '
set @li_Rc = -1
end
if @lnc_ExtendedLogicalChecks = 'Y' and @lnc_PhysicalOnly = 'Y' and @li_Rc = 0
begin
set @lnvc_ErrorMessage = N'Extended Logical Checks and Physical Only cannot be used together.' + char(13) + char(10) + ' '
set @li_Rc = -1
end
if @lnc_DataPurity = 'Y' and @lnc_PhysicalOnly = 'Y' and @li_Rc = 0
begin
set @lnvc_ErrorMessage = N'Physical Only and Data Purity cannot be used together.' + char(13) + char(10) + ' '
set @li_Rc = -1
end
if @li_Rc != 0
goto errlog
/*==============================================================================
Code Section
==============================================================================*/
select @lnvc_SQL = N'select d.name, d.compatibility_level, d.create_date, d.user_access_desc, d.state_desc,
d.page_verify_option_desc, cast(d.is_in_standby as tinyint), cast(d.is_read_only as tinyint),
cast(databasepropertyex(quotename(d.name), ''IsAutoShrink'') as tinyint),
cast(databasepropertyex(quotename(d.name), ''IsAutoClose'') as tinyint),
0
from master.sys.databases d
where d.name = ' + case when isnull(@lnvc_Catalogue, '') = '' then ' d.name'
else '''' + @lnvc_Catalogue + ''''
end + '
and d.name != ''tempdb'''
insert into @ltbl_Catalogue (Catalogue, CompatibilityLevel, CreateDate, UserAccess,
StateDescription, PageVerifyOption, IsReadOnly, IsInStandBy,
IsAutoShrink, IsAutoClose, Flag)
exec sp_executesql @lnvc_SQL
while (select top 1 1
from @ltbl_Catalogue c
where c.Flag = 0) = 1
begin
select top 1 @lnvc_Catalogue = c.Catalogue
,@li_Compatibility = c.CompatibilityLevel
,@ldt_CreateDate = c.CreateDate
,@lnvc_UserAccess = c.UserAccess
,@lnvc_StateDescription = c.StateDescription
,@lnvc_PageVerifyOption = c.PageVerifyOption
,@lti_IsReadOnly = c.IsReadOnly
,@lti_IsInStandBy = c.IsInStandBy
from @ltbl_Catalogue c
where c.Flag = 0
select top 1 @lnvc_Catalogue
,@li_Compatibility
,@ldt_CreateDate
,@lnvc_UserAccess
,@lnvc_StateDescription
,@lnvc_PageVerifyOption
,@lti_IsReadOnly
,@lti_IsInStandBy
if @lnvc_StateDescription = 'ONLINE' and @lnvc_UserAccess != 'SINGLE_USER'
begin
-- Build Execution String
select @lnvc_SQL = N'dbcc checkdb (' + quotename(@lnvc_Catalogue) + ')' + case when @lnc_NoIndex = 'Y' then ', noindex'
else ''
end + ' with tableresults, no_infomsgs, all_errormsgs '
+ case when @lnc_PhysicalOnly = 'Y' then ', physical_only'
else ''
end
+ case when @lnc_DataPurity = 'Y' then ', data_purity'
else ''
end
-- Option not supported with Compatibility < 100 (SQL Server 2005 and below)
+ case when @lnc_ExtendedLogicalChecks = 'Y' then
case when @li_Compatibility = 100 then ', extended_logical_checks'
else ''
end
else ''
end
+ case when @lnc_TabLock = 'Y' then ', tablock'
else ''
end
-- Prepare Processing Environment
truncate table #ltbl_Output
set @ldt_ExecutionFinish = null
set @ldt_ExecutionStart = null
-- Capture Start Time.
set @ldt_ExecutionStart = getdate()
-- Execute the Command.
insert into #ltbl_Output(Error, Level, State, MessageText, RepairLevel, Status,
DBID, ObjectID, IndexID, PartitionID, AllocunitID,
[File], Page, Slot, RefFile, RefPage, RefSlot, Allocation)
exec sp_executesql @lnvc_SQL
-- Capture Completion Time.
set @ldt_ExecutionFinish = getdate()
-- Add Header Record to Confirm Execution.
insert into SysAdm.ConsistencyCheck.ExecutionLog(Instance, [Version], Edition, Catalogue, PhysicalOnly,
NoIndex, ExtendedLogicalChecks, DataPurity, [TabLock],
Command, ExecutionStart, ExecutionFinish,
CreatedOn, CreatedBy)
values(@lnvc_Instance, @lnvc_Version, @lnvc_Edition, @lnvc_Catalogue, @lnc_PhysicalOnly,
@lnc_NoIndex, @lnc_ExtendedLogicalChecks, @lnc_DataPurity, @lnc_TabLock,
@lnvc_SQL, @ldt_ExecutionStart, @ldt_ExecutionFinish,
@ldt_ExecutedOn, @lnvc_ExecutedBy)
-- Capture Header Record ID
select @li_ConsistencyCheckID = @@IDENTITY
-- Were there errors?
if (select top 1 1
from #ltbl_Output t) = 1
begin
select @li_ConsistencyCheckID, t.Error, t.Level, t.State, t.MessageText, t.RepairLevel,
t.Status, t.ObjectID, t.IndexID, t.PartitionID, t.AllocunitID, t.[File], t.Page,
t.Slot, t.RefFile, t.RefPage, t.RefSlot, t.Allocation, @ldt_ExecutedOn, @lnvc_ExecutedBy
from #ltbl_Output t
-- Log Failure Entries
insert into SysAdm.ConsistencyCheck.ErrorLog (ExecutionLogID, Error, Severity, [State]
,ErrorMessage, RepairLevel, [Status], ObjectID
,IndexID, PartitionID, AllocationUnitID, FileID
,Page, Slot, RefFileID, RefPage, RefSlot, Allocation
,CreatedOn, CreatedBy)
select @li_ConsistencyCheckID, t.Error, t.Level, t.State, t.MessageText, t.RepairLevel,
t.Status, t.ObjectID, t.IndexID, t.PartitionID, t.AllocunitID, t.[File], t.Page,
t.Slot, t.RefFile, t.RefPage, t.RefSlot, t.Allocation, @ldt_ExecutedOn, @lnvc_ExecutedBy
from #ltbl_Output t
-- Configure Alert Mail Subject Line
set @lnvc_Subject = 'Consistency Check failure for Database ' + quotename(@lnvc_Catalogue) + ' on Instance ' + quotename(@lnvc_Instance) + ' !'
set @lnvc_ErrorMessage = 'To view more details, logon to the Instance and execute the query: ' +
+ char(13) + char(10) + char(13) + char(10) +
'select * from sysadm.consistencycheck.ErrorLog where ExecutionLogID = ' + cast(@li_ConsistencyCheckID as varchar) + ''
+ char(13) + char(10) + char(13) + char(10) +
'Consistency Check Output: ' +
+ char(13) + char(10)
select @lnvc_SQL = N'set nocount on;select ltrim(rtrim(ErrorMessage)) as Message
from SysAdm.ConsistencyCheck.ErrorLog r
where r.ExecutionLogID = ''' + cast(@li_ConsistencyCheckID as nvarchar(128)) + ''''
exec msdb.dbo.sp_send_dbmail @profile_name = 'SQL Mailbox',
@recipients = @lnvc_Recipients,
@subject = @lnvc_Subject,
@body = @lnvc_ErrorMessage,
@query = @lnvc_SQL,
@execute_query_database = @lnvc_Catalogue,
@query_result_header = 1,
@query_result_width = 32767,
@query_no_truncate = 1,
@body_format = 'TEXT',
@importance = 'High'
end
end
else
begin
-- If we get here, then the database was not processed due to it having a status other than ONLINE, being in SINGLE_USER mode or
-- having a compatability level < 100
set @lnvc_Subject = 'Unable to perform consistency checks for Database ' + quotename(@lnvc_Catalogue) + ' on ' + quotename(@lnvc_Instance) + '!'
set @lnvc_ErrorMessage = 'One of the following conditions was not met. ' + CHAR(13) + CHAR(10) + CHAR(13) + CHAR(10) +
'* Database must be ONLINE. It''s current state is: ' + @lnvc_StateDescription + CHAR(13) + CHAR(10) +
'* Database access level cannot be set to SINGLE_USER. It''s current access level is: ' + @lnvc_UserAccess
exec msdb.dbo.sp_send_dbmail @profile_name = 'SQL Mailbox',
@recipients = @lnvc_Recipients,
@subject = @lnvc_Subject,
@body = @lnvc_ErrorMessage,
@body_format = 'TEXT',
@importance = 'High'
end
update t
set Flag = 1
from @ltbl_Catalogue t
where t.Catalogue = @lnvc_Catalogue
end
/*==============================================================================
Cleanup Temp Tables
==============================================================================*/
cleanup:
if object_id('tempdb..#ltbl_Output') is not null
drop table #ltbl_Output
/*==============================================================================
Exit Procedure
==============================================================================*/
quit:
return @li_Rc
/*==============================================================================
Error Processing
==============================================================================*/
errlog:
-- Raise Error, and write to Application Event Log
raiserror (@lnvc_ErrorMessage, 16, 1) with log, nowait
-- Send Email Notification of Error
exec msdb.dbo.sp_send_dbmail @profile_name = 'Mailbox',
@recipients = @lnvc_Recipients,
@subject = @lnvc_Subject,
@body = @lnvc_ErrorMessage,
@importance = 'High'
goto cleanup
go
John M. Couch

SQL 2012 DBCC CHECKDB Run Very Slow

Does anyone experience this? SQL 2012 DBCC CHECKDB runs very slow on one of the server. I monitored the server and it seems DBCC CHECKDB does not hit the disk hard enough.
It can read 100 mb per second on of my slower server, but on this particular server, it only read 1 mb per second. I saw parallel processes, but it just not read disk hard enough. I am curious what causes this? There is no user using the server when I run
DBCC command. The full database restore took 3 hours, but DBCC CHECKDB took more than 11 hours. Thanks for any input.
Lijun

Hi,
Have you made the change of 'cost threshold for parallelism'? The default value of this is 5. Increasing the cost threshold for parallelism would cause most of the queries including CHECKDB to not execute parallel and hence will tend to
take time to complete. This could be one of the issue contributing to the CHECKDB slow run.
Also, please check if the antivirus is checking SQL Database files:
http://support.microsoft.com/kb/309422
Here is a good article on CHECKDB time taken to complete.
http://blogs.msdn.com/b/sqlserverstorageengine/archive/2007/01/24/how-long-will-checkdb-take-to-run.aspx
Thanks.
Tracy Cai
TechNet Community Support

How to exclude a table when doing dbcc checkdb

when running dbcc checkdb(mydb). it will go through all tables. Is it possible to exclude a table from dbcc checkdb?

Thanks, Mark. When I run dbcc checkdb(mydb), it across a table and take over 18 hours and still waiting.
the message is:
Checking mytable: Logical pagesize is 2048 bytes
The total number of data pages in this table is 1365692.
The total number of pages which could be garbage collected to free up some space is 2923.
then I stop it manually.
Possibly something wrong with the table. When I run dbcc checktable on this table, it' also keep me waiting and never end. then I can't finish dbcc checkdb because of this table. the size of this table is about 3G. How to resolve this problem?

Shoud dbcc checkdb run in single user mode?

want to run dbcc checkdb(mydb), is it okay to run it online without impact its availability?

checkdb checks each table in the database one at a time, holding a shared table lock while it does so. On very large tables, it can take some time, so other processes would only be able to read from the table during that time, not perform any inserts, updates, or deletes.
-bret

Error message when I do DBCC CHECKDB

Msg 8921, Level 16, State 1, Line 1
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
Msg 802, Level 17, State 20, Line 1
Error: 802, Severity: 17, State: 20. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
I guess the message means I do not have enough space in tempdb.
How can I fix it?

If possible try to restart the instance which will create new tempdb.Certain operations definitely needs large tempdb.But if you encounter operational issues you may consider shrink too.its not recommended though
http://sqlsunday.com/2013/08/11/shrinking-tempdb-without-restarting-sql-server/
Best Regards, Arun http://whynotsql.blogspot.com/
If you suspect corruption in database restating SQL Server instance or taking database offline and then bringing online could be fatal.So I would not recommend you to do that.I am not sure whether large tempdb is required or not you can check tempdb usage
when you are runing Checkdb.CHECKDB is highly resource intensive and utilizes tempdb.
Other option.as pointed by Erland, would be restore valid backup of database on clean server and run checkdb there see if it comes out clean.
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

DB13 CheckDB Error

Hi Experts,
While running Checkdb through DB13 , I am getting below error :-
BR0301E SQL error -1031 at location BrDbcheckoraRead-1, SQL statement:
'OPEN curs_91 CURSOR FOR'
'SELECT NVL(UPPER(TYPE), ' '), NVL(UPPER(PARAM), ' '), NVL(PARAM, ' '), NVL(OBJECT, ' '), NVL(UPPER(OBJECT), ' '), NVL(ACTIVE, ' '), NVL(SEVERITY, ' '), NVL(CHKOP, ' '), NVL(CHKVAL, ' '), NVL(UNIT, ' '), NVL(CHKREP, ' '), NVL(REPUNIT, ' '), NVL(MODFLAG, '
ORA-01031: insufficient privileges
Please help me to resolve this error

Hi Patel,
check this, may be it would be helpfull to you
Error: ORA-01031: insufficient privileges
Cause:
You attempted to perform an operation for which you do not have the appropriate privileges. Some of the more common causes are:
You tried to change an Oracle username or password without having the appropriate privileges.
You tried to perform an UPDATE to a table, but you only have SELECT access to the table.
You tried to start up an Oracle database using CONNECT INTERNAL.
You tried to install an Oracle database without having the appropriate privileges to the operating-system.
Action:
The options to resolve this Oracle error are:
You can have the Oracle DBA grant you the appropriate privileges that you are missing.
You can have the Oracle DBA execute the operation for you.
If you are having trouble starting up Oracle, you may need to add the Oracle user to the dba group.
regards,
Balaram

CheckDB error

Hello!
I have an error in T-code DB13 checkDB in my BI system
Illegal value ' ' found in DBCHECKORA field 'CHKVAL' for key 'PROF LOG_ARCHIVE_START' - ignoring the record
What should i do about this

Hi Robert,
Check you oracle parameters in your spfile or init<SID>.ora, value of LOG_ARCHIVE_START should be either TRUE or FALSE. Also check the value of the Database check condition on DB17 match the value on the profile.
Regards
Juan

DBCC CHECKDB ERRORS

Similar Messages

Maybe you are looking for