A table can have only one primary key but multiple foreign keys.

It is possible for child rows that have a foreign key to remain in the child table at the time the parent row is deleted.

Primary key and foreign key constraints can be defined at both the column and table level.

Only the primary key can be defined the column and table level.

It is possible for child rows that have a foreign key to be deleted automatically from the child table at the time the parent row is deleted.

The foreign key columns and parent table primary key columns must have the same names.

A table can have only one primary key and one foreign key.

It contains the object privileges granted to other users by the current user session.

It contains the system privileges granted to other users by the current User session.

It contains the current system privileges available in the user session.

It contains the current object privileges available in the user session.

quantity

quantity, unit_price

total_paid

product_id

quantity * unit_price

When the session logs out is successfully

When a DBA issues a successful SHUTDOWN IMMEDIATE statement and the user then issues a COMMIT

When a CREATE INDEX statement is executed successfully in same session

When a COMMIT statement is issued by the same user from another session in the same database instance

When a CREATE TABLE AS SELECT statement is executed unsuccessfully in the same session

When a DBA issues a successful SHUTDOWN TRANSACTIONAL statement and the user, then issues a COMMIT

The grantee can grant the object privilege to any user in the database, with of without including this option.

The grantee must have the GRANT ANY OBJECT PRIVILEGE system prvilege to use this option.

It can be used when granting privileges to roles.

It can be used for system and object privileges.

It cannot be used to pass on privileges to PUBLIC by the grantee.

It can be used to pass on privileges to other users by the grantee.

The join key column must have an index.

It can be a left outer join.

It must be a full outer join.

It can be an inner join.

It must be an equijoin.

CONCAT: can be used to combine any number of values

FLOOR: returns the smallest integer greater than or equal to a specified number

CEIL: can be used for positive and negative numbers

TRUNC: can be used with NUMBER and DATE values

MOD: returns the quotient of a division operation

Option A

Option B

Option C

Option D

SELECT book_title FROM books WHERE (price< 500 OR >1000) AND (purchase date< '17-JAN-2007') ORDER BY purchase date DESC;

SELECT book_title FROM books WHERE (price IN (500, 1000)) AND (purchase date < '17-JAN-2007') ORDER BY purchase_date ASC;

SELECT book_title FROM books WHERE (price NOT BETWEEN 500 AND 1000) AND (purchase_date< '17-JAN-2007') ORDER BY purchase_date DESC;

SELECT book_title FROM books WHERE (price BETWEEN 500 AND 1000) AND (purchase_date<'17-JAN-2007') ORDER BY purchase_date;

They are always equijoins.

They require the NOT EXISTS operator in the join condition.

They have no join condition.

They can use INNER JOIN and LEFT JOIN.

They require table aliases.

They require the EXISTS opnrator in the join condition.

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.

It executes successfully but does not give the required result.

It gives an error because the ALL keyword is not valid.

It gives an error because the GROUP BY clause is not valid

It executes successfully and gives the required result.

Base tables in the data dictionary have the prefix DBA_.

All user actions are recorded in the data dictionary.

The data dictionary is constantly updated to reflect changes to database objects, permissions, and data.

All users have permissions to access all information in the data dictionary by default

The SYS user owns all base tables and user-accessible views in the data dictionary.

A create table statement can specify the maximum number of rows the table will contain.

The same table name can be used for tables in different schemas.

A system privilege is required.

Creating an external table will automatically create a file using the specified directory and file name.

A primary key constraint is manadatory.

The PROD ID column can be renamed.

The PROD_ ID column data type can be changed to VARCHAR2 (2).

The EXPIRY DATE column data type can be changed to TIME STAMP.

The EXPIRY DATE column cannot be dropped.

The PROD NAME column cannot have a DEFAULT clause added to it.

SELECT to_date(' 2019-01-01 ', 'YYYY -MM-DD' ) FROM DUAL;

SELECT DATE '2019-01-01' FROM DUAL ;

SELECT TO_CHAR('2019-01-01') FROM DUAL; 2019-01-01

SELECT '2019-01-01' FROM DUAL ; 2019-01-01

SELECT TO_ DATE('2019-01-01') FROM DUAL;

Foreign key columns allow null values.

Unique key columns allow null values

