Explore topic-wise InterviewSolutions in .

Privilege AUDITING is the auditing of the USE of powerful SYSTEM privileges WITHOUT regard to specifically NAMED objects.

Privilege auditing is the auditing of the use of powerful system privileges without regard to specifically named objects.

Roles are NAMED GROUPS of related PRIVILEGES that are granted to users or other roles.

Roles are named groups of related privileges that are granted to users or other roles.

ROLES are the EASIEST way to grant and manage common privileges needed by different groups of DATABASE users. Creating roles and assigning PROVIDES to roles. Assign each role to group of users. This will simplify the job of assigning privileges to individual users.

Roles are the easiest way to grant and manage common privileges needed by different groups of database users. Creating roles and assigning provides to roles. Assign each role to group of users. This will simplify the job of assigning privileges to individual users.

• SHUT the DATABASE.
• BACKUP the database.
• Modify/Include LOG_ARCHIVE_START_TRUE in init.ora FILE.
• START up the database.

SQL * DBA - This allows DBA to monitor and control an ORACLE database. SQL * Loader - It LOADS data from standard operating SYSTEM FILES (FLAT files) into ORACLE database tables. Export (EXP) and Import (imp) utilities allow you to move existing data in ORACLE format to and from ORACLE database.

SQL * DBA - This allows DBA to monitor and control an ORACLE database. SQL * Loader - It loads data from standard operating system files (Flat files) into ORACLE database tables. Export (EXP) and Import (imp) utilities allow you to move existing data in ORACLE format to and from ORACLE database.

STATEMENT AUDITING is the auditing of the powerful SYSTEM privileges without REGARD to specifically NAMED objects.

Statement auditing is the auditing of the powerful system privileges without regard to specifically named objects.

STATEMENT AUDITING, PRIVILEGE Auditing and OBJECT Auditing.

Statement Auditing, Privilege Auditing and Object Auditing.

The collective amount of DISK SPACE available to the OBJECTS in a schema on a PARTICULAR tablespace.

The collective amount of disk space available to the objects in a schema on a particular tablespace.

The number of concurrent sessions the user can establish the CPU processing time AVAILABLE to the user's session the CPU processing time available to a single CALL to ORACLE MADE by a SQL STATEMENT the amount of logical I/O available to the user's session the amout of logical I/O available to a single call to ORACLE made by a SQL statement the allowed amount of IDLE time for the user's session the allowed amount of connect time for the user's session.

The number of concurrent sessions the user can establish the CPU processing time available to the user's session the CPU processing time available to a single call to ORACLE made by a SQL statement the amount of logical I/O available to the user's session the amout of logical I/O available to a single call to ORACLE made by a SQL statement the allowed amount of idle time for the user's session the allowed amount of connect time for the user's session.

The Tablespace to contain SCHEMA OBJECTS created WITHOUT specifying a tablespace NAME.

The Tablespace to contain schema objects created without specifying a tablespace name.

To perform ONE of these function on an index,table, or cluster:

• To collect statistics about OBJECT used by the OPTIMIZER and STORE them in the DATA dictionary.
• To delete statistics about the object used by object from the data dictionary.
• To validate the structure of the object.
• To identify migrated and chained rows of the table or cluster.

To perform one of these function on an index,table, or cluster:

A database instance (Server) is a set of memory structure and background processes that access a set of database files.

The PROCESS can be shared by all users. The memory structure that are USED to store most QUERIED data from database. This helps up to improve database performance by DECREASING the amount of I/O performed against data file.

A database instance (Server) is a set of memory structure and background processes that access a set of database files.

The process can be shared by all users. The memory structure that are used to store most queried data from database. This helps up to improve database performance by decreasing the amount of I/O performed against data file.

An index is a database STRUCTURE used by the server to have direct access of a ROW in a table. An index is automatically created when a unique of primary key CONSTRAINT clause is specified in create table COMMAN (Ver 7.0).

An index is a database structure used by the server to have direct access of a row in a table. An index is automatically created when a unique of primary key constraint clause is specified in create table comman (Ver 7.0).

Group of TABLES physically stored together because they SHARE COMMON COLUMNS and are often USED together is called Cluster.

Group of tables physically stored together because they share common columns and are often used together is called Cluster.

MULTIPLE INSTANCES ACCESSING the same DATABASE (Only In Multi-CPU ENVIRONMENTS).

Multiple instances accessing the same database (Only In Multi-CPU environments).

The related COLUMNS of the tables are called the cluster key. The cluster key is INDEXED using a cluster INDEX and its VALUE is stored only once for multiple tables in the cluster.

The related columns of the tables are called the cluster key. The cluster key is indexed using a cluster index and its value is stored only once for multiple tables in the cluster.

The SET of OBJECTS owned by USER account is CALLED the SCHEMA.

The set of objects owned by user account is called the schema.

Two processes wating to UPDATE the rows of a table which are locked by the other process then deadlock arises. In a database environment this will often happen because of not issuing proper row lock COMMANDS. Poor design of front-end APPLICATION may cause this situation and the performance of server will reduce drastically. These locks will be RELEASED automatically when a commit/rollback OPERATION performed or any one of this processes being killed externally.

Two processes wating to update the rows of a table which are locked by the other process then deadlock arises. In a database environment this will often happen because of not issuing proper row lock commands. Poor design of front-end application may cause this situation and the performance of server will reduce drastically. These locks will be released automatically when a commit/rollback operation performed or any one of this processes being killed externally.

A Read-Only transaction ENSURES that the RESULTS of each QUERY EXECUTED in the transaction are consistant with RESPECT to the same point in time.

A Read-Only transaction ensures that the results of each query executed in the transaction are consistant with respect to the same point in time.

COMMIT makes PERMANENT the changes RESULTING from all SQL statements in the transaction. The changes made by the SQL statements of a transaction become visible to other user SESSIONS TRANSACTIONS that START only after transaction is committed.

COMMIT makes permanent the changes resulting from all SQL statements in the transaction. The changes made by the SQL statements of a transaction become visible to other user sessions transactions that start only after transaction is committed.

Considering available ACCESS paths and DETERMINING the most efficient EXECUTION plan based on STATISTICS in the data dictionary for the tables accessed by the statement and their associated CLUSTERS and indexes.

Considering available access paths and determining the most efficient execution plan based on statistics in the data dictionary for the tables accessed by the statement and their associated clusters and indexes.

The Optimizer chooses Cost_based APPROACH and optimizes with the goal of best throughput if STATISTICS for atleast one of the tables accessed by the SQL STATEMENT exist in the data DICTIONARY. OTHERWISE the OPTIMIZER chooses RULE_based approach.

The Optimizer chooses Cost_based approach and optimizes with the goal of best throughput if statistics for atleast one of the tables accessed by the SQL statement exist in the data dictionary. Otherwise the OPTIMIZER chooses RULE_based approach.

When it is COMMITTED or Rollbacked.

When it is committed or Rollbacked.

A CLUSTER with an INDEX on the Cluster KEY.

A Cluster with an index on the Cluster Key.

A COLUMN DEFINED as UNIQUE can contain Nulls while a column defined as PRIMARY KEY can't contain Nulls.

A column defined as UNIQUE can contain Nulls while a column defined as PRIMARY KEY can't contain Nulls.

A DATA block SIZE is SPECIFIED for each ORACLE database when the database is created. A database users and allocated free database space in ORACLE datablocks. Block size is specified in INIT.ORA file and can't be changed latter.

A data block size is specified for each ORACLE database when the database is created. A database users and allocated free database space in ORACLE datablocks. Block size is specified in INIT.ORA file and can't be changed latter.

A data file can be ASSOCIATED with only ONE database. Once created a data file can't CHANGE size. One or more data files FORM a logical unit of database STORAGE called a tablespace.

A data file can be associated with only one database. Once created a data file can't change size. One or more data files form a logical unit of database storage called a tablespace.

A Database contains one or more ROLLBACK Segments to temporarily STORE "undo" INFORMATION.

A Database contains one or more Rollback Segments to temporarily store "undo" information.

Indexes are AUTOMATICALLY maintained and USED by Oracle. CHANGES to table DATA are automatically incorporated into all relevant indexes.

Indexes are automatically maintained and used by Oracle. Changes to table data are automatically incorporated into all relevant indexes.

