Recovery/db copy + archive logs

Hi champions,
There is one confusion in recovery of a database. Version 10g.
I have a hot backup (using copy command) of a database(archive log mode) which I’ve taken at 22.00.00 on Sunday.
Now my database is up and running Monday,Tuesday,Wednesday in archive log mode.I have all the archive logs since the last backup(Sunday 22.00) .and my database got crashed on Wednesday 14.00 completely lost everything (CDR files) only archive logs are with me...
Can i recover my database using Sunday’s backup + archive log till the time it crashed.
Regards,
Shitesh Shukla

Shukla Shitesh wrote:
Hi champions,
There is one confusion in recovery of a database. Version 10g.
I have a hot backup (using copy command) of a database(archive log mode) which I’ve taken at 22.00.00 on Sunday.
Now my database is up and running Monday,Tuesday,Wednesday in archive log mode.I have all the archive logs since the last backup(Sunday 22.00) .and my database got crashed on Wednesday 14.00 completely lost everything (CDR files) only archive logs are with me...
Can i recover my database using Sunday’s backup + archive log till the time it crashed.
Regards,
Shitesh ShuklaDear Shitesh, you can recover the database by applying all/any archived redo log files you have.
My Oracle Video Tutorials - http://kamranagayev.wordpress.com/oracle-video-tutorials/

Similar Messages

RMAN-06054: media recovery requesting unknown archived log

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/16/2013 09:03:43
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 34751 and starting SCN of 8923445274I am receiving the error above on performing RMAN Active cloning, please advise how to resolve this

In addition to what was said, I can think of two other possibilities for RMAN-6054 during duplicate: bugs such as 12625205 (also see 8554110); duplicate was run earlier without removing the old restored files (Note 1549172.1). In the first case, just specify SCN or find the actual log file and speficy log sequence, instead of time. In the latter case, remove the old restored files or speficy noresume.
Edited by: user11989003 on May 29, 2013 10:17 AM

Need to copy archive log file "arch1_601.dbf" when restore database?

Hi all,
I have the following case:
1) Full hot backup today (Feb-12-2009) in directory /u03/db/backup
2) But ongoing archive log are generated in directory /u02/oracle/uat/uatdb/9.2.0/dbs
3) I need to restore database becuase some data files are missing.
4) Use today ful backup to restore
5) Am I need to copy all archive log files in /u02/oracle/uat/uatdb/9.2.0/dbs to /u03/db/backup because "/u03/db/backup/RMAN" is restore directory?
FAN

Here is backup scripts:
Run
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u02/db/backup/RMAN/%F.bck';
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
allocate channel ch1 type disk format '/u02/db/backup/RMAN/backup_%d_%t_%s_%p_%U.bck';
backup incremental level 1 cumulative database plus archivelog delete all input;
backup current controlfile;
backup spfile;
release channel ch1;
allocate channel for maintenance type disk;
delete noprompt obsolete;
delete noprompt archivelog all backed up 2 times to disk;

Recovery question using archive log

HPUX 11X
Oracle 10.2.0.2
I have a standby database that the customers want to test the ability to fail over. They also want to test the data integrity of the standby once it's brought on line as the primary.
I've already told the customer that any writes that they do on the standby during the test time WILL be lost. I plan on doing a incomplete recovery back to a specific sequence number / archive log when the tests are complete.
My plan is to take note of the current sequence number just before I bring the standby live. When all is said and done, I was going to do a recover back to the sequence number one PRIOR to that one. Then when I place the db back in standby mode, it will sync back up to the primary.
What I need to know is if this is a good or a bad idea. Should I plan on doing it differently and for what reason.
Thanks! :)

Use flashback database to recover the former primary database to a new standby.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/scenarios.htm#i1049997
Therefore the changes made on standby won't be lost (unless you want to lose them).
If your databases do not have Flashback Database feature enabled, you can use incomplete recovery instead.
I think Flashback Database should be your first option.

Copy archive log on remote server

Hi guys,
I have Oracle9i server installed on my local pc running on windows xp.
It's configured on Archive log mode. What I'm trying to do is to copy my archive log files to remote pc; and the location in which i want to save my archive log, i can open from my local pc. So, the following are the steps I made:
1 - Create backup of my spfile.
2- open initoradb01.ora which is the backup just created and edit on LOG_ARCHIVE_DEST = ' \\remotepc\orabkp\arch'
3 - STARTUP pfile='c:\initoradb01.ora'
The instance starts without any problem but when archiving is taken a place then the following error is returned
ERROR at line 1:
ORA-16038: log 1 sequence# 30 cannot be archived
ORA-19504: failed to create file ""
ORA-00312: online log 1 thread 1: 'C:\ORACLE9I_BASE\ORADATA\ORADB01\REDO01.LOG'
ORA-00312: online log 1 thread 1:
'C:\ORACLE9I_BASE\ORADATA\ORADB01\REDO01B.LOG'
When archive log location is changed to local pc, then no problem at all.
Would you guys tell me how to solve this problem?
thanks

There are some generic issues with mapped drives,pointed out in this metalink note:
How to Configure RMAN to Write to Shared Drives on Windows NT/2000
Doc ID: Note:145843.1
The basic story is you cannot use LocalSystem (which owns the Oracle processes by default) to write to mapped drives.
Werner

When occurs crash recovery,why use active online redo log not archived log?

If current redo log had archived, but it's still 'ACTIVE'. As we all know, archived log is just an archived copy of the current redo log which is still 'ACTIVE', they have the same data. But why use active online redo log not archived log for crash recovery?(I think, if crash recovery can use archived log, then whether the online redo log is 'ACTIVE' or not, it can be overwritten)
Quote:
Re: v$log : How redo log file can have a status ACTIVE and be already archived?
Hemant K Chitale
If your instance crashes, Oracle attempts Instance Recovery -- reading from the Online Redo Logs. It doesn't need ArchiveLogs for Instance Recovery.
TanelPoder
Whether the log is already archived or not doesn't matter here, when the instance crashes, Oracle needs some blocks from that redolog. Archivelog is just an archived copy of the redolog, so you could use either the online or achive log for the recovery, it's the same data in there (Oracle reads the log/archivelog file header when it tries to use it for recovery and validates whether it contains the changes (RBA range) in it what it needs).

Aman.... wrote:
John,
Are you sure that the instance recovery (not the media recovery) would be using the archived redo logs? Since the only thing that would be lost is the isntance, there wouldn't be any archived redo log generated from the Current redo log and the previous archived redo logs, would be already checkpointed to the data file, IMHO archived redo logs won't participate in the instance recovery process. Yep, shall watch the video but tomorrow .
Regards
Aman....
That's what I said. Or meant to say. If Oracle used archivelogs for instance recovery, it would not be possible to recover in noarchive log mode. So recovery relies exclusively on the online log.
Sorry I wasted your time, I'll try to be less ambiguous in future

Error in second destincation of Archive log

i have both path for archive log in place one is flash recovery area where archive log are to be written and another path which in my other server.
I have created a folder in my test database and map this folder in Production database but i am doing alter system switch logfile, it only create archive on the first destination and not creating any file on second destination and giving error
ORA-19504: failed to create file ""

