Data Item

Record Occurence

Record

Record Type

Areas

Record Occurence

Record Type

Data Item

True

False

A view can be created as read only.

A view can be created as a join on two or more tables. AND Insert and delete operations cannot be performed on views using functions

A view cannot have an ORDER BY clause in the SELECT statement.

A view cannot be created with a GROUP BY clause in the SELECT statement.

Both tables have NULL values.

You want all unmatched data from one table.

You want all matched data from both tables.

You want all unmatched data from both tables.

One of the tables has more data than the other.

TRUNCATE is a DDL command whereas DELETE is a DML command

TRUNCATE is much faster than DELETE

In case of TRUNCATE ,Trigger doesn't get fired.But in DML commands like DELETE .Trigger get fired

All of the above

TRUNCATE is a DDL command whereas DELETE is a DML command

TRUNCATE is much faster than DELETE

In case of TRUNCATE ,Trigger doesn't get fired.But in DML commands like DELETE .Trigger get fired

All of the above

USER_TAB_PRIVS_MADE

USER_TAB_PRIVS_RECD

USER_COL_PRIVS_MADE

USER_COL_PRIVS_RECD

A. ASEC

B. DESC

C. REVERT

D. ASC

Both B and D

Both A and B

WHERE

HAVING

RESTRICT

ORDER BY

GROUP BY

Both A and B

A. MERGE INTO <> USING <> WHEN MATCHED THEN UPDATE ------ WHEN NOT MATCHED THEN INSERT -------

B. MERGE <> USING <> WHEN MATCHED THEN UPDATE ------ WHEN NOT MATCHED THEN INSERT -------

C. MERGE INTO <> USING <> WHEN EXISTS THEN UPDATE ------

D. MERGE INTO <> USING <> WHEN NOT MATCHED THEN INSERT ------

Both A and D

A. You use a NEXTVAL pseudo column to look at the next possible value that would be generated from a sequence, without actually retrieving the value

B. You use a CURRVAL pseudo column to look at the current value just Generated from a sequence, without affecting the further values to be generated from the sequence.

You use a NEXTVAL pseudo column to obtain the next possible value from a sequence by actually retrieving the value from the sequence

Both A and B

Use the DESCRIBE command in the EMP_DEPT VU view.

Use the DEFINE VIEW command on the EMP_DEPT VU view

Use the DESCRIBE VIEW command on the EMP_DEPT VU view

Query the USER_VIEWS data dictionary view to search for the EMP_DEPT_VU view

NOT NULL and PRIMARY KEY

PRIMARY KEY and UNIQUE key

FOREIGN KEY and PRIMARY KEY

CHECK

UNIQUE

0

NULL

0.1

NA

ALTER VIEW emp_dept_vu (ADD manager_id NUMBER);

MODIFY VIEW emp_dept_vu (ADD manager_id NUMBER);

ALTER VIEW emp_dept_vu AS SELECT employee_id, employee_name, department_name, manager_id FROM employee e, departments d WHERE e.department_id = d.department_id;

CREATE OR REPLACE VIEW emp_dept_vu AS SELECT employee_id, employee_name, department_name, manager_id FROM employees e, departments d WHERE e.department_id = d.department_id;

A.SHOW ERRORS

B. Query the USER_ERRORS data dictionary view

Both A and B

None of the above

1. Bit map indexes are used on low-cardinality columns(having low distinct values) 2.B-tree indexes are most effective for high-cardinality data(only for unique columns)

B-tree indexes cannot be used in environments typically have large amounts of data and ad hoc queries

bitmap indexes can be created on partitioned tables

All of the above

True

False

Indexes

tables

public synonyms

triggers

packages