Why RMAN backup tablespace UNDO?

Similar Questions

• RMAN throwing errors during backup Tablespace - RMAN-06004 and RMAN-06019

  Hi all.
  
  
  Please, help me difficulty trail of the error message I get when trying to backup to a tablespace that is newly added in the database. I'm with RMAN as a method of recovery.
  
  Tablespace name: test
  Version of DB: Oracle 10g R1.
  OS: Red Hat Linux 5
  
  
  
  
  RMAN > outline report;
  
  Report of the database schema
  
  List of permanent data files
  ===========================
  Size (MB) Tablespace RB segs Datafile file name
  ---- -------- -------------------- ------- ------------------------
  1 490 SYSTEM YES /u01/app/oracle/oradata/qrcl/system01.dbf
  2 25 UNDOTBS1 /u01/app/oracle/oradata/qrcl/undotbs01.dbf YES
  SYSAUX 3 270 NO /u01/app/oracle/oradata/qrcl/sysaux01.dbf
  4 23 USERS NO /u01/app/oracle/oradata/qrcl/users01.dbf
  5 40 TEST NO /u01/app/test01.dbf
  
  List of temporary files
  =======================
  File Size (MB) (MB) Maxsize Tempfile Tablespace name
  ---- -------- -------------------- ----------- --------------------
  1 20 TEMP /u01/app/oracle/oradata/qrcl/temp01.dbf 32767
  
  RMAN >
  
  
  
  
  
  RMAN > backup tablespace 'test '.
  
  From 22 August 12 backup
  using channel ORA_DISK_1
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the backup command to 22/08/2012 11:57:13
  RMAN-06004: error ORACLE recovery catalog database: RMAN-20202: tablespace not found in the recovery catalog
  RMAN-06019: could not translate tablespace name 'test '.
  
  RMAN > restore tablespace test;
  
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-00558: error occurred during parsing of order entry
  RMAN-01009: syntax error: found 'test': expected an a: 'double-quoted-string, identifier, single-quoted-string '.
  RMAN-01007: in the file column 20 line 1: entry standard
  
  
  
  I tried to update the catalog server but still no luck:
  
  RMAN > RESYNC CATALOG;
  
  from full resynchronization of the recovery catalog
  full complete Resync
  
  
  Please help.
  
  
  
  
  Thank you
  Prashant Dixit

  Prashant;

  I took the time to demonstrate using a tablespace that was NOT a reserved word in the hope that you would see how bad idea using a reserved word is.

  A tablespace is a logical structure and it can be almost any other name.

  Why create this problem yourself when there are simple alternatives?

  Time is the most precious thing in my life and I don't know that it's in yours also.

  Please consider using another name of the tablespace.

  ALTER TABLESPACE TEST RENAME OTEST;

  There is no sense, make things more complex, then they already are.

  If this is really not an option then:

  RMAN> backup tablespace "TEST";
  
  Starting backup at 22-AUG-12
  starting full resync of recovery catalog
  full resync complete
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: SID=88 device type=DISK
  channel ORA_DISK_1: starting full datafile backup set
  channel ORA_DISK_1: specifying datafile(s) in backup set
  input datafile file number=00008 name=/u01/oradata/RECOVER2/test05.dbf
  channel ORA_DISK_1: starting piece 1 at 22-AUG-12
  channel ORA_DISK_1: finished piece 1 at 22-AUG-12
  piece handle=/u01/app/oracle/flash_recovery_area/RECOVER2/backupset/2012_08_22/o1_mf_nnndf_TAG20120822T152734_83bj5pt3_.bkp tag=TAG20120822T152734 comment=NONE
  channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
  Finished backup at 22-AUG-12
  
  Starting Control File and SPFILE Autobackup at 22-AUG-12
  piece handle=/u01/app/oracle/flash_recovery_area/RECOVER2/autobackup/2012_08_22/o1_mf_s_791998056_83bj5rpq_.bkp comment=NONE
  Finished Control File and SPFILE Autobackup at 22-AUG-12
  

  Best regards

  mseberg

  Published by: mseberg on August 22, 2012 15:27

