Interested to Buy Any Domain ? << Click Here >> for more details...
RMAN-07517: Reason: The file header is corrupted
- 2 Answers
- 28641 Views
- I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / pawan kumar
Dear,
First of all you startup in nomount mode
1. startup nomount
After that you set DBID of Production database
2.rman target /
3.set DBID *******
make sure u have to remove controlfile if already available.
4.restore controlfile from '/backup/************/.bak';
5.alter database mount;
6.catalog start with '/backup/**********';
7.restore database;
| Is This Answer Correct ? | 2 Yes | 3 No |
Answer / guest
Cause: Either the file is not an Oracle file or the file
header is corrupted.
Action: Delete the file using OS utility.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 9 No |
ORA-12018: following error encountered during code generation for "string"."string"
ORA-29917: cannot lock a table which gets its rows from a collection operand
ORA-12225: TNS:destination host unreachable
ORA-00320: cannot read file header from log string of thread string
ORA-16152: standby database is in 'no-data-loss' protected mode
ORA-25253: listen failed, queue string.string is not enabled for dequeue
ORA-29326: SET COMPATIBILITY release number higher than string
ORA-24775: cannot prepare or commit transaction with non-zero lock value
ORA-19909: datafile string belongs to an orphan incarnation
ORA-32815: message system link string is referenced by a foreign queue
ORA-00307: requested INSTANCE_NUMBER out of range, maximum is string
TNS-12209: TNS:encountered uninitialized global
Oracle Errors 
