Archive logs sequence - files deleted
Hi,
I am running one server (e.g. Production) on Archivelogs, and applying these to refresh standby on another server. During one of my activities, I accidentally deleted some Archivelogs that Production server generated. At this time, the database was idle, i.e. without any activity, except what I was doing.
So, I had a archivelogs sequence as:
ARC04482_0123456789.001
ARC04483_0123456789.001
ARC04484_0123456789.001
ARC04485_0123456789.001
And, I accidentally deleted from ARC04486 to ARC04568. Now, I have two archivelogs in standby:
ARC04485_0670557214.001
ARC04569_0670557214.001
How would the sequence work and if these logs would be applied to the recovery (refresh) process as normal, or the process would always look for ARC04486 log?
I am still newbie and wanted to clarify the above. Hope it makes sense.
Thanks,
>
So, does it mean there's no way unless I (somehow) recover the missing archivelogs in sequence?
>
If it is possible to "recover" the missing archivelogs then yes. Do that. That is the easiest way, however, I have a feeling you don't have a copy of them laying around or you wouldn't be asking this question. :)
You should be able to do this by taking an incremental backup of the primary starting from the current scn on the standby. Something like:
BACKUP INCREMENTAL FROM SCN "current_standby scn" DATABASE
Cancel managed recovery mode on the standby, recover the database with the new incremental backup (RECOVER DATABASE NOREDO), then bring the standby back up in managed recovery mode.
Search MOS for "roll forward standby" for complete steps.
Similar Messages
-
How to practice "Archived log sequences loss- Block corruptions recovery"
Hello,
Prepare and test a recovery scenarios
- System Tablespace loss
- Online Redolog loss
- Controlfile loss
- Data Tablespace loss
- Single/multiple datafile loss
- Archived log sequences loss- Block corruptions recovery
- Total loss (database)
- Total loss (server = database/software/parameter files)
11g on windows
I am practicing my rman recovery and found this list of recovery scenarios. I have completed all scenarios
besides "Archived log sequences loss- Block corruptions recovery"
How do I break the database for the snenario "Archived log sequences loss- Block corruptions recovery"?
Do I delete the acr.001 files in directory I:\oracle\product\11.1.0\db_1\RDBMS? Then recovery as far forward as I can?
thanks for your help.thanks for the tips
11g on windows 2003
I broke the database like this:
rman backup
shutdown immediate;
deleted datafile 5
delete most recent archivelogs seq 5 and 6;
recovered like this:
startup mount;
restore datafile 5;
recover datafile 5;
alter database open;
This does not seem correct? Did this also apply my archivelogs seq 5 and 6? Should I also do a point in time recovery?
Should I also run this?
run (set until sequence 6 thread 1; restore database; recover database;)
thanks for any help -
How I can log Sequence File version number to database?
Hi,
As in the subject.
How I can log Sequence File version number to database?
There is nothing like that under Logging object.Do you need it in a separate field in the databse?
One option is to just add it as an additional result in a step in your sequence file.
RunState.SequenceFile.AsPropertyObjectFile.Version
Hope this helps,
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~ -
Archive log automatically getting deleted
Hi,
My Archive logs are getting automatically deleted from ASM. I keep my Archive logs in FRA. My alert log shows deletions like this:
Deleted Oracle managed file +DATA1/orcl/archivelog/...Retention policy to recovery window is set to 24 days. The +DATA1 ASM disk has lots of free space. Archivelog deletion policy is set to None and I don't run archive deletion from rman too...
Is there any other option I need to check?Thank you werner,
Below queries show that I already have space in FRA...
SQL> select (SPACE_LIMIT/1024/1024/1024), (SPACE_USED/1024/1024/1024), (SPACE_RECLAIMABLE/1024/1024/1024) from v$recovery_file_dest;
(SPACE_LIMIT/1024/1024/1024) (SPACE_USED/1024/1024/1024) (SPACE_RECLAIMABLE/1024/1024/1024)
500 36.6706381 3.2632184
SQL>
SQL> select * from v$flash_recovery_area_usage;
FILE_TYPE PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
CONTROLFILE .02 0 1
ONLINELOG .12 0 12
ARCHIVELOG 1.03 .65 29
BACKUPPIECE 0 0 0
IMAGECOPY 0 0 0
FLASHBACKLOG 6.36 6.15 125
6 rows selected.
SQL>See my alert log after some "alter system switch logfile;"
Tue Apr 27 11:17:46 2010
Thread 1 advanced to log sequence 83570
Current log# 109 seq# 83570 mem# 0: +DATA1/orcl/onlinelog/group_109.19715.679998731
Current log# 109 seq# 83570 mem# 1: +DATA1/orcl/onlinelog/group_109.20362.679998737
Tue Apr 27 11:17:47 2010
Deleted Oracle managed file +DATA1/orcl/archivelog/2010_04_26/thread_3_seq_90114.17125.717358729
Deleted Oracle managed file +DATA1/orcl/flashback/log_74.12659.717340839
Deleted Oracle managed file +DATA1/orcl/flashback/log_85.18441.717351679
Deleted Oracle managed file +DATA1/orcl/flashback/log_8.11194.717355103
Deleted Oracle managed file +DATA1/orcl/flashback/log_9.12991.717355123
Deleted Oracle managed file +DATA1/orcl/flashback/log_10.17043.717355141
Deleted Oracle managed file +DATA1/orcl/flashback/log_1.15281.717355097
Deleted Oracle managed file +DATA1/orcl/flashback/log_79.13174.717355163
Deleted Oracle managed file +DATA1/orcl/flashback/log_138.15374.717355185
Deleted Oracle managed file +DATA1/orcl/flashback/log_139.19996.717357319
Tue Apr 27 11:17:48 2010
Thread 1 advanced to log sequence 83571
Current log# 105 seq# 83571 mem# 0: +DATA1/orcl/onlinelog/group_105.12632.679998535
Current log# 105 seq# 83571 mem# 1: +DATA1/orcl/onlinelog/group_105.15649.679998539
Tue Apr 27 11:17:49 2010
Deleted Oracle managed file +DATA1/orcl/archivelog/2010_04_26/thread_2_seq_87077.21363.717362485
Tue Apr 27 11:17:49 2010
Deleted Oracle managed file +DATA1/orcl/archivelog/2010_04_26/thread_4_seq_87136.11714.717365975
Deleted Oracle managed file +DATA1/orcl/flashback/log_129.20212.717344739
Deleted Oracle managed file +DATA1/orcl/flashback/log_140.11185.717358727
Deleted Oracle managed file +DATA1/orcl/flashback/log_5.21454.717358739
Deleted Oracle managed file +DATA1/orcl/flashback/log_11.15673.717358753
Deleted Oracle managed file +DATA1/orcl/flashback/log_87.12289.717358783
Deleted Oracle managed file +DATA1/orcl/flashback/log_12.21878.717358779
Deleted Oracle managed file +DATA1/orcl/flashback/log_141.17658.717358807
Deleted Oracle managed file +DATA1/orcl/flashback/log_143.20355.717358847
Deleted Oracle managed file +DATA1/orcl/flashback/log_142.15020.717358817
Deleted Oracle managed file +DATA1/orcl/flashback/log_145.11651.717358889
Deleted Oracle managed file +DATA1/orcl/flashback/log_137.13239.717351771
Deleted Oracle managed file +DATA1/orcl/flashback/log_86.20900.717355183
Deleted Oracle managed file +DATA1/orcl/flashback/log_147.11174.717362357
Deleted Oracle managed file +DATA1/orcl/flashback/log_146.10495.717358957
Deleted Oracle managed file +DATA1/orcl/flashback/log_149.14900.717362391
Deleted Oracle managed file +DATA1/orcl/flashback/log_150.19760.717362403
Deleted Oracle managed file +DATA1/orcl/flashback/log_14.20074.717362515
Deleted Oracle managed file +DATA1/orcl/flashback/log_148.12779.717362383
Deleted Oracle managed file +DATA1/orcl/flashback/log_13.15276.717362485
Deleted Oracle managed file +DATA1/orcl/flashback/log_151.13222.717365933
Deleted Oracle managed file +DATA1/orcl/flashback/log_152.21251.717365947
Tue Apr 27 11:17:53 2010
Thread 1 advanced to log sequence 83572
Current log# 104 seq# 83572 mem# 0: +DATA1/orcl/onlinelog/group_104.18737.679998357
Current log# 104 seq# 83572 mem# 1: +DATA1/orcl/onlinelog/group_104.17641.679998363
Tue Apr 27 11:17:53 2010
Deleted Oracle managed file +DATA1/orcl/archivelog/2010_04_26/thread_1_seq_83563.18107.717366141
Tue Apr 27 11:17:54 2010
Deleted Oracle managed file +DATA1/orcl/archivelog/2010_04_26/thread_4_seq_87137.10526.717366139
Deleted Oracle managed file +DATA1/orcl/flashback/log_153.20718.717365963
Deleted Oracle managed file +DATA1/orcl/flashback/log_17.21619.717365977
Deleted Oracle managed file +DATA1/orcl/flashback/log_18.20172.717365989
Deleted Oracle managed file +DATA1/orcl/flashback/log_19.12078.717366005
Deleted Oracle managed file +DATA1/orcl/flashback/log_48.19221.717366017
Deleted Oracle managed file +DATA1/orcl/flashback/log_154.14279.717366053
Deleted Oracle managed file +DATA1/orcl/flashback/log_155.14745.717366079
Deleted Oracle managed file +DATA1/orcl/flashback/log_156.17031.717366101
Tue Apr 27 11:18:07 2010
Deleted Oracle managed file +DATA1/orcl/archivelog/2010_04_27/thread_2_seq_87079.20751.717379897
Deleted Oracle managed file +DATA1/orcl/flashback/log_157.10653.717366127
Deleted Oracle managed file +DATA1/orcl/flashback/log_144.17927.717358881
Deleted Oracle managed file +DATA1/orcl/flashback/log_2.18495.717366169
Deleted Oracle managed file +DATA1/orcl/flashback/log_20.16857.717369567
Deleted Oracle managed file +DATA1/orcl/flashback/log_16.12724.717363263
Deleted Oracle managed file +DATA1/orcl/flashback/log_23.13471.717369587
Deleted Oracle managed file +DATA1/orcl/flashback/log_89.16244.717369613
Deleted Oracle managed file +DATA1/orcl/flashback/log_88.11076.717369605
Deleted Oracle managed file +DATA1/orcl/flashback/log_158.11103.717369643
Deleted Oracle managed file +DATA1/orcl/flashback/log_159.21379.717369685
Deleted Oracle managed file +DATA1/orcl/flashback/log_15.22226.717362555
Deleted Oracle managed file +DATA1/orcl/flashback/log_160.13946.717369711
Deleted Oracle managed file +DATA1/orcl/flashback/log_6.14447.717369491
Deleted Oracle managed file +DATA1/orcl/flashback/log_24.11233.717373129
Deleted Oracle managed file +DATA1/orcl/flashback/log_76.10929.717373141
Deleted Oracle managed file +DATA1/orcl/flashback/log_90.12864.717373157
Deleted Oracle managed file +DATA1/orcl/flashback/log_163.13475.717373171
Deleted Oracle managed file +DATA1/orcl/flashback/log_164.20384.717373187
Deleted Oracle managed file +DATA1/orcl/flashback/log_165.15963.717373215
Deleted Oracle managed file +DATA1/orcl/flashback/log_166.20629.717373249
Deleted Oracle managed file +DATA1/orcl/flashback/log_167.21197.717373279
Deleted Oracle managed file +DATA1/orcl/flashback/log_161.13500.717369751
Deleted Oracle managed file +DATA1/orcl/flashback/log_25.13335.717373553
Deleted Oracle managed file +DATA1/orcl/flashback/log_162.17288.717372027
Deleted Oracle managed file +DATA1/orcl/flashback/log_22.20002.717372205
Deleted Oracle managed file +DATA1/orcl/flashback/log_91.16639.717376749
Deleted Oracle managed file +DATA1/orcl/flashback/log_92.15382.717376759
Deleted Oracle managed file +DATA1/orcl/flashback/log_169.19652.717376787
Deleted Oracle managed file +DATA1/orcl/flashback/log_170.14527.717376801
Deleted Oracle managed file +DATA1/orcl/flashback/log_168.10371.717376781
Tue Apr 27 11:21:28 2010
Thread 1 advanced to log sequence 83573
Current log# 103 seq# 83573 mem# 0: +DATA1/orcl/onlinelog/group_103.11697.679998293
Current log# 103 seq# 83573 mem# 1: +DATA1/orcl/onlinelog/group_103.21923.679998297
Tue Apr 27 11:21:28 2010
Deleted Oracle managed file +DATA1/orcl/archivelog/2010_04_27/thread_1_seq_83564.19690.717379897
Deleted Oracle managed file +DATA1/orcl/archivelog/2010_04_27/thread_2_seq_87080.11232.717383337
Tue Apr 27 11:22:10 2010
Deleted Oracle managed file +DATA1/orcl/flashback/log_26.12608.717374927
Deleted Oracle managed file +DATA1/orcl/flashback/log_27.12714.717380335
Deleted Oracle managed file +DATA1/orcl/flashback/log_33.17297.717380353
Deleted Oracle managed file +DATA1/orcl/flashback/log_34.14547.717380371
Deleted Oracle managed file +DATA1/orcl/flashback/log_36.17079.717380389
Deleted Oracle managed file +DATA1/orcl/flashback/log_93.18491.717380407
Deleted Oracle managed file +DATA1/orcl/flashback/log_174.10790.717380465
Tue Apr 27 11:22:11 2010
Thread 1 advanced to log sequence 83574
Current log# 108 seq# 83574 mem# 0: +DATA1/orcl/onlinelog/group_108.15776.679998703
Current log# 108 seq# 83574 mem# 1: +DATA1/orcl/onlinelog/group_108.13383.679998709
Tue Apr 27 11:22:11 2010
Deleted Oracle managed file +DATA1/orcl/archivelog/2010_04_27/thread_1_seq_83566.16358.717383421
Deleted Oracle managed file +DATA1/orcl/archivelog/2010_04_27/thread_4_seq_87141.11563.717383423
Deleted Oracle managed file +DATA1/orcl/archivelog/2010_04_27/thread_3_seq_90119.12158.717383423
Tue Apr 27 11:22:25 2010Edited by: OSSGeek on Apr 27, 2010 12:49 AM -
Archive Logs Will Not Delete from OS
Hi Everyone,
Here's my issue. Somehow i have a few archivelogs that are corruptued, plus a backup of the database that is corrupted. Since then, I have made a new backup of the database and everything is running smoothly. WHen i try to delete the files from DISK (which i cannot delete), i get this error: CANNOT DELETE <file_name>: The file or directory is corrupted and unreadable. I try to search for the corrupted files in rman, but i get this message "specification does not match any archived log in the recovery catalog". It seems that rman doesn't recognize that the files exist.
I go to the alert log and I have this error:
Corrupt block seq: 10511 blocknum=1.
Bad header found during deleting archived log
Data in bad block - seq:0. bno:0. time:0
beg:0 cks:0
calculated check value: 0
Reread of seq=10511, blocknum=1, file=APP\ORACLE\FLASH_RECOVERY_AREA\PPROD\ARCHIVELOG\2010_11_04\O1_MF_1_10511_6F5SOFC7_.ARC, found same corrupt data
Reread of seq=10511, blocknum=1, file=APP\ORACLE\FLASH_RECOVERY_AREA\PPROD\ARCHIVELOG\2010_11_04\O1_MF_1_10511_6F5SOFC7_.ARC, found same corrupt data
Reread of seq=10511, blocknum=1, file=APP\ORACLE\FLASH_RECOVERY_AREA\PPROD\ARCHIVELOG\2010_11_04\O1_MF_1_10511_6F5SOFC7_.ARC, found same corrupt data
Reread of seq=10511, blocknum=1, file=APP\ORACLE\FLASH_RECOVERY_AREA\PPROD\ARCHIVELOG\2010_11_04\O1_MF_1_10511_6F5SOFC7_.ARC, found same corrupt data
Reread of seq=10511, blocknum=1, file=APP\ORACLE\FLASH_RECOVERY_AREA\PPROD\ARCHIVELOG\2010_11_04\O1_MF_1_10511_6F5SOFC7_.ARC, found same corrupt data
I would really appreciate some help to delete these files from the OS. Thanks in advance to anyone that can help.RMAN> Change Archivelog All Validate;
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=363 device type=DISK
validation succeeded for archived log
archived log file name=APP\ORACLE\FLASH_RECOVERY_AREA\PROD\ARCHIVELOG\2010_11_04\O1_MF_1_10514_6F6SJ9D6_.ARC RECID=11389 STAMP=734220234
validation succeeded for archived log
archived log file name=APP\ORACLE\FLASH_RECOVERY_AREA\PROD\ARCHIVELOG\2010_11_07\O1_MF_1_10546_6FDRCHQX_.ARC RECID=11421 STAMP=734412064
validation succeeded for archived log
archived log file name=\APP\ORACLE\FLASH_RECOVERY_AREAPPROD\ARCHIVELOG\2010_11_07\O1_MF_1_10556_6FGTGZNJ_.ARC RECID=11431 STAMP=734479760
validation succeeded for archived log
archived log file name=APP\ORACLE\FLASH_RECOVERY_AREA\PROD\ARCHIVELOG\2010_11_07\O1_MF_1_10557_6FGX6CG5_.ARC RECID=11432 STAMP=734482556
validation failed for archived log
archived log file name=APP\ORACLE\FLASH_RECOVERY_AREA\PROD\ARCHIVELOG\2010_11_07\O1_MF_1_10558_6FGZ9SLK_.ARC RECID=11433 STAMP=734484714
validation failed for archived log
archived log file name=APP\ORACLE\FLASH_RECOVERY_AREA\PROD\ARCHIVELOG\2010_11_08\O1_MF_1_10559_6FH12R00_.ARC RECID=11434 STAMP=734486537
validation failed for archived log
archived log file name=APP\ORACLE\FLASH_RECOVERY_AREA\PROD\ARCHIVELOG\2010_11_08\O1_MF_1_10560_6FH6OJRW_.ARC RECID=11435 STAMP=734492259
validation failed for archived log
archived log file name=APP\ORACLE\FLASH_RECOVERY_AREA\PROD\ARCHIVELOG\2010_11_08\O1_MF_1_10561_6FHL3J98_.ARC RECID=11436 STAMP=734503969
validation failed for archived log
archived log file name=APP\ORACLE\FLASH_RECOVERY_AREA\PROD\ARCHIVELOG\2010_11_08\O1_MF_1_10562_6FHTF2QX_.ARC RECID=11437 STAMP=734512468
validation failed for archived log
archived log file name=APP\ORACLE\FLASH_RECOVERY_AREA\PROD\ARCHIVELOG\2010_11_08\O1_MF_1_10563_6FJ32ZSD_.ARC RECID=11438 STAMP=734521361
validation failed for archived log
archived log file name=APP\ORACLE\FLASH_RECOVERY_AREA\PROD\ARCHIVELOG\2010_11_08\O1_MF_1_10564_6FJB1OMK_.ARC RECID=11439 STAMP=734528486
validation failed for archived log
archived log file name=APP\ORACLE\FLASH_RECOVERY_AREA\PROD\ARCHIVELOG\2010_11_08\O1_MF_1_10565_6FJJH3TV_.ARC RECID=11440 STAMP=734535062
validation failed for archived log
archived log file name=APP\ORACLE\FLASH_RECOVERY_AREA\PROD\ARCHIVELOG\2010_11_08\O1_MF_1_10566_6FJKJ6PY_.ARC RECID=11441 STAMP=734536118
validation failed for archived log
archived log file name=APP\ORACLE\FLASH_RECOVERY_AREA\PROD\ARCHIVELOG\2010_11_08\O1_MF_1_10567_6FJV244W_.ARC RECID=11442 STAMP=734545911
validation failed for archived log
archived log file name=APP\ORACLE\FLASH_RECOVERY_AREA\PROD\ARCHIVELOG\2010_11_08\O1_MF_1_10568_6FK5BMYR_.ARC RECID=11443 STAMP=734556421
validation failed for archived log
archived log file name=APP\ORACLE\FLASH_RECOVERY_AREA\PROD\ARCHIVELOG\2010_11_08\O1_MF_1_10569_6FK68QRW_.ARC RECID=11444 STAMP=734557384
validation failed for archived log
archived log file name=APP\ORACLE\FLASH_RECOVERY_AREA\PROD\ARCHIVELOG\2010_11_08\O1_MF_1_10570_6FKDM74D_.ARC RECID=11445 STAMP=734563863
validation failed for archived log
archived log file name=APP\ORACLE\FLASH_RECOVERY_AREA\PROD\ARCHIVELOG\2010_11_08\O1_MF_1_10571_6FKGK4LK_.ARC RECID=11446 STAMP=734565848
validation failed for archived log
archived log file name=APP\ORACLE\FLASH_RECOVERY_AREA\PROD\ARCHIVELOG\2010_11_08\O1_MF_1_10572_6FKH42MK_.ARC RECID=11447 STAMP=734566452
validation succeeded for archived log
archived log file name=APP\ORACLE\FLASH_RECOVERY_AREA\PROD\ARCHIVELOG\2010_11_09\O1_MF_1_10573_6FKOQX6C_.ARC RECID=11448 STAMP=734573238
validation succeeded for archived log
archived log file name=APP\ORACLE\FLASH_RECOVERY_AREA\PROD\ARCHIVELOG\2010_11_09\O1_MF_1_10574_6FKVHC8S_.ARC RECID=11449 STAMP=734579100
validation succeeded for archived log
archived log file name=APP\ORACLE\FLASH_RECOVERY_AREA\PROD\ARCHIVELOG\2010_11_09\O1_MF_1_10575_6FL6T300_.ARC RECID=11450 STAMP=734590708
validation succeeded for archived log
archived log file name=APP\ORACLE\FLASH_RECOVERY_AREA\PROD\ARCHIVELOG\2010_11_09\O1_MF_1_10576_6FLJ3NMK_.ARC RECID=11451 STAMP=734600229
validation succeeded for archived log
archived log file name=APP\ORACLE\FLASH_RECOVERY_AREA\PROD\ARCHIVELOG\2010_11_09\O1_MF_1_10577_6FLO72K2_.ARC RECID=11452 STAMP=734605459
validation succeeded for archived log
archived log file name=APP\ORACLE\FLASH_RECOVERY_AREA\PROD\ARCHIVELOG\2010_11_09\O1_MF_1_10578_6FLTF31G_.ARC RECID=11453 STAMP=734610772
validation succeeded for archived log
archived log file name=APP\ORACLE\FLASH_RECOVERY_AREA\PROD\ARCHIVELOG\2010_11_09\O1_MF_1_10579_6FM1N500_.ARC RECID=11454 STAMP=734618166
Crosschecked 26 objects -
I have a situation where I don't want to recover a file... I want to see how it was deleted.
Is there any way to review file deletions via Apple log files or any other method? My research so far says no... but perhaps someone is craftier than I've proven to be.An unfortunate circumstance to be sure. Out of curiosity is there any particular reason you can't use ClamXAV rather than NAV?
I suppose that if NAV has a log and nothing relevant is in the log, then you're at a loss to even know if NAV is responsible for the folder's mysterious disappearance. Maybe you have technically savvy cockroaches in the building that come out at night to play? An informational age version of Archie and Mehitabel?
This experience may be an impetus to install software that keeps track of what's installed or removed from a computer. Doesn't help much now but it would be useful in the future.
Oh, one thing comes to mind - file recovery software:
Data Rescue II
File Salvage
TechTool Pro
Message was edited by: Kappy -
Log sequence file is not genrated
Hi All,
I am running ECC on Maxdb 7.8.02.23
As i checked after the complete backup i am having the log file's till sequence number 3641 but after that 3642 is missing.
From 3643 onwards i am having all the log files available.
As i checked from dbm.mdf only seqeunce file 3642 is missing.
Please advice why this happened. ?..
4E4BE1C9005A|LOG_000003636|Prod_Archive_Log_Backup |vftFile |YES| 0| 8|S|/sapdb/WIP/logarchive/WIP_LOG_BACKUP/WIP_LOG.3636
4E4BEFD9005B|LOG_000003637|Prod_Archive_Log_Backup |vftFile |YES| 0| 8|S|/sapdb/WIP/logarchive/WIP_LOG_BACKUP/WIP_LOG.3637
4E4BFDED005D|LOG_000003638|Prod_Archive_Log_Backup |vftFile |YES| 0| 8|S|/sapdb/WIP/logarchive/WIP_LOG_BACKUP/WIP_LOG.3638
4E4C0C0C0060|LOG_000003639|Prod_Archive_Log_Backup |vftFile |YES| 0| 8|S|/sapdb/WIP/logarchive/WIP_LOG_BACKUP/WIP_LOG.3639
4E4C1A170061|LOG_000003640|Prod_Archive_Log_Backup |vftFile |YES| 0| 8|S|/sapdb/WIP/logarchive/WIP_LOG_BACKUP/WIP_LOG.3640
4E4C28310062|LOG_000003641|Prod_Archive_Log_Backup |vftFile |YES| 0| 8|S|/sapdb/WIP/logarchive/WIP_LOG_BACKUP/WIP_LOG.3641
4E523AA20007|LOG_000003643|Prod_Archive_Log_Backup |vftFile |YES| 0| 8|S|/sapdb/WIP/logarchive/WIP_LOG_BACKUP/WIP_LOG.3643
4E5244E20007|LOG_000003644|Prod_Archive_Log_Backup |vftFile |YES| 0| 8|S|/sapdb/WIP/logarchive/WIP_LOG_BACKUP/WIP_LOG.3644
Regards,
SahilHi Lars,
As i checked dbm.knl file i got the below error903 for the missing log file.
4E57531C0056|LOG_000000202|SAVE WARM|2011-08-26 13:02:43|2011-08-26 13:32:30|2011-08-26 13:32:36|2011-08-26 13:32:36| 1621143| 1626510| |Prod_Archive_Log_Backup | 3224| 0| 0| |
4E575A240057|LOG_000000203|SAVE WARM|2011-08-26 13:32:41|2011-08-26 14:02:34|2011-08-26 14:02:36|2011-08-26 14:02:36| 1626511| 1630432| |Prod_Archive_Log_Backup | 0| 0| -903| |
4E576939005D|LOG_000000204|SAVE WARM|2011-08-26 13:32:41|2011-08-26 15:06:53|2011-08-26 15:06:57|2011-08-26 15:06:58| 1626511| 1652309| |Prod_Archive_Log_Backup | 18224| 0| 0|
Please advice.
Regards,
Sahil -
Deleting the old Archive Log Files from the Hard Disk
Hello All,
I want to delete the old archive files of Oracle. These files are very old and consuming very huge disk space.
Is there any way by which I can delete these files from the Hard Disk?
Can I directly delete them using the Operating System Command?
Will it cause any dilfference to the normal functioning of my Database?
If I need to delete these files, do I need to bring the database down?
Please guide me.
I need to do this activity to make some space free on the Hard Disk.
Thanks in advance.
HimanshuHi.
Keep archived logs from time of last backup and forward to currenct time on disk together with the backup itself. And keep older archived logs together with older warm/cold backupfiles on tape as long as there is enough capasity or following your recovery strategy. This way you might be able to roll forward a recovery without restoring these files from tape which often the faster.
Older archived logs can be deleted manually, with scheduled OS script or automatically with RMAN.
Good luck
rgds
Kjell Ove -
Hello,
I have a understanding problem off the function of the archived log files. My Oracle 9i Database is running in ARCHIVELOG. So if the online log files are full they get backed up to 3 different locations.
However if I view now the v$archive_log view then I see all the archived log files.
So now my questions:
1. At which point does these archived log files get deleted ?
2. If they never get deleted how do I know which archived log file can I delete.
3. If I run a full hot/cold backup can I delete this archive log files?
4. Is there any other way to delete the archived log files then using rman "delete input" option ? Like is there any way to delete the archived log files form the sqplplus prompt ?
I have searched and read some articles in the net about it but it is always just about how to set up the db into archivelog mode but I was not able to find anything answering my questions.
Thank you
MarcusOut of the box, archived logs are not deleted
automatically. However, you can delete them via
RMAN. RMAN will delete them based on the set
retention policy. You can see which logs and
backups RMAN considers obsolete via the "report
obsolete" command. RMAN keeps track of logs that
are necessary for recovery, and those that can
be safely deleted.
Another option, as you have noted, is to backup
archivelogs using RMAN, with the "delete input"
option.
The best option (IMHO) is to automate deletion
of obsolete archive logs via a script. This
can be done using the "delete noprompt obsolete"
RMAN command.
I'm not aware of any SQLPlus based method to delete
logs. In any case, this would NOT be a good idea, as
RMAN would not be aware of any such deletions.
Hope this helps.
Kailash. -
Best way of deleting archive logs on standby when backup taken on primary
Hello,
I have a 11gr2 dataguard configuration without the broker.
main problem in my particular situation arises from my FRA size on primary much more than on standby (90Gb vs 30Gb) and in some situations I'm constrained with FRA space on standby.... I'm going to align the FRAs but in the mean time....
can anyone confirm that if I have configuration as in subject with maximum performance mode and I'm not using the broker I should consider a sort of "external" way for archive log deletion on the physical standby?
In fact I'm setting on primary
- retention policy = redundancy 1
- archivelog deletion = applied on standby (without using any "backed up...." option)
Considering the standby it seems from docs that:
- retention policy always wins over deletion policy (so no archive eligible for deletion is deleted if retention is not satisfied)
- I can set on standby archivelog deletion = applied on standby (without using any "backed up...." option)
But it is not clear to me the effect of this config in case this is a standby itself and without any other cascade standby databases
The manual says this has to be met:
1) The archived redo log files have been applied to the required standby databases.
---> what does this mean in case the db is a standby.. met or not met as I have no other cascade standby dependant on this one?
2) The logs are not needed by the BACKED UP ... TIMES TO DEVICE TYPE deletion policy. If the BACKED UP policy is not set, then this condition is always met.
---> I should be ok
So the last question for standby is
- what to set retention policy to?
I have not understood if I set it to "NONE", this means no retention at all or retention for ever....
sometimes I read that there is no policy; in other examples that files will be retained forever (because no file considered as obsolete).... or at least so I understood...
I would like to have a sort of policy on standby where the archive logs can be deleted as soon as they are applied during the continuous media recovery phase...
It seems I can't find a self contained set of configurations across the dataguard....
Thanks in advance.
GianlucaI agree with you.... It is a temporary contingency....
I already stressed the fact that sizes between sites must be quite identical...
we are going towards a production dataguard, migrating from a windows config (without it) to a Linux based config....
but this contingency made me think about these considerations regarding policies and automatic dataguard operations
I also stressed on equal size grow capability for both sites file systems, also for data tablespaces, so that for example in case of high fragmentation we have to avoid a limit situation where
1) a file system full for DR datafiles causes abend of automatic media recovery
2) this generates FRA growth in DR because archive logs are shipped but not applied any more
3) FRA goes 100% in DR and primary cannot ship any more
4) archive logs cannot be automatically deleted on primary because not already shipped
5) FRA full on primary and DB hangs....
Thanks anyway for input -
Generate archive logs are not in sequence number?
On last friday... the latest archive log number was ARC00024.ARC. Tomorrow when I come backup, the archive logs ARC00001.ARC and ARC00002.ARC were being generated by oracle itself. I wondering the archive log sequence should be in sequence. What is happening?
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination C:\oracle\ora92\RDBMS
Oldest online log sequence 1
Next log sequence to archive 3
Current log sequence 3
SQL>
FAN
Edited by: user623471 on Jun 7, 2009 7:35 PMkhurram,
Its our production instance and havent issued resetlogs option but when listing the arvchives it shows in different sequence number...
and also while copying the archives by RMAN it doesnt copy in sequence
-rw-r----- 1 xxx dba 69363859 May 28 19:16 2_10373.arc.gz
-rw-r----- 1 xxx dba 43446622 May 28 19:16 1_10553.arc.gz
-rw-r----- 1 xxx dba 52587365 May 28 19:16 1_10578.arc.gz
-rw-r----- 1 xxx dba 45251820 May 28 19:16 1_10543.arc.gz
-rw-r----- 1 xxx dba 60890256 May 28 19:17 1_10579.arc.gz
-rw-r----- 1 xxx dba 46659008 May 28 19:17 1_10548.arc.gz
-rw-r----- 1 xxx dba 116899466 May 28 19:17 2_10353.arc.gz
-rw-r----- 1 xxx dba 77769517 May 28 19:17 1_10531.arc.gz
-rw-r----- 1 xxx dba 66401923 May 28 19:18 1_10530.arc.gz
-rw-r----- 1 xxx dba 45972697 May 28 19:18 1_10605.arc.gz
-rw-r----- 1 xxx dba 55082543 May 28 19:18 1_10600.arc.gz
-rw-r----- 1 xxxq dba 42682207 May 28 19:19 1_10547.arc.gz
thanks,
baskar.l -
Auto archive log deletion from single location out of multiple locations.
Hi,
I am running database on 11r1 version.
I have set two archive log locations. now i want archive logs to be deleted through RMAN from only one location the other location shouldn't be affected. what are the specific parameters to be set. Is there any specific command for this please advise.
Thanks in advance.If you see Hemant's reply in the below link, he had shown how to delete archives from 1 location.
RMAN backup with 2 archive log locations -
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 -
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.
ThanksHi 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 hangs up on archive logs
Hi,
in 9i on Linux, My rman backup script is :
RMAN> run {
2> allocate channel t1 type disk;
3> backup incremental level=0 format '/mnt/rman/MYDB/full_%d_%t_%s_%p' database;
4> sql 'alter system switch logfile';
5> backup format '/mnt/rman/MYDB/al_%d_%t_%s_%p'
6> archivelog all delete input;
7> backup format '/mnt/rman/MYDB/ctl_%d_%t_%s_%p' current controlfile;
8> }
It works well until :
backup format '/mnt/rman/MYDB/al_%d_%t_%s_%p' archivelog all delete input;
Here it hangs up (may be there are many many archive log files). What do you propose ? How can we ask RMAN just backup archive logs since some recent dates ? How can we delete most of ancient archive logs ? Since many times RMAN backup was in error then archive logs were not deleted. Now impossible to finish RMAN backup. Many thanks for your help.Hi,
I launched following since last night but it is always waiting :
RMAN> crosscheck archivelog all;
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=110 devtype=DISK
What can I do ? Any other way to say to RMAN that archived logs are not available ?
Many thanks.
Maybe you are looking for
-
JButton on XP non-modal Jdialog doen't work.
I recently upgraded from 1.3 to 1.4 while upgrading my OS from NT 4.0 to XP. In a stand-alone application I have non-modal JDialog's that are launched as threads so that I can have multiple instances of them running simultaneously. There are JButton'
-
Close() missing, memory leak in XMLType Support Sample [04-Mar-2003]
In the function private void viewXML() from the XMLType Support Sample [04-Mar-2003] http://www.oracle.com/technology/sample_code/tech/java/sqlj_jdbc/files/9i_jdbc/XMLTypeSample/XMLTypeSample.java.html I am missing the close() statement. I think, thi
-
I accidentally removed launchpad from my dock? what to do?
I accidentally removed launchpad from my dock? What to do now???
-
6.1 vs 10.3: between column spacing
It appears that there is a slight difference in the spacing between columns in 6.1 and 10.3 Given that we use full column width images in each of our portlets, this is now causing us to have a minor horizontal scroll in the ballpark of 10 pixels in a
-
Uninstalled Bonjour, now startup error message.
I have just set up a network using an Airport Extreme router. The users on the network all use Windows XP. The printer connected to the Airport is an HP 3050 AIO. Bonjour would see the printer but would not send print jobs. SWet the printer connectio