Database has been forced to open with _allow_resetlogs_corruption and _corrupted_rollback_segments
Now we are trying to export all the data to recreate database, export fails with:
Connected to: Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
ORA-31626: job does not exist
ORA-31633: unable to create master table "SYS.SYS_EXPORT_SCHEMA_05"
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPV$FT", line 871
ORA-01115: IO error reading block from file 1 (block # 68730)
ORA-01110: data file 1: '/pelican/PELICAN/system01.dbf'
ORA-27091: unable to queue I/O
ORA-27072: File I/O error
IBM AIX RISC System/6000 Error: 110: Media surface error
Additional information: 7
Additional information: 68729
Additional information: -1

ora10g4S@(/pelican/PELICAN)$ /orahome/ora10204s/bin/dbv file=system01.dbf feedback=100
DBVERIFY: Release 10.2.0.4.0 - Production on Wed Aug 14 12:50:05 2013
Copyright (c) 1982, 2007, Oracle. All rights reserved.
DBVERIFY - Verification starting : FILE = system01.dbf
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
.....................
DBV-00102: File I/O error on FILE (system01.dbf) during verification read operation (-2)

run
{
allocate channel d1 type disk;
backup check logical validate datafile 1;
release channel d1;
}


RMAN> backup check logical validate datafile 1;
Starting backup at 14-AUG-13
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=380 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=/pelican/PELICAN/system01.dbf
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/14/2013 13:31:14
ORA-19501: read error on file "/pelican/PELICAN/system01.dbf", blockno 66817 (blocksize=8192)
ORA-27063: number of bytes read/written is incorrect
IBM AIX RISC System/6000 Error: 110: Media surface error
Additional information: -1
Additional information: 1048576

Reading a block of system datafile fails with IBM AIX RISC System/6000 Error: 110: Media surface err
Reading a block of system datafile fails with IBM AIX RISC System/6000 Error: 110: Media surface err

Action Plan:
=========
1. Shutdown the database with immediate option
2-Un-mount the FS that contain the Datafile
3-Run FSCK to fix the corrupted OS Blocks.
4-Re-mount the FS.
5. Restart the database

Mon Jan 14 00:09:42 2015 
MMNL started with pid=16, OS id=14990 
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'... 
starting up 1 shared server(s) ... 
ORACLE_BASE from environment = /u01/app/oracle 
Mon Jan 14 00:09:42 2015 
ALTER DATABASE MOUNT 
Set as converted control file due to db_unique_name mismatch 
Changing di2dbun from to orcl 
Successful mount of redo thread 1, with mount id 1434172742 
Database mounted in Exclusive Mode 
Lost write protection disabled 
Create Relation IPS_PACKAGE_UNPACK_HISTORY 
Completed: ALTER DATABASE MOUNT 
Mon Jan 14 00:10:13 2015 
alter database open 
Errors in file /u01/app/oracle/oradata/orcl/diag/rdbms/orcl/orcl/trace/orcl_ora_15080.trc: 
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open 
ORA-1589 signalled during: alter database open... 
Mon Jan 14 00:10:26 2015 
ALTER DATABASE RECOVER database using backup controlfile until cancel 
Media Recovery Start 
Serial Media Recovery started 
WARNING! Recovering data file 1 from a fuzzy file. If not the current file 
it might be an online backup taken without entering the begin backup command. 
WARNING! Recovering data file 2 from a fuzzy file. If not the current file 
it might be an online backup taken without entering the begin backup command. 
WARNING! Recovering data file 3 from a fuzzy file. If not the current file 
it might be an online backup taken without entering the begin backup command. 
WARNING! Recovering data file 4 from a fuzzy file. If not the current file 
it might be an online backup taken without entering the begin backup command. 
WARNING! Recovering data file 5 from a fuzzy file. If not the current file 
it might be an online backup taken without entering the begin backup command. 
WARNING! Recovering data file 6 from a fuzzy file. If not the current file 
it might be an online backup taken without entering the begin backup command. 
ORA-279 signalled during: ALTER DATABASE RECOVER database using backup controlfile until cancel ... 
ALTER DATABASE RECOVER CONTINUE DEFAULT 
Media Recovery Log /u01/app/oracle/flash_recovery_area/ORCL/archivelog/2015_03_14/o1_mf_1_2_%u_.arc 
Errors with log /u01/app/oracle/flash_recovery_area/ORCL/archivelog/2015_03_14/o1_mf_1_2_%u_.arc 
ORA-308 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ... 
ALTER DATABASE RECOVER CANCEL 
ORA-1547 signalled during: ALTER DATABASE RECOVER CANCEL ... 
Mon Jan 14 00:10:29 2015 
Checker run found 7 new persistent data failures 
Mon Jan 14 00:10:47 2015 
alter database open resetlogs 
RESETLOGS is being done without consistancy checks. This may result 
in a corrupted database. The database should be recreated. 
RESETLOGS after incomplete recovery UNTIL CHANGE 67619908 
Online log /u01/app/oracle/soft/orcl/REDO03.LOG: Thread 1 Group 3 was previously cleared 
Mon Jan 14 00:10:53 2015 

... 

Hex dump of (file 1, block 3273) in trace file /u01/app/oracle/oradata/orcl/diag/rdbms/orcl/orcl/trace/orcl_ora_15080.trc 
Corrupt block relative dba: 0x00400cc9 (file 1, block 3273) 
Bad header found during buffer read 
Data in bad block: 
type: 255 format: 7 rdba: 0xffffffff 
last change scn: 0xffff.ffffffff seq: 0xff flg: 0xff 
spare1: 0xff spare2: 0xff spare3: 0xffff 
consistency value in tail: 0x43830601 
check value in block header: 0xffff 
computed block checksum: 0x446e 
Reading datafile '/u01/app/oracle/soft/orcl/SYSTEM01.DBF' for corruption at rdba: 0x00400cc9 (file 1, block 3273) 
Reread (file 1, block 3273) found same corrupt data 
Mon Jan 14 00:10:54 2015 
Hex dump of (file 2, block 72411) in trace file /u01/app/oracle/oradata/orcl/diag/rdbms/orcl/orcl/trace/orcl_p000_15112.trc 
Corrupt block relative dba: 0x00811adb (file 2, block 72411) 
Bad header found during buffer read 
Data in bad block: 
type: 255 format: 7 rdba: 0xffffffff 
last change scn: 0xffff.ffffffff seq: 0xff flg: 0xff 
spare1: 0xff spare2: 0xff spare3: 0xffff 
consistency value in tail: 0x3ce30608 
check value in block header: 0xffff 
computed block checksum: 0xfe3c 
Reading datafile '/u01/app/oracle/soft/orcl/SYSAUX01.DBF' for corruption at rdba: 0x00811adb (file 2, block 72411) 
Reread (file 2, block 72411) found same corrupt data 
Errors in file 

I have reviewed the alert log and I see the database is finding serious issues.

This is a physical corruption and considering we have it also in file 1, there are probably bootstrap objects.

Do you have any backup for this database? If yes, please proceed with restore/recovery operations.

Otherwise, the information in the blocks is lost and with the errors reported and previous actions of the database, I am not sure if any option to open it.

I have no any backup on this database.

With no backup, the last resort was to force open the database, which was already attempted.

This didn’t work as we have affected a bootstrap object.

Unless the database can be recreated from other source, PRM-DUL (Data recovery UnLoaderhttp://www.parnassusdata.com/en) might be used to scan a database file, recognize table header blocks, access extent information, and read all rows.

It places the unloaded data into a flat file to be subsequently loaded back into a database.

TRY PRM-DUL  http://www.parnassusdata.com/en

PRM-DUL works on oracle ASM .

If you cannot recover data by yourself, ask Parnassusdata, the professional ORACLE database recovery team for help.

Parnassusdata Software Database Recovery Team

Service Hotline:  +86 13764045638 E-mail: service@parnassusdata.com

DUL a database scavenger tool For Oracle

Most important features

• RDBMS versions supported from as early as 6.0.34 up to the latest production software
• Standalone program written in C
• Platform independent, cross platform unloading fully supported
• Output in SQL*Loader (stream or fixed record) or export format
• DUL will not dump or crash however bad its input is
• All normal datatypes including adt's, varrays and clobs, blobs, cfiles and bfiles
• Direct reads of datafiles on asm, no asm instance needed
• Unexp and unpump commands to recover data from corrupted dump files
• Retrieve data from corrupt not mounted filesystems (scan device, create block index)
• Parts of data files as small as a single block
• Easy of configuration through datafile/disk header inspection
• Recover data from an accidentally truncated table

Restrictions

• 11g secure file lobs are not supported yet.
• Label security
• Encryption
• 11g ASM with variable extent sizes and ASM striping support is available on request in a beta
• Asm disks on exadata cells (no idea how to read those efficiently yet)
• Complex types not supported in export_mode
• The generated dump file in export_mode=true contains minimal create and insert statement to allow the table to load, metadata not included.

Professional Oracle Datenbank Wiederherstellung / Rettungsdienst

Laden Sie unsere PRM-DUL Oracle Database Recovery / Unloader Software herunter

Datenbank-Wiederherstellungsdienst

Error	Description	Corruption related to:
ORA-1578	ORA-1578 is reported when a block is thought to be corrupt on read.	Block
	OERR: ORA-1578 “ORACLE data block corrupted (file # %s, block # %s)” Master Note
	OERR: ORA-1578 “ORACLE data block corrupted (file # %s, block # %s)”
	Fractured Block explanation
	Handling Oracle Block Corruptions in Oracle7/8/8i/9i/10g/11g
	Diagnosing and Resolving 1578 reported on a Local Index of a Partitioned table
ORA-1410	This error is raised when an operation refers to a ROWID in a table for which there is no such row. The reference to a ROWID may be implicit from a WHERE CURRENT OF clause or directly from a WHERE ROWID=… clause. ORA 1410 indicates the ROWID is for a BLOCK that is not part of this table.	Row
	Understanding The ORA-1410
	Summary Of Bugs Containing ORA 1410
	OERR: ORA 1410 “invalid ROWID”
ORA-8103	The object has been deleted by another user since the operation began. If the error is reproducible, following may be the reasons:- a.) The header block has an invalid block type. b.) The data_object_id (seg/obj) stored in the block is different than the data_object_id stored in the segment header. See dba_objects.data_object_id and compare it to the decimal value stored in the block (field seg/obj).	Block
	ORA-8103 Troubleshooting, Diagnostic and Solution
	OERR: ORA-8103 “object no longer exists” / Troubleshooting, Diagnostic and Solution
ORA-8102	An ORA-08102 indicates that there is a mismatch between the key(s) stored in the index and the values stored in the table. What typically happens is the index is built and at some future time, some type of corruption occurs, either in the table or index, to cause the mismatch.	Index
	OERR ORA-8102 “index key not found, obj# %s, file %s, block %s (%s)
ORA-1499	An error occurred when validating an index or a table using the ANALYZE command. One or more entries does not point to the appropriate cross-reference.	Index
	ORA-1499. Table/Index row count mismatch
	OERR: ORA-1499 table/Index Cross Reference Failure – see trace file
ORA-1498	Generally this is a result of an ANALYZE … VALIDATE … command. This error generally manifests itself when there is inconsistency in the data/Index block. Some of the block check errors that may be found:- a.) Row locked by a non-existent transaction b.) The amount of space used is not equal to block size c.) Transaction header lock count mismatch. While support are processing the tracefile it may be worth the re-running the ANALYZE after restarting the database to help show if the corruption is consistent or if it ‘moves’. Send the tracefile to support for analysis. If the ANALYZE was against an index you should check the whole object. Eg: Find the tablename and execute: ANALYZE TABLE xxx VALIDATE STRUCTURE CASCADE;	Block
	OERR: ORA 1498 “block check failure – see trace file”
