- #Waiting for snapshot control file enqueue how to#
- #Waiting for snapshot control file enqueue install#
- #Waiting for snapshot control file enqueue software#
Then, obtain and install the third-party media management module for integration with the database server.
#Waiting for snapshot control file enqueue how to#
Refer to your media management documentation to learn how to back up files to the media manager outside of RMAN. This step makes later troubleshooting much easier, by confirming that the basic integration of the media manager with the target host has been successful. Ensure that you can make non-RMAN backups of operating system files on the target database host.
#Waiting for snapshot control file enqueue software#
In general, you should begin by installing and configuring the media management software on the target host or production network.
Instructions for this procedure should be available in the media manager vendor's software documentation. Prerequisites for Using a Media Manager with RMANīefore you can begin using RMAN with a media manager, you must install it and make sure that RMAN can communicate with it. To direct the restored archived redo logs to the flash recovery area, set one of the LOG_ARCHIVE_DEST_ n parameters to ' LOCATION=USE_DB_RECOVERY_FILE_DEST", and make sure you are not using SET ARCHIVELOG DESTINATION to direct restored archived logs to some other destination. RMAN restores any redo log files needed during these operations to the flash recovery area, and delete them once they are applied during media recovery. These commands restore archived redo logs from backup for use during media recovery, as required by the command. RECOVER DATABASE or TABLESPACE, BLOCKRECOVER, and FLASHBACK DATABASE If you do not specify SET ARCHIVELOG DESTINATION to override this behavior, then restored archived redo log files will be stored in the flash recovery area. Control file autobackups will be placed in the flash recovery area when no other destination is configured.Įxplicitly or implicitly (as in the case of), set one of the LOG_ARCHIVE_DEST_n) parameters to ' LOCATION=USE_DB_RECOVERY_FILE_DEST'. Use the RMAN command CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK CLEAR to clear any configured format option for the control file autobackup location on disk. RMAN can create control file autobackups in the flash recovery area.
In such a case, RMAN creates backup pieces and image copies in the flash recovery area, with names in Oracle Managed Files name format. The commands are:ĭo not specify a FORMAT option to the BACKUP command, and do not configure a FORMAT option for disk backups. The assumption in all cases is that a flash recovery area has already been configured for your database. This section describes RMAN commands or implicit actions (such as control file autobackup) that can create files in the flash recovery area, and how to control whether a specific command creates files there or in some other destination. RMAN File Creation in the Flash Recovery Area On Solaris, for example, the default is: ?/dbs. If you do not set any value for LOG_ARCHIVE_DEST, LOG_ARCHIVE_DEST_ n, or DB_RECOVERY_FILE_DEST, then the redo logs are archived to a default location that is platform-specific. If you have a flash recovery area configured, you can explicitly add the flash recovery area to the set of archiving destinations by setting one of the LOG_ARCHIVE_DEST_ n parameters to LOCATION=USE_DB_RECOVERY_FILE_DEST (note that this does not have to be LOG_ARCHIVE_DEST_10). In this case, redo log files are not archived in the flash recovery area by default. If you set any local destinations for LOG_ARCHIVE_DEST_ n, then archived redo logs are stored only in the destinations you specify using those parameters. (You can override this behavior by explicitly setting LOG_ARCHIVE_DEST_10 to an empty string.) If DB_RECOVERY_FILE_DEST is specified (that is, if a flash recovery area is configured) and no LOG_ARCHIVE_DEST_ n is specified, then LOG_ARCHIVE_DEST_10 is implicitly set to the flash recovery area. If LOG_ARCHIVE_DEST (and, optionally, LOG_ARCHIVE_DUPLEX_DEST) is set, these parameters will specify the only redo log archiving destinations. The interactions among different initialization parameters affecting redo log archiving distinctions are as follows: Rules for Initialization Parameters Affecting Redo Log File Destinations
0 kommentar(er)
