Delete saved logs archived

Similar Questions

• RMAN-08137: WARNING: log archived not deleted, necessary for intelligence or upstream collection procedure

  Hi Oracle Community,

  I have a few databases (11.2.0.4 POWER 2 block and 12.1.0.2) with Data Guard. Back up this database with RMAN to ribbons, only on the primaries.

  During the backup, sometimes I got RMAN-08137: WARNING: log archived not deleted, necessary for intelligence or upstream collection procedure

  By reason of this global warning to backup status is "COMPLETED WITH WARNINGS". Is it possible to remove this warning, or perhaps change RMAN configuration to avoid the appearance of this warning?

  Concerning

  J

  Where is the problem on these warnings? If you do not want to see such warnings, why not simply to perform the removal of the archivelogs in a separate step? For example:

  RMAN> backup database plus archivelog;
  RMAN> delete noprompt archivelog all completed before 'sysdate-1';
  

• Delete logs archive > 1 day

  Hi all

  9i

  RHEL5

  I posted a thread here on how to remove the log archiving liked only 1 day for both PRIMARY and standby database.

  But I don't find it anymore

  Is it possible to search all the contents of my son using Keywork "delete archive logs?

  Thank you all,

  JC

  Hello;

  You old thread:

  Remove the archivelogs and old backups

  Best regards

  mseberg

• delete files from archive log with rman

  Hi guys,.

  I try to delete the log file archive on my backup site, but I get the following message. There are a lot of archive logs is present on the storage but rman may show that. No idea what I'm doing wrong here.

  RMAN > list archivelog all;

  specification does not match any newspaper archived in the repository

  RMAN >

  Kind regards

  Sorry about that. Its 11g 2 R (11.2.0.1) and OS Version is 2008 R2 64 bit. Sleep is in auto recovery mode. (hope this helps).

• delete the log file archive

  Hello
  I use oracle 10g on linux, I want to delete archive log file automatically, there is no way to do this.or can someone tell me scripts to do this.ur help on this is very appreciated
  
  Respect, s
  Umair Iqbal

  Hello

  Can you please let us know why you want to delete the log file archive?

  BTW, you can use RMAN to achieve by archiving log backup and delete the original file using the following command:

  Backup archivelog all delete input;
  

  Concerning

• Delete log archiving

  Hi friends,
  
  I use oracle 10.2.0.1 on windows xp.
  
  11/05/2009 I give:
  RMAN > backup database;
  
  Completed successfully.
  
  On 02/08/2010 I give:

  RMAN> show all;
  RMAN configuration parameters are:
  CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
  CONFIGURE BACKUP OPTIMIZATION OFF; # default
  CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
  CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
  CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
  CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
  CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
  CONFIGURE MAXSETSIZE TO UNLIMITED; # default
  CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
  CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
  CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
  CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\SNCFORCL.ORA'; # default
  
  RMAN> run
  2> {
  3> backup database;
  4> BACKUP ARCHIVELOG ALL DELETE INPUT;
  5> }
  
  Finished backup at 08-FEB-10

  On 02/10/2010 I give: (with the same parameters of RMAN from 02/08/2010)
  
  run
  {
  ARCHIVELOG backup all;
  overlap archivelog all;
  remove expired archivelog all;
  }
  
  ...
  ...
  In the end, there were:
  
  output channel: ORA_DISK_1
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: sid = 133 devtype = DISK
  specification does not match any newspaper archive in the recovery catalog
  
  I give you today (26/02/2010):

  RMAN> show all;
  
  RMAN configuration parameters are:
  CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
  CONFIGURE BACKUP OPTIMIZATION OFF; # default
  CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
  CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
  CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
  CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
  CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
  CONFIGURE MAXSETSIZE TO UNLIMITED; # default
  CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
  CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
  CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
  CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\SNCFORCL.ORA'; # default
  
  RMAN> run
  2> {
  3> backup archivelog all;
  4> crosscheck archivelog all;
  5> delete expired archivelog all;
  6> }
  
  ..
  ..
  Crosschecked 153 objects
  
  
  released channel: ORA_DISK_1
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: sid=157 devtype=DISK
  specification does not match any archive log in the recovery catalog
  
  RMAN> BACKUP ARCHIVELOG ALL DELETE INPUT;
  input archive log thread=1 sequence=627 recid=593 stamp=710249727
  input archive log thread=1 sequence=628 recid=595 stamp=710411997
  ..
  ..
  
  Finished backup at 26-FEB-10

  But the location of archive (5 files, and arch2 = 50 = arch1) files are still there. Can I delete these files from OS commands.
  
  In C:\oracle\product\10.2.0\flash_recovery_area\ORCL, there are 405. ARC files is also available. I can remove them too; because I took the backup of all archive logs? Location of the Archive previous was FRA, but now I take archives at 2 different locations i.e. d:\orcl\arch1 and d:\orcl\arch2.
  
  Thanking you,
  Nisha

  Why not look at the file names (indicating the sequence numbers) and timestamps and make a decision on your own?

  And go ahead: take MORE FREQUENT backups. And copy your backups on the server. If you lose the discs/storage, you lose the backup and the database!

  Hemant K Collette

  Published by: Hemant K grapple on February 26, 2010 16:53

• How long should we keep logs archived in the comic book?

  11.2.0.4 DB Oracle Linux 6.5

  We have a database whose archive generation is as follows.

  Average of generation of archive log: 400 GB/day

  Max log generation: 900 GB/day

  Archive log diskgroup size: 4 TB

  Backup strategy: we take full backups on Monday and Wednesday and Level1 for the rest of the days.

  -----------------

  Sunday-> level 0 backup

  Monday-> level 1 backup

  Tuesday-> level 1 backup

  Wednesday-> level 0 backup

  Thursday-> level 1 backup

  Friday-> level 1 backup

  Saturday-> level 1 backup

  Both Level0 and Level1 scripts have MORE ARCHIVELOG; (without a clause to DELETE all THE ENTRIES )

  We have archiveLog backup script that runs at 10:00 and 16:00 which does not REMOVE all ENTRIES either.

  We serve the archivelogs of Level0 and Level1 backup scripts, with the following command

  delete noprompt archivelog until 'SYSDATE -2";

  Question1. What is the industry standard to keep (retention period), archiving within DB logs? Is there a 'formula' / rule for this? When a restore, recovery lose us not a lot of time restore backup media archivelogs. That's why we stay 2 days now archivelog within the DB.

  Question2. We have 4 TB of space to store the archivelogs in this particular PB. With 900 GB Max generation arch daily newspapers, we can keep safe the last 3 days of the archivelogs. Right? I mean, is there a possibility of hitting the terrible archiver error if we increase the shelf life of the archive logs using the delete noprompt archivelog until 'SYSDATE -3';

  N ° DELETE OBSOLETE removes old newspapers also all the log_archive_dest.

  
  

  I could be wrong, but this is the first I hear of this and on a quick scan, I found no support in that either rman reference or guide the user to rman.  Could cite your source?

  DELETE OBSOLETE is not the same thing as REMOVE EXPIRES.

  -EDIT

  Never mind.  I found it.

  DELETE

  OBSOLETE

  Removes backups of data files and copies stored in the repository RMAN which are obsolete, in other words, is no longer required (see example 2-66). RMAN also deletes the log of the obsolete filesand archived redo log backups. RMAN determines what backups and copies of data files are no longer needed, which in turn determines what records (and backups of logs) are no longer needed. RMAN considers that the creation of a data file as a backup to decide which connects to keep.

  Post edited by: EdStevens

  Historically, I saved my archivelogs with the option to DELETE the ENTRIES, I never had reason to notice or question this behavior... a rman DELETE OBSOLETE reach out to the archivelogs themselves.   Thinking maybe it was related to the maintenance of the FRA, I just tried a little test in two ways... archivlogs wrote to FRA and archivelogs writes destined for non - FRA.  Of course, anyway DELETE OBSOLETE also deleted real archivelogs.  I don't know that I'll change my procedures as well, but it is good to know.

  I learned something new today.  Can I go home now?

