Checkpoint during RMAN backup

Similar Questions

• ERROR during RMAN backups

  channel ORA_DISK_1: starting piece 1 to August 8, 11
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03009: failure of the backup command on the channel ORA_DISK_1 at 08-08-2011 21:01
  : 49
  ORA-19502: write error on file ' / home/oracle/backups/df_t758667603_s13834_p1, "
  blockno 334721 (blocksize = 8192)
  ORA-27063: skgfospo: number of bytes read or written is incorrect
  Additional information: 172032
  Additional information: 1048576
  
  
  What does that mean?

  878226 wrote:
  channel ORA_DISK_1: starting piece 1 to August 8, 11
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03009: failure of the backup command on the channel ORA_DISK_1 at 08-08-2011 21:01
  : 49
  ORA-19502: write error on file ' / home/oracle/backups/df_t758667603_s13834_p1, "
  blockno 334721 (blocksize = 8192)
  ORA-27063: skgfospo: number of bytes read or written is incorrect
  Additional information: 172032
  Additional information: 1048576

  What does that mean?

  It seems that you don't have enough space to ' home/oracle/backups /' directory

• RMAN backup Linux drivers shared on windows 2008 Server.

  Hi all
  
  I want to know is - it possible to rman backup to shared disk windows 2008 for a database of runnig under Linux.
  
  I tried it and getting rman-03002 followed by ORA-19504, error Ora-27040 and linux-x86_64.
  
  I used the following command to mount my windows share
  Mount-t cifs/o username = administrator, password = "XXXXXX" //172.16.1.50/files/MNT
  
  
  Concerning
  Nidsh
  
  Edited by: 883687 August 15, 2012 23:08

  Hello;

  It should be possible. The ORA-27040 is

  "O/S-Error: (OS 3) The system cannot find the path specified."
  

  and the second error ORA-27040 seems to be an effect of the first.

   File create error, unable to create file
  

  Could be a permissions problem, so if you can mount the disk space windows, but cannot write to it (yet)

  There is a note of support Oracle that covers this:

  ORA-19504 ORA-27040 during Rman backup in a Directory Windows mounted under Linux [464267.1 ID]

  Which confirms, in my view, the answer is Yes.

  Further that:

  RMAN fail with ORA-19504 ORA-27040 when backup remote server linux [726858.1 ID] Windows Mount Volume

  Best regards

  mseberg

  Published by: mseberg on August 16, 2012 04:33

• Switch journal during the RMAN backup

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

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

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

  Aman...

