RMAN-06025: no log backup archived for thread 1 with sequence - on double

Similar Questions

• CPU, RAM and disk, file system information for the data, logs, temp, Archive for database

  Hello gurus,
  
  How can we see what size of CPU and RAM for the database? According to the previous steps of this great site, I could able to do
  

  SQL> show parameter sga_max_size
  
  NAME                                 TYPE        VALUE
  ------------------------------------ ----------- ------------------------------
  sga_max_size                         big integer 800M
  SQL> exit

  Therefore, the size of the RAM for the database to which I have connected
  

  rootd2n3v5# ioscan -kfn |grep -i processor
  processor    0  13/120         processor CLAIMED     PROCESSOR    Processor
  processor    1  13/121         processor CLAIMED     PROCESSOR    Processor
  processor    2  13/122         processor CLAIMED     PROCESSOR    Processor
  processor    3  13/123         processor CLAIMED     PROCESSOR    Processor
  rootd2n3v5#

  The one above was the command give the OS level that I don't know what information he gives and what database, since there are 12 databases on this server.
  
  How can I get the CPU information?
  
  And where can I find information for information of system data files, logs, temp, Archive?
  

  <div class="jive-quote">select * from v$version</div>
  BANNER                                                           
  ---------------------------------------------------------------- 
  Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bi 
  PL/SQL Release 10.2.0.5.0 - Production                           
  CORE     10.2.0.5.0     Production                                         
  TNS for HPUX: Version 10.2.0.5.0 - Production                    
  NLSRTL Version 10.2.0.5.0 - Production

  Ask the system administrator if the database server is a physical machine, if it is hardware partitioned or created under a virtual machine Manager? Check the operating system utilities. On AIX uname to identify if you are on an LPAR.

  In Oracle, you can query the parameter $ v to cpu_count to see how many cpu Oracle says he sees.

  HTH - Mark D Powell.

• dig into the log backup archive compressed RMAN

  Hello

  I need to investigate on what is inside some archiving logs. I have this archive of newspapers backed up by RMAN. I know that I need to connect minor tools to watch in the archiving log, etc. but these backups seem to be compressed, do I unpack them first? Here is the part of RMAN backup list of the archivelog all;:

  BS key size

  Time of accomplishment of the time device Type

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

  8223	5.33 M	DISC	00:00:04	MAY 9, 14
  	BP key: 8223 situation: AVAILABLE Tablet: YES Tag: BACKUP_MYDB_0002_050914010501
  	Name of the element: / opt/backup/rman/1kp7qpof_1_1

  List of newspapers archived in defined backup 8223

  THRD Seq

  Low RCS

  Low time YVERT following next time

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

  2	210826 15899507552 8 MAY 14 15899524705 8 MAY 14
  2	210827 15899524705 8 MAY 14 15899541179 8 MAY 14
  2	210828 15899541179 8 MAY 14 15899560575 8 MAY 14

  ...

  Do something like this:

  RUN

  {

  # Set a new location for 1 to 100 newspapers.

  SET the ARCHIVELOG DESTINATION in the ' / fs1/tmp ";

  RESTORE OF ARCHIVELOG FROM SEQUENCE TO SEQUENCE 100 1;

  # Set a new location for the newspapers from 101 to 200.

  SET the ARCHIVELOG DESTINATION in the ' / fs2/tmp ";

  RESTORE OF ARCHIVELOG FROM SEQUENCE TO SEQUENCE 200 101;

  # Set a new location for the 201 to 300 newspapers.

  SET the ARCHIVELOG DESTINATION in the ' / fs3/tmp ";

  RESTORE OF ARCHIVELOG FROM 201 TO 300 SEQUENCE SEQUENCE;

  # restore and recover the data files as needed

  .

  .

  .

  }