Actually i mount the folder of test server in my database, so that one archive copy will be saved in different storage for any disaster recovery
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 197
Next log sequence to archive 201
Current log sequence 201
SQL> show parameter db_recovery_file_dest;
NAME TYPE VALUE
db_recovery_file_dest string /home/u01/app/oracle/product/1
0.2.0/db_1/flash_recovery_area
db_recovery_file_dest_size big integer 15G
Following is the content of trace file mentioned
/home/u01/app/oracle/product/10.2.0/db_1/admin/db0/bdump/demeter_arc0_27244.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /home/u01/app/oracle/product/10.2.0/db_1
System name: Linux
Node name: db0
Release: 2.6.18-5-amd64
Version: #1 SMP Sat Dec 22 20:43:59 UTC 2007
Machine: x86_64
Instance name: db0
Redo thread mounted by this instance: 1
Oracle process number: 17
Unix process pid: 27244, image: oracle@db0 (ARC0)
*** 2008-04-23 11:19:13.799
*** SERVICE NAME:(SYS$BACKGROUND) 2008-04-23 11:19:13.799
*** SESSION ID:(210.1) 2008-04-23 11:19:13.799
Failed to create file '/home/archive-logs/1_198_645895824.dbf' (file not accessible?)
ORA-19504: Message 19504 not found; No message file for product=RDBMS, facility=ORA; arguments: [home/archive-logs/1_198_645895824.dbf]
ORA-27086: Message 27086 not found; No message file for product=RDBMS, facility=ORA
Linux-x86_64 Error: 5: Input/output error
Additional information: 9
Additional information: 5
*** 2008-04-23 11:19:13.799 61287 kcrr.c
ARC0: Error 19504 Creating archive log file to '/home/archive-logs/1_198_645895824.dbf'
*** 2008-04-23 11:19:13.799 59530 kcrr.c
kcrrfail: dest:2 err:19504 force:0 blast:1
*** 2008-04-23 11:35:42.553
Failed to create file '/home/archive-logs/1_200_645895824.dbf' (file not accessible?)
ORA-19504: Message 19504 not found; No message file for product=RDBMS, facility=ORA; arguments: [home/archive-logs/1_200_645895824.dbf]
ORA-27086: Message 27086 not found; No message file for product=RDBMS, facility=ORA
Linux-x86_64 Error: 5: Input/output error
Additional information: 9
Additional information: 5
*** 2008-04-23 11:35:42.553 61287 kcrr.c
ARC0: Error 19504 Creating archive log file to '/home/archive-logs/1_200_645895824.dbf'
*** 2008-04-23 11:35:42.553 59530 kcrr.c
kcrrfail: dest:2 err:19504 force:0 blast:1

Unable to find archived log

Hi
I am restoring a hot backup taken through RMAN using following commands:
configure controlfile autobackup on;
BACKUP DATABASE ;
BACKUP ARCHIVELOG ALL DELETE INPUT;
Now I am going to restore that using following commands:
restore spfile from autobackup;
restore controlfile from autobackup;
shutdown immediate;
startup mount;
restore database;
RECOVER DATABASE;
ALTER DATABASE OPEN RESETLOGS;
But it goes fine till restore database. At recover database I get following errors:
archived log for thread 1 with sequence 2461 is already on disk as file /u01/app/oracle/fast_recovery_area/XE/onlinelog/o1_mf_1_8fbs9bvt_.log
archived log for thread 1 with sequence 2462 is already on disk as file /u01/app/oracle/fast_recovery_area/XE/onlinelog/o1_mf_2_8fbs9chb_.log
unable to find archived log
archived log thread=1 sequence=545
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 09/11/2013 20:41:43
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 545 and starting SCN of 25891726
I have checked the backup folder and there are only empty date wise folders under archivedlog folders.
If I write RMAN> ALTER DATABASE OPEN RESETLOGS; I get:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 09/11/2013 20:43:01
ORA-01190: control file or data file 1 is from before the last RESETLOGS
ORA-01110: data file 1: '/u01/app/oracle/oradata/XE/system.dbf'
If I write RMAN> recover database until sequence 545; I get
Starting recover at 11-SEP-13
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=695 device type=DISK
starting media recovery
unable to find archived log
archived log thread=1 sequence=545
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 09/11/2013 21:09:34
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 545 and starting SCN of 25891726
I don't mind if some data is lost. Will be really thankful if someone can help me get my database open;
Habib