• During the backup archivelog backups online

  Hello

  Oracle 11.2.0.4

  Linux SLES 11 SP2

  
  During our backup window, some batches are executed generate an amount of redo. Completion of our hot backup, it backs up all records generated and removes all the. We are afraid to fill our archivelog files before the end of hot backup. It's going to be any problem if I back up and delete the archivelogs during the backup hot (using a different RMAN command)?  For the moment, we are unable to add space for the file archive system.

  
  

  These are the rman commands executed:

  
  

  Hot backup
  

  
  

      RUN{
                  ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
                  ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';
                  ALLOCATE CHANNEL ch02 TYPE 'SBT_TAPE';
                  ALLOCATE CHANNEL ch03 TYPE 'SBT_TAPE';
                  SEND 'NB_ORA_SERV=$NB_ORA_SERV,NB_ORA_CLIENT=$NB_ORA_CLIENT,NB_ORA_POLICY=$NB_ORA_POLICY';
                  BACKUP
                         $BACKUP_TYPE
                         SKIP INACCESSIBLE
                         TAG $BTAG$(date +"%Y%m%d%H%M%S")
                         FILESPERSET 1
                         FORMAT 'bk_%U_%t'
                         DATABASE;
                  sql 'alter system archive log current';
                  RELEASE CHANNEL ch00;
                  RELEASE CHANNEL ch01;
                  RELEASE CHANNEL ch02;
                  RELEASE CHANNEL ch03;
                  # backup all archive logs
                  ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
                  ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';
                  BACKUP
                          filesperset 20
                          TAG $BTAGAR$(date +"%Y%m%d%H%M%S")
                          FORMAT 'al_%s_%p_%t'
                          ARCHIVELOG ALL DELETE INPUT;
                  RELEASE CHANNEL ch00;
                  RELEASE CHANNEL ch01;
          }
  
  

  
  

  Archives

  
  

        RUN{
                  # backup all archive logs
                  ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
                  ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';
                  ALLOCATE CHANNEL ch02 TYPE 'SBT_TAPE';
                  ALLOCATE CHANNEL ch03 TYPE 'SBT_TAPE';
                  ALLOCATE CHANNEL ch04 TYPE 'SBT_TAPE';
                  SEND 'NB_ORA_SERV=$NB_ORA_SERV,NB_ORA_CLIENT=$NB_ORA_CLIENT,NB_ORA_POLICY=$NB_ORA_POLICY';
                  BACKUP
                          filesperset 10
                          TAG $BTAGAR$(date +"%Y%m%d%H%M%S")
                          FORMAT 'al_%s_%p_%t'
                          ARCHIVELOG ALL DELETE INPUT;
                  RELEASE CHANNEL ch00;
                  RELEASE CHANNEL ch01;
                  RELEASE CHANNEL ch02;
                  RELEASE CHANNEL ch03;
                  RELEASE CHANNEL ch04;
          }
  
  

  
  

  Thank you for your time.

  Kind regards

  Ferran

  If you delete the archivelogs that have not been funded until you lose the ability to recover your database using incremental backups hot. When you make a hot backup, you'll need archivelogs to recover data files to recover the database in a consistent state. As long as you have archivelogs in any backupset should not be a problem. Archivelogs are always in their own backupset. You can use additional settings when you perform the backup of the archivelogs, such as 'no saved' or 'skip inaccessible', in order to avoid the mistakes of rman backup.

• Why RMAN backup tablespace UNDO?

  DB version: 11.2.0.4

  OS: Oracle Linux 6.4

  I found the following log RMAN backup Level0. Is the UNDO data in the tablespace, undo being saved really useful during the restoration?

  If the UNDO data are not used for recovery, then these data impossible recreated duing ALTER DATABASE OPEN files just like the REDO Log files and Temp tablespace?

  Enter a number of file datafile = name=+STG_DATA/ctgsprd/datafile/undotbs1_5.dbf 00024

  ch04 chain: total departure from 1 to 30 - SEP-2014 00:59:18

  channel ch10: finished piece 1 to 30 - SEP-2014 01:01:03

  piece handle = STGlv0_23191_1_20140710 tag = comment STG_BK_LEVEL0_140709 = Version of the API 2.0, MMS Version 1.1.1.0

  channel ch10: complete set of backups, time: 00:41:21

  channel ch10: start the incremental level 0 datafile backup set

  channel ch10: specification-datafile in the backup set (s)

  Enter a number of file datafile = name=+STG_DATA/ctgsprd/datafile/undotbs2_2.dbf 00025

  channel ch10: total departure from 1 to 30 - SEP-2014 01:01:03

  channel ch11: finished piece 1 to 30 - SEP-2014 01:01:48

  piece handle = STGlv0_23201_1_20140710 tag = comment STG_BK_LEVEL0_140709 = Version of the API 2.0, MMS Version 1.1.1.0

  channel ch11: complete set of backups, time: 00:23:18

  channel ch11: start the incremental level 0 datafile backup set

  channel ch11: specification-datafile in the backup set (s)

  Enter a number of file datafile = name=+STG_DATA/ctgsprd/datafile/undotbs2_3.dbf 00026

  You must include the UNDO Tablespace in backup. You NEED restored and used in the database to recover.

  At any time, there will be transactions not yet validated.  The CANCELLATION option maintains this information.   The open air after a recovery must be able to restore uncommitted operations and it must be able to read the CANCELLATION.

  Hemant K Collette

• RMAN backup disrupted because of failure

  DB version: 11.2.0.2
  Platform: Sun solaris 5.10
  
  During the race

  backup database plus archivelog;

  our server got DB decommissioned due to a power failure.
  
  In the log file, I see that after all the data files are listed as «enter a file datafile = xxx "...»
  We got the message 'done' as

  channel ch00: starting piece 1 at 13-MAR-12
  channel ch00: finished piece 1 at 13-MAR-12

  So, this means that a level 0 DB Backup is available. Right?
  It looks like all newspaper Archives are saved, then RMAN successfully has the backup of all data files, while he was trying to backup logs arch created after the full backup, then the power went off. Am I wrong?
  
  These are the shortcuts out of the log RMAN backup
  

  Starting backup at 13-MAR-12
  current log archived
  channel ch00: starting archived log backup set
  channel ch00: specifying archived log(s) in backup set
  input archived log thread=1 sequence=5104 RECID=2944 STAMP=777804213
  input archived log thread=1 sequence=5105 RECID=2947 STAMP=777806830
  input archived log thread=1 sequence=5106 RECID=2950 STAMP=777809240
  .
  .
  .
  .
  .
  
  channel ch00: starting piece 1 at 13-MAR-12
  channel ch00: finished piece 1 at 13-MAR-12
  piece handle=rman_ORCL_LEVEL0_FULL_5an5pu3m_1_1_777844854.rmbk tag=ORCL1_LEVEL0_FULL comment=API Version 2.0,MMS Version 5.0.0.0
  channel ch00: backup set complete, elapsed time: 00:15:45
  channel ch00: deleting archived log(s)
  archived log file name=+DG_ARCH/orcl_arch/orcl_5104_1_769896013.arc RECID=2944 STAMP=777804213
  archived log file name=+DG_ARCH/orcl_arch/orcl_5105_1_769896013.arc RECID=2947 STAMP=777806830
  archived log file name=+DG_ARCH/orcl_arch/orcl_5106_1_769896013.arc RECID=2950 STAMP=777809240
  .
  .
  .
  .
  
  Finished backup at 13-MAR-12
  
  Starting backup at 13-MAR-12
  channel ch00: starting incremental level 0 datafile backup set
  channel ch00: specifying datafile(s) in backup set
  input datafile file number=00006 name=+DG1/gridxxx/datafile/data_01_01.dbf
  input datafile file number=00010 name=+DG1/gridxxx/datafile/data_01_04.dbf
  input datafile file number=00013 name=+DG1/gridxxx/datafile/data_01_07.dbf
  input datafile file number=00025 name=+DG3/gridxxx/datafile/data_03_05.dbf
  input datafile file number=00028 name=+DG4/gridxxx/datafile/data_04_01.dbf
  .
  .
  .
  .
  .
  input datafile file number=00031 name=+DG4/gridxxx/datafile/data_04_04.dbf
  channel ch00: starting piece 1 at 13-MAR-12
  channel ch00: finished piece 1 at 13-MAR-12
  piece handle=rman_ORCL_LEVEL0_FULL_5bn5pv1l_1_1_777845813.rmbk tag=ORCL1_LEVEL0_FULL comment=API Version 2.0,MMS Version 5.0.0.0
  channel ch00: backup set complete, elapsed time: 04:29:35
  Finished backup at 13-MAR-12
  
  Starting backup at 13-MAR-12
  current log archived
  channel ch00: starting archived log backup set
  channel ch00: specifying archived log(s) in backup set
  input archived log thread=1 sequence=5132 RECID=3008 STAMP=777845828
  input archived log thread=1 sequence=5133 RECID=3011 STAMP=777846764
  input archived log thread=1 sequence=5134 RECID=3014 STAMP=777847595
  input archived log thread=2 sequence=2595 RECID=3007 STAMP=777845618
  input archived log thread=2 sequence=2596 RECID=3009 STAMP=777845834
  input archived log thread=2 sequence=2597 RECID=3010 STAMP=777846245
  input archived log thread=2 sequence=2598 RECID=3012 STAMP=777847027
  input archived log thread=2 sequence=2599 RECID=3013 STAMP=777847590
  channel ch00: starting piece 1 at 13-MAR-12
  
  ---- Power outage at this point

  Hello

  So, this means that a level 0 DB Backup is available. Right?

  Yes you are right that this db of level 0 backup is available.

  It looks like all newspaper Archives are saved, then RMAN successfully has the backup of all data files, while he was trying to backup logs arch created after the full backup, then the power went off. Am I wrong?

  It seems that all archive logs are backed up, all the data files are saved. Archive logs generated during the full backup had begun, but it is not finished.

  Query the status column in V$ RMAN_BACKUP_JOB_DETAILS views to see accurate results.

  Talip Hakan Öztürk
  http://taliphakanozturken.WordPress.com/

• RAC RMAN backup

  Hello
  
  DB is 10.2.0.4 OS = BSG (CARS with 2 nodes BD01, db02). Here are the types of automated RMAN backups taken on db01.
  
  -OCR
  -Voting record
  -Talespaces Snapshot
  -Archivelog (hourly)
  -Backup incremental level 0 (SUNDAY)
  -backup incremental level 1 (Mon - Sat)
  -Automatic backup of the control file and SPFILE (CONTROLFILE AUTOBACKUP ON)
  
  Two big questions please. First of all, are these types of backups/backup are enough to RESTORE FULL speaking of RMAN backup on a RAC environment with 2 nodes? Otherwise please suggest what I need to backup?
  
  Second, home backup location is /rman that I can see on db01 ONLY. This directory of /rman that I don't see on db02. My question is what db02 failure can I restore from directory /rman? or do I need to automate the backup also schedules on db02 separately?
  

  [root@db01~]# df -h
  Filesystem            Size  Used Avail Use% Mounted on
  /dev/mapper/VolGroup00-LogVol00
                        3.9G  2.9G  814M  79% /
  /dev/sda3             190M   34M  147M  19% /boot
  tmpfs                  16G     0   16G   0% /dev/shm
  /dev/mapper/VolGroup00-LogVol05
                        3.9G  137M  3.6G   4% /home
  /dev/mapper/VolGroup00-LogVol03
                        3.9G  225M  3.5G   6% /tmp
  /dev/mapper/VolGroup00-LogVol02
                        7.8G  3.7G  3.8G  50% /usr
  /dev/mapper/VolGroup00-LogVol04
                        3.9G  379M  3.4G  11% /var
  /dev/mapper/VolGroup00-ORACLE_BASE
                         12G  8.7G  2.6G  78% /oracle
  10.10.28.140:/vol/px4cinconso
                         40G  1.4G   39G   4% /inconso_px
  /dev/mapper/36001ec9000d5ea810000061349015d98
                        1.3T  551G  665G  46% /rman

  [root@db02~]# df -h
  Filesystem            Size  Used Avail Use% Mounted on
  /dev/mapper/VolGroup00-LogVol00
                        3.9G  887M  2.9G  24% /
  /dev/sda3             190M   34M  147M  19% /boot
  tmpfs                  16G     0   16G   0% /dev/shm
  /dev/mapper/VolGroup00-LogVol05
                        3.9G  137M  3.6G   4% /home
  /dev/mapper/VolGroup00-LogVol03
                        3.9G  261M  3.5G   7% /tmp
  /dev/mapper/VolGroup00-LogVol02
                        7.8G  3.7G  3.8G  50% /usr
  /dev/mapper/VolGroup00-LogVol04
                        3.9G  355M  3.4G  10% /var
  /dev/mapper/VolGroup00-ORACLE_BASE
                         12G  6.5G  4.8G  58% /oracle
  10.10.28.140:/vol/px4cinconso
                         40G  1.4G   39G   4% /inconso_px

  [oracle@db01~]$ rman target /
  
  Recovery Manager: Release 10.2.0.5.0 - Production on Fri Feb 24 11:49:59 2012
  
  Copyright (c) 1982, 2007, Oracle.  All rights reserved.
  
  connected to target database: F1 (DBID=1245145263)
  
  RMAN> show all;
  
  using target database control file instead of recovery catalog
  RMAN configuration parameters are:
  CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 28 DAYS;
  CONFIGURE BACKUP OPTIMIZATION ON;
  CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
  CONFIGURE CONTROLFILE AUTOBACKUP ON;
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rman/f1/fullbackup/%F';
  CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1;
  CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
  CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
  CONFIGURE MAXSETSIZE TO UNLIMITED; # default
  CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
  CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
  CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
  CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/product/10.2.0/db/dbs/snapcf_f11.f'; # default

  # Script for backup
  
  level0 ()
  run {
    allocate channel c1 type disk  maxpiecesize 2000M format '/rman/$ORACLE_SID/fullbackup/$ORACLE_SID-data-%U-%t';
    allocate channel c2 type disk  maxpiecesize 2000M format '/rman/$ORACLE_SID/archive/$ORACLE_SID-arch-%U-%t';
    backup incremental level 0 tag = weeklyfull database channel c1 
    plus archivelog tag = ARCH_$TODAY delete all input channel c2;
    release channel c1;
    release channel c2;
  }
  
  run {
    allocate channel c1 type disk;
    delete noprompt obsolete;
    release channel c1;
  }

  Bundle of thanks.
  
  Kind regards
  
  Published by: 910385 on February 24, 2012 03:00

  Hi 910385,
  The error on the node db02

  ORA-19504: cannot create the file ' / rman/fp1/backup/c-1245145263-20120210-11.

  is caused by your installation.
  You have a /rman of mount point visible only on the node db01.
  The controlfile autobackup setting triggers the creation of a backup of the controlfile:
  -during the rman backup (this seems to work only on db01)
  -in the case of a structural change in the database (eg. Adding a data file).
  Sessions to make a structural change can be connected to one of your two instances, but the instance on db02 cannot create controlfile autobackup in /rman.
  You must change the configuration and put the backup on a shared disk that is seen by the two systems.
  Strangely, you have a shared file system:

  10.10.28.140:/vol/px4cinconso 40G 1.4 G 39G 4% /inconso_px

  Better would be to make a second for rman...
  Kind regards
  Tycho

