RMAN, or Recovery Manager, is a solution that is fully integrated within the Oracle database that can perform a variety of backup-related activities. Within the capabilities of Oracle there’s two main backup strategies: RMAN and user-managed. Depending on the extent of corruption, some lesser app errors can be more or less fixed using some variation of a block media recovery. In the case of media corruption (also called physical corruption), it’s quite common for the entire block to not be recognized by the database at all, with the checksums that are not matching, the entire block containing zeroes, and so on.
#ORACLE DATABASE BACKUP AND RECOVERY SOFTWARE#
Because of that same reason, it’s not uncommon for companies to develop some sort of a disaster recovery program in an attempt to mitigate the potentially disastrous effects of a media failure, among other things (since media failures are known for paralyzing the entire storage device at once).Īpp errors are the result of a software malfunction, typically represented by a corrupt data block. It’s important to mention that media errors are something that can happen to any storage device in the first place. The appropriate measure in response to a media failure depends on the device type and the data type in question. Media failure is another error type, this one is mostly represented by some sort of a physical problem with a storage device that causes problems with read or write requests. Widespread damage, on the other hand, is the one that deletes massive amounts of data and needs to be countered as soon as possible to at least partially prevent a massive downtime for the entire database. Localized damage is something relatively insignificant that can be fixed with an accurate repair process. There are also two different scopes of the potential disaster – localized and widespread. This single error type is considered to be the biggest cause of the majority of database downtimes all over the world.
#ORACLE DATABASE BACKUP AND RECOVERY MANUAL#
User errors represent the possibility when, due to either the manual mistake or the error in the app logic, the specific part of the database is either changed or deleted incorrectly. While there are some possible exceptions, the majority of error cases that demand the data recovery process to be initiated can be attributed to one of the three error types: user errors, media failures, and app errors. Creating a physical backup of a database is the act of “backing up” said database. Unless specified otherwise, the majority of backup and recovery documentation refers to a physical backup as the “backup” term. These backups are often treated as a good supplement to the physical backups but are essentially useless without their counterpart. Logical backups are a copy of logical data within the database, such as stored procedures and tables. Physical backups typically include such file types as control files, data files, and archived redo logs. Physical backup is a copy of the physical files stored to use in case of an emergency. In the context of Oracle there are two main backup types – physical backup and logical backup. This also applies equally to Oracle backup and restore of course, and in today’s world having at least one backup of your database is practically a necessity if you don’t want to eventually lose everything because of a simple error or similar unfortunate accident.Ī backup is a copy of your data that can be used to reconstruct your original database’s contents. Typically, backup and recovery operations are regarded as one of the key pillars of data protection.
0 kommentar(er)
