RMAN validate

Similar Questions

• RMAN validate in Noarchive mode - is no longer available in 12 c?

  We conducted a weekly working on our bodies to detect corruption. A simple RMAN "check logical backup validate database;"

  We have a few instances that are running in NOARCHIVE mode. As we were moving from 11G to 12 c NOARCHIVE instances jobs were failing.

  RMAN > check logical backup validate database.

  2 > output

  From backup 5 October 15

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

  allocated channel: ORA_DISK_1

  channel ORA_DISK_1: SID = 800 type device = DISK

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

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

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

  RMAN-03002: failure of the command to backup to 10/05/2015 05:00:06

  RMAN-06149: cannot BACKUP of DATABASE in NOARCHIVELOG mode

  Complete recovery manager.

  
  

  Are we on this GROUND? Is there no way less of 12 c to validate a database in NOARCHIVE mode?

  Guys...

  This is a bug!

  DOC - ID 21132367.8

  If the necessary patch, bug 21132367 , you may need to create a SR.

  Thank you

• Validate the recovery area / files results in RMAN-00600: internal error

  Dear members,
  
  I did experience (specifically RMAN) with Oracle 11.1.0.7 on instance AWS (amazon delegating thingy).
  

  SQL> select * from v$version;
  
  Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
  PL/SQL Release 11.1.0.7.0 - Production
  CORE    11.1.0.7.0      Production
  TNS for Linux: Version 11.1.0.7.0 - Production
  NLSRTL Version 11.1.0.7.0 - Production

  Database instance works fine, so far.
  However when I try to VALIDATE the recovery or file BOX, she translates RMAN-0600 as follows...

  RMAN> validate recovery area;
  
  Starting validate at 15-JUN-12
  using channel ORA_DISK_1
  RMAN-00571: ===========================================================
  RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
  RMAN-00571: ===========================================================
  RMAN-03002: failure of validate command at 06/15/2012 19:00:33
  RMAN-00600: internal error, arguments [8708] [] [] [] []

  Any help is greatly appreciated.
  Sincerely,
  Jennifer B.
  
  PS:
  All others to VALIDATE the options work great.
  One runs in such situation? I searched for his MOS, Google and this forum but nothing helped :-(

  Hello;

  I'm pretty sure it's a bug.

  It is an Oracle noted that while not an exact match is very, very close.

  VALIDATE ARCHIVELOG ALL fails with RMAN-00600 [8708] [974813.1 ID]

  Best regards

  mseberg

• validate the rman backups

  Hello
  
  Oracle 9.2.0.1
  backup incremental cumalative RMAN
  
  Hello
  
  I do backups incremental cumalative. Full level 0 Friday, level 1 differential made Mon. - game.
  
  I noticed that if I run a RESTORE DATABASE VALIDATE command, it checks / uses all the pieces that are part of FULL LEVEL 0 only. But it doesn't tell me whether the incremental backup items created are good or not.
  
  How (without actually restoring to test the server) can test/validate until the last daily incremental backup?
  
  J

  VALIDATE RESTORE them will do only full backups, LEVEL 0 backups, controlfiles, spfile, copies of data file and the archivelogs. However, you can VALIDATE a LEVEL 1 backupset with simply:

  RMAN> VALIDATE BACKUPSET ;
  

• RMAN block recovery

  Hello

  I have an Oracle 11 g R2 server and the journal of alerts reported the following

  ORA-01578: ORACLE data block corrupted (file # xx, block # xxx)

  
  

  Yes, I didRMAN> validate check logical database;

  And after that on checkingV$ database_block_corruption I found 3 block are corrupt, all 3 are indexes of the index table_space segment_type.

  
  

  Please let me know what would be the best way to recover the corrupt blocks

  Will,RMAN> recover corruption list;  repair the block corruption

  
  

  
  

  Another concern is that the backup of the database doesn't do 'check logical' before doing the backup. Does it mean that the recovery from backup might not work ?

  
  

  Thanks


  No, you need to do both.

  The first command handles the bad or blocks

  Best regards

  mseberg

• validate backupset

  Hi all

  I'm using Oracle 11 g 2.

  I take the backup of my database as below:

  database of the 'LEV0' tag drive backup incremental level 0 appliance type include current controlfile more archivelog tag 'LEV0' not backed up 2 times

  To make another copy of the backups that I am:

  backup format tag 'LEV0' backupset "backup_location/destination /".

  The statements above generate the same key backupset at two different location the first disk ASM + FRA and the second group to ' backup_location/destination / ".

  Let's say that the commands above created backup sets as below:

  Backup the key value in the key to backup location

  19173                         37470                                      +FRA....

  19173 37471 "backup_location/destination /"

  When I am trying to validate the backup as set below:

  validate backupset 19173.

  It's playback of + FRA or "/ destination/backup_location" (randomly sometimes it reads the backup sets of + FRA sometimes "/ destination/backup_location ' )

  My question is possible to force the "validate backupset 19173;" read + FRA only during the validation of the backupsets?

  Kind regards

  The exemplary value 15264 defined backup #1 backup

  Time of accomplishment of the time Type compressed device Tag

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

  00:19:04 DISC 17 JUNE 15 NO INCR_LV1_1506170100

  The list of items to backup to the backup set 15264 copy #1

  Name of the Key BP Pc # status element

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

  22580 +FRA/DB_NAME/backupset/2015_06_17/nnndn1_incr_lv1_1506170100_0.2699.882579633 AVAILABLE 1

  Backup the exemplary value n ° 2 defined backup 15264

  Time of accomplishment of the time Type compressed device Tag

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

  00:19:04 DISC 17 JUNE 15 NO INCR_LV1_1506170100

  The list of items to backup to the backup set 15264 copy #2

  Name of the Key BP Pc # status element

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

  22585 1 AVAILABLE/location_on_disk/INCR_LV1_1506170100_t7q9m65e_1_2

  You can also change COPY #2 unavailable to force rman validate the first copy.

  RMAN > change backuppiece 22585 unavailable;

  RMAN > validate backupset 15264.

  RMAN > change backuppiece 22585 available;

  If you don't want to validate all FRA, you can change only the backupieces filtering by tag.

  Select "change backuppiece ' |" RECID: ' unavailable;' -' available ';

  cmd to v$ element_sauvegarde

  where copy # 1

  and IS_RECOVERY_DEST_FILE = 'NO '.

  and tag = "INCR_LV1_1506170100."

  - AND COMPLETION_TIME FROM SYSDATE-1 TO SYSDATE"

  ;

  PS: Files in the recovery area flash cannot be marked as UNAVAILABLE. Because that where clause have ' IS_RECOVERY_DEST_FILE = 'NO "".

• 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...

• STATUS = FAILURE FOR DEVICE_TYPE = SBT_TAPE

  Hi all

  Please see the output of the SQL statement that indicates the size of each backupset in the last 7 days of oracle database machine: here STATUS = FAILURE are rman backups triggered from Netvault Dell backup server. Those with STATUS = COMPLETED is the backup manually from the machines of oracle rman database command prompt. The configuration of the Oracle RMAN database server is also attached.

  Can you tell why the STATUS = FAILURE comes for DEVICE_TYPE = SBT_TAPE?

  
  

  
  

  Hello

  You can check your backups on tape of rman with:

  RMAN > validate backupset 42,30,22,19,16,13,10,7,4;  (failure of 42,30,22,19,16,13,10,7,4 are backupset_keys your output.png file.)

  http://docs.Oracle.com/CD/B28359_01/backup.111/b28273/rcmsynta053.htm#RCMRF162

  Concerning

• ORA-19599: block number 45289 is corrupt in the backup piece

  OS: RHEL 5.7 64bits

  Database: 11.1.0.7

  Hi all

  I have problems to restore RMAN backup on test computer. The restore command is sick of following error message:

  ORA-19599: block number 45289 is corrupted in the backup/oracle/clone/DEV/rman/RMAN_ERP_20150227_15927509_1 item

  I already checked the piece back on prod and it seems OK:

  RMAN > validate backupset 3840;

  From post on 27 February 15

  using channel ORA_DISK_1

  using the ORA_DISK_2 channel

  channel ORA_DISK_1: starting from the validation of the data file backup set

  channel ORA_DISK_1: reading of the backup/oradata/ERP/RMAN_BACKUP/RMAN_ERP_20150227_15927509_1 element

  channel ORA_DISK_1: piece handle = / oradata/ERP/RMAN_BACKUP/RMAN_ERP_20150227_15927509_1 tag = TAG20150227T040007

  channel ORA_DISK_1: restored the backup part 1

  channel ORA_DISK_1: validation complete, duration: 00:02:45

  Finished post on 27 February 15

  Restore validate command also fails on the test machine:

  RMAN > restore database validation verification logic;

  From restoration to 27 February 15

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

  allocated channel: ORA_DISK_1

  channel ORA_DISK_1: SID = 779 type device = DISK

  allocated channel: ORA_DISK_2

  channel ORA_DISK_2: SID = 778 type device = DISK

  channel ORA_DISK_1: sweeping datafile copy /oracle/DEV/db/apps_st/data/a_ref03.dbf

  channel ORA_DISK_2: from the validation of the data file backup set

  channel ORA_DISK_2: reading of the backup/oracle/clone/DEV/rman/RMAN_ERP_20150227_15927510_1 element

  channel ORA_DISK_1: sweeping datafile copy /oracle/DEV/db/apps_st/data/a_txn_data05.dbf

  channel ORA_DISK_2: ORA-19870: error when restoring backup/oracle/clone/DEV/rman/RMAN_ERP_20150227_15927510_1 piece

  ORA-19599: block number 233296 is corrupted in the backup/oracle/clone/DEV/rman/RMAN_ERP_20150227_15927510_1 item

  channel ORA_DISK_2: scanning datafile copy /oracle/DEV/db/apps_st/data/a_int01.dbf

  channel ORA_DISK_1: starting from the validation of the data file backup set

  channel ORA_DISK_1: reading of the backup/oracle/clone/DEV/rman/RMAN_ERP_20150227_15927509_1 element

  channel ORA_DISK_1: ORA-19870: error when restoring backup/oracle/clone/DEV/rman/RMAN_ERP_20150227_15927509_1 piece

  ORA-19599: block number 45289 is corrupted in the backup/oracle/clone/DEV/rman/RMAN_ERP_20150227_15927509_1 item

  switch to the previous backup

  My confusion is why validate backupset succeeds the prod and the same backupset presents corruption block during test.

  Kind regards

  Vinod

  Maybe the backuppiece has been altered in the transfer to the DEV machine?  Run a checksum on the backuppiece on both machines and compare.

  Hemant K Collette

• Error ORA-01115 creating the materialized view

  Hi friends,

  When I create a materialized view it by throwing some error

  CREATE THE PNR_RES_MV MATERIALIZED VIEW
  TABLESPACE FAS
  NOCACHE
  LOGGING
  NOCOMPRESS
  NOPARALLEL
  IMMEDIATE CONSTRUCTION
  REFRESH THE STRENGTH TO DEMAND
  WITH THE PRIMARY KEY
  AS
  SELECT C_CREATION_DATE, C_PNR, B.CARRIER_CD1, B.CARRIER_CD2, B.CURRENT_STATUS_CD, A.CANCELLED_IND, A.BOOKING_OFFC_NMBR,-, B.LEG_NMBR, C_PAX_NMBR
  COUNT (CASE WHEN TRIM (B.CURRENT_STATUS_CD) = "HK" AND (TRIM (C_CHANGE_OR_CANCELL_IND) = "OR C_CHANGE_OR_CANCELL_IND IS NULL) THEN 1 OTHER TRAILING NULL) CONFIRMED_COUNT,.
  COUNT (CASE WHEN (B.CURRENT_STATUS_CD) TRIM = "HK" AND (TRIM (C_CHANGE_OR_CANCELL_IND) = "or C_CHANGE_OR_CANCELL_IND IS NULL) null THEN 1 OTHER END) cancELLED_COUNT
  OF PNR_RES_LEG_PAX_MV B, PNR_RES HAS
  WHERE A.PNR = B.PNR
  AND a.CREATION_DATE = b.CREATION_DATE
  - and A.BOOKING_OFFC_NMBR = '1F'
  - AND C_PNR = 'XE76V. '
  AND A.FILE_UPDATE_DATE. A.UPDATE_DATE IN (SELECT MAX (D.FILE_UPDATE_DATE |)) (UPDATE_DATE) OF PNR_RES D WHERE D.PNR = B.PNR AND D.CREATION_DATE = B.CREATION_DATE)
  GROUP OF C_CREATION_DATE, C_PNR, B.CARRIER_CD1, B.CARRIER_CD2, B.CURRENT_STATUS_CD, A.CANCELLED_IND, A.BOOKING_OFFC_NMBR;

  
  

  
  

  When executing it it gives this error

  
  

  ORA-01115: reading block IO file error 4 (block # 63757)
  ORA-01110: data file 4: ' D:\APP\IGT\ORADATA\ORCL\USERS01. DBF'
  ORA-27070: async read/write failed
  OSD-04006: ReadFile() failure, unable to read the file
  S/O-error: (27 OS) the drive cannot find the sector requested.

  
  

  
  

  And I checked through RMAN

  RMAN > validate the audit logic datafile 4;

  From post 11 March 14
  using the control file of the target instead of recovery catalog database
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: SID = 127 type device = DISK
  channel ORA_DISK_1: starting from the data file validation
  channel ORA_DISK_1: datafile (s) for specification validation
  Enter a number of file datafile = 00004 name = D:\APP\IGT\ORADATA\ORCL\USERS01. DBF
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03009: failure to validate the command channel ORA_DISK_1 11/03/2014 13:0
  04:12
  ORA-19501: read error on the file 'D:\APP\IGT\ORADATA\ORCL\USERS01. DBF', block numbe
  r 63745 (block size = 8192)
  ORA-27070: async read/write failed
  OSD-04016: error queuing an asynchronous i/o request.
  S/O-error: (27 OS) the drive cannot find the sector requested.

  
  

  
  

  Please suggest me what to do it is a mistake to associate related database or OS. DB version is - 11 GR 2

  
  

  Kind regards

  
  

  Arya
  

  
  

  This is the error message that you should focus:

  > O/S-error: (27 OS) the drive cannot find the sector requested.

  Run disk checker utilities, eventually the file system is damaged.

  Hemant K Collette

• ORA-19599: block number 1985 is corrupt in archived log + FG.

  Hi team,
  
  I couldn't take the RAC database archivelog backup. Please help me
  
  RMAN > VALIDATE the BACKUP DATABASE ARCHIVELOG ALL;
  
  From backup 24 March 13
  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=+DG1/kvxcprd/datafile/system.260.777756857
  input datafile fno = name=+DG1/kvxcprd/datafile/sysaux.268.777756857 00003
  input datafile fno = name=+DG1/kvxcprd/datafile/undotbs1.263.777756857 00002
  input datafile fno = 00005 name=+DG1/kvxcprd/datafile/undotbs2.264.777756983
  input datafile fno = name=+DG1/kvxcprd/datafile/users.267.777756857 00004
  channel ORA_DISK_1: complete set of backups, time: 00:00:25
  channel ORA_DISK_1: from archive newspaper backupset
  channel ORA_DISK_1: specification of archive log backup set
  archive log entry thread = 2 sequence 17 recid = 26 = 810915691 stamp =
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03009: failure of the backup command on the channel ORA_DISK_1 at 24/03/2013-14:37:11
  ORA-19599: block number 1985 is corrupted in +FG/kvxcprd/archivelog/2013_03_24/thread_2_seq_17.269.810915689 archived journal
  
  RMAN > backup archivelog all;
  
  From backup 24 March 13
  Current archived log
  using channel ORA_DISK_1
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the backup to 24/03/2013-14:39:52 command
  ORA-19563: file header validation failure
  
  Thank you and best regards,
  
  
  Published by: 995796 on March 24, 2013 02:26
  
  Published by: 995796 on March 24, 2013 02:27

  You must exclude this backup archivelog. Rename the archivelog (via asmcmd) and then run OVERLAP ARCHIVELOG ALL while Oracle would mark it as 'Out of date' when it does not find the archivelog. (You can also run an ARCHIVELOG DELETE or REMOVE the ARCHIVELOG EXPIRES to logically remove).

  You should document this archivelog missing so that any required later retrieval knows this archivelog isn't available, so a point in time to recover to any point of the last backup before this archivelog to a point in time of the archivelog or as the result of it would not be possible until the next backup.

  Needless to say, take a fresh database backup.

  Hemant K Collette

• segments of corrupt

  Hi all
  
  one of my blocks of database is damaged. While performing the check in rman validate we gave only datafile id and the id of the block.
  
  How we can find segments damaged with these details. Please let me know.
  
  database is 11 GR 2 on linux 5.5
  
  
  Thank you

  Is that what you are looking for?
  a8 col ownr format 'Owner' topic justifies c
  Collar type format a8 direction 'Type' justify trunc c
  Col name format a28 titled 'The Segment name' justify c
  exid Col. 990 title format "measure #" justify c
  justify position 9990 fiid col format "file #" c
  blid col 99990 title format "block #" justify c
  topic 'Blocks' of col blks format 999 990 justify c

  SQL> ed
  Wrote file afiedt.buf
  
    1  select
    2  owner ownr,
    3  segment_name name,
    4  segment_type type,
    5  extent_id exid,
    6  file_id fiid,
    7  block_id blid,
    8  blocks blks
    9  from
   10  dba_extents
   11  where
   12  file_id = &file_id
   13  and block_id=&block_id
   14  order by
   15* block_id
  SQL> /
  Enter value for file_id: 2
  old  12: file_id = &file_id
  new  12: file_id = 2
  Enter value for block_id: 80048
  old  13: and block_id=&block_id
  new  13: and block_id=80048
  
   Owner           Segment Name           Type   Extent# File# Block#  Blocks
  -------- ---------------------------- -------- ------- ----- ------ --------
  SYS      WRI$_ADV_MESSAGE_GROUPS_PK   INDEX          5     2  80048        8
  
  SQL>
  

  He invites starts and ID (you have) and will tell you the name of the segment (what you need).

  Get on the Internet but lack to copy the link.

  Concerning
  Girish Sharma

• How to check if my backups are usable?

  Dear friends,
  
  How will I know if my backups would be helpful when I anymore?
  
  In any case to test at least on a monthly basis?
  
  Any suggestions?

  user645399 wrote:
  Dear friends,

  How will I know if my backups would be helpful when I anymore?

  In any case to test at least on a monthly basis?

  Any suggestions?

  RMAN > validate database

  check

  http://download.Oracle.com/docs/CD/B28359_01/backup.111/b28270/rcmvalid.htm#i1031282

  Published by: CKPT on October 19, 2011 13:56

• DBVERIFY - given in bad block

  During RMAN validate the structure I noticed that I have a lot of files with the corruption of the data. Then, I run DBVERIFY and identify files and database objects. I know what to do with broken tables and indexes, but the 2 lines are strange for me:
  (1) object with the segment type 'TYPE2 CANCEL' on undo tablespace
  (2) block broken on data file user who is empty (without any object on it)
  
  What I eat sort of these bad blocks or leave without changes?
  
  My DB: 9i
  My OS: Linux x 32

  Ok thank you. So this bad empty block leave without doing anything? I ask because I do not know if Oracle making a few flag automatically or not. Flag means a space Oracle knows it's bad block and do not write something again in the future.

  If it's the bad block, then it is still impossible to write too...

• Test block corruptions of a large database

  Hello
  We intend to change our database to a new computer.
  Before using the new database, I want to clarify this new instance has no block corruption.
  I am looking for a way to detect corruptions of block on a large database size 2.5 to.
  Oracle version is 10.2.0.5 (ASM, RAC)
  System configuration: lcpu = 24 mem = Mo 127744
  Thanks in advance

  MetaLink Note 836658.1 could be very useful for you.
  In addition, rman complete the order, you can also use db check utility (dbv) to control the corruption of the block. In addition, you can use Rman validate by allocating multiple channels, which could make your check faster.