Are you the publisher? Claim or contact us about this channel


Embed this content in your HTML

Search

Report adult content:

click to rate:

Account: (login)

More Channels


Channel Catalog


Channel Description:

SQLServerCentral

older | 1 | .... | 4 | 5 | (Page 6) | 7 | 8 | .... | 12 | newer

    0 0

    Hi Folks,We are receiving following message on one of the user databases and unable to repair via DBCC check DB. ALso, we don't have clean backups for last 3-4 months. Please advise on how to fix the issue.Msg 8992, Level 16, State 1, Line 1Check Catalog Msg 3853, State 1: Attribute of row in sys.columns does not have a matching row in sys.objects

    0 0

    HelloI have a server that is reporting NTFS errors; one of the error messages implicates d:\$MFT as being possibly corrupt. My SQL data files reside on this drive.The Master File Table holds information about all files on the disk, so I imagine if the corruption was to occur SQL may not be able to read data from one of the MDFs or NDFs?I imagine CHECKDB will not be a relevant consistency check, and the only way to resolve this error would be a chkdsk /r?Any help would be appreciated. We haven't had any corruption reports in the SQL error log yet. I imagine it could get serious depending on what parts of the MFT are corrupted (as previously stated it could affect SQL's ability to read MDFs or NDFs)?Thanks

    0 0

    Hi,I initially took backup from SQL Server 2012 (database compatibility mode was set to SQL Server 2008 (100)) but when I try to restore that backup on SQL Server 2008 R2 it is giving me error as "Specified cast is not valid".I would appreciate if anyone can help me or if there is any alternate solution to backup from SQL Server 2012 and successfully restore it on SQL Server 2008 R2, please let me know.Thank you.

    0 0

    While i try to attach the mdf file i got the error, The Error is: [b]DatabaseName.mdf is not SQL Server Database Primary Data File[/b]The[b] SQL server Error No. 5171[/b]

    0 0

    --Error Number 824DESCRIPTION: SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:845407; actual 1:607839). It occurred during a read of page (1:845407) in database ID 46 at offset 0x0000019ccbe000 in file ‘xx.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.--If run this , I am getting below specified error message DBCC CHECKDB ('DBname') WITH NO_INFOMSGS, ALL_ERRORMSGS--Error message:Msg 8946, Level 16, State 12, Line 1Table error: Allocation page (1:145584) has invalid PFS_PAGE page header values. Type is 0. Check type, alloc unit ID and page ID on the page.Msg 8921, Level 16, State 1, Line 1Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.Msg 8998, Level 16, State 2, Line 1Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 6 pages from (1:145584) to (1:153671). See other errors for cause.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 72057594050707456 (type Unknown), page (1:145584). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 62916617 and -4.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 72057594050707456 (type Unknown), page (1:145584). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 62916617 and -4.Can you suggest me to resolve this please….Can you please let me know if you need any other details….Thank you in Advance…..Krishna

    0 0

    Hi All,What are the available options of running CHECKDB on VLDBs and where my prod maintenance window is less?I can think of backup and restore option. Are there any other viable options available?Thanks in Advance.

    0 0

    Hi,I would like to know , just in case CHECKDB maintenance job is running for 5 hours and admin chosen to kill that operation.Usually the job takes not more than 2 hrs.What can happen if CHECKDB is killed in the middle of process?What are steps to be taken care even before thinking of killing CHECKDB operation ?Did anyone faced this situation any time? if so, please do share on how to handle such situation.Thanks in advance.

    0 0

    So Saturday the drive that holds our DB's ran out of space and on Monday I fixed the space issue and moved my backups to a new drive to reduce space. I ran a successful DB Integrity check after and the DB has been functioning without any complaints since but...I noticed my full backups went from 28GB down to 4GB. The db properties under General, Database says the size is 33033.63MB with 27.36MB free space.Can someone explain what is going on all of a sudden after this event or help me out?

    0 0
  • 05/29/14--02:53: Logical Consistency Error
  • It seems that I have some corruption within a user database. Running DBCC CHECKDB results in the following error:[quote]Msg 8921, Level 16, State 1, Line 1Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.[/quote]I tried running DBCC CHECKALLOC and DBCC CHECKCATALOG. Both complete without an error. Next, I ran DBCC CHECKTABLE on each table. I found a single table that produced the same error as above from DBCC CHECKDB.When I try to query the table (for instance, SELECT COUNT(*) FROM dbo.Table), SSMS returns this error (which is identical to the corresponding errors in the SQL Server error log and the system event log):[quote]Msg 824, Level 24, State 2, Line 1SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:98530; actual 57553:769). It occurred during a read of page (1:98530) in database ID 26 at offset 0x000000301c4000 in file 'D:\Program Files\Microsoft SQL Server\MSSQL10.ATLCSETASQL\MSSQL\DATA\xt3_newbraunfels_01.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.[/quote]Next, I took the info from above and ran this:[code="sql"]DBCC TRACEON (3604)DECLARE @DBId INT = DB_ID(DB_Name())DBCC PAGE( @DBId, 1, 98530 )[/code]I'm trying to interpret the output from DBCC PAGE (see attached). However, I'm not sure how to proceed.

    0 0

    Our schedule CHECKDB failed today for out largest DB (4TB). Attempting to isolate the problem I start with the index filegroup and ran [code="sql"]DBCC CHECKFILEGROUP (N'NCIndexes') WITH PHYSICAL_ONLY, NO_INFOMSGS, ALL_ERRORMSGS[/code]This worked just fine, when i removed the PHYSICAL_ONLY I got the following errors:[quote]Msg 5269, Level 16, State 1, Line 1Check terminated. The transient database snapshot for database 'MYDB' (database ID 7) has been marked suspect due to an IO operation failure. Refer to the SQL Server error log for details.Msg 0, Level 20, State 0, Line 0A severe error occurred on the current command. The results, if any, should be discarded.[/quote]A couple of things to note:1. The window I was running this from lost its connection completely after the failure (i.e. no longer connected to the server)2. There is no stack dump or further logging in the SQL Error other than[quote]Error: 17053, Severity: 16, State: 1.N:\CA_NCIndexes.ndf:MSSQL_DBCC23: Operating system error 1450(Insufficient system resources exist to complete the requested service.) encountered.The operating system returned error 1450(Insufficient system resources exist to complete the requested service.) to SQL Server during a write at offset 0x000063064d0000 in file 'N:\CA_NCIndexes.ndf:MSSQL_DBCC23'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.[/quote]And then a informational message got printed out:DBCC CHECKFILEGROUP (COREACQUIRE) WITH all_errormsgs, no_infomsgs executed by FLEETONE\miraultsj found 0 errors and repaired 0 errors. Elapsed time: 2 hours 17 minutes 14 seconds. Internal database snapshot has split point LSN = 0006ffe5:0167d9d1:000b and first LSN = 0006ffe5:0167d5ba:0001.Any ideas?

    0 0
  • 06/25/14--23:17: Phantom FK violation
  • I use a proc to delete a row from a PK table, based on a query of "get the PK ids that don't exist in the FK table". The proc fails with an FK violation. The proc does a simple "delete from PK table where pk_id = n"So I delete the PK row manually (delete from PK table where pk_id = n). No complaints. Fine -- well not really, but...Verified that the row does not exist in either the PK nor FK tables.So I:- DBCC'ed, no errors reported. - Dropped and re-created the FK WITH CHECK. No complaints.- Call the proc again just for good times, and still get the FK violation????? - Put the delete statement in the sproc into a try...catch block to the sure it was actually failing at that point, confirmed. There are no triggers on either table.There must be a SNAFU somewhere. Can someone point me in the right direction?Thanks!

    0 0

    Hi,Two months back Installed SQL server 2008 enterprise edition in PC based server.. Now database running with consistency error.. Could anyone suggestion me, how to resolve this error? DBCC Checkdb 'dbname' with data_purityResultMsg 8928, Level 16, State 1, Line 1Object ID 485576768, index ID 0, partition ID 72057594040745984, alloc unit ID 72057594041794560 (type In-row data): Page (1:425) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 485576768, index ID 0, partition ID 72057594040745984, alloc unit ID 72057594041794560 (type In-row data), page (1:425). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.SQL Error Log and system Event ViewerMessageSQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0xbfc9c6fa; actual: 0x9fc9c6fa). It occurred during a read of page (1:425) in database ID 5 at offset 0x00000000352000 in file 'D:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\HWDATA7.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.Thanksananda

    0 0

    Hi All,I recently found (from our weekend maintenance) that one of our vendor databases encountered a corruption notice and am trying to figure out (without going straight to allow_repair_data_loss) what rows have the 'bad' data and what is the actual cause of this error:I ran this command: dbcc checkdb ('pmdb_cn') WITH DATA_PURITYResults:[code="sql"]DBCC results for 'POBS'.Msg 2570, Level 16, State 3, Line 1Page (1:110113), slot 10 in object ID 2121058592, index ID 1, partition ID 72057594055688192, alloc unit ID 72057594065453056 (type "In-row data"). Column "pobs_name" value is out of range for data type "varchar". Update column to a legal value.Msg 2570, Level 16, State 3, Line 1Page (1:110113), slot 14 in object ID 2121058592, index ID 1, partition ID 72057594055688192, alloc unit ID 72057594065453056 (type "In-row data"). Column "pobs_name" value is out of range for data type "varchar". Update column to a legal value.Msg 2570, Level 16, State 3, Line 1Page (1:110117), slot 38 in object ID 2121058592, index ID 1, partition ID 72057594055688192, alloc unit ID 72057594065453056 (type "In-row data"). Column "pobs_name" value is out of range for data type "varchar". Update column to a legal value.Msg 2570, Level 16, State 3, Line 1Page (1:110117), slot 42 in object ID 2121058592, index ID 1, partition ID 72057594055688192, alloc unit ID 72057594065453056 (type "In-row data"). Column "pobs_name" value is out of range for data type "varchar". Update column to a legal value.There are 299 rows in 7 pages for object "POBS".CHECKDB found 0 allocation errors and 4 consistency errors in table 'POBS' (object ID 2121058592).DBCC results for 'HQDATA'.There are 0 rows in 0 pages for object "HQDATA".DBCC results for 'TPROJMAP'.There are 0 rows in 8 pages for object "TPROJMAP".DBCC results for 'WRK_LOG_RESULTS'.There are 0 rows in 0 pages for object "WRK_LOG_RESULTS".CHECKDB found 0 allocation errors and 4 consistency errors in database 'PMDB_CN'.DBCC execution completed. If DBCC printed error messages, contact your system administrator.[/code]The table structure is this:[code="sql"]CREATE TABLE [dbo].[POBS]( [pobs_id] [int] NOT NULL, [seq_num] [int] NOT NULL, [pobs_name] [varchar](255) NOT NULL, [pobs_parent_id] [int] NULL, [pobs_descr] [varchar](255) NULL, [pobs_manager] [varchar](255) NULL, [update_date] [datetime] NULL, [update_user] [varchar](255) NULL, [create_date] [datetime] NULL, [create_user] [varchar](255) NULL, [delete_session_id] [int] NULL, [delete_date] [datetime] NULL, CONSTRAINT [pk_pobs] PRIMARY KEY CLUSTERED ( [pobs_id] ASC)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]) ON [PRIMARY][/code]I'm running on SQL Server 2008 R2 + SP3When I do a count of the records in Management Studio, I get 303.DBCC CHECKDB output says 299 rows.So am I really missing 4 rows? Or is it indicating that there are 4 rows that have invalid data in the particular column? -- which wouldn't make sense as I would've figured the datatype definition wouldn't have allowed the data to be inserted in the first place.Thanks in advance

    0 0

    Problem:Person tbl holds personal information for everyone (patient, and emergency contacts).Due to bad data entry, we have some people name misspelled under the person tbl who are either husband or wife (relationship type W or H) to the patient. To resolve the issue 1) We need to identify if the person is listed more than one time, and who are related to the same patient with same relation type (Wife or husband) and has same phone to find the names which are misspelled. For example, I have person name first name Lina and Linda entered twice, she has relationtype = W to patient 1, and also she got same phones listed in phone tbl. We want to list both records of Lina and Linda who is wife of patient 1 and her phone is the same in phone tbl. That way we identify that Linda name was typed incorrectly. Below is the schema, I am also attaching same data as well. Person_Info: PersonID, Person Info contains everyone (patient, vistor, Emergecy contact) First and last namesPatien_Info: PatientID, table contains patient ID and other information Patient_PersonRelation: Person_ID, patientID, relationAdress: Contains address of all person and patient (key PersonID)Phone: Contains phone # of everyone (key is personID)

    0 0

    Hi All,I'm troubleshooting an issue that's occurred in one of our applications, which produced error 669, severity 22 - The row object is inconsistent. Please rerun the query.I've tried doing some research into this, and very little has come up.The application itself is written in cold fusion and is using a loop to update a table (I'm currently rewriting this as a stored procedure), which I'll happily admit I know diddly squat about; so I've no idea whether that might cause an issue.If I run the code manually in SQL it runs fine.I've also run DBCC CHECKTABLE against the tables in question, which has shown no issue, and also run DBCC CHECKALLOC as well and no issues there. At this point I won't be able to run CHECKDB until I get a maintenance window.The only other thing of note I can think of is that the page verification is set to TORN_PAGE_DETECTION; I'm going to request changing this to CHECKSUM, but not sure if that might cause an issue that means the corruption checks aren't as good as they might be?CheersMatthew

    0 0

    I backed up a production database from Data Center A, backed it up across the network and restored it to a SQL Server in Data Center B which is nonproduction. THe restore worked fine. However, a DBCC CHECKDB shows the below errors. If I run a DBCC CHECKDB on the DB in DataCenter A it says zero errors. The SQL Server in DataCenter A is SQL2008R2 SP1 and the one in DataCenter B is SQL2008R2 SP2. My question is that my Storage guys say there is no issues with the back end storage. I say that cannot be... He thinks we need to rule out the SQL Server binaries as the issue. I say this is data corruption. Thoughts?The SQL Server log when I restored the db says no errors. I know that is a very minor checkdb routine that is run upon a db restore.CHECKDB for database 'TESTEDB' finished without errors on 2014-08-05 04:15:10.257 (local time). Here is the output of the checkdb:Msg 8928, Level 16, State 1, Line 1Object ID 805577908, index ID 1, partition ID 72057598210211840, alloc unit ID 72057597152591872 (type In-row data): Page (1:91593) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 805577908, index ID 1, partition ID 72057598210211840, alloc unit ID 72057597152591872 (type In-row data), page (1:91593). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.Msg 8976, Level 16, State 1, Line 1Table error: Object ID 805577908, index ID 1, partition ID 72057598210211840, alloc unit ID 72057597152591872 (type In-row data). Page (1:91593) was not seen in the scan although its parent (1:103922) and previous (1:122896) refer to it. Check any previous errors.Msg 8978, Level 16, State 1, Line 1Table error: Object ID 805577908, index ID 1, partition ID 72057598210211840, alloc unit ID 72057597152591872 (type In-row data). Page (1:91597) is missing a reference from previous page (1:91593). Possible chain linkage problem.CHECKDB found 0 allocation errors and 4 consistency errors in table 'RPT_Q_ProjectMetrics' (object ID 805577908).Msg 8928, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057594124828672 (type LOB data): Page (1:476600) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057594124828672 (type LOB data), page (1:476600). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057594124828672 (type LOB data). The off-row data node at page (1:476600), slot 0, text ID 523304960 is referenced by page (1:400692), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057594124828672 (type LOB data): Page (1:476646) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057594124828672 (type LOB data), page (1:476646). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057594124828672 (type LOB data). The off-row data node at page (1:476646), slot 0, text ID 1045168128 is referenced by page (1:476007), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057594124828672 (type LOB data): Page (1:490950) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057594124828672 (type LOB data), page (1:490950). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057594124828672 (type LOB data). The off-row data node at page (1:490950), slot 0, text ID 985333760 is referenced by page (1:490930), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057594124828672 (type LOB data): Page (1:493604) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057594124828672 (type LOB data), page (1:493604). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057594124828672 (type LOB data). The off-row data node at page (1:493604), slot 0, text ID 613679104 is referenced by page (1:493593), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057594124828672 (type LOB data): Page (1:496267) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057594124828672 (type LOB data), page (1:496267). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057594124828672 (type LOB data). The off-row data node at page (1:496267), slot 0, text ID 179961856 is referenced by page (1:495862), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057594124828672 (type LOB data): Page (1:546836) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057594124828672 (type LOB data), page (1:546836). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057594124828672 (type LOB data). The off-row data node at page (1:546836), slot 0, text ID 225050624 is referenced by page (1:546598), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057594124828672 (type LOB data): Page (1:554558) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057594124828672 (type LOB data), page (1:554558). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057594124828672 (type LOB data). The off-row data node at page (1:554558), slot 0, text ID 2686976 is referenced by page (1:554481), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057594124828672 (type LOB data): Page (1:571110) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057594124828672 (type LOB data), page (1:571110). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057594124828672 (type LOB data). The off-row data node at page (1:571110), slot 0, text ID 1405157376 is referenced by page (1:570190), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057594124828672 (type LOB data): Page (1:571405) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057594124828672 (type LOB data), page (1:571405). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057594124828672 (type LOB data). The off-row data node at page (1:571405), slot 0, text ID 1107755008 is referenced by page (1:571251), slot 0, but was not seen in the scan.Msg 8929, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057597161635840 (type In-row data): Errors found in off-row data with ID 2686976 owned by data record identified by RID = (1:2714:21)Msg 8929, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057597161635840 (type In-row data): Errors found in off-row data with ID 2686976 owned by data record identified by RID = (1:2715:2)Msg 8929, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057597161635840 (type In-row data): Errors found in off-row data with ID 2686976 owned by data record identified by RID = (1:2716:8)Msg 8929, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057597161635840 (type In-row data): Errors found in off-row data with ID 523304960 owned by data record identified by RID = (1:2737:10)Msg 8929, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057597161635840 (type In-row data): Errors found in off-row data with ID 985333760 owned by data record identified by RID = (1:2737:26)Msg 8929, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057597161635840 (type In-row data): Errors found in off-row data with ID 179961856 owned by data record identified by RID = (1:2740:17)Msg 8929, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057597161635840 (type In-row data): Errors found in off-row data with ID 2686976 owned by data record identified by RID = (1:2748:16)Msg 8929, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057597161635840 (type In-row data): Errors found in off-row data with ID 2686976 owned by data record identified by RID = (1:2757:11)Msg 8929, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057597161635840 (type In-row data): Errors found in off-row data with ID 2686976 owned by data record identified by RID = (1:2761:9)Msg 8929, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057597161635840 (type In-row data): Errors found in off-row data with ID 2686976 owned by data record identified by RID = (1:2793:9)Msg 8929, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057597161635840 (type In-row data): Errors found in off-row data with ID 613679104 owned by data record identified by RID = (1:2840:0)Msg 8929, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057597161635840 (type In-row data): Errors found in off-row data with ID 2686976 owned by data record identified by RID = (1:4339:16)Msg 8929, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057597161635840 (type In-row data): Errors found in off-row data with ID 2686976 owned by data record identified by RID = (1:4342:5)Msg 8929, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057597161635840 (type In-row data): Errors found in off-row data with ID 2686976 owned by data record identified by RID = (1:107627:2)Msg 8929, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057597161635840 (type In-row data): Errors found in off-row data with ID 2686976 owned by data record identified by RID = (1:107627:17)Msg 8929, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057597161635840 (type In-row data): Errors found in off-row data with ID 2686976 owned by data record identified by RID = (1:107627:25)Msg 8929, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057597161635840 (type In-row data): Errors found in off-row data with ID 225050624 owned by data record identified by RID = (1:107627:28)Msg 8929, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057597161635840 (type In-row data): Errors found in off-row data with ID 1045168128 owned by data record identified by RID = (1:110237:4)Msg 8929, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057597161635840 (type In-row data): Errors found in off-row data with ID 2686976 owned by data record identified by RID = (1:110318:9)Msg 8929, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057597161635840 (type In-row data): Errors found in off-row data with ID 1405157376 owned by data record identified by RID = (1:110780:10)Msg 8929, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057597161635840 (type In-row data): Errors found in off-row data with ID 2686976 owned by data record identified by RID = (1:526312:12)Msg 8929, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057597161635840 (type In-row data): Errors found in off-row data with ID 2686976 owned by data record identified by RID = (1:526315:34)Msg 8929, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057597161635840 (type In-row data): Errors found in off-row data with ID 2686976 owned by data record identified by RID = (1:526317:3)Msg 8929, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057597161635840 (type In-row data): Errors found in off-row data with ID 2686976 owned by data record identified by RID = (1:526318:6)Msg 8929, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057597161635840 (type In-row data): Errors found in off-row data with ID 225050624 owned by data record identified by RID = (1:544144:4)Msg 8929, Level 16, State 1, Line 1Object ID 1945773989, index ID 1, partition ID 72057598217420800, alloc unit ID 72057597161635840 (type In-row data): Errors found in off-row data with ID 1107755008 owned by data record identified by RID = (1:544147:5)CHECKDB found 0 allocation errors and 53 consistency errors in table 'SGM_FileStore' (object ID 1945773989).CHECKDB found 0 allocation errors and 57 consistency errors in database 'TESTDB'.repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (TESTDB).

    0 0
  • 09/03/14--04:02: CHECKDB errors
  • Over the weekend I noticed a schedule DB integrity check failing. The DB size is about 225GB and in the past have had no issues. At first I received two emails with errors like this:[quote]DESCRIPTION: Failed to initialize the Common Language Runtime (CLR) v2.0.50727 with HRESULT 0x80004005. You need to restart SQL Server to use CLR integration features.DESCRIPTION: A read of the file 'E:\VDBs\CORELIBRARY.mdf' at offset 0x000004c44f0000 succeeded after failing 3 time(s) with error: 23(Data error (cyclic redundancy check).). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.[/quote]Which I thought was odd, and after looking at the job that ran the CHECKDB, I decided to run it myself:[code="sql"]DBCC CHECKDB('SSRS') WITH ALL_ERRORMSGS , NO_INFOMSGS[/code]This was the output:[quote]Msg 6512, Level 16, State 27, Line 6Failed to initialize the Common Language Runtime (CLR) v2.0.50727 with HRESULT 0x80004005. You need to restart SQL Server to use CLR integration features.Msg 6512, Level 16, State 27, Line 6Failed to initialize the Common Language Runtime (CLR) v2.0.50727 with HRESULT 0x80004005. You need to restart SQL Server to use CLR integration features.[/quote]There's no other messages outputted to the screen.Has anyone encountered this error before when running a DBCC CHECKDB?

    0 0

    Again, I've received another notification that just doesn't give me a warm and fuzzy feeling, despite the final message. I ran a CHECKDB on a large database last night (about 2TB), got the following messages:[quote]The operating system returned error 1450(Insufficient system resources exist to complete the requested service.) to SQL Server during a write at offset 0x00002516b1c000 in file 'H:\MYDB.mdf:MSSQL_DBCC37'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.Error: 17053, Severity: 16, State: 1.H:\MYDB.mdf:MSSQL_DBCC37: Operating system error 1450(Insufficient system resources exist to complete the requested service.) encountered.The operating system returned error 1450(Insufficient system resources exist to complete the requested service.) to SQL Server during a write at offset 0x00002516b1c000 in file 'H:\MYDB.mdf:MSSQL_DBCC37'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.Error: 17053, Severity: 16, State: 1.H:\MYDB.mdf:MSSQL_DBCC37: Operating system error 1450(Insufficient system resources exist to complete the requested service.) encountered.[/quote]Yet, here's the part that confuses me:[quote]DBCC CHECKDB (MYDB) WITH all_errormsgs, no_infomsgs executed by FLEETONE\F1Onsitelog found 0 errors and repaired 0 errors. Elapsed time: 2 hours 52 minutes 30 seconds. Internal database snapshot has split point LSN = 000a866b:006105c6:0001 and first LSN = 000a866b:006105c5:0001.[/quote]I realize this could be a sparse file problem, but I have over 300 GB of free space on the drive and tempdb has about 300GB free as well. Running an ESTIMATEONLY shows that the process should only take approximately 742 MB of space.I had a similar thing happen last week with another database, and after a series of running various forms of CHECKDB, the end result came back clean with no errors - Is there a potential disk issue here?

    0 0

    I just was handed off another Server.The backups were failing I believe The Network Service does not have permissions to the D:\Backups\Full directory.I tried creating a new Job and I got error message Login does not have permissions.I have a Domain Account which I use for the SQL Server Service account which I use on my Servers.Is that why it is failing?

    0 0
  • 09/10/14--05:43: DBCC CHECKDB & FILESTREAM
  • I’ve run DBCC CHECKDB on multiple servers and this one is a first for me. It's also the first I'm using a DB with Filestream in use. I get the following error when I try to run the job and it hits the specific database. I"m using the Ola.Hallegren Maintenance Solution, but this isn't an issue with the solution. I've run the command on it's own:DBCC CHECKDB('FCA') WITH all_errormsgs, no_infomsgs, data_purity Results:Msg 7905, Level 16, State 1, Line 1Database error: The directory "temp" is not a valid FILESTREAM directory.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 'FCA'. Ola was kind enough to reply to my email query and suggest I ask in the MSDN forums. I figured I'd start here.Thanks for any help.kDBAjan

older | 1 | .... | 4 | 5 | (Page 6) | 7 | 8 | .... | 12 | newer