March 16, 2012 at 1:41 am
Hi,
We tested the Trace Flag 610, and when only this one is activated, we got an 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 cannot be opened. It has been marked SUSPECT by recovery.
We got it on the Production Environment + Test Env., that means with different hardware.
Then, is it possible it's a bug? Or do you have an idea?
Thank you
March 16, 2012 at 2:03 am
Also asked here: http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=172135
Frankly, my advice remains the same. Check Connect and see if there are any matching bugs (I know there's a least one rollback-related bug but without knowing what the SSIS package does I can't say whether it's relevant for you), check your hardware and if you think it's a bug open a CSS case.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply