Database Recovery in NOARCHIVELOG Mode

Hi All,
I was trying to 'startup' my database & encountered the following error in the alert.log
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
ORA-01122: database file 469 failed verification check
ORA-01110: data file 469: '/ora/ctcm_uat02/CMOLP1/undo/CMOLP1_undots_30.dbf'
ORA-01209: data file is from before the last RESETLOGS
I then looked up on the internet and since the error was related to the UNDO TABLESPACE, i did the following:
sql>startup mount
sql>alter database datafile '/ora/ctcm_uat02/CMOLP1/undo/CMOLP1_undots_30.dbf' offline drop;
sql>alter database open
Thereafter the database kept on erroring on all the datafiles belonging to the undo tablespaces and i dropped all the datafiles belonging to the undo tablespace using the above command. (alter database datafile ....offline drop).
Next, i tried to open the database and got the following error from the alert log:
Tue May 12 18:15:24 2009
alter database open
Tue May 12 18:15:33 2009
Beginning crash recovery of 1 threads
Tue May 12 18:15:33 2009
Started redo scan
Tue May 12 18:15:33 2009
Completed redo scan
21 redo blocks read, 3 data blocks need recovery
Tue May 12 18:15:33 2009
Started recovery at
Thread 1: logseq 252, block 2, scn 1917.14626262
Tue May 12 18:15:33 2009
Recovery of Online Redo Log: Thread 1 Group 3 Seq 252 Reading mem 0
Mem# 0 errs 0: /ora/ctcm_dev/CMOLP1/redo/CMOLP1_redo03a.dbf
Tue May 12 18:15:33 2009
Completed redo application
Tue May 12 18:15:33 2009
Ended recovery at
Thread 1: logseq 252, block 23, scn 1917.14646284
3 data blocks read, 3 data blocks written, 21 redo blocks read
Crash recovery completed successfully
Tue May 12 18:15:35 2009
Thread 1 advanced to log sequence 253
Thread 1 opened at log sequence 253
Current log# 4 seq# 253 mem# 0: /ora/ctcm_dev/CMOLP1/redo/CMOLP1_redo04a.dbf
Successful open of redo thread 1
Tue May 12 18:15:38 2009
LOG_CHECKPOINT_INTERVAL was set when MTTR advisory was switched on.
Tue May 12 18:15:38 2009
SMON: enabling cache recovery
Tue May 12 18:15:38 2009
Successfully onlined Undo Tablespace 1.
Tue May 12 18:15:39 2009
SMON: enabling tx recovery
Tue May 12 18:15:39 2009
Database Characterset is US7ASCII
Tue May 12 18:15:39 2009
SMON: about to recover undo segment 1
Can someone please help me on this issue? Thanks and Regards

Hi ERROR,
I think i figured out the hidden parameter that you were referring to.
(1) I set the allowresetlogs_corruption=TRUE and commented undo_management. Then opened the database using--> alter database open resetlogs;
But still was not able to start the database. The alert log entries are as below:
ALTER DATABASE MOUNT
Thu May 14 18:11:56 2009
Successful mount of redo thread 1, with mount id 4113112614
Thu May 14 18:11:56 2009
Database mounted in Exclusive Mode.
Completed: ALTER DATABASE MOUNT
Shutting down instance: further logons disabled
Shutting down instance (immediate)
License high water mark = 2
Thu May 14 18:12:05 2009
ALTER DATABASE CLOSE NORMAL
ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
Thu May 14 18:12:05 2009
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archiving is disabled
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archiving is disabled
Would be great if you can help me further on this.
Regards,
Fuzzy

Similar Messages

Oracle recovery in noarchivelog mode

