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 |
ORA-01479: last character in the buffer is not Null
ORA-23342: invalid parameter column string
ORA-13480: the Source Type is not supported
ORA-39315: illegal swap() call: only applys after clone/sync_code
ORA-19682: file string not in block media recovery context
ORA-26076: cannot set or reset value after direct path structure is allocated
ORA-29289: directory access denied
ORA-16608: one or more sites have warnings
PLS-00341: declaration of cursor 'string' is incomplete or malformed
ORA-27157: OS post/wait facility removed
RMAN-06431: recovery catalog created
ORA-40220: maximum number of attributes exceeded