• RMAN backup especially for tablespaces

  Hi@everybody,

  We have an Oracle 11 g 2 (11.2.0.3.0) server, based on RedHat 6, installed in our company. For backups I use with an RMAN script. In this script, copy the following code specifically creates the backup:

          run {
              allocate channel oem_backup_disk1 type disk;
              backup incremental level ${level} cumulative as COMPRESSED BACKUPSET tag '${tag}' database;
              backup as COMPRESSED BACKUPSET tag '${tag}' archivelog all not backed up;
              release channel oem_backup_disk1;
          }
  
  

  ${level} is 0 or 1, full or incremental backup. ${tag} is the name of the backup. This script is the database of the hole. But now I want to change this script at the tablespace level. We have some 'test' tablespaces, where a backup is not necessary. I just found this one:

  backup tablespace TEST tag='BACKUP_TEST';
  

  But now I'm not shure how I can implement which in my script.

  Can you guys help me?

  Thank you and best regards,

  David

  Hello

  You can exclude certain tablespaces from the database as below

  Example of CONFIGURATION EXCLUDE for the TABLESPACE;

  You can use the normal backup script.

  http://docs.Oracle.com/CD/B13789_01/server.101/B10734/rcmconfg.htm

  Hope that helps,

  SAM L.

• Can I plug in (food) a tablespace, RMAN backup in another DB?

  11.2.0.3/AIX 6.1
  
  We accidentally dropped a DB development without taking the last backup expdp of a basic scheme. All objects on this schema belong to the single tablespace and we have this tablespace RMAN backup. Is there anyway we could recreate this pattern by restoring the backup tablespace in a different database?

  Yes.

  Use the function/method of TRANSPORT TABLESPACE:

  http://Oracle.Su/docs/11g/backup.112/e10643/rcmsynta2021.htm

  See also sys.dbms_tts.transport_set_check

  RMAN> transport tablespace emp_data, emp_data2
             tablespace destination '/u01/app/oracle/oradata'
             auxiliary destination '/u04/app/oracle/oradata';
  

  If you need to check your endian use this query format:

  SELECT
    PLATFORM_NAME,
    ENDIAN_FORMAT
  FROM
    V$TRANSPORTABLE_PLATFORM;
  

  http://www.Fadalti.com/Oracle/database/how_to_transportable_tablespaces.htm

  http://husnusensoy.WordPress.com/2008/07/12/migrating-data-using-transportable-tablespacetts/

  Best regards

  mseberg

