RAC RAC CLONE OF RMAN cold backup

Similar Questions

• RMAN cold backup pending

  10.2.0.4 RMAN + catalogue + Data Guard
  
  Hi, I'm confused about a few things here :) I was wondering if someone has faced these same issues.
  
  1 documentation states that on making backups in sleep mode, rather than on the primary:
  

  Only the backups that have been written to tape are available to the primary database for restoration and recovery.

  So if I took a backup on the disk and then he went to band (not directly on tape via RMAN), I can't use this backup to restore my first? This is not sensible.
  
  2 oracle recommends to use editable incremental image copy backups as best practices of database pending backup. Someone at - it a link to an explanation of this? Thank you!

  Perhaps you need to specify where you will find in the documentation
  a. that are aligned with the backups, writings on the Strip
  (b) the recommendation to use progressively update backups

  If you have taken a backup of the day before cold and you have restored it on the primary (Note: you must be aware that the backup of the previous day will not have the most recent applied archivelogs!), the restored controlfile is a controlfile "Standby". Then you would have to convert it to a primary
  The sequence would be (similar to that of the primary be "destroyed" - alias 'a disaster')
  RECOVER MANAGED DATABASE ENSURES CANCEL
  ACTIVATE THE BACKUP DATABASE

  (You will not be able to "PASSAGE OF the EVE" that, conceptually, you do not have a PRIMARY.)

  Hemant K Collette
  http://hemantoracledba.blogspot.com

• Try to clone RAC database with RMAN database RAC but becomes lower than ORA-01503

  I'm trying to clone a RAC database of RMAN target database is also CARS, so for every thing wen fine but getting "ORA-01503.

  Please find below, please help me solve this problem.

  connect sys/p0ck3t@pcard1 target;

  auxiliary connection;

  Connect the rmancat/rmanamex@rmandb catalog;

  Run {}

  SQL "alter session set optimizer_mode = RULE ';"

  until ' to_date (' may 1, 2015 06:30 ',' Lun ' DD YYYY HH24:MI:SS);

  allocate auxiliary channel t1 type disk;

  allocate auxiliary channel t2 type disk;

  allocate auxiliary channel t3 type disk;

  the value of newname for datafile 4 to "+ DATA/pcardtst/datafile/users.304.723229675";

  the value of newname for datafile 3 to "+ DATA/pcardtst/datafile/sysaux.395.723228961";

  the value of newname for datafile 2 to "+ DATA/pcardtst/datafile/undotbs1_1.dbf";

  the value of newname for datafile 1 to "+ DATA/pcardtst/datafile/system.328.723229027";

  the value of newname for datafile 5 to "+ DATA/pcardtst/datafile/undotbs2.409.723228957";

  the value of newname for datafile 6 to "+ DATA/pcardtst/datafile/pwrcrd_usr01.dbf";

  the value of newname for datafile 7 to "+ DATA/pcardtst/datafile/pwrcrd_undotbs01.dbf";

  the value of newname for datafile 8 to "+ DATA/pcardtst/datafile/pwrcrd_undotbs02.dbf";

  the value of newname for datafile 9 to "+ DATA/pcardtst/datafile/pwrcrd_data_par01.dbf";

  the value of newname for datafile 10 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_par01.dbf";

  the value of newname for datafile 11 in "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part01_01.dbf";

  the value of newname for datafile 12 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part01_02.dbf";

  the value of newname for datafile 13 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part01_03.dbf";

  the value of newname for datafile 14 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part01_04.dbf";

  the value of newname for datafile 15 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_bo_part01_01.dbf";

  the value of newname for datafile 16 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_bo_part01_02.dbf";

  the value of newname for datafile 17 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part02_01.dbf";

  the value of newname for datafile 18 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part02_02.dbf";

  the value of newname for datafile 19 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part02_03.dbf";

  the value of newname for datafile 20 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part02_04.dbf";

  the value of newname for datafile 21 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_bo_part02_01.dbf";

  the value of newname for datafile 22 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_bo_part02_02.dbf";

  the value of newname for datafile 23 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part03_01.dbf";

  the value of newname for datafile 24 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part03_02.dbf";

  the value of newname for datafile 25 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part03_03.dbf";

  the value of newname for datafile 26 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_bo_part03_01.dbf";

  the value of newname for datafile 27 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_bo_part03_02.dbf";

  the value of newname for datafile 28 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part04_01.dbf";

  the value of newname for datafile 29 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part04_02.dbf";

  the value of newname for datafile 30 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part04_03.dbf";

  the value of newname for datafile 31 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_bo_part04_01.dbf";

  the value of newname for datafile 32 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_bo_part04_02.dbf";

  the value of newname for datafile 33 to '+ DATA/pcardtst/datafile/pwrcrd_data_fe_part01_01.dbf;

  the value of newname for datafile 34 at "+ DATA/pcardtst/datafile/pwrcrd_data_fe_part01_02.dbf";

  the value of newname for datafile 35 to "+ DATA/pcardtst/datafile/pwrcrd_data_fe_part01_03.dbf";

  the value of newname for datafile 36 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_fe_part01_01.dbf";

  the value of newname for datafile 37 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_fe_part01_02.dbf";

  the value of newname for datafile 38 at "+ DATA/pcardtst/datafile/pwrcrd_data_fe_part02_01.dbf";

  the value of newname for datafile 39 to "+ DATA/pcardtst/datafile/pwrcrd_data_fe_part02_02.dbf";

  the value of newname for datafile 40 to "+ DATA/pcardtst/datafile/pwrcrd_data_fe_part02_03.dbf";

  the value of newname for datafile 41 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_fe_part02_01.dbf";

  the value of newname for datafile 42 at "+ DATA/pcardtst/datafile/pwrcrd_ndx_fe_part02_02.dbf";

  the value of newname for datafile 43 at "+ DATA/pcardtst/datafile/pwrcrd_data_fe_part03_01.dbf";

  the value of newname for datafile 44 to "+ DATA/pcardtst/datafile/pwrcrd_data_fe_part03_02.dbf";

  the value of newname for datafile 45 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_fe_part03_01.dbf";

  the value of newname for datafile 46 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_fe_part03_02.dbf";

  the value of newname for datafile 47 to "+ DATA/pcardtst/datafile/pwrcrd_data_fe_part04_01.dbf";

  the value of newname for datafile 48 to "+ DATA/pcardtst/datafile/pwrcrd_data_fe_part04_02.dbf";

  the value of newname for datafile 49 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_fe_part04_01.dbf";

  the value of newname for datafile 50 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_fe_part04_02.dbf";

  the value of newname for datafile 51 to "+ DATA/pcardtst/datafile/pwrcrd_data_batch01.dbf";

  the value of newname for datafile 52 at "+ DATA/pcardtst/datafile/pwrcrd_data_batch02.dbf";

  the value of newname for datafile 53 to '+ DATA/pcardtst/datafile/pwrcrd_data_batch03.dbf;

  the value of newname for datafile 54 to "+ DATA/pcardtst/datafile/pwrcrd_data_batch04.dbf";

  the value of newname for datafile 55 to "+ DATA/pcardtst/datafile/pwrcrd_data_batch05.dbf";

  the value of newname for datafile 56 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_batch01.dbf";

  the value of newname for datafile 57 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_batch02.dbf";

  the value of newname for datafile 58 at "+ DATA/pcardtst/datafile/pwrcrd_ndx_batch03.dbf";

  the value of newname for datafile 59 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part01_01.dbf";

  the value of newname for datafile 60 to "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part01_01.dbf";

  the value of newname for datafile 61 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part02_01.dbf";

  the value of newname for datafile 62 at "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part02_01.dbf";

  the value of newname for datafile 63 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part03_01.dbf";

  the value of newname for datafile 64 at "+ DATA/pcardtst/datafile/pwrcrd_data_index_part03_01.dbf";

  the value of newname for datafile 65 at "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part04_01.dbf";

  the value of newname for datafile 66 to "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part04_01.dbf";

  the value of newname for datafile 67 to '+ DATA/pcardtst/datafile/pwrcrd_data_hist_part05_01.dbf;

  the value of newname for datafile 68 to "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part05_01.dbf";

  the value of newname for datafile 69 at "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part06_01.dbf";

  the value of newname for datafile 70 to "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part06_01.dbf";

  the value of newname for datafile 71 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part07_01.dbf";

  the value of newname for datafile 72 at "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part07_01.dbf";

  the value of newname for datafile 73 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part08_01.dbf";

  the value of newname for datafile 74 at "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part08_01.dbf";

  the value of newname for datafile 75 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part09_01.dbf";

  the value of newname for datafile 76 to '+ DATA/pcardtst/datafile/pwrcrd_index_hist_part09_01.dbf;

  the value of newname for datafile 77 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part10_01.dbf";

  the value of newname for datafile 78 to "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part10_01.dbf";

  the value of newname for datafile 79 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part11_01.dbf";

  the value of newname for datafile 80 to "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part11_01.dbf";

  the value of newname for datafile 81 to '+ DATA/pcardtst/datafile/pwrcrd_data_hist_part12_01.dbf;

  the value of newname for datafile 82 to "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part12_01.dbf";

  the value of newname for datafile 83 at "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part13_01.dbf";

  the value of newname for datafile 84 to "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part13_01.dbf";

  the value of newname for datafile 85 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part14_01.dbf";

  the value of newname for datafile 86 to '+ DATA/pcardtst/datafile/pwrcrd_index_hist_part14_01.dbf;

  the value of newname for datafile 87 to "+ DATA/pcardtst/datafile/powercard_users.375.723228963";

  the value of newname for datafile 88 to "+ DATA/pcardtst/datafile/powercard_users.396.723228959";

  the value of newname for datafile 89 to "+ DATA/pcardtst/datafile/powercard_users.399.723228959";

  the value of newname for datafile 90 to "+ DATA/pcardtst/datafile/powercard_users.393.723228961";

  the value of newname for datafile 91 to '+ DATA/pcardtst/datafile/mig_pc_delivery.309.723228955;

  the value of newname for datafile 92 to "+ DATA/pcardtst/datafile/powercard_index_par.403.723228961";

  the value of newname for datafile 93 to "+ DATA/pcardtst/datafile/powercard_users.381.723228963";

  the value of newname for datafile 94 to "+ DATA/pcardtst/datafile/powercard_index_hist_part01.275.723229411";

  the value of newname for datafile 95 at "+ DATA/pcardtst/datafile/powercard_data_fe_part01.364.723229607";

  the value of newname for datafile 96 to "+ DATA/pcardtst/datafile/powercard_data_hist_part05.380.723228963";

  the value of newname for datafile 97 to '+ DATA/pcardtst/datafile/powercard_data_hist_part10.310.723228959;

  the value of newname for datafile 98 in "+ DATA/pcardtst/datafile/powercard_data_hist_part14.268.723229465";

  the value of newname for datafile 99 to "+ DATA/pcardtst/datafile/powercard_index_hist_part08.367.723229607";

  the value of newname for datafile 100 to "+ DATA/pcardtst/datafile/powercard_index_hist_part09.385.723229087";

  the value of newname for datafile 101 to "+ DATA/pcardtst/datafile/powercard_index_hist_part11.286.723229559";

  the value of newname for datafile 102 to "+ DATA/pcardtst/datafile/powercard_index_hist_part13.355.723229615";

  the value of newname for datafile 103 to "+ DATA/pcardtst/datafile/powercard_data_batch.330.723228961";

  the value of newname for datafile 104 to "+ DATA/pcardtst/datafile/powercard_data_hist_part13.335.723229485";

  the value of newname for datafile 105 to "+ DATA/pcardtst/datafile/powercard_index_bo_part03.285.723229567";

  the value of newname for datafile 106 to "+ DATA/pcardtst/datafile/powercard_index_bo_part01.351.723229617";

  the value of newname for datafile 107 to "+ DATA/pcardtst/datafile/powercard_index_fe_part04.261.723229627";

  the value of newname for datafile 108 to "+ DATA/pcardtst/datafile/powercard_index_hist_part02.264.723229465";

  the value of newname for datafile 109 to "+ DATA/pcardtst/datafile/powercard_data_bo_part01.284.723229573";

  the value of newname for datafile 110 to "+ DATA/pcardtst/datafile/powercard_data_hist_part01.406.723229497";

  the value of newname for datafile 111 to "+ DATA/pcardtst/datafile/powercard_data_hist_part07.291.723229557";

  the value of newname for datafile 112 to "+ DATA/pcardtst/datafile/powercard_data_hist_part08.371.723229615";

  the value of newname for datafile 113 to "+ DATA/pcardtst/datafile/powercard_data_hist_part09.346.723228973";

  the value of newname for datafile 114 to "+ DATA/pcardtst/datafile/powercard_data_hist_part12.401.723229447";

  the value of newname for datafile 115 to "+ DATA/pcardtst/datafile/powercard_index_fe_part02.262.723229625";

  the value of newname for datafile 116 to "+ DATA/pcardtst/datafile/powercard_data_fe_part04.374.723229627";

  the value of newname for datafile 117 to "+ DATA/pcardtst/datafile/powercard_data_bo_part03.276.723229585";

  the value of newname for datafile 118 to "+ DATA/pcardtst/datafile/powercard_data_bo_part04.350.723229633";

  the value of newname for datafile 119 to "+ DATA/pcardtst/datafile/powercard_index_bo_part04.317.723229633";

  the value of newname for datafile 120 to "+ DATA/pcardtst/datafile/powercard_data_hist_part03.400.723229511";

  the value of newname for datafile 121 in '+ DATA/pcardtst/datafile/powercard_index_hist_part12.369.723229605;

  the value of newname for datafile 122 to "+ DATA/pcardtst/datafile/powercard_index_hist_part05.373.723229641";

  the value of newname for datafile 123 to "+ DATA/pcardtst/datafile/powercard_data_par.319.723229635";

  the value of newname for datafile 124 to "+ DATA/pcardtst/datafile/powercard_users.402.723228957";

  the value of newname for datafile 125 to "+ DATA/pcardtst/datafile/powercard_index_batch.356.723229609";

  the value of newname for datafile 126 to "+ DATA/pcardtst/datafile/powercard_index_bo_part02.256.723229647";

  the value of newname for datafile 127 to "+ DATA/pcardtst/datafile/powercard_index_hist_part07.320.723229641";

  the value of newname for datafile 128 to "+ DATA/pcardtst/datafile/powercard_index_hist_part04.258.723229615";

  the value of newname for datafile 129 to "+ DATA/pcardtst/datafile/powercard_data_bo_part02.366.723229651";

  the value of newname for datafile 130 to "+ DATA/pcardtst/datafile/powercard_data_hist_part06.348.723228965";

  the value of newname for datafile 131 to "+ DATA/pcardtst/datafile/powercard_data_hist_part02.307.723229525";

  the value of newname for datafile 132 to "+ DATA/pcardtst/datafile/powercard_index_fe_part01.370.723229647";

  the value of newname for datafile 133 to "+ DATA/pcardtst/datafile/powercard_index_fe_part03.352.723229619";

  the value of newname for datafile 134 to "+ DATA/pcardtst/datafile/powercard_index_hist_part06.266.723229659";

  the value of newname for datafile 135 to "+ DATA/pcardtst/datafile/powercard_index_hist_part10.329.723229027";

  the value of newname for datafile 136 to "+ DATA/pcardtst/datafile/powercard_index_hist_part03.337.723229651";

  the value of newname for datafile 137 to "+ DATA/pcardtst/datafile/powercard_index_hist_part14.263.723229627";

  the value of newname for datafile 138 to "+ DATA/pcardtst/datafile/stpmw_data01.dbf";

  the value of newname for datafile 139 to "+ DATA/pcardtst/datafile/undotbs1_2.dbf";

  the value of newname for datafile 140 to "+ DATA/pcardtst/datafile/undotbs1_3.dbf";

  the value of newname for datafile 141 to "+ DATA/pcardtst/datafile/undotbs1_4.dbf";

  the value of newname for datafile 142 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part05_03.dbf";

  the value of newname for datafile 143 to "+ DATA/pcardtst/datafile/powercard_data_hist_part05.426.851242407";

  the value of newname for datafile 144 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part11_02.dbf";

  the value of newname for datafile 145 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part12_02.dbf";

  the value of newname for datafile 146 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part05_04.dbf";

  the value of newname for datafile 147 in "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part05_02.dbf";

  the value of newname for tempfile 1 to "+ DATA/pcardtst/tempfile/temp1.dbf";

  the value of newname for tempfile 2 to "+ DATA/pcardtst/tempfile/temp2.dbf";

  the value of newname for tempfile 3 to "+ DATA/pcardtst/tempfile/temp3.dbf";

  the value of newname for tempfile 4 to "+ DATA/pcardtst/tempfile/pwrcard_temp01.dbf";

  the value of newname for tempfile 5 to "+ DATA/pcardtst/tempfile/pwrcard_temp02.dbf";

  the value of newname for tempfile 6 to "+ DATA/pcardtst/tempfile/pwrcard_temp03.dbf";

  the value of newname for tempfile 7 to "+ DATA/pcardtst/tempfile/pwrcard_temp04.dbf";

  duplicate target database in the pcardtst log file

  GROUP 10 ('+ DATA/pcardtst/onlinelog/group_10_01') size 512 M,

  GROUP 10 ('+ DATA/pcardtst/onlinelog/group_10_02') size 512 M,

  GROUP 11 ('+ DATA/pcardtst/onlinelog/group_11_01') size 512 M,

  GROUP 11 ('+ DATA/pcardtst/onlinelog/group_11_02') size 512 M,

  GROUP 12 ('+ DATA/pcardtst/onlinelog/group_12_01') size 512 M,

  GROUP 12 ('+ DATA/pcardtst/onlinelog/group_12_02') size 512 M,

  GROUP 13 ('+ DATA/pcardtst/onlinelog/group_13_01') size 512 M,

  GROUP 13 ('+ DATA/pcardtst/onlinelog/group_13_02') size 512 M,

  GROUP 14 ('+ DATA/pcardtst/onlinelog/group_14_01') size 512 M,

  GROUP 14 ('+ DATA/pcardtst/onlinelog/group_14_02') size 512 M,

  GROUP 7 ('+ DATA/pcardtst/onlinelog/group_7_01') size 512 M,

  GROUP 7 ('+ DATA/pcardtst/onlinelog/group_7_02') size 512 M,

  GROUP 8 ('+ DATA/pcardtst/onlinelog/group_8_01') size 512 M,

  GROUP 8 ('+ DATA/pcardtst/onlinelog/group_8_02') size 512 M,

  GROUP 9 ('+ DATA/pcardtst/onlinelog/group_9_01') size 512 M,

  GROUP 9 ('+ DATA/pcardtst/onlinelog/group_9_02') size 512 M;

  output channel t1;

  output channel t2;

  output channel t3;

  }

  But gettting error below

  DATA FILE

  "+ DATA/pcardtst/datafile/system.635.878984933".

  CHARACTER SET WE8ISO8859P1

  output channel: t1

  output channel: t2

  output channel: t3

  RMAN-00571: ===========================================================

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

  RMAN-00571: ===========================================================

  RMAN-03002: failure of Db in dual at 06/05/2015 14:26:01

  RMAN-06136: the auxiliary database ORACLE error: ORA-01503: CREATE CONTROLFILE failed

  ORA-01167: two files are the same file/group number or the same file

  ORA-01517: Member of journal: '+ DATA/pcardtst/onlinelog/group_10_02.

  ORA-01517: Member of journal: '+ DATA/pcardtst/onlinelog/group_10_01.

  Complete recovery manager.

  Kind regards.

  Younus

  Hi Eric,.

  Let's not your syntax for log files. Check out the docs:

  http://docs.Oracle.com/CD/B28359_01/backup.111/b28270/rcmdupdb.htm#BRADV89956

  You need only name the Group once followed a list separated by commas of the logfile members.

  Concerning

  Thomas

• Cold backup RMAN

  Basically I ask this question for a problem surrounding in another thread, but here go us:

  Suppose we take a COLD backup. I know, not something directly related with RMAN, but further action is:

  This guy says: I take a backup to cold, I copy the files to another server, on which he has made the necessary in order to start this database.

  But then, since the backup and the time of the action above, time is up.

  So, there are archived redologs... because the database is in archivelog mode.

  And he wants to do what is obvious: use these Redos archived, to update the database at a later stage in time.

  To be clear; the Oder archived are created by the source database. The target database has been copied and started, nothing else.

  If the backup is a backup hot, without issue. But because the backup is cold, it is not possible, right?

  My idea is that he must also take a hot backup, in addition.

  I asked already, and despite the execution of the database in archivelog mode, the backup must be taken cold, backup mode for some reason. It is probably the old method, who they now want to just add redolog recovery, but without change from cold to hot.

  At some point, RMAN must be running, of course.

  I guess that RMAN is used for the entire operation, not "at some point" (I see no reason not to).

  The cold food at the start is to make a clone. THEN, the question is asked, but can we also restore to a point more recent in time?

  Yes, you can recover the "clone" until a more recent point in time as long as you do not OPEN it, and you have all necessary archivelogs. The sequence:

  1 startup nomount

  2 restore controlfile

  3. change the editing of the database

  4 restore your cold backup (do not open the database)

  5. If necessary, catalogue archivelog backups

  6 back to the desired point in time

  7. alter database open resetlogs.

  But I repeat, why did you stop your databases, if that is not necessary? (of course I think of my dozens of databases 24 x 7).

• Re: is the cold backup of rman includes onlinde redologs?

  Hello
  
  cold backup of rman includes onlinde redologs?
  
  So that at the time of the recovery when I restore the database the redologs online also restored at this point?
  
  Please, please add your suggestions. I read in 10g database in condition to mount everything taking the backup RMAN as cold as the oracle process overall are down we cannot copy the redologs online.
  Am I correct, otherwise please someone answer me why the redologs online are not copied.
  
  Thanks in advance
  SAI

  A cold backup (i.e., MOUNT but not given) to RMAN does not backup online redo logs.

  If you restore this backup you will need OPEN RESETLOGS to recreate the online redo logs to the target.

  Hemant K Collette

  PS: Oracle Documentation prefers to call an RMAN backup backs "Cohérent" when the database is mounted but the State is not OPEN. "Cold Backup" is today used for the non-RMAN methods.

  Published by: Hemant K Collette on 8 January 2013 11:47
  Added PS

• cold backup of rman includes onlinde redologs?

  Hello
  
  cold backup of rman includes onlinde redologs?
  
  So that at the time of the recovery when I restore the database the redologs online also restored at this point?
  
  I reason,.
  
  Thanks to advanced
  Sairanga

  RMAN never backup online redo logs.

  If you ever need to restore a database that had been saved cold with rman, you'd end up working with an alter database open resetlogs, which will create newspapers online brand new, empty.