• VMWare backup software for funky VM with OS customers

  Hey there,

  I'm still new to this free version of VM Server and I wonder if someone as gone through this before:

  My business takes 3 new servers/Applications which they will copy of virtual computer Images and we will import it onto a new server VM 2.0 host. These applications are: Linux, Open source, and another funky OS that I've never dealt with before. Such, ideas of backups are once a week, stop the virtual machines and save them as flat files or buy backup of virtual machine software (very little probable that I said). I prefer the option of backup of virtual machine and run every day, but with costs are the big problem at the moment, can anyone recommend another option for backup everyday live, these virtual machines?

  Thank you

  You could build a script than for vm snapshots, copy the base vmdk and then commits the snapshot.  Once copied to a shared location you can dump on tape no matter.  If you create the script and run as long as a cron job, you could reach a full vmdk backup every day.

  SID Smith - don't forget to award points for correct and useful responses.

  -

• RMAN-06025 and double standby: no backup of the log 1 thread

  Hi all
  
  I use oracle 10.2.0.3.
  
  I tried to make a duplicate of standby restore/recovery
  from a band. The duplicate takes about 15 hours. So, upon arrival
  I got the following error:
  

  Oracle Error:
  ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
  ORA-01194: file 1 needs more recovery to be consistent
  ORA-01110: data file 1: '+DATA/PROJ/datafile/system.346.764664523'
  
  released channel: c1
  released channel: c2
  released channel: c3
  released channel: c4
  released channel: ac1
  released channel: ac2
  released channel: ac3
  released channel: ac4
  RMAN-00571: ===========================================================
  RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
  RMAN-00571: ===========================================================
  RMAN-03002: failure of Duplicate Db command at 10/28/2011 01:19:11
  RMAN-03015: error occurred in stored script Memory Script
  RMAN-06053: unable to perform media recovery because of missing log
  RMAN-06025: no backup of log thread 1 seq 35000 lowscn 74343144157 found to restore
  .
  .
  .

  Well,.
  
  The duplicate database is restored. It remains only the archivelogs.
  If I try to backup all archivelogs again and to run the double once more,
  The data files already restored are underwritten, or RMAN ALL restart again, RESTORE
  ALL DATA FILES?
  The database has 600 GB. So, if I start again, it's a big problem.
  
  What can I do to fix this?
  
  Thank you very much!!!

  This is an Enterprise edition? Have you configured in Eve and dataguard on primary configuration?
  Which command you gave to duplicate?
  RMAN > target database duplicate for standby?

  then start MRP from sleep mode: -.
  SQL > recover database managed altert disonnect waiting database session;

  Main post office: -.
  Select the code from ds.dest_id
  ad.status
  ds.database_mode db_mode
  type ad.archiver
  ds.recovery_mode
  ds.protection_mode
  , ds.standby_logfile_count 'LAR '.
  Active ds.standby_logfile_active
  ds.archived_seq #.
  v $ archive_dest_status ds
  , announcement of v$ archive_dest
  where ds.dest_id = ad.dest_id
  and ad.status! = 'INACTIVE '.
  order by
  DS.dest_id
  /

  The duplicate database is restored. It remains only the archivelogs.
  If I try to backup all archivelogs again and to run the double once more,
  The data files already restored are underwritten, or RMAN ALL restart again, RESTORE
  ALL DATA FILES?
  The database has 600 GB. So, if I start again, it's a big problem.

  First thing is that you can make two copies because the database is already mounted...
  Why you want to restore again?

  Just start MRP and post if no errors.

• 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';
  

