RMAN- unable to find archive log

Hi All,
I am facing this problem while i am recovering my database. I have checked this archive file and it is present on the location where it should be. So what can be the solution.
Pls help...
Thanks and Regards
Amit Raghuvanshi

Hi Dear,
The location is on the disk and the error is...
released channel: ORA_DISK_1
allocated channel: dev2
channel dev2: sid=12 devtype=DISK
Starting recover at 08-AUG-07
starting media recovery
archive log thread 1 sequence 54266 is already on disk as file /erpp/erppdata/log01a.dbf
archive log thread 1 sequence 54267 is already on disk as file /erpp/erppdata/log02a.dbf
unable to find archive log
archive log thread=1 sequence=54259
released channel: dev2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/08/2007 11:33:57
RMAN-06054: media recovery requesting unknown log: thread 1 scn 5965732883373
Regards
Amit Raghuvanshi

Similar Messages

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;

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-08591: WARNING: invalid archived log deletion policy

Hi,
My database is 11.2.0.1 running on OEL 5.
We have stndby database running on other server, i have configured rman like this
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
But while running db backup, getting the error
RMAN-08591: WARNING: invalid archived log deletion policy.
RMAN retention policy is set to redundancy 1.
The archive files are deleting even though they are not applied on standby.
Thanks,

kkrm333 wrote:
Hi,
My database is 11.2.0.1 running on OEL 5.
We have stndby database running on other server, i have configured rman like this
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
But while running db backup, getting the error
RMAN-08591: WARNING: invalid archived log deletion policy.
RMAN retention policy is set to redundancy 1.
The archive files are deleting even though they are not applied on standby.
Thanks,
bcm@bcm-laptop:~$ oerr rman 8591
8591, 3, "WARNING: invalid archived log deletion policy"
// *Cause: An invalid ARCHIVELOG DELETION POLICY was supplied. The archived
//         log deletion policy was APPLIED but there was no mandatory
//         archived log destinations.
// *Action: One of the following:
//          1) Change archived log deletion policy using CONFIGURE command
//          2) Make one or more of standby destination as MANDATORY.

How do I setup RMAN not to delete archive log files on the source database so GoldenGate can process DDL/DML changes?

I want to setup RMAN not to delete any archive log files that will be used by GoldenGate.   Once GoldenGate is completed with the archive log file, the archive log file can be backup and deleted by RMAN.   It's my understanding that I can issue the following command "REGISTER EXTRACT <ext_name>, LOGRETENTION" to enable to functionally.   Is this the only thing I need to do to execute to enable this functionally?

Hello,
Yes this is the rigth way using clasic capture.
Using the command : REGISTER EXTRACT Extract_name LOGRETENTION.
Create a Oracle Streams Group Capture (Artificial) that prevent RMAN archive deletion if these are pending to process for Golden Gate capture process.
You can see this integration doing a SELECT * FROM DBA_CAPTURE; after execute the register command.
Then, when RMAN try to delete a archive file pending to process for GG this warning appear AT RMAN logs:
Error:     RMAN 8317 (RMAN-08317 RMAN-8317)
Text:     WARNING: archived log not deleted, needed for standby or upstream capture process.
Then , this is a good manageability feature. I think is a 11.1 GG new feature.
Tip. To avoid RMAN backup multiples times a archive pending to process, there is a option called BACKUP archivelog not backed 1 times.
If you remove a Capture process that is registered with the database you need to use this comand to remove the streams capture group:
unREGISTER EXTRACT extract_name LOGRETENTION;
Then if you query dba_capture, the artificial Streams group is deleted.
I hope help.
Regards
Arturo

Are there any possible reason RMAN generates some corrupt archive log files

Dear all,
Are there any possible reason RMAN generates some corrupt archive log files?
Best Regards,
Amy