• Purge logs archiving on things primary and Standby and for Data Guard RMAN

  
  Hi, I saw a couple of orders in regard to the purge archive records in a Data Guard configuration.

  Set UP the STRATEGY of SUPPRESSION of ARCHIVE to SHIPPED to All RELIEF;

  Set UP the STRATEGY of ARCHIVELOG DELETION to APPLIED on All RELIEF;

  Q1. The above only removes logs archiving to the primary or primary and Standby?

  Q2. If deletions above archive logs on the primary, is it really remove them (immediately) or does the FRA to delete if space is needed?

  I also saw

  CONFIGURE ARCHIVELOG DELETION POLICY TO SAVED;

  Q3. That what precedes, and once again it is something that you re primary side?

  I saw the following advice in the manual of Concepts of data protection & Admin

  Configure the DB_UNIQUE_NAME in RMAN for each database (primary and Standby) so RMAN can connect remotely to him

  Q4. Why would I want my primary ro connect to the RMAN Repository (I use the local control file) of the standby? (is this for me to say define RMAN configuration settings in the Standby) manual

  Q5. Should I only work with the RMAN Repository on the primary or should I be also in things in the deposits of RMAN (i.e. control files) of the standby?

  Q6. If I am (usually mounted but not open) Physics, of standby I able to connect to its own local repository for RMAN (i.e. control based on files) while sleep mode is just mounted?

  Q7. Similiarly if I have an old lofgical (i.e. effectively read-only), to even connect to the local RMAN Repository of Eve?

  Q8. What is the most common way to schedule a RMAN backup to such an environment? example cron, planner of the OEM, DBMS_SCHEDULER? MY instinct is cron script as Planner OEM requires running the OEM service and DBMS_SCHEDULER requires the data runs?

  Any idea greatly appreciated,

  Jim

  The above only removes logs archiving to the primary or primary and Standby?

  When CONFIGURE you a deletion policy, the configuration applies to all destinations archive

  including the flash recovery area. BACKUP - ENTRY DELETE and DELETE - ARCHIVELOG obey this configuration, like the flash recovery area.

  You can also CONFIGURE an archived redo log political suppression that newspapers are eligible for deletion only after being applied to or transferred to database backup destinations.

  If deletions above archive logs on the primary, is it really remove them (immediately) or does the FRA to delete if space is needed?

  Its a configuration, it will not erase by itself.

  If you want to use FRA for the automatic removal of the archivelogs on a database of physical before you do this:

  1. make sure that DB_RECOVERY_FILE_DEST is set to FRA - view parameter DB_RECOVERY_FILE_DEST - and - setting DB_RECOVERY_FILE_DEST_SIZE

  2. do you have political RMAN primary and Standby set - CONFIGURE ARCHIVELOG DELETION POLICY to APPLY ON ALL STANDBY;

  If you want to keep archives more you can control how long keep logs by adjusting the size of the FRA

  Great example:

  http://emrebaransel.blogspot.com/2009/03/delete-applied-archivelogs-on-standby.html

  All Oracle is worth a peek here:

  http://emrebaransel.blogspot.com/

  That what precedes, and once again it is something that you re primary side?

  I would never use it. I always had it put it this way:

  CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;

  I would use only 'BACKED UP' for the data protection system. Usually it tell oracle how many times to back up before removing.

  Why would I want my primary ro connect to the RMAN Repository?

  Because if you break down, you want to be able to backup there, too.

  Also if it remains idle for awhile you want.

  Should I only work with the RMAN Repository on the primary or should I be also in things in the deposits of RMAN (i.e. control files) of the standby?

  Always use a database of catalog RMAN with Data Guard.

  If I am (usually mounted but not open) Physics, of standby I able to connect to its own local repository for RMAN (i.e. control based on files) while sleep mode is just mounted?

  Same answer as 5, use a catalog database.

  Similiarly if I have an old lofgical (i.e. effectively read-only), to even connect to the local RMAN Repository of Eve?

  Same answer as 5, use a catalog database.

  What is the most common way to schedule a RMAN backup to such an environment? example cron, planner of the OEM, DBMS_SCHEDULER? MY instinct is cron script as Planner OEM requires running the OEM service and DBMS_SCHEDULER requires the data runs?

  I think cron is still, but they all work. I like cron because the database has a problem at work always reports its results.

  Best regards

  mseberg

  Summary

  Always use a database with RMAN catalog.

  Always use CRF with RMAN.

  Always set the deletion «To APPLY ON ALL STANDBY» policy

  DB_RECOVERY_FILE_DEST_SIZE determines how long to keep the archives with this configuration.

  Post edited by: mseberg

