1Z0-025 無料問題集「Oracle Backup and Recovery」

（A）It is not possible to disable archive destinations?

（B）Specify the initialization parameter LOG_ARCHIVE_DEST_STATE_n=DEFER.

（C）Shut down the database and delete the archive destination dictionary at the operating system level.

（D）Issue the command ALTER SESSION SET LOG_ARCHIVE_DEST=DEFER.

（A）To allow for automatic data file recovery.

（B）To recover it later, when database is in NOARCHIVELOG mode.

（C）To minimize downtime.

（D）To prevent further corruption of a damaged data file.

（A）Perform a tablespace recovery.

（B）Perform a complete database recovery.

（C）There is no possibility too make the database available.

（D）Restore the data files, redo log files, and control files from an earlier copy of a full database backup.

（A）More background processes are required.

（B）Additional disk resources are required.

（C）An operating systems script must be written to copy the online redo-log files.

（D）A DBA must issue an SQL command to archive the online redo-log files.

（A）Issue the ALTER DATABASE. . . ADD LOGFILE GROUP command.

（B）Shut down the database, copy the online redo-log, edit the REDO_LOG_FILES parameter, and start up the database.

（C）Issue the ALTER DATABASE. . . ADD LOGFILE MEMBER command.

（D）Shut down the database, copy the online redo-log, and start up the database.

（A）Set the AUTO_ARCHIVE_LOG initialization parameter.

（B）Use the AUTOMATIC clauses of the RECOVER command.

（C）Enter the word AUTO when prompted for a log.

（D）Within SQL*Plus, issue SET AUTORECOVERY ON command.

（A）The primary database can be set up in a way that it automatically copies archived redo-log files to the standby site.

（B）The standby database automatically copies archived redo-log files from the primary server to release 8.1

（C）The standby database automatically copies archived redo-log files from the primary server when it is in sustained recovery mode.

（D）Files can be copied via FTP or other platform-specific commands.

（E）The standby database automatically copies archived redo-log files from the primary server when it is in a managed recovery mode.

（A）Make sure the database is the only primary database in the current configuration.

（B）Copy all affected data files to the standby server.

（C）Manually reapply the changes to the standby database.

（D）Switch log files on the primary database.

（A）The operating system crashes.

（B）An application file is accidentally deleted.

（C）A table is accidentally truncated.

（D）The application program receives an addressing exception.

（E）Incorrect data is committed.

（F）There are insufficient privileges.

（A）Nothing

（B）Create a tablespace for the catalog and a recovery manager user.

（C）Start up the target database.

（D）Connect to target database.