Get in touch: [email protected]

Category: RMAN Restore and Recovery

  • Create a Directory Object and Granting Access – External Tables

    First, create a directory object that points to the location of the file on disk: SQL> create directory example_dir as ‘/oradata/sales’; Grant READ and WRITE on the directory object to the user (your account or application account) that is accessing the directory object. SQL> grant read, write on directory example_dir to app_user; Create Table Then,…

    Read more...

  • External Table Types – External Tables

    We just discussed the SQL*Loader type of external tables, and that is what is used by default. However, there are other types of external tables that each has its own access drivers and helps you work with the different data types you might be using. The types of external tables are as follows: •     ORACLE_LOADER…

    Read more...

  • Flashback – RMAN Backups and Reporting

    Although the RECOVER TABLE command is a nice enhancement, I recommend that if you have an accidentally dropped table, you first explore using the recycle bin or Flashback Table to Before Drop feature to restore the table. Or, if the table was erroneously deleted from, then use the Flashback Table feature to restore the table…

    Read more...

  • Restoring to a Restore Point – RMAN Backups and Reporting

    There are two types of restore points: normal and guaranteed. The main difference between a guaranteed restore point and a normal restore point is that a guaranteed restore point is not eventually aged out of the control file; a guaranteed restore point will persist until you drop it. Guaranteed restore points do require an FRA.…

    Read more...

  • Performing Log Sequence–Based Recovery – RMAN Backups and Reporting

    Usually this type of incomplete database recovery is initiated because you have a missing or damaged archivelog file. If that is the case, you can recover only up to your last good archivelog file, because you cannot skip a missing archivelog. How you determine which archivelog file to restore up to (but not including) will…

    Read more...

  • Determining the Type of Incomplete Recovery – RMAN Backups and Reporting

    Time-based restore and recovery are commonly used when you know the approximate date and time to which you want to recover your database. For instance, you may know approximately the time you want to stop the recovery process, but not a particular SCN. Log sequence-based and cancel-based recovery work well in situations in which you…

    Read more...

  • Incomplete Recovery – RMAN Backups and Reporting

    The term incomplete database recovery means you cannot recover all committed transactions. Incomplete means you do not apply all redo to restore up to the point of the last committed transaction that occurred in your database. In other words, you are restoring and recovering to a point in time in the past. For this reason,…

    Read more...

  • Using an Autobackup – RMAN Backups and Reporting

    When you enable the autobackup of your control file and are using an FRA, restoring your control file is fairly simple. First, connect to your target database and then issue a STARTUP NOMOUNT command, followed by the RESTORE CONTROLFILE FROM AUTOBACKUP command, like this: $ rman target / RMAN> startup nomount; RMAN> restore controlfile from…

    Read more...

  • Restoring to a Nondefault Location – RMAN Backups and Reporting

    Use the SET ARCHIVELOG DESTINATION clause if you want to restore archivelog files to a location different from the default. The following example restores to the nondefault location /u01/archtemp. The option of the SET command must be executed from within an RMAN run{} block. run{set archivelog destination to ‘/u01/archtemp’; restore archivelog from sequence 8 force;}…

    Read more...

  • Restoring Archivelog Files – RMAN Backups and Reporting

    RMAN will automatically restore any archivelog files that it needs during a recovery process. You normally do not need to restore archivelog files manually. However, you may want to do so if any of the following situations apply: •     You need to restore archivelog files in anticipation of later performing a recovery; the idea is…

    Read more...