ORA-26040	Trying to access data in block that was loaded without redo generation using the NOLOGGING/UNRECOVERABLE option. This Error raises always together with ORA-1578	Block
	OERR ORA-26040 Data block was loaded using the NOLOGGING option
	ORA-1578 / ORA-26040 Corrupt blocks by NOLOGGING – Error explanation and solution
	ORA-1578 ORA-26040 in a LOB segment – Script to solve the errors
	ORA-1578 ORA-26040 in 11g for DIRECT PATH with NOARCHIVELOG even if LOGGING is enabled
	ORA-1578 ORA-26040 On Awr Table
	Errors ORA-01578, ORA-26040 On Standby Database
	Workflow Tables ORA-01578 ORACLE data block corrupted ORA-26040 Data block was loaded using the NOLOGGING option
	ORA-1578, ORA-26040 Data block was loaded using the NOLOGGING option
ORA-600[12700]	Oracle is trying to access a row using its ROWID, which has been obtained from an index. A mismatch was found between the index rowid and the data block it is pointing to. The rowid points to a non-existent row in the data block. The corruption can be in data and/or index blocks. ORA-600 [12700] can also be reported due to a consistent read (CR) problem.	Consistent Read
	Resolving an ORA-600 [12700] error in Oracle 8 and above.
	ORA-600 [12700] “Index entry Points to Missing ROWID”
ORA-600[3020]	This is called a ‘STUCK RECOVERY’. There is an inconsistency between the information stored in the redo and the information stored in a database block being recovered.	Redo
	ORA-600 [3020] “Stuck Recovery”
	Information Required for Root Cause Analysis of ORA-600 [3020] (stuck recovery)
ORA-600[4194]	A mismatch has been detected between Redo records and rollback (Undo) records. We are validating the Undo record number relating to the change being applied against the maximum undo record number recorded in the undo block. This error is reported when the validation fails.	Undo
	ORA-600 [4194] “Undo Record Number Mismatch While Adding Undo Record”
	Basic Steps to be Followed While Solving ORA-00600 [4194]/[4193] Errors Without Using Unsupported parameter
ORA-600[4193]	A mismatch has been detected between Redo records and Rollback (Undo) records. We are validating the Undo block sequence number in the undo block against the Redo block sequence number relating to the change being applied. This error is reported when this validation fails.	Undo
	ORA-600 [4193] “seq# mismatch while adding undo record”
	Basic Steps to be Followed While Solving ORA-00600 [4194]/[4193] Errors Without Using Unsupported parameter
	Ora-600 [4193] When Opening Or Shutting Down A Database
	ORA-600 [4193] When Trying To Open The Database
ORA-600[4137]	While backing out an undo record (i.e. at the time of rollback) we found a transaction id mis-match indicating either a corruption in the rollback segment or corruption in an object which the rollback segment is trying to apply undo records on. This would indicate a corrupted rollback segment.	Undo/Redo
	ORA-600 [4137] “XID in Undo and Redo Does Not Match”
ORA-600[6101]	Not enough free space was found when inserting a row into an index leaf block during the application of undo.	Index
	ORA-600 [6101] “insert into leaf block (undo)”
ORA-600[2103]	Oracle is attempting to read or update a generic entry in the control file. If the entry number is invalid, ORA-600 [2130] is logged.	Control File
	ORA-600 [2130] “Attempt to access non-existant controlfile entry”
ORA-600[4512]	Oracle is checking the status of transaction locks within a block. If the lock number is greater than the number of lock entries, ORA-600 [4512] is reported followed by a stack trace, process state and block dump. This error possibly indicates a block corruption.	Block
	ORA-600 [4512] “Lock count mismatch”
ORA-600[2662]	A data block SCN is ahead of the current SCN. The ORA-600 [2662] occurs when an SCN is compared to the dependent SCN stored in a UGA variable. If the SCN is less than the dependent SCN then we signal the ORA-600 [2662] internal error.	Block
	ORA-600 [2662] “Block SCN is ahead of Current SCN”
	ORA 600 [2662] DURING STARTUP
ORA-600[4097]	We are accessing a rollback segment header to see if a transaction has been committed. However, the xid given is in the future of the transaction table. This could be due to a rollback segment corruption issue OR you might be hitting the following known problem.	Undo
	ORA-600 [4097] “Corruption”
ORA-600[4000]	It means that Oracle has tried to find an undo segment number in the dictionary cache and failed.	Undo
	ORA-600 [4000] “trying to get dba of undo segment header block from usn”
ORA-600[6006]	Oracle is undoing an index leaf key operation. If the key is not found, ORA-00600 [6006] is logged. ORA-600[6006] is usually caused by a media corruption problem related to either a lost write to disk or a corruption on disk.	Index
	ORA-600 [6006]
ORA-600[4552]	This assertion is raised because we are trying to unlock the rows in a block, but receive an incorrect block type. The second argument is the block type received.	Block
	ORA-600 [4555]
ORA-600[6856]	Oracle is checking that the row slot we are about to free is not already on the free list. This internal error is raised when this check fails.	Row
	ORA-600 [6856] “Corrupt Block When Freeing a Row Slot
ORA-600[13011]	During a delete operation we are deleting from a view via an instead-of trigger or an Index organized table and have exceeded a 5000 pass count when we raise this exception.	Row
	ORA-600 [13011] “Problem occurred when trying to delete a row”
ORA-600[13013]	During the execution of an UPDATE statement, after several attempts (Arg [a] passcount) we are unable to get a stable set of rows that conform to the WHERE clause.	Row
	ORA-600 [13013] “Unable to get a Stable set of Records”
	How to resolve ORA-00600 [13013], [5001]
ORA-600[13030]
	ORA-600 [13030]
ORA-600[25012]	We are trying to generate the absolute file number given a tablespace number and relative file number and cannot find a matching file number or the file number is zero.	afn/rdba/tsn
	ORA-600 [25012] “Relative to Absolute File Number Conversion Error”
ORA-600[25026]	Looking up/checking a tablespace invalid tablespace ID and/or rdba found	afn/rdba/tsn
	ORA-600 [25026]
ORA-600[25027]	Invalid tsn and/or rfn found	afn/rdba/tsn
	ORA-600 [25027]
ORA-600[kcbz_check_objd_typ]	An object block buffer in memory is checked and is found to have the wrong object id. This is most likely due to corruption.	Buffer Cache
	ORA-600 [kcbz_check_objd_typ_3]
	ORA-600 [kcbz_check_objd_typ]
ORA-600[kddummy_blkchk] ORA-600[kdblkcheckerror]	ORA-600[kddummy_blkchk] is for 10.1/10.2 and ORA-600[kdblkcheckerror] for 11 onwards.	Block
	ORA-600 [kddummy_blkchk]
	How to Resolve ORA-00600[kddummy_blkchk]
	ORA-600 [kdblkcheckerror]
	QREF – kddummy_blkchk / kdBlkCheckError – Check Codes Listing (Full) [This section is not visible to customers.]
	QREF – kddummy_blkchk / kdBlkCheckError – Check Codes Definition && Return Values[This section is not visible to customers.]
ORA-600[ktadrprc-1]		Dictionary
	ORA-600 [ktadrprc-1]
ORA-600[ktsircinfo_num1]	This exception occurs when there are problems obtaining the row cache information correctly from sys.seg$. In most cases there is no information in sys.seg$.	Dictionary
	ORA-600 [ktsircinfo_num1]
ORA-600[qertbfetchbyrowid]		Row
	ORA-600 [qertbfetchbyrowid]
