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.

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.

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.

OPEN

IDLE

MOUNT

NOMOUNT

SET

ALTER

CHANGE

UPDATE

TNSLSNR

LISTENER

LOCAL_LISTENER

DEFAULT_LSRN

PMON

SMON

RECO

ARCn

CKPT

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.

Control file

Extent

Segment

Data file

Log file

Tablespace

ABORT

NORMAL

IMMEDIATE

TRANSACTIONAL

TARGET_REDO_BLKS

FAST_START_IO_TARGET

LOG_CHECKPOINT_TIMEOUT

RECOVERY_ESTIMATED_IOS

LOG_FILE_SIZE_REDO_BLKS

LOG_CHECKPOINT_INTERVAL

Perform I/O

Lock rows that are not data dictionary rows

Monitor other Oracle processes

Connect users to the Oracle instance

Execute SQL statments issued through an application

CREATE USER

CREATE SESSION

CREATE ANY TABLE

IMP_FULL_DATABASE

EXP_FULL_DATABASE

Oracle Managed Files used for this instance.

The USER_DATA tablespace in managed using FET$/UET$ tables.

The COMPATIBLE intialization paramter must be 9.0.0 or higer.

Space within segments is the USER_DATA tablespace is managed with freelists.

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.

The control file can grow in size.

The control file can store RMAN scripts.

CONTROL_FILE_RECORD_KEEP_TIME determine retention time for RMAN records.

The RMAN catalog can exist solely in the control file of the target database.

SYNC or ASYNC to identify the network transmission mode.

LGWR or ARCH to identify the primary database process responsible for sending redo information to the standby.

AFFIRM or NOAFFIRM to control whether log archiving disk write operations are to be performed synchronously or asynchronously.

PROTECTED or UNPROTECTED to control the degree of divergence and data loss at the standby database.

Data encryption

User authentication

Transparent data conversion

Configuration and administration mechanisms

Support for multiple network transport protocols

Oracle Net is layered on top of the network protocol.

Oracle Net must reside on both the client and the server for peer-to-peer communication to occur.

On the client side, Oracle Net is responsible for working with the listener to receive incoming connection requests.

On the server side, Oracle Net is responsible for several connectivity issues such as : the location of the server, whatever one or more protocol is involved in the connection, and how to handle exception and interrupts.