• Log of archives by RMAN backup

  Topic: Backup of archive logs by RMAN

  I create newspapers archived in two locations on my server. I do backup of archive logs to a destination:

  Backup in back pain tablets

  ARCHIVELOG like the "$DEST1DR/%.arc" format "${RMBKUPDIR} arlog_ %U % _ %t".

  skip an entry delete inaccessible;

  So after that the archived logs are backed up on tape, they will be removed from dest1.

  On dest2 I remove newspapers archived by using a shell script, some files older than 7 days will be deleted.

  My question is this:

  If I do a rman restore and some archived logs that are present in dest2 needed, he uses them

  Or it will try to restore archived newspapers of the tapes (which were present in dest1 before they were deleted).

  If the answer is that the rman restore will not know anything either on the archived logs present in dest2, how can publicize rman; How can I change my backup or restoration of the rman scripts knows about the newspapers of dest1 and dest2, but removes logs from only dest1 using some commands rman similar to what I described above.

  Thank you very much.

  Hello

  Yes, it will use dest2 archivelogs, but because you delete them without rman, he will try to restore from dest2 even if they are no longer present.

  You should do an overlap after deleting the files outside of rman.

  Moreover, it is better to use FRA and set up a deletion policy and never issue to remove or rm...

  Kind regards

  Franck.

• RMAN > recover DB with backup controlfile > RMAN-06025: no backup of...

  Oracle Database 10g Enterprise Edition Release 10.2.0.2.0
  on RHEL 5
  
  I am trying to execute the following commands to RMAN in a TEST instance and receive errors. I don't have the archive logs in the test OS instance (they were deleted manually... "I know it's a big mistake). Is there a way to always run 'restore database using backup controlfile until Cancel' successfully?
  
  Step 1:
  
  SQL > restore database using backup controlfile until cancel;
  ORA-00279: change 40600690589 September at 2010-04-18 19:38:24 to
  thread 1
  ORA-00289: suggestion: /u001/dbsvr/deverp1/arch_575406629_1_122104.arc
  ORA-00280: change 40600690589 thread 1 is in sequence #122104
  
  Specify the log: {< RET > = suggested |} Filename | AUTO | CANCEL}
  
  Auto
  
  ORA-00308: cannot open archived log
  ' / u001/dbsvr/deverp1/arch_575406629_1_122104.arc'
  ORA-27037: unable to get file status
  Linux-x86_64 error: 2: no such file or directory
  Additional information: 3
  
  
  ORA-01547: WARNING: RECOVER succeeded but OPEN RESETLOGS would get below error
  ORA-01194: file 1 needs a recovery more match
  ORA-01110: data file 1: '+ DATA2/prod/datafile/system.291.716736657 '.
  
  
  ==========================================================
  Step 2:
  
  rman target $ /.
  RMAN >
  run
  {
  allocate channel d1 type disk;
  define archivelog destination to ' / u001/dbsvr/deverp1 / ";
  restore the logseq 122104 than logseq 122204 thread 1 all archivelog;
  output channel d1;
  }
  
  allocated channel: d1
  channel d1: sid = 1971 devtype = DISK
  
  executing command: SET DESTINATION ARCHIVELOG
  
  From restoration to April 19, 10
  
  output channel: d1
  RMAN-00571:
  RMAN-00569:
  = FOLLOWS THE ERROR MESSAGE BATTERY =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the restore command at 19/04/2010 19:45:29
  RMAN-06026: some targets not found - abandonment of restoration
  RMAN-06025: no thread 1 122116 lowscn found 40607234921 seq log backup to restore
  RMAN-06025: no thread 1 122115 lowscn found 40606700559 seq log backup to restore
  
  RMAN >
  
  Published by: CipherDBA on April 19, 2010 18:43

  I see you are using ASM. In this case, I strongly suggest forgetting all about giving orders for recovery of any kind in SQL * more and make sure that you have completely mastered RMAN. RMAN is the only reliable tool that can be used to do anything in ASM. In general, it is a very bad idea to mix managed by users and managed by RMAN recovery mechanisms: you ask just for confusion all round!

  Also, I see someone suggesting 'Restoration until the 122114 seq archivelog', but it is false. If you run the syntax in this way, eventually you recovery until the end of the log 122113 and not enforce a 122114 again, that seems to exist. Numbers you put in an rman command "set until" are not exhaustive, so if you are missing journal 115, it's that you defined up to the number. You do not go around off delimbing a 1 or so just in case where, unless you plan to perform a recovery more incomplete than you can actually go out with.

  Overall, the most appropriate RMAN recovery command in this case would be, I would say:

  crosscheck archivelog all;
  crosscheck backup;
  run {
  set until logseq 122115;
  restore database;
  recover database;}
  

  More seriously: I have no idea why you are trying to recover with a bit of 'backup controlfile' in your syntax. It is only necessary if you have actually lost the original control file and have restored a backup. But since I don't see you do that ('Restore automatic backup controlfile' would be the usual thing to do with RMAN), then there is no need to specify that little bit of syntax in your orders. Now that you once asked Oracle to think he's working with a backup controlfile, however, all bets are off, so if I were you, in view of this is that a test system, I put things in a working state, and then start your recovery from scratch test. Just say 'using backup controlfile' If you actually are. If you simply mount the original controlfile that has not been lost by the disaster, so there no need to mention and the above commands should work properly.

