Introduction to Enterprise DB System:

As the technology is growing and people are using online resources more than offline, amount of data is increasing day by
day. If we talk about any big organization such as E-Commerce market, etc. which has million of customer bases and has millions
of data to be stored then we will know why enterprise database comes into play. More and more businesses are looking to
bring in powerful ways when it comes to handling ever-increasing volumes of data.
Why EDS?
Scalability: High Availability:
Designed to handle massive amounts of data and support Enterprise databases are designed for 24/7 operations
many concurrent users without performance with features like failover, clustering, and replication to
degradation. minimize downtime.

Security: Performance Optimization:

They offer advanced security features like user Features like indexing, partitioning, dynamic views, query
authentication, role-based access control, auditing, and optimization, and caching to ensure high-performance
compliance with regulatory requirements. data processing.

Backup and Recovery:

Support for robust backup and disaster recovery strategies, including point-in-time recovery, incremental backups, and hot
backups (backups while the database is running).
DBA Responsibility:
Database Adminitrator is a person who is expert in sql and a database software product & have all the responsibility to
manage a database in an organization:

100% 100% 70%

who can access data what command each one can use manage backups as and when
user & role management what rights and privileges(object & needed
sys) a user have on data knows the recovery procedures
Example Enterprise Database Systems:
Oracle Architecture: A Deep Dive
Oracle Database employs a client-server architecture, with the database server and client connections running in separate
processes. The server process manages data and resources, and client connections communicate with the server to
access and manipulate data.
Network and Connectivity
1 Listener 2 Network Protocols 3 Connection Management
The listener process is a key Oracle handles the creation,
component that listens for maintenance, and termination
Oracle supports various network
incoming client connections and of connections between clients
protocols, such as TCP/IP for
routes them to the appropriate and the database server.
establishing connections with client
database instance.
applications.

4 Security and Authentication

Network connections are secured through mechanisms like authentication, authorization, and encryption to protect
data and prevent unauthorized access.
Oracle Architecture:
ODB architecture consists of:

Memory Area

Background Processes

Physical Storage/ Database

Memory Area + BG Processes = DB Instance

Note: Memory Area does not have only SGA but PGA also
Oracle Arch…
Oracle Server = Instance + Storage

Oracle Instance = BG Processes + Memory Area

Physical Structure = Storage

Storage and Memory Subsystems
In Oracle, both the System Global Area (SGA) and the Program Global Area (PGA) are memory regions that play key roles in
the performance and management of the database. Datafiles are stored on disk subsystem.

System Global Area (SGA) Program Global Area (PGA) Disk Subsystems
The SGA is a shared memory area The PGA is a non-shared memory Oracle databases rely on disk
that stores data structures, region/private memory area subsystems for storing data,
control information, and buffers associated with each user session that including data files, redo logs, control
used by the Oracle instance. stores session-specific data and files, and temporary files.
shared among all database users. control information.
SGA Components:
Database buffer cache: The Buffer Cache is a portion of the SGA that stores copies of data blocks read from datafiles. It
is used to cache frequently accessed data blocks, reducing the number of disks I/Os required to access the data. This can
improve performance by reducing disk I/O time and increasing the speed of data retrieval.
Redo log Buffer: The most crucial structure for recovery operations is the redo log, which consists of two or more
preallocated files that store all changes made to the database as they occur. Every instance of an Oracle Database has an
associated redo log to protect the database in case of an instance failure.
Shared pool: The Shared Pool is a portion of the SGA that contains shared memory structures, such as shared SQL and PL/SQL
areas.
Large Pool: The Large Pool is an optional portion of the SGA that can be used for large memory allocation.
Backgroud Processes:
System Monitor Process (SMON):
1 These processes are responsible for performing system-level recovery and
maintenance activities.

Process Monitor Process (PMON):

2
The task of these processes is to monitor other background processes.

Database Writer Process (DBWR):

3 This process performs the task of writing data blocks from the Database
Buffer Cache (present in SGA) to physical data files(Present in the
storage).

Log Writer Process (LGWR):

4 This process writes the Redo blocks from Redo Log Buffer
(present in SGA) to Redo Log Files(present in the storage).

CheckPoint (CKPT):
5 This process maintains data files and control files with
the most recent checkpoint information.
Other Components
SQL Engine Java Pool
The SQL engine processes SQL statements, interprets The Java Pool is an optional portion of the SGA. This pool
them, and executes them against the database. is used when the Oracle Database is configured to run
Java applications or when using Oracle JVM.
Storage/Database System:

Data files: Redo log files: Control files:

These files hold the actual data in the These files are used to hold the It is a binary file that holds database
database. changes made in the database. Redo status-related information like
log files can be utilized during the Database Name, Data File and Redo
database recovery process to retrieve Log file Names and location,
the original information. Database creation timestamps.
Security and Access Control:
1 2 3

Authentication Authorization Auditing

Users must authenticate themselves Once authenticated, users are Database activity can be audited to
to access the database, typically granted specific privileges to access track user actions, security events,
through usernames and passwords. and modify database objects based and potential security breaches.
on their roles.
Conclusion and Key Takeaways
Oracle's architecture offers a robust, scalable, and secure platform for
managing data. By understanding the key components and
subsystems, you can optimize performance, ensure high availability,
and effectively manage security and access control.