单选题You run the following commands：   RMAN> list expired backup； RMAN> delete expired backup；   What will happen to the backup set pieces associated with the backups that appear in the list expired backup command？（）AThey will be renamed.BNothing will happe

 to configure RMAN to maintain backup information in the RMAN repository for seven days

 to configure RMAN to maintain backup information in the control file for at least seven days

 to display the list of files that have not been backed up for the last seven days

 to display the list of files that must be backed up within seven days

EXPIRED

AVAILABLE

UNAVAILABLE

ACCESSIBLE

 Create a backup of the database and recover all corrupted blocks found in the backup.

 Run a backup validation and list all the logically corrupt blocks as well as physically corrupt blocks in the database.

 Run a backup validation to populate V$COPY_CORRUPTION view， and then list any corrupt blocks recorded in the view.

 Run a backup validation to populate V$DATABASE_BLOCK_CORRUPTION view， and then repair any corrupt blocks recorded in the view.

 Run a backup validation， repair any corrupt blocks found during the validation process， and then update V$DATABASE_BLOCK_CORRUPTION view to indicate which corrupt blocks have been repaired.

The script is stored only in the control file.

The script is stored only in the recover catalog.

The script can be executed only by using the RMAN RUN command.

The commands of the script can be displayed with the LIST command.

The commands of the script can be displayed with the PRINT command.

The commands of the script can be displayed with the REPORT command.

It produces a warning for new failures before advising for CRITICAL and HIGH failures.

It ignores new failures and considers the failures listed in the last LIST FAILURE command only.

It produces an error with recommendation to run the LIST FAILURE command before the ADVISE FAILURE command.

It produces advice only for new failures and the failures listed in the last LIST FAILURE command are ignored.

 run { open script backup_database； run script backup_database }

 run { engage script backup_database； }

 run { run script backup_database； }

 Run { execute script backup_database； }

 The name backup_database is an invalid name for an RMAN script. Trying to run it from RMAN would result in an error.

a list of files that require a backup within three days

a list of files that have not been backed up for three days

a list of files that RMAN recommends be backed up only once in every three days， based on low volatility

a list of files for which a backup has already been performed and may need a backup after three days

 They will be renamed.

 Nothing will happen to them. The backup set pieces do not exist.

 They will be deleted immediately since they are not in the flash recovery area.

 You will need to manually remove the physical files listed in the output of the commands.

 They will become hidden files and removed 10 days later.

Only one channel is allocated and the backup is created in the flash recovery area

Only one channel is allocated and the backup is created in the destination specified for channel 1

Two channels are allocated and backup sets are created in the destinations specified for channels 1 and 2

Three channels are allocated and backup sets are created in the destinations specified for channels 1, 2, and FRA

 a list of files that require a backup within three days

 a list of files requiring more than 3 days of archive logs to apply

 a list of files that RMAN recommends be backed up only once in every three days，based on low volatility

 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 list of all those files that have been deleted in the last two days

 a list of all those files that have been recovered within the last two days

 a list of all the expired backups and copies

 a list of backups and copies that are outside the range covered by the current retention policy

Repair the corrupted blocks. If any. In the backup created

Populate VSCOPV_CORRUPTION with names of files that have corrupted blocks

Back up the database after checking whether array of the files have corrupted blocks

Discover any corrupt blocks that are viewable with the VSDATABASE_BI-OCK_CORBUPTION view

Repair all corrupted blocks that have been logged in the VSDATABASE_BLOCK_ CORRUPTION

create a backup of the database and recover all corrupted blocks found in the backup

run a backup validation and list all the logically corrupt blocks as well as physically corrupt blocks in the database

run a backup validation to populate V$COPY_CORRUPTION view， and then list any corrupt blocks recorded in the view

run a backup validation to populate V$DATABASE_BLOCK_CORRUPTION view， and then repair any corrupt blocks recorded in the view

run a backup validation， repair any corrupt blocks found during the validation process， and then update V$DATABASE_BLOCK_CORRUPTION view to indicate which corrupt blocks have been repaired

 A list of files that require a backup within 3 days

 A list of files requiring more than 3 days of archivelogs to apply

 A list of files that RMAN recommends be backed up only once in every three days，based on low volatility

 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

when you change the name of a datafile

when you drop a table from the database

when you take an export of the database

when you back up the database using OS utilities

when you issue an ALTER SYSTEM SWITCH LOGFILE statement

when you issue a BACKUP command from inside the RMAN run block

control file

all datafiles

password file

online redo log file

archive redo log file

server parameter file

only the SYSTEM datafile