RMAN-07517: Reason: The file header is corrupted
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 | 2 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 | 8 No |
PCB-00636: This attribute is only valid for External LOB types
ORA-14280: all rows in table do not qualify for specified subpartition
ORA-16505: site ID is invalid
RMAN-08580: channel string: starting datafile copy
ORA-02853: Invalid server list latch time out value
ORA-06564: object string does not exist
NNL-00403: Number of answers: number
ORA-13757: "SQL Tuning Set" "string" is active.
ORA-32640: FOR LIKE loops are not allowed for multi-byte character types
ORA-01586: database must be mounted EXCLUSIVE and not open for this operation
ORA-25204: invalid value, SEQUENCE_DEVIATION should be BEFORE or TOP
IMG-00553: invalid rotate value