They way you are trying to recover will try to recover up to the last know SCN. Try to do a point in time recover up to a few minutes before the database was shutdown or crashed.
Try something like this
run{
set until time "to_date('2013-09-11:00:00:00', 'yyyy-mm-dd:hh24:mi:ss')";
restore spfile from autobackup;
restore controlfile from autobackup;
shutdown immediate;
startup mount;
restore database;
RECOVER DATABASE;
ALTER DATABASE OPEN RESETLOGS;

Change Archive Log Mode, Restart instance, show ORA-12505 error!!!

We are still use Oracle 9i.
Now we want to use Symantec Backupexec 12 to backup oracle 9i.
In accordance with Backupexec's requirements. must change recovery mode to Archive Log Mode.
I use the Enterprise manager console to change it. and select restart immediately.
a error message be display in the step 2 (starting up the database). see below
ORA-12505: TNS:listener could not resolve SID given in connect descriptor
I'm a new oracle user. Hope you give me some suggestion.
THK.

If database is down, then start it up directly login to server and
sqlplus "/ as sysdba"
startup;
Read this thread for first:
Re: ORA-12505, TNS:listener does not currently know of SID given in connect
The main problem is Your listner doesn't know the sid in connect descriptor.
Check
lsnrctl services
and look in tnsnames.ora file - is there such sercive defined in Your connection description.
issue tnsping in order to check is it able to read and connect correctly tnsnames.ora entry.

10gr2 standard edition standby question - archive log shipping

Hello,
I have 2 servers with 10gr2 standard edition, one is production(primary) and secondary is standby on windows platform. To keep standby synchronized i use a script to copy archived logs from primary to standby and applying manually (with scripts).
My question is: can i use redo transport service in order to copy archivelogs from primary to standby ?
Thank you in advance.

Hi,
It is a bit of topic.
According to the Licensing Document page 10 DataGuard is not supported for standard edition.
http://download.oracle.com/docs/cd/B28359_01/license.111/b28287.pdfRegards,
Tycho

Recovery window retention policy deletes archive logs before a backup?

Hi All,
Oracle 11G on Windows 2008 R2
This afternoon, I changed my RMAN retention policy from 'RETENTION POLICY REDUNDANCY 3' to RETENTION POLICY RECOVERY WINDOW OF 3 DAYS'
However, i checked tonight and after my daily backup ran, all the archive logs prior to the backup had been deleted! Thus meaning i dont think i can restore to any point in time, prior to my daily backup. All the .arc logs were there after the backup. So i tried another test and kicked off the daily backup again. During the backup process, the archive logs got deleted again! Now i don't have any archive logs..
Is this proper behaviour of RETENTION POLICY RECOVERY WINDOW?? I thought it would keep all the files needed for me to restore to any point in time for the previous 3 days. When i used REDUNDANCY, with my daily backups, it kept 3 days worth of backups+ archive logs so i could restore point-in-time to any point. How can i use RECOVERY WINDOW so that i can actually restore to any point-in-time for the 3 days??
I wanted to change to RECOVERY WINDOW since i read that by using REDUNDANCY it only keeps X copies of a backup (so if i ran the backup 3 times in a day, i would only have those 3).
Thanks in advance.

Hi All,
Here is the SHOW ALL output:
RMAN> show all;
RMAN configuration parameters for database with db_unique_name MMSPRD7 are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOA
D TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLE\DATABASE\ORA11G\DATABASE\SNCFM
MSPRD7.ORA'; # default
Here is the RMAN script:
Recovery Manager: Release 11.2.0.3.0 - Production on Mon Jan 20 23:03:12 2014
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: XXX (DBID=)
RMAN> CROSSCHECK ARCHIVELOG ALL;
2> CROSSCHECK BACKUPSET;
3> CROSSCHECK BACKUP;
4> CROSSCHECK COPY;
5> DELETE NOPROMPT EXPIRED ARCHIVELOG ALL;
6> DELETE NOPROMPT EXPIRED BACKUPSET;
7> DELETE NOPROMPT OBSOLETE;
8> BACKUP CURRENT CONTROLFILE;
9> BACKUP AS COMPRESSED BACKUPSET DATABASE PLUS ARCHIVELOG DELETE INPUT;
Also, not sure if you needed the whole RMAN output, but here is the deletion part:
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 3 days
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type                 Key    Completion Time    Filename/Handle
Backup Set           1392   15-JAN-14
Backup Piece       1392   15-JAN-14          F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_15\O1_MF_NNNDF_TAG20140115T190054_9FG89R8N_.BKP
Backup Set           1393   15-JAN-14
Backup Piece       1393   15-JAN-14          F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_15\O1_MF_ANNNN_TAG20140115T192204_9FG9KDHX_.BKP
Backup Set           1397   16-JAN-14
Backup Piece       1397   16-JAN-14          F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_16\O1_MF_ANNNN_TAG20140116T190027_9FJWNW6L_.BKP
Backup Set           1400   17-JAN-14
Backup Piece       1400   17-JAN-14          F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_17\O1_MF_ANNNN_TAG20140117T190138_9FMK349M_.BKP
deleted backup piece
backup piece handle=F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_15\O1_MF_NNNDF_TAG20140115T190054_9FG89R8N_.BKP RECID=1392 STAMP=836938856
deleted backup piece
backup piece handle=F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_15\O1_MF_ANNNN_TAG20140115T192204_9FG9KDHX_.BKP RECID=1393 STAMP=836940124
deleted backup piece
backup piece handle=F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_16\O1_MF_ANNNN_TAG20140116T190027_9FJWNW6L_.BKP RECID=1397 STAMP=837025228
deleted backup piece
backup piece handle=F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_17\O1_MF_ANNNN_TAG20140117T190138_9FMK349M_.BKP RECID=1400 STAMP=837111700
Deleted 4 objects

RMAN: How to apply Archive Logs after recoverying of all physical files

Hi;
I am using RMAN Oracle10g; my test database has being corrupted. I have already taken 0 level backup through this command
run {
allocate channel c1 type disk;
backup incremental level 0 tag = Test_Weekly_database format 'O:\rman\backup\Full_Weekly_%d_%s_%p_%t'(database);
release channel c1;
configure controlfile autobackup format for device type disk to 'O:\rman\backup\Auto_Ctrl_weekly_%F';
allocate channel c1 type disk;
sql 'alter system archive log current';
BACKUP tag = Test_Weekly_Arch ARCHIVELOG UNTIL TIME 'SYSDATE-7' format 'O:\rman\backup\Archive_weekly_%d_%s_%p_%t';
DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
release channel c1;
After backing up I inserted few records in TEST123 table. And switch current log file.
Then my database has been corrupted. Now I have last 0 level backup (RMAN) and archive logs files on OS level.
I am recovering my database with the following commands; but archive logs have not being applied. And my inserted records were not presented in TEST123 table.
Kindly guide me
SQL> startup nomount
CMD> RMAN target=/
RMAN>set DBID 1168995671
RMAN>RUN {
SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'O:\rman\backup\Auto_Ctrl_weekly_%F';
RESTORE CONTROLFILE from autobackup;
RMAN> ALTER DATABASE MOUNT;
RMAN> RESTORE DATABASE CHECK READONLY;
RMAN> RECOVER DATABASE NOREDO;
RMAN> restore archivelog all;
SQL> startup mount
SQL> alter database backup controlfile to trace;
SQL> shut immediate
SQL> startup nomount
SQL> CREATE CONTROLFILE REUSE DATABASE "ORCL" RESETLOGS ARCHIVELOG................;
SQL> alter database open resetlogs
---Database altered.
SQL> select * from TEST123;
Not record found
regards;
Asim

Dear Khurram;
Kindly advise where i m worrg???????
C:\>RMAN target=/
RMAN> set DBID 1168995671
executing command: SET DBID
RMAN> RUN {
2> SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'O:\rman\backup\Auto_Ctrl_weekly_%F';
3> RESTORE CONTROLFILE from autobackup;
4> }
executing command: SET CONTROLFILE AUTOBACKUP FORMAT
Starting restore at 27-DEC-07
using channel ORA_DISK_1
recovery area destination: O:\rman\backup
database name (or database unique name) used for search: ORCL
channel ORA_DISK_1: no autobackups found in the recovery area
channel ORA_DISK_1: looking for autobackup on day: 20071227
channel ORA_DISK_1: autobackup found: O:\rman\backup\Auto_Ctrl_weekly_c-11689956
71-20071227-04
channel ORA_DISK_1: control file restore from autobackup complete
output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL01.CTL
output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL02.CTL
output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL03.CTL
Finished restore at 27-DEC-07
RMAN> ALTER DATABASE MOUNT;
database mounted
released channel: ORA_DISK_1
RMAN> RESTORE DATABASE CHECK READONLY;
Starting restore at 27-DEC-07
Starting implicit crosscheck backup at 27-DEC-07
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=155 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=154 devtype=DISK
Crosschecked 9 objects
Finished implicit crosscheck backup at 27-DEC-07
Starting implicit crosscheck copy at 27-DEC-07
using channel ORA_DISK_1
using channel ORA_DISK_2
Finished implicit crosscheck copy at 27-DEC-07
searching for all files in the recovery area
cataloging files...
no files cataloged
using channel ORA_DISK_1
using channel ORA_DISK_2
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF
restoring datafile 00002 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\UNDOTBS01.DBF
restoring datafile 00003 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSAUX01.DBF
restoring datafile 00004 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\USERS01.DBF
restoring datafile 00005 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\TEST.DBF
restoring datafile 00006 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\TEST2
channel ORA_DISK_1: reading from backup piece O:\RMAN\BACKUP\FULL_WEEKLY_ORCL_3_
1_642420573
channel ORA_DISK_1: restored backup piece 1
piece handle=O:\RMAN\BACKUP\FULL_WEEKLY_ORCL_3_1_642420573 tag=Test_WEEKLY_DATAB
ASE
channel ORA_DISK_1: restore complete, elapsed time: 00:00:46
Finished restore at 27-DEC-07
RMAN> restore archivelog all;
archive log thread 1 sequence 1 is already on disk as file O:\ARCHIVE\ARC00001_0642356125.001
archive log thread 1 sequence 2 is already on disk as file O:\ARCHIVE\ARC00002_0642356125.001
archive log thread 1 sequence 3 is already on disk as file O:\ARCHIVE\ARC00003_0642356125.001
archive log thread 1 sequence 4 is already on disk as file O:\ARCHIVE\ARC00004_0642356125.001
archive log thread 1 sequence 5 is already on disk as file O:\ARCHIVE\ARC00005_0642356125.001
archive log thread 1 sequence 6 is already on disk as file O:\ARCHIVE\ARC00006_0642356125.001
archive log thread 1 sequence 7 is already on disk as file O:\ARCHIVE\ARC00007_0642356125.001
archive log thread 1 sequence 8 is already on disk as file O:\ARCHIVE\ARC00008_0642356125.001
archive log thread 1 sequence 9 is already on disk as file O:\ARCHIVE\ARC00009_0642356125.001
archive log thread 1 sequence 10 is already on disk as file O:\ARCHIVE\ARC00010_0642356125.001
archive log thread 1 sequence 11 is already on disk as file O:\ARCHIVE\ARC00011_0642356125.001
archive log thread 1 sequence 12 is already on disk as file O:\ARCHIVE\ARC00012_0642356125.001
channel ORA_DISK_1: starting archive log restore to default destination
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=15
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=16
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=17
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=18
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=19
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=20
channel ORA_DISK_1: reading from backup piece O:\RMAN\BACKUP\ARCHIVE_WEEKLY_ORCL_5_1_642420630
channel ORA_DISK_1: restored backup piece 1
piece handle=O:\RMAN\BACKUP\ARCHIVE_WEEKLY_ORCL_5_1_642420630 tag=Test_WEEKLY_ARCH
channel ORA_DISK_1: restore complete, elapsed time: 00:00:08
Finished restore at 27-DEC-07
RMAN> ALTER DATABASE OPEN;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 12/27/2007 10:27:10
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF'
Regards;
Asim

Rman - rolling foward with archive logs during recovery

Database: 9.2.0.6; OS Windows 2003, Rman Backups performed through OEM 10g.
I have been a long time "write your own scripts" for backups but now I'm learning rman. Purchased the Oracle Database 10g RMAN Backup and Recovery book, but it doesn't have all the answers.
I have previously recovered a database using my "scripts" and rolled the database forward using archive files, but how is this done with rman? Rman seems to rely on the control file and backup pieces, where the scripts allowed me to just specify "recover database until cancel".
I have successfully recovered a database. It stopped once it could no longer find the next scn number. I then thought I could copy over the archive logs I have and try it again, try to roll forward, however, during the recover process there were two archive files created which were the next sequence, so I have dupes.
How do I perform a recover, and apply any archives which were not part of the rman backup?
The following is what I performed. I copied all my rman backup pieces to a new server. I created a clone of the directory structure,
oradim -new -sid <dbname>
orapwd file=<file_name> password=tiger
set oracle_sid=<dbname>
rman target /
startup force nomount
restore spfile from <file_name>
shutdown immediate
startup nomount
restore controlfile from <file_name>
restore database
-- NOTE: It ran and then stopped when it could no longer file the next log sequence
alter database reset logs;
The database opened and I can access it, but I really need to roll the logs forward.
thanks in advance.

If these are archive logs that RMAN doesn't know about, you'll need to CATALOG these archivelogs before RMAN can use them.

Recovery using Full BCV backup & archive logs

Hello DBA's ,
I have Last Sunday's Full BCV (Buisness Copy Volume) backup (i.e. ..... the tablespaces were taken into Backup mode then Sync the BCV, then split the BCV , take the backup of BCV and take the tabespaces in normal mode in short what we call as HOT BACKUP ........ ) & also I am taking only archive log & control file backup Daily.
Now I want to Run my database on Different Server using the above FULL BCV & daily backed up Archive logs & Control file.
Kindly update me- Can I go for following recovery steps for above scenario.
1) Install ORACLE software on new server.
2) Restore the last Sunday's FULL BCV (Hot backup)
3) Restore the archive log from last Sunday's Full BCV backup.
4) Restore the latest backed up control file.
5) Mount the database.
6) Recover the database using backed up control file & archive logs.
7) Open the database with RESETLOGS option.
Please Guide me whether I can Fully Recover/Start database on this new server using above steps. ---OR---- " Are there any more files except data files that need to be backed up daily after Full BCV ? " ---OR ---- More suggestions are Welcome.
I want to test this scenario bcz.
a) I can't afford daily BCV due to lack of storage with current retention given by buisness.
b) I can't afford long time taken by RMAN for backup & recovery, as it disturbs my other backup shedules, also RTO should be very low as per my buisness requirement.
c) Currently we are not thinking for any another Backup options.
OS platform -- SOLARIS 10
Database version -- ORACLE 9i/10g
Atul.