ORA-600[ktbdchk1-bad dscn]	This exception is raised when we are performing a sanity check on the dependent SCN and fail. The dependent scn is greater than the current scn.	Dictionary
	ORA-600 [ktbdchk1: bad dscn]

Service de récupération / sauvetage de base de données Oracle Professionnel

Télécharger notre logiciel de récupération / déchargement de bases de données Oracle PRM-DUL

Error	Description	Corruption related to:
ORA-1578	ORA-1578 is reported when a block is thought to be corrupt on read.	Block
	OERR: ORA-1578 “ORACLE data block corrupted (file # %s, block # %s)” Master Note
	OERR: ORA-1578 “ORACLE data block corrupted (file # %s, block # %s)”
	Fractured Block explanation
	Handling Oracle Block Corruptions in Oracle7/8/8i/9i/10g/11g
	Diagnosing and Resolving 1578 reported on a Local Index of a Partitioned table
ORA-1410	This error is raised when an operation refers to a ROWID in a table for which there is no such row. The reference to a ROWID may be implicit from a WHERE CURRENT OF clause or directly from a WHERE ROWID=… clause. ORA 1410 indicates the ROWID is for a BLOCK that is not part of this table.	Row
	Understanding The ORA-1410
	Summary Of Bugs Containing ORA 1410
	OERR: ORA 1410 “invalid ROWID”
ORA-8103	The object has been deleted by another user since the operation began. If the error is reproducible, following may be the reasons:- a.) The header block has an invalid block type. b.) The data_object_id (seg/obj) stored in the block is different than the data_object_id stored in the segment header. See dba_objects.data_object_id and compare it to the decimal value stored in the block (field seg/obj).	Block
	ORA-8103 Troubleshooting, Diagnostic and Solution
	OERR: ORA-8103 “object no longer exists” / Troubleshooting, Diagnostic and Solution
ORA-8102	An ORA-08102 indicates that there is a mismatch between the key(s) stored in the index and the values stored in the table. What typically happens is the index is built and at some future time, some type of corruption occurs, either in the table or index, to cause the mismatch.	Index
	OERR ORA-8102 “index key not found, obj# %s, file %s, block %s (%s)
ORA-1499	An error occurred when validating an index or a table using the ANALYZE command. One or more entries does not point to the appropriate cross-reference.	Index
	ORA-1499. Table/Index row count mismatch
	OERR: ORA-1499 table/Index Cross Reference Failure – see trace file
ORA-1498	Generally this is a result of an ANALYZE … VALIDATE … command. This error generally manifests itself when there is inconsistency in the data/Index block. Some of the block check errors that may be found:- a.) Row locked by a non-existent transaction b.) The amount of space used is not equal to block size c.) Transaction header lock count mismatch. While support are processing the tracefile it may be worth the re-running the ANALYZE after restarting the database to help show if the corruption is consistent or if it ‘moves’. Send the tracefile to support for analysis. If the ANALYZE was against an index you should check the whole object. Eg: Find the tablename and execute: ANALYZE TABLE xxx VALIDATE STRUCTURE CASCADE;	Block
	OERR: ORA 1498 “block check failure – see trace file”
ORA-26040	Trying to access data in block that was loaded without redo generation using the NOLOGGING/UNRECOVERABLE option. This Error raises always together with ORA-1578	Block
	OERR ORA-26040 Data block was loaded using the NOLOGGING option
	ORA-1578 / ORA-26040 Corrupt blocks by NOLOGGING – Error explanation and solution
	ORA-1578 ORA-26040 in a LOB segment – Script to solve the errors
	ORA-1578 ORA-26040 in 11g for DIRECT PATH with NOARCHIVELOG even if LOGGING is enabled
	ORA-1578 ORA-26040 On Awr Table
	Errors ORA-01578, ORA-26040 On Standby Database
	Workflow Tables ORA-01578 ORACLE data block corrupted ORA-26040 Data block was loaded using the NOLOGGING option
	ORA-1578, ORA-26040 Data block was loaded using the NOLOGGING option
ORA-600[12700]	Oracle is trying to access a row using its ROWID, which has been obtained from an index. A mismatch was found between the index rowid and the data block it is pointing to. The rowid points to a non-existent row in the data block. The corruption can be in data and/or index blocks. ORA-600 [12700] can also be reported due to a consistent read (CR) problem.	Consistent Read
	Resolving an ORA-600 [12700] error in Oracle 8 and above.
	ORA-600 [12700] “Index entry Points to Missing ROWID”
ORA-600[3020]	This is called a ‘STUCK RECOVERY’. There is an inconsistency between the information stored in the redo and the information stored in a database block being recovered.	Redo
	ORA-600 [3020] “Stuck Recovery”
	Information Required for Root Cause Analysis of ORA-600 [3020] (stuck recovery)
ORA-600[4194]	A mismatch has been detected between Redo records and rollback (Undo) records. We are validating the Undo record number relating to the change being applied against the maximum undo record number recorded in the undo block. This error is reported when the validation fails.	Undo
	ORA-600 [4194] “Undo Record Number Mismatch While Adding Undo Record”
	Basic Steps to be Followed While Solving ORA-00600 [4194]/[4193] Errors Without Using Unsupported parameter
ORA-600[4193]	A mismatch has been detected between Redo records and Rollback (Undo) records. We are validating the Undo block sequence number in the undo block against the Redo block sequence number relating to the change being applied. This error is reported when this validation fails.	Undo
	ORA-600 [4193] “seq# mismatch while adding undo record”
	Basic Steps to be Followed While Solving ORA-00600 [4194]/[4193] Errors Without Using Unsupported parameter
	Ora-600 [4193] When Opening Or Shutting Down A Database
	ORA-600 [4193] When Trying To Open The Database
ORA-600[4137]	While backing out an undo record (i.e. at the time of rollback) we found a transaction id mis-match indicating either a corruption in the rollback segment or corruption in an object which the rollback segment is trying to apply undo records on. This would indicate a corrupted rollback segment.	Undo/Redo
	ORA-600 [4137] “XID in Undo and Redo Does Not Match”
ORA-600[6101]	Not enough free space was found when inserting a row into an index leaf block during the application of undo.	Index
	ORA-600 [6101] “insert into leaf block (undo)”
ORA-600[2103]	Oracle is attempting to read or update a generic entry in the control file. If the entry number is invalid, ORA-600 [2130] is logged.	Control File
	ORA-600 [2130] “Attempt to access non-existant controlfile entry”