• Size of the huge log archive

  I have 5 redo log files. Each is 4 GB. There are huge transactions (1800-2000 per second). So we have every hour 5-6 journal of the switches. So all the hours of archives journal 20 to 24 GB and daily increase in size, the size 480 GB.
  
  I had planned to take an incremental backup of level 1 and level 0 per week daily with the option delete log archiving 'sysdate-1 '.
  
  But we have little storage if, it is impossible to the sphere 480 GB per day and take backup of these 480 GB for 7 days (480 * 7) GB = 4 TB. How can I correct this situation? Help, please.

  1 disk is cheap
  2 the onus on those who "Advanced" application
  3 you can use Log Miner to check what is happening.

  You need to this address with application developers and/or clients and/or buy the disc.
  There are no other solutions.

  -----------
  Sybrand Bakker
  Senior Oracle DBA

  Published by: sybrand_b on July 16, 2012 11:11

• Manully deleted the file Archive.

  Hello
  
  Version: 11.2.0.1.0 / OS: AIX
  I deleted manually 3 files of newspapers to archive. Now im getting error when running below a.
  How to restore these 3 files?
  
  RMAN > backup database more entered archivelog delete;
  
  
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of backup so archivelog command at 02/07/2011 21:16:08
  RMAN-06059: expected found archived newspaper, loss of archived newspaper compromised recoverability
  ORA-19625: error identification of file /fixdb2_arc/fixfarc1068_1_730735006.arc
  ORA-27037: unable to get file status
  IBM AIX RISC System/6000 error: 2: no such file or directory
  Additional information: 3
  
  RMAN > list expired archivelog SNA = 1;
  
  List Copies of newspapers archived to database with db_unique_name fixdb2
  =====================================================================
  
  Thrd Seq S key low time
  ------- ---- ------- - ---------
  1056 1 1068 X 01-JUL-11
  Name: /fixdb2_arc/fixfarc1068_1_730735006.arc
  
  1057 1 1069 X 01-JUL-11
  Name: /fixdb2_arc/fixfarc1069_1_730735006.arc
  
  1058 1 1070 X 01-JUL-11
  Name: /fixdb2_arc/fixfarc1070_1_730735006.arc
  
  
  RMAN >
  
  RMAN > restore sequence archivelog 1068 until the sequence 10703 validate;
  
  From restoration to July 2, 11
  allocated channel: ORA_SBT_TAPE_1
  channel ORA_SBT_TAPE_1: SID = 207 device type = SBT_TAPE
  channel ORA_SBT_TAPE_1: for Oracle Data Protection: version 5.4.1.0
  allocated channel: ORA_SBT_TAPE_2
  channel ORA_SBT_TAPE_2: SID = 304 device type = SBT_TAPE
  channel ORA_SBT_TAPE_2: for Oracle Data Protection: version 5.4.1.0
  using channel ORA_DISK_1
  
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the restore command at 02/07/2011 21:25:41
  RMAN-06026: some targets not found - abandonment of restoration
  RMAN-06025: no backup log archived for 1 with sequence 1070 threading and YVERT departure from 4755287261712 found to restore
  RMAN-06025: no backup log archived for thread 1 with sequence 1069 and YVERT departure from 4755287227194 found to restore
  RMAN-06025: no backup log archived for thread 1 with sequence 1068 and YVERT departure from 4755287190271 found to restore

  Gowin_dba wrote:
  Accidentally, I shot myself in the foot.
  Is it possible to bypass these newspapers from archives files when executing the next time...

  Take a full, RMAN backup online NOW!

