Rman datafile recovery ORA-01178

Hi Team,
I need to suggestion in recovering this file.
SQL> /
NAME STATUS
+DATA_GRP/demo/datafile/test.dbf RECOVER
Here I manually removed the file from asm.
ASMCMD> ls -ltr
Type Redund Striped Time Sys Name
DATAFILE UNPROT COARSE SEP 02 14:00:00 Y SYSAUX.264.695779475
DATAFILE UNPROT COARSE SEP 02 14:00:00 Y SYSTEM.263.695779475
DATAFILE UNPROT COARSE SEP 02 14:00:00 Y UNDOTBS1.266.695779475
DATAFILE UNPROT COARSE SEP 02 14:00:00 Y USERS.262.695779511
DATAFILE UNPROT COARSE SEP 02 15:00:00 Y TEST.271.696521689
N test.dbf => +DATA_GRP/DEMO/DATA
FILE/TEST.271.696521689
ASMCMD> rm -f test.dbf
ASMCMD> ls -ltr
Type Redund Striped Time Sys Name
DATAFILE UNPROT COARSE SEP 02 14:00:00 Y SYSAUX.264.695779475
DATAFILE UNPROT COARSE SEP 02 14:00:00 Y SYSTEM.263.695779475
DATAFILE UNPROT COARSE SEP 02 14:00:00 Y UNDOTBS1.266.695779475
DATAFILE UNPROT COARSE SEP 02 14:00:00 Y USERS.262.695779511
Then I tried to recreate the datafile, But I failed
SQL> alter database create datafile 5;
alter database create datafile 5
ERROR at line 1:
ORA-01178: file 5 created before last CREATE CONTROLFILE, cannot recreate
ORA-01110: data file 5: '+DATA_GRP/demo/datafile/test.dbf'
and also I tried to restore the datafile.same error.
RMAN> restore datafile 5;
Starting restore at 02-SEP-09
using channel ORA_DISK_1
creating datafile fno=5 name=+DATA_GRP/demo/datafile/test.dbf
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 09/02/2009 17:50:47
ORA-01178: file 5 created before last CREATE CONTROLFILE, cannot recreate
ORA-01110: data file 5: '+DATA_GRP/demo/datafile/test.dbf'
could anyone suggest me to recover the datafile and my retention policy is set to none.
Thanks & Regards,
Muhammed Thameem. S

You look remarkably close to both toast and a runner up spot on a reality TV show titled "What were you thinking when you ....?"
Open an SR at metalink.

Similar Messages

Blockrecover but full datafile restore + ORA-01193

