Is there any way I can get all the archive log files present in a backup piece. I tried following but it always gives me all the log files for each piece:
**** SQL> select s.set_stamp, s.set_count, s.PIECES, s.backup_type, s.controlfile_included from v$backup_set s, v$backup_piece p where s.set_stamp=p.set_stamp and s.set_count=p.set_count and p.handle='5mjv4do0_1_1';
Actually, i have test database open in read only and i want to apply archive files carry from production database at daily level. When i'm going for recovery, since database is already in consistent state, it is not asking for recovery.
I had a production db with archive logging enabled
SQL> select name,status 2 from v$archived_log;
NAME STATUS ---------------------------------------- - D:ORACLEARCHIVE_ORCL11_13.DBF A D:ORACLEARCHIVE_ORCL11_14.DBF A D:ORACLEARCHIVE_ORCL11_15.DBF A
[code]...
So i need to restore archivelogs by using sequence
RMAN>RESTORE ARCHIVELOG FROM SEQUENCE 20 UNTIL SEQUENCE 28; So the restore is completed successfully So its very hard to monitor archivelog files i feel i should have included all archivelog files while taking RMAN backup
RMAN >backup database plus archivelog all delete input;
but the problem is my RMAN backup is already 360GB in size and it takes 4-5 hrs to complete .so i need to schedule RMAN backup at one time (e.g sunday) ,delete the archivelog files older than sundayand now schedule the archivelog backup at another day (e.g wed &sat)
my question is where i have to change my script to backup all avaialbe archivelog files if old archivelog files are deleted at os level?
RMAN> run { 2> allocate channel c1 type disk; 3> sql 'alter system archive log current'; 4> backup archivelog all format 'D:oracleackuplog_t%t_s%s_p%p' delete input; 5> release channel c1; 6> }
There is a archive log backupset,and the backup set contains many archive log file,and now i want extract to a directory,how can i do?
BS Key Size Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ --------------- 3 86.20M DISK 00:00:21 02-JUN-12 BP Key: 3 Status: AVAILABLE Compressed: NO Tag: TAG20120602T113622 Piece Name: /u02/rman_bak/20120602/archive_log_t784899382_s4_p1
There is an incident that in production database 1000 archive log files generated.From 1000 files, 100 archive log files have been removed.When i take incremental backup next day , what will happen in database?
Starting restore at 18-AUG-11 released channel: c1 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of restore command at 08/18/2011 09:20:21 RMAN-06004: ORACLE error from recovery catalog database: RMAN-20242: specification does not match any archive log in the recovery catalog
changing archive mode during DB running.Before in 9.2, 'ALTER SYSTEM ARCHIVE LOG START/STOP' is available for this job. But, after 10g/11g, it cause 'archive log stop has been deprecated'.
However, for my practice, I need to estimate archived logs size before backup them, so I need to stop archive log for a while and enable it later during DB running.
I check Oracle documents, it only mentions changing archive log mode at DB mounted but not open.
this my f drive space is full so i want to change this my archive destination to my another g drive so how can i do this.and if i change this my archive destination does its affect any problem while recover my database in future.
We have a nightly rman backup that was complete and clean.The backup contains a Data File, Control File and a backup Archive Log file.The database server crashed with all the subsequent archive logs lost.
We are trying to recover from the three backup files.We are bumping into the backup piece missing as all the archive logs are done. how to restore with the exising backup files. the lost archive logs are probably salvageable.
We are trying to restore a database on the different server using RAM incremental level 0 and 1 backups. We have weekly Incremental level 0 backups along with incremental backups on daily basis. During recovery of Incremental level 0 backup, RMAN is expecting/looking for Incremental Level 0 backup of prior week as well. Is this the usual process for RMAN to look for prior level 0 backup though we need to restore from the current level 0 backup and roll forward by a week with subsequent Level 1 backup.?
We intend to restore from the Level 0 of 1/16 and roll forward with daily incrementals till 1/22. RMAN is expecting level 0 backupsets from 1/9 backup as well and keep failing since those backups are not available. quick inputs since we are in middle of recovery and trying to resolve if this is even doable.
I have problem on using "delete obsolete" in RMAN.
First, let describe my backup configuration.
1. Full backup every Monday (17-Oct, 10-Oct, 3-Oct, 26-Sep) 2. Incremental backup for other days 3. Enable autobackup of control file 4. Backup archive log every day 5. RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS 6. Execute "Delete obsolete" every day 7. control file is used instead of catalog
The results observed: 1. Backup of control files older than 30 days will be deleted 2. Backup of archive log files older than 30 days will be deleted. 3. Backup of datafiles older than ~14 days but before 30 days are also DELETED.
In my example, the backup of datafiles created at 26-Sep is deleted at 16-Oct.
I tried "restore database validate until time "sysdate-22"" at 17-Oct. And RMAN reported "datafile xx will be created automatically during restore operation". It seems that RMAN failed to do restoration up to 22 days ago. The retention policy I set seems not effective on datafile backups.
I checked view v$backup_set and the "Keep" is "No" and "Keep until" is empty.
The only thing I can think of, is the settings of "CONTROL_FILE_RECORD_KEEP_TIME". It is marked "7" in the Oracle, which is less than the retention. But I suppose this only causes the backup not deleted, but NOT be deleted earlier.
I`m using the the version 11.0.2.3 for testing. I read a line as below from the OCP book.
If none of the LOG_ARCHIVE_DEST_n parameters have been set, then transitioning. the database to archivelog mode will internally set LOG_ARCHIVE_DEST_10 to the flash recovery area, if it has been configured. In my database the fast recovery already been set as below.
SQL> show parameter db_recovery
NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ db_recovery_file_dest string +FASTRECOVERY db_recovery_file_dest_size big integer 4248M
So I thought if I turn the database into archive log mode, then the log_archive_dest_10 will be set as the same value as db_recovery_dest.
SQL> alter database archivelog;
Database altered.
SQL> alter database open;
Database altered.
SQL> show parameter log_archive_dest
NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ log_archive_dest string log_archive_dest_1 string log_archive_dest_10 string
See, after the database become archive, the log_archive_dest_10 still be empty. So is there any thing wrong with my understanding?
I have 2 seperate rman backup one backup is of only datafile ,spfile and controlfile which i am able to restore and recover without any problem say bkp1 taken at 10 am
other set of backup is of only archive log files of same day but later time than datafile backup say bkp2 taken at 8pm...if i restore and recover bkp1 and try to restore bkp2 it gives error datafile exist (possibly due to fact both backup have control file)
if i just restore bkp1 and try to restore bkp2 so that i can do one recover at time it gives error datafile permission issue (possibly due to fact both backup have control file)
I want to restore database upto 8pm time how can i use both bkp1 and bkp2 to do it(restore datafiles and apply all archive logs on it)
I am running the following command to backup my archive logs and want to keep at least two hours of .arc files on disk.
rman < connect target login/password connect catalog login/password show all; sql "alter system archive log current"; backup filesperset 5 archivelog until time 'sysdate-2/24' format $FILE_DEST_ARCH delete input ; resync catalog; EOT
On some occassions, there will not be any archive logs that meet this criteria and I get the following error:
RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of backup command at 12/01/2010 12:50:58 RMAN-06004: ORACLE error from recovery catalog database: RMAN-20242: specificati on does not match any archive log in the recovery catalog
Is there anything I can do to the rman command above that will prevent this error from happening but yet keeping same functionality?
We are having an intermittent problem related to failing RMAN archive log backups. Normally everything works fine but once every fortnight or so the archive log backup starts to fail with the below message. We run two Oracle instances on this windows box, so they are using same oracle and TSM client binaries, but it is only of the instances that have this problem - the largest instance though. Restarting the Oracle instance solves the problem and everything is back to normal, until next time ...
This is the error message in the rman log file CODERMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03009: failure of allocate command on c1 channel at 03/27/2013 11:00:29 ORA-03113: end-of-file on communication channel
Trace file CODE Trace file R:\ORA_DATA\SDC002\diag\rdbms\sdc002\sdc002\trace\sdc002_ora_12328.trc Oracle Database 11g Release 11.2.0.3.0 - 64bit Production Windows NT Version V6.1 Service Pack 1 CPU : 40 - type 8664, 20 Physical Cores Process Affinity : 0x0x0000000000000000 Memory (Avail/Total): Ph:85656M/147445M, Ph+PgF:96175M/157683M Instance name: sdc002 Redo thread mounted by this instance: 1 Oracle process number: 57 Windows thread id: 12328, image: ORACLE.EXE (SHAD)
I have the incident file as well if that is of any use.
Could the problem be related to running two backups in parallel?
We run full backups once a week and both this time and last time the archive log backup failed it was in conjunction to when the full backup also was running.
Is there any other solution to the problem than restarting the oracle instance?
Since this is a busy production instance it is a big problem for us to restart it outside of maintenance windows.
I have Oracle 10gR2 database on a windows server, I have scheduled rman backup for this database from Solaris server
set echo onrun { crosscheck archivelog all; backup check logical database plus archivelog; delete noprompt obsolete device type DISK; } exit;
It is deleting the obsolete backup pieces but it is not deleting old archive logs (obsolete archive logs) and it is not even showing old archives as obsolete when I check thru report obsolete
We are going to implement oracle 11g. Now I wanna use rman to take the incremental backup in the follwing way:
Level-0 backup weekly, in the way:
run { allocate channel c1 type disk; allocate channel c2 type disk; BACKUP incremental level 0 DATABASE TAG 'Weekly_full' FORMAT 'E:RMAN_backupweekly_full_%d_%Y%M%D_s%s_p%p.bak'; backup archivelog all not backed up 1 times delete input TAG 'Weekly_full_arc' FORMAT 'E:RMAN_backupweekly_full_arc_%d_%Y%M%D_s%s_p%p.bak';
[code].....
and RETENTION POLICY TO RECOVERY WINDOW is set to 10 days, so that there is no chance that i will delete expired backup before taking backup.
Now my question is,
1) Is the way is correct that there is no wrong configuration. My main concern is about archive log, is it correct?
2) As i am deleting archive log files with the backup and after that the expired archive log backup is also deleted, so is there any chance of failure in recovery.
3) here how archive log backup will work with 10 days retention policy.
i have found an issue regarding log archiving on dest1. yesterday one sequence number 76871 not archive to dest1.alert logfile content as follow. i configure standby and ship archive manually with window copy command. i need this archive to complete recovery on standby database.
Mon Oct 21 09:29:28 2013 ARC2: Completed archiving log# 3 seq# 76869 Mon Oct 21 09:39:28 2013 Thread 1 advanced to log sequence 76871 Current log# 2 seq# 76871 mem# 0: D:ORACLEORADATAORC1REDO02.LOG [code]....
