CREATE USER

CREATE SESSION

CREATE ANY TABLE

IMP_FULL_DATABASE

EXP_FULL_DATABASE

SYNC or ASYNC to identify the network transmission mode.

LGWR or ARCH to identify the primary database process responsible for sending redo information to the standby.

AFFIRM or NOAFFIRM to control whether log archiving disk write operations are to be performed synchronously or asynchronously.

PROTECTED or UNPROTECTED to control the degree of divergence and data loss at the standby database.

Perform I/O

Lock rows that are not data dictionary rows

Monitor other Oracle processes

Connect users to the Oracle instance

Execute SQL statments issued through an application

Control file

Extent

Segment

Data file

Log file

Tablespace

Oracle Managed Files used for this instance.

The USER_DATA tablespace in managed using FET$/UET$ tables.

The COMPATIBLE intialization paramter must be 9.0.0 or higer.

Space within segments is the USER_DATA tablespace is managed with freelists.

The control file can grow in size.

The control file can store RMAN scripts.

CONTROL_FILE_RECORD_KEEP_TIME determine retention time for RMAN records.

The RMAN catalog can exist solely in the control file of the target database.

Oracle Net is layered on top of the network protocol.

Oracle Net must reside on both the client and the server for peer-to-peer communication to occur.

On the client side, Oracle Net is responsible for working with the listener to receive incoming connection requests.

On the server side, Oracle Net is responsible for several connectivity issues such as : the location of the server, whatever one or more protocol is involved in the connection, and how to handle exception and interrupts.

Restore the data file and perform incomplete recovery.

Restore the data file and perform point-in-time recover.

Drop the tablespace and lose all data in the tablespace.

Restore the database and lose all data since the last backup.

alert.ora

init.ora

tnsname.ora

redolog

SELECT COUNT(*) IN Sales

SELECT NUM() FROM Sales

SELECT COUNTER(*) FROM Sales

SELECT COUNT(*) FROM Sales

INSERT Projects ('Content Development', 'Website content development project')

INSERT INTO Projects (ProjectName, ProjectDescription) VALUES ('Content Development', 'Website content development project')

INSERT Projects VALUES ('Content Development', 'Website content development project')

SAVE INTO Projects (ProjectName, ProjectDescription) VALUES ('Content Development', 'Website content development project')

CAST

LEFT

MIN

RIGHT

ORDER BY clause

GROUP BY clause.

JOIN clause.

WHERE clause.

JOIN

LEN

LEFT

AVG

update database table.

verify that the inserted data is correct.

select data from 2 or more tables related by common attribute (table column).

delete data from database table.

SELECT * FROM Contest HAVING ContestDate >= '05/25/2006'

SELECT * FROM Contest WHERE ContestDate >= '05/25/2006'

SELECT * FROM Contest WHERE ContestDate < '05/25/2006'

SELECT * FROM Contest IN ContestDate < '05/25/2006'

You can if you use nested SQL statements

You can use UPDATE and SELECT clauses together, even if you don’t have nested SQL statements.

You can if you use WITH clause.

You can't

The FROM SQL keyword specifies a column list

The FROM SQL keyword specifies a search condition.

The FROM SQL keyword specifies the tables, views, and joined tables used in SELECT, UPDATE and DELETE SQL statements.

The FROM SQL keyword specifies a find condition.

a single table in the database

to all tables in the database

to all the tables of the user

more than one table in the database

ORDER BY clause.

GROUP BY clause.

JOIN clause.

WHERE clause.