Professional Documents
Culture Documents
I t d ti
Introduction
s a
) h a
c o m d e
ail t Gu i
m
g den
ed Stu@
m
ha e this
o
c l em to us
( o ra se
a b 2014, c n and/or its affiliates. All rights reserved.
eOracle
z
Copyright l i
e d a able
r
o hamansfe
m -tr
non
Objectives
s a
) h a
c o m d e
ail t Gu i
m
g den
ed Stu@
m
ha e this
o
c l em to us
( o ra se
a b 2014, c n and/or its affiliates. All rights reserved.
eOracle
z
Copyright l i
e d a able
r
o hamansfe
m -tr
non
Enterprise Manager
RAC Grids of Managing Cloud Control and
s a
clusters change
g database
a
)h
low-cost
low cost m
for hardware and across the o
consolidation de
ilc Guiacross
availability storage a t
enterprise gm thenenterprise
e d@ Stude
o hame this
c l em to us
( o ra se
a b 2014, c n and/or its affiliates. All rights reserved.
eOracle
z
Copyright l i
e d a able
hama10g s f er
m o
Oracle Database
r n was the first database management system designed for grid
computing.n- t
Oracle n
o
Database 11g consolidates and extends Oracles Oracle s unique ability to deliver the benefits
of grid computing, transforming data centers from silos of isolated system resources to shared
pools of servers and storage.
Oracle Database 12c and Enterprise Manager Cloud Control are designed for cloud
computing. Cloud computing creates a complete, pre-integrated, off-the-shelf private cloud
solution that allows you to quickly transform the enterprise data center into a private cloud.
The key benefits are the following:
Reduce server sprawl and improve CPU utilization by consolidating on fewer servers.
Reduce the amount of time a DBA spends installing and configuring databases, by
automating deployment of standard database configurations.
A single console manages the entire Cloud life cycleplan, set up, deliver, and operate.
Prevent resource hogging by setting quotas for individual users.
Forecast future resource needs byy analyzing
y g trending g reports.
p
Compute chargeback based on performance and configuration metrics.
JOBS
COUNTRIES JOB_ID (PK)
COUNTRY_ID (PK) JOB_TITLE
COUNTRY_NAME MIN_SALARY JOB_HISTORY
REGION ID (FK)
REGION_ID MAX SALARY
MAX_SALARY EMPLOYEE_ID (PK)
START_DATE (PK)
END_DATE
JOB_ID (FK)
LOCATIONS EMPLOYEES DEPARTMENT_ID (FK)
LOCATION_ID (PK) EMPLOYEE_ID (PK)
STREET_ADDRESS FIRST_NAME
LAST_NAME
POSTAL_CODE
CITY EMAIL
s a
STATE_PROVINCE PHONE_NUMBER a
)h
COUNTRY_ID ((FK)
) HIRE_DATE
o m e
ilc Guid
JOB_ID (FK)
SALARY
COMMISION_PCT a
m ent
DEPARTMENTS MANAGER_ID (FK) g
DEPARTMENT_ID (PK) DEPARTMENT_ID (FK)
e d@ Stud
hame this
DEPARTMENT_NAME
MANAGER_ID
o
em to us
LOCATION_ID (FK)
c l
( o ra se
a b 2014, c n and/or its affiliates. All rights reserved.
eOracle
z
Copyright l i
e d a able
r
o hamused
The examples
a n s
in
f ethis course are from a human resources (HR) schema, which can be
m
created as n t r
- of the starter database.
part
n o
The following are some principal business rules implemented in the HR schema:
Each department may be the employer of one or more employees. Each employee may
be assigned to only one department.
Each job must be a job for one or more employees. Each employee must be currently
assigned to only one job.
When an employee changes his or her department or job, a record in the JOB_HISTORY
table records the start and end dates of the past assignments.
g
JOB_HISTORY records are identified by a composite primary key (PK): the
EMPLOYEE_ID and the START_DATE columns.
Notation: PK = Primary Key, FK = Foreign Key
Solid lines represent mandatory foreign key (FK) constraints and dashed lines represent
optional FK constraints.
p
The EMPLOYEES table also has an FK constraint with itself. This is an implementation of the
business rule: Each employee may be reporting directly to only one manager. The FK is
optional because the top employee does not report to another employee.
s a
) h a
c o m d e
ail t Gu i
m
g den
ed Stu@
m
ha e this
o
c l em to us
( o ra se
a b 2014, c n and/or its affiliates. All rights reserved.
eOracle
z
Copyright l i
e d a able
r
o hamansfe
m -tr
non