Hello,
SAP Release : ECC6
Oracle 10G
Solaris 10g
Our SAP system is in noarchivelog mode (formation environnement, with frequent client copies).
We frequently perform an offline backup.
The solaris server that is hosting our Sap system, has been brutally shutdown this morning,
due to a network issue.
Afterwards, we had to restart the sap system.
A fisrt error occured ; inconsistency between the control files ...
ORA-00205: error in identifying control file, check alert log for more info
In alert log :
ORA-00202: control file: '/oracle/ZMA/origlogA/cntrl/cntlrZMA.dbf'
ORA-27037: unable to obtain file status
We regenerated a new control file and replaced it.
The error was solved.
Then a second error occured :
SQL> startup
ORACLE instance started.
Total System Global Area 1660944384 bytes
Fixed Size                  2268216 bytes
Variable Size             851207112 bytes
Database Buffers          805306368 bytes
Redo Buffers                2162688 bytes
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> alter database open resetlogs ;
alter database open resetlogs
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oracle/ZMA/sapdata1/system_1/system.data1'
SQL> recover database using backup controlfile until cancel ;
ORA-00279: change 647063400 generated at 04/28/2008 11:10:01 needed for thread
1
ORA-00289: suggestion : /oracle/ZMA/oraarch/ZMAarch1_76005_618576658.dbf
ORA-00280: change 647063400 for thread 1 is in sequence #76005
The redo log #76005 is no more available; I tried to apply the online redo logs, but it didn't help.
We had to restore the whole database from the offline backup.
1/ I still have problems understanding why Oracle is asking for a recovery, when we tried to reopen the database ? The database was consistent this morning, how is it that the file '/oracle/ZMA/sapdata1/system_1/system.data1' became inconsistent ?
2/ In sap note 863417 "If the database operates in NOARCHIVELOG mode, the database can ONLY be completely recovered from instance failure but not from media failure. "
What is exactly the difference between media failure and instance failure ?
Does a network problem and then a reboot of the host is considered a media failure ?
Best Regards.
thank you for your help .

> 1/ I still have problems understanding why Oracle is asking for a recovery, when we tried to reopen the database ? The database was consistent this morning, how is it that the file '/oracle/ZMA/sapdata1/system_1/system.data1' became inconsistent ?
Because the database was not shut down cleanly. An open database is by definition "inconsistent" without the proper logfiles.
> 2/ In sap note 863417 "If the database operates in NOARCHIVELOG mode, the database can ONLY be completely recovered from instance failure but not from media failure. "
> What is exactly the difference between media failure and instance failure ?
Media = File/Raw-Device. If you database is crashing due to a software error it can be recovered, if a file is corrupt it can't be (since you have no redo logs).
> Does a network problem and then a reboot of the host is considered a media failure ?
A corrupt control file (e. g.) is a media failure.
Markus

Recovery in NOARCHIVELOG mode. A Sybex Study GUide quibble

Hi.
Actually, this is much more than a quibble as its a crucial point vis a vis the exam.
To perform a recovery in noarchivelog mode, we have to restore the db from the last backup.
I was under the impression that a backup of the database should NOT include the online redo logs.
But, to quote this Sybex book (p291 for Exam 032):
"To perform the database restore, you will need to copy all the data files, online redo logs, and controlfiles from the last backup and perform a full database restore" .
I understand that if we do a closed backup (as we would do if the db is in noarchivelog mode) then the redo logs are not available to be backed up and therefore are not included.
I just need this detail ironed out once and for all!
Thanks.
DA

When you restore the redo log file, you are basically defining the most recent time to which the restore can occur.
In a noarchivelog restore (of a proper clean backup), the most recent possible time is the time when the database was shut down and thus there are no redo entries to roll forward. Therefore, functionally, it really does not matter whether the redo log is restored or not. However, if the redo log file is not restored, you have two situations that must be managed: redo is much newer than the rest of the database, or redo is totally missing. Since you are in learning mode, I'll leave it to you to describe how to handle those two cases.
In an archivelog environment, restoring the redo log will severely limit the ability to restore to point-in-time as you can not move forward from the redo log's time. Therefore the recommendation is to not bother backing up the redo log file at all, so it can not be accidently restore. RMAN enforces this.
Personal 'best practice' is to make a safety copy of the redo log files before any restore. That way if an old set of redo is accidently copied or if the restore/recovery needs to be restarted, the environment can be reset to the start of the restore.

Recovery in noarchivelog mode

Scenario :
- Database is in noarchivelog mode.
- There are two redo logs for a database.
- A closed database backup was taken at log sequence 144.
- While the database was at log sequence 145, data file 2 was lost.
how can i recover the database till log sequence 145.
Kindly help me in this regard.

Hi,
If Current log sequence 145
& If log sequence 144 not overwritten the time cold backup (all datafiles+controlfile+redo logfile ) was taken, then use following steps:
1> shutdown ( if database is open)
2> restore only corrupted datafile
3> startup mount
4>recover database
5> alter database open

Database recovery in Inconsistent mode

Hi,
We have mirroring at 24:00 on one of the mount point in Solaris which copy all oracle datafiles,redo files and control files and create a replica of all these files in a separate folder. But my database is running in NOARCHIVELOG mode.I am assuming it would be an inconsistent backup.
I am wondering if in case of any failure can we recover with these replica files created on 24:00.
My query is if the database is in NOARCHIVELOG mode, Can we use the command "recover database until time" and recover database till 23:55.
Thanks,
Vaibhav

user10624526 wrote:
Hi,
We have mirroring at 24:00 on one of the mount point in Solaris which copy all oracle datafiles,redo files and control files and create a replica of all these files in a separate folder. But my database is running in NOARCHIVELOG mode.I am assuming it would be an inconsistent backup.
I am wondering if in case of any failure can we recover with these replica files created on 24:00.
My query is if the database is in NOARCHIVELOG mode, Can we use the command "recover database until time" and recover database till 23:55.
Thanks,
Vaibhavno & no
For you to obtain a consistent backup, the DB must first be cleanly shutdown.
Consider changing into ARCHIVE MODE

Taking the datafile offline when the database is in NOARCHIVELOG mode

My question is when the database is in No Archive log mode i'm not able to take the datafile offline.
When i tried in my computer i have noticed fallowing.
case1:
SYS>alter database datafile 5 offline;
ERROR at line1;
ORA-01145:offline immediate disallowed unless media recovery enabled.
case 2:
SYS>alter database datafile 5 offline immediate;
ERROR at line 1;
ORA-00933:SQL command not properly ended
case3:
I have tried the command alter database datafile 6 offline drop; (in NOARCHIVELOG mode) and it is showing the same effect as alter database datafile 6 offline; ( in ARCHIVELOG mode).
*In the NOARCHIVELOG mode are we really dropping the datafile to take the datafile offline? Will you please tell me the effect of keyword drop.

JohnWatson wrote:
You've marked your question answered - was that a mistake?
The answer is that you cannot directly take a datafile offline in noarchivelog mode. You must take the tablespace offline:
Hmm, are you certain about that? Perhaps I'm missing something.
SQL> select file_id, file_name, online_status, status from dba_data_files where tablespace_name = 'USERS';
   FILE_ID FILE_NAME                                          ONLINE_ STATUS
         4 /u01/app/oracle/oradata/TEST/users01.dbf           ONLINE AVAILABLE
SQL> select log_mode from v$database;
LOG_MODE
NOARCHIVELOG
SQL> alter database datafile 4 offline drop;
Database altered.
SQL> select file_id, file_name, online_status, status from dba_data_files where tablespace_name = 'USERS';
   FILE_ID FILE_NAME                                          ONLINE_ STATUS
         4 /u01/app/oracle/oradata/TEST/users01.dbf           RECOVER AVAILABLE
