- 3-13 Planning the Size of the Flash Recovery Area. - This chapter describes how to maintain the RMAN backup metadata, which is stored in the control file of the target database.. - Enter one of the options. - That you can repeat a portion of the code. - However, logical backups are for the most part beyond the scope of the backup and recovery documentation.. - A database's data is collectively stored in the datafiles that constitute each tablespace of the database. - The control file contains a crucial record of the physical structures of the database and their status. - Loss of the control file makes recovery from a data loss much more difficult.. - The preceding scenario outlined the basics of the restore-and-recovery process.. - Primary storage for RMAN repository information is in the control file of the production database. - Oracle Database Backup and Recovery Advanced User's Guide to learn how to use the flashback features of the Oracle database. - The state of the database (open, crashed, closed consistently, and so on). - The last backup of the control file and all the datafiles. - compromising the completeness of the redundancy set.. - If you are using a flash recovery area, use it as one of the archiving locations.. - The remainder of the database is intact, but all data in the affected files is lost.. - It is recommended that you take advantage of the flash recovery area to store as many backup and recovery-related fileas as possible, including disk backups and archived redo logs.. - on page 3-11 for more about the uses and benefits of the flash recovery area.. - You may want to keep a copy of the database for archival purposes.. - Of course, you can back up other parts of the database as well.. - The version and patch of the operating system. - The name of the database instance (SID). - The version and patch release of the Oracle database server. - Use of the flash recovery area is strongly recommended.. - The only permanent files (assuming these are configured to be stored in the recovery area) are multiplexed copies of the current control file and online redo logs. - Planning the Size of the Flash Recovery Area. - Ideally, the flash recovery area should be large enough to contain all of the following files:. - Initialization parameters can be specified by any of the following means:. - Include them initialization parameter file of the target database. - After you start SQL*Plus and connect to the database, set the size of the flash recovery area. - Set the location of the flash recovery area. - The database will no longer provide the space management features of the flash recovery area for the files stored in the old DB_RECOVERY_FILE_DEST location.. - You now have four backups of the datafile. - Maintain a multiplexed copy of the control file in the flash recovery area. - Maintain multiplexed copies of the online redo logs in the flash recovery area. - and the flash recovery area. - Another copy of the control file and online logs is created in the flash recovery area.. - No multiplexed copies of the online redo logs or control files are created in the flash recovery area.. - BACKUPSET option of the BACKUP command, in Oracle Database Recovery Manager Reference.. - Oracle Database Backup and Recovery Advanced User's Guide for a discussion of the various RMAN backup types. - A manual backup of the control file is not the same as a control file autobackup. - For any use of the BACKUP command that creates backupsets, you can take. - A level 1 incremental backup can be either of the following types:. - This example makes a level 0 incrementnal backup of the database:. - FOR RECOVER OF COPY WITH TAG form of the BACKUP command. - The effect of the script is as follows:. - UNTIL TIME statement applies the level 1 incremental from seven days ago to the copy of the database. - Make an incremental backup of the database to the flash recovery area.. - Disk Quota = Size of X copies of the database + size of Y days of archived redo logs. - Disk Quota = Size of 1 copy of the database. - Disk Quota = Size of 1 copy of the database + size of 8 days of archived logs. - Make a full backup of the database to the flash recovery area.. - Disk Quota = Size of X copies of the database + Size of 1 incremental backup. - FOR RECOVER OF COPY command makes a level 0 incremental backup of the database to the flash recovery area. - Execute each day of the week. - Table 4–4 describes how the contents of the flash recovery area and tape change as this script is run each day. - The elements of the strategy are as follows:. - A full backup of the database is taken to the flash recovery area once each week.. - determining your disk quota depends upon the frequency of backups of the flash recovery area to tape, as follows:. - Disk Quota = Size of 1 copies of the database + size of (Y+1) days of archived logs. - This command has no effect, because there is no level 0 backup of the database yet.. - Create level 0 backup as result of the BACKUP. - Flash recovery area contains the level 0 incremental backup of the database, to be rolled forward each week.. - Tape contains a backup of the level 0 incremental backup of the database.. - For example, enter any of the following commands:. - operation creates a new incarnation of the database. - Oracle Database Recovery Manager Reference for an explanation of the various columns in the LIST output. - What was the physical schema of the database at some previous time?. - When one copy of the control file is lost, the database will automatically shut down. - Determine the status of the database by executing the following SQL query:. - PREVIEW output is in the same format as the output of the LIST command. - This example performs restore and recovery of the database, using automatic channels.. - Default Destination for Restore of the Control File. - "Restore of the Control File to a New Location". - Restore of the Control File from Control File Autobackup. - Restore of the Control File When a Flash Recovery Area is Used. - This improves the usefulness of the restored control file in the restoration of the rest of your database.. - Restore of the Control File When Using a Recovery Catalog. - Restore of the Control File From a Known Location. - You can restore the control file from a known control file copy using this form of the command:. - Restore of the Control File to a New Location. - If the database is up at the time of the loss of the SPFILE, connect to the target database. - Restore of the SPFILE from the Control File Autobackup. - After the control file is mounted, you can restore the remainder of the database.. - You make a backup of the database. - View the status of backups in one of the following locations:. - Oracle Database Recovery Manager Reference for descriptions of the recovery catalog views. - You can even catalog a backup piece from a prior incarnation of the database. - After connecting RMAN to the target database, catalog the filenames of the backup pieces. - This example deletes repository references to disk copies of the control file and datafile 1:. - Use the command BACKUP RECOVERY AREA , to back up the contents of the flash recovery area to a tertiary device such as tape.. - You can run the RMAN CROSSCHECK command to have RMAN re-check the contents of the flash recovery area and identify expired files, and then use the DELETE. - the flash recovery area. - where location is the location of the flash recovery area.. - The mode of the database in which Oracle copies filled online redo logs to disk.. - You can only take consistent backups after you have made a consistent shutdown of the database. - The automatic backup of the current control file that RMAN makes in the situations:. - A user-specified limit to the size of the flash recovery area. - flash recovery area. - You can specify the disk quota, which is the maximum size of the flash recovery area.
Xem thử không khả dụng, vui lòng xem tại trang nguồn hoặc xem
Tóm tắt