SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 General SQL Server Forums
 Data Corruption Issues
 TraceFlag 834 and Indexes corrupted
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

titeuf
Starting Member

4 Posts

Posted - 03/06/2012 :  05:42:21  Show Profile  Reply with Quote
Hi,

I have SqlServer 2008 SP3, it has been running for months. We decided to test the TraceFlag 834 (large-page) but after that we got from a job this error:
Unable to find index entry in index ID 2, of table 1063674837, in database 'XXXX'. The indicated index is corrupt or there is a problem with the current update plan. Run DBCC CHECKDB or DBCC CHECKTABLE. If the problem persists, contact product support

And from an other one:
Internal Query Processor Error: The query processor encountered an unexpected error during execution.

Is there a known relation with the TraceFlag?
Thanks

GilaMonster
Flowing Fount of Yak Knowledge

South Africa
4507 Posts

Posted - 03/06/2012 :  07:51:42  Show Profile  Visit GilaMonster's Homepage  Reply with Quote
The index corruption shouldn't be, that's IO-subsystem related. What does CheckDB return?

Do note that traceflag 834 is not recommended. Product support has stated that it can cause problems with memory allocations and very, very seldom improves performance.

--
Gail Shaw
SQL Server MVP
Go to Top of Page

titeuf
Starting Member

4 Posts

Posted - 03/15/2012 :  08:53:47  Show Profile  Reply with Quote
Hi,

I come back to you.
We found out it's not the trace flag 834.
There was 3 acivated TF, and we checked them separately.
When the TF 610 is activated, we got this error from a SSIS job:

Error Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "During undoing of a logged operation in database 'XXXX', an error occurred at log record ID (82254385:1023360:1). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.".
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "The log for database 'XXXX' is not available. Check the event log for related error messages. Resolve any errors and restart the database.".
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "During undoing of a logged operation in database 'XXXX', an error occurred at log record ID (82254385:3868989:319). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.".
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "The log for database 'XXXX' is not available. Check the event log for related error messages. Resolve any errors and restart the database.".
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "During undoing of a logged operation in database 'XXXX', an error occurred at log record ID (82254385:1024028:195). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.".
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "An inconsistency was detected during an internal operation. Please contact technical support.".
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Time-out occurred while waiting for buffer latch type 4 for page (9:1538572), database ID 5.".

The database is down.

Do you have an idea?
Thank you
Go to Top of Page

GilaMonster
Flowing Fount of Yak Knowledge

South Africa
4507 Posts

Posted - 03/15/2012 :  09:40:35  Show Profile  Visit GilaMonster's Homepage  Reply with Quote
Restore from backup, check the IO subsystem for errors.

--
Gail Shaw
SQL Server MVP
Go to Top of Page

titeuf
Starting Member

4 Posts

Posted - 03/15/2012 :  10:09:19  Show Profile  Reply with Quote
Thank you Gail!

The problem is we got errors on the Production Env. but also on the Test Env., that means with different hardware.
Then, is it possible this is a bug?
Go to Top of Page

GilaMonster
Flowing Fount of Yak Knowledge

South Africa
4507 Posts

Posted - 03/15/2012 :  10:31:13  Show Profile  Visit GilaMonster's Homepage  Reply with Quote
Always a small possibility, if you think it's a bug open a CSS call. Double-check all your hardware first and search Connect to make sure there's no existing bug filed for this.

--
Gail Shaw
SQL Server MVP
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.05 seconds. Powered By: Snitz Forums 2000