Because I try to perform daily backup at lunch time and found out it takes more than 1 hour had no any progress. Normally we take around 40 minus. The following is the log file:
RMAN> Run
2> {
3> CONFIGURE CONTROLFILE AUTOBACKUP ON;
4> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u03/db/backup/RMAN/%F.bck';
5> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
6> allocate channel ch1 type disk format '/u03/db/backup/RMAN/backup_%d_%t_%s_%p_%U.bck';
7> backup incremental level 1 cumulative database plus archivelog delete all input;
8> backup current controlfile;
9> backup spfile;
10> release channel ch1;
11> }
12> allocate channel for maintenance type disk;
13> delete noprompt obsolete;
14> delete noprompt archivelog all backed up 2 times to disk;
15>
16>
using target database controlfile instead of recovery catalog
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters are successfully stored
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u03/db/backup/RMAN/%F.bck';
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u03/db/backup/RMAN/%F.bck';
new RMAN configuration parameters are successfully stored
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
new RMAN configuration parameters are successfully stored
allocated channel: ch1
channel ch1: sid=99 devtype=DISK
Starting backup at 31-MAR-09
current log archived
After that I go to archive log directory "/u02/oracle/uat/uatdb/9.2.0/dbs" and use ls -lt command to see how many archive logs and my screen just hang. After we found out that we cannot use ls -lt command to read arch1_171.dbf
archive log, the rest of archive logs able to use ls -lt command.
We cannot delete this file as well. We shutdown database abort and perform check disk...... and fix the disk error and then open database again. Everything seems back to normal and we can use ls -lt command to read arch1_171.dbf.
The strange problem is we have the same problem in Development and Production..... one ore more archive logs seems to be corrupted under the same directories /u02/oracle/uat/uatdb/9.2.0/dbs.
Does anyone encounter the same problem?
Amy

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.

RMAN,Data Guard and Archive log deletion

Our DG environment is running Oracle 11g R2
we have a 3 node DG environment with
A being the Primary
B and C being Active Data Guard Standbys
Backups are taken off of B and go directly to tape.
Standby Redo Logs and Fast Recovery Area are being used
Taking recommendation from "Using Recovery Manager with Oracle Data Guard in Oracle Database 10g"
RMAN Setting on Primary ("A")
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY
RMAN Setting on Standby ("B") where Backup is done
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE
RMAN Setting on other Standby ("C")
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY
How can we know what archive logs are eligible to be deleted from "A" and "C" ?
When does the delete take place?
How can we tell when the archive logs are being deleted from "A" and "C" ?

Dear user10260925,
The documentation that you have read is reliable but insufficient.
The Oracle can manage the archivelog directory and knows which one is eligible for the deletion. Those stuff you have posted in here has been taken from the online documentation and is supported and can be used when the Oracle knows and manages the archivelogs. That is simply called the flash recovery area. Please read about the FRA in this very moment.
Under normal circumstances people in the industry uses some scripts to achive the archivelog deletion on the standby system.
Here is a useful example to you;
# Remove old archivelogs
00,30 * * * * /home/oracle/scripts/delete_applied_redo_logs_OPTSTBY.sh
vals3:/home/oracle#cat /home/oracle/scripts/delete_applied_redo_logs_OPTSTBY.sh
export ORACLE_SID=optstby
export ORACLE_HOME=/oracle/product/10.2.0/db_1
cd /db/optima/archive/OPTPROD/archivelog
/oracle/product/10.2.0/db_1/bin/sqlplus "/ as sysdba" @delete_applied_redo_logs.sql
grep arc delete_applied_redo_logs.lst > delete_applied_redo_logs_1.sh
chmod 755 delete_applied_redo_logs_1.sh
sh delete_applied_redo_logs_1.sh
rm delete_applied_redo_logs_1.sh
rm delete_applied_redo_logs.lst
vals3:/home/oracle#cd /db/optima/archive/OPTPROD/archivelog
vals3:/db/optima/archive/OPTPROD/archivelog#cat delete_applied_redo_logs.sql
set echo off
set heading off
spool /db/optima/archive/OPTPROD/archivelog/delete_applied_redo_logs.lst
select 'rm -f ' || name from v$archived_log where applied = 'YES';
spool off
exit
vals3:/db/optima/archive/OPTPROD/archivelog#Hope That Helps.
Ogan

Unable to delete archive log.

Hi,
Our database server's archive log destination is full,but after running
backup archivelog all delete input;
it's taking archive log backup,but not deleting archivelogs.
Could you suggest me what is the reason.

