Enable flashback logging.
Start the database in the ARCHIVELOG mode.
Issue the ALTER DATABASE FLASHBACK ON; command.
Set the FAST_START_MTTR_TARGET initialization parameter.
第1题:
The database is currently running in the NOARCHIVELOG mode. What would be the first step to configure Flashback Database?()
第2题:
Your database is in NOARCHIVELOG mode. After which two operations you should take the backup of control file?()
第3题:
Your database is in ARCHIVELOG mode. You lost an index tablespace due to a disk failure while the database was open. You have neither a backup of the lost index tablespace nor the scripts containing the CREATE INDEX statements to recreate the indexes. Currently, several users are executing long-running queries on the database. What will happen to the ongoing activity in the database?()
第4题:
Ensure that database is running with version 10.1 compatibility.
Enable Flashback Logging.
Enable Supplemental Logging.
Ensure that the database is running with version 10.0 compatibility.
Ensure that the database is in ARCHIVELOG mode.
第5题:
You can perform open database backups.
You can perform closed database backups.
You cannot perform schema-level logical backups.
You can perform the backup of only the SYSTEM tablespace when the database is open.
第6题:
The backups would be consistent.
The backups would be inconsistent.
The backups would be possible only if the database is running in ARCHIVELOG mode.
The backups would be possible only if the database is running in NOARCHIVELOG mode.
The backups need to be restored and the database has to be recovered in case of a media failure.
第7题:
Enable flashback logging.
Start the database in the ARCHIVELOG mode.
Issue the ALTER DATABASE FLASHBACK ON; command.
Set the FAST_START_MTTR_TARGET initialization parameter.
第8题:
Enable the flash recovery area and specify it as the archived redo log destination.
Disable the flash recovery area and start the database instance in ARCHIVELOG mode.
Enable the flash recovery area but do not specify it as the archived redo log destination.
Disable the flash recovery area and start the database instance in NOARCHIVELOG mode.
第9题:
backup of offline tablespaces
backup of readonly tablespaces
backup of systemcritical tablespaces
backup of online, locally managed tablespaces
backup of read/write dictionarymanaged tablespaces
第10题:
Configure Java Pool to cache the java objects.
Configure Streams Pool to enable parallel processing.
Increase Shared Pool size to cache more PL/SQL objects.
Increase Database Buffer Cache size to increase cache hits.
Configure Large Pool to be used by RMAN and shared server.
Increase the total System Global Area (SGA) size to increase memory hits.
第11题:
The backups would be consistent.
The backups would be inconsistent.
The backups would be possible only if the database is running in ARCHIVELOG mode.
The backups would be possible only if the database is running in NOARCHIVELOG mode.
The backups need to be restored and the database has to be recovered in case of a media failure
第12题:
The instance aborts.
The database cannot be recovered.
The database can be recovered by restoring the control files from the backup.
The database remains opened and you have to shut it down with the ABORT option.
The database can be restored till the point of the last closed whole database backup.
第13题:
You are managing an Oracle Database 11g database. The database is open, and you plan to perform Recovery Manager (RMAN) backups. Which three statements are true about these backups()
第14题:
you can perform an active database duplication when the database is in NOARCHIVELOG mode.()
第15题:
Your database is configured in NOARCHIVELOG mode. All the control files have been lost due to a hard disk failure but the data files are not lost. You have the closed whole database backup available to you. Which two statements are true in this scenario?()
第16题:
The queries that are currently executing will abort and an error message will be returned to the user.
The queries that are currently executing will execute normally but future queries will not executed.
Data Manipulation Language (DML) statements cannot be performed on the tables on which the indexes are based.
The currently executing and future queries will execute normally, but will be slower
第17题:
adding a new user to the database
dropping a user from the database
dropping a table from the database
dropping a data file from a tablespace
adding a new tablespace to the database
第18题:
The destination must be global only.
A maximum of five destinations can be assigned.
A maximum of ten different destinations can be assigned.
All the destinations are determined by the server automatically.
The destination may be local or remote for a Standby Database.
The destination can be changed by setting the LOG_ARCHIVE_FORMAT initialization parameter.
第19题:
You can perform online whole database backups.
You can performofflinewhole database backups.
You cannot perform schema-level export/import operations.
You can perform the backup of only the SYSTEM tablespace when the database is open.
第20题:
True
False
第21题:
Configure Java Pool to cache the java objects.
Configure Streams Pool to enable parallel processing.
Increase Shared Pool size to cache more PL/SQL objects.
Increase Database Buffer Cache size to increase cache hits.
Configure Large Pool to be used by RMAN and shared server.
Increase the total System Global Area (SGA) size to increase memory hits.
第22题:
Allow the database to continue running, drop the TEMP tablespace, and then re-create it with new tempfiles
Shut down the database, restore and recover the tempfile from backup, and then open the database with RESETLOGS
Allow the database to continue running, take the TEMP tablespace offline, drop the missing tempfile, and then create a new tempfile
Allow the database to continue running, add a new tempfile to TEMP tablespace with a new name, and drop the tempfile that has been corrupted.
第23题:
DBA_SCHEDULER_RUNNING_JOBS
DBA_SCHEDULER_JOB_RUN_DETAILS
DBA_SCHEDULER_JOBS
DBA_SCHEDULER_JOB_LOG
第24题:
Restore the data file and perform incomplete recovery.
Restore the data file and perform point-in-time recover.
Drop the tablespace and lose all data in the tablespace.
Restore the database and lose all data since the last backup.