Tag: databases

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.

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.

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.

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.

alert.ora

init.ora

tnsname.ora

redolog

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.

Extent

Segement

Oracle block

Operating system block

V$UNDOSTAT

V$TRANSACTION

V$ROLLSTAT

DBA_UNDO_EXTENTS

DBA_ROLLBACK_SEGS

OPEN

IDLE

MOUNT

NOMOUNT

PMON

SMON

RECO

ARCn

CKPT