ORACLE DATABASE (ORACLE DB)

Oracle database (Oracle DB) is a relational database management system (RDBMS) from the Oracle Corporation.
Originally developed in 1977 by Lawrence Ellison and other developers, Oracle DB is one of the most trusted and
widely-used relational database engines.
An Oracle database is a collection of data treated as a unit. The purpose of a database is to store and retrieve
related information. A database server is the key to solving the problems of information management. In general,
a server reliably manages a large amount of data in a multiuser environment so that many users can concurrently
access the same data. All this is accomplished while delivering high performance.
A database server also prevents unauthorized access and provides efficient solutions for failure recovery.
ORACLE DATABASE CONSISTS OF THREE FILES:
• Parameter File
• Password File
• Archived Log Files
AN ORACLE SERVER:
Is a database management system that provides an open, comprehensive, integrated approach to information
Management
DATABASE INSTANCE
A database instance is a set of memory structures that manage database files. A database is a set of physical files
on disk created by the CREATE DATABASE statement. The instance manages its associated data and serves the
users of the database.
Every running Oracle database is associated with at least one Oracle database instance. Because an instance
exists in memory and a database exists on disk, an instance can exist without a database and a database can exist
without an instance.
YOU CAN RUN ORACLE DATABASE IN EITHER OF THE FOLLOWING MUTUALLY EXCLUSIVE
CONFIGURATIONS:
• Single-instance configuration: A one-to-one relationship exists between the database and an instance.
• Oracle Real Application Clusters (Oracle RAC) configuration: A one-to-many relationship exists between the
database and instances.

System Global Area (SGA)

The System Global Area (SGA) and the set of database processes constitute an Oracle Database instance. Oracle
Database automatically allocates memory for an SGA when you start an instance, and the operating system
reclaims the memory when you shut down the instance. Each instance has its own SGA.
Program Global Area
Oracle Database allocates a program global area (PGA) for each server process. The PGA is used to process SQL
statements and to hold logon and other session information. For the purposes of memory management, the
collection of all PGAs is known as the instance PGA. Using an initialization parameter, you set the size of the
instance PGA, and the database distributes memory to individual PGAs as needed.
TYPES OF ORACLE DATABASE PROCESS:

1
• User Processes
• Server Processes
• Background Process
When a user runs an application program (such as a Pro*C program) or an Oracle tool (such as Oracle Enterprise
Manager or SQL*Plus), Oracle Database creates a user process to run the user's application.
Oracle Database creates server processes to handle the requests of user processes connected to the instance. In
some situations when the application and Oracle Database operate on the same computer, it is possible to
combine the user process and corresponding server process into a single process to reduce system overhead.

To maximize performance and accommodate many users, a multiprocess Oracle Database system uses some
additional Oracle Database processes called background processes. An Oracle Database instance can have many
background processes; not all are always present. There are numerous background processes.
ORACLE DATABASE ADMINISTRATOR
A database administrator (DBA) is the information technician responsible for directing or performing all activities
related to maintaining a successful database environment. A DBA makes sure an organization's database and its
related applications operate functionally and efficiently.

TASKS OF AN ORACLE DATABASE ADMINISTRATOR

 Evaluating the database server hardware
 Installing the Oracle software
 Planning the database and security strategy
 Creating, migrating, and opening the database
 Backing up the database
 Enrolling system users and planning for their Oracle Network access
 Implementing the database design
 Recovering from database failure
 Monitoring database performance
SYSTEM REQUIREMENTS
• System Architecture:- Processor: AMD64 and Intel EM64T
• Physical Memory (RAM):- 4 GB minimum
• Virtual Memory (swap): - If physical memory is between 2 GB and 16 GB, then set virtual memory to 1 times
the size of the RAM
- If physical memory is more than 16 GB, then set virtual memory to 16 GB
• Disk Space:
- Typical Install Type total: 10 GB
- Advanced Install Types total: 10 GB
• Video adapter - 256 colors
• Screen Resolution: - 1024 X 768 minimum

OPTIMAL FLEXIBLE ARCHITECTURE

Optimal Flexible Architecture is a set of guidelines that you should adopt when organizing Oracle directories and
files on your computer. All Oracle components on the installation media are compliant with Optimal Flexible
Architecture.
The Optimal Flexible Architecture standard is designed to:
2
 • Organize large amounts of complicated software and data on disk, to avoid device bottlenecks and poor
