How to delete archive log by RMAN.

Hi All,
How to delete archive log by RMAN and what is the difference between
delete all input & all delete input in RMAN backup.

plus archivelog all delete inputYou get an error on the syntax.
"PLUS ARCHIVELOG" does not allow the "ALL" keyword.
(See "backupSpecOperand" in the RMAN Documentation of the BACKUP command syntax).
However, "DELETE INPUT" allows the optional "ALL" keyword as in "DELETE ALL INPUT" to delete from all archivelog destinations.
I guess that you have confused the "ALL" keyword in "BACKUP ARCHIVELOG" as being possible in "BACKUP .. PLUS ARCHIVELOG".
"ALL" is allowed in "BACKUP ARCHIVELOG" but not in "BACKUP .. PLUS ARCHIVELOG".
Hemant K Chitale

Similar Messages

How to delete archive log files from ASM through Grid Control

Hi
Anybody suggest me how to delete archive log files from ASM through Grid Control.
Thanks

It is important to specify both, the oracle version and os version when posting, so confusions can be avoided.
In this particular case, since you are referring to asm and grid control you could be talking about either 10gR1, 10gR2 or 11gR1; but I strongly suggest you to avoid us to be guessing. In either case, you sould go to the maintenance tab of the target database and program a scheduled 'delete noprompt obsolete;' procedure. This will purge the information stored at the Flash recovery area, which I assume you have declared inside the ASM.
~ Madrid
http://hrivera99.blogspot.com/

How to delete archive log on standby site

hi
i configured dataguard on 10g. could anyone suggest how to delete archived log on standby site..

Hi,
There is no automatic feature out-of-the-box but you have the following views:
1) Shows archive logs transfered:
select sequence#, first_time, next_time from v$archived_log order by sequence#;
2) Shows archive logs applied:
select sequence#, archived, applied from v$archived_log order by sequence#;
If you see your archivelogs applied you can safely remove archive log files from your disk. It is your decision if you keep or delete them completely.

How to delete archive logs on the standby database....in 9i

Hello,
We are planning to setup a data guard (Maximum performance configuration ) between two Oracle 9i databases on two different servers.
The archive logs on the primary servers are deleted via a RMAN job bases on a policy , just wondering how I should delete the archive logs that are shipped to the standby.
Is putting a cron job on the standby to delete archive logs that are say 2 days old the proper approach or is there a built in data guard option that would some how allow archive logs that are no longer needed or are two days old deleted automatically.
thanks,
C.

We are planning to setup a data guard (Maximum performance configuration ) between two Oracle 9i databases on two different servers.
The archive logs on the primary servers are deleted via a RMAN job bases on a policy , just wondering how I should delete the archive logs that are shipped to the standby.
Is putting a cron job on the standby to delete archive logs that are say 2 days old the proper approach or is there a built in data guard option that would some how allow archive logs that are no longer needed or are two days old deleted automatically.From 10g there is option to purge on deletion policy when archives were applied. Check this note.
*Configure RMAN to purge archivelogs after applied on standby [ID 728053.1]*
Still it is on 9i, So you need to schedule RMAN job or Shell script file to delete archives.
Before deleting archives
1) you need to check is all the archives are applied or not
2) then you can remove all the archives completed before 'sysdate-2';
RMAN> delete archvielog all completed before 'sysdate-2';
As per your requirement.

How to delete archive log file

hii,
presently i am working on oracle 10gR2 on windows server 2003.
hard disk drive is almost full.
when i execute this command
"DELETE EXPIRED ARCHIVE LOG ALL";
it give message
"specifies does not match any archive log in the recovery catalog"
how can i delete archive log files ??
Regards
Vaibhav Dixit

