Error 7987, soliciting suggestions
-
(I've tried to clean the names of databases, components, tasks, and dataflows, but otherwise, most of this is copy&paste info.)
****
When I run the SSIS packages in the debugger, I get a failure, and here are the first error messages (about 1000 lines into the output buffer):
Information: 0x4004300C at MyOtherDataFlow, DTS.Pipeline: Execute phase is beginning.
Information: 0x0 at MyOtherDataFlow, component "MyCustomComponent#2" (418): Doing nice stuff 2006-02-27 13:57:58
Error: 0xC0202009 at TroubledDataFlowName, TroubledTable [8299]: An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Warning: Fatal error 7987 occurred at Feb 27 2006 1:58PM".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Warning: Fatal error 7987 occurred at Feb 27 2006 1:57PM".
Error: 0xC0209029 at MyDataFlow, TroubledTable [8299]: The "input "OLE DB Destination Input" (8312)" failed because error code 0xC020907B occurred, and the error row disposition on "input "OLE DB Destination Input" (8312)" specifies failure on error. An error occurred on the specified object of the specified component.
Error: 0xC0047022 at MyDataFlow, DTS.Pipeline: The ProcessInput method on component "TroubledTable" (8299) failed with error code 0xC0209029. The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running.
Error: 0xC0047021 at MyDataFlow, DTS.Pipeline: Thread "WorkThread0" has exited with error code 0xC0209029.
Information: 0x40043008 at MyDataFlow, DTS.Pipeline: Post Execute phase is beginning.
****
select @@version
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
****
Checking the Application Event Log, I see errors today corresponding to this, and errors from Friday corresponding to errors on Friday.
** Today Application Event Log
Error: 7987, Severity: 22, State: 3
A possible database consistency problem has been detected on database 'MyWorkingDatabase'. DBCC CHECKDB and should be run on database 'MyWorkingDatabase'.
*** and the following which I just discovered (I had been chasing an HRESULT which is not really documented, since Friday, not realizing that it was another database inconsistency occurrence)
** (Friday, Application Event Log)
Error: 823, Severity: 24, State: 7
I/O error (bad page ID) detected during read at offset 0x00000019de2000 in file 's:\Program Files\Microsoft SQL Server\MSSQL\data\tempdb.mdf'.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
****** DBCC CHECKDB (MyWorkingDatabase) WITH ALL_ERRORMSGS, NO_INFOMSGS
The command(s) completed successfully.
****** DBCC CHECKCATALOG (MyWorkingDatabase) WITH ALL_ERRORMSGS, NO_INFOMSGS
The command(s) completed successfully.
****** DBCC CHECKDB (model) WITH ALL_ERRORMSGS, NO_INFOMSGS
The command(s) completed successfully.
****** DBCC CHECKCATALOG (model) WITH ALL_ERRORMSGS, NO_INFOMSGS
The command(s) completed successfully.
****** DBCC CHECKDB (tempdb) WITH ALL_ERRORMSGS, NO_INFOMSGS
The command(s) completed successfully.
****** DBCC CHECKCATALOG (tempdb) WITH ALL_ERRORMSGS, NO_INFOMSGS
The command(s) completed successfully.
---------------------------
I'm not the system administrator, so I cannot speak authoritatively on hardware and backup issues.
This is the third virtual machine on which I've had sporadic SQL Server errors.
I have two main jobs.
- One is all T-SQL, and it generally works.
- The other involves a collection of SQL Server SSIS packages (now ported to the release version). They exhibit these types of apparent database inconsistency errors frequently -- so frequently that I cannot get the desired database populated with them.
We tried moving from vmware ESX Server to vmware GSX server, I think.
We tried increasing the SQL Server machine's memory up to 3Gb.
The current virtual machine/SQL Server 2000 database engine, which I am using, has SQL Server 2000 client tools, SQL Server 2000 Server, SQL Server 2005 Server (not being used), and SQL Server 2005 client tools (including SSIS, which I am obviously using).
This virtual machine was created recently, and has never had any CTP or beta builds of SQL Server 2005 on it.
As I mentioned elsewhere, at one point I found a technical article somewhere at Microsoft about some setting which, if I recall correctly, made SQL Server preserve some recent error info in some type of ring buffer, to be dumped if inconsistency was found -- but I cannot recall where I found that tech article.
-
This was removed by the editor as SPAM
-
Hi,
Generally 823 error message occurs when:
•
A ReadFile, WriteFile, ReadFileScatter, WriteFileGather, or etOverlappedResult operation results in any operating system error code.
•
The page number on the page read from disk is not the expected page ID.
•
The data transfer size is not valid.
•
A torn read is detected when torn page detection is enabled.
•
A stale read is detected when stale read detection is enabled.
SQL Server 2000 uses standard Windows API calls, such as ReadFile, ReadFileScatter, WriteFile, and WriteFileGather, to perform I/O with its database files. When SQL Server 2000 uses the Windows API calls, the file has already been opened successfully, or SQL Server 2000 would not try to read from it or write to it. Therefore, if a Windows API call is not successful and if the error is anything other than the operating system error 6 ("Invalid Handle"), the error is likely being raised in Windows or by a lower-level software component, such as a device driver. Because the operating system error 6 is an invalid handle, the problem may occur if SQL Server is using an invalid handle to make a Windows API call. However, this may still be a system problem.
Steps you should take to troubleshoot is that :
1. Please check your hardware with your hardware vendore.
2. Run SQLIOSTRESS utility. You can use this utility to perform stress tests on disk subsystems to simulate Microsoft SQL Server 2000 and Microsoft SQL Server 7.0 read, write, checkpoint, backup, sort, and read ahead activities.
3. Enable the trace flag 818 as SQL startup parameter.
Trace flag 818 enables an in-memory ring buffer that is used for tracking the last 2,048 successful write operations that are performed by the computer running SQL Server, not including sort and workfile I/Os. When errors such as Error 605, 823, or 3448 occur, the incoming buffer's log sequence number (LSN) value is compared to the recent write list. If the LSN that is retrieved during the read operation is older than the one specified during the write operation, a new error message is logged in the SQL Server error log. Most SQL Server write operations occur as checkpoints or as lazy writes. A lazy write is a background task that uses asynchronous I/O. The implementation of the ring buffer is lightweight, thereby making the performance affect on the system negligible.
I still recomend you to check the hardware of the system and update to latest firmaware. I have seen in many cases that the hardware vendore will report that there is no problem with the hardware. In that case plaese run the SQLIOSTRESS and check the output which reports for stale read / lost write.
Lost Write: A successful call to the WriteFile API, but the operating system, a driver, or the caching controller does not correctly flush the data to the physical media even though SQL Server is informed that the write was successful.
Stale Read: A successful call to the ReadFile API, but the operating system, a driver, or the caching controller incorrectly returns an older version of the data.
Links for your reference:
http://support.microsoft.com/kb/307775/en-us
http://support.microsoft.com/kb/231619
http://support.microsoft.com/kb/828339/en-us
http://support.microsoft.com/kb/826433/en-us
Regards,
Minaz Amin
email id : meenakshikundar@yahoo.com
Phno: 9341735900.
"More Green More Oxygen !! Plant a tree today"
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply