RMAN backup runs twice (sequential) even if it is not configured in this way

Similar Questions

• vDI continue to go to sleep even though to the Horizon and Wyse Teradici is not configured.  To view group policies are also configured in this way.

  Any ideas?

  Have you checked the power options in Windows? You have a screen saver?

• RMAN backup permission problem

  My RMAN backup is scheduled.
  
  Even backup script fails sometimes and sometimes executed successfully
  When fails, it gives the following error.
  
  Your "cron" job the xxxx
  / U07/RMAN/scripts/call_arch_bkup. SCP
  
  produces the following output:
  
  
  Recovery Manager: release 9.2.0.1.0 - 64 bit Production
  
  Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
  
  connected to target database: xxxx
  connected to the recovery catalog database
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-00554: initialization of the package manager internal collection failed
  RMAN-04005: target database error:
  ORA-09925: cannot create the audit trail file
  SVR4 error: 13: permission denied
  Additional information: 9925
  
  
  If there is permission problem then there a few times, it runs successfully.

  It totally depends on your condition. Security can you move your old files to another location, course and then run your command?

• RMAN backup shell script

  Hello
  on 10 G R2 in AIX 6.1
  
  I'm looking for an RMAN backup Shell script.
  
  In addition, if we should connect like this:

  rman nocatalog target sys/password@myDB << EOF
  backup as compressed backupset format '$savdir/ctl_%d_%T_%s_%p' current controlfile;
  exit
  EOF

  How to avoid writing the password in shell script?
  
  Thank you.

  There is a standard 'backup' option in the control of the database.
  You don't need any shell script and you're wasting your time by establishing a.

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

• IPhone Bluetooth pair with car even when I do not have a call

  I recently started having a problem with my IPhone 4 s automatically picking up the sound system in cars, even if I did not call. This happens as soon as I turn on the car. When I press the keys on the phone I hear the click key in the car sound system, and the radio is removed. This happened with a Chevy Volt and a Ford CMax, then this is the phone, not the car. The only way I can make the radio work is to turn off the Bluetooth on my phone. It started only in the last week or two and I downloaded an update of the phone on the right, then, that could be the problem. Any suggestions?

  If the phone is paired with the car, it will happen.

  Can you not turn off the twinning/forget the connection?