these are the list
RMAN> list archivelog all;
List of Archived Log Copies
Key Thrd Seq S Low Time Name
696 1 341 A 25-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_341_758982530.ARC
698 1 342 A 26-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_342_758982530.ARC
700 1 343 A 26-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_343_758982530.ARC
702 1 344 A 26-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_344_758982530.ARC
704 1 345 A 26-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_345_758982530.ARC
705 1 346 A 26-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_346_758982530.ARC
708 1 347 A 26-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_347_758982530.ARC
710 1 348 A 27-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_348_758982530.ARC
712 1 349 A 27-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_349_758982530.ARC
714 1 350 A 27-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_350_758982530.ARC
716 1 351 A 28-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_351_758982530.ARC
719 1 352 A 28-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_352_758982530.ARC
720 1 353 A 28-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_353_758982530.ARC
721 1 354 A 28-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_354_758982530.ARC
722 1 355 A 28-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_355_758982530.ARC
727 1 356 A 29-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_356_758982530.ARC
728 1 357 A 29-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_357_758982530.ARC
730 1 358 A 29-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_358_758982530.ARC
732 1 359 A 29-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_359_758982530.ARC
734 1 360 A 29-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_360_758982530.ARC
736 1 361 A 30-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_361_758982530.ARC
738 1 362 A 30-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_362_758982530.ARC
740 1 363 A 30-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_363_758982530.ARC
741 1 364 A 30-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_364_758982530.ARC
742 1 365 A 30-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_365_758982530.ARC
743 1 366 A 30-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_366_758982530.ARC
744 1 367 A 30-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_367_758982530.ARC
745 1 368 A 30-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_368_758982530.ARC
746 1 369 A 30-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_369_758982530.ARC
753 1 370 A 30-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_370_758982530.ARC
756 1 371 A 01-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_371_758982530.ARC
758 1 372 A 01-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_372_758982530.ARC
759 1 373 A 01-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_373_758982530.ARC
763 1 374 A 01-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_374_758982530.ARC
764 1 375 A 02-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_375_758982530.ARC
767 1 376 A 02-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_376_758982530.ARC
768 1 377 A 02-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_377_758982530.ARC
770 1 378 A 02-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_378_758982530.ARC
772 1 379 A 02-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_379_758982530.ARC
774 1 380 A 02-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_380_758982530.ARC
776 1 381 A 03-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_381_758982530.ARC
778 1 382 A 03-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_382_758982530.ARC
780 1 383 A 03-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_383_758982530.ARC
782 1 384 A 03-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_384_758982530.ARC
784 1 385 A 04-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_385_758982530.ARC
785 1 386 A 04-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_386_758982530.ARC
788 1 387 A 05-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_387_758982530.ARC
790 1 388 A 05-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_388_758982530.ARC
791 1 389 A 05-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_389_758982530.ARC
792 1 390 A 05-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_390_758982530.ARC
793 1 391 A 06-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_391_758982530.ARC
794 1 392 A 06-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_392_758982530.ARC
795 1 393 A 06-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_393_758982530.ARC
796 1 394 A 06-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_394_758982530.ARC
797 1 395 A 06-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_395_758982530.ARC
798 1 396 A 06-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_396_758982530.ARC
799 1 397 A 06-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_397_758982530.ARC
800 1 398 A 06-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_398_758982530.ARC
801 1 399 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_399_758982530.ARC
802 1 400 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_400_758982530.ARC
803 1 401 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_401_758982530.ARC
804 1 402 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_402_758982530.ARC
805 1 403 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_403_758982530.ARC
806 1 404 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_404_758982530.ARC
808 1 405 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_405_758982530.ARC
814 1 406 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_406_758982530.ARC
816 1 407 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_407_758982530.ARC
817 1 408 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_408_758982530.ARC
822 1 409 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_409_758982530.ARC
823 1 410 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_410_758982530.ARC
824 1 411 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_411_758982530.ARC
826 1 412 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_412_758982530.ARC
829 1 413 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_413_758982530.ARC
831 1 414 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_414_758982530.ARC
839 1 415 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_415_758982530.ARC
841 1 416 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_416_758982530.ARC
843 1 417 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_417_758982530.ARC
844 1 418 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_418_758982530.ARC
848 1 419 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_419_758982530.ARC
849 1 420 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_420_758982530.ARC
850 1 421 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_421_758982530.ARC
851 1 422 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_422_758982530.ARC
852 1 423 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_423_758982530.ARC
853 1 424 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_424_758982530.ARC
854 1 425 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_425_758982530.ARC
856 1 426 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_426_758982530.ARC
862 1 427 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_427_758982530.ARC
870 1 428 A 09-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_428_758982530.ARC
872 1 429 A 09-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_429_758982530.ARC
874 1 430 A 09-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_430_758982530.ARC
875 1 431 A 09-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_431_758982530.ARC
878 1 432 A 09-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_432_758982530.ARC
880 1 433 A 09-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_433_758982530.ARC
882 1 434 A 10-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_434_758982530.ARC
884 1 435 A 10-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_435_758982530.ARC
886 1 436 A 10-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_436_758982530.ARC
888 1 437 A 10-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_437_758982530.ARC
890 1 438 A 11-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_438_758982530.ARC
891 1 439 A 11-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_439_758982530.ARC
893 1 440 A 12-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_440_758982530.ARC
896 1 441 A 12-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_441_758982530.ARC
898 1 442 A 12-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_442_758982530.ARC
900 1 443 A 12-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_443_758982530.ARC
901 1 444 A 12-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_444_758982530.ARC
902 1 445 A 13-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_445_758982530.ARC
903 1 446 A 13-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_446_758982530.ARC
904 1 447 A 13-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_447_758982530.ARC
910 1 448 A 13-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_448_758982530.ARC
912 1 449 A 13-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_449_758982530.ARC
914 1 450 A 13-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_450_758982530.ARC
916 1 451 A 13-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_451_758982530.ARC
918 1 452 A 13-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_452_758982530.ARC
920 1 453 A 13-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_453_758982530.ARC
922 1 454 A 13-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_454_758982530.ARC
924 1 455 A 14-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_455_758982530.ARC
926 1 456 A 14-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_456_758982530.ARC
RMAN> delete noprompt expired archivelog all;
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=77 devtype=DISK
specification does not match any archive log in the recovery catalog

How to delete archived log file in rman

Hi friends,
I got a series list of archived log validation failed by crosscheck.
How can I delete these files to release space?
Thanks for help!
Jimmy

user589812 wrote:
Thanks for your help!
RMAN> report obsolete;
RMAN> DELETE OBSOLETE;
these twon way does not work. the fail backup is still in backup report by EM
How do I get a backup set number?
JIm
Edited by: user589812 on Nov 17, 2008 2:52 PMDELETE OBSOLETE deletes the backups that are no longer needed to meet the recovery policy.
DELETE EXPIRED deletes backups that are found (through a CROSSCHECK) to no longer exist - usually because the files were deleted outside of rman.
Documentation is at tahiti.oracle.com

How to delete archive log entries from catalog?

Some old, not needed archive logs are deleted from disk using OS commands but RMAN catalog still lists them.
How can I get rid of them in RMAN?

First mark them expired
crosscheck archivelog all;then delete them from the RMAN catalog
delete expired archivelog all;Cheers

HELP....How to delete archive log from v$archived_log table...

Hi All
Our prod database was running in Archive log mode and now it is in NO Archive log mode. I deleted all archive logs from the disk but I can still see them in v$archived_log table. How do I delete them from this table.
Environment is Oracle8i(8.1.7) running on Windows 2000 Advanced Server.
Thank you
Amit

Hi,
Recreating the controlfile is the only way to force a cleanup of all entries in v$archived_log.
You can see information on Metalink Note:1012929.6
Paolo

How to restore archive logs with rman

Hi,
here is the scenario:
we have lost everything because of disk failure.
we have a full cold backup and archivelog backups which were created after cold backup and were backed up with rman.
after restoring from cold backup, because archivelog backups do not exist in controlfile, how can we catalog archivelog backups and restore them?
could you give me the exact rman command for this?
Best Regards,
Kamil