• Archive log backup Question

  Hi all - I am trying to reach a log backup strategy archive. So far, I did the following to mux the archiver process in two different places to allow potential disaster scenarios:
  
  
  1. set log_archive_dest_1 as the location of the FRA:
  
  ALTER SYSTEM SET LOG_ARCHIVE_DEST_1 = 'LOCATION = USE_DB_RECOVERY_FILE_DEST';
  
  2. change the log_archive_dest_2 to be an external location:
  
  ALTER SYSTEM SET LOG_ARCHIVE_DEST_1 = ' LOCATION = ' G:\Backup\ArchiveLogs;
  
  3. ensure to that the LOG_ARCHIVE_DEST_STATE_n for the two sites above is set to enable. It is the default property, and must already be defined.
  
  4. to take effect, a log switch must take place. This can be implemented by using the RMAN backup command:
  
  BACKUP DATABASE MORE ARCHIVELOG;
  
  
  Now that I have the archiver written in two different places, I want to back up the files also in two different places for the same reasons. I assume that I can do it in EM and schedule being new to Oracle but custom task I'm not sure how to go on this subject, and the wizard does not allow me to backup to a location.
  
  Can help or advise if what I'm doing is perhaps not common practice?
  
  Thank you very much

  Kwisatz78 wrote:
  Sorru Orawiss I'm still a bit thick here but how I'm doing backup in two places. For example if I use your script.

  RUN {}
  ALLOCATE CHANNEL d1 DEVICE TYPE DISK FORMAT ' / u01/backups/%U';
  ALLOCATE CHANNEL d2 DEVICE TYPE DISK FORMAT ' / u02/backups/%U';
  BACKUP DATABASE MORE ARCHIVELOG;
  OUTPUT CHANNEL;
  }

  I change the /u01/backups/%you to some thing like + DBFLASH_SOA and keep the auto manage the appearance of the FRA?

  Thank you

  See below; Only Autobackup spfile + controlfile is considered to be accompanied in the FRA. Because I choose CONFIGURE CONTROLFILE AUTOBACKUP.

  If you choose to specify the locations of your RMAN scripts, the FRA's automatic space management will not be enabled for these backups.

  So in my example, the format of the backup command clause sends the backup the physical location "/ home/oracle/backups/fra" (not the FRA) and ' / home/oracle/backup. There is no way to specify the FRA as the destination in a format clause, so if you format in your backup, by definition statement, you do not send something of the FRA.

  SQL> show parameter db_recovery
  
  NAME                         TYPE      VALUE
  ------------------------------------ ----------- ------------------------------
  db_recovery_file_dest               string      /home/oracle/backups/fra
  db_recovery_file_dest_size          big integer 4G
  SQL> 
  
  SQL> select  SUM(NUMBER_OF_FILES) from v$flash_recovery_area_usage;
  
   SUM(NUMBER_OF_FILES)
  --------------------
         33
  
  SQL> 
  
  RMAN> show all;
  
  using target database control file instead of recovery catalog
  RMAN configuration parameters for database with db_unique_name ORAWISS are:
  CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
  CONFIGURE BACKUP OPTIMIZATION OFF; # default
  CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
  CONFIGURE CONTROLFILE AUTOBACKUP ON;
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
  CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 2;
  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 ON;
  CONFIGURE ENCRYPTION ALGORITHM 'AES192';
  CONFIGURE COMPRESSION ALGORITHM 'medium' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE;
  CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
  CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/home/oracle/backups/scncf/sncf.ora';
  
  RMAN> 
  
  RMAN> run{
     sql 'alter system set encryption wallet open identified by "wissem"';
     ALLOCATE CHANNEL d1 DEVICE TYPE DISK FORMAT '/home/oracle/backups/%U';
     ALLOCATE CHANNEL d2 DEVICE TYPE DISK FORMAT '/home/oracle/backups/fra/%U';
     BACKUP DATABASE PLUS ARCHIVELOG;
     RELEASE CHANNEL d1;
     RELEASE CHANNEL d2;
   }2> 3> 4> 5> 6> 7> 8> 
  
  sql statement: alter system set encryption wallet open identified by "wissem"
  
  allocated channel: d1
  channel d1: SID=410 device type=DISK
  
  allocated channel: d2
  channel d2: SID=28 device type=DISK
  
  Starting backup at 01-JUN-11
  current log archived
  channel d1: starting compressed archived log backup set
  channel d1: specifying archived log(s) in backup set
  input archived log thread=1 sequence=169 RECID=271 STAMP=752254789
  input archived log thread=1 sequence=170 RECID=272 STAMP=752525448
  input archived log thread=1 sequence=171 RECID=275 STAMP=752531841
  channel d1: starting piece 1 at 01-JUN-11
  channel d2: starting compressed archived log backup set
  channel d2: specifying archived log(s) in backup set
  input archived log thread=1 sequence=172 RECID=277 STAMP=752684381
  input archived log thread=1 sequence=173 RECID=278 STAMP=752684468
  channel d2: starting piece 1 at 01-JUN-11
  channel d2: finished piece 1 at 01-JUN-11
  piece handle=/home/oracle/backups/fra/2qmdq3dk_1_1 tag=TAG20110601T150108 comment=NONE
  channel d2: backup set complete, elapsed time: 00:00:03
  channel d1: finished piece 1 at 01-JUN-11
  piece handle=/home/oracle/backups/2pmdq3dk_1_1 tag=TAG20110601T150108 comment=NONE
  channel d1: backup set complete, elapsed time: 00:00:07
  Finished backup at 01-JUN-11
  
  Starting backup at 01-JUN-11
  channel d1: starting compressed full datafile backup set
  channel d1: specifying datafile(s) in backup set
  input datafile file number=00003 name=/home/oracle/app/oracle/oradata/ORAWISS/undotbs01.dbf
  input datafile file number=00002 name=/home/oracle/app/oracle/oradata/ORAWISS/sysaux01.dbf
  input datafile file number=00004 name=/home/oracle/app/oracle/oradata/ORAWISS/users01.dbf
  input datafile file number=00008 name=/home/oracle/app/oracle/oradata/ORAWISS/mgmt_ad4j.dbf
  channel d1: starting piece 1 at 01-JUN-11
  channel d2: starting compressed full datafile backup set
  channel d2: specifying datafile(s) in backup set
  input datafile file number=00001 name=/home/oracle/app/oracle/oradata/ORAWISS/system01.dbf
  input datafile file number=00007 name=/home/oracle/app/oracle/oradata/ORAWISS/mgmt.dbf
  input datafile file number=00005 name=/home/oracle/app/oracle/oradata/ORAWISS/example01.dbf
  input datafile file number=00006 name=/home/oracle/app/oracle/oradata/ORAWISS/mgmt_ecm_depot1.dbf
  input datafile file number=00009 name=/home/oracle/app/oracle/oradata/ORAWISS/fb_data_archive.dbf
  channel d2: starting piece 1 at 01-JUN-11
  
  channel d1: finished piece 1 at 01-JUN-11
  piece handle=/home/oracle/backups/2rmdq3ds_1_1 tag=TAG20110601T150116 comment=NONE
  channel d1: backup set complete, elapsed time: 00:00:45
  channel d2: finished piece 1 at 01-JUN-11
  piece handle=/home/oracle/backups/fra/2smdq3ds_1_1 tag=TAG20110601T150116 comment=NONE
  channel d2: backup set complete, elapsed time: 00:01:15
  Finished backup at 01-JUN-11
  
  Starting backup at 01-JUN-11
  current log archived
  channel d1: starting compressed archived log backup set
  channel d1: specifying archived log(s) in backup set
  input archived log thread=1 sequence=174 RECID=280 STAMP=752684552
  channel d1: starting piece 1 at 01-JUN-11
  channel d1: finished piece 1 at 01-JUN-11
  piece handle=/home/oracle/backups/2tmdq3g8_1_1 tag=TAG20110601T150232 comment=NONE
  channel d1: backup set complete, elapsed time: 00:00:01
  Finished backup at 01-JUN-11
  
  Starting Control File and SPFILE Autobackup at 01-JUN-11
  piece handle=/home/oracle/backups/fra/ORAWISS/autobackup/2011_06_01/o1_mf_s_752684554_6ydg3bww_.bkp comment=NONE
  Finished Control File and SPFILE Autobackup at 01-JUN-11
  
  released channel: d1
  
  released channel: d2
  
  RMAN> 
  
  [oracle@wissem ~]$ rlsqlplus 
  
  SQL*Plus: Release 11.2.0.1.0 Production on Wed Jun 1 15:03:02 2011
  
  Copyright (c) 1982, 2009, Oracle.  All rights reserved.
  
  Enter user-name: sys as sysdba
  Enter password: 
  
  Connected to:
  Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
  With the Partitioning, OLAP, Data Mining and Real Application Testing options
  
  SQL> select  SUM(NUMBER_OF_FILES) from v$flash_recovery_area_usage;
  
  SUM(NUMBER_OF_FILES)
   --------------------
              34
  
  [oracle@wissem ~]$ ls -rtl /home/oracle/backups/
  total 113424
  drwxr-xr-x 2 oracle oinstall      4096 Jan 15 00:07 arch
  drwxr-xr-x 2 oracle oinstall      4096 Jan 15 00:07 scncf
  -rw-r----- 1 oracle oinstall  11566080 Jun  1 15:01 2pmdq3dk_1_1
  drwxr-xr-x 3 oracle oinstall      4096 Jun  1 15:01 fra
  -rw-r----- 1 oracle oinstall 104546304 Jun  1 15:01 2rmdq3ds_1_1
  -rw-r----- 1 oracle oinstall     15872 Jun  1 15:02 2tmdq3g8_1_1
  [oracle@wissem ~]$ ls -rtl /home/oracle/backups/fra
  total 242424
  drwxr-x--- 5 oracle oinstall      4096 Jan 21 11:04 ORAWISS
  -rw-r----- 1 oracle oinstall   9469952 Jun  1 15:01 2qmdq3dk_1_1
  -rw-r----- 1 oracle oinstall 238764032 Jun  1 15:02 2smdq3ds_1_1
  [oracle@wissem ~]$ 
  

