The transaction (process ID 57) is deadlocked with another process on the lock resource and has been selected as the deadlock victim. Please rerun the transaction.
This error is common in UFIDA Changjietong T+ series software. The main cause: 99% of database damage comes from forced power outage, blue screen, crash, power outage, unplugging and plugging the power source, etc., which cause the computer to shut down abnormally.
The disk is running at high speed. Forcibly cutting off the power will cause scratches on the head and the disk, which will result in damage to the file at the sector location!
The select * from sysindexes table is damaged.
Customers using dbcc checkdb('UFTData413173_000001',repair_allow_data_loss) cannot recover the database effectively.
Database error
Repair the database DBCC Checkdb, report "message 211, level 23, status 51, line 1
An architectural damage may have occurred. Please run DBCC CHECKCATALOG.
Fault picture tempdb space is used up or a certain system table is inconsistent
Description of data recovery failure:
A factory in Guangxi used UFIDA T+ software. After a sudden power failure, UFIDA’s T+ database questioned it. After being repaired by a local data recovery company, it still reported an error when used in T+. After searching for "Shenma Software System Center" on Baidu, it was finally determined that we would do it. Repair this extremely important database! The database needs to be called normally!
Data recovery process:
The engineer used the self-researched and successfully researched database lightning repair technology. Winhex successfully repaired the database by hand, and passed the remote verification by the after-sales engineer of UFIDA!
Focus on solving the following problems: The database repair experts around you:
1. The structure may be damaged. Please run DBCC CHECKCATALOG. "Error
2. A failure was detected when collecting fact data. It may be because tempdb space is used up or a certain system table is inconsistent. Please check the previous error message.
3. Server: Message 8966, Level 16, State 1, Line 1 failed Read and latch the page (1:4380) (using the latch type SH). sysobjects failed. DBCC execution is complete. If DBCC outputs an error message, please contact the system administrator.
4. Attach the database 823 824 error
5. SQL Server Consistency-based logical I/O
detected SQL Server has detected a consistency-based logical I/O error. The pageid is incorrect (should be 1:27363, but actually 0:0). In the file'E:\Database\YF_data .mdf', offset 0x0000000d5c6000, the page (1:27363) in database ID 5, the error occurred during the read. SQL Server error log or other messages in the system event log may provide more information Details. This is a serious error condition that threatens the integrity of the database and must be corrected immediately. Please perform a complete database consistency check (DBCC CHECKDB). This error can be caused by many factors; for details, see SQL Server Books Online .
Free detection of database files [email protected]
————————————————
Copyright statement: This article is the original article of the CSDN blogger "q_q275835897", following the CC 4.0 BY-SA copyright agreement, reprinted Please attach a link to the original source and this statement.
Original link: https://blog.csdn.net/cmddate/article/details/114131475