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.

Similar Messages

  • 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

  • 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 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

  • 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;

  • Can't backup database in NOarchivelog mode

    Hi there,
    I get this error when I run this command from rman:
    backup database
    Starting backup at 19-JAN-11
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 01/19/2011 17:18:10
    ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
    please help.
    Thanks in advance!

    user13286861 wrote:
    ok it finally shutdown cleanly.
    I altered it in archivelog mode.
    Now I can run a backup database command from rman?What does it cost to try it and see? What would be the worst thing that could possibly happen? An error message saying you can't do that?
    And please note, this forum is not a chat line. Operators are NOT standing by. Posting a new message every two minutes to give an update on the fact that the database hasn't shut down yet is not necessary and not productive.
    If there are a lot of pending transactions when you issue SHUTDOWN IMMEDIATE, they will all have to be rolled back as part of the shutdown. That can take some time. And if you bypass that with SHUTDOWN ABORT, they will have to be rolled back as part of instance crash recovery on the next startup, which will also take some time. Five minutes may feel like an eternity when you are sitting there waiting for your command to complete, but is no reason to panic.

  • Back-up in noarchivelog mode

    If running in NOARCHIVELOG mode, the script displays the following output:
    Warning: Log archiving (ARCHIVELOG mode) is currently disabled. If
    you restore the database from this backup, any transactions that take
    place between this backup and the next backup will be lost. It is
    recommended that you enable ARCHIVELOG mode before proceeding so
    that all transactions can be recovered upon restore. See the section
    'Enabling ARCHIVELOG Mode...' in the online help for instructions.
    Backup with log archiving disabled will shut down and restart the
    database. Are you sure [Y/N]?
    i was wondering why will it be lost when i am going to make a current backup? I will obviously stop all transactions isn't it?

    Case of archive log mode online redo log files dumped into archives. So let suppose you have full backup at morning 6 am.
    If your database crashes around 8 am, you can restore 6 am backup and you option of recovery until 8am. So there is no data loss until you have archives.
    Now we talk of noarchivelog mode, here online redo log files are not dumped because of noarchivelog mode of database.
    You have backup at 6 am
    Now the time is 8 am , your database crashed. Now you have to restore 6 am backup. Later there is no concept of recovery. It's just restore. Because you don't have archives to perform recovery.
    So again archivelog mode depends on your business requirements.
    Overall you have two hours of data loss in noarchivelog mode.
    HTH.

  • ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode

    Hi All,
    Need help from the gurus.
    Currently we are in state unable to do anything.
    Was using a database and all of a sudden it crashed. Tried to mount the database, open it, it failed. Also tried the recover and alter database open, even that failed. Errors are as follows.
    Errors in file e:\oracle\product\10.2.0 \admin\devrevdb\bdump\devrevdb_p000_2620.trc:
    ORA-00603: ORACLE server session terminated by fatal error
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    ORA-00449: background process 'DBW0' unexpectedly terminated with error 1242
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    In my spfile, the administrator has set only two control files and there is no mirroring and hence do not have another control file that will help me boot the db.
    Please let me know how I should go about it. I am only a timebeing person trying to carryout a db activity. Any help would be of great help.

    Hemant,
    thanks for the reply.
    I tried the way you suggested and it threw an error.
    ORA-01145: offline immediate disallowed unless media recovery enabled
    I searched and found that an additional tag of drop needs to be added to the command which you suggested.
    ALTER DATABASE DATAFILE '<filename>' OFFLINE DROP.
    i don't know what will the drop command have an effect ?
    i have copied the data file to another location. Since i don't know much, i just want to be sure of what im doing.
    if the above command is successfull, will it drop the datafile or the tablespace and i can no more use it. How can i use the copied datafile.
    Thanks,
    Sachin
    I

  • Recover database in NOarchivelog mode :)

    Hi all. How to recover a database wich is in noarchivelog mode? B-)
    Suppose,
    I have 3 redolog groups (with two members in each, the second members are located on another drive ). When first redo log group was 1/2 full I took a full backup. Then there were 2 switches from first to second and from second to third. Now the currnet redolog group - 3 (just started). At this point we faced media failer. How to roll forward changes using backup + online redologs?
    Edited by: Junior Oracle DBA on Oct 16, 2008 1:53 PM

    Restore your database cold backup (excluding redo logs).
    Then issue this command :
    RECOVER DATABASE USING BACKUP CONTROLFILE
    provide the names of the last ACTIVE / CURRENT Redo Logs in the database when Oracle prompts for an ArchiveLog.
    When Oracle has finished recovery to a consistent point in time, it will return to the command prompt without any error.
    Now issue this command :
    ALTER DATABASE OPEN RESETLOGS
    You would have a Complete Recovery.
    This is provided that Oracle had NOT cycled through all the Online Redo Logs since the time when the Cold Backup was taken. (If Oracle had cycled through all the Online Redo Logs, it would have overwrriten the oldest log because it wasn't in ArchiveLog mode).
    Hemant K Chitale
    http://hemantoracledba.blogspot.com

  • Changing database to noarchivelog mode during impdp

    Hi Guys,
    I am using Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit Production on RHEL5.
    I am in the middle on the impdp and I want my database to run on noarchivelog as it creates a lot of archivelogs.
    Will it be proper if I stop the import:
    e.g Import> STOP_JOB=IMMEDIATE
    and shutdown the database put the database on noarchivelog mode.
    then opne database and
    impdp hr/hr@mydb ATTACH=myfulljob Will these work fine?
    Or should I execute:
    alter system archive log stop;
    Please Help !!!!!!!!!!!

    Vinod Dhandapani wrote:
    Running the database in Noarchivelog mode means you should be ready to lose data incase there is any crash. I would recommend you to change the size of the redologs so that it will not create frequent archivelogs. Which does nothing about the space required for the archivelogs. If you are generating redo at the rate of 1gb/hour, you will consume archivelog dest space at the rate of 1gb/hour. Doesn't matter if those files are 10mb each or 100mb each.
    If space is the problem then use a shell script to move the archivelog to another location (Tape)....And hopefully that shell script is invoking rman to do the work, so that in the event of recovery, rman will know that backups were taken and where they are located.
    >
    Incase you want to convert the database from archivelog to noarchivelog, follow the steps provided in the following link.
    http://racadmin.blogspot.com/2011/06/convert-archivelog-mode-to-noarchivelog.html
    Thanks

  • ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode

    Hi All
    Its my first time to use RMAN in our ERP EBSR12
    our database version is 11g
    Please help how to resolv and make successfully backup
    RMAN> backup database;
    Starting backup at 24-JAN-11
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 01/24/2011 11:18: 25
    ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
    continuing other job steps, job failed will not be re-run
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    including current control file in backup set
    channel ORA_DISK_1: starting piece 1 at 24-JAN-11
    channel ORA_DISK_1: finished piece 1 at 24-JAN-11
    piece handle=/oracle/mybackup_db/PROD2/backupset/2011_01_24/o1_mf_ncnnf_TAG20110 124T111824_6msvw4cv_.bkp tag=TAG20110124T111824 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 01/24/2011 11:18: 25
    ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
    RMAN>
    Thanks

    ORA-19602: cannot backup or copy active file in NOARCHIVELOG modeIs your database in archivelog or noarchivelog mode?
    How to Turn Archiving ON and OFF [ID 69739.1]
    Please also see these docs/links.
    ORA-19602 Using RMAN to Backup Database [ID 246183.1]
    COLD RMAN backup fails: Ora-19602 even after SHUTDOWN IMMEDIATE and STARTUP MOUNT [ID 373828.1]
    Backup & Recovery
    http://www.oracle.com/pls/db112/portal.portal_db?selected=14&frame=#backup_and_recovery
    Thanks,
    Hussein

  • 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

  • How to recover a PDB in noarchivelog mode?

    Hi all,
    Urgent! We have a PDB currently in mount stage after restoring and recovering from backup. Whenever I tried to open it or recover data file, I keep getting this error message:
    Errors in file C:\ORACLE\diag\rdbms\us022348\us022348\trace\us022348_p000_8788.trc:
    ORA-01113: file 9 needs media recovery
    ORA-01110: data file 9: 'D:\ORADATA\12C\US022348\0FB7D663771D443E8DE2229B76E0DCA7\DATAFILE\O1_MF_USERS_B2TVTBL1_.DBF'
    The CDB and PDB both are in noarchivelog modes.
    Which command should I use to bring the database back?
    Thanks!!

    I tried these but no luck.
    RMAN> alter pluggable database PDBNAME open;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of sql statement command at 12/15/2014 14:10:49
    ORA-01113: file 9 needs media recovery
    ORA-01110: data file 9: 'D:\ORADATA\12C\US022348\0FB7D663771D443E8DE2229B76E0DCA7\DATAFILE\O1_MF_USERS_B2TVTBL1_.DBF'
    RMAN> alter pluggable database PDBNAME open resetlogs;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of sql statement command at 12/15/2014 14:11:05
    ORA-39862: RESETLOGS option only valid after a Pluggable Database incomplete recovery

Maybe you are looking for