SQL> ALTER SYSTEM FLUSH BUFFER_CACHE; <-- may not have been necessary
System altered.
SQL> select count(*) from scott.emp;
select count(*) from scott.emp
ERROR at line 1:
ORA-00376: file 4 cannot be read at this time
ORA-01110: data file 4: '/u01/app/oracle/oradata/TEST/users01.dbf'
SQL> recover datafile 4;
Media recovery complete.
SQL> select file_id, file_name, online_status, status from dba_data_files where tablespace_name = 'USERS';
   FILE_ID FILE_NAME                                          ONLINE_ STATUS
         4 /u01/app/oracle/oradata/TEST/users01.dbf           OFFLINE AVAILABLE
SQL> alter database datafile 4 online;
Database altered.
SQL> select file_id, file_name, online_status, status from dba_data_files where tablespace_name = 'USERS';
   FILE_ID FILE_NAME                                          ONLINE_ STATUS
         4 /u01/app/oracle/oradata/TEST/users01.dbf           ONLINE AVAILABLE
SQL> select count(*) from scott.emp;
COUNT(*)
        14
Also, please see the following link from the manual which discusses altering data file availability in noarchivelog mode.
Altering Datafile Availability

System datafile block corruption - no backups and database in NOARCHIVELOG mode

Dear All,
Database version - oracle 11.1 Enterprise
OS - RHELinux 5.8
What are the options of recovering from physical block corruption when there are no backup available to perform block media recovery?
V$DATABASE_BLOCK_CORRUPTION reports two segments corrupted (please see attached image for details).
1 table in system datafile - sys_fba_barrierscn
1 index - (applicaiton index)
What are my options?
I know there is a possibility that the database will not restart after a shutdown due to corruption in system tablespace.
Database is in noarchivelog mode. So online backups are not possible and there aren't any full backups either.
I am thinking of below,
1. Run dbms_repair with fix_block_corruption. - Still database startup might fail?
2. Shutdown the database and take offline full backup with RMAN MAXCorrupt option.
Appreciate your suggestions and advises.
Thanks
Stefan

Thanks Sybrand,
Agree with your first two suggestions .
Also scheduled a expdp job tonight. (Only backup like thing they had was a expdp cron, but until today all the large tables were failing due to small undo_retention).
Yes. Flashback is not used. So hopefully it will not affect the a database restart i guess?
Related to dbms_repair, I was referring to - http://askdba.org/weblog/2010/08/physical-corruption-ora-1578-part-3/.
Where DBMS_REPAIR.FIX_CORRUPT_BLOCKS and DBMS_REPAIR.SKIP_CORRUPT_BLOCKS used.
Which i think will not use any redo.
Thanks
Stefan

Noarchivelog mode Recovery scenario

Hi,
We have a development server which has local unix file systems /u01-/u24 mount points. As many mount points are near to 100% our unix admin said they can't provide more space on the local file systems but we will be moving to EMC storage which has /u01-/u08 mount points. The databases on this server are in Noarchivelog mode. When they move to EMC storage i will copy (re-map) /u09-/u24 mount points data in the local file system to EMC storage /u01-/u08 mount points. After doing that i have to re-create the control file. When i am trying to open the database it will ask for media recovery. Since the database is in Noarchivelog mode i have no archive logs to apply. Please let me know in this scenario how to recover the database so that it opens without any errors. Appreciate your response.

We have a development server which has local unix file systems /u01-/u24 mount points. As many mount points are near to 100% our unix admin said they can't provide more space on the local file systems but we will be moving to EMC storage which has /u01-/u08 mount points. The databases on this server are in Noarchivelog mode. When they move to EMC storage i will copy (re-map) /u09-/u24 mount points data in the local file system to EMC storage /u01-/u08 mount points. After doing that i have to re-create the control file. When i am trying to open the database it will ask for media recovery. Since the database is in Noarchivelog mode i have no archive logs to apply. Please let me know in this scenario how to recover the database so that it opens without any errors. Appreciate your response.If your database is in NOARCHIVE LOG mode.
1) First put in mount status,
2) Copy datafiles by RMAN.
copy datafile 1 to ' new location';
3) rename all the datafiles from local to Storage.
alter database renaem file 'old location' to 'new location';
4) If you want to change the controflile to SAN
take a backup of controlfile,
alter database backup controlfile as 'location';
5) shutdown
Edit the PFILE to change controlfile location(new) if ASM follow below one.
startup in nomount.
rman> restore controlfile from 'backup location';
5) Now startup will do , no need to recreate the controlfile.
If your datafiles are huge, then after copying all the files to new location, take the trace of the controlfile and recreate.