ORA-600[4512]	Oracle is checking the status of transaction locks within a block. If the lock number is greater than the number of lock entries, ORA-600 [4512] is reported followed by a stack trace, process state and block dump. This error possibly indicates a block corruption.	Block
	ORA-600 [4512] “Lock count mismatch”
ORA-600[2662]	A data block SCN is ahead of the current SCN. The ORA-600 [2662] occurs when an SCN is compared to the dependent SCN stored in a UGA variable. If the SCN is less than the dependent SCN then we signal the ORA-600 [2662] internal error.	Block
	ORA-600 [2662] “Block SCN is ahead of Current SCN”
	ORA 600 [2662] DURING STARTUP
ORA-600[4097]	We are accessing a rollback segment header to see if a transaction has been committed. However, the xid given is in the future of the transaction table. This could be due to a rollback segment corruption issue OR you might be hitting the following known problem.	Undo
	ORA-600 [4097] “Corruption”
ORA-600[4000]	It means that Oracle has tried to find an undo segment number in the dictionary cache and failed.	Undo
	ORA-600 [4000] “trying to get dba of undo segment header block from usn”
ORA-600[6006]	Oracle is undoing an index leaf key operation. If the key is not found, ORA-00600 [6006] is logged. ORA-600[6006] is usually caused by a media corruption problem related to either a lost write to disk or a corruption on disk.	Index
	ORA-600 [6006]
ORA-600[4552]	This assertion is raised because we are trying to unlock the rows in a block, but receive an incorrect block type. The second argument is the block type received.	Block
	ORA-600 [4555]
ORA-600[6856]	Oracle is checking that the row slot we are about to free is not already on the free list. This internal error is raised when this check fails.	Row
	ORA-600 [6856] “Corrupt Block When Freeing a Row Slot
ORA-600[13011]	During a delete operation we are deleting from a view via an instead-of trigger or an Index organized table and have exceeded a 5000 pass count when we raise this exception.	Row
	ORA-600 [13011] “Problem occurred when trying to delete a row”
ORA-600[13013]	During the execution of an UPDATE statement, after several attempts (Arg [a] passcount) we are unable to get a stable set of rows that conform to the WHERE clause.	Row
	ORA-600 [13013] “Unable to get a Stable set of Records”
	How to resolve ORA-00600 [13013], [5001]
ORA-600[13030]
	ORA-600 [13030]
ORA-600[25012]	We are trying to generate the absolute file number given a tablespace number and relative file number and cannot find a matching file number or the file number is zero.	afn/rdba/tsn
	ORA-600 [25012] “Relative to Absolute File Number Conversion Error”
ORA-600[25026]	Looking up/checking a tablespace invalid tablespace ID and/or rdba found	afn/rdba/tsn
	ORA-600 [25026]
ORA-600[25027]	Invalid tsn and/or rfn found	afn/rdba/tsn
	ORA-600 [25027]
ORA-600[kcbz_check_objd_typ]	An object block buffer in memory is checked and is found to have the wrong object id. This is most likely due to corruption.	Buffer Cache
	ORA-600 [kcbz_check_objd_typ_3]
	ORA-600 [kcbz_check_objd_typ]
ORA-600[kddummy_blkchk] ORA-600[kdblkcheckerror]	ORA-600[kddummy_blkchk] is for 10.1/10.2 and ORA-600[kdblkcheckerror] for 11 onwards.	Block
	ORA-600 [kddummy_blkchk]
	How to Resolve ORA-00600[kddummy_blkchk]
	ORA-600 [kdblkcheckerror]
	QREF – kddummy_blkchk / kdBlkCheckError – Check Codes Listing (Full) [This section is not visible to customers.]
	QREF – kddummy_blkchk / kdBlkCheckError – Check Codes Definition && Return Values[This section is not visible to customers.]
ORA-600[ktadrprc-1]		Dictionary
	ORA-600 [ktadrprc-1]
ORA-600[ktsircinfo_num1]	This exception occurs when there are problems obtaining the row cache information correctly from sys.seg$. In most cases there is no information in sys.seg$.	Dictionary
	ORA-600 [ktsircinfo_num1]
ORA-600[qertbfetchbyrowid]		Row
	ORA-600 [qertbfetchbyrowid]
ORA-600[ktbdchk1-bad dscn]	This exception is raised when we are performing a sanity check on the dependent SCN and fail. The dependent scn is greater than the current scn.	Dictionary
	ORA-600 [ktbdchk1: bad dscn]

Профессиональный Oracle Восстановление базы данных / спасательной службы

Скачать Наш PRM-DUL Oracle Database Recovery / UNLOADER программного обеспечения

Область службы

 

 

ParnassusData аварийная служба охватывает по всему миру, обеспечивают 7 * 24 поддержки английского языка, в том числе продукта Oracle: Oracle RDBMS и MYSQL.

 

 

 

Даже если у вас нет резервных копий, мы можем спасти базу данных после того, как в результате несчастных случаев:

 

 

 

 

DROP TABLE или DROP / CREATE, TRUNCATE TABLE; Undrop / Untruncate Таблица

DROP TABLESPACE

Неустранимая ехр / резервного копирования EXPDP или резервного копирования RMAN

Неправильный UPDATE / DELETE Undelete

не удалось смонтировать ASM дисковую группу

Поврежденный файловая система

Исключен System01.dbf

DROP USER

Решить ORA-00600 ORA-07445

Решить базы данных не может быть открыта

Восстановление данных с помощью базы данных ParnassusData Recovery Manager PRM

Исправить поврежденный блок

восстановление вручную и ремонт повреждение базы данных Oracle

Обеспечить решение Oracle исправить ошибку

 

 

Что может быть восстановлен:

 

ASM дисковая диска заголовок / метаданные повреждены, ASM дисковая не может быть установлен

Несогласованные восстановления / восстановление или любой ситуации, мешающие вашей datase от открытия, как недостающие archivelogs

несоответствие резервных копий из-за вращения неисправной ленты

искажение словаря данных или начальной загрузки объектов

потеря системы табличного: в случае отсутствия словаря данных, эвристический сканер проверяет данные, и будет пытаться определить типы данных и столбцов

осиротевшие файлы данных: такой же, как потеря системы табличного, даже если у вас есть только один файл данных слева - данные могут быть извлечены

упал табличные: если файлы данных все еще существуют, данные могут быть восстановлены

упал таблицы: заморозить приложение / базу данных и сделать копию пораженного файла данных (ы) немедленно, чтобы улучшить шансы на выздоровление

усеченные таблицы: в основном такая же, как отброшенных таблиц