• Why is backup RMAN 2 TB DB still 2 TB when expdp dump was only 600 MB?

  RDBMS version: 11.2.0.3/Oracle Linux 6.2

  We took a RMAN of below mentioned DB Backup.

  
  Since DBA_SEGMENTS showed 2 TB, I thought that RMAN backup size will be half of this IE. 1 TB. But the size of the RMAN backups was 1.95 TB!

  expdp full DB was only 600 MB!

  SQL > select sum (bytes/power (1024,3)) of dba_segments;

  SUM (BYTES/POWER (1024,3))
  ------------------------
  2056.27728

  SQL > select sum (bytes/power (1024,3)) sumbytesGB, sum (maxbytes/power (1024,3)) sumMaxBytes of dba_data_files;

  SUMBYTESGB SUMMAXBYTES
  ---------- -----------
  5451 427.998978

  
  SQL > col file_name format a75
  SQL > set 300 pages
  SQL > select file_name, bytes/power (1024,3) bytesGB, maxbytes/power (1024,3) from dba_data_files;

  FILE_NAME BYTESGB MAXBYTES/POWER (1024,3)
  --------------------------------------------------------------------------- ---------- ----------------------
  +CMS_DATA/bcmsprd/datafile/cms_s_asset_xa_dat_01.dbf 20 0
  +CMS_DATA/bcmsprd/datafile/cms_s_asset_xa_dat_02.dbf 20 0
  +CMS_DATA/bcmsprd/datafile/cms_s_asset_xa_dat_03.dbf 20 0
  +CMS_DATA/bcmsprd/datafile/cms_s_asset_xa_dat_04.dbf 20 0
  +CMS_DATA/bcmsprd/datafile/cms_s_asset_xa_dat_05.dbf 20 0
  +CMS_DATA/bcmsprd/datafile/cms_s_asset_xa_dat_06.dbf 20 0
  +CMS_DATA/bcmsprd/datafile/cms_s_asset_xa_dat_07.dbf 20 0
  +CMS_DATA/bcmsprd/datafile/cms_s_asset_xa_dat_08.dbf 20 0
  +CMS_DATA/bcmsprd/datafile/users.271.803502221 6 31.9999847
  20 20 +CMS_DATA/bcmsprd/datafile/undotbs1.265.803502221
  +CMS_DATA/bcmsprd/datafile/SYSAUX.272.803502221 10 31.9999847
  +CMS_DATA/bcmsprd/datafile/system.260.803502221 10 31.9999847
  20 20 +CMS_DATA/bcmsprd/datafile/undotbs2.261.803502407
  20 20 +CMS_DATA/bcmsprd/datafile/undotbs3.267.803502407
  +CMS_DATA/bcmsprd/datafile/cms_s_asset_xa_dat_09.dbf 20 0
  +CMS_DATA/bcmsprd/datafile/cms_s_asset_xa_dat_10.dbf 20 0

  < snipped >
  

  RMAN backs up all blocks of formatting - even if the lines have been removed and the blocks are "logically empty."  expdp, obviously, do not save deleted rows.  Similarly, if you have created a table, and then later he truncated, the blocks are formatted and be candidates for RMAN backups.  Truncated tables would be "empty" and would result in 0 rows exported.

  So, you will have this problem if you have deleted a large number of lines and/or issued truncates.

  Hemant K Collette

• Why RMAN is not storage of backups in "db_recovery_file_dest?

  Hello

  Select the name, the value of the parameter $ v

  WHERE name = 'db_recovery_file_dest.

  NAME	VALUE
  db_recovery_file_dest	/ora_backup

  When I run the following commands, RMAN lance store backups in "$ORACLE_HOME/dbs':

  RMAN > check effective additional 0 logical backup

  format "% d_ %%U t_ level0_.

  as a database of compressed backupset;

  My understanding is that RMAN should save the backups under '/ora_backup'.

  And when I run the following command, RMAN stores save under ' / ora_backup ':

  RMAN > backup database;

  Could you get it someone please let me know what I'm missing here?

  Here is the config RMAN:

  RMAN > show all.

  RMAN configuration parameters are:

  CONFIGURE RETENTION POLICY TO RECOVERY OF 7-DAY WINDOW;

  CONFIGURE BACKUP OPTIMIZATION # by default

  SET UP DEFAULT DISK DEVICE TYPE; # by default

  CONFIGURE CONTROLFILE AUTOBACKUP ON;

  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default

  SET UP THE DEVICE TYPE DISK PARALLELISM 10 TYPE OF BACKUP BACKUPSET.

  CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default

  CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default

  CONFIGURE CHANNEL DEVICE TYPE DISK MAXPIECESIZE 5 G;

  CONFIGURE MAXSETSIZE TO UNLIMITED; # by default

  CONFIGURE ENCRYPTION OF DATABASE # by default

  CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default

  CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default

  CONFIGURE the SNAPSHOT CONTROLFILE NAME to "/app/oracle/product/10.2.0/dbee/dbs/snapcf_< SID >.f '; # by default

  RMAN >

  Best regards

  If you specify a FORMAT, it substitutes for the use of the FRA.

  Run a

  INCREMENTAL LEVEL 0 AS COMPRESSED BACKUPSET DATABASE BACKUP

  Hemant K Collette

