Understanding of database backup RMAN

Similar Questions

• Database backup RMAN with Veritas NetBackup catalog

  Hello
  
  How can I use Veritas NetBackup to backup my database of catalog RMAN? I need to stop this catalog DB in order to save it. How can I plan with NetBackup?
  
  Thanks in advance.
  
  qtpham

  Hello

  Normally, the catalog database backup is currently off cause is very small database and may remain unavailable for a few minutes. In my company, we use netbackup.
  Try to schedule an offline backup of the database via the Netbackup graphical interface, it will generate RMAN scripts bpstart_notify. YOUR_POLICY_NAME and bpend_notify. YOUR_POLICY_NAME under/usr/openv/netbackup/bin/if you use SOLARIS.

  Kind regards

  Rodrigo Mufalani
  http://mufalani.blogspot.com

• 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

• How to make a backup of the database with RMAN Oracle Single Instance

  People,

  Hello. I use the server of Oracle 11 GR 1 material with operating system Oracle Linux 5.10 database.

  I understand how to back up the database instance in SQL Server with Windows. But do not really understand how to back up the database instance in Oracle on Linux.
  I did it cold and hot backup for the database HRCS90 instance, but both receive the same error message.

  
  Cold backup is below:

  SQL > startup
  ORACLE instance started.

  Total System Global Area 538677248 bytes
  Bytes of size 2146024 fixed
  528482584 variable size bytes
  4194304 buffers of data bytes
  Redo buffers 3854336 bytes
  Mounted database.
  Open database.

  
  SQL > shutdown immediate
  The database is closed.
  The database is dismounted.
  ORACLE instance stops.

  
  RMAN > backup database;

  From backup 25 November 13
  using the control file of the target instead of recovery catalog database
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the backup command to the 25/11/2013 14:26:52
  RMAN-06171: not connected to the target database

  
  RMAN > backup HRCS90

  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-00558: error occurred during parsing of order entry
  RMAN-01009: syntax error: found 'distinctive sign': expected an of: ' archivelog, auxiliary, as, backup backupset, blocks, channel, check, copy, copies, controlfilecopy, cumulative, current, basic data, datafile, datafilecopy, device, diskratio, db_recovery_file_dest, db_file_name_convert, duration, filesperset, for, format, from, full, strength, file, incremental, keep, (, maxsetsize nochecksum, noexclude, nokeep, not, proxy, pool, re-use, recovery, section, skip). ', spfile, skip readonly, setsize, tablespace, tag to validate.
  RMAN-01008: the identifier of the AfDB was: HRCS90
  RMAN-01007: line 1 column 8 file: entry standard

  
  RMAN > backup database HRCS90

  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-00558: error occurred during parsing of order entry
  RMAN-01009: syntax error: found 'distinctive sign': expected an of: ' archivelog, auxiliary, backupset channel, copy, controlfilecopy, backup, common, base data, data file, datafilecopy, remove, diskratio, db_recovery_file_dest, filesperset, format, force, file, include, keep, (, maxsetsize, noexclude, nokeep, not, pool, more reuse, recovery, section, skip, spfile, pass readonly, setsize, tablespace, tag, to).
  RMAN-01008: the identifier of the AfDB was: HRCS90
  RMAN-01007: line 1 column 17 file: entry standard

  While the instance of database HRCS90 is starting, I do hot backup by using the same commands and get the same error message with above cold backup.

  My question is:

  Can any folk tell me specific steps (order by order) to back up a single instance of the database in Oracle with RMAN?

  
  Thank you.

  Yes, you can restore and recover the backup, but not at the moment. You will only be able to restore and recover at the time of your backup.

  For example.

  If you take backup (mount point with no mode of journal archive) at 06:00 and your grave database crashes at 21:00, you will be able to restore and recover until 06:00. You will find all the changes made to the database between 06:00 and 21:00.

  If you want your database to recover until 9 PM or until a point in time, then you must put your database in log mode archive, and then save the archives.

