When I try to delete a job from Enterprise Manager Console I get the following error:
Erro 644: Could not find the index entry for RID '163bd10000010000' in index page (1:553), index ID 0 database 'msdb'
Oh and this is on MSDE.
Here is my complete output of DBCC CHECKDB
DBCC results for 'msdb'.
DBCC results for 'sysobjects'.
There are 280 rows in 6 pages for object 'sysobjects'.
DBCC results for 'sysindexes'.
There are 143 rows in 6 pages for object 'sysindexes'.
DBCC results for 'syscolumns'.
There are 1567 rows in 26 pages for object 'syscolumns'.
DBCC results for 'systypes'.
There are 26 rows in 1 pages for object 'systypes'.
DBCC results for 'syscomments'.
There are 357 rows in 108 pages for object 'syscomments'.
DBCC results for 'sysfiles1'.
There are 2 rows in 1 pages for object 'sysfiles1'.
DBCC results for 'syspermissions'.
There are 116 rows in 1 pages for object 'syspermissions'.
DBCC results for 'sysusers'.
There are 13 rows in 1 pages for object 'sysusers'.
DBCC results for 'sysproperties'.
There are 0 rows in 0 pages for object 'sysproperties'.
DBCC results for 'sysdepends'.
There are 1635 rows in 8 pages for object 'sysdepends'.
DBCC results for 'sysreferences'.
There are 12 rows in 1 pages for object 'sysreferences'.
DBCC results for 'sysfulltextcatalogs'.
There are 0 rows in 0 pages for object 'sysfulltextcatalogs'.
DBCC results for 'sysfulltextnotify'.
There are 0 rows in 0 pages for object 'sysfulltextnotify'.
DBCC results for 'sysfilegroups'.
There are 1 rows in 1 pages for object 'sysfilegroups'.
DBCC results for 'backupset'.
There are 1045 rows in 44 pages for object 'backupset'.
DBCC results for 'sysjobschedules'.
There are 7 rows in 1 pages for object 'sysjobschedules'.
DBCC results for 'syscategories'.
There are 19 rows in 1 pages for object 'syscategories'.
DBCC results for 'systargetservers'.
There are 0 rows in 0 pages for object 'systargetservers'.
DBCC results for 'backupfile'.
There are 1451 rows in 24 pages for object 'backupfile'.
DBCC results for 'systargetservergroups'.
There are 0 rows in 0 pages for object 'systargetservergroups'.
DBCC results for 'systargetservergroupmembers'.
There are 0 rows in 0 pages for object 'systargetservergroupmembers'.
DBCC results for 'restorehistory'.
There are 1 rows in 1 pages for object 'restorehistory'.
DBCC results for 'sysalerts'.
There are 9 rows in 1 pages for object 'sysalerts'.
DBCC results for 'sysoperators'.
There are 0 rows in 0 pages for object 'sysoperators'.
DBCC results for 'sysnotifications'.
There are 0 rows in 0 pages for object 'sysnotifications'.
DBCC results for 'restorefile'.
There are 2 rows in 1 pages for object 'restorefile'.
DBCC results for 'systaskids'.
There are 0 rows in 0 pages for object 'systaskids'.
DBCC results for 'syscachedcredentials'.
There are 0 rows in 0 pages for object 'syscachedcredentials'.
DBCC results for 'restorefilegroup'.
There are 1 rows in 1 pages for object 'restorefilegroup'.
DBCC results for 'logmarkhistory'.
There are 0 rows in 0 pages for object 'logmarkhistory'.
DBCC results for 'sysdtscategories'.
There are 3 rows in 1 pages for object 'sysdtscategories'.
DBCC results for 'sysdtspackages'.
There are 0 rows in 0 pages for object 'sysdtspackages'.
DBCC results for 'sysdtspackagelog'.
There are 0 rows in 0 pages for object 'sysdtspackagelog'.
DBCC results for 'sysdtssteplog'.
Server: Msg 8935, Level 16, State 1, Line 1
Table error: Object ID 2073058421, index ID 1. The previous link (1:343) on page (1:371) does not match the previous page (1:382) that the parent (1:300), slot 32 expects for this page.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2073058421, index ID 1. Page (1:371) is missing a reference from previous page (1:343). Possible chain linkage problem.
There are 0 rows in 0 pages for object 'sysdtssteplog'.
DBCC results for 'sysdtstasklog'.
There are 0 rows in 0 pages for object 'sysdtstasklog'.
DBCC results for 'sysdbmaintplans'.
There are 4 rows in 1 pages for object 'sysdbmaintplans'.
DBCC results for 'sysdbmaintplan_jobs'.
There are 4 rows in 1 pages for object 'sysdbmaintplan_jobs'.
DBCC results for 'sysdbmaintplan_databases'.
There are 12 rows in 1 pages for object 'sysdbmaintplan_databases'.
DBCC results for 'sysdbmaintplan_history'.
There are 724 rows in 23 pages for object 'sysdbmaintplan_history'.
DBCC results for 'log_shipping_primaries'.
There are 0 rows in 0 pages for object 'log_shipping_primaries'.
DBCC results for 'log_shipping_secondaries'.
There are 0 rows in 0 pages for object 'log_shipping_secondaries'.
DBCC results for 'mswebtasks'.
There are 0 rows in 0 pages for object 'mswebtasks'.
DBCC results for 'sqlagent_info'.
There are 0 rows in 0 pages for object 'sqlagent_info'.
DBCC results for 'sysdownloadlist'.
There are 0 rows in 0 pages for object 'sysdownloadlist'.
DBCC results for 'backupmediaset'.
There are 1045 rows in 11 pages for object 'backupmediaset'.
DBCC results for 'sysjobhistory'.
Server: Msg 8935, Level 16, State 1, Line 1
Table error: Object ID 2073058421, index ID 1. The previous link (1:382) on page (1:564) does not match the previous page (1:371) that the parent (1:300), slot 33 expects for this page.
There are 626 rows in 208 pages for object 'sysjobhistory'.
CHECKDB found 0 allocation errors and 3 consistency errors in table 'sysjobhistory' (object ID 2073058421).
DBCC results for 'sysjobs'.
There are 7 rows in 1 pages for object 'sysjobs'.
DBCC results for 'backupmediafamily'.
There are 1045 rows in 20 pages for object 'backupmediafamily'.
DBCC results for 'sysjobservers'.
There are 7 rows in 1 pages for object 'sysjobservers'.
DBCC results for 'sysjobsteps'.
There are 9 rows in 1 pages for object 'sysjobsteps'.
CHECKDB found 0 allocation errors and 3 consistency errors in database 'msdb'.
repair_rebuild is the minimum repair level for the errors found by DBCC CHECKDB (msdb ).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
I am getting the following after kicking off DBCC CHECKDB 'DATABASE', REPAIR_ALLOW_DATA_LOSS) :
Executed as user: USER. Database 'TEST' consistency errors in sysobjects, sysindexes, syscolumns, or systypes prevent further CHECKDB processing. [SQLSTATE 42000] (Error 7995) Clustered index successfully restored for object 'syscolumns' in database 'TEST'. [SQLSTATE 01000] (Error 2592) DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000] (Error 2528). The step failed.
I have a database that is being restored to another instance of SQL server 2000 sp4 by attatching the mdf and ldf files. I then run EXEC sp_change_users_login to sync the users. When I try to run some delete commands on the new restored database I get 'Fatal error 8908'
I then run a DBCC CHECKDB on the database and told to run it again with REPAIR_ALLOW_DATA_LOSS
I have noticed that when I create a new databse and restore a .bak over this the delete commands work.
Am I correct in thinking that I can get rid of the corruption on the original database by creating a new database then restoring a valid .bak backup on this new database.
I've read the bad news in other post but hopefully I misunderstood them. We have a database on an old sql 2000 server which had a data drive failure. The last backup is a year old. They told me they stopped doing backups because nothing was going to change. Well, changes were made to structures and stored procedures on the production (only) server and they want to try to recover the database. Should I bother opening a support call with MS? I'm embarred to even post the question but you never know. The database is currently in emergency mode. I can't see any of the user tables or stored procedures in Mangement Studio.
Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:17913) with latch type SH. sysobjects failed.
In earlier versions of SQL Server, it was recommended that DBCC statements be made a regular part of a database backup strategy. It was recommended that databases be checked before being backed up. In SQL Server 7.0, this is no longer necessary.
Are integrity checks really no longer necessary in SQL Server 7? I have a third-party book in which the author states that he still does them anyway. Should I continue to do DBCC CHECKDB?
Also, I am using database maintenance plans for several SQL Servers. When the integrity checks are performed will it log any errors in the output log generated during the execution of the maintenance plan? The logs I receive look like the following:
[2] Database CPMCC_GL: Check Data and Index Linkage...
** Execution Time: 0 hrs, 39 mins, 54 secs **
If an error is detected would it be recorded here, or is this just a log to let me know that the checks were performed?
Our supplyer of application we use say that dbcc checkdb or dbcc newalloc can give corrupt database (use version 6.5). I wonders about this statement. Are ther some how have explanation about this
Let me start off by saying that under normal circumstance I would just restore from the last good backup. However in this case it appears as though the last good backup was sometime last August ... arg! After much yelling at the person responsible I've been attempting to get my blood pressure below 200 and see what data is recoverable.
First off, this was a RAID5 system that failed 1 drive. Secondly, before we got someone in there to replace said drive it failed a second drive and the system went down. We managed to massage the system back online but it appears that there is some corruption as a result which is no surprise.
I've done DB repairs in the past and it hasn't been too bad, but this time it is looking a little gnarly.
I've kicked everyone off the server and tried starting SQLServer several different ways.
I tried starting the service normally and then flagging the bad DB into single user mode with "ALTER DATABASE foo SET SINGLE_USER". I then did a select * from sysdatabases to make sure it took, which it did. I also tried starting the whole SQLServer in single user mode from the command line, "SQLServr -m".
I can run "DBCC CHECKDB('foo')" and I get a long ugly list of allocation errors. I posted it to a link as the 1349 lines returned is a little long: http://chrisnet.net/sqlbad/dbcc_checkdb.txt
But when I attempt to bite the bullet and destroy data in an attempt to put things back together with: "DBCC CHECKDB('foo', REPAIR_ALLOW_DATA_LOSS) WITH ALL_ERRORMSGS" I get: Server: Msg 7919, Level 16, State 2, Line 1 Repair statement not processed. Database needs to be in single user mode. DBCC execution completed. If DBCC printed error messages, contact your system administrator.
But yet the database is in single user mode, according to everything I check check on. Is this just SQL's way of telling me the corruption is too severe to be repaired? No output is displayed in the shell cmd window like it is for a successful DBCC either (when running sqlservr -m).
I have huge database on prod. One time I tried to run DBCC CHECKDB, it took more than a day. My question is can I created a snapshot of the prod database on the same server and run DBCC CHECKDB on the Snapshot DB? will doing this interfere production database? I don’t have option to make copy of the database on a test server and run it there.
we've been having this ancient database with old accounting data running in suspect mode since as long as I can remember (I started working here a year ago), and finally I had some time on my hands so I thought I'd try to get it online again. However I'm running in to problems:
DBCC CHECKDB (myDBName) gives this error: Msg 926, Level 14, State 1, Line 1 Database 'myDBName' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
Running sp_helpdb only does not display the suspect database and sp_helpdb 'myDBName' gives this error even though I'm a system administrator: No permission to access database 'myDBName'.
It's possible that I might be able to dig up a backup but that would be quite tedious. Is it possible to bring the database to a state where I'm able to do a CHECKDB at least...?
-- Lumbago "Real programmers don't document, if it was hard to write it should be hard to understand"
We recently migrated our production server from SQL 2005 (Standard) on Win2003(32-bit) to SQL2012 (Standard; v11.0.3000) on Win2008-R2(64bit). Single-server Dell R510 with 1.2TB storage. Everything went smoothly; the only nagging issue remaining is failure of our maintenance jobs. I tracked the issue down to failure of DBCC CHECKDB. Specifically, the error is:Executed as user: NT SERVICESQLSERVERAGENT. The database could not be exclusively locked to perform the operation. [SQLSTATE 42000] (Error 5030) Check statement aborted. The database could not be checked as a database snapshot could not be created and the database or table could not be lockedI have Googled this issue and read extensively. For instance, informative blogs (albeit dated) such as these by Paul Randal (Managing
CheckDB by default takes an internal DB snapshot to get the consistent, point-in-time view of the DB that it needs. If that snapshot creation fails, then it will try to get an exclusive database lock before proceeding (same as if you had executed DBCC CHECKDB WITH TABLOCK). The root problem is not that the lock could not be obtained, it's that the internal database snapshot could not be created. msdn.microsoft.com/en-us/library/ms188796.aspx details the specific situations when an internal database snapshot is not created and table locking is attempted.
I have verified the SQLSERVERAGENT service account has full permissions on the SQLDATA directory where the databases reside and has full permissions on each database within the directory. Just for giggles, I created a job (run as SQLSERVERAGENT) that creates and then deletes a text file in the SQLDATA directory. It runs fine.
Also testedI get the snapshot creation error when manually running DBCC CHECKDB against any of our databases and when executing under a variety of administrator accounts that are members of the SQL sysadmin role and the Domain Admins security group (the Domain Admins is a member of the local Administrators group that has full permissions on all SQL directories/folders).
Additionally, the databases in question are small (200MB to 6GB) and the disk has plenty of elbow room (978GB free on 1.22TB RAID5 array) to create the internal database snapshots. CHECKDB doesn't surface an error message that is detailed enough to determine the precise cause of the error. Any example successfully running DBCC CHECKDB on the SQL2012 (Standard) on a Win2008 R2 (64-bit) server.
I followed the advice of Paul Randal, but Im stumped as I am not able to determin what the corruption issues are. This is SQL 2000 and the database is a Solomon database that was recently upgraded to 6.5. the error I get when running the DBCC checkdb is as follows:
Server: Msg 8966, Level 16, State 1, Line 1 Could not read and latch page (1:18645) with latch type SH. sysindexes failed. DBCC execution completed. If DBCC printed error messages, contact your system administrator.
DBCC execution completed. If DBCC printed error messages, contact your system administrator. DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Now, the bad news. I am a bit of a novice and have picked this up from someone who left my company. It appears the latch error has been around for some time and only reared up when I instituted a new back up system that runs a dbcc check befor backing up. I don't think I have any clean backups.
In my environment, there is maintenance plan configured on one of the server and while running DBCC checkdb on a database of size around 200GB, log file usage of tempdb is increasing and causing the maintenance job to fail.
What can I do to make the maintenance job run successfully, size of the tempdb database is only 50GB and recovery model is set to simple. It cannot be increased as the mount point on which it is residing is 50GB.
I am in the process of setting up a dbcc checkdb and dbcc newalloc job for the user database in production. Do I need to include master and msdb to have checkdb and msdb run against them daily?
Any information you can provide will be greatly appreciated. Thanks.
I am running SQL Server 2000 with Service Pack 4. We recently had a rather nasty corruption problem over several of our databases on our server. It primarily affected indexes and page allocation tables. As of yet, we have yet to identify the cause of this problem. We ran hardware diagnostics and no problems were returned, and nothing aside from the errors that alerted us to the issue in the first place were found in the event logs or SQL error logs.
DBCC CHECKDB was ran several times (we ran it on all DBs on the server just to be safe, several came up corrupted) and used that to repair the data, but very quickly new corruptions popped up.
However, this is not the extent of my bewilderment. Due to the need to get our server back online, a couple co-workers decided to detatch the databases and reinstall the SQL server, then reattatch the databases and try and repair them. I am not sure why this would have mattered but it seems to have prevented any new corruptions.
Anyway, while I was repairing the problem databases to bring them back online, one of them has been giving me a particular problem. Several indexes were pretty thoroughly trashed, giving over 1000 consistency errors. There were also around 25 or so allocation errors. I rebuilt all of the indexes to remove the consistency errors, however the allocation errors still remain and CHECKDB will not remove them. Here are the results of my most recent checkdb repair attempt:
Server: Msg 8905, Level 16, State 1, Line 1 Extent (1:886000) in database ID 37 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:886112) in database ID 37 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:886224) in database ID 37 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:886424) in database ID 37 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:886520) in database ID 37 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:886656) in database ID 37 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:886736) in database ID 37 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:886936) in database ID 37 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:887024) in database ID 37 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:887176) in database ID 37 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:887344) in database ID 37 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:887464) in database ID 37 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:887624) in database ID 37 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:887816) in database ID 37 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:887920) in database ID 37 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:888096) in database ID 37 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:888248) in database ID 37 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:888352) in database ID 37 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:888584) in database ID 37 is marked allocated in the GAM, but no SGAM or IAM has allocated it. Could not repair this error. Repairing this error requires other errors to be corrected first. Repairing this error requires other errors to be corrected first. Repairing this error requires other errors to be corrected first. Repairing this error requires other errors to be corrected first. Repairing this error requires other errors to be corrected first. Repairing this error requires other errors to be corrected first. Repairing this error requires other errors to be corrected first. Repairing this error requires other errors to be corrected first. Repairing this error requires other errors to be corrected first. Repairing this error requires other errors to be corrected first. Repairing this error requires other errors to be corrected first. Repairing this error requires other errors to be corrected first. Repairing this error requires other errors to be corrected first. Repairing this error requires other errors to be corrected first. Repairing this error requires other errors to be corrected first. Repairing this error requires other errors to be corrected first. Repairing this error requires other errors to be corrected first. Server: Msg 8905, Level 16, State 1, Line 1 Extent (1:888704) in database ID 37 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:888840) in database ID 37 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:889024) in database ID 37 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:889168) in database ID 37 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:889328) in database ID 37 is marked allocated in the GAM, but no SGAM or IAM has allocated it. Repairing this error requires other errors to be corrected first. Repairing this error requires other errors to be corrected first. Repairing this error requires other errors to be corrected first. Repairing this error requires other errors to be corrected first. Repairing this error requires other errors to be corrected first. Repairing this error requires other errors to be corrected first. CHECKDB found 24 allocation errors and 0 consistency errors not associated with any single object. CHECKDB found 24 allocation errors and 0 consistency errors in database 'PRODUCTION_CATEGORIZER'. repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (PRODUCTION_CATEGORIZER repair_allow_data_loss).
As you can see, it is telling me that the errors cannot be repaired until other errors are corrected first, but there are no other errors! I cannot figure it out. The rest of our databases on the server are now clean, this is the only one that is not working. Does anyone have any suggestions before we restore to the last backup?
I have a few extremely large databases in SQL Server 6.5 sp3 (soon to be 5a - but we won't talk about that!!) NT 4.0 sp4 (about 10 GIG each). I don't have a big window of down-time in order to do any maintenance. Does anyone know of a way to be able to run dbcc checkdb or other dbcc's that I can run to verify the database yet complete within a reasonable amount of time? The last time dbcc checkdb was run, it was started Friday night and still not complete Sunday night. Over a weekend, I may have up to a 24 hour maintenance window.
Any suggestions would be appreciated. Thanks! Toni
Hai , When I ran DBCC CHECK DB of userdatabase, its reporting along with usual messages as Descriptor for system table '8' in database '8' not found in the descriptor hash table. I could'nt understand being familiar error encounterd . Any one will appreciate for the help
I recently took over a SQL server with 300 MB of data. I am relatively new to SQL 6.5 and have been reading that DBCC checkdb and checkalloc should be run at least once per week. Apparently the person before me never ran any of those checks. Is not running the database consistency checks for so long going to present a problem? has anyone run into problems when running those checks? Any advise is greatly appreciated.
I ran "dbcc checkdb(MCMSdb) with no_infomsgs" and I get the following: Server: Msg 8946, Level 16, State 12, Line 2 Table error: Allocation page (1:274992) has invalid PFS_PAGE page header values. Type is 0. Check type, object ID and page ID on the page.
What cane be done to correct this problem? Can this error prevent a user from connecting to the database?
I ran checkdb and found 4 error message on the db.. it seen like same object.. can anyone tell me what it is.. and how can i fix it? thanks !!!!
1. Server: Msg 8976, Level 16, State 1, Line 35 Table error: Object ID 2094630505, index ID 1. Page (1:809859) was not seen in the scan although its parent (1:77885) and previous (1:809767) refer to it. Check any previous errors. 2. Server: Msg 8978, Level 16, State 1, Line 35 Table error: Object ID 2094630505, index ID 1. Page (1:809860) is missing a reference from previous page (1:809859). Possible chain linkage problem. 3. Server: Msg 8976, Level 16, State 1, Line 35 Table error: Object ID 2094630505, index ID 1. Page (1:1453795) was not seen in the scan although its parent (1:1453347) and previous (1:1453796) refer to it. Check any previous errors. 4. Server: Msg 8978, Level 16, State 1, Line 35 Table error: Object ID 2094630505, index ID 1. Page (1:1453801) is missing a reference from previous page (1:1453795). Possible chain linkage problem.
Does anybody know if the results of DBCC CHECKDB are stored anywhere? If yes, where? Also, if you don't select "attempt to repair minor problems" option when you set up the maintenance plan, will SQL Server let you know about any errors Integrity check encounters? If yes, where the erros can be found?
in the SQL 6.5 documentation it says when running the DBCC CHECKDB, you should make the database read Only or DBO use only. Do you guys know if SQL 6.5 locks rows while this runs? In SQL 7.0/2000 it only locks the schema.
I am using windows nt40 and sql server 6.5 on a DEC ALPHA and accidentlly started a dbcc checkdb. Is it possible to stop the process with out damaging the database?
When running dbcc checkdb from my workstation(nt) I recieve some of the output and then I get "Connection Broken" this is on a 6.5 machine with the service pack 5, what could be causing my ODBC connection to drop during the proccess of running checkdb?
How can I make the dbcc checkdb fail so I can get the errors displayed in the report log? DBCC Checkdb is the step in the integrity job that I run once a month. What I am trying to do is when the dbcc checkdb fails for any reason, I want to get notified so I can correct the problem. I don't want to use repair fast or any other repair parameters that you can select when you run dbcc checkdb function because most of my dbs are 24x7.
I have a job set up that runs the dbcc checkdb and puts the results into a table. Then I run a query against this table to check the results of dbcc checkdb. If there are errors, I get a page that lets me know that there are some problems. When I ran this job on my production server, the job failed stating that there are problems with data integrity. So I copied this db to a dev server and recreated the job just like I have in prod. The job completed successfully withou any errors. Can anybody tell me what to look at to figure out why it failed on the prod server?
Madhur writes "Last week DBCC CHECKDB <database name> took 2 Hrs to complete on a database. Today again i have started but with the following command: dbcc checkdb (<database name>, REPAIR_FAST ).
It is now running for more than 2.5 Hrs now.
Does the execution time increases even when the DB is consistent?
Can we cancel the execution in the middle? What consequences it may have on the db?
I have a db that is about 50Gigs. Last night it went into a suspect mode and I have not been able to get any of my tables to display. I am running the dbcc checkdb. I have been running it for over 7 hrs. Do you have any suggestions as to what I should do or do you have any ideas as to how long this process might take?
Ricardo writes "We are consistently getting this error. We have check the hardware and nothing appears in the checkdk, can you help.
Thanks
Ricardo
dbcc checkdb (virtualrequest) DBCC results for 'tblVRAnswers'. Server: Msg 8928, Level 16, State 1, Line 1 Object ID 370256524, index ID 3: Page (1:243518) could not be processed. See other errors for details. Server: Msg 8939, Level 16, State 1, Line 1 Table error: Object ID 370256524, index ID 3, page (1:243518). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1. There are 9608 rows in 106 pages for object 'tblVRAnswers'.
CHECKDB found 0 allocation errors and 2 consistency errors in database 'VirtualRequest'.
dbcc checkdb (virtualrequest) DBCC results for 'tblvrquestions'. Server: Msg 8952, Level 16, State 1, Line 1 Table error: Database 'VirtualRequest', index 'tblVRRequestedItems.IX_NC_tblVRRequestedItems_CurrentStatusID' (ID 784825958) (index ID 2). Extra or invalid key for the keys: Server: Msg 8956, Level 16, State 1, Line 1 Index row (1:214293:372) with values (CurrentStatusID = 3 and RequestedItemID = 413260) points to the data row identified by (). There are 6614 rows in 103 pages for object 'tblvrquestions'.
CHECKDB found 0 allocation errors and 1 consistency errors in database 'VirtualRequest'
dbcc checkdb (virtualrequest) DBCC results for 'tblvrquestions'. Server: Msg 8952, Level 16, State 1, Line 1 Table error: Database 'VirtualRequest', index 'tblVRRequestedItems.IX_NC_tblVRRequestedItems_CurrentStatusID' (ID 784825958) (index ID 2). Extra or invalid key for the keys: Server: Msg 8956, Level 16, State 1, Line 1 Index row (1:214293:372) with values (CurrentStatusID = 3 and RequestedItemID = 413260) points to the data row identified by (). There are 6614 rows in 103 pages for object 'tblvrquestions'.
CHECKDB found 0 allocation errors and 1 consistency errors in database 'VirtualRequest'."
My nightly maintenance task runs fine normally. Last night it didn't. When it got to DBCC CHECKDB for an audit database (it gets populated from triggers in other databases; one of the tables has over a million records), the live database server shut down and did not come back up. DBCC CHECKDB completed in 6 seconds with no errors. The next task in the sequence that would have run (but the log has no message of it completing or failing) was DBCC INDEXDEFRAG on that audit table with over a million records.
Even the OFF button on the 64-bit Dell server (SQL2005, Windows Server Enterprise x64 2003 SP1, 16 gig ram) did not work. There wasn't even the blue screen of death. It was just a blue screen. A plug out and plug back in was required.
The only recent configuration change has been that we have had Dell install a piece of disk-level replication software called Double Take.
When i run TKizers sp to check database integrity. I'm getting this error.
Executed as user: IAPESQLAdmin. ...536) DBCC results for 'sysobjects'. [SQLSTATE 01000] (Message 2536) There are 1364 rows in 23 pages for object 'sysobjects'. [SQLSTATE 01000] (Message 2593) DBCC results for 'sysindexes'. [SQLSTATE 01000] (Message 2536) There are 138 rows in 5 pages for object 'sysindexes'. [SQLSTATE 01000] (Message 2593) DBCC results for 'syscolumns'. [SQLSTATE 01000] (Message 2536) There are 5251 rows in 104 pages for object 'syscolumns'. [SQLSTATE 01000] (Message 2593) DBCC results for 'systypes'. [SQLSTATE 01000] (Message 2536) There are 26 rows in 1 pages for object 'systypes'. [SQLSTATE 01000] (Message 2593) DBCC results for 'syscomments'. [SQLSTATE 01000] (Message 2536) There are 2115 rows in 1112 pages for object 'syscomments'. [SQLSTATE 01000] (Message 2593) DBCC results for 'sysfiles1'. [SQLSTATE 01000] (Message 2536) There are 2 rows in 1 pages for object 'sysfiles1'. [SQLSTATE 01000] (Message 2593) DBCC results for 'syspermissions'. [SQLSTATE... The step failed.