An index is an optional structure associated with a table to have DIRECT access to ROWS, which can be created to increase the PERFORMANCE of data RETRIEVAL. Index can be created on one or more columns of a table.

An index is an optional structure associated with a table to have direct access to rows, which can be created to increase the performance of data retrieval. Index can be created on one or more columns of a table.

• Mask the real name and owner of an object.
• Provide public ACCESS to an object.
• Provide location TRANSPARENCY for TABLES, views or program units of a REMOTE database.
• Simplify the SQL statements for database users.

Any DATABASE USER can ACCESS a PUBLIC SYNONYM.

Any database user can access a public synonym.

Only its OWNER can ACCESS a PRIVATE SYNONYM.

Only its owner can access a private synonym.

There are TWO TYPES of SYNONYMS PRIVATE and PUBLIC.

There are two types of synonyms private and public.

A SYNONYM is an alias for a table, view, sequence or PROGRAM UNIT.

A synonym is an alias for a table, view, sequence or program unit.

A SEQUENCE generates a serial LIST of unique numbers for NUMERICAL COLUMNS of a DATABASE's tables.

A sequence generates a serial list of unique numbers for numerical columns of a database's tables.

• PROVIDE an additional level of table security, by restricting access to a predetermined set of rows and columns of a table.
• Hide data complexity.
• Simplify COMMANDS for the user.
• Present the data in a different PERSPECTIVE from that of the BASE table.
• Store COMPLEX queries.

Yes.

Yes.

A table is the basic unit of DATA STORAGE in an ORACLE database. The TABLES of a database hold all of the user ACCESSIBLE data. Table data is stored in ROWS and columns.

A table is the basic unit of data storage in an ORACLE database. The tables of a database hold all of the user accessible data. Table data is stored in rows and columns.

A VIEW is a virtual table. EVERY view has a Query ATTACHED to it. (The Query is a SELECT statement that IDENTIFIES the columns and rows of the table(s) the view uses).

A view is a virtual table. Every view has a Query attached to it. (The Query is a SELECT statement that identifies the columns and rows of the table(s) the view uses).

An Extent is a specific NUMBER of CONTIGUOUS data blocks, obtained in a single allocation, and USED to STORE a specific TYPE of information.

An Extent is a specific number of contiguous data blocks, obtained in a single allocation, and used to store a specific type of information.

An INDEX is an optional structure associated with a table to have direct ACCESS to rows, which can be created to increase the PERFORMANCE of DATA retrieval. Index can be created on one or more COLUMNS of a table.

An Index is an optional structure associated with a table to have direct access to rows, which can be created to increase the performance of data retrieval. Index can be created on one or more columns of a table.

An integrity CONSTRAINT is a declarative way to DEFINE a BUSINESS RULE for a column of a table.

An integrity constraint is a declarative way to define a business rule for a column of a table.

Clusters are GROUPS of one or more tables PHYSICALLY STORES together to share common columns and are often USED together.

Clusters are groups of one or more tables physically stores together to share common columns and are often used together.

DATA SEGMENT, INDEX Segment, ROLLBACK Segment and TEMPORARY Segment.

Data Segment, Index Segment, Rollback Segment and Temporary Segment.

Each DATABASES logically divided into one or more TABLESPACES one or more DATA files are explicitly created for each TABLESPACE.

Each databases logically divided into one or more tablespaces one or more data files are explicitly created for each tablespace.

Each INDEX has an Index SEGMENT that STORES all of its DATA.

Each Index has an Index segment that stores all of its data.

The set of Redo Log files YSDATE,UID,USER or USERENV SQL functions, or the pseudo COLUMNS LEVEL or ROWNUM.

The set of Redo Log files YSDATE,UID,USER or USERENV SQL functions, or the pseudo columns LEVEL or ROWNUM.

There are TWO TYPES of SYNONYMS PRIVATE and PUBLIC.

There are two types of Synonyms Private and Public.

UPDATE and DELETE Restrict - A REFERENTIAL integrity rule that disallows the update or deletion of referenced DATA. DELETE CASCADE - When a referenced row is DELETED all associated dependent rows are deleted.

UPDATE and DELETE Restrict - A referential integrity rule that disallows the update or deletion of referenced data. DELETE Cascade - When a referenced row is deleted all associated dependent rows are deleted.