• RMAN backup doubt?

  Hello
  Our of is an ERP instance single node R12.0.6 with Oracle database 10g on AIX server. I take daily RMAN incremental backup, Script is the following:
  RUN
  {
  TAG DATABASE INCREMENTAL LEVEL 1 = "XXX_BACKUP_INCR1";
  }
  EXIT;
  Archive log backup will not take place. Is it necessary to have the backup of the journal of the Archives? Or do I need to keep logs of archiving or not?
  
  Concerning

  If you have level 1 and level 0 backups, you need only archived recovery logs that are generated after the level 1 backup.

  RMAN uses incremental backups during recovery instead of using archived redo log files, you have to save all archived files redo log generated during the backup procedure

  Kamran Agayev a.
  Oracle ACE
  - - - - - - - - - - - - - - - - - - - - -
  My video tutorials of Oracle - http://kamranagayev.wordpress.com/oracle-video-tutorials/

• RMAN backup and cross-checking script

  Hello
  
  I just joined a new company this week. As would any s/n, I was going just through the RMAN backup scripts used in the new environment.
  Here we run weekly RMAN backup complete for some of the databases that I am responsible for managing. The script and schedules are as follows.
  
  Every Sunday from 21:00, we organize a weekly job overlap
  
  Connect target username/pwd@DBNAME
  Connect catalog username/pwd@DBNAME
  
  Run {}
  CROSS-CHECKING OF BACKUP;
  DUPLICATION OF COPY;
  OVERLAP BACKUPSET;
  OVERLAP ARCHIVELOG ALL;
  DELETE NOPROMPT OBSOLETE;
  }
  
  Every Sunday from 9:30, we run the RMAN backup command which is
  
  Connect target username/pwd@DBNAME
  Connect catalog username/pwd@DBNAME
  
  run
  {
  CONFIGURE RETENTION POLICY TO RECOVERY OF 7-DAY WINDOW;
  SQL 'alter system archive log current';
  backup as backupset database include current controlfile;
  SQL 'alter system archive log current';
  ARCHIVELOG BACKUP of time ' SYSDATE-8';
  DELETE ARCHIVELOG ALL COMPLETED BEFORE ' SYSDATE-15';
  }
  
  
  A database that I will handle has been set up just over a week before I join.
  28 FEV 21:00 - no set of backup/copy/backup of overlap. I hope it will be cuts across all archive logs available in the database. No obsolete backup/copy/backup/archivelogs to remove.
  28 FEV 21:30 - sets the retention policy at 7 days, full backup of database backup and backup all archivelogs (sysdate-8). No newspaper archive to remove the database was created (migrated) less than 15 days back.
  
  7 March 21:00 - contre-vérifie the backupset (taking the 28 fev 21:30). No backup/copy of overlap.
  Question 1: Is there a backup obsolete here to delete?
  Own thought: Recovery window is 7 days. RMAN needs a backup in order to recover the database in any time-7 days to the present time (7 March 21:00 - 7 days = 28 fev 21:00). No obsolete backup to delete.
  
  7 March 21:30 - full database backup and fails to save all logs archiving (sysdate-8). No space in the Flash recovery disk group. As the archivelog backup failed and RMAN complete, it has not removed the archivelogs ' sysdate-15'.
  
  Backup is running again on 14 March. Of course, it will fail because there is no enough space in the Group of recovery disks.
  
  Future: I'm confused
  March 14, 21:00: contre-vérifie the backupset (supported March February 21:30). No backup/copy of overlap.
  Question 2: How do I know what is here obsolete? From the window of 7 days recovery, 14 March 21:00-7 days is March 7, 21:00. Last backup was taken on March 7, 21:30.
  To get back to 21:00, RMAN makes keep the backup of 28 March?... Does this mean whenever I'll have copies of backup 3?...
  
  14 March 21:30 - backup database... Log Archive backup will fail because there is no space. (I think to make a compressed backup).
  
  Question 3: How those wise commands?
  ARCHIVELOG BACKUP of time ' SYSDATE-8';
  DELETE ARCHIVELOG ALL COMPLETED BEFORE ' SYSDATE-15';
  
  If I take a successful backup of the archivelogs sysdate-8, why I need to keep the archivelogs before that? What could be the reason the previous DBA kept DELETE ARCHIVELOG COMPLETED BEFORE ANY 'SYSDATE-15 '; Rather than give DELETE ARCHIVELOG FINISHED FIRST and FOREMOST ' SYSDATE-8 "?
  
  Thanks in advance for your help.
  
  Published by: user8907052 on March 11, 2010 12:10

  If your database to 9i and above, then you don't need to pass - sql 'alter system archive log current;' before you perform the backup as RMAN automatically archives the log during recovery.