• 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

• RMAN-06820: WARNING: unable to archive the current log on the primary database

  I got the following exception when I try to backup the data files and the archivelogs on the physical by uisng RMAN standby database.

  RMAN-06820: WARNING: unable to archive the current log on the primary database

  Target ORACLE database error:

  ORA-17629: unable to connect to the remote database server

  ORA-17627: ORA-00942: table or view does not exist

  It's the backup script

  "

  connection target sys/oracle

  Configure controlfile autobackup on;

  Run {}

  nocfau together;

  allocate channel ch01 device type disc format ' / test/%U';

  allocate channel ch02 device type disc format ' / test/%U';

  backup database copy archivelog;

  backup copy current controlfile;

  }

  "

  And there is no error ora in the primary alert log.

  I was able to tnsping two server (primary/secondary) properly and could also primary of the remote login on standby db server and switch logfile. I read there is a very similar thread, but it has failed so I post again and hope I could get a few clues. Thank you.

  Hello again;

  Try to change this:

  connection target sys/oracle

  to something like this:

  RMAN target sys/password@PRIMARY auxiliary.

  Complete example:

  http://www.Visi.com/~mseberg/data_guard/duprman2.html

  Best regards

  mseberg

• RMAN retention policy does not log source archive

  Oracle 11.2
  Windows server 2008
  CONFIGURE ARCHIVELOG DELETION POLICY TO SAVED 1 TIME TO THE DISK.
  
  I ran after command
  TIME BACKUP ARCHIVELOG ' SYSDATE-6' UNTIL ' SYSDATE-1';
  
  RMAN > ARCHIVELOG BACKUP OF TIME ' SYSDATE-6' until ' SYSDATE-1';
  
  From backup may 29, 13
  using the control file of the target instead of recovery catalog database
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: SID = 386 type device = DISK
  allocated channel: ORA_DISK_2
  channel ORA_DISK_2: SID = 773 type device = DISK
  jump the C:\ARC\ARC0000000564_0808506935.0001 archived log file; already supported
  up to 1 times
  \\172.16.1.2\DATABASE_BACKUP\RMAN\ARCHIVE_34\ARC00 of the archived log file skipping
  00000564_0808506935.0001; already saved 1 time
  \\172.16.1.2\DATABASE_BACKUP\RMAN\ARCHIVE_34\ARC00 of the archived log file skipping
  00000565_0808506935.0001; already saved 1 time
  jump the C:\ARC\ARC0000000565_0808506935.0001 archived log file; already supported
  up to 1 times
  \\172.16.1.2\DATABASE_BACKUP\RMAN\ARCHIVE_34\ARC00 of the archived log file skipping
  00000566_0808506935.0001; already saved 1 time
  jump the C:\ARC\ARC0000000566_0808506935.0001 archived log file; already supported
  up to 1 times
  jump the C:\ARC\ARC0000000567_0808506935.0001 archived log file; already supported
  up to 1 times
  \\172.16.1.2\DATABASE_BACKUP\RMAN\ARCHIVE_34\ARC00 of the archived log file skipping
  00000567_0808506935.0001; already saved 1 time
  jump the C:\ARC\ARC0000000568_0808506935.0001 archived log file; already supported
  up to 1 times
  \\172.16.1.2\DATABASE_BACKUP\RMAN\ARCHIVE_34\ARC00 of the archived log file skipping
  00000568_0808506935.0001; already saved 1 time
  \\172.16.1.2\DATABASE_BACKUP\RMAN\ARCHIVE_34\ARC00 of the archived log file skipping
  00000569_0808506935.0001; already saved 1 time
  jump the C:\ARC\ARC0000000569_0808506935.0001 archived log file; already supported
  up to 1 times
  \\172.16.1.2\DATABASE_BACKUP\RMAN\ARCHIVE_34\ARC00 of the archived log file skipping
  00000570_0808506935.0001; already saved 1 time
  jump the C:\ARC\ARC0000000570_0808506935.0001 archived log file; already supported
  up to 1 times
  Backup finished 29 May 13
  
  RMAN >
  
  
  According to policy to delete rman does not delete source archive logs.

  This is the backup... command where the delete command

  obsolete report;

  Confirm if the archivelog you want to remove, then

  remove obsolete;

  so if you had manually deleted archivelogs use below to remove the entry of records controlfile

  overlap archivelog all;

  list expired archivelog all;

  REMOVE EXPIRED ARCHIVELOG ALL;

  edited part-

  read [url http://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmconfb.htm#CHDCFHBG]

  This plocy deletion makes these archivelog eligible for deletion. They will be deleted automatocally if they are inside the FRA FRA is short of space.

  Published by: Patricia kebe on May 29, 2013 01:16

• RMAN-08120: WARNING: log archived not deleted, not yet applied watch

  I get RMAN-08120: WARNING: journal archived not deleted, not yet applied watch on primaries
  but when I run under query, I get the same result of primary and backup
  
  SQL > select max(sequence#) from v$ archived_log;
  
  MAX(SEQUENCE#)
  --------------
  44051
  
  SQL >
  
  
  Eve is a log switch behind only!

  Hello;

  If RMAN tries to remove an archive which is not yet applied in standby log, you see the RMAN-08120

  It's a good thing. As long as you don't have any archives for days on standby, you probably don't have a problem.

  What are your RMAN settings for the database of the day before?

  MetaLink Note: 361182.1 can help too. Or Note 1079953.1

  Your main, make sure that:

  CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
  

  Please consider closing some of your old issues to clean up the forum.

  Best regards

  mseberg

• remove the logs of archiving in log_archive_dest_2 with RMAN

  Hello
  
  Installation program:
  Primary DB: oracle 10g
  Standby DB: Oracle 10g
  Physical active DataGuard paused.
  
  We nun RMAN on the primary db every night, which also removes the archives connects log_archive_dest_1 located on the primary server. How to activate the same working RMAN delete logs archiving in log_archive_dest_2 located on the backup server.
  
  -Shashi

  Hey Shashi,

  You can use similar job on your backup server for the removal of the old archivelogs in about 1 week. Also, please pay attention to the setting of the RMAN ARCHIVELOG DELETION POLICY on the primary database. Maybe it's to set as APPLIES ON STANDBY to prevent the removal of the archivelogs not yet applied to the primary.

  Best regards
  Alex

• RMAN-06025 during replication

  Hello list,
  
  
  IAM trying to duplicate a database to a new host, it's my script
  
  ______________________________
  double-target database orcl pfile='D:\oracle\product\10.2.0\db_3\database\Clone\initorcl.ora'
  size of the logfile "D:\oracle10g\orcl\redo01.dbf" 50 m,
  *'D:\oracle10g\orcl\redo02.dbf"size 50 m, *.
  *'D:\oracle10g\orcl\redo03.dbf"size 50 m; *
  _________________________________
  
  I copied a backup of database to three days before the coated and the archivelogs generated since the last backup of both duplication to the new host.
  
  In vain the duplication during recovery to this statement:
  
  RMAN-06025: no s Log-Threads 1 seq 214 lowscn 2683354 restore backup not found
  RMAN-06025: Kein backup logs-Threads 1 seq 213 lowscn 2656377 zur found time.
  
  Here's my question: during duplication, rman sees only the archivelogs in backupup if iam replication to a remote host?
  and how I will duplicate the last archiving genrated log if I copied all archivelogs just before I start replication?, I don't want to take a new backup simply always use the last generated backup.
  
  Windows 2003 Server
  Database 10g SE.
  
  Thanks for your advice.

  Hey Walker,
  (Q)
  RMAN apply archive logs, even if they are not saved but copied to the remote host?
  It depends on the settings for the destination of the newspaper archive and archive log format side auxiliary if rman can apply to your archive logs.

  (I normally use rman to back up the archive logs and use the pieces to the auxiliary copy.) During the recovery phase of the cloning process files from archive get restored to the auxiliary archivelog dest and get the format as set out in the pfile (s) on the auxiliary)

  Kind regards
  Tycho