- 1-7 Storage of the RMAN Repository in the Recovery Catalog. - 1-7 Storage of the RMAN Repository in the Control File. - 6-2 Configuring Control File Creation in the Flash Recovery Area. - 6-2 Archived Redo Log Creation in the Flash Recovery Area. - 6-26 Default Location of the Snapshot Control File. - 6-27 Viewing the Configured Location of the Snapshot Control File. - 6-27 Setting the Location of the Snapshot Control File. - 13-4 Managing Target Database Records in the Recovery Catalog. - 13-5 Registering a Database in the Recovery Catalog. - 13-8 Resetting a Database Incarnation in the Recovery Catalog. - 13-13 Forcing a Full Resynchronization of the Recovery Catalog. - 13-28 Increasing Availability of the Recovery Catalog. - 13-31 Determining the Schema Version of the Recovery Catalog. - 16-3 Making User-Managed Backups of the Whole Database. - 16-12 Making User-Managed Backups of the Control File. - 19-5 Step 2: Identify All of the Files in the Recovery and Auxiliary Set Tablespaces. - You can send com- ments to us in the following ways:. - This chapter describes the application architecture of the RMAN environment.. - This chapter describes how to use DUPLICATE to create a copy of the target database.. - Enter one of the options. - That you can repeat a portion of the code. - Multiplexed copies of the control file and online redo logs – Archived redo logs and flashback logs. - The contents of the backup sets that define which files are multiplexed – The level of multiplexing. - See Also: Oracle Database Recovery Manager Reference to learn about the behavior of the RECOVER command. - Oracle Database Recovery Manager Reference to learn about the behavior of the RESTORE command. - Oracle Database Recovery Manager Reference to learn about the output of the BACKUP command. - This chapter describes the Recovery Manager (RMAN) interface and the basic components of the RMAN environment.. - Table 1–1 lists possible components of the RMAN environment.. - Table 1–1 Components of the RMAN Environment. - Duplicate database A copy of the primary database that you can use for testing purposes.. - The recovery catalog’s version of the RMAN repository is maintained solely by RMAN. - Storage of the RMAN Repository in the Recovery Catalog. - Registration of Databases in the Recovery Catalog. - You can register more than one target database in the same recovery catalog. - Contents of the Recovery Catalog. - Persistent RMAN configuration settings Resynchronization of the Recovery Catalog. - Resynchronization of the recovery catalog ensures that the metadata that RMAN obtains from the control file stays current. - See Also: "Registering a Database in the Recovery Catalog". - See Also: "Types of Records in the Control File". - Recovery Manager Architecture 1-9 consistent view of the control file. - RMAN records the snapshot control file checkpoint in the recovery catalog to indicate the currency of the recovery catalog.. - Backups of the Recovery Catalog. - Consequently, loss of the recovery catalog can be disastrous. - Compatibility of the Recovery Catalog. - Note: You can specify the name and location of the snapshot control file. - Storage of the RMAN Repository in the Control File. - Types of Records in the Control File. - specified in the CONFIGURE command. - If you specify DEVICE TYPE DISK, then your backups are created on disk, in the file name space of the target instance that is creating the backup. - You can use the CHANNEL option of the BACKUP command to manually assign a channel to back up specified files. - You can also manually allocate channels as in the following example:. - Oracle Database Recovery Manager Reference for reference material on the CHANNEL parameter of the BACKUP command. - The following example creates 3 copies of the backup of datafile 7 : BACKUP DEVICE TYPE DISK COPIES 3 DATAFILE 7 FORMAT. - For example, you can execute the following BACKUP command weekly as part of the production backup schedule:. - If you duplexed a backup to four locations, then RMAN deletes all four copies of the pieces in the backup set.. - See Also: Oracle Database Recovery Manager Reference for descriptions of the FORMAT parameter and the substitution variables. - When applied to a backup set, a tag applies to a specific copy of the backup set. - However, you can back up this backup set and give this new copy of the backup set the tag BAR . - Overview of the MAXSETSIZE Parameter. - For example, you can restore non-incremental image copies of the datafiles in the database, and RMAN can recover them with incremental backups.. - A level 1 incremental backup can be either of the following types:. - The RMAN repository records in the control file will be copied to the new recovery catalog.. - After the control file autobackup completes, the database writes a message containing the complete path of the backup piece and the device type to the alert log.. - substitution variable %F is defined in the description of the CONFIGURE command in Oracle Database Backup and Recovery Basics. - This means that the control file is backed up in the following situations:. - To take better advantage of restartable backups, you can use set the MAXSETSIZE parameter of the BACKUP command. - If the backup completes without exceeding MAXCORRUPT,then the database records the address of the corrupt blocks and the type of corruption in the control file. - In the RMAN BACKUP and RESTORE commands, do not specify the. - You can run the BACKUP. - If yes, then RMAN updates the datafile names in the control file to the names of the restored files. - information in the RMAN repository. - The database records an archived log in the control file whenever one of the following occurs:. - Results of the DBVERIFY utility. - Use the RMAN DUPLICATE command to create a copy of the target database in another location. - As part of the duplication, RMAN manages the following:. - You can:. - Incarnation A of the database started at SCN 1. - Figure 4–2 illustrates a crosscheck of the media manager. - You can view the status information in the output of the LIST command and the recovery catalog views.. - Control file. - INFO column displays in the following format:. - OPNAME A text description of the row. - This record is stored in the control file. - Updates the backup records in the control file to status DELETED. - If you specify ALL INPUT , then RMAN deletes all copies of the files recorded in the RMAN repository.. - The BACKUP. - Configuring Control File Creation in the Flash Recovery Area. - Archived Redo Log Creation in the Flash Recovery Area. - RMAN can create control file autobackups in the flash recovery area. - set one of the LOG_ARCHIVE_DEST_. - In the. - This could arise in the following situations:. - The backup of the tools tablespace uses the MAXSETSIZE setting of 5G used in the BACKUP command.. - The size of a backup set is measured in the total bytes of the included backup pieces. - For example, you can enter one of the following commands:. - Configuring the RMAN Environment: Advanced Topics 6-27 file only when resynchronizing with the recovery catalog or when making a backup of the current control file.. - Default Location of the Snapshot Control File. - By default, the location of the snapshot control file is determined by the rules in the following table:. - Viewing the Configured Location of the Snapshot Control File. - Setting the Location of the Snapshot Control File
Xem thử không khả dụng, vui lòng xem tại trang nguồn hoặc xem
Tóm tắt