• RMAN backup optimization CANCEL 11g

  Hi all?
  
  I tested 11g RMAN CANCEL backup optimization
  1 I filled out by manipulation sql undo tablespace and not commit
  2nd undo_ts backed up by RMAN (size 24 m)
  3rd I made a commit
  Then the tablespace undo supported again but the backup_size column has not changed (24 m)
  Then I did some more manipulations and supported undo_ts again. This reduced time backup_size column. (11 m)
  Then I rebooted db and saved to undo_ts again. Size of backup at this time became what I expected (600K)
  
  The question is why did not reduce the size 11 g rman undo tablespace backups after validation?
  According to 11 g cancel optimization to
  
  ...

  SQL > select sum (bytes) of dba_free_space where nom_tablespace = 'UNDOTBS2 ';
  SUM (BYTES)
  13172736
  SQL > start
  because me 1.100000 loop
  insert into testundo values (i);
  end loop;
  end;
  /
  2 3 4 5 6
  PL/SQL procedure successfully completed.
  SQL > SQL > update of testundo game
  ID = 2 where id > 0;
  2
  Update testundo set
  *
  ERROR on line 1:
  ORA-30036: unable to extend segment by 8 in undo tablespace "UNDOTBS2".
  SQL > select sum (bytes) of dba_free_space where nom_tablespace = 'UNDOTBS2 ';
  Sum (bytes)

  RMAN > backup datafile 6;
  
  RMAN > backup from the list of the 6 data file;
  
  
  List of backup sets
  ===================
  
  Time of accomplishment BS key Type LV size device Type elapsed time
  10 full * 24.54M* DISK 00:00:04 June 10, 10
  BP key: 10 location: AVAILABLE Tablet: NO Tag: TAG20100610T142437
  Part name: /home/oracle/flash_recovery_area/11GR1/backupset/2010_06_10/o1_mf_nnndf_TAG20100610T142437_611ctr1f_.bkp
  List of files of data backup set 10
  Name of file LV Type cash SNA cash time
  6 integer 577669 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf 10 June 10
  
  
  

  SQL > commit;
  
  Full validation.

  RMAN > backup datafile format 6 "after commit.backup";
  
  RMAN > backup from the list of the 6 data file;
  
  List of backup sets
  ===================
  
  Time of accomplishment BS key Type LV size device Type elapsed time
  11 full * 24.54M* DISK 00:00:02 June 10, 10
  BP key: 11 location: AVAILABLE Tablet: NO Tag: TAG20100610T142541
  Item name: / home/oracle/product/11/Db_1/dbs/after commit.backup
  List of files of data backup set 11
  Name of file LV Type cash SNA cash time
  6 integer 577705 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf 10 June 10
  

  SQL > alter system archive log current;
  Modified system.
  SQL > commit;
  Validation complete.
  SQL > select count (*) in the testundo;
  COUNT (*)
  100000
  SQL > delete from testundo;
  100000 deleted rows.
  SQL > commit;
  Validation complete.
  SQL > insert into testundo values (1);
  1 line of creation.
  SQL > commit;
  Validation complete.
  SQL > alter system flush buffer_cache;
  Modified system.

  RMAN > backup datafile 6;
  
  RMAN > backup from the list of the 6 data file;
  
  
  List of backup sets
  ===================
  
  Time of accomplishment BS key Type LV size device Type elapsed time
  13 full * 11.03M* DISK 00:00:01 June 10, 10
  BP key: 13 status: AVAILABLE Tablet: NO Tag: TAG20100610T143359
  Part name: /home/oracle/flash_recovery_area/11GR1/backupset/2010_06_10/o1_mf_nnndf_TAG20100610T143359_611dd8sz_.bkp
  List of files to backup data value 13
  Name of file LV Type cash SNA cash time
  6 integer 578410 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf 10 June 10
  
  RMAN >
  

  SQL > shutdown immediate;
  The database is closed.
  The database is dismounted.
  ORACLE instance stops.
  SQL > startup
  ORACLE instance started.
  
  Total System Global Area 393375744 bytes
  Bytes of size 1300156 fixed
  352323908 variable size bytes
  33554432 buffers of data bytes
  Redo buffers 6197248 bytes
  Mounted database.
  Open database.
  SQL >

  RMAN > backup datafile 6;
  RMAN > backup from the list of the 6 data file;
  
  
  List of backup sets
  ===================
  
  Time of accomplishment BS key Type LV size device Type elapsed time
  
  Full 14 * DISK 00:00:02 600.00K* 10 June 10
  BP key: 14 location: AVAILABLE Tablet: NO Tag: TAG20100610T152843
  Part name: /home/oracle/flash_recovery_area/11GR1/backupset/2010_06_10/o1_mf_nnndf_TAG20100610T152843_611hlwmv_.bkp
  List of defined backup data files 14
  Name of file LV Type cash SNA cash time
  
  6 integer 580347 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf 10 June 10
  
  Thanks in advance
  Turkel

  Hi Turkel,
  Space used to cancel is also linked to the undo retention implementation.
  As it seems do you an update of test and perform backups on:
  -14: 24:37 (-> 25 M)
  -14: 25:41 (-> 25 M)
  -14:33:59 (-> 11 M)
  -15: 28:43 (-> 600 K)
  The first two backups are probably still in the retention period to cancel the update.
  The third backup shows a cancellation partly empty (is your setting 900?).
  The last falls outside the period of retention for the update, resulting the small size of backup.
  Kind regards
  Tycho

