An ORDER BY clause always sorts NULL values last.

An ORDER BY clause can perform a binary sort

An ORDER BY clause can perform a linguistic sort

By default an ORDERBY clause sorts rows in ascending order

An ORDR BY clause will always precede a HAVI NG clause if both are used in the same top-level

UPDATE can be granted only on tables and views.

DELETE can be granted on tables, views, and sequences.

REFERENCES can be granted only on tables and views.

INSERT can be granted on tables, views, and sequences.

SELECT can be granted only on tables and views.

ALTER can be granted only on tables and sequences.

SELECT customer_ name FROM customers WHERE customer_ name LIKE ' % a % ’ ;

SELECT customer_ name FROM customers WHERE customer name LIKE 'Ma%' ;

SELECT customer_ name FROM customers WHERE customer_ name='*Ma*';

SELECT customer_ name FROM customers WHERE UPPER (customer_ name ) LIKE 'MA*. ;

SELECT customer_ name FROM customers WHERE customer name LIKE 'Ma*';

SELECT customer_ name FROM customers WHERE UPPER (customer name) LIKE 'MA&';

SELECT customer_ name FROM customers WHERE customer_ name KIKE .*Ma*';

A ROLLBACK statement can be used to retrieve the deleted data.

It drops any triggers defined on the table.

It retains the indexes defined on the table.

It retains the integrity constraints defined on the table,

It always retains the space used by the removed rows.

A FLASHBACK TABLE statement can be used to retrieve the deleted data.

A primary key column referenced by another column as a foreign key can be dropped if using the CASCADE option.

A DROP COLUMN command can be rolled back.

An UNUSED column's space is remained automatically when the block containing that column is next queried.

An UNUSED column's space is remained automatically when the row containing that column is next queried.

Partition key columns cannot be dropped.

A column that is set to NNUSED still counts towards the limit of 1000 columns per table.

providing graphical capabilities

providing variable definition capabilities.

providing database transaction control

processing sets of data

providing update capabilities for data in external files

The owner of an object acquires all object privilege on that object by default.

The WITH GRANT OPTION clause can be used only by DBA users.

A table owner must grant the references privilege to allow other users to create FOREIGN KEY constraints using that table.

An object privilege can be granted to a role only by the owner of that object.

An object privilege can be granted to other users only by the owner of object.

A VARCHAR2 blank pads column values only if the data stored is non numeric and contains no special characlers

A BFILE stores unstructured binary data in operating systerm files

A CHAR column definition does not require the length to be specified

The default length for a CHAR column is always one character

A VARCHAR2 column definition does not require the length to be specified

A BLOB stores unstructured binary data within the database

SELECT * FROM employees WHERE salary+NULLF(commission,0)>=20000;

SELECT * FROM employees WHERE salary+NVL2(commission,commission,0)>=20000;

SELECT * FROM employees WHERE NVL2(salary)+commission,salary+commission,

SELECT * FROM employees WHERE salary+NVL(commission,0)>=20000;

SELECT * FROM employees WHERE NVL(salary+commission,0)>=20000;

SELECT * FROM employees WHERE NVL(salary+commission,0)>==20000;

Views can be indexed.

Theethi CHEcK clause prevents certalin rows from being updated or inserted in the underying table through the view.

Tables in the defining query of a view must always exist in order to create the view.

Views can be updated without the need to re-grant privileges on the view.

The wITH CHECK clause prevents certain rows from being displayed when querying the view.

The WHERE clause can be used to exclude rows after dividing them into groups

WHERE and HAVING clauses can be used in the same statement only if applied to different table columns.

The HAVING clause can be used with aggregating functions in subqueries.

Aggregating functions and columns used in HAVING clauses must be specified in these SELECT list of a query.

The WHERE clause can be used to exclude rows before dividing them into groups.

It can be used from SQL Developer.

It can be used to display the structure of an existing view.

It can be used only from SQL*Plus.

It displays the NOT NULL constraint for any columns that have that constraint.