• backup rman design database with phsical ensures

  Hello

  12 c database, after physical expectation is created, I need backup rman configuration,

  The goal is: a) backup of database b) remove archivelogs that have been backed up, free up space FRA.

  Design as below:

  1:

  in RMAN (primary and standby):
  RMAN >
  Configure controlfile autobackup on;
  set the type of backup device type disk compressed backupset;
  CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;

  
  2: primary school:
  RMAN > CONFIGURE RETENTION POLICY to the 5 DAY RECOVERY WINDOW;

  3: in priamry, turn on track changes to block

  4: primary, implemented since rman level 0 (full backup) on Sunday.

  5: in the primary, the installation program rman level 1 backup from Monday to Saturday.

  6: primary, set up since rman "save archive backup delete them all obsolete" every hour;

  questions here:

  1. as in step 5, for the protection of the o and delete archivelog, the script using:

  Run {}
  allocate channel d1 type disk;
  SQL 'alter system archive log current';
  overlap archivelog all;
  backup AS COMPRESSED BACKUPSET archivelog all delete them all input;
  output channel d1;
  }

  I wonder if ' archivelog all delete all entries "will delete archivelog which was not taken on the eve of the database and broken standby database

  (hanging and out-of-sync with primary)... it is a concern, is that possible?

  2. If the primary database crashed, failover to standby mode, then restore/recovery primary, switch back to the primary, this design is just? If you have any good suggestions, please let me know.

  (to put it simply, I don't want to full/incremental backup to install standby, primary server CPU is good enough)

  Thank you very much!

  A few brief notes worth a visit:

  Based on Oracle 11 g Data Guard for the backup database and restore

  http://www.databasejournal.com/features/Oracle/article.php/3830766/leveraging-Oracle-11g-Data-Guard-for-database-backup-and-recovery.htm

  Standby database using RMAN

  http://Arup.blogspot.com/2007/07/standby-database-using-RMAN.html

  Best regards

  mseberg

• How to use backups RMAN to restore a RAC database to single instance on another host?

  How to use backups Rman to restore a RAC database to single instance on another host?

  I tried to copy these inline for you:

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

  Backups RMAN disk HowTo restore database RAC to single Instance on another node (Doc ID 415579.1)

  Down

• Restoring a backup RMAN to a new instance of the database

  Hi guys,.

  I have a problem with restoring a backup RMAN I have with me a new instance of the database. I have with me are:

  1. backup of the SPFile. (O1_MF_NCNNF_CTLFILE_BU_92DVGYO2_. BKP)

  2. backup of the control file (O1_MF_NNSNF_SPFILE_BU_92DVGW9H_. BKP)

  3. the full backup (O1_MF_NNSNF_FULLPROD_BU_92DVGW9H_. BKP)

  I received these files to a client environment and I need to restore these to a new instance of the database on a local computer. I gave an attempt as follows (in Oracle 10 g):

  1, creates a new instance of the (Test75) database using the Oracle Database Configuration Assistant

  2 SET ORACLE_SID = Test75

  3 connection to this instance with RMAN

  4 tried to restore the SPFILE from the BKP file received.

  
  

  I make mistakes and cannot continue. I don't know if I will carry out the correct steps. Please help me telling me how I should achieve this goal.

  
  

  Thank you.
  

  1. backup of the SPFile. (O1_MF_NCNNF_CTLFILE_BU_92DVGYO2_. BKP)

  2 backup of control file (O1_MF_NNSNF_SPFILE_BU_92DVGW9H_. BKP)

  The first backuppiece resembles a ControlFile and the other looks like a SPFILE'

  > I get error and cannot continue

  What is the error?  (I assume that you have tried to restore the O1_MF_NNSNF_SPFILE_BU_92DVGW9H_ SPFILE. BKP

  Note that you must also SET the DBID before restoring the controlfile

  Hemant K Collette

• Restore from different database Rman backup RMAN

  Hello world
  
  I'm practicing Rman, so I request that the way to restore the rman backup in a different database.
  
  For example:
  
  1. I have backup Rman of DB1 to level 0 and level 1 cumulative data base more archievelog
  
  2. I need to import or restore the backup Rman of DB1 to a different database DB2.
  
  What is the procedure to make the queries above. Please anyone one help out me.
  
  I use oracle 10g r2 running in windows server 2003.
  
  Thanks in advance.

  flanged wrote:
  Hello world

  I'm practicing Rman, so I request that the way to restore the rman backup in a different database.

  For example:

  1. I have backup Rman of DB1 to level 0 and level 1 cumulative data base more archievelog

  2. I need to import or restore the backup Rman of DB1 to a different database DB2.

  What is the procedure to make the queries above. Please anyone one help out me.

  I use oracle 10g r2 running in windows server 2003.

  Thanks in advance.

  If you want to restore the database from one node to the node of dfiferent, you can follow below url

  http://mohamedazar.WordPress.com/2011/03/13/disaster-recoveryrestore-database-from-one-server-to-another-server-when-different-location/

  but you couldnot able to restore the database backup entire rman in another database instance struture.

• The RMAN catalog database backup

  Version: 10.2.0.1.0
  
  We have created a database to host our RMAN catalog. This catalog contains info backup more RMAN stored scripts for 5 production databases. Now, we have to save this the RMAN catalog database.
  
  I'm going to use the control as the catalog file (IE. NOCATALOG) for our the RMAN catalog database. This should be good. Right? Best practices should I follow this topic?

  The catalog database can be saved as a BACKUP when COLD, if not in use for other purposes. Simple and easy backup and restore.

  Otherwise, you can make backups RMAN, but the this backup catalog database Controlfile.

  (You can even take copies to export the schema from the RMAN catalog!)

  Hemant K Collette

  Published by: Hemant K grapple on July 8, 2010 14:45

• Firewall rules RMAN target database and RMAN catalog database

  Hi, we are on Oracle 11.2.0.4 and we just build a new environment, in which case the RMAN catalog is located on a seprate from the target database server. I'm trying to figure if the firewall between these two rules should be two-way, so that the target database and RMAN catalog database can ping each other. If bi-directional rules in place, so what's the reason for this? I understand that during RMAN backup entries are made in the RMAN catalog database, but do not know if the RMAN catalog database must always meet target db. Thank you!

  If you run the rman command on the target database server, it acts as a client to the catalog database server by connecting on sqlnet to the catalog database.

  If you run the rman command on the catalog database server, it's a sqlnet connection join the target database server.

  In both cases, rman is simply a client that connects to the two databases.

  Hemant K Collette

• How to take database backup ASM/Instance?

  Hello
  
  I'm new with ASM. We take ASM/instance of database backup.
  
  can we have the idea to backup ASM?
  
  1. what components should be saved as database/Instance ASM / ASM all files?
  
  
  Please do the needful.
  
  Thank you
  Nitin

  Hello Nitin,

  First of all, you must understand that the RDBMS & ASM instance is different but yes, both are running on the same computer.

  ASM includes essentially two things: ASM instance (1) and the storage of the DSO (2).

  (1) ASM instance
  ------------------------

  That's just an instance when we do not backup but Yes if you want to keep the ASM instance configuration file then just follow these steps:

  [grid@host01 ~] $. oraenv
  ORACLE_SID = [+ ASM1]? + ASM1
  The basic Oracle for ORACLE_HOME=/u01/app/11.2.0/grid is/u01/app/grid

  SQL > create pfile='/home/grid/init+ASM1.ora' of spfile;

  Created file.

  (2) ASM STORAGE
  -------------------------

  -Storage ASM includes essentially ASM starts, namely new set of disks.

  -Whenever we do not create ASM diskgroup diskgroup contains still three things:

  (a) disc ASM
  (b) models and metadata
  (c) the ASM files (essentially datafile or all database files)

  -We take backup of two things on three things in ASM diskgroup:

  (1) ASM files - with RMAN because these are files of database.
  (2) ASM diskgroup models & metadata - with the MD_BACKUP of ASMCMD command.

  Now, MD_BACKUP will create a backup as your specified location file and this file will includes all models and metadata of the diskgroup. Benefits of taking diskgroup metadata are, if we lost the diskgroup, so we do not worry some details configuration command MD_RESTORE use to recreate the diskgroup with the same configuration. But remember that it does not restore the data file or any other file that was there on the diskgroup going to use RMAN to restore the missing files.

  See the example:

  ASMCMD > lsdg

  State Type sector Rebal to Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files name of the block
  EXTERN MOUNTED N 512 4096 1048576 11742 11643 0 11643 0 N ABC /.
  NORMAL CLIMB N 512 4096 1048576 15656 10661 1259 4701 0 N DATA.
  EXTERN MOUNTED N 512 4096 1048576 15656 13874 0 13874 0 N FRA.
  ASMCMD >
  >

  ASMCMD >/home/grid/data_backup_file - G DATA md_backup
  Group of disk to save metadata: DATA
  Path to current directory alias: cluster01
  Path to current directory alias: ORCL
  Path to current directory alias: ORCL/fichier_parametres
  Path to current directory alias: ORCL/DATA file
  Current directory alias path: cluster01/OCRFILE
  Path to current directory alias: ORCL/CONTROLFILE
  Path to current directory alias: ORCL/TEMPFILE
  Path to current directory alias: ORCL/ONLINELOG
  Current directory alias path: cluster01/ASMPARAMETERFILE
  ASMCMD >

  * vim # / home/grid/data_backup_file *.

  @diskgroup_set =)
  {
  "ATTRINFO"-ONLINE {}
  "MODEL. OCRBACKUP. REDUNDANCY '-ONLINE 18',
  "MODEL. FICHIER_PARAMETRES. MIRROR_REGION '-ONLINE '0',
  "MODEL. TEMPORARY FILE. REDUNDANCY '-ONLINE 18',
  "MODEL. TEMPORARY FILE. MIRROR_REGION '-ONLINE '0',
  "MODEL. FICHIER_PARAMETRES. REDUNDANCY '-ONLINE 18',
  "SECTOR_SIZE"-ONLINE '512',
  "MODEL. DATAGUARDCONFIG. REDUNDANCY '-ONLINE 18',
  ' ACCESS_CONTROL. UMASK '-ONLINE '066'.
  "MODEL. ASM_STALE. STRIPE '-ONLINE '0',
  "MODEL. ARCHIVELOG. STRIPE '-ONLINE '0',
  "MODEL. DATAGUARDCONFIG. PRIMARY_REGION '-ONLINE '0',
  "MODEL. OCRBACKUP. STRIPE '-ONLINE '0',
  "MODEL. DATA FILE. STRIPE '-ONLINE '0',
  "AU_SIZE"-ONLINE '1048576',
  "MODEL. ASMPARAMETERFILE. STRIPE '-ONLINE '0',
  "MODEL. TRACK CHANGES. PRIMARY_REGION '-ONLINE '0',
  "MODEL. CONTROLFILE. REDUNDANCY '-ONLINE 19',
  "MODEL. FLASHFILE. STRIPE '-ONLINE '0',
  "MODEL. BACKUPSET. PRIMARY_REGION '-ONLINE '0',
  "MODEL. ARCHIVELOG. PRIMARY_REGION '-ONLINE '0',
  "MODEL. TRACK CHANGES. STRIPE '-ONLINE '0',
  "MODEL. ONLINELOG. PRIMARY_REGION '-ONLINE '0',
  "MODEL. TRACK CHANGES. REDUNDANCY '-ONLINE 18',
  "MODEL. BACKUPSET. STRIPE '-ONLINE '0',
  "MODEL. OCRFILE. MIRROR_REGION '-ONLINE '0',
  "DISK_REPAIR_TIME' => '3.6 h."
  "MODEL. AUTOBACKUP. REDUNDANCY '-ONLINE 18',
  "MODEL. DUMPSET. REDUNDANCY '-ONLINE 18',
  "MODEL. RETURN OF FLAME. MIRROR_REGION '-ONLINE '0',
  "MODEL. DUMPSET. MIRROR_REGION '-ONLINE '0',
  "MODEL. DUMPSET. PRIMARY_REGION '-ONLINE '0',
  "MODEL. ASM_STALE. REDUNDANCY '-ONLINE 19',
  "MODEL. RETURN OF FLAME. PRIMARY_REGION '-ONLINE '0',
  "MODEL. CONTROLFILE. STRIPE '-ONLINE 1',
  "MODEL. DATA FILE. REDUNDANCY '-ONLINE 18',
  "MODEL. XTRANSPORT. REDUNDANCY '-ONLINE 18',
  "MODEL. AUTOBACKUP. PRIMARY_REGION '-ONLINE '0',
  "MODEL. CONTROLFILE. MIRROR_REGION '-ONLINE '0',
  "MODEL. DATA FILE. PRIMARY_REGION '-ONLINE '0',
  "MODEL. ASMPARAMETERFILE. REDUNDANCY '-ONLINE 18',
  "MODEL. FLASHFILE. MIRROR_REGION '-ONLINE '0',
  "MODEL. ASM_STALE. MIRROR_REGION '-ONLINE '0',
  "MODEL. RETURN OF FLAME. REDUNDANCY '-ONLINE 18',
  "MODEL. DATAGUARDCONFIG. STRIPE '-ONLINE '0',
  "CELL. SMART_SCAN_CAPABLE'-ONLINE 'FALSE. '
  "TEMPLATE_VERSION"-ONLINE '186646528',
  "MODEL. FICHIER_PARAMETRES. STRIPE '-ONLINE '0',
  "MODEL. DATA FILE. MIRROR_REGION '-ONLINE '0',
  "MODEL. FICHIER_PARAMETRES. PRIMARY_REGION '-ONLINE '0',
  "MODEL. BACKUPSET. MIRROR_REGION '-ONLINE '0',
  "MODEL. OCRBACKUP. MIRROR_REGION '-ONLINE '0',
  "MODEL. ONLINELOG. REDUNDANCY '-ONLINE 18',
  "MODEL. ASMPARAMETERBAKFILE. STRIPE '-ONLINE '0',
  ' ACCESS_CONTROL. PERMIT TO '-ONLINE 'FALSE. '
  "MODEL. DATAGUARDCONFIG. MIRROR_REGION '-ONLINE '0',
  "MODEL. TEMPORARY FILE. PRIMARY_REGION '-ONLINE '0',
  "COMPATIBLE. RDBMS '-ONLINE '10.1.0.0.0'.
  "MODEL. FLASHFILE. PRIMARY_REGION '-ONLINE '0',
  "MODEL. ONLINELOG. MIRROR_REGION '-ONLINE '0',
  "MODEL. FLASHFILE. REDUNDANCY '-ONLINE 18',
  "MODEL. OCRBACKUP. PRIMARY_REGION '-ONLINE '0',
  "MODEL. OCRFILE. STRIPE '-ONLINE '0',
  "MODEL. AUTOBACKUP. MIRROR_REGION '-ONLINE '0',
  "MODEL. ASM_STALE. PRIMARY_REGION '-ONLINE '0',
  "MODEL. ASMPARAMETERBAKFILE. PRIMARY_REGION '-ONLINE '0',
  "MODEL. XTRANSPORT. PRIMARY_REGION '-ONLINE '0',
  "MODEL. DUMPSET. STRIPE '-ONLINE '0',
  "MODEL. TEMPORARY FILE. STRIPE '-ONLINE '0',
  "MODEL. OCRFILE. PRIMARY_REGION '-ONLINE '0',
  "MODEL. ONLINELOG. STRIPE '-ONLINE '0',
  "MODEL. ARCHIVELOG. REDUNDANCY '-ONLINE 18',
  "MODEL. OCRFILE. REDUNDANCY '-ONLINE 18',
  "MODEL. ARCHIVELOG. MIRROR_REGION '-ONLINE '0',
  "MODEL. ASMPARAMETERFILE. MIRROR_REGION '-ONLINE '0',
  "MODEL. RETURN OF FLAME. STRIPE '-ONLINE '0',
  "MODEL. CONTROLFILE. PRIMARY_REGION '-ONLINE '0',
  "MODEL. XTRANSPORT. MIRROR_REGION '-ONLINE '0',
  "MODEL. BACKUPSET. REDUNDANCY '-ONLINE 18',
  "MODEL. ASMPARAMETERBAKFILE. REDUNDANCY '-ONLINE 18',
  "MODEL. XTRANSPORT. STRIPE '-ONLINE '0',
  "MODEL. TRACK CHANGES. MIRROR_REGION '-ONLINE '0',
  "COMPATIBLE. ASM '-ONLINE '11.2.0.0.0'.
  "MODEL. ASMPARAMETERBAKFILE. MIRROR_REGION '-ONLINE '0',
  "MODEL. ASMPARAMETERFILE. PRIMARY_REGION '-ONLINE '0',
  "MODEL. AUTOBACKUP. STRIPE'-'0' ONLINE
  },
  "DISKSINFO"-ONLINE {}
  "ASMDISK02"-ONLINE {}
  "ASMDISK02"-ONLINE {}
  "TOTAL_MB"-ONLINE '3914',
  "FAILGROUP" => "ASMDISK02."
  "NAME" => "ASMDISK02."
  "DGNAME"-ONLINE "DATA."
  'PATH' => 'ORCL:ASMDISK02 '.
  }
  },
  "ASMDISK01"-ONLINE {}
  "ASMDISK01"-ONLINE {}
  "TOTAL_MB"-ONLINE '3914',
  "FAILGROUP" => "ASMDISK01."
  "NAME" => "ASMDISK01."
  "DGNAME"-ONLINE "DATA."
  'PATH' => 'ORCL:ASMDISK01 '.
  }
  },
  "ASMDISK04"-ONLINE {}
  "ASMDISK04"-ONLINE {}
  "TOTAL_MB"-ONLINE '3914',
  "FAILGROUP" => "ASMDISK04."
  "NAME" => "ASMDISK04."
  "DGNAME"-ONLINE "DATA."
  'PATH' => 'ORCL:ASMDISK04 '.
  }
  },
  "ASMDISK03"-ONLINE {}
  "ASMDISK03"-ONLINE {}
  "TOTAL_MB"-ONLINE '3914',
  "FAILGROUP" => "ASMDISK03."
  "NAME" => "ASMDISK03."
  "DGNAME"-ONLINE "DATA."
  'PATH' => 'ORCL:ASMDISK03 '.
  }
  }
  },
  "DGINFO"-ONLINE {}
  "DGTORESTORE"-ONLINE 0
  "DGCOMPAT"-ONLINE ' 11.2.0.0.0. "
  "DGNAME"-ONLINE "DATA."
  "DGDBCOMPAT"-ONLINE ' 10.1.0.0.0. "
  "DGTYPE"-ONLINE "NORMAL."
  "DGAUSZ"-ONLINE '1048576'
  },
  "ALIASINFO"-ONLINE {}
  '6' => {
  "DGNAME"-ONLINE "DATA."
  'LEVEL'-ONLINE 1
  "ALIASNAME"-online "cluster01/ASMPARAMETERFILE"
  'REFERENCE_INDEX'-'16777322' ONLINE
  },
  '3' => {
  "DGNAME"-ONLINE "DATA."
  'LEVEL'-ONLINE 1
  "ALIASNAME" => "ORCL/CONTROLFILE.
  'REFERENCE_INDEX'-'16777534' ONLINE
  },
  '7' => {
  "DGNAME"-ONLINE "DATA."
  'LEVEL'-ONLINE 1
  "ALIASNAME" => "ORCL/FICHIER_PARAMETRES,"
  'REFERENCE_INDEX'-'16777693' ONLINE
  },
  '2' => {
  "DGNAME"-ONLINE "DATA."
  'LEVEL'-ONLINE 1
  "ALIASNAME" => "ORCL/ONLINELOG,"
  'REFERENCE_INDEX'-'16777587' ONLINE
  },
  '8' => {
  "DGNAME"-ONLINE "DATA."
  'LEVEL'-ONLINE 1
  "ALIASNAME"-online "cluster01/OCRFILE"
  'REFERENCE_INDEX'-'16777375' ONLINE
  },
  '1' => {
  "DGNAME"-ONLINE "DATA."
  'LEVEL'-ONLINE 0
  "ALIASNAME"-online "cluster01."
  'REFERENCE_INDEX'-'16777269' ONLINE
  },
  '4' => {
  "DGNAME"-ONLINE "DATA."
  'LEVEL'-ONLINE 1
  "ALIASNAME" => ORCL/DATA FILE"."
  'REFERENCE_INDEX'-'16777481' ONLINE
  },
  '0' => {
  "DGNAME"-ONLINE "DATA."
  'LEVEL'-ONLINE 0
  "ALIASNAME" => "ORCL".
  'REFERENCE_INDEX'-'16777428' ONLINE
  },
  '5' => {
  "DGNAME"-ONLINE "DATA."
  'LEVEL'-ONLINE 1
  "ALIASNAME" => "ORCL/TEMPFILE"
  'REFERENCE_INDEX'-'16777640' ONLINE
  }
  },
  'TEMPLATEINFO'-ONLINE {}
  '11' => {}
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  'TEMPNAME' => 'AUTOBACKUP.
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '7' => {
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME' => 'ASMPARAMETERFILE."
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '2' => {
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME' => 'ARCHIVELOG."
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '17' => {}
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME' => 'OCRBACKUP."
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '1' => {
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME' => 'ASM_STALE."
  "REDUNDANCY"-ONLINE "HIGH."
  'SYSTEM' => 'Y '.
  },
  '18' => {}
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME' => 'ONLINELOG."
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '0' => {
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  'TEMPNAME' => 'DATAFILE ',.
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '16' => {}
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME' => 'OCRFILE."
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '13' => {}
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME'-ONLINE"TRACK CHANGES. "
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '6' => {
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME' => 'ASMPARAMETERBAKFILE."
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '3' => {
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME' => 'FLASHFILE."
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '9' => {
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME" => "TEMPFILE"
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '12' => {}
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME' => 'XTRANSPORT."
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '14' => {}
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME'-ONLINE"FLASHBACK. "
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '15' => {}
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME' => 'DATAGUARDCONFIG."
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '8' => {
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME' => 'FICHIER_PARAMETRES."
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '4' => {
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE "FINE."
  'TEMPNAME' => 'CONTROLFILE.
  "REDUNDANCY"-ONLINE "HIGH."
  'SYSTEM' => 'Y '.
  },
  '10' => {}
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME' => 'BACKUPSET."
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '5' => {
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME' => 'DUMPSET."
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  }
  }
  }
  );

  NOTE:

  To re-create the diskgroup dropped with the same restoration of the configuration of the diskgroup even with the aid of diskgroup as:

  asmcmd >/home/grid/data_backup_file - full - G DATA md_restore

  Hope its clear now.

  Thank you

  Ashish Shukla

• backup RMAN with damaged block

  Hello
  
  First-, I have problem on non-production 11.2.0.1.0 database, so I'm not deeply concerned about data. But I need to understand what happened with database backups and how to prevent these things in the future.
  So - I have backup complete regular weekly EM and daily incremental backups. Later, he had problem with equipment and some blocks corrupted database found. The weekly backup ran without error and obsolete backups have been removed. Now, it is not possible to 'retrieve the list of corruption' because there is no backup without the corruption (RMAN-06023: no backup or copy of the data file 6 found to restore). I'm not worried about the loss of data, but I need to know how is the backup contains the corrupt blocks.
  
  I checked the data file using utility dbv
  

  DBVERIFY - Verification starting : FILE = /opt/oracle/oradata/orcl/users03.dbf
  
  DBV-00200: Block, DBA 27525766, already marked corrupt
  csc(0x0001.7b01729f) higher than block scn(0x0000.00000000)
  Page 2359942 failed with check code 6054
  
  
  DBVERIFY - Verification complete
  
  Total Pages Examined         : 3840000
  Total Pages Processed (Data) : 453896
  Total Pages Failing   (Data) : 1
  Total Pages Processed (Index): 2959104
  Total Pages Failing   (Index): 0
  Total Pages Processed (Other): 424025
  Total Pages Processed (Seg)  : 0
  Total Pages Failing   (Seg)  : 0
  Total Pages Empty            : 2975
  Total Pages Marked Corrupt   : 1
  Total Pages Influx           : 0
  Total Pages Encrypted        : 0
  Highest block SCN            : 2156227446 (1.2156227446)

  As you can see the data file 6 - user03.dbf contains errors. Also the backups now contain errors.
  
  (1) so how is it possible that the scheduled backup EM took place without problems and now the backup contains corrupted blocks. How to avoid this in the future? I know there is MAXCORRUPT setting. How can I check its current value? How can I configure using backups EM on-demand?
  
  (2) Secondly, at the same time, I studied the RMAN commands. So I have suspended the work of backup EM and run follwing command. And backup represented without error. How is this possible, if the data in the file users06.dbf is corrupted block?
  
  
  Thank you!
  

  RMAN> run {
   set MAXCORRUPT for datafile 6 to 0;
   backup as compressed backupset datafile 6;
   }
  2> 3> 4>
  executing command: SET MAX CORRUPT
  
  Starting backup at 07-NOV-12
  using channel ORA_DISK_1
  using channel ORA_DISK_2
  using channel ORA_DISK_3
  using channel ORA_DISK_4
  using channel ORA_DISK_5
  channel ORA_DISK_1: starting compressed full datafile backup set
  channel ORA_DISK_1: specifying datafile(s) in backup set
  input datafile file number=00006 name=/opt/oracle/oradata/orcl/users03.dbf
  channel ORA_DISK_1: starting piece 1 at 07-NOV-12
  channel ORA_DISK_1: finished piece 1 at 07-NOV-12
  piece handle=/opt/oraBackup/rman/nrnpo0sg_1_1 tag=TAG20121107T200120 comment=NONE
  channel ORA_DISK_1: backup set complete, elapsed time: 01:13:05
  Finished backup at 07-NOV-12
  
  Starting Control File and SPFILE Autobackup at 07-NOV-12
  piece handle=/opt/oraBackup/rman/c-1253245572-20121107-03 comment=NONE
  Finished Control File and SPFILE Autobackup at 07-NOV-12

  OK, sounds good, do not hesitate to open a TAR because bedbugs are not all public...

  Keep us in the loop.

  Good bye.

• Full restore of the database of RMAN cross-platform

  All the
  
  I have a database 10.2.0.3 on Solaris 10 OS.
  
  I did a full upward (level 0) this database using rman with auto save on. I'm trying to worl on a scenario where I could restore that backup on another linux machine. so I copied all the elements on the target linux server backup. go to a local installation of RDBMS (10.2.0.3) on the linux machine I'm trying to restore the database... but does not yet...
  
  When I deliver restore spfile or restore the control file a + < backup file name > +; the guest continues search in rear location that responded to the questionnaire didn't tell no piece found backup... Here are the encode stage, I'm...
  
  
  1. set up env on the linux server
  
  2 rman target /.
  
  (instance not started but rman to connect)
  
  3 set the DBID = + < ID DB data source running on Solaris > +.
  
  It run set dbid =
  
  4 startup nomount
  
  as the pfile/spfile file is not available in $ORACLE_HOME/dbs on a linux machine picks it up pfile by default however, but the instance stars no Assembly...
  
  5 restore spfile to ' / u01/app/oracle/product/10.2.0/rman_bkp/c-300009955'
  
  Here, he is not able to restore any thing.same is the case with the control file.
  
  Ideas please advice
  
  Sarat

  Sarat Chandra C wrote:
  Thanks for the referance. Now, I understand that I am not able to use the transportable database command to carry the entire db. However, there is a line in the 'Cross-Platform Database Transportable Restrictions' that says ++ 'main restricting cross-platform transportable database is that the platform of source and destination must share the same endian format. For example, while you can transport a database from Microsoft Windows to Linux for x 86 (the two little endian) or HP - UX, Aix (the two big endian), you may not carry a set of base HP_UX to Linux for x 86 using this feature. You can, however, create a new database on a destination manually, and necessary transport of tablespaces of the source database platform using cross-platform transportable tablespace as described in "Cross - Platform Tranportation Tablespace: CONVERT DATAFILE or TABLESPACE. » +

  I understand that if we are willing to carry each tablespace from Source to target individually, may then be able to replicate a transportable database. Fact the transportable tablespace have not all restrictions has obtained from the database of transport compared to the platform and Endian? Please specify.

  Also is there a matrix of support for thr transportable database and tablespaces which we could see?

  Kind regards!
  Sarat

  Sarat,

  The same restriction that is there for the transport of the whole base is quite real for the transportable tablespace as well if you go to the cross-platform. Endian must match across platforms that only you can do otherwise, as the database feature, you must convert the source file to the target-endian.

  If you look at the doc of reference order of unlocking Tablespace
  http://download.Oracle.com/docs/CD/B19306_01/backup.102/b14194/rcmsynta063.htm#RCMRF1919

  This restriction is documented here in addition to the other restrictions
  ,
  >
  Restrictions and antonyms

  Limitations on the creation of tablespace portable games described in the Oracle database administrator's Guide apply to transport backup storage spaces, with the exception of accountability read-only storage.

  TRANSPORT TABLESPACE does not format endian conversion. If the target platform has a different endian format, you must use the CONVERT RMAN command to perform the separate step of conversion of data files endian format portable overall.
  >

  HTH
  Aman...

• Only the unused blocks backup RMAN as well?

  DB version: 11.2.0.4

  OS: RHEL 6.6

  If I remember correctly, RMAN backs up only used blocks. I created a tablespace of 20 GB, as shown below. When I backed up, the backup piece is only 4MB in size, as shown below.

  SQL > create tablespace TEST_TS3 datafile '+ DATA_DG' size 20 G

  autoextend on

  MaxSize 32767 m

  Local extended management

  single 4 M size

  Auto segment space management;

  Created tablespace.

  SQL >

  SQL > select tablespace_name, bytes/1024/1024 of dba_Data_Files where nom_tablespace = 'TEST_TS3 ';

  BYTES/1024/1024 NOM_TABLESPACE

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

  TEST_TS3 20480

  Backup tablespace TEST_TS3 that is not used by all segments (empty)

  RMAN > backup tablespace TEST_TS3 format='/u05/RMAN_BKP/TBS_%U_%T.rmbk' tag = TEST_TS3_BKP;

  From 18 February 16 backup

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

  allocated channel: ORA_DISK_1

  channel ORA_DISK_1: SID = 4941 instance = HMAGPRD2 = DISK device type

  channel ORA_DISK_1: starting full datafile from backup set

  channel ORA_DISK_1: specifying datafile (s) in the backup set

  Enter a number of file datafile = name=+DATA_DG/hmagprd2/datafile/test_ts3.413.904152141 00144

  channel ORA_DISK_1: starting piece 1-18 February 16

  channel ORA_DISK_1: finished piece 1-18 February 16

  piece handle=/u05/RMAN_BKP/TBS_03qu8hg2_1_1_20160218.rmbk tag = TEST_TS3_BKP comment = NONE

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

  Backup finished on 18 February 16

  $

  $ ls - lh /u05/RMAN_BKP/TBS_03qu8hg2_1_1_20160218.rmbk

  -rw - r - 1 oracle oinstall 4.1 M 18 Feb 17:29 /u05/RMAN_BKP/TBS_03qu8hg2_1_1_20160218.rmbk

  But in the world of real output, size of the RMAN backups seems to be much higher.

  The following production DB is 27.5 terabytes in size as evidenced by the physical layer (DBA_DATA_FILES. Column of BYTES)

  SQL > select sum(bytes/1024/1024/1024) bytesGB from dba_Data_Files;

  BYTESGB

  ----------

  27885.3252

  But at the level of the logic layer, the used space is only 16.5 TB as evidenced by DBA_EXTENTS. BYTES column

  SQL > select sum(bytes/1024/1024/1024) bytesGB from dba_extents.

  BYTESGB

  ----------

  16621.316

  But the size of RMAN backup came to 20 terabytes , become almost 4TB that space consumed at the level of the logical layer (DBA_EXTENTS. BYTES).

  Why is this?

  RMAN jump blocks that have never been used. If a block has been used in the past, it will be included in the same backup if currently is not used:

  https://docs.Oracle.com/CD/B28359_01/backup.111/b28270/rcmcncpt.htm

  Compression for backup sets

  When you back up the data files of backup sets, RMAN can use unused block compression to skip blocks of data file. RMAN always ignores blocks that have never been used. Under certain conditions, which are listed in the BACKUP AS BACKUPSET entry in reference Oracle database backup and recovery, RMAN also ignores the blocks that are not currently used. Data file backup sets are generally smaller than copies of data file and take less time to write. Compression of the unused block is fundamental to how RMAN writes files of data in backup items and cannot be disabled.

• Help remove backups rman (delete the repository)

  Hi all.

  I will soon be administering a few databases Oracle (11g Rel2). Currently these DBs area in log mode archive with a backup rman in place policy.

  
  

  I don't like this policy and you want to use my own, incremental backups from updadateable, so this is the plan I have in mind.

  
  

  (1) disable mode archive.

  
  

  (2) a clean shutdown and take a backup to cold.

  
  

  (3) since after you disable archiving, backups RMAN ALL will be unusable, I want to remove them (including newspapers archive and backup sets).

  
  

  (4) after the correct deletion, set up some persistent RMAN settings, such as retention policy, controlfile autobackup and optimization.

  
  

  (5) turn on archiving

  
  

  (6) to set up the new policy based backups backup incremental updateable with duplex location for archiving logs.

  
  

  Help is requested on the best way to clean all the backups (3).

  
  

  I can manually delete the backups and do overlap, but according to the Oracle Documentation "Delete backup" will be delete all backups for data recorded in the RMAN Repository.

  
  

  So which is the best way easier and faster? Will delete backup include the archive logs?

  
  

  Thanks in advance. Luis!

  
  

  myluism wrote:

  Can I still use them?

  I would say it is "the wrong answer to evil. When you disable log mode archive, you can only back up the database when it is stopped and only to restore and recover the database until the last stop.

  Looking at your plan, I wonder what you are trying to accomplish first log mode archive disabling and then enabling archive mode log again. Why do you think that this is necessary and what you're trying to accomplish.

  You need not disable and enable log mode archive in order to eliminate the obsolete achivelogs.

  If you are not satisfied with the retention policy, simply change it. All backups that are outside your retention policy will be considered as obsolete and you can remove them using RMAN delete obsolete, which will remove all files as well as the appropriate data backup from the RMAN Repository.

  For example you can archivelog delete all the entries backup and then delete the backupset or remove them at the OS level, do overlap and then use delete noprompt expired archivelog all.

  The retention policy applies to backup and archivelogs. However, you can have a separate archivelog deletion policy that applies to archivelogs.