• RMAN backup restore a band

  Hello gurus
  
  We have lvl0 RMAN backup restored to a band, but a few reasons that we couldn't apply recovery on it. Verification of the information contained in the controlfile, he identified the file system only and no other files. So we recreated the controlfile and decided to recover using backup controlfile (up to cancel or to change or until). However, to my surprise, when I listed the columns checkpointchange # and checkpoint_time v$ datafile_header, I found the difference in time stamps ranging from 24 hours - including menat we had to apply 24 hrs of archiving to bring dbfs all in a consistent state (before it has allowed us to open the db) - well, it worked this way.
  
  My question is that if I trigger a lvl0 RMAN backup to say 16:00 July 27 and ends at 16:00 on 28 July (as I am directly pushing around 1 TB of data on tapes) - what is the timestamp of the coherence of this backup. In other words, there is this backup to restore from 16:00 July 27? Or it is only available for a restore from 16:00 28 July and later...?
  
  Is it not that RMAN works at the block level and when I start a backup should give me all the dbf than timestamp... ?
  
  Enjoy your entries and comments.

  When you take an online backup with RMAN, the backup of data files is always inconsistent because they have logs archived redo generated during the backup to match: http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/intro005.htm#sthref70.

  A full online backup can only be used to restore the database to a point in time begins after the end of backup: If a backup starts at 16:00 on 27 July and ends at 16:00 on 28 July, you can use it to restore the database to a point in time after 28 - DEC 16:00.

• RMAN - backup on FRA and somewhere else

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

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

