Delete essbase log file daily

Hi
I would like essbase to delete application log file each day,
how can I do it?
Thx

How about the CLEARLOGFILE Essbase.cfg file setting?
Setting it to TRUE will overwrite the Essbase server and application logs whenever Essbase is restarted.
Also, there's a EXCEPTIONLOGOVERWRITE setting that allows the overwrite of .xcp files.
Both of these can be found in the Technical Reference guide.
Regards,
Cameron Lackpour

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 can I delete a Log File in EM

    I created a log file in the Log Configuration from "SOA Infrastructure -> logs -> Log Configuration", but later I found I cannot remove the new created log file. There only are Create, Create Like, Edit Configuration, View Configuration options in EM. Is there any way to delete the log file? I am using SOA suite 11.1.1.3 Thanks.

    Highlight the said file on the Music section of your Library, and press the Backspace key.  When asked whether you want to move to the trash, say yes.  Then you may download it again looking in Your Account in the purchased section.

  • 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.

  • Want to delete out.log files

    Log files having a file name of {servername}-out
    n.log (where
    n is a numeric identifying separate log files) accumulate in
    great numbers in the folder, \JRun4\logs\. Some log files appear to
    expand beyond their typical 200kb size into the hundreds of
    megabyte range. We're looking for a solution that will
    automatically delete these log files before they accumulate beyond
    control.
    What might be available to handle this, such as a solution
    that will delete old log files after a certain limit is reached?
    We are running CF MX 7.02 on Window 2003 OS.

    videveloper wrote:
    > Log files having a file name of {servername}-out
    n.log (where
    n is
    > a numeric identifying separate log files) accumulate in
    great numbers in the
    > folder, \JRun4\logs\. Some log files appear to expand
    beyond their typical
    > 200kb size into the hundreds of megabyte range. We're
    looking for a solution
    > that will automatically delete these log files before
    they accumulate beyond
    > control.
    >
    > What might be available to handle this, such as a
    solution that will delete
    > old log files after a certain limit is reached?
    Did you try the JRun update:
    http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=8698aeb8
    Jochem
    Jochem van Dieten
    Adobe Community Expert for ColdFusion

  • Essbase  log files

    Does anyone know what the info codes are at the end of the various lines in the Essbase log files. eg: [Wed Oct 22 08:18:17 2003]Local/ESSBASE0///Info(1051164)- id like to understand what "info (1051164)" is

    If you have licensed the Essbase API, on your essbase server there should be an essbase\api\include folder. In that folder there should be a file called message.txt that has a list of all the codes and messages associated with them.If you have a newer version of Essbase, some of the messages are documented in greater detail in an html document in the docs folder of the Essbase server. Look for /essbase/docs/errmsgs/erhelp.htm (or something like that).Good luck,Bruce

  • 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

  • How to delete TMS log file and and request log no.

    Dear experts,
    How to delete TMS log file and and request log no...My TMS log is not deleted since 2007. Please advice
    Thnks

    You can delete them from OS level. You can delete safely the following files:
    /usr/sap/trans/log/SAP*.<SID>
    Is this you were looking for?
    Regards,
    Faisal

  • When to delete Archive Log files ? and is safe to delete ?

    Hi all,
    I have a question, my DB is running in Archive Log mode and is growing day by day, so should I delete archive log files and where i find that my which files are old and how to delete theses files, for info I also take full RMAN and export backup regularly .
    abbas

    Well, if you're not comfortable with Backup and Recovery principles, i'd advise you to first read TFM: Backup and Recovery Concept(click) for you data safety's sake.
    Anyway, just to give you a glance at what could happen, immagine suche a situation where your database is made of 5 different datafiles (whatever they are - SYSTEM, SYSAUX, UNDO, ...), controlfiles and online redo logs. If, for example your backup is done in a timeline such as:T0 : Backup datafile F1 and F2
    T1 : Backup datafile F2 and controlfile
    T2 : Backup datafile F3, F4
    T3 : Backup datafile F5
    T0' : Backup datafile F1 and F2
    T1' : Backup datafile F2 and controlfile
    T2' : Backup datafile F3, F4
    T3' : Backup datafile F5
    ...If your server crashes (for example is thrown though the 5th floor window..) in order to make a full recovery, you could proceed multiple ways.
    . Restore files from Tx' backups. Then you'd need every archived redo logs created from T0' to now in order to be able to do a full recovery.
    . Restore files from backups; T3, T0', T2' and rectreate controlfile. Then you'd need every archived redo log created from T3 (inclusive).
    . Restore Tx backup, ...
    . Restore ...
    and so on.
    What's important is that you're at least able to resynch a full-set backup. What I mean is: if you restored "T3, T0', T2' and rectreate controlfile", in order to open the database you'll absolutely need every archived redo log created between T3 and T2' inclusive. If one is missions, you won't be able to open it.
    That is the principle. Read the concept book I linked to get more infos.
    Regards,
    Yoann.

  • Delete archive log file

    hello,
    I am using oracle 10g on linux i want to delete archive log file automaticaly there is any way to do this.or anyone can tell me scripts for do this.ur help regarding this is highly appreciated
    Regard,s
    Umair Iqbal

    Hi,
    Can you please let us know why you want to delete the archive log file?
    BTW, you can use RMAN to achieve this by taking the backup of archive log and delete the original file using the following command:
    Backup archivelog all delete input;Regards

  • 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

  • Will RMAN delete archive log files on a Standby server?

    Environment:
    Oracle 11.2.0.3 EE on Solaris 10.5
    I am currently NOT using an RMAN repository (coming soon).
    I have a Primary database sending log files to a Standby.
    My Retention Policy is set to 'RECOVERY WINDOW OF 8 DAYS'.
    Question: Will RMAN delete the archive log files on the Standby server after they become obsolete based on the Retention Policy or do I need to remove them manually via O/S command?
    Does the fact that I'm NOT using an RMAN Repository at the moment make a difference?
    Couldn't find the answer in the docs.
    Thanks very much!!
    -gary

    Hello again Gary;
    Sorry for the delay.
    Why is what you suggested better?
    No, its not better, but I prefer to manage the archive. This method works, period.
    Does that fact (running a backup every 4 hours) make my archivelog deletion policy irrelevant?
    No. The policy is important.
    Having the Primary set to :
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBYBut set to "NONE" on the Standby.
    Means the worst thing that can happen is RMAN will bark when you try to delete something. ( this is a good thing )
    How do I prevent the archive backup process from backing up an archive log file before it gets shipped to the standby?
    Should be a non-issue, the archive does not move, the REDO is transported and applied. There's SQL to monitor both ( Transport and Apply )
    For Data Guard I would consider getting a copy of
    "Oracle Data Guard 11g Handbook" - Larry Carpenter (AKA Dr. Paranoid ) ISBN 978-0-07-162111-2
    Best Oracle book I've read in 10 years. Covers a ton of ground clearly.
    Also Data Guard forum here :
    Data Guard
    Best Regards
    mseberg
    Edited by: mseberg on Apr 10, 2012 4:39 PM

  • Include Delete DM log files program in a BPC process chain

    Hi All,
    We are currently referring to a 'how-to' article which deletes the data manager log files stored at the backend. There is a custom program which does this job. This program can also be scheduled as a backend job to be run periodically as per the guide.
    Our requirement is bit different.
    What we need, is it possible to create a data manager package where this program can be run by the business user. We have tried creating a BPC process chain and included a BW process type 'ABAP Program' in it. In this we are calling the custom program and also used a variant based on which the program is expected to run.
    - Created a BPC process chain by including BPC process types 'Modify Dynamically' and at the end of the process chain 'BPC clear tables (with close_mode = 0)
    Is the above a workable solution? Though the package is successful from BPC excel, it is not doing the required job for us. How to make it work from a data manager package?
    Thanks

    Hi Ramya,
    if you want to see the result it should run first.
    after adding abap program to process chain, activate it.
    now right click on process chain start --> display variant --> change selection.
    check what is the start condition, if it is nto in immediate then comback
    click on edit --> change selection
    select immediate --> unchek the periodic values. and save. come back
    again click on save. come back.
    now schedule your process chain by clikc on clock symbol.
    after successfull completion of your process chain you can check in SE16
    Regards,
    Venkatesh

  • Delete archive log files on physical standby

    I want to delete the archive log files on the phsical standby database when they were applied. The archive log files are in the flash recovery area. So i used
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
    in rman.
    My question:
    Does rman delete the archive log files immediately when they are applied or when the disk space becomes scarce?

    Hi,
    They're marked as reclaimable when applied, so they're still on the disk but when the flah recovery area will become full they'll be deleted to give space to the new one, and so...
    Loïc

  • Deleted redo log files

    hi everbody,
    i use oracle 9.2 and 3 redo log files was created when installation. Now, i could not open database because two of redo log files was deleted (that i haven't understood how deleted.) So what can i do ? recovery is possible ? if poosibel how ?
    NOTES :
    my database does not work Archive mode and give below error messages...
    Total System Global Area 126950220 bytes
    Fixed Size 453452 bytes
    Variable Size 96468992 bytes
    Database Buffers 29360128 bytes
    Redo Buffers 667648 bytes
    Database mounted.
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: 'C:\ORACLE\ORADATA\ABUZER\REDO01.LOG'

    thanks everbody. i couldn't give information because some problems was internet connections. i solved problems. i found command and info in the Oracle 8i Admin Guide documentation. first i dropped two log groups whose files are missing then recreate these these log groups with redo log files..before that i start up an new instance, but do not mount the database. after that i use commands like below :
    ALTER DATABASE DROP LOGFILE GROUP 1 ;
    ALTER DATABSE DROP LOGFILE GROUP 2 ;
    ALTER DATABASE ADD LOGFILE GROUP 1 ('C:\...\REDO01.LOG') SIZE 1020400K
    ALTER DATABASE ADD LOGFILE GROUP 2 ('C:\...\REDO02.LOG') SIZE 1020400K
    thanks everbody...

Maybe you are looking for