• Cannot retrieve table of rman backup

  For the test, I want to recover the deleted table of rman backup.

  I do oracle 11g VM.  the next step, I've applied but could not recover the table.

  RMAN > backup database;

  On sqlplus create connect scott/Tiger

  create table scott.emp1 (col1 varchar2 (10));

  Insert into the value emp1 (col1) ('Young');

  commit;

  Select * from emp1.

  He shows me a single line successfully.

  Now, I have connection to the sys as sysdba

  sqlplus > alter system switch logfile;

  After I remove the table.

  Now to retrieve the table I restored the database on the same virtual machine.

  RMAN > restore database;

  RMAN > restore database;

  RMAN > alter database open;

  sqlplus I've issued

  sqlplus > select * from scott.emp1;

  table or view does not exist.

  any help how to recover the deleted table of rman backup

  Hello

  Check this test scenario

  SQL > create table TEST2 in select * from emp;

  Table created.

  SQL > select count (*) from TEST2;

  COUNT (*)

  ----------

  15

  SQL > select TO_CHAR (SYSDATE, "MON-DD-YYYY HH24:MI:SS) twice;

  TO_CHAR (SYSDATE,'DD-)

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

  2013-SEPT-10 10:57:05

  SQL > alter system switch logfile;

  Modified system.

  SQL > drop table TEST2 is serving;

  Deleted table.

  SQL > immediate shu

  rman target $ [oracle@vnode MYSHELL].

  Recovery Manager: release 11.2.0.2.0 - Production kills Sep 10 10:58:39 2013

  Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

  connected to target database: DDTEST (DBID = 1667776968, is not open)

  RMAN > run {}

  until ' to_date (' 10 10:57 ',' yyyy Sep 2013 my dd HH24 ') ";

  restore the database;

  recover the database;

  ALTER database open resetlogs;

  } 2 > 3 > 4 > 5 > 6 >

  ...........

  ...........

  media recovery complete, duration: 00:00:02

  Finished recover 13 / SEP / 10

  open database

  RMAN > exit

  SQL > define pages of lin 200 100

  SQL > select count (*) from test2;

  COUNT (*)

  ----------

  15

  HTH

• RMAN: Backups not exipring after the window of redundancy.

  Hello

  I meet backup sbt_tape and the use of the slot block:

  run{
  ALLOCATE CHANNEL C1 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so,
  ENV=(STORAGE_UNIT=CH2-nwtdb-Oracle, BACKUP_HOST=172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
  ALLOCATE CHANNEL C2 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so,
  ENV=(STORAGE_UNIT=CH2-nwtdb-Oracle, BACKUP_HOST=172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
  ALLOCATE CHANNEL C3 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so,
  ENV=(STORAGE_UNIT=CH2-nwtdb-Oracle, BACKUP_HOST=172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
  ALLOCATE CHANNEL C4 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so,
  ENV=(STORAGE_UNIT=CH2-nwtdb-Oracle, BACKUP_HOST=172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
  backup incremental level 0 database filesperset=1 format '%d_L0_DF%f_%T_%u.dbf' tag 'DB_L0_DF_#_DT_UNQNO';
  backup current controlfile format '%d_L0_CF_%T_%u.ctl' tag 'DB_L0_CF_DT_UNQNO';
  backup incremental level 0 archivelog all filesperset=1 format '%d_L0_AL_%h_%e_%T_%u.arc' tag 'DB_L0_ARC#_DT_UNQNO';
  crosscheck backup of database;
  crosscheck backup of archivelog all;
  delete noprompt expired backup of database;
  delete noprompt expired backup of archivelog all;
  }
  

  My backups work perfectly, but for some reason, my backups expire even though my redudancy is set to 7 days.

  In my dest backup, I have backups as old as March 13, which should have been expired since a long time back.

  Any ideas what could be wrong?

  RMAN> show all;
  using target database control file instead of recovery catalog
  RMAN configuration parameters for database with db_unique_name IWTPR are:
  CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 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 '%F'; # default
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
  CONFIGURE DEVICE TYPE DISK PARALLELISM 4 BACKUP TYPE TO COMPRESSED BACKUPSET;
  CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 4 BACKUP TYPE TO BACKUPSET;
  CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
  CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
  CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
  CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
  CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS  'SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so, ENV=(STORAGE_UNIT=CH2-nwtdb-Oracle, BACKUP_HOST=172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
  CONFIGURE MAXSETSIZE TO UNLIMITED;
  CONFIGURE ENCRYPTION FOR DATABASE OFF;
  CONFIGURE ENCRYPTION ALGORITHM 'AES128';
  CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE;
  CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
  CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+IWTPRFRA/IWTPR/snapcf_IWTPR.f';
  CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+IWTPRFRA/iwtpr/snapcf_iwtpr.f';
  

  Thanks in advance,

  aBBy.

  Details of env: RAC 4 node cluster running 11.2.0.3.4 GI/RDBMS on RHEL 5. 6

  AB007 wrote:

  Hello

  I meet backup sbt_tape and the use of the slot block:

  1. Run {}
  2. ALLOCATE CHANNELS C1 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so.
  3. ENV = (STORAGE_UNIT = CH2-nwtdb-Oracle, BACKUP_HOST = 172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
  4. ALLOCATE channel C2 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so,
  5. ENV = (STORAGE_UNIT = CH2-nwtdb-Oracle, BACKUP_HOST = 172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
  6. ALLOCATE CHANNELS C3 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so.
  7. ENV = (STORAGE_UNIT = CH2-nwtdb-Oracle, BACKUP_HOST = 172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
  8. ALLOCATE CHANNELS C4 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so.
  9. ENV = (STORAGE_UNIT = CH2-nwtdb-Oracle, BACKUP_HOST = 172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
  10. filesperset database backup incremental level 0 = 1 format '% d_L0_DF%f_%T_%u.dbf' tag "DB_L0_DF_ #_DT_UNQNO";
  11. backup current controlfile '% d_L0_CF_%T_%u.ctl' format tag "DB_L0_CF_DT_UNQNO".
  12. incremental backup of level 0 archivelog all filesperset = 1 format '% d_L0_AL_%h_%e_%T_%u.arc' tag "DB_L0_ARC #_DT_UNQNO";
  13. cross-checking of backup of database;
  14. backup duplication of the archivelog all;
  15. delete noprompt expired backup of database;
  16. delete expired backup noprompt to archivelog all;
  17. }

  My backups work perfectly, but for some reason, my backups expire even though my redudancy is set to 7 days.

  In my dest backup, I have backups as old as March 13, which should have been expired since a long time back.

  Any ideas what could be wrong?

  1. RMAN > show all.
  2. using the control file of the target instead of recovery catalog database
  3. RMAN settings for database with db_unique_name IWTPR are:
  4. CONFIGURE RETENTION POLICY TO RECOVERY OF 7-DAY WINDOW;
  5. CONFIGURE BACKUP OPTIMIZATION
  6. CONFIGURE THE TYPE OF DEFAULT DEVICE TO 'SBT_TAPE ';
  7. CONFIGURE CONTROLFILE AUTOBACKUP
  8. CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
  9. CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO "%F" # by default
  10. SET UP THE DEVICE TYPE DISK PARALLELISM 4 TYPE OF BACKUP TO COMPRESSED BACKUPSET;
  11. SET UP THE DEVICE TYPE 'SBT_TAPE' PARALLELISM 4 TYPE OF BACKUP BACKUPSET.
  12. CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1;
  13. CONFIGURE BACKUP COPIES OF DATA FILE FOR THE 'SBT_TAPE' UNIT 1;
  14. CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1;
  15. CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE 'SBT_TAPE' 1;
  16. CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so, ENV is (STORAGE_UNIT = CH2-nwtdb-Oracle, BACKUP_HOST = 172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
  17. CONFIGURE MAXSETSIZE TO UNLIMITED;
  18. CONFIGURE THE DATABASE ENCRYPTION
  19. CONFIGURE THE ENCRYPTION ALGORITHM "AES128";
  20. CONFIGURE COMPRESSION ALGORITHM 'BASIC' AND 'DEFAULT' LIBERATION OPTIMIZE FOR TRUE LOAD;
  21. CONFIGURE THE NONE ARCHIVELOG DELETION POLICY;
  22. CONFIGURE the SNAPSHOT CONTROLFILE NAME to "+ IWTPRFRA/IWTPR/snapcf_IWTPR.f";
  23. CONFIGURE the SNAPSHOT CONTROLFILE NAME to "+ IWTPRFRA/iwtpr/snapcf_iwtpr.f";

  Thanks in advance,

  aBBy.

  Details of env: RAC 4 node cluster running 11.2.0.3.4 GI/RDBMS on RHEL 5. 6

  You are confusing "expired" with "obsolete".

  When a backupset is created, an account of which is placed in the control file.

  If you backup ' overlap ', rman checks these records against reaility.  If no backup turns out have disappeared, his file is marked as "expired".  That follow-up with a 'delete expired backup', and missing backups (expired) records will be deleted from the repository.

  What you want is "delete obsolete.  Which will remove any backup that is no longer necessary to enforce the retention period.

  BTW, "redundancy" and "x days" are mutually exclusive.

• RMAN backup recovery point in time

  Hi all
  
  Here's my rman backup script configuration and rman.
  Because of size constraints I save my logs to archive by rman and delete.
  I wanted to know if it was possible to go at a certain time using these archiving logs.
  ex: -.
  Racing script at 10:00 in the evening daily say it ran on March 1 and March 2, to 22:00, if I want to recover until 14:00 on March 2, will be March 2 backup enough or I'll need March 1 backup and archive logs until 14:00 for which I need to physcially archive backup logs daily , with rman.
  

  RUN
  { 
    ALLOCATE CHANNEL ch1 DEVICE TYPE DISK;
    ALLOCATE CHANNEL ch2 DEVICE TYPE DISK;
    ALLOCATE CHANNEL ch3 DEVICE TYPE DISK;
    BACKUP DATABASE INCLUDE CURRENT CONTROLFILE format 'G:\Oracle\flash_recovery_area\TEST\BACKUPSET\tmp\rman_backup\df_%d_%s_%p_%T';
    DELETE NOPROMPT OBSOLETE;
    SQL "ALTER SYSTEM ARCHIVE LOG CURRENT";
    BACKUP ARCHIVELOG ALL DELETE INPUT format 'G:\Oracle\flash_recovery_area\TEST\BACKUPSET\tmp\rman_backup\arc_%d_%s_%p_%T';
  
  }

  RMAN configuration parameters for database with db_unique_name TEST are:
  CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
  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 'G:\Oracle\flash
  _recovery_area\TEST\BACKUPSET\tmp\RMAN_BACKUP\CTL_%F';
  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 COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOA
  D TRUE ; # default
  CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
  CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'C:\ORACLE\PRODUCT\11.2.0\DBHOME_1\DATABA
  SE\SNCFTEST.ORA'; # default

  Hello;

  RMAN> startup mount
  RMAN> restore database until time "to_date('02-MAR-2013 09:00:00', dd-mon-rrrr hh24:mi:ss')";
  RMAN> recover database;
  RMAN> alter database open; 
  

  Best regards

  mseberg

• Switch journal during the RMAN backup

  I saw a lot of scripts in RMAN backup that a manual log switching is performed in the first line of the script? That is - this goal, just to write the changes necessary to rebuild instructions DML/DDL of redo log online and start archiving process so db runs in log mode archive?

  918868 wrote:
  I saw a lot of scripts in RMAN backup that a manual log switching is performed in the first line of the script? That is - this goal, just to write the changes necessary to rebuild instructions DML/DDL of redo log online and start archiving process so db runs in log mode archive?

  This could be the only reason, but even this is not necessary, as would a log switch automatically to push the current log file again to do is archive log and include it in the RMAN backup.

  Aman...

• make it work how I want that he the rman backup-shared-disk fix - up

  Network of Oracle greetings!
  (Oracle 10g enterprise edition on windows server 2003 platform)
  
  http://www.DBA-Oracle.com/t_os_error_os5_access_denied.htm
  
  is a link where a fix on the location of the rman backups is suggested. It asks me to change logon oracleservicesid. my database is what runs a Web site. When I change the connection oracleservicesid the Web site is no longer functions.this is not desirable.
  How can I fix it?
  Even on my test server that hosts the databases, change the opening of session oracleservicesid to administrator, disable all connections made to the database on the local network using SQL developer. How to not let that happen?
  
  Help, please
  Thanks in advance
  cordially 946207
  
  Edited by: 946207 July 14, 2012 03:01

  10g is desupported for a long time.
  Your question is you backup to a network drive.
  The solution provided by Donald Burleson is correct.
  Why the site no longer works is not clear that you provide no error message, or whatever.
  Course, a simple solution would be to buy an extra drive to connect directly to the server.
  Your post is poorly understood why you plan to implement that.
  Also, your statement on the test server is far too vague. You did not yet provide no error message.

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

• format + RMAN backup

  Dear friends,
  
  Seasonal greetings.
  
  I use these commands to make my backup.
  

  backup database tag "everyday_full_bkup" format='D:\Oracle_Backup\Database_Name\%I_%T.bkp';

  Can I use the .bkp?
  
  This is the message I get when I run the above, receives the command.
  

  Starting backup at 11-MAY-10
  using channel ORA_DISK_1
  channel ORA_DISK_1: starting full datafile backupset
  channel ORA_DISK_1: specifying datafile(s) in backupset
  input datafile fno=00002 name=D:\ORACLE\DATA\MARSDB\UNDO_01.DBF
  input datafile fno=00001 name=D:\ORACLE\DATA\MARSDB\SYSTEM_01.DBF
  input datafile fno=00004 name=D:\ORACLE\DATA\MARSDB\DATA_01.ORA
  input datafile fno=00005 name=D:\ORACLE\DATA\MARSDB\INDEXES_01.ORA
  input datafile fno=00003 name=D:\ORACLE\DATA\MARSDB\SYSAUX_01.DBF
  input datafile fno=00006 name=D:\ORACLE\DATA\MARSDB\XXSMALLTABS_01.ORA
  channel ORA_DISK_1: starting piece 1 at 11-MAY-10
  channel ORA_DISK_1: finished piece 1 at 11-MAY-10
  piece handle=D:\ORACLE_BACKUP_DATA\MARSDB\1970380511_20100511 tag=EVERYDAY_FULL_BKUP comment=NONE
  channel ORA_DISK_1: backup set complete, elapsed time: 00:00:25
  channel ORA_DISK_1: starting full datafile backupset
  channel ORA_DISK_1: specifying datafile(s) in backupset
  including current control file in backupset
  channel ORA_DISK_1: starting piece 1 at 11-MAY-10
  RMAN-00571: ===========================================================
  RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
  RMAN-00571: ===========================================================
  RMAN-03009: failure of backup command on ORA_DISK_1 channel at 05/11/2010 11:03:01
  ORA-19504: failed to create file "D:\ORACLE_BACKUp\DatabaseName\1970380511_20100511"
  ORA-27038: created file already exists
  OSD-04010: <create> option specified, file already exists

  Seeing this error, I removed the backup:
  

  list backup;
  delete backup piece n; 

  n is based on the number that I see in the backup from the list.
  
  Since then, I thought that set up channel might help, tried this but still getting the same error.
  

  RMAN>
  
  CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT 'the path\%F.bkp';
  BACKUP DATABASE tag "everyday_full_bkup";

  Want to clarify, if the channel set is only to set the path where is made the backup as well as the naming convention?
  
  Just to make sure that everything is fine, I checked
  

  crosscheck backup;

  and all is well.
  
  I even tried
  

  rman> backup database;

  and still the same error.
  
  Please throw some light on this. Please guide me. I'm desperate.
  
  Thanking you in advance.
  
  See you soon!
  
  Nith
  
  Published by: user645399 on May 11, 2010 11:00
  
  Published by: user645399 on May 11, 2010 11:36
  
  Published by: user645399 on May 11, 2010 11:53

  Hi.There occur error because you used format(for backup) is a mistake. Because used this format, rman cannot generate a unique name for each backupset. RMAN create the first backup set using this format, then want to also eponymous and the error occur (backupsets cannot be the same name). You can use %U this guarantees uniqueness in
  generated backups.
  See also
  http://SS64.com/ora/rman_format_string.html

• RMAN - backup on FRA and somewhere else

  Hi all
  
  I would like to configure RMAN, so it would create two copies of backupset...
  In the recovery area Flash (maintenance of the FRA nice, i.e. < file_name > F:\ora_fra\db_name\backupset\ directory structure) and the other to a custom domain (say I:\ora_bck\ < Filename >).
  
  I tried on:
  RMAN > 2 copies of backup of database format 'F:\ora_flash\%U', 'I:\ora_bck\%U ';
  But this resulted in the creation of a file directly in F:\ora_flash (not in accordance with the FRA directory structure, so I don't really know if this file is or is not included in FRA)
  
  If I do the following:
  RMAN > backup database;
  RMAN > run {}
  2 > backup copies of the value = 2;
  3 > backupset backup completed between ' sysdate-1' and 'sysdate' format 'I:\ora_bck\%U ';
  {4 >}
  To do this, what I expect of her (a good copy in FRA, second on I :), but I can even smell it is a terrible solution.)
  
  Any ideas? (The requirement must perform full backup of the DB from time to time in 2 places - FRA and disk I :)
  
  Thank you.
  Adam

  Unfortunately, two-sided printing is unusable during the creation of files in the flash recovery area. BACKUPSET BACKUP is an option, or you can just use a command of the o/s to copy, and then if necessary CATALOGUE files.

• RMAN backup location must change and remove obsolete

  Dear Experts,

  I'm working on the following environment,

  Operating system: Windows server 2012 R2

  Oracle version: 11.2.0.1.0 release

  Type of RMAN backup: Cumulative (preferred by the direction and I can't change it in differential backup)

  My current situation,

  I set up RMAN and H: drive for purposes of backup and G: for Archivelog.

  Recently, my city was covered by the flood waters and the server works not for a week so that we delete obsolete level 0 does not work.

  Currently there is not enough space to run a level 1 and level 0, while I should change the backup location.

  My Question is,

  (1) I need to change this location of drive H: to G: drive backup backup correctly without error not enough space.

  (2) after having taken a level 1 and level 0, depending on my 1 redundancy, RMAN mechanism should delete obsolete backup disk without failure G: and H:.

  Kindly help me how to get to my need. This will help me, thanks in advance

  You can

  1. replace the DB_RECOVERY_FILE_DEST G:

  2 run backups

  3. wait for the DELETE OBSOLETE delete obsolete backups of H:

  and then

  4. change the DB_RECOVERY_FILE_DEST return h as it was more early

  In this way, you don't have to use the FORMAT or CHANNEL of CONFIGURE commands (I was referring to CONFIGURE CHANNEL, not ALLOCATE CHANNEL) to change the destination of the backup

  Hemant K Collette

• Waiting for redo log file missing when restore main database using RMAN backup that was taken on the database physical standby

  Here's my question after tons of research and test without have the right solutions.

  Target:

  (1) I have a 12.1.0.2 database unique main enterprise 'testdb' as database instance running on the server "node1".

  (2) I created physical standby database "stbydb" on the server "node2".

  (3) DataGuard running on the mode of MaxAvailability (SYNC) with roll forward in real time 12 default c apply.

  (4) primary database has 3 groups of one-man redo. (/oraredo/testdb/redo01.log redo02.log redo03.log)

  (5) I've created 4 standby redo logfiles (/oraredo/testdb/stby01.log stby02.log stby03.log stby04.log)

  (6) I do RMAN backup (database and archivelog) on the site of relief only.

  (7) I want to use this backup for full restore of the database on the primary database.

  He is a DR test to simulate the scenario that has lost every primary & Eve total servers.

  Here is how to save, on the database pending:

  (1) performance 'alter database recover managed standby database Cancel' to ensure that compatible data files

  (2) RMAN > backup database;

  (3) RMAN > backup archivelog all;

  I got elements of backup and copied to primary db Server something like:

  /Home/Oracle/backupset/o1_mf_nnndf_TAG20151002T133329_c0xq099p_.BKP (data files)

  /Home/Oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.BKP (spfile & controlfile)

  /Home/Oracle/backupset/o1_mf_annnn_TAG20151002T133357_c0xq15xf_.BKP (archivelogs)

  So here's how to restore, on the main site:

  I clean all the files (data files, controlfiles oder all gone).

  (1) restore spfile from pfile

  RMAN > startup nomount

  RMAN > restore spfile from pfile ' / home/oracle/pfile.txt' to ' / home/oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.bkp';

  (2) modify pfile to convert to db primary content. pFile shows below

  *.audit_file_dest='/opt/Oracle/DB/admin/testdb/adump '

  * .audit_trail = "db".

  * full = '12.1.0.2.0'

  *.control_files='/oradata/testdb/control01.ctl','/orafra/testdb/control02.ctl'

  * .db_block_size = 8192

  * .db_domain = "

  *.db_file_name_convert='/testdb/','/testdb /'

  * .db_name = "testdb".

  * .db_recovery_file_dest ='/ orafra'

  * .db_recovery_file_dest_size = 10737418240

  * .db_unique_name = "testdb".

  *.diagnostic_dest='/opt/Oracle/DB '

  * .fal_server = "stbydb".

  * .log_archive_config = 'dg_config = (testdb, stbydb)'

  * .log_archive_dest_2 = "service = stbydb SYNC valid_for = (ONLINE_LOGFILE, PRIMARY_ROLE) db_unique_name = stbydb'"

  * .log_archive_dest_state_2 = 'ENABLE '.

  *.log_file_name_convert='/testdb/','/testdb /'

  * .memory_target = 1800 m

  * .open_cursors = 300

  * runoff = 300

  * .remote_login_passwordfile = "EXCLUSIVE."

  * .standby_file_management = "AUTO".

  * .undo_tablespace = "UNDOTBS1.

  (3) restart db with updated file pfile

  SQLPLUS > create spfile from pfile='/home/oracle/pfile.txt'

  SQLPLUS > the judgment

  SQLPLUS > startup nomount

  (4) restore controlfile

  RMAN > restore primary controlfile to ' / home/oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.bkp';

  RMAN > change the editing of the database

  (5) all elements of backup catalog

  RMAN > catalog starts by ' / home/oracle/backupset / '.

  (6) restore and recover the database

  RMAN > restore database;

  RMAN > recover database until the SNA XXXXXX; (this YVERT is the maximum in archivelog backups that extends beyond the scn of the backup of the data file)

  (7) open resetlogs

  RMAN > alter database open resetlogs;

  Everything seems perfect, except one of the file log roll forward pending is not generated

  SQL > select * from v$ standby_log;

  ERROR:

  ORA-00308: cannot open archived log ' / oraredo/testdb/stby01.log'

  ORA-27037: unable to get file status

  Linux-x86_64 error: 2: no such file or directory

  Additional information: 3

  no selected line

  I intended to use the same backup to restore primary basic & helps record traffic and the downtime between them in the world of real output.

  So I have exactly the same steps (except STANDBY restore CONTROLFILE and not recover after database restore) to restore the database pending.

  And I got the same missing log file.

  The problem is:

  (1) complete alert.log filled with this error, not the concern here

  (2) now repeat it in real time apply won't work since the Party shall LGWR shows always "WAITING_FOR_LOG."

  (3) I can't delete and re-create this log file

  Then I tried several and found:

  The missing standby logfile was still 'ACTIVE' at present RMAN backup was made.

  For example, on db standby, under Group #4 (stby01.log) would be lost after the restoration.

  SQL > select GROUP #, SEQUENCE #, USE (s), the STATUS from v$ standby_log;

  GROUP # SEQUENCE # USED STATUS

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

  4 19 ACTIVE 133632

  5 0 0 UNASSIGNED

  6 0 0 not ASSIGNED

  7 0 0 UNASSIGNED

  So until I take the backup, I tried on the primary database:

  SQL > alter system set log_archive_dest_state_2 = delay;

  This was the Group of standby_log side Eve #4 was released:

  SQL > select GROUP #, SEQUENCE #, USE (s), the STATUS from v$ standby_log;

  GROUP # SEQUENCE # USED STATUS

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

  4 0 0 UNASSIGNED

  5 0 0 UNASSIGNED

  6 0 0 not ASSIGNED

  7 0 0 UNASSIGNED

  Then, the backup has been restored correctly without missing standby logfile.

  However, to change this primary database means break DataGuard protection when you perform the backup. It's not accept on the production environment.

  Finally, my real questions come:

  (1) what I do may not do on parameter change?

  (2) I know I can re-create the control file to redo before delete and then recreate after. Is there any simple/fast to avoid the standby logfile lost or recreate the lost one?

  I understand that there are a number of ways to circumvent this. Something to keep a copy of the log file waiting restoration progress and copy up one missing, etc, etc...

  And yes I always have done no real-time applies "to the aid of archived logfile" but is also not accept mode of protection of production.

  I just want proof that the design (which is displayed in a few oracle doc Doc ID 602299.1 is one of those) that backs up data backup works effectively and can be used to restore the two site. And it may be without spending more time to resume backups or put the load on the primary database to create the database before.

  Your idea is very much appreciated.

  Thank you!

  Hello

  1--> when I take via RMAN backup, RMAN does not redo log (ORL or SRL) file, so we cannot expect ORLs or SRL would be restored.

  2nd--> when we opened the ORL database should be deleted and created

  3rd--> Expecting, SRL should not be an issue.we should be able to do away with the fall.

  DR sys@cdb01 SQL > select THREAD #, SEQUENCE #, GROUP #, STATUS from v$ standby_log;

  THREAD # SEQUENCE # GROUP # STATUS

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

  1 233 4 ACTIVE

  1 238 5 ACTIVE

  DR sys@cdb01 SQL > select * from v$ logfile;

  GROUP # STATUS TYPE MEMBER IS_ CON_ID

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

  3 /u03/cdb01/cdb01/redo03.log no. 0 online

  /U03/cdb01/cdb01/redo02.log no. 0 2 online

  1 /u03/cdb01/cdb01/redo01.log no. 0 online

  4 /u03/cdb01/cdb01/stdredo01.log WATCH No. 0

  /U03/cdb01/cdb01/stdredo02.log EVE 5 No. 0

  DR sys@cdb01 SQL > ! ls - ltr /u03/cdb01/cdb01/stdredo01.log

  method: cannot access the /u03/cdb01/cdb01/stdredo01.log: no such file or directory

  DR sys@cdb01 SQL >! ls - ltr /u03/cdb01/cdb01/stdredo02.log

  -rw - r-. 1 oracle oinstall 52429312 17 Oct 15:32 /u03/cdb01/cdb01/stdredo02.log

  DR sys@cdb01 SQL > alter database force claire logfile 4;

  change the database group claire logfile 4

  *

  ERROR on line 1:

  ORA-01156: recovery or current flashback may need access to files

  DR sys@cdb01 SQL > alter database recover managed standby database cancel;

  Database altered.

  DR sys@cdb01 SQL > change the database group claire logfile 4;

  Database altered.

  DR sys@cdb01 SQL > ! ls - ltr /u03/cdb01/cdb01/stdredo01.log

  -rw - r-. 1 oracle oinstall 52429312 17 Oct 15:33 /u03/cdb01/cdb01/stdredo01.log

  DR sys@cdb01 SQL >

  If you do, you can recreate the controlfile without waiting for redo log entry...

  If you still think it's something is not acceptable, you must have SR with support to analyze why he does not abandon SRL when controlfile_type is "underway".

  Thank you

• content managed rman backup crushing and selection procedure of the tape media

  Hello Experts.

  I have a question about the backupset rman tape media manage tape of the osb.

  [ENV]

  Exadata rman backup assistance OSB(version: 10.4.0.3.0) SL500 LTO5 4 Tape Drive with rman scripts and full backup is working well.

  1 Appendix backup on OS crontab

  -Each backup full day at 00:00 AM

  2 rman view all:

  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  using the control file of the target instead of recovery catalog database

  RMAN settings for database with db_unique_name TESTDW are:

  CONFIGURE RETENTION POLICY TO 3 DAY RECOVERY WINDOW;

  CONFIGURE BACKUP OPTIMIZATION # by default

  CONFIGURE THE TYPE OF DEFAULT DEVICE TO 'SBT_TAPE ';

  SET UP THE DEVICE TYPE 'SBT_TAPE' PARALLELISM 4 TYPE OF BACKUP BACKUPSET.

  CONFIGURE CONTROLFILE AUTOBACKUP ON;

  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  3 rman backup scirpts

  Run {}

  allocate channels c01 type 'sbt_tape' connect 'sys/manager@testdw1';

  allocate channel c02 type 'sbt_tape' connect 'sys/manager@testdw2';

  allocate channel c03 type 'sbt_tape' connect 'sys/manager@testdw1';

  allocate channels c04 type 'sbt_tape' connect 'sys/manager@testdw2';

  Backup section size 900g database;

  output channel c01;

  output channel c02;

  output channel c03;

  output channel c04;

  }

  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  1st quarter > after several weeks and I run the command as "#obtool u admin Pei welcome1 lsvol-L lib1.

  and are used in many media of rman backup band (about 50EA media, perhaps 46EA are full and 4EA are appendble)

  So, I issue the command 'lsvol - a - c' and could not display expired on all media content.

  Why OSB no has not select and replace the tape media despite the rman rman default retention policy (3days) all show the setting.

  Why OSB does not have the expired status of rman content on tape media?

  -> I need the rman (delete expired, delete obsolete etc...) command to share the summary status of OSB and rman rman?

  Q2 > selection procedure for the tape media all backup rman

  Suppose the total number of tape media is 5EA. (1,2,3,4,5) with an available tape LTO5 drive.

  Status: 1 (full-rman content already expired), 2 (content integral-rman not expired), 3 (editable, remaining space), 4 (new media), 5 (currnet wring media)

  If OSB burn now 5 and reach at the end of the Strip and possibly another media, media to be selected by the OSB?

  Advanced thanks.

  If I place the order obsolete in the rman script as 'delete type 'SBT_TAPE' noprompt obsolete device;' the results will be the same as your

  the syntax because rman default setting (CONFIGURE RETENTION POLICY to RECOVERY WINDOW OF 3 DAYS ;) has already been fixed on the command "Show all", right? @)

  Yes.

  I use the catalog of recovery on a different database and backup script has catalog db connection string.

  And if I only use controlfile instead of recovery catalog to save the backup information and put in place "control_file_record_keep_time" a default of 7 days to 365 days, "remove obsolete" command to remove several weeks backupset works well, is it not?

  Possible problem are existing backups for several weeks if you left default control_file_record_keep_time. Change now will not help unless you catalog later manually all the old pieces not catalogued on tape backup.

  After you clean up the situation and particularly to remove obsolete in your script, rman, you will never make problems with control_file_record_keep_time from this moment. By default will do just fine because it is larger than your window of recovery.

  Kind regards

  Mitja