RMAN> backup archivelog all delete input;
Starting backup at 17-DEC-10
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=155 recid=422 stamp=737092752
input archive log thread=1 sequence=156 recid=425 stamp=737156432
input archive log thread=1 sequence=157 recid=428 stamp=737257293
input archive log thread=1 sequence=158 recid=431 stamp=737322402
input archive log thread=1 sequence=159 recid=434 stamp=737389991
input archive log thread=1 sequence=160 recid=437 stamp=737408597
input archive log thread=1 sequence=161 recid=440 stamp=737476660
input archive log thread=1 sequence=162 recid=443 stamp=737542384
input archive log thread=1 sequence=163 recid=446 stamp=737634615
input archive log thread=1 sequence=164 recid=449 stamp=737658567
input archive log thread=1 sequence=165 recid=452 stamp=737726432
input archive log thread=1 sequence=166 recid=455 stamp=737827094
input archive log thread=1 sequence=167 recid=456 stamp=737860748
input archive log thread=1 sequence=168 recid=464 stamp=737980097
input archive log thread=1 sequence=169 recid=461 stamp=737980094
input archive log thread=1 sequence=170 recid=467 stamp=737980099
input archive log thread=1 sequence=171 recid=470 stamp=737980425
input archive log thread=1 sequence=172 recid=472 stamp=737981508
input archive log thread=1 sequence=173 recid=474 stamp=737985385
channel ORA_DISK_1: starting piece 1 at 17-DEC-10
channel ORA_DISK_1: finished piece 1 at 17-DEC-10
piece handle=D:\RMAN\BACKUP\0MLVPGRB_1_1 comment=NONE
channel ORA_DISK_1: starting piece 2 at 17-DEC-10
channel ORA_DISK_1: finished piece 2 at 17-DEC-10
piece handle=D:\RMAN\BACKUP\0MLVPGRB_2_1 comment=NONE
channel ORA_DISK_1: starting piece 3 at 17-DEC-10
channel ORA_DISK_1: finished piece 3 at 17-DEC-10
piece handle=D:\RMAN\BACKUP\0MLVPGRB_3_1 comment=NONE
channel ORA_DISK_1: starting piece 4 at 17-DEC-10
channel ORA_DISK_1: finished piece 4 at 17-DEC-10
piece handle=D:\RMAN\BACKUP\0MLVPGRB_4_1 comment=NONE
channel ORA_DISK_1: starting piece 5 at 17-DEC-10
channel ORA_DISK_1: finished piece 5 at 17-DEC-10
piece handle=D:\RMAN\BACKUP\0MLVPGRB_5_1 comment=NONE
channel ORA_DISK_1: starting piece 6 at 17-DEC-10
channel ORA_DISK_1: finished piece 6 at 17-DEC-10
piece handle=D:\RMAN\BACKUP\0MLVPGRB_6_1 comment=NONE
channel ORA_DISK_1: starting piece 7 at 17-DEC-10
channel ORA_DISK_1: finished piece 7 at 17-DEC-10
piece handle=D:\RMAN\BACKUP\0MLVPGRB_7_1 comment=NONE
channel ORA_DISK_1: starting piece 8 at 17-DEC-10
channel ORA_DISK_1: finished piece 8 at 17-DEC-10
piece handle=D:\RMAN\BACKUP\0MLVPGRB_8_1 comment=NONE
channel ORA_DISK_1: starting piece 9 at 17-DEC-10
channel ORA_DISK_1: finished piece 9 at 17-DEC-10
piece handle=D:\RMAN\BACKUP\0MLVPGRB_9_1 comment=NONE
channel ORA_DISK_1: starting piece 10 at 17-DEC-10
channel ORA_DISK_1: finished piece 10 at 17-DEC-10
piece handle=D:\RMAN\BACKUP\0MLVPGRB_10_1 comment=NONE
channel ORA_DISK_1: starting piece 11 at 17-DEC-10
channel ORA_DISK_1: finished piece 11 at 17-DEC-10
piece handle=D:\RMAN\BACKUP\0MLVPGRB_11_1 comment=NONE
channel ORA_DISK_1: starting piece 12 at 17-DEC-10
channel ORA_DISK_1: finished piece 12 at 17-DEC-10
piece handle=D:\RMAN\BACKUP\0MLVPGRB_12_1 comment=NONE
channel ORA_DISK_1: starting piece 13 at 17-DEC-10
channel ORA_DISK_1: finished piece 13 at 17-DEC-10
piece handle=D:\RMAN\BACKUP\0MLVPGRB_13_1 comment=NONE
channel ORA_DISK_1: starting piece 14 at 17-DEC-10
channel ORA_DISK_1: finished piece 14 at 17-DEC-10
piece handle=D:\RMAN\BACKUP\0MLVPGRB_14_1 comment=NONE
channel ORA_DISK_1: starting piece 15 at 17-DEC-10
channel ORA_DISK_1: finished piece 15 at 17-DEC-10
piece handle=D:\RMAN\BACKUP\0MLVPGRB_15_1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:03:41
channel ORA_DISK_1: deleting archive log(s)
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00155.001 recid=422 stamp=737
092752
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00156.001 recid=425 stamp=737
156432
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00157.001 recid=428 stamp=737
257293
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00158.001 recid=431 stamp=737
322402
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00159.001 recid=434 stamp=737
389991
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00160.001 recid=437 stamp=737
408597
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00161.001 recid=440 stamp=737
476660
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00162.001 recid=443 stamp=737
542384
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00163.001 recid=446 stamp=737
634615
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00164.001 recid=449 stamp=737
658567
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00165.001 recid=452 stamp=737
726432
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00166.001 recid=455 stamp=737
827094
archive log filename=D:\ORANT\ARCLOG1\REDO01.LOGARC00167.001 recid=456 stamp=737
860748
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00168.001 recid=464 stamp=737
980097
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00169.001 recid=461 stamp=737
980094
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00170.001 recid=467 stamp=737
980099
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00171.001 recid=470 stamp=737
980425
archive log filename=D:\ORANT\ARCLOG2\REDO02.LOGARC00172.001 recid=472 stamp=737
981508
archive log filename=D:\ORANT\ARCLOG1\REDO01.LOGARC00173.001 recid=474 stamp=737
985385
Finished backup at 17-DEC-10
Starting Control File and SPFILE Autobackup at 17-DEC-10
piece handle=D:\RMAN\BACKUP\C-1738882432-20101217-02 comment=NONE
Finished Control File and SPFILE Autobackup at 17-DEC-10