performance
• Facilitate routine administrative tasks such as software and data backup, which are often vulnerable to
data corruption
• Facilitate switching between multiple Oracle databases
• Adequately manage and administer database growth
• Help eliminate fragmentation of free space in the data dictionary, isolate other fragmentation, and
minimize resource contention
DATA BASE
Data Warehouse:
- Research and Marketing data
- State or federal tax payments
- Professional licensing (doctors, nurses, and so on)
• Transaction Processing:
- Store checkout register system
- Automatic Teller Machine (ATM) transactions
• General Purpose:
- Retail billing system (for example, for a software house or a nursery)

DATABASE OBJECTS:- Oracle object types are user-defined types that make it possible to model real-world
entities such as customers and purchase orders as objects in the database.
SCHEMA OBJECTS:- A schema is a collection of logical structures of data, or schema objects. A schema is
owned by a database user and has the same name as that user. Each user owns a single schema.
Schema objects can be created and manipulated with SQL and include the following types of objects:
• Tables Index - organized tables
• Views - Indextypes
• Indexes - Java classes, Java resources, Java sources
• Clusters - Materialized views
• Synonyms - Materialized view logs

SCHEMA OBJECTS
•Constraints - Mining models
• Database links - Object tables
• Database triggers - Object types
• Dimensions - Object views
• Packages - Stored functions, stored procedures
• External procedure libraries

VIEWS
A view is a logical representation of another table or combination of tables. A view derives its data from the tables
on which it is based. These tables are called base tables. Base tables might in turn be actual tables or might be
views themselves. All operations performed on a view actually affect the base table of the view.

Clusters
A table cluster is a group of tables that share common columns and store related data in the same blocks. When
tables are clustered, a single data block can contain rows from multiple tables. For example, a block can store
rows
from both the employees and departments tables rather than from only a single table.

The cluster key is the column or columns that the clustered tables have in common. For example, the
employees and departments tables share the department_id column. You specify the cluster key
when creating the table cluster and when creating every table added to the table cluster.
The cluster key value is the value of the cluster key columns for a particular set of rows. All data that contains
the same cluster key value, such as department_id=20, is physically stored together. Each cluster key value is

3
stored only once in the cluster and the cluster index, no matter how many rows of different tables contain the
value.

SYNONYM
A synonym is an alias or alternate name for a table, view, sequence, or other schema object. They are used
mainly to make it easy for users to access database objects owned by other users. They hide the underlying
object's identity and make it harder for a malicious program or user to target the underlying object.
THERE ARE TWO MAJOR USES OF SYNONYMS:
• Object invisibility: Synonyms can be created to keep the original object hidden from the user.
• Location invisibility: Synonyms can be created as aliases for tables and other objects that are not part of
the local database.
SEQUENCES
Sequences are database objects from which multiple users can generate unique integers. The sequence generator
generates sequential numbers, which can help to generate unique primary keys automatically, and to coordinate
keys across multiple rows or tables.

OTHER SCHEMA OBJECTS (CONSTRAINTS)

• Constraints: Use a constraint to define an integrity constraint--a rule that restricts the values in a database.
Oracle Database lets you create six types of constraints and lets you declare them in two ways.
• The six types of integrity constraint are:
• A NOT NULL constraint prohibits a database value from being null.
• A unique constraint prohibits multiple rows from having the same value in the same column or
combination of columns but allows some values to be null.
• A primary key constraint combines a NOT NULL constraint and a unique constraint in a single
declaration. That is, it prohibits multiple rows from having the same value in the same column or
combination of columns and prohibits values from being null.
• A foreign key constraint requires values in one table to match values in another table.
• A check constraint requires a value in the database to comply with a specified condition.
NON SCHEMA OBJECTS
• Contexts
• Directories
• Editions
• Restore points
• Roles
• Rollback segments
• Tablespaces
• Users
PRIVILEGES
A privilege is a right to execute a particular type of SQL statement or to access another user's object. Some
examples of privileges include the right to:
• Connect to the database (create a session)
• Create a table
• Select rows from another user's table
• Execute another user's stored procedure

GRANTING AND REVOKING SYSTEM PRIVILEGES:

You can grant or revoke system privileges to users and roles. If you grant system privileges to roles, then you
can use the roles to manage system privileges. For example, roles permit privileges to be made selectively
available.
Use either of the following to grant or revoke system privileges to users and roles: