A redo log file is corrupted while the database is open； as a consequence， database operations are stopped because archiving cannot continue. What would you do to solve the problem？（）

A .  log writer B .  archival C .  process monitor D .  system monitor E .  change tracking writer F .  database writer

A .  import the database from the last export B .  restore all the members in the group from the last backup C .  drop the lost member from the database and then add a new member to the group D .  restore all the database files from the backup and then perform a complete recovery E .  restore all the database files from the backup and then perform an incomplete recovery

A . RMAN keeps a list of archive logs in a text file. B . The DBA must manually tell RMAN which archive logs to backup. C . RMAN has access to target control file and/or catalog information. D . RMAN looks at the ARCHIVE_LOG_DEST parameter of your target database and backs up all archive logs found.

A .  The LGWR process concurrently writes the redo log entries to both the members of a group. B .  When a member of a group becomes corrupt， the database crashes. C .  The sizes of the redo01a.log and redo01b.log online redo log members of group Group1 can be different. D .  When redo02a.log and redo02b.log files become corrupt， then the database operations will proceed as normal.

A .  backup database B .  backup database and archivelogs C .  backup database plus archivelogs D .  backup database plus archivelog delete input E .  backup database and archivelog delete input

A . archival B . log writer C . database writer D . system monitor E . process monitor F . change tracking writer

A . import the database from the last export B . restore all the members in the group from the last backup C . drop the lost member from the database， and then add a new member to the group D . restore all the database files from the backup， and then perform a complete recovery  E . restore all the database files from the backup， and then perform an incomplete recovery

A . Archiving will be disabled because the destination for the redo log files is missing. B . The database instance will shut down and the error details will be logged in the alert log file. C . Archiving will be enabled and the destination for the archived redo log file will be set to the Flash RecoveryArea implicitly. D . Archiving will be enabled and the location for the archive redo log file will be created in the default location$ORACLE_HOME/log.

A . NOCHECKSUM B . MAXCORRUPT C . CHECK LOGICAL D . BACKUP INCREMENTAL E . CONFIGURE DEVICE TYPE ... PARALLELISM

A .  Recover the online redo log from backup. B .  Delete and re-create the log file. C .  Use the alter database clear logfile command to clear the log file. D .  Shut down the database and restart it. E .  Shut down the database and then mount it. Clear the log file with the alter database clear logfile command and then restart the database with alter database open resetlogs.

A . Cancel-based B . Recovery using a backup control file C . Time-based D . Change-based

A . The deleted file is still open by the application. The system must be rebooted before ‘df’ will show the reduction in the filesystem. B . The deleted file is still open by the application. The application must be stopped before ‘df’ will show the reduction in the filesystem. C . The filesystem is still marked as full in the /etc/fs.status file. The system must be rebooted before ‘df’ will show the reduction in the filesystem. D . The filesystem is still marked as full in the /etc/fs.status file. The application must be stopped before ‘df’ will show the reduction in the filesystem.

A .  If the lost redo log group is ACTIVE， you should first attempt to clear the log file. B .  If the lost redo log group is CURRENT， you must clear the log file. C .  If the lost redo log group is ACTIVE， you must restore，perform cancel-based incomplete recovery，and open the database using the RESETLOGS option. D .  If the lost redo log group is CURRENT， you must restore，perform cancel-based incomplete recovery，and open the database using the RESETLOGS option.

A . until the last commit B . cannot be recovered C . until the last offline backup D . until the beginning of the last transactio

A . log01.log  B . logORCL01.log  C . 1_2.logALTER ROLLBACK SEGMENT  D . ora_1_asdf1234.log

A . ARCn B . DBWn C . CKPT D . LGWR E . PMON F . SMON

A . Transactions are rolled back using redo log files. B . Transactions are rolled forward using redo log files. C . Transactions are rolled back using redo log files and archived log files. D . Transactions are rolled forward using redo log files and rolled back using redo log files.

A . ALTER DATABASE  B . ALTER SYSTEM  C . ALTER USER  D . ALTER REDO LOG

A .  The block change tracking feature must be enabled. B .  OMF must be configured on your database. C .  The database must be in ARCHIVELOG mode. D .  A USERID must be supplied.

A . The database instance aborts. B . The database operation temporarily halts till the member becomes available. C . Writing proceeds as normal. LGWR writes to the available members of a group and ignores the unavailable members. D . The member would be marked as STALE and an error message would be written to the alert log file and LGWR trace file. E . The status of the group changes to INACTIVE and an error message would be written to the alert log file and LGWR trace file.

A .  The database will hang. B .  The database will be crashed. C .  The database will be shut down. D .  The LGWR process writes redo log entries to the other redo log member of the Group2 grou

A . Inactive and current redo log files are required to accomplish recovery. B . Online and archived redo log files are required to accomplish instance recovery. C . All redo log entries after the last checkpoint are applied from redo log files to data files. D . All redo log entries recorded in the current redo log file until the checkpoint position are applied to data file

A .  Complete database recovery. B .  Incomplete database recovery. C .  Approximate database recovery. D .  Archived database recovery. E .  The database could not be recovered with RMAN.

A . The deleted file is still open by the application.The system must be rebooted before'df' will show the reduction in the filesystem. B . The deleted file is still open by the application.The application must be stoppedbefore 'df' will show the reduction in the filesystem. C . The filesystem is still marked as full in the /etc/fs.status file.The system must be rebooted before 'df' will show the reduction in the filesystem. D . The filesystem is still marked as full in the /etc/fs.status file.The application must be stopped before 'df' will show the reduction in the filesystem.