Unable to delete archive logs from primary

Dear DBAs,
I made the necessary configuration in RMAN at both site (primary and physical standby) as below:
on primary:
configure archivelog deletion policy to applied on standby;
alter system set "_log_deletion_policy"=ALL scope=spfile;
log_archive_dest_10=LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=ora10cs1
log_archive-dest_1=service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)
(HOST=LBLX-ORA10-SCS1)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=ora10scs1_XPT)(INSTANCE_NAME=ora10cs1)(SERVER=dedicated)))",
ARCH SYNC NOAFFIRM delay=0 OPTIONAL max_failure=0 max_connections=1 reopen=300 db_unique_name="ora10scs1" register net_timeout=180 valid_for=
(online_logfile,primary_role)
at standby:
configure archivelog deletion policy to none;
By the way i'm using Oracle 10gR2 patch4 on RHEL 5
and till now the database won't delete the archivelogs automaticaly, since the current available size in the flash folder is only 2MB.
Please waiting your advice
Thx in advance

Hi,
I have a different issue, I am not sure i can combine on the same thread.
From the DOC, this command is appeared to be useful. I am not sure if it can be applied to my environment.
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY
We have some databases with DG configuration on Sun. We take the backups only primary using RMAN online & archivelog alternate days. But, the archivelogs on standby are to be deleted every day manually (i mean we have a script scheduled for it).
Note: We use "delete input" on primary backup every day after they are backedup by RMAN. Anyway, the logs that are not applied on standby will not be deleted as RMAN is intelligent to keep them safe.
In the past we attempted to delete using rman script with the command shown below.
delete archivelog all completed before 'sysdate-2/24';
This causes a problem every time for us with regard to the primary database Backup as it expects the archivelogs on primay which were deleted by RMAN on standby. We had to crosscheck archivelog all every time to resolve the issue. There seems to be a mismatch of the archlog status both on primary and standby.
Please let me know if the above configuration command "CONFIGURE ARCHIVELOG DELETION POLICY " on both primary and standby or give an idea/steps what way i can use this.
Regards,
Vasu.
Edited by: vasu77 on Aug 31, 2009 4:02 PM
Edited by: vasu77 on Aug 31, 2009 4:05 PM
Edited by: vasu77 on Aug 31, 2009 4:10 PM