упали столбцы

 

 

Короче говоря, если данные по-прежнему на носителях мы можем получить его обратно.

 

 

 

Непосредственные действия для предоставления услуг Oracle / MySQL восстановления данных

 

Время дорого, когда дело доходит до восстановления данных. В любой момент Oracle / MySQL или операционная система может переписать данные.

 

В зависимости от сценария отказа первые шаги, которые вы должны сделать

 

 

 

 

 

 

Oracle / MySQL Data Recovery Service Гарантия

 

 

 

Несмотря на то, как правило, мы достигаем довольно высокую скорость восстановления мы не можем гарантировать успешное восстановление в договоре. Тем не менее, мы сделаем все возможное, чтобы получить данные обратно.

 

 

 

 

 

Готов к заказу Oracle / MySQL Data Recovery Service?

 

Так что не откладывайте, чат или позвоните нам. Мы онлайн 24 × 7 и готовы помочь.

 

 

 

 

 

 

 

 

 

 

Процесс поддержки чрезвычайным ситуациям

 

 

 

 

Если вы по контракту клиента, пожалуйста, смотри деталь аварийной поддержки предприятия горячая линия +86 13764045638 и нажмите 2 для непосредственного обслуживания. ParnassusData подписывает эксперт по своему техническому делу. Если вы потенциальный клиент, который имел контракт с, пожалуйста DAIL +86 13764045638 и нажмите 1 для конкретного случая поддержки. Технический ресурс имеет 7 * 24 высокой доступности. Дежурный инженер ParnassusData докажет немедленно обслуживать по телефону и удаленного доступа для вашего решения проблем. После того, как вопрос или проблема не может быть решена с помощью пульта дистанционного управления, ParnassusData подписывает инженер на месте немедленно центра обработки данных.

 

 

 

 

Услуги Восстановление базы данных

 

 

ParnassusData восстановления службы в том числе: БД не может быть открыта, система табличного / файл данных утерян, файл данных удалены по ошибке, файловую систему коррумпированной, ASM дисковая размонтированием / поврежден, и т.п ..

 

 

 

PD полна опыта в hanling об ошибке и проблемы. Кроме того, PD имеет в доме инструмент для восстановления данных, которая не может Gurantee никаких данных потерянных.

 

 

 

 

Проблема Fix

После Это происходит Unknow DB блок / блокировку или проблему отбоя наши специалисты хорошо ниже проблемы.

 

 

 

Oracle Block / Блокировка Информация об ошибке:

ORA-1578 Примечание: 28814,1

ORA-1578 ORA-26040. Лоб Примечание 293515,1

ORA-8103 Примечание: 268302,1

ORA-1499 Несовпадение между таблицами / индекс (анализ VALIDATE каскадной структуры):

Таблица / индекс строки Несоответствие числа

Строка не найдено в индексе

ORA-1498 (анализировать структуру Validate)

ORA-600 [kcbzpb_1] / ORA-600 [kcbzpbuf_1]

ORA-600 [12700] Несовпадение между таблицей и индексирование

ORA-600 [kdsgrp1] Новое в 10g похож на ORA-600 [12700]

"Коррумпированные блок относительное DBA: ..."сообщение

 

ORA-1578

ORA-8103

ORA-1410

ORA-1499

ORA-1578

ORA-15042

ORA-15032

ORA-15040

ORA-15066

ORA-15038

ORA-15196 kfc.c endian_kfbh

ORA-81 ##

ORA-14 ##

ORA-26040

Ошибки ORA-600

Блок Коррупция

Индекс коррупции

Ряд коррупции

UNDO Коррупция

Контроль файлов

Последовательное чтение

Словарь

Файл / RDBA / BL

Error	Description	Corruption related to:
ORA-1578	ORA-1578 is reported when a block is thought to be corrupt on read.	Block
	OERR: ORA-1578 “ORACLE data block corrupted (file # %s, block # %s)” Master Note
	OERR: ORA-1578 “ORACLE data block corrupted (file # %s, block # %s)”
	Fractured Block explanation
	Handling Oracle Block Corruptions in Oracle7/8/8i/9i/10g/11g
	Diagnosing and Resolving 1578 reported on a Local Index of a Partitioned table
ORA-1410	This error is raised when an operation refers to a ROWID in a table for which there is no such row. The reference to a ROWID may be implicit from a WHERE CURRENT OF clause or directly from a WHERE ROWID=… clause. ORA 1410 indicates the ROWID is for a BLOCK that is not part of this table.	Row
	Understanding The ORA-1410
	Summary Of Bugs Containing ORA 1410
	OERR: ORA 1410 “invalid ROWID”
ORA-8103	The object has been deleted by another user since the operation began. If the error is reproducible, following may be the reasons:- a.) The header block has an invalid block type. b.) The data_object_id (seg/obj) stored in the block is different than the data_object_id stored in the segment header. See dba_objects.data_object_id and compare it to the decimal value stored in the block (field seg/obj).	Block
	ORA-8103 Troubleshooting, Diagnostic and Solution
	OERR: ORA-8103 “object no longer exists” / Troubleshooting, Diagnostic and Solution
ORA-8102	An ORA-08102 indicates that there is a mismatch between the key(s) stored in the index and the values stored in the table. What typically happens is the index is built and at some future time, some type of corruption occurs, either in the table or index, to cause the mismatch.	Index
	OERR ORA-8102 “index key not found, obj# %s, file %s, block %s (%s)
ORA-1499	An error occurred when validating an index or a table using the ANALYZE command. One or more entries does not point to the appropriate cross-reference.	Index
	ORA-1499. Table/Index row count mismatch
	OERR: ORA-1499 table/Index Cross Reference Failure – see trace file
ORA-1498	Generally this is a result of an ANALYZE … VALIDATE … command. This error generally manifests itself when there is inconsistency in the data/Index block. Some of the block check errors that may be found:- a.) Row locked by a non-existent transaction b.) The amount of space used is not equal to block size c.) Transaction header lock count mismatch. While support are processing the tracefile it may be worth the re-running the ANALYZE after restarting the database to help show if the corruption is consistent or if it ‘moves’. Send the tracefile to support for analysis. If the ANALYZE was against an index you should check the whole object. Eg: Find the tablename and execute: ANALYZE TABLE xxx VALIDATE STRUCTURE CASCADE;	Block
	OERR: ORA 1498 “block check failure – see trace file”