ORA-01152 when restoring from RMAN backupset in NOARCHIVELOG mode

Hi all,
I got the error ORA-01152 when I tried restoring an Oracle 10g R1 database from an RMAN backupset into a new server. The error returned when it reached to the level of opening the database in resetlogs.
The database runs on NOARCHIVELOG mode and on Windows 2003 Server SP2 32-bit.
Following is what I did in RMAN:
set ORACLE_HOME=D:\oracle\product\10.1.0\db_1
set ORACLE_SID=DAWA
set PATH=D:\oracle\product\10.1.0\db_1\bin;%PATH%
cd %ORACLE_HOME%\bin
rman target sys/mypassword
Recovery Manager: Release 10.2.0.1.0 - Production on Tue Feb 13 00:36:55 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database (not started)
RMAN> startup nomount pfile=X:\temp\DawaPFILE.ORA
connected to target database (not started)
Oracle instance started
Total System Global Area 1048576000 bytes
Fixed Size 792200 bytes
Variable Size 551807352 bytes
Database Buffers 494927872 bytes
Redo Buffers 1048576 bytes
RMAN> restore controlfile from
'X:\temp\Flash_Rec\DAWA\AUTOBACKUP\2011_07_16\O1_
MF_S_756655133_7226R018_.BKP';
Starting restore at 19-JUL-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=270 devtype=DISK
channel ORA_DISK_1: restoring controlfile
channel ORA_DISK_1: restore complete
output filename=D:\ORACLE\ORADATA\DAWA\CONTROL01.CTL
output filename=D:\ORACLE\ORADATA\DAWA\CONTROL02.CTL
output filename=D:\ORACLE\ORADATA\DAWA\CONTROL03.CTL
Finished restore at 17-AUG-11
alter database mount;
database mounted
catalog backuppiece 'X:\temp\PUMHJATD_1_1';
catalog backuppiece 'X:\temp\PTMHJ91Q_1_1';
/* Rename the Redologfiles,so that they can be created in new locations
the database is opened in resetlogs */
SQL>conn sys as sysdba
-- get registered files from SELECT * FROM V$LOGFILE
SQL> alter database rename file
'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO01.LOG' to
'X:\oracle\oradata\dawa\REDO01.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO02.LOG'
to 'X:\oracle\oradata\dawa\REDO02.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO03.LOG'
to 'X:\oracle\oradata\dawa\REDO03.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO04.LOG'
to 'X:\oracle\oradata\dawa\REDO04.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO05.LOG'
to 'X:\oracle\oradata\dawa\REDO05.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO06.LOG'
to 'X:\oracle\oradata\dawa\REDO06.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO07.LOG'
to 'X:\oracle\oradata\dawa\REDO07.LOG';
/* Now in RMAN: restore the datafiles
    to new locations and recover. */
