You can use this information to perform a block-level recovery (see Chapter 6 for more details). This view contains information on the file number, block number, and number of blocks affected. If RMAN detects any corrupt blocks, the V$DATABASE_BLOCK_CORRUPTION is populated. While connected as SYS to the root container, validate any associated pluggable databases: RMAN> validate pluggable database salespdb If you’re using the Oracle 12c pluggable database feature, you can validate specific databases within the container. RMAN> validate datafile 3 block 20 to 30 Here are a few more examples: RMAN> validate database skip offline You can specify that you also want to check for logical corruption by using the CHECK LOGICAL clause: RMAN> validate check logical database include current controlfile plus archivelog Under normal conditions the VALIDATE command only checks for physical corruption. You may want to combine all the prior integrity checks into one command, as shown: RMAN> validate database include current controlfile plus archivelog You can validate the archive redo log files, like so: RMAN> validate archivelog all You can also validate just the control file, as follows: RMAN> validate current controlfile For example, this command will validate all data files and the control files: RMAN> validate database The VALIDATE command can be used stand-alone to check for missing files or physical corruption in database data files, archive redo log files, control files, spfiles, and backup set pieces. The BACKUP.VALIDATE and RESTORE.VALIDATE commands are available in Oracle 10g and higher. Note The stand-alone VALIDATE command is available in Oracle 11g and higher.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |