Workflow logs - Delete or Archive?

Hello
The tables SWW_*, SWWWIHEAD, SWWLOGHIST, SWPNODELOG, SWPSTEPLOG are growing rapidly in our system, totalling over 100 GB.  We are considering archiving/deleting old work items, i.e. older than three months that are in status completed.
What are the risks in terms of data integrity / auditability when deleting these logs, in other words, do we have to archive the old work items or can we simply dleete them?
Thanks
Wilhelm

Hi,
Check the T.code SARA.
Refer [Link|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/3643cdbb-0601-0010-c89d-c069bc395909].
Regards,
Surjith

Similar Messages

  • How to find out who deleted the archive logs

    Hi All,
    Recently some archive logs were deleted from one of our servers. Is there any way to find out which user has deleted the archive logs through OS or through database ?
    OS Version :-
    SunOS Generic_Virtual sun4u sparc SUNW,SPARC-Enterprise
    Database Version:-
    SQL*Plus: Release 9.2.0.8.0 - Production on Mon Apr 9 01:12:15 2012

    888132 wrote:
    Hi All,
    Recently some archive logs were deleted from one of our servers. Is there any way to find out which user has deleted the archive logs through OS or through database ?
    OS Version :-
    SunOS Generic_Virtual sun4u sparc SUNW,SPARC-Enterprise
    Database Version:-
    SQL*Plus: Release 9.2.0.8.0 - Production on Mon Apr 9 01:12:15 2012As explained by others, from oracle database there is no record if they are deleted from OS.
    But you can probably find the history of OS command been run with history command :). You can get the date and time.
    Following link can help
    http://stackoverflow.com/questions/99755/how-do-i-get-the-command-buffer-in-solaris-10
    http://www.cyberciti.biz/faq/unix-linux-bash-history-display-date-time/
    http://www.linuxquestions.org/questions/solaris-opensolaris-20/in-solaris-command-line-how-to-get-the-previous-commands-573814/
    But i suggest you to post in Sun OS forum to get more details as its nothing to do with Database(in this scenario)

  • *HOW TO DELETE THE ARCHIVE LOGS ON THE STANDBY*

    HOW TO DELETE THE ARCHIVE LOGS ON THE STANDBY
    I have set the RMAN CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY; on my physical standby server.
    My archivelog files are not deleted on standby.
    I have set the CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default on the Primary server.
    I've checked the archivelogs with the FRA and they are not beign deleted on the STANDBY. Do I have to do something for the configuation to take effect? Like run a RMAN backup?
    I've done a lot ofresearch and i'm getting mixed answers. Please help. Thanks in advanced.
    J

    Setting the Policy will not delete the Archive logs on the Standby. ( I found a thread where the Data Guard product manager says "The deletion policy on both sides will do what you want" ). However I still
    like to clean them off with RMAN.
    I would use RMAN to delete them so that it can use that Policy are you are protected in case of Gap, transport issue etc.
    There are many ways to do this. You can simply run RMAN and have it clean out the Archive.
    Example :
    #!/bin/bash
    # Name: db_rman_arch_standby.sh
    # Purpose: Database rman backup
    # Usage : db_rman_arch_standby <DBNAME>
    if [ "$1" ]
    then DBNAME=$1
    else
    echo "basename $0 : Syntax error : use . db_rman_full <DBNAME> "
    exit 1
    fi
    . /u01/app/oracle/dba_tool/env/${DBNAME}.env
    echo ${DBNAME}
    MAILHEADER="Archive_cleanup_on_STANDBY_${DBNAME}"
    echo "Starting RMAN..."
    $ORACLE_HOME/bin/rman target / catalog <user>/<password>@<catalog> << EOF
    delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-8';
    exit
    EOF
    echo `date`
    echo
    echo 'End of archive cleanup on STANDBY'
    mailx -s ${MAILHEADER} $MAILTO < /tmp/rmandbarchstandby.out
    # End of ScriptThis uses ( calls an ENV) so the crontab has an environment.
    Example ( STANDBY.env )
    ORACLE_BASE=/u01/app/oracle
    ULIMIT=unlimited
    ORACLE_SID=STANDBY
    ORACLE_HOME=$ORACLE_BASE/product/11.2.0.2
    ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data
    LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib
    LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib
    LIBPATH=$LD_LIBRARY_PATH:/usr/lib
    TNS_ADMIN=$ORACLE_HOME/network/admin
    PATH=$ORACLE_HOME/bin:$ORACLE_BASE/dba_tool/bin:/bin:/usr/bin:/usr/ccs/bin:/etc:/usr/sbin:/usr/ucb:$HOME/bin:/usr/bin/X11:/sbin:/usr/lbin:/GNU/bin/make:/u01/app/oracle/dba_tool/bin:/home/oracle/utils/SCRIPTS:/usr/local/bin:.
    #export TERM=linux=80x25 wrong wrong wrong wrong wrong
    export TERM=vt100
    export ORACLE_BASE ORACLE_SID ORACLE_TERM ULIMIT
    export ORACLE_HOME
    export LIBPATH LD_LIBRARY_PATH ORA_NLS33
    export TNS_ADMIN
    export PATH
    export MAILTO=?? your email hereNote use the env command in Unix to get you settings.
    There are probably ten other/better ways to do this, but this works.
    other options ( you decide )
    Configure RMAN to purge archivelogs after applied on standby [ID 728053.1]
    http://www.oracle.com/technetwork/database/features/availability/rman-dataguard-10g-wp-1-129486.pdf
    Maintenance Of Archivelogs On Standby Databases [ID 464668.1]
    Tip I don't care myself but in some of the other forums people seem to mind if you use all caps in the subject. They say it shouting. My take is if somebody is shouting at me I'm probably going to just move away.
    Best Regards
    mseberg
    Edited by: mseberg on May 8, 2012 11:53 AM
    Edited by: mseberg on May 8, 2012 11:56 AM

  • Logical standby | archive log deleted | how to remove gap ???

    hi gurus...
    i have problem on logical standby
    by mistake standby log coming to logical standby has been deleted , now how to fill up the gap ???
    ON STANDBY
    SEQUENCE# FIRST_CHANGE# NEXT_CHANGE# APPLIED
    228 674847 674872 YES
    229 674872 674973 CURRENT
    230 674973 674997 NO
    231 674997 675023 NO
    232 675023 675048 NO
    233 675048 675109 NO
    234 675109 675135 NO
    235 675135 675160 NO
    236 675160 675183 NO
    237 675183 675208 NO
    238 675208 675232 NO
    239 675232 675257 NO
    240 675257 675282 NO
    241 675282 675382 NO
    242 675382 675383 NO
    243 675383 675650 NO
    244 675650 675652 NO
    245 675652 675670 NO
    246 675670 675688 NO
    247 675688 675791 NO
    248 675791 678524 NO
    archive log are shipping to standby location also and getting registered
    ALERT LOG OF STANDBY
    Fri May 7 12:25:36 2010
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[21]: Successfully opened standby log 5: '/u01/app/oracle/oradata/BEST/redo05.log'
    Fri May 7 12:25:37 2010
    RFS LogMiner: Registered logfile [u01/app/oracle/flash_recovery_area/BEST/archivelog/archBEST_248_1_715617824.dbf] to LogMiner session id [1]
    but i dont have standby log after 229 sequence ...
    ON PRIMARY
    SYS@TEST AS SYSDBA> archive log list
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination /u01/app/oracle/flash_recovery_area/TEST/standlogOldest online log sequence 247
    Next log sequence to archive 249
    Current log sequence 249
    what to do next to apply sequences and bring both in sync.
    please help me ,,,,
    Edited by: user12281508 on May 7, 2010 9:45 AM

    thanks for response.
    no its pure logical standby
    i have tried to ftp the archive logs of primary to standby and applied manually
    SYS@BEST AS SYSDBA> alter database register logfile '/u01/app/oracle/flash_recovery_area/BEST/archivelog/archBEST_230_1_715617824.dbf';
    alter database register logfile '/u01/app/oracle/flash_recovery_area/BEST/archivelog/archBEST_230_1_715617824.dbf'
    ERROR at line 1:
    ORA-01289: cannot add duplicate logfile
    SYS@BEST AS SYSDBA> alter database register logfile '/u01/app/home/archTEST_230_1_715617824.dbf';
    alter database register logfile '/u01/app/home/archTEST_230_1_715617824.dbf'
    ERROR at line 1:
    ORA-01289: cannot add duplicate logfile
    any other way ????

  • Question about Archive Log Deletion policy

    I've a problem to understand the Archive Log Deletion policy, and I I'd like to this problem explain with the following example.
    Messages of the database are in German, but I guess you'll understand them.
    SQL> startup
    ORACLE-Instance hochgefahren.
    Total System Global Area 5344731136 bytes
    Fixed Size                  2129240 bytes
    Variable Size            2684355240 bytes
    Database Buffers         2617245696 bytes
    Redo Buffers               41000960 bytes
    Datenbank mounted.
    Datenbank geöffnet.
    SQL> archive log list
    Datenbank-Log-Modus              Archive-Modus
    Automatische Archivierung             Aktiviert
    Archivierungsziel            E:\oracle\thetis_iv\arch
    Älteste Online-Log-Sequenz     17917
    Nächste zu archivierende Log-Sequenz   17919
    Aktuelle Log-Sequenz           17919
    SQL> alter system switch logfile;
    System wurde geändert.I created a brand new archive log.
    SQL> exit
    Verbindung zu Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options beendet
    D:\OracleDB\product\11.1.0\db_1\BIN>dir E:\oracle\thetis_iv\arch
    Datenträger in Laufwerk E: ist Volume
    Volumeseriennummer: 3EBD-77E5
    Verzeichnis von E:\oracle\thetis_iv\arch
    06.04.2011  15:04    <DIR>          .
    06.04.2011  15:04    <DIR>          ..
    06.04.2011  15:04        17.137.152 ARC17919_0721667907.001
                   1 Datei(en),     17.137.152 Bytes
                   2 Verzeichnis(se), 41.073.258.496 Bytes freiand this is the only archive log in the directory. Now I start rman:
    D:\OracleDB\product\11.1.0\db_1\BIN>rman target / catalog rmanrepo@rmanrepo
    Recovery Manager: Release 11.1.0.7.0 - Production on Mi Apr 6 15:05:35 2011
    Copyright (c) 1982, 2007, Oracle.  All rights reserved.
    Mit Ziel-Datenbank verbunden: ENTWIV (DBID=21045568)
    Kennwort für Recovery-Katalog-Datenbank:
    Verbindung mit Datenbank des Recovery-Katalogs
    RMAN> show all;
    RMAN-Konfigurationsparameter für Datenbank mit db_unique_name ENTWIV sind:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
    CONFIGURE CONTROLFILE AUTOBACKUP OFF;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'E:\oracle\thetis_iv\backup\CF_%F_ENTWIV.ORA';
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
    CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS  'ENV=(TPDO_OPTFILE=D:\Services\Tivoli\TSM\AgentOBA64\tpdo.opt)';
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE COMPRESSION ALGORITHM 'BZIP2'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO 'SBT_TAPE';
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLEDB\PRODUCT\11.1.0\DB_1\DATABASE\SNCFENTWIV.ORA'; # defaultThe archive log deletion policy says the the logfiles have to be backed up for two times before they get deleted.
    Now I backup all archive logs, that havn't been backed up for at least two times.
    RMAN> run { backup archivelog all not backed up 2 times
    2>       format '%d_AR_%Y%M%D_%s_%t'
    3>       tag 'ARCHIVE LOGS'
    4>       DELETE ALL INPUT;
    5>     }
    Starten backup um 06.04.2011 15:08:01
    Aktuelles Log archiviert
    Zugewiesener Kanal: ORA_SBT_TAPE_1
    Kanal ORA_SBT_TAPE_1: SID=253 Device-Typ=SBT_TAPE
    Kanal ORA_SBT_TAPE_1: Data Protection for Oracle: version 5.5.1.0
    Kanal ORA_SBT_TAPE_1: Backup Set für Archive Log wird begonnen
    Kanal ORA_SBT_TAPE_1: Archive Logs in Backup Set werden angegeben
    Eingabe-Archive-Log-Thread=1 Sequence=17919 RECID=147 STAMP=747759899
    Eingabe-Archive-Log-Thread=1 Sequence=17920 RECID=148 STAMP=747760081
    Kanal ORA_SBT_TAPE_1: Piece 1 wird auf 06.04.2011 15:08:02 begonnen
    Kanal ORA_SBT_TAPE_1: Piece 1 auf 06.04.2011 15:08:09 beendet
    Piece Handle=ENTWIV_AR_20110406_23_747760082 Tag=ARCHIVE LOGS Kommentar=API Version 2.0,MMS Version 5.5.1.0
    Kanal ORA_SBT_TAPE_1: Backup Set vollstõndig, abgelaufene Zeit: 00:00:08
    Kanal ORA_SBT_TAPE_1: Archive Logs werden gel÷scht
    Archive Log-Dateiname=E:\ORACLE\THETIS_IV\ARCH\ARC17919_0721667907.001 RECID=147 STAMP=747759899
    Archive Log-Dateiname=E:\ORACLE\THETIS_IV\ARCH\ARC17920_0721667907.001 RECID=148 STAMP=747760081
    Beendet backup um 06.04.2011 15:08:10
    RMAN> exit
    Recovery Manager abgeschlossen.
    D:\OracleDB\product\11.1.0\db_1\BIN> dir E:\oracle\thetis_iv\arch
    Datenträger in Laufwerk E: ist Volume
    Volumeseriennummer: 3EBD-77E5
    Verzeichnis von E:\oracle\thetis_iv\arch
    06.04.2011  15:08    <DIR>          .
    06.04.2011  15:08    <DIR>          ..
                   0 Datei(en),              0 Bytes
                   2 Verzeichnis(se), 41.090.396.160 Bytes freirman deleted all archive logs, even I they are on tape only once by now.
    Thats not what I expected. Where is my mistake?

    Hi,
    I do new tests it's very strange.
    BACKUP ARCHIVELOG command is not obeying the policy of archivelog.
    You can open a SR on MOS. (to check bugs)
    I reproduce the same test and the result was the same, it seems that this is a bug.
    CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO DISK;
    RMAN> backup archivelog all not backed up 2 times delete all input;
    Starting backup at 06-APR-11
    current log archived
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting archived log backup set
    channel ORA_DISK_1: specifying archived log(s) in backup set
    input archived log thread=1 sequence=15 RECID=16 STAMP=747753711
    input archived log thread=2 sequence=20 RECID=17 STAMP=747753714
    input archived log thread=1 sequence=16 RECID=19 STAMP=747753729
    input archived log thread=2 sequence=21 RECID=18 STAMP=747753729
    channel ORA_DISK_1: starting piece 1 at 06-APR-11
    channel ORA_DISK_1: finished piece 1 at 06-APR-11
    piece handle=+DATA/orcl/backupset/2011_04_06/annnf0_tag20110406t132210_0.304.747753731 tag=TAG20110406T132210 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    channel ORA_DISK_1: deleting archived log(s)
    archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_1_seq_15.293.747753711 RECID=16 STAMP=747753711
    archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_2_seq_20.295.747753715 RECID=17 STAMP=747753714
    archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_1_seq_16.294.747753729 RECID=19 STAMP=747753729
    archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_2_seq_21.298.747753729 RECID=18 STAMP=747753729
    Finished backup at 06-APR-11
    RMAN> list archivelog all;
    specification does not match any archived log in the repositoryOracle Docs Says:
    The BACKUP ARCHIVELOG ... DELETE INPUT command deletes archived log files after they are backed up.
    This command eliminates the separate step of manually deleting archived redo logs.
    With DELETE INPUT, RMAN deletes only the specific copy of the archived log chosen for the backup set.
    With DELETE ALL INPUT, RMAN deletes each backed-up archived redo log file from all log archiving destinations.
    As explained in "Configuring an Archived Redo Log Deletion Policy",
    the BACKUP ... DELETE INPUT and DELETE ARCHIVELOG commands obey the archived redo log deletion policy
    for logs in all archiving locations. For example, if you specify that logs should only be deleted when backed
    up at least twice to tape, then BACKUP ... DELETE honors this policy.http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmbckba.htm#BRADV89524
    But in ours case it's not honors this policy.
    Only with the FORCE command should this happen. But it is not our case.
    Oracle Docs:
    If FORCE is not specified on the deletion commands,
    then these deletion commands obey the archived log deletion policy.
    If FORCE is specified, then the deletion commands ignore the archived log deletion policy.http://download.oracle.com/docs/cd/E11882_01/backup.112/e10643/rcmsynta010.htm#RCMRF113
    Alternatively you can do the following:
    Set the commands separately.
    Check this:
    RMAN>  run {
    2> backup archivelog all not backed up 2 times ;
    3> delete archivelog all backed up 2 times to disk;
    4> }
    Starting backup at 06-APR-11
    current log archived
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting archived log backup set
    channel ORA_DISK_1: specifying archived log(s) in backup set
    input archived log thread=2 sequence=22 RECID=21 STAMP=747755128
    input archived log thread=1 sequence=17 RECID=20 STAMP=747755127
    channel ORA_DISK_1: starting piece 1 at 06-APR-11
    channel ORA_DISK_1: finished piece 1 at 06-APR-11
    piece handle=+DATA/orcl/backupset/2011_04_06/annnf0_tag20110406t134528_0.295.747755129 tag=TAG20110406T134528 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    Finished backup at 06-APR-11
    released channel: ORA_DISK_1
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=78 instance=orcl1 device type=DISK
    RMAN-08138: WARNING: archived log not deleted - must create more backups
    archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_1_seq_17.298.747755127 thread=1 sequence=17
    RMAN-08138: WARNING: archived log not deleted - must create more backups
    archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_2_seq_22.294.747755129 thread=2 sequence=22
    RMAN>Edited by: Levi Pereira on Apr 6, 2011 1:35 PM

  • RMAN-08591: WARNING: invalid archived log deletion policy

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

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

  • Script for automatic delete of archive logs/redologs

    Hi Experts,
    Do you have any idea on how to create a shell script. Actually the function of it, is to automatically deletes the archive logs/redologs if reaches the limit. Or is there any parameter to change to set the automatic deletion of archive logs/redologs.
    Regards

    Hi,
    at first, archivelogs should always be saved to tape before you delete them. If you don't want to backup them, may be for a test system, you can suppress them in ORACLE instead to delete them later.
    You can run the database in "NOARCHIVE LOG MODE". If you do so, the online redologs are not archived, they are still reused and overwritten. You can not run an online Backup, when the database is in noarchive log mode. If you want to backup the database, you have to run an offline backup.
    Do not use the NOARCHIVE LOG MODE for production or developemet systems.
    To change the archive log mode:
    shutdown the database
    startup mount;
    alter database noarchivelog;
    alter database open;
    archive log list       will show the actual status
    regards Ulrich

  • How to delete the archive logs.

    Hi,
    I need to delete the archive logs in standby database which has been generated after created the restore point.
    SEQUENCE# APPLIED
    17 YES
    18 YES
    1 NO
    2 NO
    19 YES
    18 YES
    21 YES
    22 YES
    20 YES
    23 YES
    24 YES
    sequence 1,2 has been generated after created the restore point,how can i remove sequence# 1 and 2 from the v$archived_log;
    ways i have tried
    1.dropped the restore point during that time only the flashback logs has been deleted not the archive log
    2.manually tried from rman ,but i was not working.
    please help me out....
    ***points are waiting for you guys****

    Hi,
    I need to delete the archive logs in standby database which has been generated after created the restore point.
    SEQUENCE# APPLIED
    17 YES
    18 YES
    1 NO
    2 NO
    19 YES
    18 YES
    21 YES
    22 YES
    20 YES
    23 YES
    24 YES
    sequence 1,2 has been generated after created the restore point,how can i remove sequence# 1 and 2 from the v$archived_log;
    ways i have tried
    1.dropped the restore point during that time only the flashback logs has been deleted not the archive log
    2.manually tried from rman ,but i was not working.
    please help me out....
    ***points are waiting for you guys****

  • Archive log deletion

    Hello,
    -rw-r----- 1 oracle dba 193739264 Jun 22 13:23 1_5_754473298.dbf
    -rw-r----- 1 oracle dba 193052160 Jun 22 15:00 1_6_754473298.dbf
    -rw-r----- 1 oracle dba 492818944 Jun 22 16:14 2_161956_733073720.dbf
    -rw-r----- 1 oracle dba 491902976 Jun 22 16:14 2_161955_733073720.dbf
    -rw-r----- 1 oracle dba 193459200 Jun 22 16:14 2_161957_733073720.dbf
    -rw-r----- 1 oracle dba 193587200 Jun 22 16:14 2_161958_733073720.dbf
    -rw-r----- 1 oracle dba 193142272 Jun 22 16:14 2_161959_733073720.dbf
    rw-r----- 1 oracle dba 1024 Jun 23 23:17 1_56660_733073720.dbf
    -rw-r----- 1 oracle dba 196693504 Jun 23 23:17 2_163084_733073720.dbf
    -rw-r----- 1 oracle dba 493167104 Jun 23 23:18 2_163085_733073720.dbf
    -rw-r----- 1 oracle dba 492434944 Jun 23 23:19 2_163086_733073720.dbf
    -rw-r----- 1 oracle dba 226295808 Jun 24 04:07 c-1981727300-20110624-00
    -rw-r----- 1 oracle dba 226263040 Jun 24 10:09 52mfm6c2_1_1
    -rw-r----- 1 oracle dba 491752448 Jun 26 23:29 2_164881_733073720.dbf
    -rw-r----- 1 oracle dba 192917504 Jun 26 23:31 2_164882_733073720.dbf
    -rw-r----- 1 oracle dba 1024 Jun 26 23:31 1_57258_733073720.dbf
    -rw-r----- 1 oracle dba 193144320 Jun 26 23:32 2_164883_733073720.dbf
    -rw-r----- 1 oracle dba 193007616 Jun 26 23:34 2_164884_733073720.dbf
    -rw-r----- 1 oracle dba 194516480 Jun 27 23:48 2_165577_733073720.dbf
    -rw-r----- 1 oracle dba 195362816 Jun 27 23:48 2_165578_733073720.dbf
    -rw-r----- 1 oracle dba 1024 Jun 27 23:48 1_57490_733073720.dbf
    -rw-r----- 1 oracle dba 194276864 Jun 27 23:49 2_165579_733073720.dbf
    -rw-r----- 1 oracle dba 494327296 Jun 27 23:51 2_165580_733073720.dbf
    -rw-r----- 1 oracle dba 493318656 Jun 27 23:53 2_165581_733073720.dbf
    -rw-r----- 1 oracle dba 1024 Jun 27 23:56 1_57491_733073720.dbf
    -rw-r----- 1 oracle dba 193768448 Jun 27 23:56 2_165582_733073720.dbf
    -rw-r----- 1 oracle dba 193017344 Jun 28 00:10 2_165583_733073720.dbf
    -rw-r----- 1 oracle dba 197171712 Jun 28 00:12 2_165584_733073720.dbf
    -rw-r----- 1 oracle dba 1024 Jun 28 00:13 1_57492_733073720.dbf
    -rw-r----- 1 oracle dba 491688448 Jun 28 00:14 2_165585_733073720.dbf
    -rw-r----- 1 oracle dba 494400512 Jun 28 00:15 2_165586_733073720.dbf
    -rw-r----- 1 oracle dba 195551232 Jun 28 00:15 2_165587_733073720.dbf
    -rw-r----- 1 oracle dba 1024 Jun 28 00:15 1_57493_733073720.dbf
    -rw-r----- 1 oracle dba 195021824 Jun 28 00:15 2_165588_733073720.dbf
    22,23,24,26,27 of june archive log exist in archive folder when i run
    delete archivelog all completed before 'SYSDATE -1'
    this command 26 june of some archive deleted but i want to delete above 22,23,24,27 of june archive.how can i delete above dates archivelog.
    Thanks,
    Umair

    Hi;
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF X DAYS; << it says how many days you will keep your db and archive backups If you set it 2 its mean 2 days bakcup will be keep your db backups
    For your issue you can set this parameter or you can delete them manualy and then can run crosscheck from rman(Both method mention by Mdtaylor already)
    For me i am also using this:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    delete noprompt backup of archivelog until time 'sysdate-4'; << My system is keep my backups 7 days but wiht this command i can delete sysdate-4 hours archivelog from system(Dont forget it will delete wiht hour base,i mean if your time is now 10.00 am than it will delete sysdate-4 until 10.00 am, you can see 10.20 asrchivelog on your system)
    Regard
    Helios

  • Deleting applied archives from standby

    Hello Guys,
    We have oracle 10g rel 2 on hp-ux
    I feel this common question for dataguard implementation
    Just want to check best way of deleting archives automatically from standby database,i have 2 methods in mind
    as below
    1)At os level shell script-finding last seqno from alert log at standby/or query v$views(select max(sequence#) from v$archived_log) ,passing it to script
    using rman as :*delete archivelog until sequence seqno;*
    or deleting at os level upto this seqno
    (Making script is not issue with this functionality and scheduling it in cron)
    2)by RMAN at standby
    set alter system set "_log_deletion_policy"='ALL' scope=spfile;
    set CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
    however i have no plans to take backup at standby,still can i use above command
    is it reliable i faced some issues in past inspite of this configurations archives were not deleted at standby
    Please give your views is there any other method to delete archives automatically ,and which one is more preferred
    and reliable method/best method
    Thanks

    804719 wrote:
    Hello Guys,
    We have oracle 10g rel 2 on hp-ux
    I feel this common question for dataguard implementation
    Just want to check best way of deleting archives automatically from standby database,i have 2 methods in mind
    as below
    1)At os level shell script-finding last seqno from alert log at standby/or query v$views(select max(sequence#) from v$archived_log) ,passing it to script
    using rman as :*delete archivelog until sequence seqno;*
    or deleting at os level upto this seqno
    (Making script is not issue with this functionality and scheduling it in cron)
    2)by RMAN at standby
    set alter system set "_log_deletion_policy"='ALL' scope=spfile;
    set CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
    however i have no plans to take backup at standby,still can i use above command
    is it reliable i faced some issues in past inspite of this configurations archives were not deleted at standby
    Please give your views is there any other method to delete archives automatically ,and which one is more preferred
    and reliable method/best method
    ThanksConfigure RMAN to purge archivelogs after applied on standby [ID 728053.1]
    logdeletion_policy parameter is static, so which you cant change dynamically, PRimary should bounce, If it is fine then you can go ahead.
    If you do not have time, then prepare an RMAN script to delete the archives.

  • Deletion without archiving is not allowed in the production client

    Hi Gurus!
    I have a new problem with regards deleting products in the Production system in CRM. I can't seem to delete the product in Production Box using this report(COM_PRODUCT_DELETE_SINGLE). It gives me this error: 'Deletion without archiving is not allowed in the production client' I'm doing this to solve my issue with regards some of the products not having any Sales and Distribution Data. The steps i did below worked in QA box.
    These are the steps i did in the QA box to delete the product:
    1) I've deleted the products that has no sales data using the report COM_PRODUCT_DELETE_SINGLE. I went to COMMPR01 to tag the said products with a status 'To Archive' then saved it before I triggered this report.
    2) I've registered it first in the table COMC_PR_TOOL_REG and filling up the necessary parameters
    3) After Deleting the said products in CRM, I logged into R/3 to access the material (MM02). I just changed the sales text and saved it to trigger the replication in CRM.
    When I checked the product in CRM, it worked. The Sales and Distribution Data is already shown.
    Now I have a new problem with regards this procedure. I can't seem to delete the product in Production Box using this report. It gives me this error: 'Deletion without archiving is not allowed in the production client'
    I have already followed the same procedure as to what I did in the QA box but for some reason it didn't work in the Production Box.
    Could anyone please help me with this. Thanks!
    Thanks & Regards
    Nathan

    I was able to solve the problem.
    In Report COM_PRODUCT_DELETE_SINGLE,there is a special check in order for the productive system detection.
    The logic in this program has a perform check_authority which will automatically produce the error and prevents you from deleting a product in the production system.
    Solution:
    I copied the program COM_PRODUCT_DELETE_SINGLE to new one ZCOM_PRODUCT_DELETE_SINGLE then I placed a comment on the PERFORM check_authority.

  • Deletion of archives

    hi all,
    Good day...Currently am deleting the archives in standby by using
    rman  target /  LOG = $LOG <<EOF
    run {
    crosscheck archivelog all;
    delete noprompt ARCHIVELOG ALL COMPLETED BEFORE 'sysdate-1';
    EOFSince we need archives in standby for a day... i havent configured 'apply on standby'...How can i modify the above script in such a way that i deletes the archives older than sysdate-1 and which are applied archives......It should not delete the archives which are not applied...
    thanks
    baskar.l

    One way but not sure it will be helpful for you or not.I didn't test it.Create that procedure within that schema which have rights to select the asm views v$asm_alias,v$asm_file.
    SQL> declare
      2  cursor c1 is
      3  select al.name
      4    from v$asm_alias al,v$asm_file af
      5   where al.group_number=af.group_number
      6     and al.file_number =af.file_number
      7     and af.type='ARCHIVELOG'
      8     and af.creation_date<sysdate-1;
      9  v1 varchar2(500);
    10  begin
    11  for m in c1
    12  loop
    13    v1:='alter diskgroup <diskgroupname> drop file "<+diskgroupname/>||m1.name||"';
    14    execute immediate v1;
    15  end loop;
    16  end;
    17  .
    SQL> /
    PL/SQL procedure successfully completed.scheduled that above procedure within dbms_job
    DBMS_JOB.SUBMIT (
       job       OUT BINARY_INTEGER,
       what      IN  VARCHAR2,
       next_date IN  DATE DEFAULT sysdate,
       interval  IN  VARCHAR2 DEFAULT 'null',
       no_parse  IN  BOOLEAN DEFAULT FALSE,
       instance  IN  BINARY_INTEGER DEFAULT any_instance,
       force     IN  BOOLEAN DEFAULT FALSE); Check more detail using oracle doc about dbms_job.
    Note: I have not tested above procedure.
    Khurram

  • Can we delete the archived RS tables data in unix path?

    Hi Experts
    As you all know that when we perform RS table archiving we setup a Logical file path 'ARCHIVE_GLOBAL_PATH' pointing to the physical path '/usr/sap/<SYSID>/SYS/global/<FILENAME>' in unix system.
    Here we have our RS table data in the unix path and this logical path will make sure that there are no problems with requests status.
    Now our unix path has grown in size hence we would like to delete some archived data from this path. Could you pls confirm if we delete the data from this unix path will there be any problems with the requests status?
    Simply can we delete the RS table archived data from the unix file path??
    Thanks!!

    Hi All
    Any idea about this would be appreciated.
    Thanks!!

  • Recipients view in workflow log

    Hi all,
    Today I noticed that Recipients list in workflow log for a particular task looks different if I log on with two different users.
    For example I have a decision step with two possible agents US 00000001 and US 00000002.
    If I logon with my user id I see recipients list like this:
    Approval process
    |--> US 00000001
    |--> US 00000002
    But If logon with another user id I see recipient list like this:
    US 00000001
    |--> US 00000002
    Do you know if it is something related with configuration?
    If yes what should we do to change it?
    Thanks!

    Thanks for your answers,
    I tryed changing WLC parameter Id but it did not worked.
    Below I add two screenshots with view differences:
    [https://lh6.googleusercontent.com/-m2jdjm8X5qU/Tab0sWd6_YI/AAAAAAAAAQs/wEdtyRaF2zA/s288/untitled2.JPG|https://lh6.googleusercontent.com/-m2jdjm8X5qU/Tab0sWd6_YI/AAAAAAAAAQs/wEdtyRaF2zA/s288/untitled2.JPG]
    [https://lh4.googleusercontent.com/-TSg8eQrQ5qg/Tab0sVo8i-I/AAAAAAAAAQw/i220aJIbMIw/s288/untitled1.JPG|https://lh4.googleusercontent.com/-TSg8eQrQ5qg/Tab0sVo8i-I/AAAAAAAAAQw/i220aJIbMIw/s288/untitled1.JPG]
    Hope someone can help me.
    Thanks!

  • Document change via workflow log.......

    Dear all
    In our scenario, I am creating a word document in workflow.After creation its going to first level approver for his decision.consider he is not executed the doc.
    When I check the status of document from the workflow log(from :Work item executed by me), its allowing me to change the doc.If I made any changes its updating the document,which is already waiting for decision.......Is this correct?Is there any possibilities to restict the document changes from the workflowlog view?
    Not only for Word doc.......other doc also.........

    I feel you can restrict this by putting some authorization. May be there is something you can restrict in the HOLD Document option.
    Thanks
    Arghadip

Maybe you are looking for