Oracle11g - SQL - Fund1
Oracle11g - SQL - Fund1
Oracle11g - SQL - Fund1
D64258GC10
Edition 1.0
January 2010
D65028
Authors Copyright © 2010, Oracle and/or its affiliates. All rights reserved.
Editor Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other
names may be trademarks of their respective owners.
Amitha Narayan
Graphic Designer
Rajiv Chandrabhanu
Publisher
Jobi Varghese
Contents
I Introduction
Lesson Objectives I-2
Lesson Agenda I-3
Course Objectives I-4
Course Agenda I-5
Appendixes Used in the Course I-7
iii
1 Retrieving Data Using the SQL SELECT Statement
Objectives 1-2
Lesson Agenda 1-3
Capabilities of SQL SELECT Statements 1-4
Basic SELECT Statement 1-5
Selecting All Columns 1-6
Selecting Specific Columns 1-7
Writing SQL Statements 1-8
Column Heading Defaults 1-9
Lesson Agenda 1-10
Arithmetic Expressions 1-11
iv
Range Conditions Using the BETWEEN Operator 2-10
Membership Condition Using the IN Operator 2-11
Pattern Matching Using the LIKE Operator 2-12
Combining Wildcard Characters 2-13
Using the NULL Conditions 2-14
Defining Conditions Using the Logical Operators 2-15
Using the AND Operator 2-16
Using the OR Operator 2-17
Using the NOT Operator 2-18
Lesson Agenda 2-19
Rules of Precedence 2-20
v
Number Functions 3-16
Using the ROUND Function 3-17
Using the TRUNC Function 3-18
Using the MOD Function 3-19
Lesson Agenda 3-20
Working with Dates 3-21
RR Date Format 3-22
Using the SYSDATE Function 3-24
Arithmetic with Dates 3-25
Using Arithmetic Operators with Dates 3-26
Lesson Agenda 3-27
vi
Using the NULLIF Function 4-32
Using the COALESCE Function 4-33
Lesson Agenda 4-36
Conditional Expressions 4-37
CASE Expression 4-38
Using the CASE Expression 4-39
DECODE Function 4-40
Using the DECODE Function 4-41
Quiz 4-43
Summary 4-44
Practice 4: Overview 4-45
vii
6 Displaying Data from Multiple Tables Using Joins
Objectives 6-2
Lesson Agenda 6-3
Obtaining Data from Multiple Tables 6-4
Types of Joins 6-5
Joining Tables Using SQL:1999 Syntax 6-6
Qualifying Ambiguous Column Names 6-7
Lesson Agenda 6-8
Creating Natural Joins 6-9
Retrieving Records with Natural Joins 6-10
Creating Joins with the USING Clause 6-11
viii
7 Using Subqueries to Solve Queries
Objectives 7-2
Lesson Agenda 7-3
Using a Subquery to Solve a Problem 7-4
Subquery Syntax 7-5
Using a Subquery 7-6
Guidelines for Using Subqueries 7-7
Types of Subqueries 7-8
Lesson Agenda 7-9
Single-Row Subqueries 7-10
Executing Single-Row Subqueries 7-11
ix
INTERSECT Operator 8-19
Using the INTERSECT Operator 8-20
Lesson Agenda 8-21
MINUS Operator 8-22
Using the MINUS Operator 8-23
Lesson Agenda 8-24
Matching the SELECT Statements 8-25
Matching the SELECT Statement: Example 8-26
Lesson Agenda 8-27
Using the ORDER BY Clause in Set Operations 8-28
Quiz 8-29
9 Manipulating Data
Objectives 9-2
Lesson Agenda 9-3
Data Manipulation Language 9-4
Adding a New Row to a Table 9-5
INSERT Statement Syntax 9-6
Inserting New Rows 9-7
Inserting Rows with Null Values 9-8
Inserting Special Values 9-9
Inserting Specific Date and Time Values 9-10
Creating a Script 9-11
Copying Rows from Another Table 9-12
Lesson Agenda 9-13
Changing Data in a Table 9-14
UPDATE Statement Syntax 9-15
Updating Rows in a Table 9-16
Updating Two Columns with a Subquery 9-17
Updating Rows Based on Another Table 9-18
Lesson Agenda 9-19
Removing a Row from a Table 9-20
DELETE Statement 9-21
Deleting Rows from a Table 9-22
Deleting Rows Based on Another Table 9-23
TRUNCATE Statement 9-24
Lesson Agenda 9-25
Database Transactions 9-26
x
Database Transactions: Start and End 9-27
Advantages of COMMIT and ROLLBACK Statements 9-28
Explicit Transaction Control Statements 9-29
Rolling Back Changes to a Marker 9-30
Implicit Transaction Processing 9-31
State of the Data Before COMMIT or ROLLBACK 9-33
State of the Data After COMMIT 9-34
Committing Data 9-35
State of the Data After ROLLBACK 9-36
State of the Data After ROLLBACK: Example 9-37
Statement-Level Rollback 9-38
xi
PRIMARY KEY Constraint 10-23
FOREIGN KEY Constraint 10-24
FOREIGN KEY Constraint: Keywords 10-26
CHECK Constraint 10-27
CREATE TABLE: Example 10-28
Violating Constraints 10-29
Lesson Agenda 10-31
Creating a Table Using a Subquery 10-32
Lesson Agenda 10-34
ALTER TABLE Statement 10-35
Read-Only Tables 10-36
xii
Modifying a Sequence 11-31
Guidelines for Modifying a Sequence 11-32
Lesson Agenda 11-33
Indexes 11-34
How Are Indexes Created? 11-36
Creating an Index 11-37
Index Creation Guidelines 11-38
Removing an Index 11-39
Lesson Agenda 11-40
Synonyms 11-41
Creating a Synonym for an Object 11-42
xiii
Debugging Procedures and Functions C-25
Database Reporting C-26
Creating a User-Defined Report C-27
Search Engines and External Tools C-28
Setting Preferences C-29
Resetting the SQL Developer Layout C-30
Summary C-31
xiv
Publishing Java to PL/SQL E-16
How Can I Learn More About JDeveloper 11g? E-17
Summary E-18
Index
xv
Oracle Internal & Oracle Academy Use Only
Practices and Solutions
Appendix A
In any practice, there may be exercises that are prefaced with the phrases “If you have
time” or “If you want an extra challenge.” Work on these exercises only if you have
Perform the practices slowly and precisely. You can experiment with saving and running
command files. If you have any questions at any time, ask your instructor.
Note
1) All written practices use Oracle SQL Developer as the development environment.
Although it is recommended that you use Oracle SQL Developer, you can also use
SQL*Plus that is available in this course.
2) For any query, the sequence of rows retrieved from the database may differ from the
screenshots shown.
Testing and Connecting Using the Oracle SQL Developer Database Connection
4) Test the new connection.
5) If the status is Success, connect to the database using this new connection.
Browsing the Tables in the Connections Navigator
6) In the Connections Navigator, view the objects available to you in the Tables node.
Verify that the following tables are present:
COUNTRIES
DEPARTMENTS
EMPLOYEES
JOB_GRADES
JOB_HISTORY
JOBS
LOCATIONS
REGIONS
7) Browse the structure of the EMPLOYEES table.
8) View the data of the DEPARTMENTS table.
5) If the status is Success, connect to the database using this new connection.
True/False
True/False
3) There are four coding errors in the following statement. Can you identify them?
SELECT employee_id, last_name
sal x 12 ANNUAL SALARY
FROM employees;
Part 2
Note the following points before you begin with the practices:
• Save all your lab files at the following location:
/home/oracle/labs/sql1/labs
• Enter your SQL statements in a SQL Worksheet. To save a script in SQL
Developer, make sure that the required SQL worksheet is active and then from the
File menu, select Save As to save your SQL statement as a
lab_<lessonno>_<stepno>.sql script. When you are modifying an existing
script, make sure that you use Save As to save it with a different file name.
• To run the query, click the Execute Statement icon in the SQL Worksheet.
Alternatively, you can press [F9]. For DML and DDL statements, use the Run
Script icon or press [F5].
• After you have executed the query, make sure that you do not enter your next
query in the same worksheet. Open a new worksheet.
You have been hired as a SQL programmer for Acme Corporation. Your first task is to
create some reports based on data from the Human Resources tables.
The HR department wants a query to display the last name, job ID, hire date, and
employee ID for each employee, with the employee ID appearing first. Provide an
alias STARTDATE for the HIRE_DATE column. Save your SQL statement to a file
named lab_01_05.sql so that you can dispatch this file to the HR department.
6) Test your query in the lab_01_05.sql file to ensure that it runs correctly.
Note: After you have executed the query, make sure that you do not enter your next
query in the same worksheet. Open a new worksheet.
Part 3
If you have time, complete the following exercises:
8) The HR department wants more descriptive column headings for its report on
employees. Copy the statement from lab_01_05.sql to a new SQL Worksheet.
Name the column headings Emp #, Employee, Job, and Hire Date, respectively.
Then run the query again.
9) The HR department has requested a report of all employees and their job IDs. Display
the last name concatenated with the job ID (separated by a comma and space) and
name the column Employee and Title.
True/False
True/False
3) There are four coding errors in the following statement. Can you identify them?
SELECT employee_id, last_name
sal x 12 ANNUAL SALARY
FROM employees;
The EMPLOYEES table does not contain a column called sal. The column is
called SALARY.
The ANNUAL SALARY alias cannot include spaces. The alias should read
ANNUAL_SALARY or should be enclosed within double quotation marks.
The HR department wants a query to display the last name, job ID, hire date, and
employee ID for each employee, with the employee ID appearing first. Provide an
alias STARTDATE for the HIRE_DATE column. Save your SQL statement to a file
named lab_01_05.sql so that you can dispatch this file to the HR department.
6) Test your query in the lab_01_05.sql file to ensure that it runs correctly.
SELECT employee_id, last_name, job_id, hire_date StartDate
FROM employees;
7) The HR department wants a query to display all unique job IDs from the EMPLOYEES
table.
SELECT DISTINCT job_id
FROM employees;
Part 3
If you have time, complete the following exercises:
8) The HR department wants more descriptive column headings for its report on
employees. Copy the statement from lab_01_05.sql to a new SQL Worksheet.
Name the column headings Emp #, Employee, Job, and Hire Date, respectively.
Then run the query again.
SELECT employee_id "Emp #", last_name "Employee",
job_id "Job", hire_date "Hire Date"
FROM employees;
9) The HR department has requested a report of all employees and their job IDs. Display
the last name concatenated with the job ID (separated by a comma and space) and
name the column Employee and Title.
SELECT last_name||', '||job_id "Employee and Title"
FROM employees;
4) Create a report to display the last name, job ID, and hire date for employees with the
last names of Matos and Taylor. Order the query in ascending order by the hire date.
7) The HR department needs a report that displays the last name and hire date for all
employees who were hired in 1994.
8) Create a report to display the last name and job title of all employees who do not have
a manager.
9) Create a report to display the last name, salary, and commission of all employees who
earn commissions. Sort data in descending order of salary and commissions.
Use the column’s numeric position in the ORDER BY clause.
6) Modify lab_02_03.sql to list the last name and salary of employees who earn
between $5,000 and $12,000, and are in department 20 or 50. Label the columns
Employee and Monthly Salary, respectively. Save lab_02_03.sql as
lab_02_06.sql again. Run the statement in lab_02_06.sql.
SELECT last_name "Employee", salary "Monthly Salary"
FROM employees
WHERE salary BETWEEN 5000 AND 12000
AND department_id IN (20, 50);
Enter 12000 when prompted for a value in a dialog box. Click OK.
11) The HR department wants to run reports based on a manager. Create a query that
prompts the user for a manager ID and generates the employee ID, last name, salary,
and department for that manager’s employees. The HR department wants the ability
to sort the report on a selected column. You can test the data with the following
values:
manager _id = 103, sorted by last_name
manager_id = 201, sorted by salary
manager_id = 124, sorted by employee_id
15) Modify lab_02_06.sql to display the last name, salary, and commission for all
employees whose commission amount is 20%. Save lab_02_06.sql as
lab_02_15.sql again. Rerun the statement in lab_02_15.sql.
SELECT last_name "Employee", salary "Monthly Salary",
commission_pct
FROM employees
WHERE commission_pct = .20;
2) The HR department needs a report to display the employee number, last name, salary,
and salary increased by 15.5% (expressed as a whole number) for each employee.
Label the column New Salary. Save your SQL statement in a file named
lab_03_02.sql.
4) Modify your query lab_03_02.sql to add a column that subtracts the old salary
from the new salary. Label the column Increase. Save the contents of the file as
lab_03_04.sql. Run the revised query.
Rewrite the query so that the user is prompted to enter a letter that the last name starts
with. For example, if the user enters “H” (capitalized) when prompted for a letter,
Modify the query such that the case of the entered letter does not affect the output.
The entered letter must be capitalized before being processed by the SELECT query.
6) The HR department wants to find the duration of employment for each employee. For
each employee, display the last name and calculate the number of months between
today and the date on which the employee was hired. Label the column as
MONTHS_WORKED. Order your results by the number of months employed. Round the
number of months up to the closest whole number.
Note: Because this query depends on the date when it was executed, the values in the
MONTHS_WORKED column will differ for you.
8) Create a query that displays the first eight characters of the employees’ last names
and indicates the amounts of their salaries with asterisks. Each asterisk signifies a
thousand dollars. Sort the data in descending order of salary. Label the column
EMPLOYEES_AND_THEIR_SALARIES.
4) Modify your query lab_03_02.sql to add a column that subtracts the old salary
from the new salary. Label the column Increase. Save the contents of the file as
lab_03_04.sql. Run the revised query.
SELECT employee_id, last_name, salary,
ROUND(salary * 1.155, 0) "New Salary",
ROUND(salary * 1.155, 0) - salary "Increase"
FROM employees;
5) Write a query that displays the last name (with the first letter in uppercase and all the
other letters in lowercase) and the length of the last name for all employees whose
name starts with the letters “J,” “A,” or “M.” Give each column an appropriate label.
Sort the results by the employees’ last names.
SELECT INITCAP(last_name) "Name",
LENGTH(last_name) "Length"
FROM employees
WHERE last_name LIKE 'J%'
OR last_name LIKE 'M%'
OR last_name LIKE 'A%'
ORDER BY last_name ;
Rewrite the query so that the user is prompted to enter a letter that starts the last
name. For example, if the user enters H (capitalized) when prompted for a letter, then
the output should show all employees whose last name starts with the letter “H.”
Note: Because this query depends on the date when it was executed, the values in the
MONTHS_WORKED column will differ for you.
SELECT last_name, ROUND(MONTHS_BETWEEN(
SYSDATE, hire_date)) MONTHS_WORKED
FROM employees
ORDER BY months_worked;
2) Display each employee’s last name, hire date, and salary review date, which is the
first Monday after six months of service. Label the column REVIEW. Format the dates
to appear in the format similar to “Monday, the Thirty-First of July, 2000.”
3) Display the last name, hire date, and day of the week on which the employee started.
Label the column DAY. Order the results by the day of the week, starting with
Monday.
5) Using the DECODE function, write a query that displays the grade of all employees
based on the value of the JOB_ID column, using the following data:
Job Grade
AD_PRES A
ST_MAN B
IT_PROG C
SA_REP D
ST_CLERK E
None of the above 0
6) Rewrite the statement in the preceding exercise by using the CASE syntax.
SELECT job_id, CASE job_id
WHEN 'ST_CLERK' THEN 'E'
WHEN 'SA_REP' THEN 'D'
5) Modify the query in lab_05_04.sql to display the minimum, maximum, sum, and
average salary for each job type. Save lab_05_04.sql as lab_05_05.sql again.
Run the statement in lab_05_05.sql.
7) Determine the number of managers without listing them. Label the column Number
of Managers.
Hint: Use the MANAGER_ID column to determine the number of managers.
8) Find the difference between the highest and lowest salaries. Label the column
DIFFERENCE.
11) Create a matrix query to display the job, the salary for that job based on department
number, and the total salary for that job, for departments 20, 50, 80, and 90, giving
each column an appropriate heading.
Generalize the query so that the user in the HR department is prompted for a job title.
Save the script to a file named lab_05_06.sql. Run the query. Enter IT_PROG
when prompted and click OK.
SELECT job_id, COUNT(*)
FROM employees
WHERE job_id = '&job_title'
GROUP BY job_id;
3) The HR department needs a report of employees in Toronto. Display the last name,
job, department number, and the department name for all employees who work in
Toronto.
4) Create a report to display employees’ last name and employee number along with
their manager’s last name and manager number. Label the columns Employee, Emp#,
Manager, and Mgr#, respectively. Save your SQL statement as lab_06_04.sql.
Run the query.
6) Create a report for the HR department that displays employee last names, department
numbers, and all the employees who work in the same department as a given
employee. Give each column an appropriate label. Save the script to a file named
lab_06_06.sql.
7) The HR department needs a report on job grades and salaries. To familiarize yourself
with the JOB_GRADES table, first show the structure of the JOB_GRADES table. Then
create a query that displays the name, job, department name, salary, and grade for all
employees.
9) The HR department needs to find the names and hire dates of all the employees who
were hired before their managers, along with their managers’ names and hire dates.
Save the script to a file named lab_06_09.sql.
3) Write a query that displays the employee number and last name of all employees who
work in a department with any employee whose last name contains the letter “u.”
Save your SQL statement as lab_07_03.sql. Run your query.
Modify the query so that the user is prompted for a location ID. Save this to a file
named lab_07_04.sql.
5) Create a report for HR that displays the last name and salary of every employee who
6) Create a report for HR that displays the department number, last name, and job ID for
every employee in the Executive department.
7) Create a report that displays a list of all employees whose salary is more than the
salary of any employee from department 60.
If you have the time, complete the following exercise:
8) Modify the query in lab_07_03.sql to display the employee number, last name,
and salary of all employees who earn more than the average salary, and who work in
a department with any employee whose last name contains a “u.” Save
lab_07_03.sql as lab_07_08.sql again. Run the statement in lab_07_08.sql.
3) Produce a list of jobs for departments 10, 50, and 20, in that order. Display the job ID
and department ID by using the set operators.
4) Create a report that lists the employee IDs and job IDs of those employees who
currently have a job title that is the same as their job title when they were initially
hired by the company (that is, they changed jobs, but have now gone back to doing
their original job).
3) Create an INSERT statement to add the first row of data to the MY_EMPLOYEE table
from the following sample data. Do not list the columns in the INSERT clause. Do not
enter all rows yet.
6) Write an INSERT statement in a dynamic reusable script file to load the remaining
rows into the MY_EMPLOYEE table. The script should prompt for all the columns (ID,
LAST_NAME, FIRST_NAME, USERID, and SALARY). Save this script to a
lab_09_06.sql file.
7) Populate the table with the next two rows of the sample data listed in step 3 by
26) Confirm that the new row was added with correct USERID.
3) Create an INSERT statement to add the first row of data to the MY_EMPLOYEE table
from the following sample data. Do not list the columns in the INSERT clause.
4) Populate the MY_EMPLOYEE table with the second row of the sample data from the
preceding list. This time, list the columns explicitly in the INSERT clause.
INSERT INTO my_employee (id, last_name, first_name,
userid, salary)
VALUES (2, 'Dancs', 'Betty', 'bdancs', 860);
5) Confirm your additions to the table.
SELECT *
FROM my_employee;
21) Discard the most recent DELETE operation without discarding the earlier INSERT
operation.
ROLLBACK TO step_17;
22) Confirm that the new row is still intact.
SELECT *
FROM my_employee;
23) Make the data addition permanent.
COMMIT;
1) Create the DEPT table based on the following table instance chart. Save the statement
in a script called lab_10_01.sql, and then execute the statement in the script to
create the table. Confirm that the table is created.
2) Populate the DEPT table with data from the DEPARTMENTS table. Include only
columns that you need.
3) Create the EMP table based on the following table instance chart. Save the statement
in a script called lab_10_03.sql, and then execute the statement in the script to
create the table. Confirm that the table is created.
Column Name ID LAST_NAME FIRST_NAME DEPT_ID
Key Type
Nulls/Unique
FK Table DEPT
FK Column ID
Data type NUMBER VARCHAR2 VARCHAR2 NUMBER
Length 7 25 25 7
4) Create the EMPLOYEES2 table based on the structure of the EMPLOYEES table. Include
only the EMPLOYEE_ID, FIRST_NAME, LAST_NAME, SALARY, and DEPARTMENT_ID
columns. Name the columns in your new table ID, FIRST_NAME, LAST_NAME,
SALARY, and DEPT_ID, respectively.
5) Alter the EMPLOYEES2 table status to read-only. Please note that this option is
supported in Oracle Database 11g.
7) Revert the EMPLOYEES2 table to the read/write status. Now, try to insert the same
row again. Please note that this option is supported in Oracle Database 11g.
You should get the following messages:
1) Create the DEPT table based on the following table instance chart. Save the statement
in a script called lab_10_01.sql, and then execute the statement in the script to
create the table. Confirm that the table is created.
CREATE TABLE dept
(id NUMBER(7)CONSTRAINT department_id_pk PRIMARY KEY,
name VARCHAR2(25));
To confirm that the table was created and to view its structure, issue the following
command:
DESCRIBE dept
2) Populate the DEPT table with data from the DEPARTMENTS table. Include only those
columns that you need.
INSERT INTO dept
SELECT department_id, department_name
FROM departments;
3) Create the EMP table based on the following table instance chart. Save the statement
in a script called lab_10_03.sql, and then execute the statement in the script to
create the table. Confirm that the table is created.
Column Name ID LAST_NAME FIRST_NAME DEPT_ID
Key Type
Nulls/Unique
FK Table DEPT
FK Column ID
Data type NUMBER VARCHAR2 VARCHAR2 NUMBER
Length 7 25 25 7
Note, you will get the “Update operation not allowed on table” error message.
Therefore, you will not be allowed to insert any row into the table because it is
assigned a read-only status.
INSERT INTO employees2
VALUES (34, 'Grant','Marcie',5678,10)
7) Revert the EMPLOYEES2 table to the read/write status. Now try to insert the same row
again.
Now, because the table is assigned a READ WRITE status, you will be allowed to
insert a row into the table.
ALTER TABLE employees2 READ WRITE
3) Using your EMPLOYEES_VU view, write a query for the HR department to display all
employee names and department numbers.
4) Department 50 needs access to its employee data. Create a view named DEPT50 that
contains the employee numbers, employee last names, and department numbers for
all employees in department 50. You have been asked to label the view columns
EMPNO, EMPLOYEE, and DEPTNO. For security purposes, do not allow an employee to
be reassigned to another department through the view.
5) Display the structure and contents of the DEPT50 view.
Part 2
7) You need a sequence that can be used with the PRIMARY KEY column of the DEPT
table. The sequence should start at 200 and have a maximum value of 1,000. Have
2) Confirm that the view works. Display the contents of the EMPLOYEES_VU view.
SELECT *
3) Using your EMPLOYEES_VU view, write a query for the HR department to display all
employee names and department numbers.
SELECT employee, department_id
FROM employees_vu;
4) Department 50 needs access to its employee data. Create a view named DEPT50 that
contains the employee numbers, employee last names, and department numbers for
all employees in department 50. They have requested that you label the view columns
EMPNO, EMPLOYEE, and DEPTNO. For security purposes, do not allow an employee to
be reassigned to another department through the view.
CREATE VIEW dept50 AS
SELECT employee_id empno, last_name employee,
department_id deptno
FROM employees
WHERE department_id = 50
WITH CHECK OPTION CONSTRAINT emp_dept_50;
SELECT *
FROM dept50;
6) Test your view. Attempt to reassign Matos to department 80.
UPDATE dept50
SET deptno = 80
WHERE employee = 'Matos';
The error is because the DEPT50 view has been created with the WITH CHECK
OPTION constraint. This ensures that the DEPTNO column in the view is protected
from being changed.
8) To test your sequence, write a script to insert two rows in the DEPT table. Name your
script lab_11_08.sql. Be sure to use the sequence that you created for the ID
column. Add two departments: Education and Administration. Confirm your
2) The HR department needs a report of all employees. Write a query to display the last
name, department number, and department name for all employees. Run the query.
3) The HR department needs a report of employees in Toronto. Display the last name,
job, department number, and department name for all employees who work in
Toronto.
4) Create a report to display the employees’ last names and employee number along
with their managers’ last names and manager number. Label the columns Employee,
Emp#, Manager, and Mgr#, respectively. Save your SQL statement as
lab_f_04.sql.
7) The HR department needs a report on job grades and salaries. To familiarize yourself
with the JOB_GRADES table, first show the structure of the JOB_GRADES table. Then
create a query that displays the name, job, department name, salary, and grade for all
employees.
9) The HR department needs to find the names and hire dates for all employees who
were hired before their managers, along with their managers’ names and hire dates.
Save the script to a file named lab_f_09.sql.
2) The HR department needs a report of employees who earn commission. Show the last
name, job, salary, and commission of those employees. Sort the data by salary in
descending order.
8) Find the number of employees who have a last name that ends with the letter “n.”
Create two possible solutions.
11) Create a report that displays the jobs that are found in the Administration and
Executive departments. Also display the number of employees for these jobs. Show
the job with the highest number of employees first.
These exercises can be used for extra practice after you have discussed the following
topics: basic SQL SELECT statements, basic SQL Developer commands, SQL functions,
joins, group functions, and subqueries.
12) Show all the employees who were hired in the first half of the month (before the 16th
of the month).
17) Create a report that displays departments where no sales representatives work.
Include the department number, department name, manager ID, and the location in
the output.
19) Create a report that displays the employee number, last name, salary, department
number, and the average salary in their department for all employees.
21) Create an anniversary overview based on the hire date of the employees. Sort the
anniversaries in ascending order.
5) Show those employees who have a last name starting with the letters “J,” “K,” “L,” or
“M.”
SELECT last_name
FROM employees
WHERE SUBSTR(last_name, 1,1) IN ('J', 'K', 'L', 'M');
These exercises can be used for extra practice after you have discussed the following
topics: basic SQL SELECT statement, basic SQL Developer commands, SQL functions,
joins, and group functions.
7) Create a report that displays the department name, location ID, name, job title, and
salary of those employees who work in a specific location. Prompt the user for the
These exercises can be used for extra practice after you have discussed the following
topics: basic SQL SELECT statements, basic SQL Developer commands, SQL functions,
16) Create a report to display the department number and lowest salary of the department
with the highest average salary.
SELECT department_id, MIN(salary)
FROM employees
GROUP BY department_id
HAVING AVG(salary) = (SELECT MAX(AVG(salary))
FROM employees
GROUP BY department_id);
17) Create a report that displays the departments where no sales representatives work.
Include the department number, department name, and location in the output.
SELECT *
FROM departments
WHERE department_id NOT IN(SELECT department_id
FROM employees
WHERE job_id = 'SA_REP'
AND department_id IS NOT NULL);
18) Create the following statistical reports for the HR department: Include the department
number, department name, and the number of employees working in each department
that:
a) Employs fewer than three employees:
SELECT d.department_id, d.department_name, COUNT(*)
FROM departments d JOIN employees e
ON d.department_id = e.department_id
GROUP BY d.department_id, d.department_name
HAVING COUNT(*) < 3;
TITLE
for #* id
RESERVATION * title
#* res date the subject * description
of o rating
set up for o category
available as
responsible a copy
for
TITLE_COPY
MEMBER #* id
#* id * status
* last name
o first name the subject of
o address responsible
o city for made against
o phone
* join date RENTAL
created #* book date
for o act ret date
o exp ret date
Note: If you want to build the tables, you can execute the commands in the
buildtab.sql script in SQL Developer. If you want to drop the tables, you can execute
the commands in the dropvid.sql script in SQL Developer. Then you can execute the
commands in the buildvid.sql script in SQL Developer to create and populate the
tables.
All the three SQL scripts are present in the /home/oracle/labs/sql1/labs
folder.
• If you use the buildtab.sql script to build the tables, start with step 4.
Length 10 60 400 4 20
2) Verify that the tables were created properly by checking in the Connections Navigator
in SQL Developer.
2 RENTED 2
3 RENTED 3
b) Title number for the TITLE table: Start with 92; do not allow caching of the
values. Name the sequence TITLE_ID_SEQ.
CREATE SEQUENCE title_id_seq
START WITH 92
NOCACHE;
b) Add data to the MEMBER table. Place the insert statements in a script named
COMMIT
SET VERIFY ON
5) Create a view named TITLE_AVAIL to show the movie titles, the availability of each
copy, and its expected return date if rented. Query all rows from the view. Order the
results by title.
Note: Your results may be different.
CREATE VIEW title_avail AS
SELECT t.title, c.copy_id, c.status, r.exp_ret_date
FROM title t JOIN title_copy c
ON t.title_id = c.title_id
FULL OUTER JOIN rental r
ON c.copy_id = r.copy_id
AND c.title_id = r.title_id;
SELECT *
FROM title_avail
ORDER BY title, copy_id;
DESCRIBE title
LOCATIONS
HR DEPARTMENTS
department_id location_id
department_name street_address
manager_id postal_code
location_id city
state_province
country_id
JOB_HISTORY
employee_id
start_date EMPLOYEES
end_date employee_id
job_id first_name
last_name
COUNTRIES
department_id country_id
Objectives
In this appendix, you are introduced to the graphical tool called SQL Developer. You learn how
to use SQL Developer for your database development tasks. You learn how to use SQL
Worksheet to execute SQL statements and SQL scripts.
1 2
Use the File Navigator to explore the file system and open
system files.
2 4 6 8
Enter SQL
statements.
F9 F5
Identify a location,
2 enter a file name,
Before
formatting
Using Snippets
You may want to use certain code fragments when you use the SQL Worksheet or create or edit
a PL/SQL function or procedure. SQL Developer has the feature called Snippets. Snippets are
code fragments such as SQL functions, Optimizer hints, and miscellaneous PL/SQL
programming techniques. You can drag snippets into the Editor window.
To display Snippets, select View > Snippets.
The Snippets window is displayed at the right. You can use the drop-down list to select a group.
A Snippets button is placed in the right window margin, so that you can display the Snippets
window if it becomes hidden.
Inserting a
snippet
Database Reporting
SQL Developer provides many reports about the database and its objects. These reports can be
grouped into the following categories:
• About Your Database reports
• Database Administration reports
• Table reports
• PL/SQL reports
• Security reports
• XML reports
• Jobs reports
• Streams reports
• All Objects reports
• Data Dictionary reports
• User-Defined reports
To display reports, click the Reports tab at the left of the window. Individual reports are
displayed in tabbed panes at the right of the window; and for each report, you can select (using a
drop-down list) the database connection for which to display the report. For reports about
objects, the objects shown are only those visible to the database user associated with the selected
database connection, and the rows are usually ordered by Owner. You can also create your own
user-defined reports.
Oracle Database: SQL Fundamentals I C - 26
Creating a User-Defined Report
Shortcuts to
frequently used tools
1
Setting Preferences
You can customize many aspects of the SQL Developer interface and environment by modifying
SQL Developer preferences according to your preferences and needs. To modify SQL Developer
preferences, select Tools, then Preferences.
The preferences are grouped into the following categories:
• Environment
• Accelerators (Keyboard shortcuts)
• Code Editors
• Database
• Debugger
• Documentation
• Extensions
• File Types
• Migration
• PL/SQL Compilers
• PL/SQL Debugger
Summary
SQL Developer is a free graphical tool to simplify database development tasks. Using SQL
Developer, you can browse, create, and edit database objects. You can use SQL Worksheet to
run SQL statements and scripts. SQL Developer enables you to create and save your own special
set of reports for repeated use.
Objectives
You might want to create SELECT statements that can be used again and again. This appendix
also covers the use of SQL*Plus commands to execute SQL statements. You learn how to format
output using SQL*Plus commands, edit SQL commands, and save scripts in SQL*Plus.
SQL statements
Server
SQL*Plus
Query results
SQL
scripts
SQL SQL*Plus
• A language • An environment
• ANSI-standard • Oracle-proprietary
• Keywords cannot be • Keywords can be
abbreviated. abbreviated.
• Statements manipulate • Commands do not
• Log in to SQL*Plus.
• Describe the table structure.
• Edit your SQL statement.
• Execute SQL from SQL*Plus.
• Save SQL statements to files and append SQL statements
to files.
SQL*Plus
SQL*Plus is an environment in which you can:
• Execute SQL statements to retrieve, modify, add, and remove data from the database
• Format, perform calculations on, store, and print query results in the form of reports
• Create script files to store SQL statements for repeated use in the future
SQL*Plus commands can be divided into the following main categories:
Category Purpose
Environment Affect the general behavior of SQL statements for the session
Format Format query results
File manipulation Save, load, and run script files
Execution Send SQL statements from the SQL buffer to the Oracle server
Edit Modify SQL statements in the buffer
Interaction Create and pass variables to SQL statements, print variable values, and
print messages to the screen
Miscellaneous Connect to the database, manipulate the SQL*Plus environment, and
display column definitions
Logging In to SQL*Plus
How you invoke SQL*Plus depends on which type of operating system you are running Oracle
Database.
To log in from a Linux environment, perform the following steps:
1. Right-click your Linux desktop and select terminal.
2. Enter the sqlplus command shown in the slide.
3. Enter the username, password, and database name.
In the syntax:
username Your database username
password Your database password (Your password is visible if you enter it here.)
@database The database connect string
Note: To ensure the integrity of your password, do not enter it at the operating system prompt.
Instead, enter only your username. Enter your password at the password prompt.
DESC[RIBE] tablename
DESCRIBE departments
• A[PPEND] text
• C[HANGE] / old / new
• C[HANGE] / text /
• CL[EAR] BUFF[ER]
• DEL
• DEL n
Guidelines
• If you press Enter before completing a command, SQL*Plus prompts you with a line
number.
• You terminate the SQL buffer either by entering one of the terminator characters
(semicolon or slash) or by pressing [Enter] twice. The SQL prompt appears.
• I[NPUT]
• I[NPUT] text
• L[IST]
• L[IST] n
• L[IST] m n
• R[UN]
Command Description
I[NPUT] Inserts an indefinite number of lines
I[NPUT] text Inserts a line consisting of text
L[IST] Lists all lines in the SQL buffer
L[IST] n Lists one line (specified by n)
L[IST] m n Lists a range of lines (m to n) inclusive
R[UN] Displays and runs the current SQL statement in the buffer
n Specifies the line to make the current line
n text Replaces line n with text
0 text Inserts a line before line 1
Note: You can enter only one SQL*Plus command for each SQL prompt. SQL*Plus commands
are not stored in the buffer. To continue a SQL*Plus command on the next line, end the first line
with a hyphen (-).
LIST
1 SELECT last_name
2* FROM employees
1
1* SELECT last_name
LIST
1 SELECT last_name, job_id
2* FROM employees
LIST
1* SELECT * from employees
c/employees/departments
LIST
1* SELECT * from departments
• SAVE filename
• GET filename
• START filename
• @ filename
• EDIT filename
• SPOOL filename
LIST
1 SELECT last_name, manager_id, department_id
2* FROM employees
SAVE my_query
Created file my_query
SERVEROUTPUT Command
Most of the PL/SQL programs perform input and output through SQL statements, to store data in
database tables or query those tables. All other PL/SQL input/output is done through APIs that
interact with other programs. For example, the DBMS_OUTPUT package has procedures, such as
PUT_LINE. To see the result outside of PL/SQL requires another program, such as SQL*Plus,
to read and display the data passed to DBMS_OUTPUT.
SQL*Plus does not display DBMS_OUTPUT data unless you first issue the SQL*Plus command
SET SERVEROUTPUT ON as follows:
SET SERVEROUTPUT ON
Note
• SIZE sets the number of bytes of the output that can be buffered within the Oracle
Database server. The default is UNLIMITED. n cannot be less than 2000 or greater than
1,000,000.
• For additional information about SERVEROUTPUT, see Oracle Database PL/SQL User's
Guide and Reference 11g.
Option Description
file_name[.ext] Spools output to the specified file name
APP[END] Adds the contents of the buffer to the end of the file
you specify
SET AUTOTRACE ON
-- The AUTOTRACE report includes both the optimizer
-- execution path and the SQL statement execution
-- statistics
Summary
SQL*Plus is an execution environment that you can use to send SQL commands to the database
server and to edit and save SQL commands. You can execute commands from the SQL prompt
or from a script file.
Objectives
In this appendix, you are introduced to JDeveloper. You learn how to use JDeveloper for your
database development tasks.
Oracle JDeveloper
Oracle JDeveloper is an integrated development environment (IDE) for developing and
deploying Java applications and Web services. It supports every stage of the software
development life cycle (SDLC) from modeling to deploying. It has the features to use the latest
industry standards for Java, XML, and SQL while developing an application.
Oracle JDeveloper 11g initiates a new approach to J2EE development with features that enable
visual and declarative development. This innovative approach makes J2EE development simple
and efficient.
Database Navigator
Using Oracle JDeveloper, you can store the information necessary to connect to a database in an
object called “connection.” A connection is stored as part of the IDE settings, and can be
exported and imported for easy sharing among groups of users. A connection serves several
purposes from browsing the database and building applications, all the way through to
deployment.
4 Click OK
Creating Connection
A connection is an object that specifies the necessary information for connecting to a specific
database as a specific user of that database. You can create and test connections for multiple
databases and for multiple schemas.
To create a database connection, perform the following steps:
1. Click the New Connection icon in the Database Navigator.
2. In the Create Database Connection window, enter the connection name. Enter the
username and password of the schema that you want to connect to. Enter the SID of the
Database you want to connect.
3. Click Test to ensure that the connection has been set correctly.
4. Click OK.
Compiling
After editing the skeleton definition, you need to compile the program unit. Right-click the
PL/SQL object that you need to compile in the Connection Navigator, and then select Compile.
Alternatively, you can also press [Ctrl] + [Shift] + [F9] to compile.
Structure Window
The Structure window offers a structural view of the data in the document currently selected in
the active window of those windows that participate in providing structure: the navigators, the
editors and viewers, and the Property Inspector.
Click View > Structure window to view the Structure window.
In the Structure window, you can view the document data in a variety of ways. The structures
available for display are based upon document type. For a Java file, you can view code structure,
UI structure, or UI model data. For an XML file, you can view XML structure, design structure,
or UI model data.
The Structure window is dynamic, tracking always the current selection of the active window
(unless you freeze the window’s contents on a particular view), as is pertinent to the currently
active editor. When the current selection is a node in the navigator, the default editor is assumed.
To change the view on the structure for the current selection, click a different structure tab.
Editor Window
Double-clicking the name of a program unit opens it in the Editor window. You can view your
project files all in one single editor window, you can open multiple views of the same file, or
you can open multiple views of different files.
The tabs at the top of the editor window are the document tabs. Clicking a document tab gives
that file focus, bringing it to the foreground of the window in the current editor.
The tabs at the bottom of the editor window for a given file are the editor tabs. Selecting an
editor tab opens the file in that editor.
Application Navigator
The Applications - Navigator gives you a logical view of your application and the data it
contains. The Applications - Navigator provides an infrastructure that the different extensions
can plug in to and use to organize their data and menus in a consistent, abstract manner. While
the Applications - Navigator can contain individual files (such as Java source files), it is
designed to consolidate complex data. Complex data types such as entity objects, UML
diagrams, EJB, or Web services appear in this navigator as single nodes. The raw files that make
up these abstract nodes appear in the Structure window.
Topic Website
Oracle JDeveloper Product http://www.oracle.com/technology/products/jdev/index.
Page html
Oracle JDeveloper 11g http://www.oracle.com/technology/obe/obe11jdev/11/in
Tutorials dex.html
Objectives
This lesson explains how to obtain data from more than one table. A join is used to view
information from multiple tables. Therefore, you can join tables together to view information
from more than one table.
Note: Information about joins is found in the section on “SQL Queries and Subqueries: Joins” in
Oracle Database SQL Language Reference 11g, Release 1 (11.1).
EMPLOYEES DEPARTMENTS
Cartesian Products
When a join condition is invalid or omitted completely, the result is a Cartesian product, in
which all combinations of rows are displayed. In other words, all rows in the first table are
joined to all rows in the second table.
A Cartesian product tends to generate a large number of rows and the result is rarely useful.
Therefore, you should always include a valid join condition unless you have a specific need to
combine all rows from all tables.
However, Cartesian products are useful for some tests when you need to generate a large number
of rows to simulate a reasonable amount of data.
• Equijoin
• Nonequijoin
• Outer join
• Self-join
Types of Joins
To join tables, you can use Oracle’s join syntax.
Note: Before the Oracle9i release, the join syntax was proprietary. The SQL:1999–compliant
join syntax does not offer any performance benefits over the Oracle-proprietary join syntax.
Oracle does not have an equivalent syntax to support the FULL OUTER JOIN of the SQL:1999–
compliant join syntax.
EMPLOYEES DEPARTMENTS
Equijoins
To determine an employee’s department name, you compare the value in the DEPARTMENT_ID
column in the EMPLOYEES table with the DEPARTMENT_ID values in the DEPARTMENTS
table. The relationship between the EMPLOYEES and DEPARTMENTS tables is an equijoin; that
is, values in the DEPARTMENT_ID column in both tables must be equal. Often, this type of join
involves primary and foreign key complements.
Note: Equijoins are also called simple joins or inner joins.
EMPLOYEES JOB_GRADES
Nonequijoins
A nonequijoin is a join condition containing something other than an equality operator.
The relationship between the EMPLOYEES table and the JOB_GRADES table is an example of a
nonequijoin. The SALARY column in the EMPLOYEES table ranges between the values in the
LOWEST_SAL and HIGHEST_SAL columns of the JOB_GRADES table. Therefore, each
employee can be graded based on the salary. The relationship is obtained using an operator other
than the equality operator (=).
DEPARTMENTS EMPLOYEES
• You use an outer join to see rows that do not meet the join
condition.
• The outer join operator is the plus sign (+).
Self-Join: Example
The example in the slide joins the EMPLOYEES table to itself. To simulate two tables in the
FROM clause, there are two aliases, namely worker and manager, for the same table,
EMPLOYEES.
In this example, the WHERE clause contains the join that means “where a worker’s manager
number matches the employee number for the manager.”
Summary
There are multiple ways to join tables.
Types of Joins
• Equijoins
• Nonequijoins
• Outer joins
• Self-joins
Cartesian Products
A Cartesian product results in a display of all combinations of rows. This is done by omitting the
WHERE clause.
Table Aliases
• Table aliases speed up database access.
• Table aliases can help to keep SQL code smaller by conserving memory.
Practice F: Overview
This practice is intended to give you practical experience in extracting data from more than one
table using the Oracle join syntax.