Hi,
We have a proplem, here is a short sescription:
We have corrupt blocks, how can we solve this problem? Blockrecover uses full datafile restore and finally fails with ORA-01193.
Here is a detailed description:
We have a 330GB datafile (bigfile tablespace) with 46 corrupt block.
DB version 10.2.0.4, Oracle linux, we use ASM.
We would repair these blocks.
V$DATABASE_BLOCK_CORRUPTION after "backup validate check logical datafile 7" :
FILE#     BLOCK#     BLOCKS     CORRUPTION_CHANGE#     CORRUPTION_TYPE
7     16872378     1     0     FRACTURED
7     16872408     40     0     CORRUPT
7     16872379     5     0     CORRUPT
The result is similar by dbv.
We have archivelog mode and backupset created by rman command:
backup as compressed backupset incremental level 0 database;
All of the corrupted blocks are in 1 LOB segment.
We copied the LOB segment, only 5 record cannot be read.
The corrupted LOB segment (and table) was exchanged by the copied (not corrupted) data, so users can work.
We remained the corrupted LOB segment in the database, but it is not in use.
I started blockrecovery by command:
BLOCKRECOVER DATAFILE 7 BLOCK 16872378,...,16872447;
The listed blocks are same as in the V$DATABASE_BLOCK_CORRUPTION, so the command could be:
BLOCKRECOVER CORRUPTION LIST;
The database was opened during blockrecocer and the datafile 7 was online.
A line appeared in the V$SESSION_LONGOPS with:
"RMAN: full datafile restore"
The restore was more than 4 hours, and finally it is failed with error:
Starting blockrecover at 29-AUG-12
starting media recovery
ORA-01193 file % is not the same file seen at start of recovery
Based on V$SESSTAT there were lot of physical read but only some physical write.
Maybe full datafile read, and only corrupted blocks was changed, but I didn't check it exactly.
We retried blockrecover with only one block, but the result was same: it failed after 4 hours with ORA-01193.
We retried the blockrecovery on a mounted but not opened database, and the datafile was offline:
SHUTDOWN IMMEDIATE;
STARTUP MOUNT;
ALTER DATABASE DATAFILE 7 offline
BLOCKRECOVER ...
The result was same: it failed after 4 hours with ORA-01193.
rman backup failed with error:
RMAN : ORA-19566: exceeded limit of 0 corrupt blocks for file %
After set maxcorrupt, rman backup ran successfuly
SET MAXCORRUPT FOR DATAFILE 7 TO 46;
Based on our current info, these workaround seems best for us:
- rman "set maxcorrupt"
- DB_BLOCK_CHECKING=FULL
- drop corrupted (but copied and not used segment)
- wait until corrupted blocks will be reallocated (checking it periodically by dbv)
- set maxcorrupt to 0
Our questions are:
*1. Why oracle uses "RMAN: full datafile restore" during blockrecover?*
Why needed to read the whole datafile?
One of the advantage of blockrecover should be the relative small IO, and fast restore.
I found only 2 results in google for "blockrecover" and "RMAN: full datafile restore".
(One of the findings was in this forum, but it was no answer for our problem)
*2. ORA-01193: file is not the same, but why?*
It is strange on opened database and online datafile, because other advantage of blockrecover should be the online recovery.
But it is more-more strange on closed(mounted) database and offline datafile. Only the rman blockrecover could change this file.
I found only 3 results in google for "blockrecover" "ORA-01193"
I found only the oerr output in google for "ORA-01193". But what does it mean? Only the rman blockrecover could change this file.
Cause: A different copy of the file was accessed the last time media recovery looked at the file header. A backup of the file was restored or the meaning of the file name changed during recovery.
Action: Ensure the correct file is available, then retry recovery.
*3. What else can be do to repair these corrupt blocks? What can we do for success blockrecover, or is there any other idea?*
Other infos:
- DB_BLOCK_CHECKING was false, but we changed it to FULL to avoid the subsequent corruptions
ALTER SYSTEM SET DB_BLOCK_CHECKING = FULL scope=both
- DBMS_REPAIR cannot detect the (out-of-line) LOB segment errors.
- rman SET MAXCORRUPT is not a "calming" solution
- When I read on internet, when we drop the corrupted LOB segments, the blocks will remains corrupt.
And the block will be repaired/formatted only when a new segment will allocate these blocks.
Based on metalink 336133.1, we can ensure the new allocation by fill the datafile with dummy data until the corrupted blocks will be allocated.
But this is a very IO intensive task.
- full recovery
very IO intensive, we try to avoid it.
Thx: lados.

Hi,
other infos:
We use ASM, and one of the disk is dropped and added after the last full (incremental level 0) backup. Can this premise causes the slow restore (something physical storage info is changed), or the ORA-01193 error (file % is not the same file seen at start of recovery) ? I don't think that a full db backup is needed after ASM disk drop/add/rebalance. But we tried a full backup (this was when the corrupt block first appeared with ORA-19566).
I found only one finding in the metalink for ORA-01193. The oerr reference (cause,action). It would be strange, if nobady else had problem with this error.
Thx: lados.

RMAN Backup error:ORA-04030: out of process memory

Hi,
Our RMAN backup is failing with below error:
===========================
RMAN-03002: failure of backup plus archivelog command at 05/22/2010 05:31:33
ORA-04030: out of process memory when trying to allocate 82444 bytes (pga heap,control file i/o buffer)
=============================
Please suggest
Thanks and Regards