• Cold backup RMAN script

  DB version: 10.2.0.4
  
  Can't you find something wrong in the below mentioned the cold backup RMAN script? Improvements, corrections?
  

  {
  shutdown immediate;
  startup mount;
  backup database including current controlfile tag='full_bkp';
  startup;
  crosscheck backup;
  delete noprompt obsolete device type disk;
  resync catalog;
  }

  Should work, but you can include more 'archivelog' in the backup statement in the case where your database is running in archivelog mode. It's also a good idea to make a backup of the trace of the controlfile using "sql" controlfile alter backup database to TRACE";"

• Unable to cold backup with rman

  Dear all
  I am trying to perform cold backup with rman and my script follows
  
  
  Run {}
  stop immediately;
  bootable media;
  allocate channel dup1 device type disk;
  allocate channel dup2 device type disk;
  backup format ' / home/oracle/ORACLEBACKUP/%U' database;
  output channel dup1;
  output channel dup2;
  ALTER database open;
  }
  When I run this script in rman it shows errord
  
  
  database closed
  dismounted database
  Instance Oracle to close
  
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the boot command at 14/01/2011 14:31:30
  ORA-12514: TNS:listener is not currently of service requested in connect descriptor
  
  RMAN >
  There is no error in my script or other
  
  Thanks in advance
  
  Shaikh Abdul Anthony

  You connect through an earpiece.
  The listener becomes aware of the database when you turn it off.

  You run RMAN from the same server as the database? You need not connect through an earpiece.

  Hemant K Collette

• Problem with the archive log when you use RMAN for backup and restore (11g 2)

  Hello world
  Please help me solve this problem.
  I'm just beginner in Oracle Database (11 g 2). Today, I had a problem, I tried to back up and restore my db by RMAN. I delete all the files in /u01/app/oracle/oradata/orcl / * , then I restore them easily, but the point is I have a table, I can restore Hungarian, but cannot restore anything ranks in it (something wrong with step restore database). I'll tell the detail below.
  -First, I create a 'Day' with command table create table hr.day (varchar (20)) day. Then I backup complete by this:
  run{
allocate channel bkp device type DISK FORMAT '/u01/backup/DB_FULL_%d_%T_s%s_p%p' ;
backup as compressed backupset incremental level 0 tag 'DB_FULL' database include current controlfile;
backup as compressed backupset tag 'ARCL_BKP_FULL' archivelog all delete input;
crosscheck archivelog all;
crosscheck backup;
delete noprompt obsolete;
release channel bkp;
}
  

  
  D ' other hand, I have insert 'Monday' to table. then do an incremental backup by this:

  run{
allocate channel bkp device type DISK FORMAT '/u01/backup/DB_INC_%d_%T_s%s_p%p' ;
backup as compressed backupset incremental level 1 tag 'DB_INC' database include current controlfile;
backup as compressed backupset tag 'ARCL_BKP_INC' archivelog all delete input;
crosscheck archivelog all;
crosscheck backup;
delete noprompt obsolete;
release channel bkp;
}

  Repeat 7 times (Monday-> Saturday). And I got these files:

  [oracle@rac ~]$ ls -l /u01/backup/
total 400280
-rw-r----- 1 oracle oinstall  10158080 Jan 20 07:23 c-1428943247-20160120-01
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:04 c-1428943247-20160120-02
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:05 c-1428943247-20160120-03
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:06 c-1428943247-20160120-04
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:08 c-1428943247-20160120-05
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:08 c-1428943247-20160120-06
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:09 c-1428943247-20160120-07
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:32 c-1428943247-20160120-08
-rw-r----- 1 oracle oinstall 296337408 Jan 20 07:23 DB_FULL_ORCL_20160120_s89_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 07:23 DB_FULL_ORCL_20160120_s90_p1
-rw-r----- 1 oracle oinstall   2266624 Jan 20 07:23 DB_FULL_ORCL_20160120_s91_p1
-rw-r----- 1 oracle oinstall   4073984 Jan 20 07:23 DB_FULL_ORCL_20160120_s92_p1
-rw-r----- 1 oracle oinstall  11201536 Jan 20 07:23 DB_FULL_ORCL_20160120_s93_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:05 DB_INC_ORCL_20160120_s100_p1
-rw-r----- 1 oracle oinstall    146944 Jan 20 08:05 DB_INC_ORCL_20160120_s101_p1
-rw-r----- 1 oracle oinstall    884736 Jan 20 08:06 DB_INC_ORCL_20160120_s103_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:06 DB_INC_ORCL_20160120_s104_p1
-rw-r----- 1 oracle oinstall     82432 Jan 20 08:06 DB_INC_ORCL_20160120_s105_p1
-rw-r----- 1 oracle oinstall    294912 Jan 20 08:07 DB_INC_ORCL_20160120_s107_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:07 DB_INC_ORCL_20160120_s108_p1
-rw-r----- 1 oracle oinstall     18944 Jan 20 08:08 DB_INC_ORCL_20160120_s109_p1
-rw-r----- 1 oracle oinstall    155648 Jan 20 08:08 DB_INC_ORCL_20160120_s111_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:08 DB_INC_ORCL_20160120_s112_p1
-rw-r----- 1 oracle oinstall    131584 Jan 20 08:08 DB_INC_ORCL_20160120_s113_p1
-rw-r----- 1 oracle oinstall    647168 Jan 20 08:09 DB_INC_ORCL_20160120_s115_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:09 DB_INC_ORCL_20160120_s116_p1
-rw-r----- 1 oracle oinstall      8704 Jan 20 08:09 DB_INC_ORCL_20160120_s117_p1
-rw-r----- 1 oracle oinstall   2203648 Jan 20 08:04 DB_INC_ORCL_20160120_s95_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:04 DB_INC_ORCL_20160120_s96_p1
-rw-r----- 1 oracle oinstall   1899008 Jan 20 08:04 DB_INC_ORCL_20160120_s97_p1
-rw-r----- 1 oracle oinstall    327680 Jan 20 08:05 DB_INC_ORCL_20160120_s99_p1


  And
  RMAN> list backup summary;
