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 | 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-25215: user_data type and queue type do not match
PCC-01202: Identifier "string" truncated to 31 characters
ORA-13356: adjacent points in a geometry are redundant
ORA-13760: duplicate entry for "SQL_ID" "string" in "SQL Tuning Set" "string"
RMAN-00563: password too long
ORA-15113: alias name 'string' refers to a directory
ORA-16803: Unable to query a database table or fixed view.
ORA-22858: invalid alteration of datatype
RMAN-03039: Spooling for log turned off
ORA-32146: Cannot perform operation on a null date
NID-00502: TARGET Username/Password (NONE)
ORA-25256: consumer cannot be specified with a single-consumer queue or an exception queue