We upgrade our catalog database(Linux) to 10.2.0.4 and our target database is 10.2.0.3(Windows),
we executed upgrade catalog twice and then when we again tried to execute the below command
rman sys/syspwd@targetdb catalog rman/rman@rmancat
Recovery Manager: Release 10.2.0.4.0 - Production on Sat May 22 15:10:36 2010
Copyright (c) 1982, 2007, Oracle. All rights reserved.
PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.03 in TARGET database is not current
PL/SQL package SYS.DBMS_RCVMAN version 10.02.00.03 in TARGET database is not current
connected to target database: WEBCT (DBID=3699379059)
connected to recovery catalog database
RMAN>
=======================
Still we are getting this error
and our backup falied with below errors:
======================
PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.03 in TARGET database is not current PL/SQL package SYS.DBMS_RCVMAN version 10.02.00.03 in TARGET database is not current connected to target database: WEBCT (DBID=3699379059) connected to recovery catalog database
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 05/22/2010 15:09:44
ORA-06550: line 1, column 14:
PLS-00306: wrong number or types of arguments in call to 'VALIDATEARCHIVEDLOG'
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
==========================
Please suggest

Problem with RMAN incomplete recovery

Oracle Version: 9i
Operating System: Windows 2000
I have a problem with RMAN incomplete recovery until sequence.
According to my database structure ............
SQL> SELECT GROUP#,SEQUENCE#,THREAD# FROM V$LOG;
GROUP# SEQUENCE# THREAD#
1 14 1
2 13 1
3 12 1
I took the backup of backup of full database using RMAN and i am trying to recover like this:
RUN
ALLOCATE CHANNEL C1 TYPE DISK;
SET UNTIL SEQUENCE 7 THREAD 1;
RESTORE DATABASE;
RECOVER DATABASE;
ALTER DATABASE OPEN RESETLOGS;
BUT i am getting a message saying there is no backup of DATAFILE 1,2,......10 to restore although my database is in archivelog mode and i took a backup.
Yachendra

Please consult v$backup_datafile.
It will tell you when the file was backed up.
RMAN will always search for a datafile backup prior to the logsequence or whatever is limiting the incomplete recovery.
Likely when you made your backup Oracle was already past sequence 7.
Sybrand Bakker
Senior Oracle DBA

RMAN-03008 and ORA-07217 after restore of controlfile, 11.2.0.2