Primary key columns allow null values.

Every primary or unique key value must refer to a matching foreign key value.

Every foreign key value must refer to a matching primary or unique key value.

The MGR column in the DEPT table will not be able to contain NULL values.

The CREATE TABLE EMP statement must precede the CREATE TABLE DEPT statement for all threestatements to execute successfully.

Both foreign key constraint definitions must be removed from the CREATE TABLE statements, andbe added with ALTER TABLE statements once both tables are created, for the two CREATE TABLEstatements to

execute successfully in the order shown.

The DEFT FKEY constraint definition must be removed from the CREATE TABLE DEF statement.and be added with an AITER TABLE statement once both tables are created, for the two CREATE TABLE statements

to execute successfully in the order shown.

The Deptno column in the emp table will be able to contain nulls values.

All three statements execute successfully in the order shown

SELECT ”

FROM employees

WHERE salary > ANY

SELECT AVG (salary)

EROM employees

GROUP BY department_ id);

SELECT

FROM employees

WHERE salary > AVG (salary) OVER (PARTITION BY department _ id);

SELECT”

FROM employees e1

WHERE salary >!

SELECT AVG (salary)

FROM employees e2

WHERE e1. Department _id = e2, department_ id

SELECT.

FROM

SELECT e.", AVG (salary) OVER (PARTITION BY department id) avg_ sal

FROM employees e

WHERE salary > avg_ sal;

SELECT”

FROM employees

WHERE salary >

( SELECT AVG

(salary) FROM

employees

GROUP BY department _ id

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.

THEY CAN BE USED in the where clause.

A SQL STATEMENT MAY HAVE MULTIPLE SINGLE ROW SUBQUERY BLOCKS.

THEY MUST BE PLACED ON THE RIGHT SIDE OF THE COMPARISON OPERATOR OR CONDITION.

they must be placed on the left side of the comparison operator or condition.

THEY CAN BE USED IN THE HAVING CLAUSE

they must return a row to prevent errors in the SQL statement.

They can be referenced In the where clause of an update or debete statement.

They can be referenced in the set clause of an update statement as the name of the column To be updated.

They can be indexed.

They cannot have a data type explicitly specified.

They can be referenced in the column expression of another virtxial column.

A create table statement can specify the maximum number of rows the table will contain.

The same table name can be used for tables in different schemas.

A system privilege is required.

Creating an external table will automatically create a file using the specified directory and file name.

A primary key constraint is manadatory.

1 and 3

1, 2 and 3

2 and 3

1 and 2

SELECT cust_first_name, cust_credit_limit * . 05 AS DUE AMOUNT

FROM customers

WHERE cust income_level !=NULL

AND cust credit_level !=NULL;

SELECT cust_first_name, cust_credit_limit * . 05 AS DUE AMOUNT

FROM customers

WHERE cust income_level IS NOT NULL

AND due_amount IS NOT NULL;

SELECT cust_first_name, cust_credit_limit * . 05 AS DUE AMOUNT

FROM customers

WHERE cust income_level <> NULL

AND due_amount <> NULL;

SELECT cust_first_name, cust_credit_limit * . 05 AS DUE AMOUNT

FROM customers

WHERE cust_income_level IS NOT NULL

AND cust_credit_limit IS NOT NULL;

SELECT cust_first_name, cust_credit_limit * . 05 AS DUE AMOUNT

FROM customers

WHERE cust income_level !=NULL

AND due_amount !=NULL;

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

TO_NUMBER(PROMO_BEGIN_DATE)-5 will return number

TO_DATE(PROMO_BEGIN_DATE * 5) will return a date

PROMO_BEGIN_DATE-SYSDATE will return a number.

PROMO_BEGIN_DATE-5 will return a date.

PROMO_BEGIN_DATE-SYSDATE will return an error.

A full outer join returns matched and unmatched rows.

A full outer join must use Oracle syntax.

Outer joins can be used when there are multiple join conditions on two tables.

Outer joins can only be used between two tables per query.

An inner join returns matched rows.

A left or right outer join returns only unmatched rows.

Regardless of salary,only if the employee id is less than 125,insert EMPLOYEE_ID,NANAGER_ID,SALARY into the MGR_HISTORY table.

If the salary is more than 20000 and the employee is less than 125,insert EMPLOYEE_ID and SALARY into the SPECIAL_SAL table.

Only if the salary is 20000 or less and the employee id is less than 125,insert EMPLOYEE_ID,MANAGER_ID,and SALARY into the MGR_HISTORY table.

Regardless of salary and employee id,insert EMPLOYEE_ID,MANAGER_ID,and SALARY into the MGR_HISTORY table.

If the salary is 20000 or less and the employee id is less than 125,insert EMPLOYEE_ID,HIRE_DATE,and SALARY into the SAL_HISTORY table.

Only if the salary is 20000 or less and the employee id is 125 or higher,insert EMPLOYEE_ID,MANAGER_ID,and SALARY into the MDR_HISTORY table.

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

GRANT UPDATE (title, address) ON customers TO andrew WITH ADMIN OPTION;

GRANT UPDATE ON customers. title, customers.address TO andrew WITH GRANT OPTION;

GRANT UPDATE ON customers.title, customers.address TO andrew WITH ADMIN OPTION;

GRANT UPDATE (title, address) ON customers TO andrew;

GRANT UPDATE ON customers. title, customers.address TO andrew;

GRANT UPDATE (title, address) ON customers TO andrew WITH GRANT OPTION:

SELECT produet_id, unit_pricer, 5 "Discount",unit_price+surcharge-discount FROM products;

SELECT product_id, (unit_price * 0.15 / (4.75 + 552.25)) FROM products;

SELECT ptoduct_id, (expiry_date-delivery_date) * 2 FROM products;

SPLECT product_id, expiry_date * 2 FROM products;

SELEGT product_id, unit_price, unit_price + surcharge FROM products;

SELECT product_id,unit_price || "Discount", unit_price + surcharge-discount FROM products;

SELECT prod_id ||q’(‘ s not available)’ ‘CURRENT AVAILABILITY’ FROM

product_ status WHERE status = ‘OUT OF STOCK’

SELECT prod_id ||q”‘ s not available” FROM

product_ status WHERE status = ‘OUT OF STOCK’;

SELECT PROD_ID||q’(‘s not available)’ FROM

product_ status WHERE status = ‘OUT OF STOCK’;

SELECT PROD_ID||q’(‘s not available)’ “CURRENT AVAILABILITY”

FROM product_ status WHERE status = ‘OUT OF STOCK’;

SELECT prod_id q’s not available” from product_ status WHERE status = ‘OUT OF STOCK’;

SELECT prod_id “CURRENT AVAILABILITY”||q’ (‘s not available)’ from product_ status WHERE status

= ‘OUT OF STOCK’;

a table

an attribute

a unique identifier

an activity

a relationship

an entity

the DEFAULT DIRECTORY clause

the REJECT LIMIT clause

the LOCATION clause

the ACCESS PARAMETERS clause

the access driver TYPE clause

MERGE INTO employees e

USING new employees ne

WHERE e.employee_id = ne.employee_ id

WHEN MATCHED THEN

UPDATE SET e.name = ne.name, e.job_id = ne.job_id,e.salary =ne. salary

WHEN NOT MATCHED THEN

INSERT VALUES (ne. employee_id,ne.name, ne.job_id,ne.salary) ;

MERGE INTO employees e

USING new_employees n

ON (e.employee_id = ne.employee_id)

WHEN MATCHED THEN

UPDATE SET e.name = ne.name, e.job id = ne.job_id,e.salary =ne. salary

WHEN NOT MATCHED THEN

INSERT VALUES (ne. employee_id,ne.name,ne.job_id,ne.salary);

MERGE INTO employees e

USING new employees ne

ON (e.employee_id = ne.employee_id)

WHEN FOUND THEN

UPDATE SET e.name =ne.name, e.job_id=ne.job_id, e.salary =ne.salary

WHEN NOT FOUND THEN

INSERT VALUES (ne.employee_id,ne.name,ne.job_id,ne.salary) ;

MERGE INTO employees e

USING new_employees n

WHERE e.employee_id = ne.employee_id

WHEN FOUND THEN

UPDATE SET e.name=ne.name,e.job_id =ne.job_id, e.salary=ne.salary

WHEN NOT FOUND THEN

INSERT VALUES (ne.employee_ id,ne.name,ne.job id,ne.salary) ;

SELECT TO _ CHAR (SYSDATE, ' FMDAY, DD MONTH, YYYY') FROM DUAL;

SELECT TO _ DATE (SYSDATE, ' FMDAY, DD MONTH, YYYY') FROM DUAL;

SELECT TO_ CHAR (SYSDATE, ' FMDD, DAY MONTH, YYYY') FROM DUAL;

SELECT TO_ CHAR (SYSDATE, ' FMDAY, DDTH MONTH, YYYY') FROM DUAL;

The subquery is executed before the UPDATE statement is executed.

All existing rows in the ORDERS table are updated.

The subquery is executed for every updated row in the ORDERS table.

The UPDATE statement executes successfully even if the subquery selects multiple rows.

The subquery is not a correlated subquery.

Creating an external table creates a directory object.

When creating an external table, data can be selected only from a table whose rows are stored in database blocks.

When creating an external table, data can be selected from another external table or from a table whose rows are stored in database blocks.

Creating an external table creates a dump file that can be used by an external table in the same or a different database.

Creating an external table creates a dump file that can be used only by an external table in the same database.

SELECT * FROM customers WHERE TO_ CHAR (customer_ id) = '0001';

SELECT * FROM customers WHERE customer id = '0001';

SELECT * FROM customers WHERE customer_ id = 0001;

SELECT FROM customers WHERE insert date = '01-JAN-19';

SELECT. FROM customers WHERE insert_ date = DATE *2019-01-01';

SELECT. FRON customers WE TO DATE (Insert _ date) = DATE ‘2019-01-01’;

A synonym can have a synonym.

All private synonym names must be unique in the database.

Any user can create a PUBLIC synonym.

A synonym can be created on an object in a package.

A synonym has an object number.

All column names in a USING clause must be qualified with a table name or table alias.

It can never be used with onatural join.

It is used to specify an equijoin of columns that have the same name in both tables.

It can never be used with a full outer join.

It is used to specify an explicit join condition involving operators.

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.

INTERSECT ignores NULLs

SELECT TO_DATE(TO_NUMBER(INTERVATL '800' SECOND)) FROM DUAL;

SELECT TO_NUMBER(INTERVAL'800' SECOND, 'HH24:MM') FROM DUAL;

SELECT TO_DATE(INTERVAL '800' SECOND,'HH24:MM') FROM DUAL;

SELECT TO_NUWBER(TO_DATE(INTERVAL '800' SECOND)) FROM DUAL;

SELECT TO_CHAR(INTERVAL '800' SECOND, 'HH24:MM') FROM DUAL;

Line 7

Line 8

Line 3

Line 5

The NEW_SALES table would not get created because the DEFAULT value cannot be specified in the column definition.

The NEW_SALES table would get created and all the NOT NULL constraints defined on the specified columns would be passed to the new table.

The NEW_SALES table would not get created because the column names in the CREATE TABLE command and the SELECT clause I do not match.

The NEW_SALES table would get created and all the FOREIGN KEY constraints defined on the specified columns would be passed to the new table

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');

INSERT INTO rate_list VALUES (-.9) inserts the value as -.9.

INSERT INTO rate_list VALUES (0.999) produces an error.

INSERT INTO rate_list VALUES (-10) produces an error.

INSERT INTO rate_list VALUES (87654. 556) inserts the value as 87654.6.

INSERT INTO rate_list VALUES (0.551) inserts the value as .55.

INSERT INTO rate_list VALUES (-99.99) inserts the value as 99.99.

Drop pseudo columns from a table.

Restrict all DML statements on a table.

Drop all columns simultaneously from a table.

Lock a set of rows in a table CE Rename a table.

Rename a table

Enable or disable constraints on a table.

SELECT last_name, salary

FROM employees

WHERE ROWNUM<=3

SELECT last_name,salary

FROM employees

ORDER BY salary

FETCH FIRST 3 ROWS ONLY;

SELECT last_name,salary

FROM employees

WHERE ROWNUM<=3

ORDER BY (SELECT salary FROM employees);

SELECT last_name,salary

FROM (SELECT * FROM employees ORDER BY salary)

SELECT last_name,salary

FROM employees

FETCH FIRST 3 ROWS ONLY

ORDER BY salary;

NULLS are not ignored during duplicate checking.

Duplicates are eliminated automatically by the UNION ALL operator

The names of columns selected in each SELECT statement must be identical.

The number of columns selected in each SELECT statement must be identical

The output is sorted by the UNION ALL operator.

A customer can exist in many countries.

The statement will fail if a row already exists in the SALES table for product 23.

The statement will fail because subquery may not be I contained in a values clause.

The SALES table has five foreign keys.

The statement will execute successfully and a new row will be inserted into the SALES table.

A product can have a different unit price at different times.

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

The WITH CHECK clause prevents certain rows from being updated or inserted.

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

Date Manipulation Language (DML) can always be used on views.

Deleting one or more rows using a view whose defining query contains a GROUP BY clause will cause an error.

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

Inserting one or more rows using a view whose defining query contains a GROUP BY clause will cause an error.

It fails unless the expression is modified to TO-CHAR(SUNBSTR(SYSDATE,1,5)

It fails unless the expression is modified to SUBSTR (TO_ CHAR(SYSDATE),1,5)

It fails unless the expression is modified to SUBSTR (TO_ CHAR(TRUNC(SYSDATE)),1,5)

It executes successfully with an implicit data type conversion

SELECT 'The first_name is '' || first_name || '' FROM employees ;

SELECT 'The first_name is '''||first_name ||'''' FROM employees ;

SELECT 'The first_name is ''' ||first_name||''' FROM employees ;

SELECT 'The first_name is '|| first_name|| '' FROM employees;

SELECT 'The first_name is \'' || first_name || '\'' FROM employees;

It displays values for variables created by the DEFINE command.

It can be used in SQL Developer and SQL*Plus.

It can be used only in SQL*plus.

It displays values for variables prefixed with &&.

It displays values for variables used only in the WHERE clause of a query.

A table can have multiple primary keys.

A table can have multiple foreign keys.

A NUMBER column without data has a zero value.

A column definition can specify multiple data types.

A VARCHAR2 column without data has a NULL value.

The first expression in NVL2 is never returned.

NVL2 can have any number of expressions in the list.

COALESCE stops evaluating the list of expressions when it finds the first null value.

COALESCE stops evaluating the list of expressions when it finds the first non-null value.

NVL must have expressions of the same data type.

NVL can have any number of expressions in the list.

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.

Roles are assigned to roles using the ALTER ROLE statement.

A single user can be assigned multiple roles.

Roles are assigned to users using the ALTER USER statement.

A single role can be assigned to multiple users.

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

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

Privileges are assigned to a role using the GRANT statement.

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

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.

The code for pen is 10.

There is no row containing fountain pen.

There is no row containing pencil.

The code for pen is 1.

The code for fountain pen is 3

There is no row containing pen

The DESCRIBE command displays unused columns

A primary key column cannot be set to unused.

A query can return data from unused columns, but no DML is possible on those columns.

Once a column has been set to unused, a new column with the same name can be added to the table.

A foreign key column cannot be set to unused.

Unused columns retain their data until they are dropped

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;

SELECT shape FROM bricks JOIN boxes ON weight >= min_weight AND weight < max_weight;

SELECT shape FROM bricks JOIN boxes ON weight > min_weight;

SELECT shape FROM bricks JOIN boxes ON weight BETWEEN min_weight AND max_weight;

SELECT shape FROM bricks JOIN boxes ON weight < max_weight;

SELECT shape FROM bricks JOIN boxes ON NOT (weight > max_weight);

CONCAT joins two or more character strings together.

FLOOR returns the largest integer less than or equal to a specified number.

CONCAT joins two character strings together.

INSTR finds the offset within a string of a single character only.

INSTR finds the offset within a character string, starting from position 0.

FLOOR returns the largest positive integer less than or equal to a specified number.

SELECT * FROM customers WHERE city ='D_%';

SELECT * FROM customers WHERE city ='%D_';

SELECT * FROM customers WHERE city LIKE'D %';

SELECT * FROM customers WHERE city LIKE'D_';

It can include the CREATE...INDEX statement for creating an index to enforce the primary key constraint.

The owner of the table should have space quota available on the tablespace where the table is defined.

It implicitly executes a commit.

It implicitly rolls back any pending transactions.

A user must have the CREATE ANY TABLE privilege to create tables.

The owner of the table must have the UNLIMITED TABLESPACE system privilege.

Option A

Option B

Option C

Option D

AIl conditions evaluated using DECODE can also be evaluated using CASE.

All conditions evaluated using CASE can also be evaluated using DECODE.

CASE is a function and DECODE is not.

DECODE is a function and CASE is not.

Neither CASE nor DECODE is a function.

Both CASE and DECODE are functions.

11-JUL-2019 6,00,00,00000000 AM – 05:00

11-JUL-2019 11,00,00,00000000 AM

11-JUL-2019 6,00,00,000000 AM

11-JUL-2019 11,00,00,000000AM -05:00

It executes successfully and displays rows in the descend ignore of PROMO CATEGORY.

It produces an error because positional, notation cannot be used in the ORDER BY clause with SBT operators.

It executes successfully but ignores the ORDER BY clause because it is not located at the end of the compound statement.

It produces an error because the ORDER BY clause should appear only at the end of a compound query-that is, with the last SELECT statement.

COMMIT erases all the transaction’s savepoints and releases its locks.

COMMIT ends the transaction and makes all its changes permanent.

ROLLBACK without the TO SAVEPOINT clause undoes all the transaction's changes but does not release its locks.

ROLLBACK to SAVEPOTNT undoes the transaction's changes made since the named savepoint and then ends the transaction.

ROLLBACK without the TO SAVEPOINT clause undoes alt the transaction's changes, releases its locks, and erases all its savepoints.

ROLLBACK without the TO SAVEPOINT clause undoes all the transaction's changes but does not erase its savepoints.

SELECT salary + 120.50 FROM employees;

SELECT SUBSTR(join date, 1, 2)- 10 FROM employees;

SELECT join date 11.’11 salary FROM employees;

SELECT join date FROM employees where join date > *10-02-2018*;

SELECT join date + 20 FROM employees;

The between condition always performs less well than using the >= and <= conditions.

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

The join syntax used makes no difference to performance.

The between condition always performs better than using the >= and <= conditions.

Table aliases can improve performance.

A Relationship can be mandatory for both entities

A one-to-one relationship is always a self-referencing relationship

A many-to-many relationship can be implemented only by using foreign keys

A table name can be specified just once when selecting data from a table having a selfreferencing relationship

A one-to-many relationship in one direction is a one-to-one relationship in the other direction

WHERE UPPER(cust_last_name) IN ('A%', 'B%') AND cust_credit_limit < 1000:

WHERE (INITCAP(cust_last_name) LIKE ‘A%' OR ITITCAP(cust_last_name) LIKE ‘B%') AND cust_credit_limit < 1000

WHERE UPPER(cust_last_name) BETWEEN UPPER('A%' AND 'B%’) AND ROUND(cust_credit_limit) < 1000;

WHERE (UPPER(cust_last_name) LIKE 'A%’ OR UPPER(cust_last_name) LIKE ‘B%’) AND ROUND(cust_credit_limit) < 1000;

WHERE (UPPER(cust_last_name) like INITCAP ('A') OR UPPER(cust_last_name) like INITCAP('B')) AND ROUND(cust_credit_limit) < ROUND(1000) ;

+ (addition) has a higher order of precedence than * (mliplpition)

NOT has a higher order of precedence than AND and OR in a condition.

AND and OR have the same order of precedence in a condition

Operators are evaluated before conditions.

|| has a higher order of precedence than +(addition)

SELECT *

FROM employees e

JOIN department d

WHERE e.department_id=d.department_id

AND d.department_id=90;

SELECT *

FROM employees e

JOIN departments d

ON e.department_id=d.department_id

WHERE d.department_id=90;

SELECT *

FROM employees e

JOIN departments d

ON e.department_id=d.department_id

AND d.department_id=90;

SELECT *

FROM employees e

JOIN departments d

ON d.departments_id=90

WHERE e.department_id=d.department_id;

SUBTRACT

INTERSECT

UNION ALL

MINUS

UNION

Add a new column as the table's first column.

Define a default value that is automatically inserted into a column containing nulls.

Add a new NOT NULL Column with a DEFAULT value.

Change a DATE Column containing data to a NUMBER data type.

Increase the width of a numeric column.

Change the default value of a column.

using single-row functions in the WHERE clause requires a subquery

using single-row functions in the HAVING clause requires a subquery

using aggregate functions in the WHERE clause requires a subquery

using aggregate functions in the HAVING clause requires a subquery

You must have SELECT privileges on a table to view it in ALL _TABLES.

You must have SELECT privileges on a table to view it in DBA TABLES.

USER_ TABLES displays all tables owned by the current user.

ALL TABLES displays all tables owned by the current user.

You must have SELECT privileges on a table to view it in USER TABLES.

All users can query DBA TABLES successfully.

Schema owners can grant object privileges on objects in their schema to any other user or role.

A combination of object and system privileges can be granted to a role.

All types of schema objects have associated object privileges .

Only users with the DBA role can create roles .

Object privileges granted on a table automatically apply to all synonyms for that table.

Only users with the GRANT ANY PRIVILEGE privilege can grant and revoke system privileges from other users.

It will return the six employees earning the highest salaries, in descending order.

It will return the five employees earning the highest salaries, in descending order.

It will return the five employees earning the lowest salaries, in ascending order.

It will return the six employees earning the lowest salaries, in ascending order.

column positions must be used in the order by clause.

The first column in the first select of the compound query with the union operator is used by default to sort output in the absence of an order by clause.

Each select statement in the compound query must have its own order by clause.

only column names from the first select statement in the compound query are recognized.

Each select statement in the compound query can have its own order by clause.

Neither can it be rolled back nor can the DEPARTMENTS table be recovered.

It will remove all views that are based on the DEPARTMENTS table.

It will delete all rows from the DEPARTMENTS table, but retain the empty table.

It will remove the DE PARTMENTS table from the database.

It will remove all synonyms for the DEPARTMENTS table.

It will drop all indexes on the DEPARTMENTS table.

A create table statement can specify the maximum number of rows the table will contain.

The same table name can be used for tables in different schemas.

A system privilege is required.

Creating an external table will automatically create a file using the specified directory and file name.

A primary key constraint is manadatory.

SELECT TO_DATE(TO_CHAR(SYSDATE,'MM/DD/YYYY'),'MM/DD/YYYY') FROM DUAL;

SELECT TO_CHAR (ADD_MONTHS (SYSDATE,6)) FROM DUAL;

SELECT TO_DATE (SYSDATE, 'RRRR-MM-DD') FROM DUAL;

SELECT TO_DATE (ADD_MONTHS(SYSDATE,6), 'dd-mon-yyyy') FROM DUAL;

SELECT TO_CHAR (SYSDATE, 'MM/DD/YYYY') FROM DUAL;

SELECT TO_CHAR (ADD_MONTHS (SYSDATE, 6), 'dd-mon-yyyy') FROM DUAL;

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 dept_id, MAX (Last_name), SUM (salary) FROM employees GROUP BY dept_id

SELECT dept_id, LENGTH (last_name), SUM (salary) FROM employees GROUP BY dept_id

SELECT dept_id, STDDEV (last_name), SUM (salary) FROM employees GROUP BY dept_id

SELECT dept_id, INSTR (last_name,'A'), SUM (salary) FROM employees GROUP BY dept_id

SELECT LOWER (SUBSTR(‘Hello World, 2, 1)) FROM DUAL;

SELECT LOWER (SUBSTR(‘Hello World’, 2)) FROM DUAL;

SELECT LOWER(TRIM(‘H’ FROM ‘Hello World’)) FROM DUAL;

SELECT SUBSTR(‘Hello world’, 2) FROM DUAL;

SELECT INITCAP(TRIM(‘H’ FROM ‘Hello World’)) FROM DUAL;

They can be created only by a user with the DBA role,but can be accessed by all users who can create a session.

Backup and recovery operations are available for these tables.

If the ON COMMIT clause is session-specific,the table is dropped when the session is terminated.

Their data is always stored in the default temporary tablespace of the user who created them.

Indexes can be created on them.

If the ON COMMIT clause Is transaction-specific, all rows in the table are deleted alter each COMMIT or ROLLBACK.