- Notes, cautions, and warnings
- Preface
- Introduction
- Installation
- Preparing to install the Avamar Plug-in for Oracle
- Installing, upgrading, and uninstalling the software on HP-UX
- Installing, upgrading, and uninstalling the software on IBM AIX
- Installing, upgrading, and uninstalling the software on Linux
- Installing, upgrading, and uninstalling the software on Solaris
- Installing, upgrading, and uninstalling the software on Windows
- Excluding Oracle directories from file system backups
- Oracle RAC Configuration
- High Availability Oracle Single-Instance Database Configuration
- Backup
- Restore and Recovery
- Backup and Restore with Oracle RMAN
- Preparing the system for RMAN backups and restores
- Specifying RMAN parameters to improve performance
- Backing up Oracle data with RMAN
- Restoring Oracle data with RMAN
- Supporting netbind flag in avoracle
- Using advanced restore commands
- Managing backup retention
- Allocating multiple channels
- Managing RMAN backups and restores through Avamar Administrator
- Plug-in Options
- Troubleshooting
- Backup and restore problems and solutions
- Avamar Administrator shows a completed RMAN backup or restore as still running
- avoracle Error <7936>: No valid targets found
- Activity monitor of RMAN backup shows an incorrect status of still running.
- Backups fail when backup copies is set to more than 1
- Log files for RMAN operations cannot be viewed from the Avamar Administrator if a custom var directory is used.
- Backups unavailable after registering secondary RAC node
- Cannot open file f_cache.dat error
- Cannot Sync error
- Failed RMAN restore of control file is reported as completed in Avamar Administrator
- Hot backup fails with Oracle not available error
- Level-1 backup of a large database fails with a snapview timeout
- ORA-19870: error while restoring backup piece
- ORA-25153: Temporary Tablespace is Empty
- ORA-27211: Failed to load Media Management Library
- Restore fails to complete successfully
- RMAN backup script fails with media management errors
- RMAN backup script fails with ORA-19511
- RMAN-06056: could not access datafile n error on AIX
- RMAN script fails with WriteFile failed error
- Time-out errors when using multiple RMAN channels
- Unable to process snapview workorder
- Unable to send CTL message
- The no_of_channels parameter no longer supported
- Hidden backups
- Configuration problems and solutions
- Avamar client and Avamar Plug-in for Oracle registration
- Bitwidth of Avamar Plug-in for Oracle and Oracle
- Cluster Configuration Tool fails to start
- Determining the version of Oracle
- Disk space for the /var/avamar directory
- Oracle RAC database failover
- Requirements for libobk_avamar.so and libobk_avamar.dll
- RMAN executable file and Oracle versions
- Stopping Avamar Administrator processes
- Unable to browse Oracle databases with Avamar Administrator
- Verifying the client and plug-in versions
- Backup and restore problems and solutions
- Glossary
Dell Avamar for Oracle 19.10 User Guide
Corrupt block recovery
The Avamar Plug-in for Oracle includes the Corrupt blocks option, which enables you to recover corrupt data blocks only and not the entire database. The Corrupt blocks option is an advanced option in the Restore Command Line Options dialog box.
To use the Corrupt blocks option, you must first configure the database to use checksums to verify data blocks. To enable this feature, set the initialization parameter, DB_BLOCK_CHECKSUM, to TYPICAL for the Oracle database. This setting enables RMAN to detect both physical and logical corruption:
- Physical corruption can occur because of defective memory boards, defective controllers, or broken sectors on a hard disk.
- Logical corruption can occur if the contents of a data block are logically inconsistent. Examples of logical corruption include corruption of a row piece or an index entry.
You can use the Corrupt blocks option while the database is open.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\