Hi,
try to restore backup done with 11.2.0.2
because upgrade to 11.2.0.3 has problems with workspace manager,
- done with DBUA - which is a other part of the story.
OS is SLES11SP1 x86_64
Here is what happens:
startup nomount with minimal pfile in 11.2.0.2 environment
restore controlfile from SBT
channel T1: restore complete, elapsed time: 00:01:45
output file name=+DSKGRP1/alkklefq/controlfile/control01.ctl
output file name=+DSKGRP1/alkklefq/controlfile/control02.ctl
then
RMAN> ALTER DATABASE MOUNT;
database mounted
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03008: error while performing automatic resync of recovery catalog
ORA-07217: sltln: Umgebungsvariable kann nicht ausgewertet werden.
No other command like show all, resync catalog or what ever is working,
always fails with RMAN-03008 and ORA-07217
and after
run {
allocate channel T1 type 'SBT_TAPE' format 'b_%d_%u_%p_%c.bck';
restore database from tag 'TAG20120730T212808';
i got
Speicherzugriffsfehler = segmentation fault
Can anyone throw light on this?
Regards
Michael

Hello;
Based on the information you probably I would double check my "env" for an issue. Something set wrong or not set.
Does the "env" work without error?
Here's what is set on mine :
/home/oracle:PRIMARY >env
HOSTNAME=
TERM=
SHELL=
HISTSIZE=
NLS_LANG=
TMPDIR=
SSH_CLIENT=
SSH_TTY=
USER=oracle
LD_LIBRARY_PATH=
LS_COLORS=
ORACLE_SID=
ORACLE_BASE=
SSH_AUTH_SOCK=
COBBLER_SERVER=
MAIL=
PATH=
INPUTRC=
PWD=
EDITOR=
LANG=
TZ=
ORACLE_TERM=
SSH_ASKPASS=
SHLVL=
HOME=
TMP=
LOGNAME=oracle
SSH_CONNECTION=
LESSOPEN=
ORACLE_HOME=
G_BROKEN_FILENAMES=Best Regards
mseberg
Edited by: mseberg on Aug 6, 2012 8:02 AM

What are the steps in RMAN Backup & Recovery 10 G

Hi All
Please list out What are the steps in RMAN Backup & Recovery 10 G
Regards

Take a look at the user guide or at the getting started section, dba core tasks - backup and recovery.
C.

RMAN-06428 recovery catalog is not installed

RDBMS Version: 8.1.6
Operating System and Version: sun sparc 5.8
Error : RMAN-06428 RMAN-06428 recovery catalog is not installed
Product (i.e. SQL*Loader, Import, etc.): RMAN
Product Version: 8.1.6
Hi,
I hv a database running in unix box 1 (say 'FAST')
and Im trying to install a recovery catalog database in unix box
2
(Rcat)
1) in unixbox2..I hv created a new database, and I hv created a
tablespace rcvcat and user rman .granted catalog_recovery_owner
to rman.
also I hv created a catalogue using this command
create catalogue tablespace rcvcat;
(no error logs generated)
2)now when I try to connect to the catalogue I am getting an
error
what I did is, I tried connecting to rman of target database
(FAST database)
% rman target /catalog rman/rman@rcat
Recovery Manager: Release 8.1.6.0.0 - Production
RMAN-06005: connected to target database: FAST (DBID=3819569154)
RMAN-06008: connected to recovery catalog database
RMAN-06428: recovery catalog is not installed
also I tried like this,
% rman target system/manager@fast catalog rman/rman@rcat
Recovery Manager: Release 8.1.6.0.0 - Production
RMAN-06005: connected to target database: FAST (DBID=3819569154)
RMAN-06008: connected to recovery catalog database
RMAN-06428: recovery catalog is not installed
I dont understand why it says recovery catalog not installed ,
when I hv created one in rcat database.
Can anyone help me how to connect to catalog and register my
database (I mean from which machine I need to run the commands)
Thanks
Venkat

You do have a problem. It seems your "Shift" key is stuck.
Anyway, please read: [ID 188682.1],
Have a nice day.

Help needed on RMAN backup/recovery

Hi All,
I planning to implement the following backup strategy..
Online hotbackup is taking using RMAN without Recovery Catalog, Instead using controlfile autobackup to the repository. We the following backup schedules
1. Weekly full backup of database.
2. Daily Incremental backup with archive logs
And the backupset files created by the above schedule are stored in tape.
My Assumption:
As we are using control file autobackup, whenever i take full/incremental backup. the backup information will be stored in control file and the control files/spfile also will be backed up.
I did the following:
1. I have taken full backup(incr level=0) of database in the morning.
2. After taking the full backup, i did some transactions in one of the table.
3. Again, i have taken the incremental backup of the database.
4. All the backup pieces are stored in a tape.
My Doubt:
1. Now, controlfile will have information of full backup and incremental backup right?
2. If i restore the database in a new machine with these backups, both full backup files and incremental backup files are considered?
Thanks,
Praveen.

To answer your questions:
1. Now, controlfile will have information of full backup and incremental backup right?Yes.
2. If i restore the database in a new machine with these backups, both full backup files and incremental backup files are considered?YES.
HTH
Thanks
Chandra

Database Datafiles Recovery. ORA-01219: database not open:

Hi,
I have a 10g database running on SuSE Linux server. I mistakenly deleted one of my file system's files that contain some of the database datafiles. I can connect to the database but I am failing to run queries:
SQL> select * from global_name;
select * from global_name
ERROR at line 1:
ORA-01219: database not open: queries allowed on fixed tables/views only
I do weekly cold backups of the server. My database is in NOARCHIVE log mode. What is the best way to recover my data; Is it possible that I restore only the file system or I should should do a complete restore of all file systems??
Regards
Kevin
Edited by: Kevin Honde on Jul 28, 2010 2:55 PM