It displays all constraints that are defined for each column.

It displays the PRIMARY KEY constraint for any column or columns that have that constraint.

CREATE SEQUENCE emp_seq START WITH 1 INCRENENT BY 1 NOCACHE;

CREATE SEQUENCE emp_seq START WITH 1 INCREMENT BY 1 CYCLE;

CREATE SEQUENCE emp_seq NOCACHE;

CREATE SEQUENCE emp_seq START WITH 1 CACHE;

CREATE SEQUENCE emp_seq START WITH 1 INCREMENT BY 1 CACHE;

CREATE SEQUENCE emp_seq;

Roles are assigned to roles using the ALTER ROLE Statement

A role is a named group of related privileges that can only be assigned to a user

Roles are assigned to users using the ALTER USER statement

A single role can be assigned to multiple users.

A single user can be assigned multiple roles

Privileges are assigned to a role using the ALTER ROLE statement.

Privileges are assigned to a role using the GRANT statement.

SELECT NULLIF(100, 100) FROM DUAL；

SELECT COALESCE(100, NULL, 200) FROM DUAL；

SELECT NULLIF(100, 'A') FROM DUAL；

SELECT NULLIF(NULL, 100) FROM DUAL；

SELECT COALESCE(100, 'A' ) FROM DUAL；

a table

an attribute

a unique identifier

an activity

a relationship

an entity

WHERE TO_NUMBER(start_date - SYSDATE)<=25

WHERE ADD_MONTHS (start date , 25)<= SYSDATE

WHERE MONTHS_BETWEEN(SYSDATE, start_date)<=25

WHERE MONTHS_BETWEEN (start_date, SYSDATE)<=25

DDL statements automatically commit only data dictionary updates caused by executing the DDL.

A DDL statement issued by a session with an uncommitted transation automaticall commits that transaction.

An uncommitted transaction is automatically committed when the user exits SQL*PLUS

DML statements always start new transactions.

A session can see uncommitted updates made by the same user in a different session

An uncommitted transaction commits automatically if the user exits SQL*Plus

Data Manipulation Language (DML) statements always start a new transaction.

A user can always see uncommitted updates made by the same user in a different session.

A Data Definition Language (DDL) statement does a commit automatically only for the data dictionary updates caused by the DDL

A session can always see uncommitted updates made by itself.

If a session has an uncommitted transaction, then a DDL statement issue a COMMIT before starting a new transaction.

intersect ignores nulls.

Reversing the order of the intersected tables can sometimes affect the output.

Column names in each select in the compound query can be different.

intersect returns rows common to both sides of the compound query.

The number of columns in each select in the compound query can be different.

A substitution variable used to prompt for a column name must be endorsed in single quotation marks.

A substitution variable used to prompt for a column name must be endorsed in double quotation marks.

A substitution variable prefixed with & always prompts only once for a value in a session.

A substitution variable can be used with any clause in a SELECT statement.

A substitution variable can be used only in a SELECT statement.

A substitution variable prefixed with 6 prompts only once for a value in a session unless is set to undefined in the session.

delete statements can remove multiple rows based on multiple conditions.

insert statements can insert nulls explicitly into a column.

insert into. . .select. . .from statements automatically commit.

DML statements require a primary key be defined on a table.

update statements can have different subqueries to specify the values for each updated column.

WHERE ordet_date> TO_CHAR(ADD_MONTHS(SYSDATE, 6),'MON DD YYYY')

WHERE TO_CHAR(order_date,'MON DD YYYY') ='JAN 20 2019';

WHERE order_date> TO_DATE('JUL 10 2018','MON DD YYYY');

WHERE order_date IN (TO_DATE ('Oct 21 2018','MON DD YYYY'), TO_CHAR('Nov 21 2018','MON DD YYYY'));

WHERE order_date> TO_DATE(ADD_MONTHS(SYSDATE,6),'MON DD YYYY');

INTERVAL YEAR TO MONTH columns only support monthly intervals within a range of years.

The value in an INTERVAL DAY TO SECOND column can be copied into an INTERVAL YEAR TO MONTH column.

INTERVAL YEAR TO MONTH columns only support monthly intervals within a single year.

The YEAR field in an INTERVAL YEAR TO MONTH column must be a positive value.

INTERVAL DAY TO SECOND columns support fractions of seconds.

INTERVAL YEAR TO MONTH columns support yearly intervals.

All remaining employee names will appear in an ascending order

The names of employees remaining the maximum salary will appear first in an ascending order

All remaining employee names will appear in ascending order

All remaining employee names will appear in descending order

The names of employees maximum salary will appear fist to descending order

The names of employees maximum salary will appear fist to ascending order

MERGE INTO new_prices n

USING(SELECT*FROM products)p

WHEN MATECHED THEN

UPDATE SET n.price=p.cost*.01

WHEN NOT MATCHED THEN

INSERT(n.prod_id,n.price)VALUES (p.prod_id,cost*01)

WHERE(p.cost<200);

MERGE INTO new_prices n

USING(SELECT*FROM product WHERE cost>150) p

ON (n.prod_id=p.prod_id)

WHEN NATCHED THEN

DELETE WHERE(p.cost<200)

WHEN NOT MATCHED THEN

INSERT (n.prod_id,n.price)VALUES (p.prod_id,p.cost*.01);

MERGE INTO new_prices n

USING (SELECT * FROM products WHERE cost>150) p

ON (n.prod_id=p.prod_id)

WHEN NATCHED THEN

UPDATE SET n.price=p.cost*.01

DELETE WHERE (p.cost<200);

MERGE INTO new_prices n

USING products p

WHEN NOT NATCHED THEN

INSERT (n.prod_id, n.price)VALUES (p.prod_id,cost*.01)

WHERE (p.cost <200);

It guarantees atomicity, consistency, isolation, and durability (ACID) features

It best supports relational databases

It is used to define encapsulation and polymorphism for a relational table

It requires that data be contained in hierarchical data storage

It is the only language that can be used for both relational and object-oriented databases

It provides independence for logical data structures being manipulated from the underlying physical data storage

SELECT SYSDATE-TO_DATE ('01-JANUARY-2019') FROM DUAL;

SELECT TO_DATE (SYSDATE, 'DD/MONTH/YYYY')-'01/JANUARY/2019' FROM DUAL;

SELECT ROUND (SYSDATE-TO_DATE ('01/JANUARY/2019')) FROM DUAL;

SELECT TO_CHAR (SYSDATE, 'DD-MON-YYYY')-'01-JAN-2019' FROM DUAL;

SELECT ROUND (SYSDATE- '01-JAN-2019') FROM DUAL:

the result of a delete can be undone by issuing a rollback

delete can use a where clause to determine which row(s) should be removed.

TRUNCATE can use a where clause to determine which row(s) should be removed.

truncate leavers any indexes on the table in an UNUSABLE STATE.

the result of a truncate can be undone by issuing a ROLLBACK.

DELETE can be granted on tables, views, and sequences.

REFERENCES can be grantrd only on tables.

INSERT can be granted only on tables and sequences.

SELECT can be granted on tables, views, and sequences.

ALTER can be granted only on tables and sequences.

The primary key constraint will be enabled and DEFERRED.

The primary key constraint will be enabled and IMMEDIATE.

The foreign key constraint will be disabled.

The foreign key constraint will be enabled and DEFERRED.

The foreign key constraint will be enabled and IMMEDIATE.

SALES1 is created with 1 row.

SALES1 has PRIMARY KEY and UNIQUE constraints on any selected columns which had those constraints in the SALES table.

SALES1 Is created with 5,000 rows.

SALES1 has NOT NULL constraints on any selected columns which had those constraints in the SALES table.

ORDER BY NVL(enam,0) DESC, ename

ORDER BY NVL(comm,0) ASC NULLS FIRST, ename

ORDER BY NVL(comm,0) ASC NULLS LAST, ename

