In Recovery Manager （RMAN）， you have set control file autobackup to ON by using the following command：  CONFIGURE CONTROLFILE AUTOBACKUP ON;  Which two events would cause the control file to be backed up automatically？ （）

A .  a list of files that require a backup within three days B .  a list of files that have not been backed up for three days C .  a list of files that RMAN recommends be backed up only once in every three days， based on low volatility D .  a list of files for which a backup has already been performed and may need a backup after three day

A . You can use RMAN stored scripts B . Recovery is faster if data is stored in catalog in addition to the control file C . You can store backup information of all registered databases in one place D . Database backups are automatically deleted when they are older than the specified time period

A . data files B . control files C . parameter file D . online redo log files E . server parameter file

A . Stored scripts in the recovery catalog B . Backups that can be deleted from disk C . Backup sets and images copies that are obsolete D . Backups that do not have the AVAILABLE status in the RMAN repository

A . New channels for restore and recovery tasks B . New name for the data files of the tablespace C . Auxiliary name for the data files of the tablespace D . Auxiliary destinations for an auxiliary set of data file

A .  A list of files that require a backup within 3 days B .  A list of files requiring more than 3 days of archivelogs to apply C .  A list of files that RMAN recommends be backed up only once in every three days，based on low volatility D .  A list of files for which a backup as already been performed in the last three days and which is  required to be backed up again based on the high number of transactions performed on them

A . backups that can be deleted B . stored scripts in the recovery catalog C . backup sets and image copies that are obsolete D . only the most recent backup sets or image copies E . backups that do not have the AVAILABLE status in RMAN repository

A .  Backup compression is disabled by default. B .  Backup compression can be used with both backup sets and image copies. C .  Backup compression cannot be enabled using the CONFIGURE command. D .  Backup compression works only if the COMPATIBILITY parameter is set to 9.0.0.0 or higher. E .  Backup compression applies to only backup sets. F .  Backup compression applies to only image copies.

A . stored scripts in the recovery catalog. B . backups that can be deleted from disk. C . backup sets and image copies are obsolete. D . backups that do not have the AVAILABLE status in the RMAN repository.

A .  stored scripts in the recovery catalog B .  backups that can be deleted from disk C .  backup sets and image copies are obsolete D .  backups that do not have the AVAILABLE status in the RMAN repository

A . a list of all the expired backups and copies B . a list of all those files that have been deleted in the last two days C . a list of all those files that have been recovered within the last two days D . a list of backups and copies that are outside the range covered by the current retention policy

A .  New channels for restore and recovery tasks B .  New name for the data files of the tablespace C .  Auxiliary name for the data files of the tablespace D .  Auxiliary destinations for an auxiliary set of data file

A . Creating the control file for the duplicate database B . Restoring the target data files to the duplicate database C . Performing complete recovery using all available backups D . Generating a new, unique DBID for the duplicate database E . Copying the online redo log files from the target database to the duplicate database

A .  a list of files that require a backup within three days B .  a list of files requiring more than 3 days of archive logs to apply C .  a list of files that RMAN recommends be backed up only once in every three days，based on low volatility D .  a list of files for which a backup has already been performed in the last three days and which is required to be backed up again based on the high number of transactions performed on them

A . The database is in NOMOUNT state. B . The database is in ARCHIVELOG mode and the tablespace is online. C . The database is in ARCHIVELOG mode and the tablespace is offline. D . The database is in NOARCHIVELOG mode and the tablespace is online. E . The database is in NOARCHIVELOG mode and the tablespace is offline.

A .  Creating the control file for the duplicate database B .  Restoring the target data files to the duplicate database C .  Performing complete recovery using all available backups D .  Generating a new， unique DBID for the duplicate database E .  Copying the online redo log files from the target database to the duplicate database

A .  You can use RMAN stored scripts B .  Recovery is faster if data is stored in catalog in addition to the control file C .  You can store backup information of all registered databases in one place D .  Database backups are automatically deleted when they are older than the specified time period

A . back up the control file to trace B . bring database to the MOUNT state C . open a connection to the RMAN recovery catalog， which contains the RMAN metadata for the target database D . set the database ID （DBID）， but only if the DB_NAME parameter associated with the target database is unique in the recovery catalog

A . You are backing up to tape and your tape device performs its own compression. B . You are making image copies, and you have not enabled tablespace compression. C . You are using disk-based backups and disk space in your Flash Recovery Area, or other disk-based backup destinations are limited. D . You are performing your backups to some device over a network where reduced network bandwidth is more important than CPU usage. E . You are using some archival backup media, such as CD or DVD, where reducing backup sizes saves media costs and archival storage.

A . A list of files that require a backup within 3 days B . A list of files requiring more than 3 days of archivelogs to apply C . A list of files that RMAN recommends be backed up only once in every three days, based on low volatility D . A list of files for which a backup as already been performed in the last three days and which is required to be backed up again based on the high number of transactions performed on them

A .  The database is in NOMOUNT state. B .  The database is in NOARCHIVELOG mode and the tablespace is online. C .  The database is in NOARCHIVELOG mode and the tablespace is offline. D .  The database is in ARCHIVELOG mode and the tablespace is offline. E .  The database is in ARCHIVELOG mode and the tablespace is online.

A . a list of files that require a backup within three days B . a list of files that have not been backed up for three days C . a list of files that RMAN recommends be backed up only once in every three days， based on low volatility D . a list of files for which a backup has already been performed and may need a backup after three day

A .  back up the control file to trace B .  bring database to the MOUNT state C .  open a connection to the RMAN recovery catalog， which contains the RMAN metadata for the target database D .  set the database ID （DBID）， but only if the DB_NAME parameter associated with the target database is unique in the recovery catalog

A .  By using the trace file. B .  By using the alert log file. C .  By using the database ID D .  By using the server parameter file. E .  By using the V$CONTROLFILE view. F .  By using the autobackup format configuration setting.

A . stored scripts in the recovery catalog B . backups that can be deleted from disk C . backup sets and image copies are obsolete D . backups that do not have the AVAILABLE status in the RMAN repository RMAN