cold backup means offline backup, you shut database normally and copy datafiles to another location.
i think operating system does not matter that much but it is RedHat Linux Enterprise Server.
backing up archivelogs whith rman script which is:
run {
allocate channel c1 type disk format '$BKUPLOC/arch_%d_%u_%s_%p.bkp';
change archivelog all validate;
sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
backup archivelog time between 'SYSDATE - (30*60/(60*60*24))' and 'sysdate';
release channel c1;
so here is the details.
1. because everything is lost, we restored all files(datafiles, controlfiles, redologs etc) from offline backup meaning copied all files from another location to corresponding location.
2. want to apply archive logs which were created after cold backup till disk failure and we have these archive logs with backups which were taken by rman.
So
first of all, we want to register these archive log rman backups(because these backup information does not exist in restored controlfile)
and then restore them and then apply them.
we need rman commands to register these backups and restore them.
Regards,
Kamil

How to delete Archive log files in ASM?

Hi,
Env: Sun Solaris
10.2.0.2.0 RAC with 2 node cluster
using ASM
I noticed that there are directories for ARCHIVELOG for every day.
for example:
2007_01_13/
2007_01_29/
ASMCMD> pwd
+DG01/<<INSTANCENAME>>/ARCHIVELOG
a) How to purge these files/directories automatically?
b) We use RMAN for backup. Not sure if these directories are created by RMAN
Thanks

Natrajan,
Since I don't remember what exactly I did which caused stopping those folder from being created, this is what I would try.
You have mentioned that these folder are being created at
"+DG01/<<INSTANCENAME>>/ARCHIVELOG" in your first post. Is this the same location what you set at init/spfile.ora ?
"*.log_archive_dest_1='LOCATION=+<<DISKNAME?>/<<DBNAEM>>/'"
If yes please change one of the nodes
node1.log_arch_dest_1 to some where else which is not the current location. Then watch whether these directories being created at this location. If they are not created we have an answer what causing this folder creation.
This is just a suggestion.
Do you see the filename inside these foloder somewhat in this pattern
"o1_mf_1_9403_2pxpr9dw_.arc"
Let me know what you think? Again it is just a suggestion I really don't know the answer.
Thanks
Leo

When to delete archive logs- using rman 10.1.0.5

Hello,
I am using rman to backup my database(10.1.0.5) along with backing up the archivelogs delete input. The retention of the backup is set to 1. I am backing the datafiles and archivelogs to disk /backupdata. I noticed that the /backupdata is filling up with a lot of backup archivelogs. Since the retention of the database is set to 1, does that mean that rman will also clean the archivelogs in /backupdata too? What I am asking is, since the retention is set to 1, does rman automatically determine witch archivelogs in the /backupdata to delete if rman determines that the archivelogs is not needed to satisfied the retention 1 condition??? Thank you in advance.

rman won't automatically purge your backups. Retention policy can be defined to be 1 (what?) redundancy copies or recovery window?
You may have defined, let's say 1 redundant copy, which means you must have at least one backup to consider the other obsolete, and you will keep one redundant copy. The other backups are not automatically deleted, they are just marked obsolete, and you can delete them.
I suggest you to manually purge your backups, as they will fill up your storage. issue, from a recovery manager session:
rman> report obsolete;
rman > delete noprompt obsolete;
rman> report obsolete;
The delete noprompt obsolete will physically purge all backups reported as obsolete by the first command. You can confirm actions from the last command.
I suggest you to perform a periodic task to purge obsolete backups, schedule last command, it can be done once your regular backup ends.
If you have Enterprise manager DB Control console enabled, it can be scheduled using the internal scheduler, and it can be monitored from within EM.
~ Madrid.

Deletion of archive log using RMAN Target in Oracle 10g