ORA-26040	Trying to access data in block that was loaded without redo generation using the NOLOGGING/UNRECOVERABLE option. This Error raises always together with ORA-1578	Block
	OERR ORA-26040 Data block was loaded using the NOLOGGING option
	ORA-1578 / ORA-26040 Corrupt blocks by NOLOGGING – Error explanation and solution
	ORA-1578 ORA-26040 in a LOB segment – Script to solve the errors
	ORA-1578 ORA-26040 in 11g for DIRECT PATH with NOARCHIVELOG even if LOGGING is enabled
	ORA-1578 ORA-26040 On Awr Table
	Errors ORA-01578, ORA-26040 On Standby Database
	Workflow Tables ORA-01578 ORACLE data block corrupted ORA-26040 Data block was loaded using the NOLOGGING option
	ORA-1578, ORA-26040 Data block was loaded using the NOLOGGING option
ORA-600[12700]	Oracle is trying to access a row using its ROWID, which has been obtained from an index. A mismatch was found between the index rowid and the data block it is pointing to. The rowid points to a non-existent row in the data block. The corruption can be in data and/or index blocks. ORA-600 [12700] can also be reported due to a consistent read (CR) problem.	Consistent Read
	Resolving an ORA-600 [12700] error in Oracle 8 and above.
	ORA-600 [12700] “Index entry Points to Missing ROWID”
ORA-600[3020]	This is called a ‘STUCK RECOVERY’. There is an inconsistency between the information stored in the redo and the information stored in a database block being recovered.	Redo
	ORA-600 [3020] “Stuck Recovery”
	Information Required for Root Cause Analysis of ORA-600 [3020] (stuck recovery)
ORA-600[4194]	A mismatch has been detected between Redo records and rollback (Undo) records. We are validating the Undo record number relating to the change being applied against the maximum undo record number recorded in the undo block. This error is reported when the validation fails.	Undo
	ORA-600 [4194] “Undo Record Number Mismatch While Adding Undo Record”
	Basic Steps to be Followed While Solving ORA-00600 [4194]/[4193] Errors Without Using Unsupported parameter
ORA-600[4193]	A mismatch has been detected between Redo records and Rollback (Undo) records. We are validating the Undo block sequence number in the undo block against the Redo block sequence number relating to the change being applied. This error is reported when this validation fails.	Undo
	ORA-600 [4193] “seq# mismatch while adding undo record”
	Basic Steps to be Followed While Solving ORA-00600 [4194]/[4193] Errors Without Using Unsupported parameter
	Ora-600 [4193] When Opening Or Shutting Down A Database
	ORA-600 [4193] When Trying To Open The Database
ORA-600[4137]	While backing out an undo record (i.e. at the time of rollback) we found a transaction id mis-match indicating either a corruption in the rollback segment or corruption in an object which the rollback segment is trying to apply undo records on. This would indicate a corrupted rollback segment.	Undo/Redo
	ORA-600 [4137] “XID in Undo and Redo Does Not Match”
ORA-600[6101]	Not enough free space was found when inserting a row into an index leaf block during the application of undo.	Index
	ORA-600 [6101] “insert into leaf block (undo)”
ORA-600[2103]	Oracle is attempting to read or update a generic entry in the control file. If the entry number is invalid, ORA-600 [2130] is logged.	Control File
	ORA-600 [2130] “Attempt to access non-existant controlfile entry”
ORA-600[4512]	Oracle is checking the status of transaction locks within a block. If the lock number is greater than the number of lock entries, ORA-600 [4512] is reported followed by a stack trace, process state and block dump. This error possibly indicates a block corruption.	Block
	ORA-600 [4512] “Lock count mismatch”
ORA-600[2662]	A data block SCN is ahead of the current SCN. The ORA-600 [2662] occurs when an SCN is compared to the dependent SCN stored in a UGA variable. If the SCN is less than the dependent SCN then we signal the ORA-600 [2662] internal error.	Block
	ORA-600 [2662] “Block SCN is ahead of Current SCN”
	ORA 600 [2662] DURING STARTUP
ORA-600[4097]	We are accessing a rollback segment header to see if a transaction has been committed. However, the xid given is in the future of the transaction table. This could be due to a rollback segment corruption issue OR you might be hitting the following known problem.	Undo
	ORA-600 [4097] “Corruption”
ORA-600[4000]	It means that Oracle has tried to find an undo segment number in the dictionary cache and failed.	Undo
	ORA-600 [4000] “trying to get dba of undo segment header block from usn”
ORA-600[6006]	Oracle is undoing an index leaf key operation. If the key is not found, ORA-00600 [6006] is logged. ORA-600[6006] is usually caused by a media corruption problem related to either a lost write to disk or a corruption on disk.	Index
	ORA-600 [6006]
ORA-600[4552]	This assertion is raised because we are trying to unlock the rows in a block, but receive an incorrect block type. The second argument is the block type received.	Block
	ORA-600 [4555]
ORA-600[6856]	Oracle is checking that the row slot we are about to free is not already on the free list. This internal error is raised when this check fails.	Row
	ORA-600 [6856] “Corrupt Block When Freeing a Row Slot
ORA-600[13011]	During a delete operation we are deleting from a view via an instead-of trigger or an Index organized table and have exceeded a 5000 pass count when we raise this exception.	Row
	ORA-600 [13011] “Problem occurred when trying to delete a row”
ORA-600[13013]	During the execution of an UPDATE statement, after several attempts (Arg [a] passcount) we are unable to get a stable set of rows that conform to the WHERE clause.	Row
	ORA-600 [13013] “Unable to get a Stable set of Records”
	How to resolve ORA-00600 [13013], [5001]
ORA-600[13030]
	ORA-600 [13030]
ORA-600[25012]	We are trying to generate the absolute file number given a tablespace number and relative file number and cannot find a matching file number or the file number is zero.	afn/rdba/tsn
	ORA-600 [25012] “Relative to Absolute File Number Conversion Error”
ORA-600[25026]	Looking up/checking a tablespace invalid tablespace ID and/or rdba found	afn/rdba/tsn
	ORA-600 [25026]
ORA-600[25027]	Invalid tsn and/or rfn found	afn/rdba/tsn
	ORA-600 [25027]
ORA-600[kcbz_check_objd_typ]	An object block buffer in memory is checked and is found to have the wrong object id. This is most likely due to corruption.	Buffer Cache
	ORA-600 [kcbz_check_objd_typ_3]
	ORA-600 [kcbz_check_objd_typ]
