Oracle Practice

Kyewook Lee
EMERGENCE OF THE RELATIONAL MODE
L - Codd's Vision
One researcher at IBM was dissatisfied with both th
e Codasyl products and IBM's database package. Ed
gar F. (Ted) Codd, an Oxford-trained mathematicia
n, joined IBM in 1949 and later moved to IBM San J
ose. Codd found existing and new database technol
ogies "taking the old-line view that the burden of fi
nding information should be placed on users. . . . [I
n this view, the database management system] sho
uld only recognize simple commands and it would b
e up to the users to put together appropriate comm
ands for finding what was needed" (Codd, 1982).
In a series of IBM technical reports and then a landmark pape
r, "A Relational Model of Data for Large Shared Data Banks,"
Codd laid out a new way to organize and access data. What C
odd called the "relational model" rested on two key points: It
provides a means of describing data with its natural structure
only--that is, without superimposing any additional structure f
or machine representation purposes. Accordingly, it provides a
basis for a high level data language which will yield maximal i
ndependence between programs on the one hand and machin
e representation on the other. (Codd, 1970) In other words, t
he relational model consisted of data independence from hard
ware and storage implementation and automatic navigation, o
r a high-level, nonprocedural language for accessing data. Ins
tead of processing one record at a time, a programmer could
use the language to specify single operations that would be p
erformed across the entire data set. Codd's model had an imm
ediate impact on research and, as described below, spawned
a number of significant prototyping projects.
Oracle Database
The Oracle database is a relational database sys
tem from Oracle corporation extensively used in pr
oduct and internet-based applications in different
platforms. Oracle database was developed by Larr
y Ellison, along with friends and former coworkers
Bob Miner and Ed Oates, who had started a consul
tancy called Software Development Laboratories
(SDL). They called their finished product Oracle, af
ter the code name of a CIA-funded project they ha
d worked on at a previous employer, Ampex
 History
 Software Development Laboratories was founded in 1977. Larry
Ellison, Bob Miner and Ed Oates found Software
Development Laboratories and build a new type of database called a
relational database  system. Their original project is for the
government and is titled Oracle. The  founders believe that Oracle,
meaning source of wisdom, would be an appropriate name for their
project. 
 In 1979 SDL changed its company name to Relational Software, Inc.
 (RSI) and introduced their product Oracle V2 as the first commercial
relational database system. The version did not support transactions
but implemented the basic SQL functionality of queries and joins.
There was no version 1, instead the first version was called version 2
as a marketing strategy.
 In 1983, RSI was renamed Oracle Corporation to more closely align
itself with its flagship product. Oracle version 3 was released which
had been re-written in the C Programming Language and supported
commit and rollback transaction functionalities. Platform support was
extended to UNIX with this version, which until then had run on
Digital VAX/VMS systems.
 In 1984, Oracle version 4 was released which supported read consis
tency.
 Starting 1985, Oracle began supporting the Client-Server model, wit
h networks becoming available in the mid 80s. Oracle version 5.0 su
pported distributed querying.
 In 1988, Oracle entered the products market and developed its ERP
product - Oracle Financials based on the Oracle Relational Databas
e. Oracle version 6 was released with support for PL/SQL, row-level
locking and hot backups.
 In 1992, Oracle version 7 was released with support for integrity co
nstraints, stored procedures and triggers.
 In 1997, Oracle version 8 was released with support for object-orien
ted development and multimedia applications.
 In 1999, Oracle 8i was released which is more in tune with the need
s of the Internet (The i in the name stands for "Internet"). The data
base has a native Java Virtual Machine.
 In 2001, Oracle 9i was released with 400 new features including the
facilty to read and write XML documents.
 In 2003, Oracle 10g was released. The g stands for "Grid"; one of th
e sales points of 10g is that it's "grid computing ready".
 Relational Database
A relational Database is an extremely simple way of thinking about and
managing the data used in a business. 

Oracle being a relational database management system turns a piece of

data into information by organizing it. 

         Oracle lets you do three things :

         * Lets you put data into it
         * keeps the data
         * Lets you get the data out and work with it 

Oracle supports this in-keep-out approach and provides clever tools that
allow you considerable sophistication in how the data is captured,
edited, modified, and put in; how you keep it securely and how you get
it out to manipulate and report on it. 
 Why it is called Relational?

ORACLE stores information in

tables. Tables can be related to each
other if they each have a column with
a common type of information. This
relationship is the basis for the name
relational database.
 ISAM File
The ISAM file is created by reading input records, in sequence (gives best perfor
mance), and writing the output disk records. In index is created that stores the k
ey field for each record along with the corresponding disk address for that recor
d. Thus even though we are creating a file in sequence, we must indicate what t
he KEY FIELD is for each record.

The COBOL select clause is:

SELECT logical-isam-file
ASSIGN TO real-file-name
ORGANIZATION IS INDEXED
ACCESS MODE IS DYNAMIC
RECORD KEY the-key.