RMAN> run{
set newname for datafile
'E:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\UNDOTBS201' TO
'D:\oracle\oradata\dawa\UNDOTBS201';
set newname for datafile
'E:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\UNDOTBS202' TO
'D:\oracle\oradata\dawa\UNDOTBS202';
restore database;
switch datafile all;
alter database open resetlogs;
.../* alter database open resetlogs returned the errors: */
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 08/18/2011 08:44:45
ORA-01152: file 2 was not restored from a sufficiently old backup
ORA-01110: data file 2: 'D:\ORACLE\ORADATA\DAWA\UNDOTBS206'Thanks in advance.

SYS @ DAWA> shutdown immediate
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SYS @ DAWA> startup mount
ORACLE instance started.
Total System Global Area 1048576000 bytes
Fixed Size                   792200 bytes
Variable Size             551807352 bytes
Database Buffers          494927872 bytes
Redo Buffers                1048576 bytes
Database mounted.
SYS @ DAWA> recover database using backup controlfile until cancel;
ORA-00279: change 329012 generated at 03/08/2005 16:24:46 needed for thread 1
ORA-00289: suggestion :
X:\ORACLE\ORADATA\FLASH_REC\DAWA\ARCHIVELOG\2011_08_18\O1_MF_1_6_%U_.ARC
ORA-00280: change 329012 for thread 1 is in sequence #6
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log
'X:\ORACLE\ORADATA\FLASH_REC\DAWA\ARCHIVELOG\2011_08_18\O1_MF_1_6_%U_.ARC'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: 'X:\ORACLE\ORADATA\DAWA\SYSTEM01.DBF'You can download the alert log from here:
http://ahmedbaraka.com/temp/alertdawa.log

Media failure in Noarchivelog mode

Dear all,
I am running Oracle database 10g in noarchivelog mode.
It has a media failure, a datafile has corrupted. How can i recovery it suppose i dont have the latest backup?
Thanks and regards,
Steve

Hi,
since you don't have a backup, and you have a media failure, you cannot recover.
You can set the tablespace/datafile in question offline, and work with whatever is left in the remaining datafiles. (i.e. export/import elsewhere)
if the file is just corrupted, and not lost,
you may be able to get some of the data back using oracles data unloader, but that is going to be expensive (i.e. you would need to engage oracle consulting to do it for you)
i strongly recommend you get familiar with the rman tool next time around, this is quite capable of performing backup and recovery.
Karsten

Standby in Noarchivelog mode

Hello,
Standby Redo Log must be archived before the redo data can be applied to the standby database. If we put our standby database in noarchivelog mode, then standby database does not generate any archive.Because of this Redo data wont apply to the standby database. Right? Is this the reason why we put standby database in archivelog mode?
Thanks

Hello;
Standby Redo Log must be archived before the redo data can be applied to the standby database.That statement is not correct.
If we put our standby database in noarchivelog mode, then standby database does not generate any archive. Because of this Redo data wont apply to the standby database. Right?That statement is not correct either. While Standby can use a process which is like generating archive, archive is really being transported from the Primary database.
Is this the reason why we put standby database in archivelog mode?Yes. If you switch modes the standby becomes the primary and needs to be in archivelog mode.
Failover
If you do a failover there are two main methods for recovery, RMAN and Flashback. You want your Standby database to be ready for use as a Primary, otherwise why have it? So you need to have it ready for anything including recovery.
I debated the archive question with somebody here last year. They claim the Standby produces Archive because such and such a process does this. I disagree. In Standby mode the database is not doing what a Primary mode database does. Those Oracle processes don't create new archive, they complete the transfer of archive from a Primary. The Sequence number was created on the Primary.
From Oracle document
"If all databases in a distributed database operate in ARCHIVELOG mode, you can perform coordinated distributed database recovery. However, if any database in a distributed database is in NOARCHIVELOG mode, recovery of a global distributed database (to make all databases consistent) is limited by the last full backup of any database operating in NOARCHIVELOG mode."
If you search this document
Data Guard Concepts and Administration 11g Release 2 (11.2) E10700-02
For "ARCHIVELOG" you get several hits.
If you search for "NOARCHIVELOG" you get none.
I suppose in theory you could run a Standby in "NOARCHIVELOG" but you gain nothing. If you ever have a switchover or failover you need to fix this ASAP. I see no reason to add that item to my checklist. It just an extra step and in the event of a failover one I could be very unhappy about.
Best Regards
mseberg
Edited by: mseberg on Mar 15, 2013 1:25 PM

Restore using incremental backup with noarchivelog mode

Hello experts,
We are running SAP on Oracle databse(IN NOARCHIVELOG MODE) for which we are having full offline backup on every sunday and post which incremental backups on rest of the days. We have scenario to do restore db to the state till last friday's incremental backup.
Please let us know the procedure for restoring till that point. If possible using brtools utility(which is SAP specific).
Thank You
Regards,
Venkateshwar

If you do not want to read the whole doc This is the snippet for you.
Recovering a NOARCHIVELOG Database with Incremental Backups
Restoring a database running in NOARCHIVELOG mode is similar to restoring a database in ARCHIVELOG mode. The main differences are:
Only consistent backups can be used in restoring a database in NOARCHIVELOG mode.
Media recovery is not possible because no archived redo logs exist.
You can perform limited recovery of changes to a database running in NOARCHIVELOG mode by applying incremental backups. The incremental backups must be consistent, like all backups of a database run in NOARCHIVELOG mode, so you cannot make backups of the database when it is open.
When you are recovering a NOARCHIVELOG database, specify the NOREDO option on the RECOVER command to indicate that RMAN should not attempt to apply archived redo logs. Otherwise, RMAN returns an error.
To recover a NOARCHIVELOG database with incremental backups:
After connecting to the target database and the recovery catalog, place the database in a mounted state:
STARTUP FORCE MOUNT
Restore and recover the database.
For example, you can perform incomplete recovery with the following commands:
RESTORE DATABASE
FROM TAG "consistent_whole_backup";
RECOVER DATABASE NOREDO;
Open the database with the RESETLOGS option.
For example, enter the following command:
ALTER DATABASE OPEN RESETLOGS;

Backup of one tablespace in noarchivelog mode

Hi,
I am running 10g.
Is it possibe to backup a specific tablespace in noarchive mode?
Thanks

Hi
I am able to backup the tablespace,
but after the recovery loosing the table data.
The database is in noarchivelog mode!
here is what I am doing:
my_table TABLE has 100 rows, and is saved under my_tablespace TABLESPACE.
RMAN> sql 'alter tablespace my_tablespace offline';
RMAN> backup tablespace my_tablespace;
RMAN> sql 'alter tablespace my_tablespace online';
Now I truncate the table
TRUNCATE TABLE my_table;
RMAN> sql 'alter tablespace my_tablespace offline';
RMAN> restore tablespace my_tablespace;
RMAN> recover tablespace my_tablespace;
RMAN> sql 'alter tablespace my_tablespace online';
Now the my_table TABLE is after the rcovery empty :-(
What I am doing wrong

Restore in noarchivelog mode ( redo log files have been dropped )

1, A full backup taken using RMAN is available on disk.
2, The current control files were NOT damaged and do not need to be restored.
3, All data files are damaged .
4, The database is in NOARCHIVELOG mode.
I restore database :
1. RMAN> STARTUP MOUNT
2. RMAN> RESTORE DATABASE;
3. RMAN> recover database;
in this step , I got the information about needing redo log files ; but the redo log
files have been dropped , what should i do ?
else
I want to know there is the command 'recover database using backup control file'
in rman or not ?
Tks

Possibly loss of data (because information in online redo logs is lost):
recover database until cancel;
(cancel immediately)
alter database open resetlogs; (to build a new set of redo logs)
It's not necessary to use a backup controlfile here.

Datafile recover in case of noarchivelog mode

my database is in noarchivelog mode and there is no backup available and one of my datafile is currupted then how can i recover the datafile??
thanx in advance

saugat chatterjee wrote:
my database is in noarchivelog mode and there is no backup available and one of my datafile is currupted then how can i recover the datafile??
thanx in advanceWhat ever version. To recover datafile archiving should be enabled. Noarchive norecovery...

Database Recovery in NOARCHIVELOG Mode

Similar Messages

Maybe you are looking for