• My RMAN backup failed

  Yesterday my RMAN backup failed and wrote my diary RMAN
  
  Cat RMAN_REPORT_030411040001_RDFDB.log
  
  Recovery Manager: Release 10.2.0.4.0 - Production Sun 3 Apr 04:02:12 2011
  
  Copyright (c) 1982, 2007, Oracle. All rights reserved.
  
  connected to target database: RDFDB (DBID = 3113112584)
  connected to the recovery catalog database
  
  RMAN >
  from full resynchronization of the recovery catalog
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of command report to the 03/04/2011 04:02:21
  RMAN-03014: implicit recovery catalog Resync failed
  RMAN-03009: resync command failed full to the default channel to 03/04/2011 04:02:21
  ORA-01578: block ORACLE (corrupted file # 2, block # 19235) data
  ORA-01110: data file 2: ' / home/oracle10g/rmandb/dbf/data/rmandb_undotbs.dbf'
  
  
  My name is RDFDB and the error is RMANDB which is on another machine how can that I solve this problem?
  
  Another backup RMANDB is going well I am a bit confused as says it error ORA-01578: data corrupted ORACLE (file # 2, block # 19235) block
  ORA-01110: data file 2: ' / home/oracle10g/rmandb/dbf/data/rmandb_undotbs.dbf' and this means that there is nothing to do with RDFDB and in what RMANDB undotbs and ifthat is the case how come RMANDB happenend backup without any problem... well kindly help me to solve this problem.

  The block has already marked corrupt. As a result, RMAN ignores when you perform a backup of RMANDB.

  The simplest solution is to recreate the tablespace Undo in RMANDB. (Create a new Undo tablespace, alter system set undo_tablespace and then drop the old undo tablespace, preferably after a reboot).

  In this way, the RESYNCHRONIZATION for RDPDB command will access a new set of undo blocks.

  Hemant K Collette

• question of RMAN backup optimization

  Hello
  
  I met a related issue of RAM and would like to understand the answer:
  
  Configuration of RMAN optimization a backup the value ONE. Which of the following commands will affect this setting?
  
  one) backup Archivelog with ALL or AS options, b) backup Backupset ALL, c) backup Tablespace, d) Backup Database
  
  I think that all of the above are affected by the backup optimization, however, only a, b and d seems correct, not c. I wonder why tablespace is not affected - it is not read-only, etc. ?
  
  Any ideas? Thank you.

  That is right. Please see the link to the doc,
  http://download.Oracle.com/docs/CD/E11882_01/backup.112/e10642/rcmconfb.htm#BRADV113

  HTH
  Aman...