The record format is:

01 INDEX-REC.
03 THE-KEY PIC X(9).
03 IR-NAME PIC X(20).
03 IR-ADDRESS PIC X(40).
 ORACLE STEPS ON FUTURE
An object relational database management system  ( ORDBMS) extends
the capabilities of the RDBMS to support object-oriented concepts.
You can use ORACLE as an RDBMS or take advantage of its object
oriented features.

Relational The traditional ORACLE relational database

Object- The traditional ORACLE relational database, exten
relational ded to include object-oriented concepts and structur
es such as abstract datatypes, nested tables, and va
rying arrays.
Object- An object-oriented database whose design is based
oriented  solely on object-oriented analysis and design.
Structured Query Language 

ORACLE was the first company to release a product that used the English
based Structured Query Language (SQL). This allowed end users to
extract information themselves, without using a systems group for
every little report. SQL has rules of grammar and syntax, but they are
basically the normal rules of  English speech and can be readily
understood. Using SQL does not require any programming
experience. The key words used in a query to ORACLE are select,
from, where, and order by. They are clues to ORACLE to help it
understand your request and respond with the correct answer. 

A simple ORACLE Query: If ORACLE had the WEATHER table in its

database, your first query to it would be simply this:

         select city from WEATHER where Humidity = 89

ORACLE would respond:        City

         -------
         Athens
         PL/SQL is Oracle’s procedural language (PL) superset of Structured
query language. 
 Oracle vs. DB2 
In the ever-increasing world of Internet business, it is becoming
imperative for businesses to obtain a competitive advantage by
adopting technology faster and faster. As a result, there has been
considerable focus on Total Cost of Ownership (TCO) of IT solutions.
In the new web-enabled environment supporting B2B and B2C e-
commerce, IT cost of ownership becomes of lesser importance than
business related metrics such as:

1. Scalability: The ability to handle high, variable, and non-predictable

transaction throughput.
2. Availability: the ability to support non-stop (24x7) operations.
3. Ease of implementation and compatibility with packaged applications.  
 Oracle vs. DB2 
On average the transaction throughput is 16% higher for Oracle8i than for
IBM DB2.
Approximately three-quarters of databases using Oracle8i exhibit availability
levels in excess    of 99% compared to   approximately 60% of those
based on the IBM DB2 database platform. The total cost of ownership
per name used per annum (including the business cost if downtime) is
28% lower for Oracle8i than for IBM DB2.

IBM DB2 Oracle8i

Average number of transactions per minute 37 43

Peak number of transactions per minute 127  143 

 ORACLE APPLICATION
 WHAT IS ORACLE APPLICATION ?
– Application program use a database as a
repository.
– Database cover a wide area. Accounting,
Human Resource, POS etc…
 HOW CAN WE USE.
 There are so many case to use oracle.
 By System configuration.
– 2 Tier - use ODBC or DAO
– Multi Tier - use TCP/IP or Remote Procedure
Call, ENCINA TUXIDO, Remote Method
Interface.
– Web application. – use ASP,JSP, XML etc
 2 Tier
SERVER SIDE
CLIENT SIDE
ODBC
ODBC
NETWORK
Connection
Application ORACLE DATABASE
Program
Running

• Client application program development tools - VB, VC, Delphi,

Power Builder etc…
• Normal way
• Including Data warehousing application program.
 2 Tier
 All formula or Logic in application program
is in Client side application program.
 Easy to configure for application program
environment.
 Depending on network bandwidth.
– ODBC can divide and control using buffer.
 Multi Tier ( 3 Tier Or More )
AP SERVER SIDE
DB SERVER SIDE
TCP/IP,
CLIENT SIDE RPC, Oracle Net Connection
RMI etc
TCP/IP,
RPC,
RMI etc Server Side ORACLE DATABASE
Application

Application
Program Oracle
Running Net Connection

• Client application program development tools - VB, VC, Delphi,

Power Builder etc…
• Large size Application ( Bank or Manufacture etc… )
 Multi Tier ( 3 Tier Or More )
 Clear separation of user-interface-control and data presentation f
rom application-logic.
 Re-definition of the storage strategy won’t influence the clients.
program environment.
 Business-objects and data storage should be brought as close to
gether as possible.
 Their authorization is simpler than that of thousands of "untruste
d" client-PCs. Data protection and security is simpler to obtain. T
heir authorization is simpler than that of thousands of "untruste
d" client-PCs. Data protection and security is simpler to obtain.
 Dynamic load balancing
 Change management: of course it’s easy - and faster - to exchan
ge a component on the server than to furnish numerous PCs wit
h new program versions.
 Web Application
CLIENT SIDE Web SERVER SIDE

Oracle Web Server

ASP,JSP
INTER NET
Connection
ORACLE DATABASE
Web Browser