• Logs archiving for the RAC ASM basics

  Hello
  
  I have a question about logs archiving on the ASM database located on a RAC. I created a database orcl who has orcl1 instance on node1 and orcl2 on Node2. For the backup of this database, I enabled for the database to archivelog.
  
  After a few transactions and backups, I noticed that there are two sets of archiving logs created on each node in the folder $ORACLE_HOME/dbs. In node 1, it starts with arch1_ * and node2 is arch2_ *.
  
  IWhy is it creates logs archiving on local disks, in which she should ideally create disks asm which is shared between the nodes. My backup application fails with journal archive not found error, because it searches newspaper archives in the other node.
  
  All entries on this will be useful.
  
  Amith

  Hello

  I have a question about logs archiving on the ASM database located on a RAC. I created a database orcl who has orcl1 instance on node1 and orcl2 on Node2. For the backup of this database, I enabled for the database to archivelog.

  After a few transactions and backups, I noticed that there are two sets of archiving logs created on each node in the folder $ORACLE_HOME/dbs. In node 1, it starts with arch1_ * and node2 is arch2_ *.

  I believe that it is missing from your configuration database and Oracle uses the default location. (i.e. your "$ORACLE_HOME/dbs")

  ARCHIVELOG must focus on a shared domain.

  You need the parameter config below:

  SQL> show parameter db_recovery_file
  NAME                                 TYPE        VALUE
  ------------------------------------ ----------- ------------------------------
  db_recovery_file_dest                string
  db_recovery_file_dest_size           big integer 
  

  Or location of default config:

  SQL> show parameter log_archive_dest
  
  NAME                                 TYPE        VALUE
  ------------------------------------ ----------- ------------------------------
  log_archive_dest                     string
  

  IWhy is it creates logs archiving on local disks, in which she should ideally create disks asm which is shared between the nodes. My backup application fails with journal archive not found error, because it searches newspaper archives in the other node.

  To resolve this problem see this example:

  SQL> show parameter recover
  
  NAME                                 TYPE        VALUE
  ------------------------------------ ----------- ------------------------------
  db_recovery_file_dest                string
  db_recovery_file_dest_size           big integer 1
  
  SQL> archive log list;
  Database log mode              Archive Mode
  Automatic archival             Enabled
  Archive destination            /u01/app/oracle/product/10.2.0/db_1/dbs/
  Oldest online log sequence     2
  Next log sequence to archive   3
  Current log sequence           3
  SQL>
  
  SQL> alter system set db_recovery_file_dest_size=20G scope=both sid='*';
  
  System altered.
  
  SQL> alter system set db_recovery_file_dest='+FRA' scope=both sid='*';
  
  System altered.
  
  SQL> archive log list;
  Database log mode              Archive Mode
  Automatic archival             Enabled
  Archive destination            USE_DB_RECOVERY_FILE_DEST
  Oldest online log sequence     5
  Next log sequence to archive   6
  Current log sequence           6
  SQL>
  

  With RMAN

  RMAN> CONFIGURE CHANNEL 1 DEVICE TYPE DISK CONNECT 'sys/oracle@db10g1';
  
  new RMAN configuration parameters:
  CONFIGURE CHANNEL 1 DEVICE TYPE DISK CONNECT '*';
  new RMAN configuration parameters are successfully stored
  starting full resync of recovery catalog
  full resync complete
  
  RMAN>  CONFIGURE CHANNEL 2  DEVICE TYPE DISK CONNECT  'sys/oracle@db10g2';
  
  new RMAN configuration parameters:
  CONFIGURE CHANNEL 2 DEVICE TYPE DISK CONNECT '*';
  new RMAN configuration parameters are successfully stored
  starting full resync of recovery catalog
  full resync complete
  
  RMAN> list archivelog all;
  
  using target database control file instead of recovery catalog
  
  List of Archived Log Copies
  Key     Thrd Seq     S Low Time  Name
  ------- ---- ------- - --------- ----
  1       1    3       A 28-FEB-11 /u01/app/oracle/product/10.2.0/db_1/dbs/arch1_3_744216789.dbf
  2       2    2       A 27-FEB-11 /u01/app/oracle/product/10.2.0/db_1/dbs/arch2_2_744216789.dbf
  
  RMAN> crosscheck archivelog all;
  
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: sid=127 instance=db10g1 devtype=DISK
  allocated channel: ORA_DISK_2
  channel ORA_DISK_2: sid=135 instance=db10g2 devtype=DISK
  validation succeeded for archived log
  archive log filename=/u01/app/oracle/product/10.2.0/db_1/dbs/arch1_3_744216789.dbf recid=1 stamp=744292116
  Crosschecked 1 objects
  
  validation succeeded for archived log
  archive log filename=/u01/app/oracle/product/10.2.0/db_1/dbs/arch2_2_744216789.dbf recid=2 stamp=743939327
  Crosschecked 1 objects
  
  RMAN> backup archivelog all delete input;
  
  Starting backup at 28-FEB-11
  current log archived
  using channel ORA_DISK_1
  using channel ORA_DISK_2
  channel ORA_DISK_1: starting archive log backupset
  channel ORA_DISK_1: specifying archive log(s) in backup set
  input archive log thread=1 sequence=3 recid=1 stamp=744292116
  channel ORA_DISK_1: starting piece 1 at 28-FEB-11
  channel ORA_DISK_2: starting archive log backupset
  channel ORA_DISK_2: specifying archive log(s) in backup set
  input archive log thread=2 sequence=2 recid=2 stamp=743939327
  channel ORA_DISK_2: starting piece 1 at 24-FEB-11
  channel ORA_DISK_1: finished piece 1 at 28-FEB-11
  piece handle=+FRA/db10g/backupset/2011_02_28/annnf0_tag20110228t120354_0.265.744293037 tag=TAG20110228T120354 comment=NONE
  channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
  channel ORA_DISK_1: deleting archive log(s)
  archive log filename=/u01/app/oracle/product/10.2.0/db_1/dbs/arch1_3_744216789.dbf recid=1 stamp=744292116
  channel ORA_DISK_2: finished piece 1 at 24-FEB-11
  piece handle=+FRA/db10g/backupset/2011_02_24/annnf0_tag20110228t120354_0.266.743940249 tag=TAG20110228T120354 comment=NONE
  channel ORA_DISK_2: backup set complete, elapsed time: 00:00:03
  channel ORA_DISK_2: deleting archive log(s)
  archive log filename=/u01/app/oracle/product/10.2.0/db_1/dbs/arch2_2_744216789.dbf recid=2 stamp=743939327
  channel ORA_DISK_1: starting archive log backupset
  channel ORA_DISK_1: specifying archive log(s) in backup set
  input archive log thread=1 sequence=4 recid=4 stamp=744293023
  input archive log thread=2 sequence=3 recid=3 stamp=743940232
  channel ORA_DISK_1: starting piece 1 at 28-FEB-11
  channel ORA_DISK_1: finished piece 1 at 28-FEB-11
  piece handle=+FRA/db10g/backupset/2011_02_28/annnf0_tag20110228t120354_0.267.744293039 tag=TAG20110228T120354 comment=NONE
  channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
  channel ORA_DISK_1: deleting archive log(s)
  archive log filename=+FRA/db10g/archivelog/2011_02_28/thread_1_seq_4.264.744293023 recid=4 stamp=744293023
  archive log filename=+FRA/db10g/archivelog/2011_02_24/thread_2_seq_3.263.743940231 recid=3 stamp=743940232
  Finished backup at 28-FEB-11
  
  Starting Control File and SPFILE Autobackup at 28-FEB-11
  piece handle=+FRA/db10g/autobackup/2011_02_28/s_744293039.263.744293039 comment=NONE
  Finished Control File and SPFILE Autobackup at 28-FEB-11
  
  SQL> alter system archive log current;
  
  System altered.
  
  RMAN> list archivelog all;
  
  using target database control file instead of recovery catalog
  
  List of Archived Log Copies
  Key     Thrd Seq     S Low Time  Name
  ------- ---- ------- - --------- ----
  5       1    5       A 28-FEB-11 +FRA/db10g/archivelog/2011_02_28/thread_1_seq_5.264.744293089
  6       2    4       A 24-FEB-11 +FRA/db10g/archivelog/2011_02_24/thread_2_seq_4.268.743940307
  
  RMAN> CONFIGURE CHANNEL 1 DEVICE TYPE DISK CLEAR;
  
  old RMAN configuration parameters:
  CONFIGURE CHANNEL 1 DEVICE TYPE DISK CONNECT '*';
  old RMAN configuration parameters are successfully deleted
  
  RMAN> CONFIGURE CHANNEL 2 DEVICE TYPE DISK CLEAR;
  
  old RMAN configuration parameters:
  CONFIGURE CHANNEL 2 DEVICE TYPE DISK CONNECT '*';
  old RMAN configuration parameters are successfully deleted
  
  RMAN> exit
  
  Recovery Manager complete.
  

  Kind regards
  Levi Pereira

  Published by: Levi Pereira on February 28, 2011 12:16