Is unable to write archive log fast enough the problem?

Oracle 10g:
I see very very long checkpoints in alert logs:
Mon Mar 23 12:35:57 2009
Beginning log switch checkpoint up to RBA [0x2001.2.10], SCN: 2667813010
Mon Mar 23 12:35:57 2009
Thread 1 advanced to log sequence 8193 (LGWR switch)
Current log# 3 seq# 8193 mem# 0: /u05/oradata/perf/redo03a.log
Current log# 3 seq# 8193 mem# 1: /u06/oradata/perf/redo03b.log
Mon Mar 23 12:41:02 2009
Completed checkpoint up to RBA [0x2001.2.10], SCN: 2667813010Our redo logs are 2gb and have 6 of those.
I am not sure why checkpoints are so long. Also, does this affect the requests trying to read-write to DB?
I am seeing high response time on our customer transactions when backup runs and one of the things I see is high checkpoints. But I am not sure if that would cause 20x high response time even though we do it at night time when the traffic is relatively low. There is something wrong and I am not sure if it's chekpoints, redo logs or something else.
Edited by: user628400 on Mar 23, 2009 5:50 PM
Edited by: user628400 on Mar 24, 2009 10:09 AM

Everything is indicating to me this is a big database.
My understanding, possilbly flawed, is to use a backup technique of spliting off the the third mirror the tablespaces should be put in backup mode before split, and out of backup mode after the split. (I believe this should be visible by entries in the alert log).
Whilst tablespaces are in backup mode extra redo will be generated, so it is important to check this time is minimized.
If data paths have been properly separated then there should only be a small blip in performance while the mirror split is occuring,
and possibly a drop when the third mirror is silverd back in.
The fact you are on a 3 way mirror backup design means you need to have documented the design and infrastucture of that set up and
ensure backup is documented and understood and monitored. This might also help pinpoint where in the process response times are increasing.
You might also try to monitor whether your disk access wait times are increasing during backups, or whether you have increased network latency.
(At abolute worst case in my opinion bad operation of this form of backup could lead to an unrecoverable database .... some system/backup admins might not appreciate this .... )
What could however be happening is while the third mirror is being backed up elsewhere that is causing contention between that backup and your databases access to storage.
This is all infrastructure dependent.
Slightly different topic what I mean was that the /uNN mounts may be filesystems set up by a volume manager, and may be on the same physical disk. Understanding the
3 way mirror backup takes priority over this.
In summary I suggest you seek all that is known about the design of your backup and its supporting documents. In your position I think I certainly would.
(It is past my bedtime and I may have veered off topic).
It is probably worth noting how often you switch redo logs and if that rate gets more frequent at certain times of day,
(ie graph when your redo logs were created and at what size).
Use Database Control / Grid Control to view AWR reports especially watching I/O quantity and waits overnight.
Before I forget it may be worth ensuring FAST_START_MTTR_TARGET is set to non zero value. (eg) 300s. This has an effect on incremental checkpointing.
Hope some of this helps - bigdelboy

Recover database but don't have archive log file

Hi
I use old backup set in tape and restore all datafile completed but I cannot recover that show below errror in RMAN
RMAN> recover database;
Starting recover at 08-SEP-09
using channel ORA_DISK_1
starting media recovery
unable to find archive log
archive log thread=1 sequence=29166
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 09/08/2009 21:49:36
RMAN-06054: media recovery requesting unknown log: thread 1 seq 29166 lowscn 1648727512
But in backup set and include archive log already that don't have seq 29166 that have last seg is 29165 when I tyr recover in sqlplus that show below error
SQL> recover database using backup controlfile;
ORA-00279: change 1648727512 generated at 09/05/2009 00:02:07 needed for thread
1
ORA-00289: suggestion : /oradata/archive/hrprd/1_29166_671345511.arc
ORA-00280: change 1648727512 for thread 1 is in sequence #29166
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log
'/oradata/archive/hrprd/1_29166_671345511.arc'
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 3
And I tried to open with reset log that show below error
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: '/oradata/data/hrprd/system01.dbf'
How can I do to open database?
Taohiko.