• RMAN backup space free after compression subpartition

  Hello!
  
  I have a strange situation. I have a table with partitions of range and 8 subpartitions. I compressed subpartitions according to this trick:
  [http://husnusensoy.wordpress.com/2008/01/23/compressing-subpartition-segments/]
  with excellent results. I released half of the disk space. But written rman still the same number of bytes to bands. Can someone explain why?
  
  My Oracle is company 10.2.0.4@itanium with HP - UX 11.23.
  
  Thans in advance.
  
  Table structure:

  CREATE TABLE tab
  (
    STREAM_ID                     NUMBER(38)      NOT NULL,
    STREAMROW                     NUMBER(38)      NOT NULL,
    EVENTBEGINDATE                DATE
    [...]
  )
  TABLESPACE DATA
  PCTUSED    0
  PCTFREE    10
  INITRANS   1
  MAXTRANS   255
  LOGGING
  PARTITION BY RANGE (EVENTBEGINDATE)
  SUBPARTITION BY HASH (STREAM_ID, STREAMROW)
  (  
    PARTITION P_MIN VALUES LESS THAN (TO_DATE(' 2006-11-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
      NOLOGGING
      COMPRESS
      TABLESPACE TYTAN_UDATA
      PCTFREE    0
      INITRANS   1
      MAXTRANS   255
      STORAGE    (
                  BUFFER_POOL      DEFAULT
                 )
      SUBPARTITIONS 8 STORE IN (DATA,DATA,UDATA,DATA,DATA,DATA,DATA,DATA),  
    PARTITION P_2006_11_01 VALUES LESS THAN (TO_DATE(' 2006-11-02 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
      NOLOGGING
      COMPRESS
      TABLESPACE DATA
      PCTFREE    0
      INITRANS   1
      MAXTRANS   255
      STORAGE    (
                  BUFFER_POOL      DEFAULT
                 )
  [...]

  It is a documented feature. Only unused blocks of RMAN backups if:

  -you are backing up to disk (NOT) - or
  -blocks were never used by any measure

  See here for more details: http://oradbatips.blogspot.com/2010/02/tip-86-what-it-is-missed-when-rman.html

  --
  Ronny Egner
  My Blog: http://blog.ronnyegner-consulting.de

  Published by: Ronny Egner on June 16, 2010 16:07

• 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

• RMAN backup on the database with data file with corrupted block

  Hi friends,

  I have a problem with a database of oracle 11g XE on windows server 2003, the database is in production, it is open, is operating normally.

  The database has no backup configured before, so I put the database archiving mode and tried to backup using rman utility, but it show me some errors.

  First of all, it showed me:

  ORA-19501: error in reading file... SYSAUX. DBF

  ORA-27070: async read/write failed

  OSD-04016: error queuing an asynchronous i/o request.

  And when I passed the dbv on the SYSAUX file utility. DBF showed the fatal error.

  So, I switched CHKDSK utility on windows to repair the disc of the error. After that, run utility dbv and he passed and showed me the corrupt on SYSAUX blocks. DBF

  Then, came to rman and ran:

  RMAN > validate the logical database checking;

  State of the file marked corrupt blocks examined empty blocks high YVERT

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

  3 0 1111 115840 78859075 FAILED

  File name: C:\ORACLEXE\APP\ORACLE\ORADATA\XE\SYSAUX. DBF

  Type block for lack of treated blocks blocks

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

  Data 0 0

  Index 0 0

  Other 38 114729

  After that: watching the content of v$ database_block_corruption;

  Show me a lot of lines like this:

  SQL > select * from v$ database_block_corruption;

  FOLDER # BLOCK # BLOCKS CORRUPTION_CHANGE # CORRUPTIO

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

  3 4440 1 FRACTURED 0

  3 4439 1 0 ZERO ALL THE

  3 4386 2 FRACTURED 0

  3 4384 1 0 ZERO ALL THE

  3 4334 1 0 ZERO ALL THE

  ...

  33 selected lines.

  Finally I try to rerun rman and he shows me the error:

  ORA-19566: exceeded the limit of 0 blocks corrupt file C:\ORACLEXE\APP\ORACLE\ORADATA\XE\SYSAUX. DBF

  How can I do backup with rman? Maybe I can by pass the corrupt block?

  I'll be grateful for any help you can provide.

  
  

  =)
  

  It would be better if you try to find the reason of corruption and try to recover the corrupt blocks. A block corrupted in the backup would really not must use. But if you're ready to take backup, you can ask RMAN to ignore corrupt blocks and move forward.

  Use the pseudo-code for the backup

  Run {set maxcorrupte for the database to 10;

  backup tablespace sysaux ;}

  HTH

  Aman...

• How to restore RMAN backups

  Hello

  I tried to include works of RMAN Oracle 12 c

  If I use the following command, I should have the backuppiece and the archivelog saved in a folder:

  RMAN > BACKUP database DATA PLUS ARCHIVELOG;

  If I ran this command in 4 different days, which I ended up having 4 folders with different inside files

  I guess that, in these files, I have the data files and the archivelogs

  Now I move these folders to tape, re-cutting the backups and delete expired

  Say that in a month, I need one of these backups if I put a band records and I added start with 'c:\path_of _restored_folder _L', so I added all files in the folder that I restored from tape

  Now, if I try to restore the basis of all is well but when I run the recover, it is missing some archiving logs it says

  If I put all the files for 4 days then he finds the archivelog she needs and pick up without problem

  on this basis I understand that in the folder containing a backuppiece of a specific day there is the newspaper of archive that I needed to recover from the DB, is that true? How can I know if the backups folder I need to replace in order to have all the required log archiving?

  At the moment my DB retrieves only if I handed out the Ribbon last backup folder, if I handed out the previous, it restores, but is not recover

  Also I have this configuration of the oracle recovery 3 days window maintains backups in order to be able to restore and recover the last 3 days and he simply deletes all obsolete if the FRA is full

  I tried earlier to set up the window of 3 days as a test recovery

  I ran a few backups and after that I ran the 5th FRA leak out of space and the backup fails

  I expect rman to remove the old backup and make way for a new that I have 5 backuppiece and the FRA is full, why he not do?

  Thank you

  The default behavior of RECOVER is to make a full recovery - right until the transactions today.  So it must all archivelogs.

  If you want to restore and recover to a point in time, use the SET clause to THAT specify a sequence of the newspaper or time or SNA.  Oracle will then not get beyond that point in time - that is to say he will not seek further archiving logs.

  (Ideally, when you restore an old backup, I also begins to restore the old controlfile, then using this controlfile).

  If you use the FRA in this way

  a. set db_recovery_file_dest_size and db_recovery_file_dest

  b. * not * used a FORMAT clause in the BACKUP command

  Oracle will recognize all backups in the FRA (you can check by querying V$ FLASH_RECOVERY_AREA_USAGE before and after the backup).

  In this case, Oracle can and will automatically purge outdated backups - that is to say any backup older than the retention period, provided that there is at least a L0 or backup complete closest to the retention period.  You should see messages to this effect in the alert of the instance database log file.

  Hemant K Collette

• RMAN backup command gets failure

  
  

  Hello;

  
  

  Merry Christmas to all
  

  
  

  It's the test database (10.2.0.1) on RHEL 4.8, Rman backup command was already.

  I don't understand why I got the error? What was the reason?
  

  
  

  RMAN > backup the database archivelog;

  From backup 25 December 14

  Current archived log

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

  allocated channel: ORA_DISK_1

  channel ORA_DISK_1: sid = 141 devtype = DISK

  channel ORA_DISK_1: from archive newspaper backupset

  channel ORA_DISK_1: specification of archive log backup set

  archive log entry thread = 1 sequence 2 recid = 1 stamp = 867230647 =

  archive log entry thread = 1 = 3 = 2 = 867233039 stamp recid sequence

  archive log entry thread = 1 sequence 4 recid = 3 = 867233044 stamp =

  archive log entry thread = 1 sequence 5 recid = 4 = 867233122 stamp =

  archive log entry thread = 1 sequence = recid 6 = 5 = 867233128 stamp

  archive log entry thread = 1 sequence = recid 7 = 6 = 867233214 stamp

  archive log entry thread = 1 sequence 8 recid = 7 = 867233453 stamp =

  archive log entry thread = 1 sequence 9 recid = 8 = 867233493 stamp =

  archive log entry thread = 1 sequence 10 recid = 9 = 867233559 stamp =

  channel ORA_DISK_1: starting piece 1 to December 25, 14

  channel ORA_DISK_1: finished piece 1 to December 25, 14

  piece handle=/home/oracle/oracle/product/10.2.0/db_1/flash_recovery_area/ORCL/backupset/2014_12_25/o1_mf_annnn_TAG20141225T101241_b9q5g4jo_.bkp tag = TAG20141225T101241 comment = NONE

  channel ORA_DISK_1: complete set of backups, time: 00:00:16

  Backup over at December 25, 14

  From backup 25 December 14

  using channel ORA_DISK_1

  channel ORA_DISK_1: from full datafile backupset

  channel ORA_DISK_1: specifying datafile (s) in backupset

  input datafile fno = 00001 name=/home/oracle/oracle/product/10.2.0/oradata/orcl/system01.dbf

  input datafile fno = name=/home/oracle/oracle/product/10.2.0/oradata/orcl/sysaux01.dbf 00003

  input datafile fno = 00005 name=/home/oracle/oracle/product/10.2.0/oradata/orcl/example01.dbf

  input datafile fno = name=/home/oracle/oracle/product/10.2.0/oradata/orcl/undotbs01.dbf 00002

  input datafile fno = name=/home/oracle/oracle/product/10.2.0/oradata/orcl/users01.dbf 00004

  channel ORA_DISK_1: starting piece 1 to December 25, 14

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

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

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

  RMAN-03002: failure of command thus backup archivelog to 2014/12/25 10:13:54

  ORA-19502: write error on file ' / home/oracle/oracle/product/10.2.0/db_1/flash_recovery_area/ORCL/backupset/2014_12_25/o1_mf_nnndf_TAG20141225T101301_%u_.bkp ', blockno 8833 (blocksize = 8192)

  ORA-27072: IO file error

  Linux error: 2: no such file or directory

  Additional information: 4

  Additional information: 8833

  Additional information: 348160

  > > Physical directories are available

  $ pwd

  /Home/Oracle/Oracle/product/10.2.0/Db_1/flash_recovery_area/ORCL

  [oracle@RAC1 ORCL] $ ls-l

  total 12

  drwxr-x - 3 oracle oinstall 4096 Dec 25 09:24 archivelog

  drwxr-x - 3 oracle oinstall 4096 Dec 25 09:18 backupset

  drwxr-x - 2 oracle oinstall 4096 Dec 24 17:16 onlinelog

  ORA-19502: write error on file ' / home/oracle/oracle/flash_recovery_area/ORCL/backupset/2014_12_26/o1_mf_nnndf_TAG20141226T233412_%u_.bkp ', blockno 37505 (blocks ize = 8192)

  I don't understand why is it taking over as "%u" rather than place a unique value for him. Is it the file with System FRA has enough space?

  DF h/home/oracle/oracle/flash_recovery_area/ORCL/backupset.

  Kind regards

  Shivananda