Hi All,
I recently have noticed that the archive logs have occupied 102 GBs out of the drive and I need to free up some space. When I tried to connect RMAN Catalog using
connect catalog user@dbI got error message as
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-06445: cannot connect to recovery catalog after NOCATALOG has been usedBut I was able to get through using
connect target user@dbMy Query is can I use
RMAN> delete noprompt expired archivelog all;as given in [how to delete archive log file |https://forums.oracle.com/forums/thread.jspa?threadID=2321257&start=0&tstart=0]
Or shall I take any other approach to delete the obsolete archive logs?
Regards,
*009*

Hello;
I recently have noticed that the archive logs have occupied 102 GBs out of the drive and I need to free up some space. When I tried to connect RMAN Catalog using
connect catalog user@dbI got error message as
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-06445: cannot connect to recovery catalog after NOCATALOG has been usedBut I was able to get through using
connect target user@db
Are you trying to connect it through Grid control ? If connecting through a script, then please post its contents.
Make sure you are not connecting to the target database using "nocatalog".
rman target sys/<pwd_of_target>@<target_db> catalog <catalog_schema>/<catalog_schema_pwd>@<catalog_db>
My Query is can I use
RMAN> delete noprompt expired archivelog all;
as given in [how to delete archive log file |https://forums.oracle.com/forums/thread.jspa?threadID=2321257&start=0&tstart=0]
Or shall I take any other approach to delete the obsolete archive logs?
Regards,
*009*Are these archives backed up ? The above command only updates the RMAN repository if in case the archives were delete manually at OS level.
I would recommend you to backup these archives and then delete them.
RMAN>backup archivelog all not backedup 1 times delete input;If these archives are already backed up and have not been deleted from the disk, then you can use the below command
RMAN>delete force noprompt archivelog all completed before 'SYSDATE-n';where "n" is the number of days behind the current date. Make sure to verify if these archives have been backed up before deleting.
Regards,
Shivananda

How can we delete archive log files from OEM

Hi,
I took backup of the archive log file and deleted it at OS level but in it is not reflecting in the EM can any one tell me how to delete archive log files from OEM.
any help will be appreciated.
Regards,
Ashraf

This link?
http://download-west.oracle.com/docs/cd/B10501_01/em.920/a96670/ch_backp.htm#26936

Is RMAN only way to take backup and delete Archive Logs?

On primary db:
===============
OS: Windows 2003 server 32-bit
Oracle: Oracle 10g (10.2.0.1.0) R2 32-bit
On Physical standby db:
===============
OS: Windows 2003 server 32-bit
Oracle: Oracle 10g (10.2.0.1.0) R2 32-bit
Data Guard just configured. Archive Logs are properly being shipped to standby db. Is RMAN only way to take backup and delete Archive Logs from both primary and standby db? What other command can be used?
Thanks

No, but anything else is way more work. Without using RMAN you would have to find another way to keep track of applied logs.
RMAN make this very simple :
RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;Using another method would be like using the handle of your screwdriver as a hammer.
See "RMAN Recipes for Oracle Database 11g" ISBN 978-1-5959-851-1
Best Regards
mseberg

Manual delete archived log files

Because we don't have RMAN in our development server, I need to use manual operation to delete all archived logs. Is my procedure correct and safe?
SHUTDOWN IMMEDIATE
STARTUP MOUNT
ALTER DATABASE NOARCHIVELOG;
EXITRun OS command to manually delete archived log files:
rm /oradata/arch/*
Login to sqlplus
SHUTDOWN IMMEDIATE
STARTUP MOUNT
ALTER DATABASE ARCHIVELOG;
STARTUP OPENThanks!

linuxos wrote:
Oh I suppose RMAN need to be configured somthing before use. I tried it, and find no pre-requisite is required. Thanks!
If the archives are deleted manually in open mode, how can Oracle match the archived logs' retention policy? Does Oracle store the archived logs in data dictionary?While you can delete archivelogs manually any time you want, you should let rman manage them with appropriate rman commands, preferably in a script that you schedule for regular execution.
Some of your questions lead me to question if you understand that archivelogs are not actively open by the database, and they technically are not part of the database. They are simply a series of "offline" copies of the online redo logs. They are written to once, when an online redo is being archived, then they just sit there until needed for a recovery.

How to delete archive log by RMAN.

Similar Messages

Maybe you are looking for