Error 605 on SQL Server 6.5

Hello!
I have a problem with two MS SQL Servers 6.5 (Microsoft SQL Server 6.50 -
6.50.416 (Intel X86) ) running on Windows 2000 advanced server(SP4). Every
night I make full backup of the database on “main server” (using job) and
start job on another MS SQL Server 6.5(“standby server”). The job on the
another server copies the file with the full backup and restores it. Then I
run dbcc chekdb for this database on the “standby server” and the following
messages appears:
--8<--
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 519096 in database 'request' belongs to object
'TSign_Request', not to object 'TRoute'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 522672 in database 'request' belongs to object
'TRoute', not to object 'TRequest'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 516440 in database 'request' belongs to object
'TRequest', not to object 'TReport'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 517296 in database 'request' belongs to object
'TSign_Request', not to object 'TRoute'.
--8<--
This message appears periodically _not_every_time_ after restoring this
backup in another database on the main server too.
Hello,
This error message indicates database corruption. You may want to run dbcc
checkdb on the original database to make sure it is OK. If so, there might
be issues when copying database.
If original database has problem, corruption issue might be caused by
hardware. Please check the following event log to see if there is any
related events on disk etc.
Please understand SQL 6.5 is out of its lifecycle, and it is recommended
that you upgrade to later version when possible.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Error 605 on SQL Server 6.5
>thread-index: AcZaG4LgFBOxVaiEQbKF7y0q+hu4HQ==
>X-WBNR-Posting-Host: 212.12.3.11
>From: =?Utf-8?B?dmFkaW1t?= <white@.community.nospam>
>Subject: Error 605 on SQL Server 6.5
>Date: Fri, 7 Apr 2006 01:16:03 -0700
>Lines: 30
>Message-ID: <23B8D9AB-AF78-4B48-A0D9-EBCF70011879@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 8bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:427209
>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hello!
>I have a problem with two MS SQL Servers 6.5 (Microsoft SQL Server 6.50 -
>6.50.416 (Intel X86) ) running on Windows 2000 advanced server(SP4). Every
>night I make full backup of the database on “main server” (using job)
and
>start job on another MS SQL Server 6.5(“standby server”). The job on
the
>another server copies the file with the full backup and restores it. Then
I
>run dbcc chekdb for this database on the “standby server” and the
following
>messages appears:
>--8<--
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 519096 in database 'request' belongs to
object
> 'TSign_Request', not to object 'TRoute'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 522672 in database 'request' belongs to
object
> 'TRoute', not to object 'TRequest'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 516440 in database 'request' belongs to
object
> 'TRequest', not to object 'TReport'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 517296 in database 'request' belongs to
object
> 'TSign_Request', not to object 'TRoute'.
>--8<--
>This message appears periodically _not_every_time_ after restoring this
>backup in another database on the main server too.
>
>
|||Hello!
""privatenews"" wrote:

> Hello,
> This error message indicates database corruption. You may want to run dbcc
> checkdb on the original database to make sure it is OK. If so, there might
> be issues when copying database.
"Dbcc checkdb" on the original database doesn't report errors.
"Dbcc checkdb" return this error _not_every_time_ only after the backup and
restore operations to another database.

> If original database has problem, corruption issue might be caused by
> hardware. Please check the following event log to see if there is any
> related events on disk etc.
There are no any disk related messages in eventlog.

> Please understand SQL 6.5 is out of its lifecycle, and it is recommended
> that you upgrade to later version when possible.
I understand this. We have to use SQLServer 6.5 because application not
support any other RDMS.
Also, all tables mentioned in dbcc error report has text column.