List of Backups
===============
Key     TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
------- -- -- - ----------- --------------- ------- ------- ---------- ---
80      B  0  A DISK        20-JAN-16       1       1       YES        DB_FULL
81      B  0  A DISK        20-JAN-16       1       1       YES        DB_FULL
82      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL
83      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL
84      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL
85      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T072332
86      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
87      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
88      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
89      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080440
90      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
91      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
92      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
93      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080545
94      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
95      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
96      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
97      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080657
98      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
99      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
100     B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
101     B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080801
102     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
103     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
104     B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
105     B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080844
106     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
107     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
108     B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC

  My configuration of rman:
  RMAN> show all;
RMAN configuration parameters for database with db_unique_name ORCL are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u01/backup/%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   '/u01/backup/backup_df%t_s%s_s%p';
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 LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome/dbs/snapcf_orcl.f'; # default

  - Thirdly, i removed all file in /u01/app/oracle/oradata/orcl/*. then restore control file from the newest backup control file (saturday backup) + restore database. Seem nothing's wrong here.
RMAN> restore controlfile from '/u01/backup/c-1428943247-20160120-08';
Starting restore at 20-JAN-16
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=18 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=20 device type=DISK
channel ORA_DISK_2: skipped, AUTOBACKUP already found
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:09
output file name=/u01/app/oracle/oradata/orcl/control01.ctl
output file name=/u01/app/oracle/flash_recovery_area/orcl/control02.ctl
Finished restore at 20-JAN-16

RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
released channel: ORA_DISK_2

RMAN> restore database;
Starting restore at 20-JAN-16
Starting implicit crosscheck backup at 20-JAN-16
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=20 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=18 device type=DISK
Crosschecked 29 objects
Finished implicit crosscheck backup at 20-JAN-16

Starting implicit crosscheck copy at 20-JAN-16
using channel ORA_DISK_1
using channel ORA_DISK_2
Finished implicit crosscheck copy at 20-JAN-16

searching for all files in the recovery area
cataloging files...
no files cataloged

using channel ORA_DISK_1
using channel ORA_DISK_2

channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to /u01/app/oracle/oradata/orcl/system01.dbf
channel ORA_DISK_1: restoring datafile 00002 to /u01/app/oracle/oradata/orcl/sysaux01.dbf
channel ORA_DISK_1: restoring datafile 00003 to /u01/app/oracle/oradata/orcl/undotbs01.dbf
channel ORA_DISK_1: restoring datafile 00004 to /u01/app/oracle/oradata/orcl/users01.dbf
channel ORA_DISK_1: restoring datafile 00005 to /u01/app/oracle/oradata/orcl/example01.dbf
channel ORA_DISK_1: reading from backup piece /u01/backup/DB_FULL_ORCL_20160120_s89_p1
channel ORA_DISK_1: piece handle=/u01/backup/DB_FULL_ORCL_20160120_s89_p1 tag=DB_FULL
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:15
Finished restore at 20-JAN-16


  -Fourth, the problem here, I got the database;
.. .every oky until this line...
starting media recovery

channel ORA_DISK_1: starting archived log restore to default destination
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=15
channel ORA_DISK_1: reading from backup piece /u01/backup/DB_INC_ORCL_20160120_s117_p1
channel ORA_DISK_1: piece handle=/u01/backup/DB_INC_ORCL_20160120_s117_p1 tag=ARCL_BKP_INC
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
archived log file name=/u01/app/oracle/flash_recovery_area/ORCL/archivelog/2016_01_20/o1_mf_1_15_c9xsyx9k_.arc thread=1 sequence=15
unable to find archived log
archived log thread=1 sequence=1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 01/20/2016 08:50:22
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 1 and starting SCN of 1205841

The error said that it is impossible to find the archived log thread = 1 sequence = 1. Then I check it with this command always there (oh, I'm wrong?)
RMAN> list backup of archivelog all;
List of Backup Sets
===================
BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
82      2.16M      DISK        00:00:00     20-JAN-16     
        BP Key: 82   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_FULL
        Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s91_p1

  List of Archived Logs in backup set 82
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
1    1       1154833    20-JAN-16 1177422    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
83      3.88M      DISK        00:00:00     20-JAN-16     
        BP Key: 83   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_FULL
        Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s92_p1

  List of Archived Logs in backup set 83
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
1    1       1162729    20-JAN-16 1188784    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
84      10.68M     DISK        00:00:01     20-JAN-16     
        BP Key: 84   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_FULL
        Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s93_p1

  List of Archived Logs in backup set 84
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    2       1177422    20-JAN-16 1201833    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
88      1.81M      DISK        00:00:01     20-JAN-16     
        BP Key: 88   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s97_p1

  List of Archived Logs in backup set 88
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    3       1201833    20-JAN-16 1204844    20-JAN-16
  1    4       1204844    20-JAN-16 1204893    20-JAN-16
  1    5       1204893    20-JAN-16 1204958    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
92      143.00K    DISK        00:00:00     20-JAN-16     
        BP Key: 92   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s101_p1

  List of Archived Logs in backup set 92
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    6       1204958    20-JAN-16 1205034    20-JAN-16
  1    7       1205034    20-JAN-16 1205253    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
96      80.00K     DISK        00:00:00     20-JAN-16     
        BP Key: 96   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s105_p1

  List of Archived Logs in backup set 96
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    8       1205253    20-JAN-16 1205354    20-JAN-16
  1    9       1205354    20-JAN-16 1205433    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
100     18.00K     DISK        00:00:00     20-JAN-16     
        BP Key: 100   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s109_p1

  List of Archived Logs in backup set 100
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    10      1205433    20-JAN-16 1205519    20-JAN-16
  1    11      1205519    20-JAN-16 1205559    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
104     128.00K    DISK        00:00:00     20-JAN-16     
        BP Key: 104   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s113_p1

  List of Archived Logs in backup set 104
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    12      1205559    20-JAN-16 1205624    20-JAN-16
  1    13      1205624    20-JAN-16 1205739    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
108     8.00K      DISK        00:00:00     20-JAN-16     
        BP Key: 108   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s117_p1

  List of Archived Logs in backup set 108
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    14      1205739    20-JAN-16 1205796    20-JAN-16
  1    15      1205796    20-JAN-16 1205840    20-JAN-16

  
If i ignore it and open the database, just my table in full backup come back but rows was not restored. I'm sure the problem is my archive log backup but i don't know how to solve it. Plz help me.

  Sorry for a long post.


  > 1 and from the 1205841 SNA sequence

  The SCN that indicates Oracle is above the range of SNA that you have in the ArchiveLog backups for sequence 1 to 15 (15 sequence ends at 1205840).

  The message

  channel ORA_DISK_1: restoring archives Journal

  Archives journal thread = 1 sequence = 15

  channel ORA_DISK_1: backup/u01/backup/DB_INC_ORCL_20160120_s117_p1 piece reading

  channel ORA_DISK_1: piece handle = / u01/backup/DB_INC_ORCL_20160120_s117_p1 tag = ARCL_BKP_INC

  indicates that he has restored the sequence up to 15

  You can check the log file alert database instance for messages on the fact of recovery.

  He is now asking sequence #1 it seems you did a RESETLOGS after sequence #15.

  Note: If you have NOT issued a COMMIT after the line is INSERTED in the table 'Day', the recovery of the database will have no * transactions * to retrieve.  An uncomitted transaction is cancelled.

  Hemant K Collette

• Cold backup of database primary affect DR sync

  Hello
  
  We have some 10gr 2 DR of installation,
  
  We are planning for the cold primary database backup on every Sunday.
  
  It's going to affect DR sync if the primary database is not available at the time of the cold backup.
  
  Thank you

  No Impact

  Check
  Cold RMAN copy backup of database primary Data Guard

• Should we backup Archivelogs special cold backups?

  B version: 11.2
  Version of the operating system: Solaris 5.10
  
  Here's the script that we use for ad-hoc cold backups. Is it necessary to take the backup of the archivelogs when we do the backup to cold?
  Size of the backup archivelog room is sometimes greater than the backup piece containing the full backup of the comic itself! Then lost too much disk space.
  
  The script that we use

  run
  {
  allocate channel t1 type disk;
  sql 'alter system archive log current';
  shutdown immediate;
  startup mount;
  backup  full database format='/mypath/ORCL_full_%U_%T.bkp' tag='ORCL_full';
  backup archivelog all tag='arch_bkp' format='/mypath/ORCL_BKP/arch_%U_%T.bkp' delete input;
  release channel t1;
  }

  Hello;

  A cold backup is a consistent state. If you do not have to save them. No new archived logs generated during the backup or if you're still OK.

  For other types of RMAN backup, you STILL want it. This ensures that backups of data taken when the command file is recoverable in a consistent state.

  Best regards

  mseberg

• Pre-upgrade cold backup

  DB version: 10.2.0.5
  Version of the operating system: Solaris
  
  We will upgrade of databases about 50 10.2.0.5 to 11.2.0.1
  
  Pre-staged at cold backup of the DBs 10.2.0.5 level, should use us regular cp command, OR should use us RMAN to take the backup to cold? What would you do?

  Hello

  We will upgrade of databases about 50 10.2.0.5 to 11.2.0.1

  Why not 11.2.0.2. The 11.2.0.2 version is more stable and much less bugs.

  Pre-staged at cold backup of the DBs 10.2.0.5 level, should use us regular cp command, OR should use us RMAN to take the backup to cold? What would you do?

  I do not recommend using cp because you cannot verify the integrity of the database and backup. RMAN is infinitely more advanced and have more resources than cp command.

  So I recommend...

  (1) conduct Validade database before backup. To check the integrity of the database
  (2) backup using RMAN 10.2.
  (3) update Perfom 11.2
  (4) to validate the database
  (5) backup database using RMAN 11.2 Perfom.

  We can ask why run the validation database... I recently upgraded from version 10.2.0.5 for 11.2.0.2 23 databases and some databases have been corrupted logical blocks after the upgrade.
  Just do the job safely and make sure that everything is ok

  Kind regards
  Levi Pereira

• RMAN information - backup of the operating system

  Hello
  I took a manual backup of a data file by using operating systems. How RMAN know about this?
  
  Thank you
  Mason.

  As Aman has mentioned, you must use the command CATALOGUE make RMAN know
  Suppose you took cold backup of the file users01.dbf data and you want to catalog them in the RMAN recovery catalog. See the example below:

  RMAN> catalog datafilecopy 'c:\users01.dbf';
  
  using target database control file instead of recovery catalog
  cataloged datafile copy
  datafile copy filename=C:\USERS01.DBF recid=1 stamp=695238977
  
  RMAN> list copy;
  
  using target database control file instead of recovery catalog
  specification does not match any archive log in the recovery catalog
  
  List of Datafile Copies
  Key     File S Completion Time Ckp SCN    Ckp Time        Name
  ------- ---- - --------------- ---------- --------------- ----
  1       4    A 18-AUG-09       546902     18-AUG-09       C:\USERS01.DBF
  
  RMAN>
  

• cold backup can use archivelog to recover the database to the point of failure?

  Hello
  
  I have little doubts. In any DB saying we have following conditions:
  
  (1) DB is running in ARCHIVELOG mode.
  (2) cold backup is performed every Sunday.
  (3) no backups hot or the RMAN backup is taken.
  
  so if any failure occurs during the week say Friday. can recover us our database to the point of failure with cold backup? If yes then pls specify the steps how to do it.
  
  Archiving log could apply on cold backup?
  
  
  Thank you
  Shailesh

  Yes. Just make sure that you use "with the HELP of BACKUP CONTROLFILE' so that Oracle ignores the sequence numbers and the SNA in the controlfile and guard"rolling-forward"until the last archivelog that provide you.
  If you have not lost all over again the logs files and want a complete recovery, you must provide log redo file names "as if they have been archived" after applying the last archivelog. This way, you will be able to achieve a complete recovery.
  Of course, you will need to OPEN RESETLOGS.

• RMAN bypass backup can be taken from question?

  Hi all

  pretty simple question (I hope that ):

  I use the suite at the moment for example:

  run
  {
  Backup CONFIGURATION DEVICE TYPE DISK PARALLELISM 2 to compressed backupset;
  TIME 01:00 PARTIAL minimize THE time data BACKUP FILESPERSET 1;
  }

  But I was wondering if there is some way to this running as a backup script planned to restart backup, if it does not (due to problems of space file etc.)

  run
  {

  Configure the disk channel CH1 device type format ' / alternate/path/for_backup/%d_DB_%M%D%Y_%p_%s_%U';
  Configure the disk channel CH2 device type format ' / alternate/path/for_backup/%d_DB_%M%D%Y_%p_%s_%U';

  
  TIME 01:00 PARTIAL minimize THE time of BACKUP data NOT BACKED UP SINCE TIME ' SYSDATE - 1' fileperset 1;    < < < I know it won't work like that but y at - it another way to accomplish this? (work around to restart the backup time and the option to reduce time?)
  

  
  

  cleaning etc release channels

  }

  PS: question side bonus points

  who can tell me more about the loss of speed MB/S compared to the rate of compression: low/medium/high?

  I hope that there are some brilliant minds out there willing to help!

  Thanks in advance.

  
  
  

  The themes you mention seem to be covered in the Advanced documentation of RMAN:

  http://docs.Oracle.com/CD/E11882_01/backup.112/e10642/rcmbckad.htm#BRADV89540

  I don't know if anyone can really give you an opinion about which compression will have the best size vs time full report. But the next test by using a simple vanilla ORCL database shows the result of the compression of 'low '. It was done on sub Oracle 11 GR 2 one running a VirtualBox VM. As you can see there is a reduction of the large size of the backupset, which however has taken so long to complete as to the 'no' compression.

  RMAN> CONFIGURE COMPRESSION ALGORITHM clear;
  
  RMAN> backup database;
  RMAN> list backup;
  
  BS Key  Type LV Size       Device Type Elapsed Time Completion Time
  ------- ---- -- ---------- ----------- ------------ ---------------
  40      Full    1.20G      DISK        00:00:08     22-JUN-15
          BP Key: 40   Status: AVAILABLE  Compressed: NO  Tag: TAG20150622T123329
  
  RMAN> CONFIGURE COMPRESSION ALGORITHM 'LOW';
  RMAN> backup as compressed backupset database;
  RMAN> list backup;
  
  BS Key  Type LV Size       Device Type Elapsed Time Completion Time
  ------- ---- -- ---------- ----------- ------------ ---------------
  44      Full    400.38M    DISK        00:00:08     22-JUN-15
          BP Key: 44   Status: AVAILABLE  Compressed: YES  Tag: TAG20150622T123811
  

  Why did you write that I know that it won't work like that? According to the example below, I don't see the problem. As you can see on the 2nd run of the backup command, it ignores the data files that he has previously treated.

  RMAN> BACKUP DURATION 1:00 PARTIAL MINIMIZE TIME database NOT BACKED UP SINCE TIME 'SYSDATE -1' FILESPERSET 1;
  
  Starting backup at 22-JUN-15
  using channel ORA_DISK_1
  channel ORA_DISK_1: starting full datafile backup set
  channel ORA_DISK_1: specifying datafile(s) in backup set
  input datafile file number=00001 name=+DATA/orcl1/datafile/system.256.862871041
  channel ORA_DISK_1: starting piece 1 at 22-JUN-15
  channel ORA_DISK_1: finished piece 1 at 22-JUN-15
  piece handle=+DATA/orcl1/backupset/2015_06_22/nnndf0_tag20150622t121929_0.283.883052369 tag=TAG20150622T121929 comment=NONE
  channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
  channel ORA_DISK_1: starting full datafile backup set
  channel ORA_DISK_1: specifying datafile(s) in backup set
  input datafile file number=00005 name=+DATA/orcl1/datafile/example.269.862871121
  channel ORA_DISK_1: starting piece 1 at 22-JUN-15
  channel ORA_DISK_1: finished piece 1 at 22-JUN-15
  piece handle=+DATA/orcl1/backupset/2015_06_22/nnndf0_tag20150622t121929_0.275.883052373 tag=TAG20150622T121929 comment=NONE
  ...etc...
  
  RMAN> delete backupset 29,30,34;
  
  RMAN> BACKUP DURATION 1:00 PARTIAL MINIMIZE TIME database NOT BACKED UP SINCE TIME 'SYSDATE -1' FILESPERSET 1;
  
  Starting backup at 22-JUN-15
  using channel ORA_DISK_1
  skipping datafile 2; already backed up on 22-JUN-15
  skipping datafile 3; already backed up on 22-JUN-15
  skipping datafile 4; already backed up on 22-JUN-15
  channel ORA_DISK_1: starting full datafile backup set
  channel ORA_DISK_1: specifying datafile(s) in backup set
  input datafile file number=00001 name=+DATA/orcl1/datafile/system.256.862871041
  channel ORA_DISK_1: starting piece 1 at 22-JUN-15
  channel ORA_DISK_1: finished piece 1 at 22-JUN-15
  piece handle=+DATA/orcl1/backupset/2015_06_22/nnndf0_tag20150622t122021_0.308.883052421 tag=TAG20150622T122021 comment=NONE
  ...etc...