I mistakenly deleted one of my file system's files that contain some of the database datafiles.Ok
I do weekly cold backups of the server.Great !!
My database is in NOARCHIVE log mode. That's the mistake in my opinion
What is the best way to recover my data; Restore it from the latest available cold backup.
There will be a data loss post weekly consistent cold backup. Which you have to accept because you do not have your database running in Archive Log mode.

Creating physical standby using rman fails with ORA-19558: error de-allocat

Dear All,
We are creating physical stadnby database from 2 node RAC ( 2 node RAC to standalone physical standby).
While in the rman duplicate process we are getting below error, we were not able to sorted out..
No third party storage has been used ....
DB version : 11gR2 and the OS is RHEL5
Appreciate if any one hepl us to resolve this issue ...
Thanks in advance ...
RMAN-03009: failure of backup command on prmy1 channel at 10/05/2011 17:59:26
ORA-19558: error de-allocating device
ORA-19557: device error, device type: DISK, device name:
ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
ORA-03113: end-of-file on communication channel
Edited by: 889828 on 2011/10/06 2:17 AM

The problem is well decribed in your alert log.....you are using Oracle Managed File names which means you will not be able to duplicate the database as RMAN won't be able to automatically generate new names for the files using the DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT initialization parameters.
Youll have to use the SET NEWNAME command to specify the names of the database files. Done this a few times , and I don't recommend using OMF specifically beacuse of this hassle.
WARNING: OMF is enabled on this database. Creating a physical standby controlfile, when OMF is enabled on the primary database, requires manual RMAN intervention to resolve OMF
datafile pathnames.
NOTE: Please refer to the RMAN documentation for procedures describing how to manually resolve OMF datafile pathnames.
Problem handling is described in
Oracle® Database Backup and Recovery Reference
10g Release 2 (10.2)
Part Number B14194-03

Rman block recovery

I have a database which has database block corruption. I had a successful rman backup of Sunday.
Monday and Tuesday rman backup failed saying
ORA-19566: exceeded limit of 0 corrupt blocks for file F:\EM…….
Then I modified rman script to skip up to 5 corrupt blocks..
set maxcorrupt for datafile 'F:\......' to 5;
Now my rman backup is successful on Wednesday…
Now, I want to repair blocks using rman’s block recover command:
recover datafile 19 block 321, 322, 385, 513, 577 restore
My questions are:
a. Will rman automatically start with Sunday’s successful back and then apply archived logs.. or
Will it start with Wednesday’s backups and then it won’t be able to recover corrupted blocks…
b. How to force rman block recover to start from Sunday’s backup …

My questions are:
a. Will rman automatically start with Sunday’s successful back and then apply archived logs.. or
Will it start with Wednesday’s backups and then it won’t be able to recover corrupted blocks…If the sunday's RMAN backup is available. It will start with sunday's backup and will perform block recovery from required archive log.
b. How to force rman block recover to start from Sunday’s backup …Not required. it will check for required backuppiece and go ahead with the process.

Rman restore/recovery

Hi Guys,
10.2.0.4
Scenario:
DELETED: REDO LOGS, ARCHIVE LOGS, DATAFILES
STILL IN PLACE: CURRENT CONTROLFILES, INIT FILE
If I have my current controlfiles with me but no re-do logs, I won't be able to use the controlfiles for recovery right as it won't be able to find the redo logs? I still have to restore the controfile from the database or use the create controlfile statement?
Please advise.
thanks

Hi Guys,
After i startup mount the database. I did a restore database followed by recover database. However, there's error as below:
RMAN> run
2> {
3> allocate channel c1 type disk;
4> recover database;
5> }
allocated channel: c1
channel c1: sid=157 devtype=DISK
Starting recover at 24-JAN-11
starting media recovery
media recovery failed
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 01/24/2011 18:54:46
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database reco
ver if needed
start
ORA-00283: recovery session canceled due to errors
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\REDO0
2.LOG'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
thanks

