Fatal Error 605

Question

Fatal Error 605

clardima

Old Hand

Points: 311
More actions
June 24, 2002 at 5:53 am

#79230

Hi all,
when executing a query, after displaying a few records the QA comes up with the error:
Fatal Error 605 : Connection Broken.
Can anybody tell me what could be a problem? Or where I have to search?
Thanks.
regards,
Maarten

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Steve Jones - SSC Editor SSC Guru Points: 738693 More actions · Answer 1

Perhaps some data item is causing QA to drop the connection. Is this a specific table or all tables/servers? Is it the same amount of rows each time?

Steve Jones

steve@dkranch.net

Steve Jones - SSC Editor SSC Guru Points: 738693 More actions · Answer 2

Perhaps some data item is causing QA to drop the connection. Is this a specific table or all tables/servers? Is it the same amount of rows each time?

Steve Jones

steve@dkranch.net

Antares686 SSC Guru Points: 125444 More actions · Answer 3

I got this the other data and found a problem with the table and it extent listing. Of course the message confused me but I had recently use the table in an expirement with First IAM listing in the system table. Try using DBCC CHECKDB and DBCC UPDATEUSAGE to see if the find issues with the table. The one thing I noticed is that my connection was not disconnecting just stopping.

"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)

clardima Old Hand Points: 311 More actions · Answer 4

Thanks for your answers. I looked into the error log and the following is there:

2002-06-24 11:27:36.53 spid55 Getpage: bstat=0x9, sstat=0, cache

2002-06-24 11:27:36.53 spid55 pageno is/should be: objid is/should be:

2002-06-24 11:27:36.53 spid55 (1:37137)/(1:37137) 1113771537/1113771025

2002-06-24 11:27:36.53 spid55 ... IAM indicates that page is allocated to this object

2002-06-24 11:27:36.53 spid55 Error: 605, Severity: 21, State: 1

2002-06-24 11:27:36.53 spid55 Attempt to fetch logical page (1:37137) in database 'UkDb' belongs to object '1113771537', not to object 'TSHPMENT'..

Antares686 SSC Guru Points: 125444 More actions · Answer 5

DBCC CHECKDB to determine the extent of the damage.

Then you will need to correct the problem.

There is a chance you will lose data so hoepfully you have a pretty recent backup you can restore somewhere else to pull the missing items. There is also the chance you won't lose data, so check when done.

From SQL BOL

quote:
Additional Information
DBCC CHECKDB offers the REPAIR_REBUILD and REPAIR_ALLOW_DATA_LOSS clauses. The REPAIR_REBUILD clause rebuilds corrupt indexes and the REPAIR_ALLOW_DATA_LOSS clause fixes allocation problems. Sometimes, deleting pages is the only way to fix allocation problems. Typically, these pages contain data that was already deleted, but the pages may contain valid data. Therefore, deleting pages is a more risky option than using DBCC CHECKDB with a repair clause. Using DBCC CHECKDB with a repair clause fixes database corruption when a database backup is not available.
If your database is a data warehouse, you may be able to continue operating without the lost data for some time before reloading the missing data. In these cases, use DBCC CHECKDB with the REPAIR_ALLOW_DATA_LOSS clause to fix the damaged database.
You can prevent problems by following these guidelines:
Run SQL Server only on hardware and controllers that are certified for your operating system.
Perform regular backups in conjunction with DBCC CHECKDB statements. DBCC CHECKDB performs all checks that DBCC NEWALLOC and DBCC CHECKALLOC previously did, but DBCC CHECKDB is faster. This is the only way to be confident of the state of the database at the time of the backup.
If the data is critical, back up the transaction log frequently. This makes it possible to reduce your window of vulnerability, even in the event of a catastrophic hardware problem, to an hour or less.
In the most critical situations, use a standby server and a continually running batch job to take transaction backups off of the primary computer and continually restore them on the standby computer.
If you have persistent data corruption problems, try to swap the computer, the controllers, and the disk device drivers for components of a different type. This makes it easier to determine whether the problem is specifically platform-related.

"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)