• How to disable the restrictions for deleting call logs

  Y at - he on an option to put the restriction to delete call log history journal calls or stops history in I cloud.

  Not that I know unfortunately.

• Deleting call logs: the waiting is the solution

  There are several positions dealing with the removal of the call logs. A problem on older versions of devices/OS, is that the deleted call log on the unit during a restart. This is consistent with the behavior of the Simulator.

  I found a working solution after a colleague fell on the problem again today.
  It seems that the question is based on a timing problem in the operating system, when the callLogAdded (of the PhoneLogListener) is called the phonelog is not yet written to storage. If you delete the log now another process still works on it and it stays on the phone.

  I solved this problem by running the removal in a new thread and issueing a sleep (2000) before deleting the call log. The 2000 is chosen at random, I don't want to use too much time on it and deleting is not time critical.

  I just wanted to post an update to this issue, MSohm wrote that it was reported, but I have found no information about it being fixed.

  just a post to mark the thread as solved

• Cannot delete the log entry: error

  Hello

  I get the error "Unable to delete the log entry" during an attempt to delete from a line in a journal template. It reproduces the newspaper.

  Thank you

  CHEK

  Thanks for your reply KK.

  I have not found something in the newspapers.

  Problem is solved. I did clear files invalid on the application that is having the problem. If the problem is resolved. I deleted the line of the journal.

  Steps to follow:

  1. go to the console of the workspace and to connect as a user admin 2. open hFM application. 3. click on peacebuilding-> data-> Manage 4. Select the icon of the eraser to erase the invalid clear records.

  Thank you

  Mohan

• Is it safe to delete the log file in/private/var/log/vnetlib?

  [Fusion 4.1.2 / Lion 10.7.4]

  My vnetlib log file is greater than 22 MB in size and has > K 250 lines of entries dating back to September 2011. Is it safe to delete this log file? A planning at startup, remove the file and then do a restart immediately after to restart VMWare network components - and we hope to recreate a new empty file. I tried erasing the contents of the file via the Terminal but do not have sufficient permissions, even with sudo - guess it was because the VMWare networking processes running at the time.

  Thank you

  John

  If you do not experience network problems, then it is safe to delete.

  I had no problem to remove in a Terminal (while VMware Fusion is running) by using the following command in (although I would recommend VMware Fusion of closing first and it doesn't have to be done in safe mode).

  sudo rm -f /var/log/vnetlib
  

  Just curious, what the big problem is why you want to delete, 22 MB is not that big a deal.