Sybase ASE數(shù)據(jù)庫恢復(fù)工具READSYBDEVICE
Sybase ASE數(shù)據(jù)庫恢復(fù)工具READSYBDEVICE:
一個不依賴數(shù)據(jù)庫管理系統(tǒng)、直接從Sybase數(shù)據(jù)庫設(shè)備文件上提取數(shù)據(jù)的業(yè)內(nèi)領(lǐng)先的恢復(fù)工具!
能夠從損壞的Sybase ASE設(shè)備文件(.dat)上提取數(shù)據(jù)的非常規(guī)恢復(fù)工具。
Sybase ASE數(shù)據(jù)庫恢復(fù)工具READSYBDEVICE的主要功能:
1.被勒索病毒加密數(shù)據(jù)文件及備份文件情況下的恢復(fù);
2.系統(tǒng)崩潰只剩下數(shù)據(jù)文件的情況下的恢復(fù),甚至數(shù)據(jù)庫文件不存在而只有損壞的備份文件情況下的恢復(fù);
3.因斷電、硬盤壞道等造成數(shù)據(jù)庫文件損壞情況下的恢復(fù);
4.delete數(shù)據(jù)恢復(fù)、誤update數(shù)據(jù)恢復(fù)、誤刪除表(drop)恢復(fù)、誤truncate表恢復(fù) 等;
5.各種Sybase內(nèi)部系統(tǒng)表損壞、索引錯誤的修復(fù);
6.master數(shù)據(jù)庫損壞而無法正常運行情況下的恢復(fù);
7.Sybase數(shù)據(jù)庫被標(biāo)記為可疑,不可用等情況的恢復(fù);
8.Sybase數(shù)據(jù)庫中數(shù)據(jù)文件內(nèi)部出現(xiàn)壞塊情況下的恢復(fù);
9.Sybase數(shù)據(jù)庫無數(shù)據(jù)文件但有日志文件的情況下的恢復(fù);
10.Sybase數(shù)據(jù)庫只有數(shù)據(jù)文件無任何日志文件的情況下的恢復(fù);
11.Sybase數(shù)據(jù)文件被誤刪除情況下的碎片提取恢復(fù);
12.磁盤陣列上的Sybase數(shù)據(jù)庫被誤格式化情況下的數(shù)據(jù)庫恢復(fù);
13.數(shù)據(jù)庫sysobjects等系統(tǒng)表損壞無法正常應(yīng)用情況下的恢復(fù);
14.Sybase數(shù)據(jù)庫還原數(shù)據(jù)庫出現(xiàn)失敗情況下的恢復(fù);
15.Sybase數(shù)據(jù)庫只剩下?lián)p壞的備份文件情況下的恢復(fù)。
Sybase ASE數(shù)據(jù)庫恢復(fù)工具READSYBDEVICE支持的版本:
Sybase ASE 10.0.x,11.0.x,11.5.x,11.9.x,12.0.x,12.5.x,15.0.x,15.5.x,15.7.x,16.0.x,16.1.x
Sybase Adaptive Server Enterprise (ASE) 常見故障錯誤號:
如果遇到以下Sybase ASE故障,可以聯(lián)系我們公司資深數(shù)據(jù)庫技術(shù)工程師協(xié)助您解決。
1、Error: 605, Severity: 21, State: 1
An attempt was made to fetch logical page '1105048' from cache 'default data cache'. Page belongs to database 'test' (5), object '<Unknown>' (0), index '<Unknown>' (0), partition '<Unknown>' (1894859881) and not to database 'test' (5), object 'PRD0408_VBFA' (485573737), index 'PRD0408_VBFA' (0), partition 'PRD0408_VBFA_485573737' (485573737).
2、Error: 624, Severity: 21, State: 1
Adaptive Server failed to retrieve a row via its RID in database 'test' because the requested RID has a higher number than the last RID on the page. Rid pageid = 0x192d23; row num = 0x49. Page pointer = 0x000000010B3E0000, pageno = 1649955, status = 0x1, ptnid = 8, indexid = 0, level = 0.
3、Error: 625, Severity: 21, State: 1
Adaptive Server failed to retrieve a row via its RID in database 'test' because the entry in the offset table for that RID is less than or equal to 0. Rid pageid = 0x359; row num = 0xe. Page pointer = 0x0x14b4a8000, pageno = 857, status = 0x101, ptnid = 576002052, indexid = 0, level = 0.
4、Error: 631, Severity: 21, State: 2
The length of 20 passed to delete row routine for the row at offset 452 is incorrect on the following page: Page pointer = 0x22496000, pageno = 126506, status = 0x11, objectid = 1600008731, indexid = 0, level = 0. The expected row length is 12852. The offset should be no greater than 472.
5、Error: 644, Severity: 21, State: 5
Index row entry for data row id (186, 0) is missing from index page 201 of index id 2 of table 'systabstats' in database 'test'. Xactid is (1650128,76). Drop and re-create the index.
6、Error: 691, Severity: 20, State: 1
Encountered invalid logical page '184' while accessing database 'test' (5), object 'systabstats' (23), index 'systabstats' (0), partition 'systabstats_23' (23). This is an internal system error. Please contact Sybase Technical Support.
7、Error: 692, Severity: 20, State: 1
Uninitialized logical page '184' was read while accessing database 'test' (5), object 'systabstats' (23), index 'systabstats' (0), partition 'systabstats_23' (23). Please contact Sybase Technical Support.
8、Error: 695, Severity: 21, State: 1
An attempt was made to read logical page '1650052' for database 'test' (5), object 'syslogs' (8), index 'syslogs' (0), partition 'syslogs_8' (8) from disk. Wrong logical page '0' was brought into cache 'default data cache'.
9、Error: 697, Severity: 21, State: 1
An attempt was made to fetch logical page '94675' for database 'test' (5), object 'PRD0408_VBFA' (485573737), index 'PRD0408_VBFA' (0), partition 'PRD0408_VBFA_485573737' (485573737) from cache 'default data cache'. Wrong logical page '0' was found in cache.
10、Error: 806, Severity: 21, State: 1
Could not find virtual page for logical page 4278284755 in database 'test'.
11、Error: 1131, Severity: 22, State: 3
The OAM for object 415781405, index 0, oam page 448, database=5, is currently allocated to another object.
12、Error: 1142, Severity: 22, State: 1
Invalid OAM Page 176. Found pstat=0x881, object=23, database=5, indid=0.
13、Error: 2503, Severity: 16, State: 2
Table Corrupt: Page linkage is not consistent. Check the following pages: current page number = %d, partition ID = %d; page number of the page pointing to this page = %d; previous page number indicated in this page = %d.
14、Error: 2509, Severity: 16, State: 2
Table Corrupt: The row number and offset of each row in the page should have a matching entry in the row number table. Check page number 857, partition ID 576002052 (row number 14, offset in row number table is 0).
15、Error: 2510, Severity: 16, State: 2
Key mismatch between index page 34, partition ID 2; at offset 1019; and data page 18 (row ID 19), partition ID 2. Drop and re-create index ID 2 of table 'sysindexes' in database 'test'.
16、Error: 2610, Severity: 22, State: 1
Could not find leaf row in nonclustered index 'ncsysobjects' page 1256 that corresponds to data row from logical data page 7291, row offset 17 during update index attempt after data page split in dbid 14.
17、Error: 2628, Severity: 21, State: 1
In database '%.*s', page %ld is linked forward to page %ld, but that page is linked backward to page %ld. Please report this internal error to Sybase Technical Support.
18、Error: 2630, Severity: 21, State: 1
In database '%.*s', page %u is linked backward to page %u, but that page is linked forward to page %u. Please report this internal error to Sybase Technical Support.
19、Error: 3401, Severity: 21, State: 1
Rec_logbounds: getnext SCAN_RID of last checkpoint failed on Rid from sysdatabases. Rid pageid = 0x192d89; row num = 0xa.
20、Error: 3403, Severity: 22, State: 2
During recovery initialization, page 1650052 was encountered. This page belongs to object 1, not the log.
21、Error: 3474, Severity: 21, State: 1
During redo the page timestamp value is less than old timestamp from log. Page #=657, object id = 608002166, page timestamp=4000 fff54592. Log old timestamp=4000 fff5aca7. Log record marker = (6157, 4).
22、Error: 3478, Severity: 21, State: 1
During undo the page timestamp value is less than new timestamp from log. Page #=%ld, object id = %ld, page timestamp=%04x %08lx. Log new timestamp=%04x %08lx. Log record marker = (%ld, %d).
23、Error: 6902, Severity: 21, State: 1
Page timestamp value falls between the old and new timestamps from log. Page #=%ld, object id = %ld, page timestamp=%04x %08lx. Log: old timestamp=%04x %08lx, new timestamp=%04x %08lx. Log record marker = (%ld, %d).
24、Error: 6908, Severity: 21, State: 1
During redo the page timestamp value is less than old timestamp from log. Page #=%ld, object id = %ld, page timestamp=%04x %08lx. Log old timestamp=%04x %08lx.
25、Error: 12308, Severity: 21, State: 8
Internal error : Invalid row id (Row 59, Page 1105048) encountered in the table 'PRD0408_VBFA' in database 'test'.
26、Error: 12315, Severity: 21, State: 1
Corrupt page, Internal error: Mismatch between tail timestamp '%04x' and the low two bytes of timestamp in the page header '%04x' while accessing page '%ld' of object '%ld' in database '%d'. Please contact Sybase Technical Support.
27、Error: 12336, Severity: 16, State: 1
Definition time object 'database 'readsybdevice' (4), object 'testtable' (1465821303)' found at run time as an attempt to drop the table had failed in a previous query. Please drop the above mentioned table using the DROP TABLE command.
28、Error: 12546, Severity: 18, State: 1
During undo the timestamp to be assigned to a page is less than the current page timestamp. Page = %ld, object id = %ld, page timestamp = (%04x %08lx), new page timestamp = (%04x %08lx).
29、Error: 15060, Severity: 21, State: 1
The state of the sort bit on OAM page %d for object ID %d does not agree with the state recorded in the object's syspartitions row. A problem may have occurred while creating or recreating index ID %d for this object.
經(jīng)典案例:(8)
-
Sybase ASE 12.5 .kalxat勒索病毒解密 數(shù)據(jù)庫中.kalxat勒索病毒數(shù)據(jù)恢復(fù)
20250516 -
Sybase ASE 15.7因Linux ext4損壞導(dǎo)致數(shù)據(jù)庫無法訪問,從Linux ext4提取Sybase數(shù)據(jù)庫碎片恢復(fù)數(shù)據(jù)
20231229 -
Sybase ASE 12.5.4 .eking勒索病毒解密 數(shù)據(jù)庫中.eking勒索病毒解密
20220206 -
Sybase ASE 12.5.1 YB數(shù)據(jù)庫損壞恢復(fù)
20211217 -
Sybase ASE 12.5.2 .makop勒索病毒解密 數(shù)據(jù)庫中.makop勒索病毒解密
20210905 -
Sybase ASE 12.5.2 FL_HIS數(shù)據(jù)庫損壞恢復(fù)
20210607 -
小型機(jī)Sybase 12.5.2 master數(shù)據(jù)庫損壞修復(fù)
20210517 -
小型機(jī)Sybase 12.5.4 JXC數(shù)據(jù)庫損壞恢復(fù)
20210405