ORA-600[kddummy_blkchk] ORA-600[kdblkcheckerror]	ORA-600[kddummy_blkchk] is for 10.1/10.2 and ORA-600[kdblkcheckerror] for 11 onwards.	Block
	ORA-600 [kddummy_blkchk]
	How to Resolve ORA-00600[kddummy_blkchk]
	ORA-600 [kdblkcheckerror]
	QREF – kddummy_blkchk / kdBlkCheckError – Check Codes Listing (Full) [This section is not visible to customers.]
	QREF – kddummy_blkchk / kdBlkCheckError – Check Codes Definition && Return Values[This section is not visible to customers.]
ORA-600[ktadrprc-1]		Dictionary
	ORA-600 [ktadrprc-1]
ORA-600[ktsircinfo_num1]	This exception occurs when there are problems obtaining the row cache information correctly from sys.seg$. In most cases there is no information in sys.seg$.	Dictionary
	ORA-600 [ktsircinfo_num1]
ORA-600[qertbfetchbyrowid]		Row
	ORA-600 [qertbfetchbyrowid]
ORA-600[ktbdchk1-bad dscn]	This exception is raised when we are performing a sanity check on the dependent SCN and fail. The dependent scn is greater than the current scn.	Dictionary
	ORA-600 [ktbdchk1: bad dscn]

PRM-DUL Oracle Database Recovery Tool (PRM-DUL) is one advanced tool developed for Oracle data recovery.

From release 1.0 to now, more functions and enhancements have been built into the new version. And continuous bug fixes and logical improvements support it to be now more stable in various enterprise environment.

Ø  Many cases have proved that PRM-DUL Oracle Database Recovery Tool can work well on multiple OS platforms (AIX/HPUX/SOLARIS/Linux/Windows). The current version now support Oracle 9i/10g/11g/12c Oracle Databases Data Rescue Operations.

Ø  It is a Java based, free installation software. You can start it directly after download and unzip the package. (On Windows, click the executable file prm.bat. On Linux/Unix, the start file is prm.sh)
** We advise users to use Java 1.6 or higher version before trying PRM-DUL 4.0.
Java official version can support most of PRM-DUL functions except raw device operations. If you are using this tool for raw device data recovery, please install Java OpenJDK instead.

Ø  PRM-DUL GUI interface can help user for easy use. It is not necessary for users to learn extra sets of commands or try to understand Oracle data file layout structures. Through PRM-DUL Recovery Wizard, we can easily rescue the database data and “save my life” J.

Ø  PRM-DUL supports single data file scan and data extraction, it also supports Oracle ASM storage data recovery.

Ø  The rescued data can be exported in sql loader data file format. And also we can use PRM-DUL Data Bridge function to export data and insert into one another new database directly, that means data can be rescued and recovered without staging. 

-------------------------

Version 4.0 Enhancements：

1. Support data recovery for table DELETE wrong operations.

2. Great improvements on exporting performance for LOB data bridge in dictionary mode.

3. Add support for LOB data bridge in non-dictionary mode.

4. Add support for re-use dictionary mode/non-dictionary mode scanning data info.

5. Add DDL export support at schema level

-------------------------

PRM-DUL Oracle Database Recovery Tool – Major functions：

·         Can do data scanning and analyzing on database files, no matter Oracle Database is running or not.

·         Support ASM, PRM-DUL can read ASM storage disks directly, find the data files and then do the data scanning and analyzing.

·         Support raw devices data files reading.

·         Support LOB (CLOB, NCLOB and BLOB) column data recovery, it also supports the case when different LOB columns have different chunk size in one same table.

·         Support Oracle database recovery on multiple Big Endian or Little Endian operating systems (AIX/HPUX/SOLARIS/Linux/Windows).

·         Support partition, sub-partition data recovery

·         Support various table data recovery, which also includes HEAP tables and CLUSTER tables.

·         Support truncated table data recovery.

·         Support dropped table data recovery.

·         Support Non-dictionary mode data recovery when SYSTEM table space is missing or data dictionary is broken. Provide part of block data to assist user to determine the data type for recovery.

·         Support BigFile table space data recovery.

·         Support data files with different block sizes in one same database.

·         Support CREATE table SQL file and sqlldr control file auto-generating when rescued data is exported into flat file.

-------------------------

In the growing enterprise IT systems, data capacity is expanding in geometric progression. Even if DBAs are aware of the importance of backup, they will still suffer from problems such as lack of backup storage space, backup failures or unavailable, physical storage disaster damage, and so on. Therefore, it’s necessary for DBAs to familiar with a physical data recovery tool and understand how to use it.
If your Oracle database downs due to an unexpected failure, the physical storage is damaged and cannot be restarted, and you are stuck in the backup is too old to be used. Then you can consider trying PRM-DUL for emergency rescue processing.

-------------------------
There are many types of errors to show Oracle Database’s disaster damage or block corruption:
Such as block corruption/bad block, index corruption/ bad block, row corruption/ bad block, UNDO corruption/bad block, control file corruption, consistent read problem, data dictionary corruption, data file/RDBA/BL problem etc. If you meet ORA-1578 / ORA-8103 / ORA-1410 / ORA-1499 / ORA-1578 / ORA-81## / ORA-14## / ORA-26040 / ORA-600 …errors but failure to recover it, we advise you to try PRM-DUL as one of your data rescue means.

-------------------------

PRM-DUL Oracle database recovery tool has two editions (for Community and Enterprise):

·         Community Edition - Oracle database users can free download the latest version at any time from www.parnassusdata.com. Without the purchase of License, the software is free for use as a community version, the community version allows each table up to 10,000 lines of data rescue export, so users can use the software for free on some small databases.

·         Enterprise Edition - If the table row number required to be recovered is more than 10,000 and you’ve tried PRM-DUL and confirm it can fix your problem. Then you can visit the official website and consider to purchase the Enterprise License for this tool. After the registration for the software by using the license you’ve got. Your software can be upgraded from the community edition to the enterprise one. The enterprise edition has no line number limit, and all other functions and enhancements will be open to you.

-------------------------

If you have more questions about using this tool or you need more help on it, don’t hesitate to visit the official website at http://www.parnassusdata.com/. Call the hotline or email our software service for additional help.

I have a client that had a problem with an Oracle Database.

I try your product and recovered the 10000 records that the trial could recover, I’d already bought other products that I try and after bought they recover only 20%  records of the tables.

I have tables with more than 500000 records and the other products only recover 100000 I need to know if I can have more guaranties that I can recover more.

Can I send the data base to you and you send me one or two tables with all or almost all the records?

feedback :

yes, please send , and we will fix your problem