Call us: +86 13764045638   service@parnassusdata.com   7 x 24 online support!

    You are here

    • You are here:
    • Home > Oracle Database 24/7 EMERGENCY RESPONSE Hotline:+86 13764045638

Oracle Database 24/7 EMERGENCY RESPONSE Hotline:+86 13764045638

Professional Oracle Database Recovery/Rescue  Service

 

Download Our PRM-DUL An Oracle Database Recovery/Unloader Software

 

 

7*24  Oracle Database Support Call  :   +86 13764045638  

7*24  Oracle Database Support Email :  service@parnassusdata.com

 

If it happens database corruption or data lost, please run below script, and send us the result: service@parnassusdata.com. Then contact us via hotline

Download Diagnosis Script

 

 


Service Scope

 

ParnassusData emergency service covers globally ,provide 7*24 English  support,including Oracle product:ORACLE RDBMS and MYSQL。

 

Even if you don’t have backups we can salvage database after following accidents:

 

 

  1. DROP TABLE or DROP/CREATE, TRUNCATE TABLE;  Undrop/Untruncate Table
  2. DROP TABLESPACE
  3. Unrecoverable exp/expdp backup or RMAN backup
  4. Wrong UPDATE/DELETE    Undelete
  5. failed to mount ASM diskgroup
  6. Corrupted file system
  7. Deleted System01.dbf
  8. DROP USER
  9. Solve ORA-00600 ORA-07445  
  10. Solve database can not be open
  11. Recover database data via ParnassusData Recovery Manager PRM
  12. Fix corrupted block
  13. Manually recovery and repair oracle database corruption
  14. Provide Oracle bug fix solution

 

What can be recovered :
 
  1. ASM diskgroup disk header/metadata corrupted, ASM diskgroup can't be mounted
  2. Inconsistent restores/recoveries or any situation preventing your datase from opening, like   missing archivelogs  
  3. mismatch of backups due to faulty tape rotation  
  4. corruption of data dictionary or bootstrap objects  
  5. the loss of system tablespace : in case of a missing data dictionary, a heuristic scanner will examine the data and will try to determine datatypes and columns  
  6. orphaned datafiles : same as the loss of the system tablespace, even if you only have one datafile left - data can be extracted  
  7. dropped tablespaces : if the datafiles still exist, data can be recovered  
  8. dropped tables : freeze the application/database and make a copy of the affected datafile(s) immediately to improve chances of recovery  
  9. truncated tables : is basically the same as dropped tables  
  10. dropped columns 

 

In short, if the data is still on media we can get it back.

 

Immediate Actions for Oracle/MySQL Data Recovery Service

Time is precious when it comes to data recovery. Any moment Oracle/MySQL or operating system can overwrite your data.

Depending on failure scenario the first steps you should do

 

 

 

Oracle/MySQL Data Recovery Service Warranty

 

Although usually we achieve pretty high recovery rate we cannot guarantee successful recovery in a contract. However we will do our best to get your data back.

 

 

Ready to order Oracle/MySQL Data Recovery Service?
 
So don’t delay, chat us or call us. We’re online 24×7 and ready to help.
 
 
 
 
 
 
 

Emergency Support Process

 

If you are contracted client, please see detail the enterprise emergency support hot line +86 13764045638 and press 2 for direct service. ParnassusData will sign an expert on your technical case. If you are potential client who did have a contract with, please dail +86 13764045638 and press 1 for case by case support. Technical resource has 7*24 high availability. The on duty engineer of ParnassusData will prove immediately service by telephone and remote access for your problem solving. Once the issue or problem can not be fixed by remote, ParnassusData will sign the onsite engineer immediately to your data center.

 


Database Recovery Service

 

ParnassusData recovery service including: DB can not be open, system tablespace/datafile lost , datafile deleted by mistake , filesystem corrupted , ASM Diskgroup unmountable/corrupted ,etc..

 

PD is full of experience in hanling about error and problem. In addition, PD has the in house tool for data recovery which can gurantee no data lost.

 


Problem Fix

Once It happens unknow DB block/lock, or HANG UP problem, our experts are good at below problem.

 

Oracle Block/Lock error info:

ORA-1578 Note:28814.1 
ORA-1578 ORA-26040. Lob Note 293515.1
ORA-8103   Note:268302.1
ORA-1499 Mismatch between table/index (analyze validate structure cascade):
Table/Index row count mismatch 
row not found in index
ORA-1498 (analyze validate structure)
ORA-600 [kcbzpb_1] / ORA-600 [kcbzpbuf_1]
ORA-600  [12700] Mismatch between Table and Index
ORA-600 [kdsgrp1] New in 10g similar to ORA-600 [12700]
“Corrupt block relative dba: …”  message 
 
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 Errors
Block Corruption
Index Corruption
Row Corruption
UNDO Corruption
Control File
Consistent Read
Dictionary
File/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_blkchkORA-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]  

 

 

 


Error  Comments
ORA-1578 Corrupt Data
ORA-1172 or ORA-3020 Missing block changes, Redo corruption
ORA-600 kddummy_blkchk or kcoapl_blkchk Block corruption during redo application
ORA-600 kccdebug_check_* Controlfile corruption
For ORA-8103 or ORA-1410 Object no. or type mismatch
kcbzib_data or kcbzib_sgh
ORA-600 related to kcbgtcr, kcbgcur, kcbnew Cache Buffer header inconsistencies
ORA-600 kcbzib_seq or kcbbvr_verify_writes  Lost Write Verification using SCN 
Immediate read after write mismatched
ORA-600 kcbzib_dobj Object number mismatch from upper layers
kcbzpbuf_1 and kcbzpb_1 Corrupt block when writing
ORA-600 [25012] Potentially corrupt rdba/tsn
ORA-600’s [4136/4137/4193/4194/4000]

Undo Corruptions

 

TEL/電話+86 13764045638
QQ 47079569