9.2.0.6 RMAN Disaster recovery issue

Our production database crashed and we are doing DR on a new host.
We dont have any catalog database and we dont use controlfile autobackup.
We just do a full backup including controlfile and also archive logs
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
run {
allocate channel d1 type disk;
backup database format '/data/TESTDB/rman/testdb_bk_%s_%p_%t' include current controlfile;
backup archivelog all format '/data/TESTDB/rman/testdb_al_%s_%p_%t' delete input;
release channel d1;
We copied these backup pieces to the new host and tried the following way to restore the database.
startup nomount
rman
connect target /
RMAN> set DBID 2507695351;
executing command: SET DBID
RMAN> run
2> {
3> allocate channel d1 type disk;
4> restore controlfile from '/data/TESTDB/rman/testdb_bk_2_1_724368405';
5> }
allocated channel: d1
channel d1: sid=12 devtype=DISK
Starting restore at 14-JUL-10
channel d1: restoring controlfile
channel d1: restore complete
replicating controlfile
input filename=/data/TESTDB/cntrl01.dbf
output filename=/data/TESTDB/cntrl02.dbf
output filename=/data/TESTDB/cntrl03.dbf
Finished restore at 14-JUL-10
released channel: d1
exit
sqlplus '/ as sysdba'
shutdown immediate;
startup mount;
RMAN> run
2> {
3> allocate channel d1 type disk;
4> restore database;
5> }
using target database controlfile instead of recovery catalog
allocated channel: d1
channel d1: sid=12 devtype=DISK
Starting restore at 15-JUL-10
released channel: d1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 07/15/2010 00:03:18
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
We are using 9.2.0.6 on LINUX
The list backup commands too return EMPTY
RMAN> list backup;
RMAN> list backup of database;
---Any ideas ?
Srinivas

I am also uploading the logfile of the backup job of the source database
RMAN> run
2> {
3> allocate channel d1 type disk;
4> backup database format '/data/TESTDB/rman/testdb_bk_%s_%p_%t' include current controlfile;
5> backup archivelog all format '/data/TESTDB/rman/testdb_al_%s_%p_%t' delete input;
6> release channel d1;
7> }
allocated channel: d1
channel d1: sid=17 devtype=DISK
Starting backup at 14-JUL-10
channel d1: starting full datafile backupset
channel d1: specifying datafile(s) in backupset
including current controlfile in backupset
input datafile fno=00001 name=/data/TESTDB/system01.dbf
input datafile fno=00002 name=/data/TESTDB/undotbs01.dbf
channel d1: starting piece 1 at 14-JUL-10
channel d1: finished piece 1 at 14-JUL-10
piece handle=/data/TESTDB/rman/testdb_bk_2_1_724368405 comment=NONE
channel d1: backup set complete, elapsed time: 00:00:01
Finished backup at 14-JUL-10
Starting backup at 14-JUL-10
current log archived
channel d1: starting archive log backupset
channel d1: specifying archive log(s) in backup set
input archive log thread=1 sequence=3 recid=1 stamp=724368322
input archive log thread=1 sequence=4 recid=2 stamp=724368406
channel d1: starting piece 1 at 14-JUL-10
channel d1: finished piece 1 at 14-JUL-10
piece handle=/data/TESTDB/rman/testdb_al_3_1_724368406 comment=NONE
channel d1: backup set complete, elapsed time: 00:00:02
channel d1: deleting archive log(s)
archive log filename=/data/TESTDB/arch/archTESTDB_3.arc recid=1 stamp=724368322
archive log filename=/data/TESTDB/arch/archTESTDB_4.arc recid=2 stamp=724368406
Finished backup at 14-JUL-10
released channel: d1
RMAN> exit

Block corruptioin after rman restore/recovery

Thanks for taking my question!
Oracle Enterprise Edition 11.1.0.7 on Windows 2008. Using Rman on-line backups COMPRESSED.
Can anyone give me any ideas on why SYSAUX data block corruption should occur after a rman recovery?
Below is my script. Am I missing something? Should I be physically removing the redo? Any ideas welcome?
Thanks!
Kathie
rman> restore until seq = 123
recover until seq = 123
alter database open resetlogs;
Background:
I had to do a rman recovery the other day to restore our database back to the previous day. After the recovery the sysaux table became logically corrupted. I tried to fix data corruption with rman but it said it couldn't after reading thru 6 days of backups. I ended up deleting the database, recreating the database and restoring from an export takien a few hours prior.
I now have a database to test rman recovery. Database has been up and rman backups (compressed) running for several days. I tried to recover back to previouse day and again SYSAUX has logical corruption. I tried to use Rman to recover data corruption but it failed.
I deleted database and recreated it. Took several rman on-line backups (this time not compressed). Did 3rd recovery this time only a few hours back. This time everything worked - no sysaux block corruption but why? The only difference is the recovery used non compressed backups and recovery was a shorter time frame. why ???

I agree the errors are not identical but I am going to stop performing compressed backups until I am sure that is not the issue.
My first two recoveries had logical block corruption and this last one without compression set had no block corruption. I performed the same recovery process for all recoveries and the big difference was the successfull recovery did not have compressed backups. I checked v$database_block_corruption and it shows no errors. I also, performed a backup and verify to double check.
The only issue I can see is below. I am hoping someone can confirm this is normal after "alter database open resetlogs". Can anyone verify that?
Thanks!
Kathie
Thu Aug 27 10:17:49 2009
alter database open resetlogs
RESETLOGS after incomplete recovery UNTIL CHANGE 3587892
Resetting resetlogs activation ID 3129052671 (0xba818dff)
Thu Aug 27 10:17:50 2009
Errors in file e:\oracle\diag\rdbms\cs90dev\cs90dev\trace\cs90dev_m000_2244.trc:
ORA-00316: log 1 of thread 1, type 0 in header is not log file
ORA-00312: online log 1 thread 1: 'E:\ORACLE\11.1.0\ORADATA\CS90DEV\REDO01.LOG'
Errors in file e:\oracle\diag\rdbms\cs90dev\cs90dev\trace\cs90dev_m000_2244.trc:
ORA-00316: log 2 of thread 1, type 0 in header is not log file
ORA-00312: online log 2 thread 1: 'E:\ORACLE\11.1.0\ORADATA\CS90DEV\REDO02.LOG'
Errors in file e:\oracle\diag\rdbms\cs90dev\cs90dev\trace\cs90dev_m000_2244.trc:
ORA-00316: log 3 of thread 1, type 0 in header is not log file
ORA-00312: online log 3 thread 1: 'E:\ORACLE\11.1.0\ORADATA\CS90DEV\REDO03.LOG'
Thu Aug 27 10:17:53 2009
Setting recovery target incarnation to 3

RMAN Database Recovery

Dear All
I am using oracle 10.0.2.4 on linux 5.
I have take backup from RMAN by using backup database.
Now i shutdown database and rename the system,sysaux,undo,users datafies.
Than start db in force mount mode by using startup force mount
Than i restore db backup by using RMAN command restore database.
then i shutdown db and starup normal. but now i am geeting follow error
Errors in file /u01/app/admin/orcl/bdump/orcl_dbw0_27539.trc:
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: '/u01/app/oradata/orcl/system01.dbf'

01157, 00000, "cannot identify/lock data file %s - see DBWR trace file"
// *Cause: The background process was either unable to find one of the data
// files or failed to lock it because the file was already in use.
// The database will prohibit access to this file but other files will
// be unaffected. However the first instance to open the database will
// need to access all online data files. Accompanying error from the
// operating system describes why the file could not be identified.
// *Action: Have operating system make file available to database. Then either
// open the database or do ALTER SYSTEM CHECK DATAFILES.

Rman datafile recovery ORA-01178

Similar Messages

Maybe you are looking for