Hello everybody ....
Actually I am doing the above scenario practically and I am facing the problem that when I am applying my archive logs using backup controlfile until cancel, the recovery completes upto the available Archive logs/sequence. But it throws the following error along with it ......
ORA-00279: change 7001791222 generated at 01/13/2008 07:23:42 needed for thread
1
ORA-00289: suggestion : /oracle/EPR/oraarch/1_9623_601570270.dbf
ORA-00280: change 7001791222 for thread 1 is in sequence #9623
ORA-00278: log file '/oracle/EPR/oraarch/1_9622_601570270.dbf' no longer needed
for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 7001816252 generated at 01/13/2008 12:53:05 needed for thread
1
ORA-00289: suggestion : /oracle/EPR/oraarch/1_9624_601570270.dbf
ORA-00280: change 7001816252 for thread 1 is in sequence #9624
ORA-00278: log file '/oracle/EPR/oraarch/1_9623_601570270.dbf' no longer needed
for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log '/oracle/EPR/oraarch/1_9624_601570270.dbf'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oracle/EPR/sapdata1/system_1/system.data1'
SQL> SQL> SQL> SQL> SQL> SQL> SQL>
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/EPR/sapdata1/system_1/system.data1'
So, I opened my database using Last (Sunday's) full hot backup only and it opens successfully without applying any archives.
Now, my question is... why my database doesn't open with OPEN RESETLOGS option when I am recovering it using command " RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE; "
I want to recover my database upto Saturday then What should I do ?
Please help me out !
Atul.

Changing the location of archive log from flash recovery area PLZ HELP!!!

Hi All,
My archive log is being stored in flash memory area which got full and the production server went down.
alert log file details.....
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 43432960 bytes disk space from 2147483648 limit
*** 2010-04-25 14:22:49.777 62692 kcrr.c
ARCH: Error 19809 Creating archive log file to
'/oracle/product/10.2.0/flash_rec
overy_area/EDWREP/archivelog/2010_04_25/o1_mf_1_232_%u_.arc'
*** 2010-04-25 14:22:49.777 60970 kcrr.c
kcrrfail: dest:10 err:19809 force:0 blast:1I removed the files and started the database,
Can someone kindly tell me as to how to avoid this problem in future by keeping archive log destination in flash recovery area.
I want to change the location of archive log files, can someone please guide me as to hiow to do that
I changed the size of flash recovery area for the time being, but i am afraid it will be full again!!
SQL> select * from v$flash_recovery_area_usage;
FILE_TYPE    PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
CONTROLFILE                   0                         0               0
ONLINELOG                     0                         0               0
ARCHIVELOG                99.44                         0              57
BACKUPPIECE                   0                         0               0
IMAGECOPY                     0                         0               0
FLASHBACKLOG                  0                         0               0
6 rows selected.
SQL> alter system set DB_RECOVERY_FILE_DEST_SIZE = 4G ;
System altered.
SQL> select * from v$flash_recovery_area_usage;
FILE_TYPE    PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
CONTROLFILE                   0                         0               0
ONLINELOG                     0                         0               0
ARCHIVELOG                49.72                         0              57
BACKUPPIECE                   0                         0               0
IMAGECOPY                     0                         0               0
FLASHBACKLOG                  0                         0               0
6 rows selected.regards,
Edited by: user10243788 on Apr 25, 2010 6:12 AM

user10243788 wrote:
Hi All,
My archive log is being stored in flash memory area which got full and the production server went down.
alert log file details.....
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 43432960 bytes disk space from 2147483648 limit
*** 2010-04-25 14:22:49.777 62692 kcrr.c
ARCH: Error 19809 Creating archive log file to
'/oracle/product/10.2.0/flash_rec
overy_area/EDWREP/archivelog/2010_04_25/o1_mf_1_232_%u_.arc'
*** 2010-04-25 14:22:49.777 60970 kcrr.c
kcrrfail: dest:10 err:19809 force:0 blast:1I removed the files and started the database,
Can someone kindly tell me as to how to avoid this problem in future by keeping archive log destination in flash recovery area.
I want to change the location of archive log files, can someone please guide me as to hiow to do that
I changed the size of flash recovery area for the time being, but i am afraid it will be full again!!
SQL> select * from v$flash_recovery_area_usage;
FILE_TYPE    PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
CONTROLFILE                   0                         0               0
ONLINELOG                     0                         0               0
ARCHIVELOG                99.44                         0              57
BACKUPPIECE                   0                         0               0
IMAGECOPY                     0                         0               0
FLASHBACKLOG                  0                         0               0
6 rows selected.
SQL> alter system set DB_RECOVERY_FILE_DEST_SIZE = 4G ;
System altered.
SQL> select * from v$flash_recovery_area_usage;
FILE_TYPE    PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
CONTROLFILE                   0                         0               0
ONLINELOG                     0                         0               0
ARCHIVELOG                49.72                         0              57
BACKUPPIECE                   0                         0               0
IMAGECOPY                     0                         0               0
FLASHBACKLOG                  0                         0               0
6 rows selected.regards,
Edited by: user10243788 on Apr 25, 2010 6:12 AMPointing the archive log dest (and/or the FRA) to a new location, or enlarging them, will do no good if you are not performing regular housekeeping on the archivelogs. You will just keep knocking down the same problem over and over.
If you simply delete the archivelogs at the OS level, the database will never know about it and it will continue to think the destination is full, based on records kept in the control file.
For regular housekeeping, you need to be doing something similar to this in rman:
run {
backup archivelog all not backed up 1 times tag='bkup_vlnxora1_arch';
delete noprompt archivelog all backed up 1 times to device type disk;
run {
delete noprompt obsolete;
crosscheck archivelog all;
delete noprompt expired archivelog all;

Recovery/db copy + archive logs

Similar Messages

Maybe you are looking for