TOOLS FOR DBA

SQL*Plus, which is a SQL command-line interface utility

■■ SQL Developer, a GUI tool to explore and manage the database using predefined menu
actions and SQL statements
■■ Oracle Enterprise Manager Database Express 12c, a GUI tool for database administration
and performance management

The user process then initiates a connection to the instance. Oracle calls the process of initiating and
maintaining communication between the user process and the instance a connection. Once the connection is
made, the user establishes a session in the instance.

When a change is committed to a database, Oracle identifies the transaction with a unique
number called the system change number (SCN). The value of an SCN is the logical point
in time at which changes are made to a database. A checkpoint is when the DBWn process
writes all the dirty buffers to the data files. When a checkpoint occurs, Oracle must update
the control file and each data file header to record the checkpoint. This update is done by the
checkpoint process (CKPT); the DBWn process writes the actual data blocks to the data files.

System Monitor SMON Performs instance recovery following an instance

crash, coalesces free space in the database, and
manages space used for sorting.
The system monitor process (SMON) performs instance or crash recovery at database startup
by using the online redo log files. SMON is also responsible for cleaning up temporary segments
in the tablespaces that are no longer used and for coalescing the contiguous free space
in the dictionary-managed tablespaces. If any dead transactions were skipped during instance
recovery because of file-read or offline errors, SMON recovers them when the tablespace or
data file is brought back online. SMON wakes up regularly to check whether it is needed.
Other processes can call SMON if they detect a need for an SMON process.

ROW SHARE (RS) Permits concurrent access to the locked table but prohibits other users from locking the entire
table for exclusive
access.

ROW EXCLUSIVE (RX) Same as ROW SHARE but also prohibits locking in SHARE mode. This type of lock is
obtained automatically with standard DML commands such as UPDATE, INSERT, or DELETE.

SHARE (S) Permits concurrent queries but prohibits updates to the table; this mode is required to create an
index on a table
and is automatically obtained when using the CREATE INDEX statement.

SHARE ROW EXCLUSIVE (SRX) Used to query a whole table and to allow other users to query the table but
prevents other users from locking the table in SHARE mode or updating rows.

EXCLUSIVE (X) The most restrictive locking mode; permits queries on the locked table but prohibits DML by any
other users. This
mode is required to drop the table and is automatically obtained when using the DROP TABLE statement.

CREATE TABLESPACE " TB_STUDENT_1 "

DATAFILE '/ORADATA/DBFILE_STUDENT_1.dbf' SIZE 20M;
ALTER DATABASE MOVE DATAFILE
'/ ORADATA/DBFILE_STUDENT_1.dbf' TO
'/ ORADATA/TestFile_1.dbf';

ALTER TABLESPACE USER_DATA OFFLINE;

ALTER DATABASE MOVE DATAFILE

'/ ORADATA/DBFILE_STUDENT_1.dbf' TO
'/ ORADATA/TestFile_1.dbf';

ALTER TABLESPACE USER_DATA OFFLINE;

ALTER TABLESPACE USER_DATA RENAME DATAFILE

'/ ORADATA/DBFILE_STUDENT_1.dbf' TO
'/ ORADATA/TestFile_1.dbf';

Create tablespace “TS_Orange” with following characteristics:

1. Default storage space (initial size 512kb, next 512kb, Minimum extent 2, maximum extents 4096kb)
2. Block size is 30kb
3. Minimum extent 1024kb
4. Logging disabled
5. Apply extent management locally

CREATE TABLESPACE APPL_DATA

DATAFILE '/disk3/oradata/DB01/appl_data01.dbf'
SIZE 100M
DEFAULT STORAGE (
INITIAL 256K
NEXT 256K
MINEXTENTS 2
PCTINCREASE 0
MAXEXTENTS 4096)
BLOCKSIZE 16K
MINIMUM EXTENT 256K
LOGGING
ONLINE
FORCE LOGGING
FLASHBACK ON
EXTENT MANAGEMENT DICTIONARY
SEGMENT SPACE MANAGEMENT MANUAL;

The SGA is a shared memory area. All the users of the database share the information
maintained in this area. Oracle allocates memory for the SGA when the instance is started
and de-allocates it when the instance is shut down. The SGA consists of three mandatory
components and four optional components.

Oracle Net is the glue that bonds the Oracle network together. It is responsible for handling
client-to-server and server-to-server communications, and it can be configured on
the client, the middle-tier application, web servers, and the Oracle server. Oracle Net manages
the flow of information in the Oracle network infrastructure. First, it establishes the
initial connection to the Oracle server, and then it acts as the messenger, passing requests
from the client back to the server or passing them between two Oracle servers. Oracle Net
handles all negotiations between the client and server during the client connection.

Scalability
Oracle Shared Server

Database Resident Connection Pooling

Connection Manager

Accessibility
Heterogeneous Services

External Procedures

Heterogeneous Services
The Heterogeneous Services component provides the ability to communicate with non-Oracle
databases and services. These services allow organizations to leverage and interact with their
existing data stores without having to necessarily move the data to an Oracle server.
The suite of Heterogeneous Services comprises the Oracle Transparent Gateway and
Generic Connectivity. These products allow Oracle to communicate with non-Oracle data
sources in a seamless configuration. Heterogeneous Services also integrates existing systems
with the Oracle environment, which allows you to leverage your investment in those systems.
These services also allow for two-way communication and replication from Oracle data
sources to non-Oracle data sources.
External Procedures
In some development efforts, interfacing with procedures that reside outside the database
may be necessary. These procedures are typically written in a third-generation language,
such as C. Oracle Net provides the ability to invoke such external procedures from Oracle
PL/SQL callouts. When a call is made, a process is started that acts as an interface between
Oracle and the external procedure. This callout process defaults to the name extproc. The
listener is then responsible for supplying information, such as a library or procedure name
and any parameters, to the called procedure. These programs are then loaded and executed
under the control of the extproc process.