Database Management Systems

This prevents SQL statements from being repeatedly parsed thus improving performance during execution of SQL statements.

During this phase, RMAN determines which objects the command will access.

Two specific cache library cache and the data dictionary caches form the shared pool.

This file is very useful in the event of a failure and is used for recovery purposes.

It's main functions are to provide memory for session memory for the shared server environment, parallel execution message buffers.

It is a contiguous group of blocks allocated for use as part of a table, index and so forth.

It allows you to specify the values to attributes that can be enforced without bouncing the database as well as after re-starting the database.

It stores the most critical data which never remains in-doubt, even if a failure occurs.

The contents of the redo log buffer are essential for instance recovery purposes.

Here, the transaction wants only to read the data item.

A tablespace will frequently group together similar objects such as relations for a specific business area or a specific function.

Yes, this is the correct choice.A table is a set of data elements (values) that is organized using a model of vertical columns (which are identified by their name) and horizontal rows, the cell being the unit where a row and column intersect.

CURSOR_SPACE_FOR_TIME parameter set to TRUE tells Oracle to keep cursors in memory even when not in use, trading memory for performance. Before enabling this, you must confirm that RELOADS in V$LIBRARYCACHE is consistently zero - meaning SQL statements aren't being reloaded, indicating sufficient shared pool memory.

To grant remote DBA access in Oracle, you must grant SYSDBA privilege to the user. The GRANT SYSDBA TO ALLEN command adds Allen to the password file with SYSDBA privileges, allowing remote database startup and administration. Option A is incorrect because DBA is a role, not a privileged connection. Option D shows orapwd syntax for creating password files, not granting privileges.

The 'Checkpoint Not Complete' message occurs when LGWR cannot write to redo log files because a checkpoint hasn't completed. This happens when redo logs are too small or too few. Solutions include: adding more redo log groups (B) so LGWR has more available logs, and increasing size of online redo log files (D) to provide more space between checkpoints. Deleting archived logs (A) doesn't help and increasing archived log size (C) is irrelevant.