taohiko wrote:
Hi Werner
I tried and show below error
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 1648727512 generated at 09/05/2009 00:02:07 needed for thread
1
ORA-00289: suggestion : /oradata/archive/hrprd/1_29166_671345511.arc
ORA-00280: change 1648727512 for thread 1 is in sequence #29166
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
CANCEL
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: '/oradata/data/hrprd/system01.dbf'
ORA-01112: media recovery not started
How to do next step?
TaohikoHi Taohiko
Have you made backup of all archived redo log files? If so, why this one was disappeared?
Have you applied all archived redo log files before that required archived redo log file?
Please try to recover the database using the following command:
RMAN> RESTORE DATABASE;
RMAN> RECOVER DATABASE UNTIL SEQUENCE 29166;
RMAN>ALTER DATABASE OPEN RESETLOGS;

What order are Archive logs restored in when RMAN recover database issued

Ok, you have a run block that has restored your level-0 RMAN backup.
Your base datafiles are down on disc.
You are about to start recovery to point in time, lets say until this morning at 07:00am.
run { set until time "TO_DATE('2010/06/08_07:00:00','YYYY/MM/DD_HH24:MI:SS')";
allocate channel d1 type disk;
allocate channel d2 type disk;
allocate channel d3 type disk;
allocate channel d4 type disk;
recover database;
So the above runs, it analyses the earlies SCN required for recovery, checks for incremental backups (none here), works out the archivelog range
required and starts to restore the archive logs. All as expected and works.
My question: Is there a particular order that RMAN will restore the archive logs and is the restore / recover process implemented as per the run block.
i.e Will all required archive logs based on the run block be restored and then the database recovered forward. Or is there something in RMAN that says restore these archive logs, ok now roll forwards, restore some more.
When we were doing this the order of the archive logs coming back seemed to be random but obviously constrained by the run block. Is this an area we need to tune to get recoveries faster for situations where incrementals are not available?
Any inputs on experience welcome. I am now drilling into the documentation for any references there.
Thanks

Hi there, thanks for the response I checked this and here are the numbers / time stamps on an example:
This is from interpreting the list backup of archivelog commands.
Backupset = 122672
==============
Archive log sequence 120688 low time: 25th May 15:53:07 next time: 25th May 15:57:54
Piece1 pieceNumber=123368 9th June 04:10:38 <-- catalogued by us.
Piece2 pieceNumber=122673 25th May 16:05:18 <-- Original backup on production.
Backupset = 122677
==============
Archive log sequence 120683 low time: 25th May 15:27:50 Next time 25th May 15:32:24 <-- lower sequence number restored after above.
Piece1 PieceNumber=123372 9th June 04:11:34 <-- Catalogued by us.
Piece2 PieceNumber=122678 25th May 16:08:45 <-- Orignial backup on Production.
So the above would show that if catalogue command you could influence the Piece numbering. Therefore the restore order if like you say piece number is the key. I will need to review production as to why they were backed up in different order completed on production. Would think they would use the backupset numbering and then piece within the set / availability.
Question: You mention archive logs are restored and applied and deleted in batches if the volume of archivelogs is large enough to be spread over multiple backup sets. What determines the batches in terms of size / number?
Thanks for inputs. Answers some questions.

RMAN backup of archive logs

I am sort of new to RMAN, I've been playing with it for a while but that's about as far as I've taken it. My question is does RMAN automatically backup any archive logs needed for recovery when I run "backup database" command or do I have to issue "backup database plus archive log" in order to insure recovery.

Backup database also backups archivelogs.No,it does not. From documentation:
backup database;
Creates a backup set (AS BACKUPSET) or group of image copies (AS COPY) for all datafiles in the database. If generating a backup set, then RMAN can include only datafiles and control files: it cannot include archived redo logs.
Werner

Archived log validation without rman

one of my archived log is corrupted, is there any utility to check other archivelogs are fine? we are not using RMAN.

one of my archived log is corrupted, is there any
utility to check other archivelogs are fine? we are
not using RMAN.Unless you have a valid backup of corrupted archivelog. You can't recover your database past this archivelog, therefore if rest archivelog are valid or not is less important issue than recovering the one having problem.
Make sure you have archivelog saved on reliable media and if possible multiplex them.

RMAN- unable to find archive log

Similar Messages

Maybe you are looking for