• Fractured block found during the backup of the data file

  Hello
  
  Version: 10.2.0.3
  
  I take backups RMAN and export of db every night. The following error is recorded in the file alertlog while taking rman full backup. Also, the backup is very slow and it worked at 18hrs now (200 GB db size). Could someone please explain this to me that this error on and the action to take to solve this problem? Thank you
  
  Kill Mar 3 20:21:52 2009
  A hexadecimal dump (file 16, block 490151) in file /opt/oracle/admin/hol/udump/holiday_ora_11507.trc trace
  Corrupt block relative s/n: 0x04077aa7 (16, block 490151 file)
  Fractured block found during the backup of the data file
  Bad block data:
  type: 2 format: 2 rdba: 0x04077aa7
  last change the SNA: following 0x0013.830b4809: 0 x 4 flg: 0x04
  spare1: 0 x 0 spare2: 0 x 0 spare3: 0x0
  consistency in tail value: 0 x 10340201
  check the value in the block header: 0x7e2e
  checksum calculated block: 0 x 361
  Review of blocknum = 490151, file=/opt/oracle/oradata/hol/undotbs03.dbf. found valid data

  The problem may occur when the data being backed up file is simultaneously and widely used. It does not necessarily mean there is really block corruption. And in your case it seems that all is well:

  Review of blocknum = 490151, file=/opt/oracle/oradata/hol/undotbs03.dbf. found valid data

  On metalink:

  A broken block Messages in the Alert.log during RMAN of Datafile backup
  DOC - ID: 199933.1

  Werner

• Unable to take backup on Windows 7 get error code 0 x 81000019 and message backup Windows found errors on the media during a backup on it and can't use it for additional backups.

  Original title: backup Windows found errors on the media during a backup.

  original title: backup errors

  Whenever I try to do my monthly backup I get the following messages

  Backup Windows found errors on the media during a backup on it and can not use it for additional backups.

  Pleas write the following label on a blank media and insert it into D: /.

  I did and then he asked me to get in shape, I say OK and I get the same message on the media errors and I put another disc and get the same problems again. I can't find out what the problem is, what can I do to fix this problem and get a new backup?

  I now have an error 0 x 81000019

  Hello

  You did changes to the computer before the show?

  Method 1: Check if the shadow copy volume is running
  (a) click Start.
  (b) in the search box, type Services.msc.
  shadow copy Volume c) right-click and go to properties.
  (d) select Auto (Delayed) in the start menu type in the menu drop-down.

  Method 2: Clean boot
  When the computer starts to boot, programs non-Microsoft will not be started and would avoid any interruption of their share.

  How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7
  http://support.microsoft.com/kb/929135.

  Note: Once you are done with the boot, follow step 7 of article to reset your computer to normal startup.

  Method 3:

  Check all your drives to NTFS.

  This problem may occur if the drive is not NTFS format.

  Please follow the steps mentioned below to convert the reader:

  Using the Convert command

  1. click on the "Start" button, click "all programs" and click on "Accessories".

  2. right click on "command prompt" and click "run as administrator".

  3. in the window "Administrator: command prompt", type the following command and press ENTER.

  CONVERT %Drive% letter: / FS: NTFS

  letter of %Drive% is the driver that you want to convert. For example, type the following command to convert drive F to NTFS:

  CONVERT F:/FS: NTFS

  4. when the following message appears in the command prompt window, type the volume label of the drive that you are converting, and then press ENTER:

  The type of the file system is FAT.

  Enter the name of the current volume of reader letter %Drive%:

  Type any string of characters for the Volume name. If you simply press ENTER, it will affect 'Local disk' as the default Volume name.

  5. when the conversion to NTFS is complete, the following line appears in the command prompt window:

  "Complete conversion".

  6. restart the computer and check the result.

  Hope this information is useful.

• Import of schemas and tables of RMAN backup

  Hi all

  I have here are 3 requirements:

  (1) is it possible that I can import a single table using RMAN backup, because I have no more than one day of EXPDP dump file and the requirement is to store the data of three days.

  (2) is it possible that I can import a single SCHEMA using RMAN backup, because I have no more than one day of EXPDP dump file and the requirement is to store the data of three days.

  (3) can I import a package from the RMAN backup?

  I have incremental backup of level 1 and level 0.

  My database is 11.2.0.3

  Thank you and best regards,

  Mukesh

  Hi Mukesh,

  All of your needs can be met with output up to 11g using RMAN database, but beyond of 12 c, you can restore a single table RMAN backup (RMAN BACK TABLE new feature to the 12 c (Doc ID 1521524.1) Oracle database). For your condition impdp/expdp is the best Utilities option until oracle provided up to version 11 g.

  I hope this helps.

  Kind regards