ORDER BY comm DESC NULLS LAST, ename

You cannot correlate them with a table in the parent statement

You can use them as a default value for a column.

.You must enclose them in parentheses.

They can return at most one row.

They can return two columns.

The Oracle join syntax only supports right outer joins,

The Oracle join syntax supports creation of a Cartesian product of two tables.

The SQL:1999 compliant ANSI join syntax supports natural joins.

The Oracle join syntax supports natural joins.

The Oracle join syntax performs better than the SQL:1999 compliant ANSI join syntax.

The SQL:1999 compliant ANSI join syntax supports creation of a Cartesian product of two tables.

The Oracle join syntax performs less well than the SQL:1999 compliant ANSI Join Answer.

SELECT department_id, COUNT (*)

FROM employees

HAVING department_ id <> 90 AND COUNT(*) >= 3

GROUP BY department_id;

SELECT department_id, COUNT (*)

FROM employees

WHERE department_ id <> 90 AND COUNT(*) >= 3

GROUP BY department_id;

SELECT department_id, COUNT(*)

FROM employees

WHERE department_id <> 90 HAVING COUNT(*) >= 3

GROUP BY department_id;

SELECT department_id, COUNT(*)

FROM employees

WHERE department_id <> 90 GROUP BY department_id

HAVING COUNT(*) >= 3;

Statement 2 returns only one row of output.

Both the statement given the same output.

Both statements will return NULL if either UNIT PRICE or QUANTITY contains NULL,

Statement 2 may return multiple rows of output.

Statement 1 returns only one row of output.

PRODUCT_ID can be assigned the PEIMARY KEY constraint.

EXPIRY_DATE cannot be used in arithmetic expressions.

EXPIRY_DATE contains the SYSDATE by default if no date is assigned to it

PRODUCT_PRICE can be used in an arithmetic expression even if it has no value stored in it

PRODUCT_PRICE contains the value zero by default if no value is assigned to it.

PRODUCT_NAME cannot contain duplicate values.

CURRENT DATE

CURRENT_ TIMESTAMP

SYSDATE

LOCALTIMESTAMP

SELECT COALESCR('DATE', SYSDATE) FROM DUAL;

SELECT NVL('DATE',SYSDATE) FROM DUAL;

SELECT COALESCE(O,SYSDATE) TRCH DUAL;

SELECT NVL('DATE',200) FROM (SELECT NULL AS “DATE” FROM DUAL);

SELECT COALESCE('DATE',SYSDATE) FROM (SELECT NULL AS “DATE” FROM DUAL) ;

ORDERBY 2, 1

ORDER BY "CUST_NO"

ORDER BY 2,cust_id

ORDER BY CUST_NO

ORDER BY "Last Name"

WITH CHECK clause has no effect when deleting rows from the underlying table through the view.

Insert statements can always be done on a table through a view.

Views cannot be used to add rows to an underlying table if the table has columns with NOT NULL constraints lacking default values which are not referenced in the defining query of the view.

Views cannot be used to add or modify rows in an underlying table if the defining query of the view contains the DISTINCT keyword.

Delete statements can always be done on a table tough a view.

Views cannot be used to query rows from an underlying table if the table has a PRIMARY KEY and the PRIMARY KEY columns are not referenced in the defining query of the view.

You must have ANY TABLE system privileges, or be granted object privilges on the table, to viewa tabl e in DBA TABLES.

USER TABLES displays all tables owned by the current user.

You must have ANY TABLE system privileges, or be granted object privileges on the table, to view a table in USER_TABLES.

ALL TABLES displays all tables owned by the current user.

You must have ANY TABLE system privileges, or be granted object privileges on the table, to view a table in ALL_TABLES.

All users can query DBA_TABLES successfully.

Numeric values are displayed in descending order if they have decimal positions.

Only columns that are specified in the SELECT list can be used in the ORDER BY cause.

NULLS are not included in the sort operation.

Column aliases can be used In the ORDER BY cause.

Ina character sort, the values are case-sensitive.