on 05-26-2008 5:06 PM
Hello all,
I am trying to attach sql2000 datafile to SQL2005. I have been following sap note 799058. When attaching the datafiles, I am getting the following error, Any one has seen this?
Date,Source,Severity,Message
05/26/2008 08:32:35,spid55,Unknown,SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
05/26/2008 08:32:35,spid55,Unknown,SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
05/26/2008 08:32:35,spid55,Unknown,SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
05/26/2008 08:32:35,spid55,Unknown,SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 9:13803264; actual 0:0). It occurred during a read of page (9:13803264) in database ID 5 at offset 0x00001a53e00000 in file 'G:\R3TDATA8\R3TDATA8\R3TDATA8.NDF'. 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<c/> see SQL Server Books Online.
05/26/2008 08:32:35,spid55,Unknown,Error: 824<c/> Severity: 24<c/> State: 2.
05/26/2008 08:32:33,spid55,Unknown,Analysis of database 'R3T' (5) is 100% complete (approximately 0 seconds remain). This is an informational message only. No user action is required.
05/26/2008 08:32:33,spid55,Unknown,Starting up database 'R3T'.
05/26/2008 08:20:00,Logon,Unknown,Login failed for user 'CORP\SAPServiceR3T'. [CLIENT: 10.10.4.159]
05/26/2008 08:20:00,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 16.
05/26/2008 08:14:17,spid55,Unknown,SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
05/26/2008 08:14:17,spid55,Unknown,SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
05/26/2008 08:14:17,spid55,Unknown,SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
05/26/2008 08:14:17,spid55,Unknown,SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 9:13803264; actual 0:0). It occurred during a read of page (9:13803264) in database ID 5 at offset 0x00001a53e00000 in file 'G:\R3TDATA8\R3TDATA8.NDF'. 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<c/> see SQL Server Books Online.
05/26/2008 08:14:17,spid55,Unknown,Error: 824<c/> Severity: 24<c/> State: 2.
05/26/2008 08:14:16,spid55,Unknown,Analysis of database 'R3T' (5) is 100% complete (approximately 0 seconds remain). This is an informational message only. No user action is required.
05/26/2008 08:14:16,spid55,Unknown,Starting up database 'R3T'.
05/26/2008 08:07:13,spid55,Unknown,SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
05/26/2008 08:07:13,spid55,Unknown,SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
05/26/2008 08:07:13,spid55,Unknown,SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
05/26/2008 08:07:13,spid55,Unknown,SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 9:13803264; actual 0:0). It occurred during a read of page (9:13803264) in database ID 5 at offset 0x00001a53e00000 in file 'G:\R3TDATA8\R3TDATA8.NDF'. 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<c/> see SQL Server Books Online.
05/26/2008 08:07:13,spid55,Unknown,Error: 824<c/> Severity: 24<c/> State: 2.
05/26/2008 08:07:11,spid55,Unknown,Analysis of database 'R3T' (5) is 100% complete (approximately 0 seconds remain). This is an informational message only. No user action is required.
05/26/2008 08:07:10,spid55,Unknown,Starting up database 'R3T'.
Hi,
you have a corruption within your SQL Server 2000 database. During the attach each and every data page gets accessed and converted and during this process the corruption was detected.
You should run a full DBCC CHECKDB for the SQl Server 2000 database, to see how severe the corruption is. You should run the CHECKDB with the no_infomsgs clause to keep the log small. If you want, you can post the log here then and i will have a closer look.
Regards
Clas Hortien
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This error indicates that Windows reports that the page is successfully read from disk, but SQL Server has discovered something wrong with the page. This error is similar to error 823 except that Windows did not detect the error. This usually indicates a problem in the I/O subsystem, such as a failing disk drive, disk firmware problems, faulty device driver, and so on.
Take a look at this informative article, it will show you methods to fix the error: http://sqltechtips.blogspot.in/2015/11/troubleshooting-error-824.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
the main reason of SQL error 823 is page level corruption which occurs through hardware problem which destruct the windows api. Read more and get more possible solution :- http://www.sqlrecoverysoftware.net/blog/sql-server-page-level-corruption.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Claus,
thank you, The corruption was in one of the datafiles that we copied over the network, However, I have another issue which I am posting it seperatly.
Please help with the next post.
Regards,
KG
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.