All of the data files must be from a backup taken prior to the point in time to which you want to recover.

Only the data files belonging from the SYSTEM tablespace must be from a backup taken prior to the point in time to which you want to recover.

Only the data files that need recovery must be from a backup taken prior to the point in time which you want to recover.

Only the data files belonging to the SYSTEM tablespace and the data files that need recovery must be from a backup taken prior to the point in time to which you want to recover.

Set the LOG_ARCHIVE_START parameter to TRUE in the initialization parameter file.

Automatic archive is the default when ARCHIVELOG mode is set. No further actions are required.

Set the LOG_ARCHIVE_MAX_PROCESSES parameter to n (where n is the number of Archiver process) in the initialization parameter file.

Immediately after setting the database in ARCHIVELOG mode, in SQL*Plus select automatic archiving using the syntax : ALTER DATABASE SET LOG_ARCHIVE_START=TRUE

A checkpoint defines the highest system change number (SCN)

All redo entries higher or at the SCN are known to be written to the data files.

Only the redo records containing SCNs higher then the checkpoint need to be applied during recovery.

The LOG_CHECKPOINT_INTERVAL initialization paramter specifies the amount of time beteen incremental checkpoints.

Do nothing, the PMON process handles everything.

Shut down the database and restore all the tables the user was updating.

Log in as DBA, clean up the partial updates in those tables, and do another manual backup.

Use LogMiner to find out which records are changed based on the user’s ID, then roll back all those changes.

A text copy of the control file.

A binary copy of the control file.

A file containing a SQL statement which will re-create the database.

A file containing a SQL statement which will re-create the control file.

Each target database requires its own recover catalog.

RMAN scripts can be stored in the recovery catalog or the targer control file.

A channel is a stream of data to a device type and corresponds to one server session.

The RMAN executable interprets server session commands and establishes connections to the target database.

The contents and data files belonging to the IND2 tablespace are dropped.

The statement will only succeed if the IND2 tablespace was built using Oracle-Managed Files (OMF) data files.

The statement will only succeed if the data files belonging to the IND2 tablespace are Oracle Managed Files (OMF) or of the database was created using OMF.

The contents of the tablespace are dropped along with all its data files except those identical with Oracle-Managed Files (OMF) naming convention.

The data file needs to be restored by using operating system commands, because a data file movement must take place, and then the database can be recovered from RMAN.

The data file needs to be restored by using operating system commands, since a data file movement must take place, and then the database must be recovered manually.

From RMAN you can issue the commands RESTORE and RECOVER. RMAN automatically restores the data file on DISK 3 to another disk, based upon utilization statistics.

From RMAN you can issue a SET NEWNAME command to update the data file location information in the control file, and then issue the RESTORE and RECOVER commands to recover the database.

Backups will never expire.

It removes any retention policy.

The DELETE OBSOLETE command will fail with an error.

It sets the retention policy to the default of REDUNDANCY 1.

TNSLSNR

LISTENER

LOCAL_LISTENER

DEFAULT_LSRN

True

False

True

False

True

False

True

False

OPEN

IDLE

MOUNT

NOMOUNT

PMON

SMON

RECO

ARCn

CKPT

Extent

Segement

Oracle block

Operating system block

The index need to be dropped, and then re-created.

The resolution of index fragmentation depends on the type of index.

The index can be rebuilt while users continue working on the table.

The fragmented can be ignored because Oracle resolve index fragmentation by means of a freelist.

The index can be rebuilt, but users will not have access to the index during this time.

The oracle server creates no undo tablespace.

The oracle server creates an undo segment in the system tablespace.

The oracle server cerates one undo tablespace with the name SYS_UNDOTBS.

Database creation fails because you did not specify an undo tablespace on the create database statment.

SELECT text FROM user_source WHERE name = 'SALARY_CALC';

SELECT * FROM user_source WHERE name='SALARY_CALC';

SELECT * FROM user_objects WHERE object_name='SALARY_CALC';

SELECT * FROM user_procedures WHERE object_name='SALARY_CALC';

SELECT text FROM user_source WHERE name='SALARY_CALC' and owner='JOHN'