Académique Documents
Professionnel Documents
Culture Documents
comprehensive integrated data management approach. The Oracle server consists of two parts:
Instance
Database
Assignment of Oracle process set and memory (SGA). Instances can only be opened by
mounting a single database at any point in time. An instance is a combination of memory
structure and process structure. The Oracle instance contains the memory part and the process
of the RDBMS server. The oracle instance consists of a memory structure and a server process
running on the server. Shutting down an instance prevents anyone from accessing the data in
the database. An instance provides an interface between a user and the data he wishes to
manipulate. This instance provides a process for client communication and data access. The
instance also consists of several memory buffers and caches. The Program Global Area (PGA)
is a no-shared, writable memory area related with a user process. The PGA always comprises
stack space for a session, which holds variables and other information related with a session.
1. The combination of SGA and Oracle process is called an Oracle database instance.
2. Oracle starts the instance and mounts the database on the instance.
3. Multiple instances can run simultaneously on the same machine, each accessing its own
physical database
A collection of databases of real operating system files. These two parts are closely
related, but the database can be mounted and opened in many cases. An Oracle database
Control file
Online redo log
Data file
Fig 1: Home
Fig 5: Tablespaces
Fig 9: Users
The instance reads the initialization parameter file, allocates SEG memory, and starts
the background process. Start the instance without mounting the database. It does not allow
access to the database and is normally only done to create the database or recreate or recreate
the control file. A parameter file is required for NOMOUNT mode. It is usually necessary for
some types of recovery operations such as control recovery.
The instance opens the database control file but does not open the data file. Start the
instance and mount the database, but leave it closed. In this state, certain DBA activities are
allowed, but general access to the database is not allowed. A control file is required for MOUNT
mode. Normally it is necessary for data file recovery operation.
This instance opens the database's redo log files and data files. Start the instance,
mount the database and open it. This can be done in unrestricted mode, allowing all users
access, or allowing only database administrators access in restricted mode. In OPEN mode,
data files and online redo log files are required.
Size 70Mb
We write SQL statement for to create a permanent tablespace INVENTORY, and the
size of the tablespace is stored in 70Mb with data file invo1.dbf. This tablespace is locally
managed and permits autoextend going on maximum size 120Mb by increment of 10Mb. With
that permits autoextend; we can get benefits as maximum size cannot larger than 120Mb and
not stop working until range 120Mb when execute the process. Autoextend can be very useful
for the busy DBA by letting oracle automatically increase file sizes to a predetermined limit when
needed, which can make it easier to work one day, minimizing the effort spent to monitor disk
space.
Users who are delegated a special control level are called privileged users. Users who do not
have most privileges are defined as unprivileged users, regular users, or regular users.
System
Object
System- Allows users to perform specific actions in the database. It is usually equivalent to
executing the DDL command. System privileges are the right to perform specific actions or
perform actions on specific types of objects. Objects include tables, views, materialized views,
synonyms, indexes, sequences, cache groups, replication schemes and PL / SQL functions,
procedures and packages. Only the instance administrator or a user with ADMIN authority can
grant or revoke system privileges. System privileges allow a user to run certain database
operations or classes of database operations. For example, to create a table, the user must
have created table privilege.
Object- Object privileges are the right to perform certain actions on an object or to access
another user's objects. Objects include tables, views, materialized views, indexes, synonyms,
sequences, cache groups, replication schemes and PL / SQL functions, procedures and
packages.
The owner of the object has all object privileges on that object and cannot revoke that privilege.
An owner of an object can grant object privileges for that object to other database users. A user
with the ADMIN privilege can grant and revoke object privileges from users who do not own the
privileged object. Permissions such as insert, update and delete tables are associated with
objects.
In this figure, create the view dept_stats in the agreen schema and write query text for
show information.
This figure is the dept_stats view of the agreen schema and the status is valid.
This figure is the display information for the dept_stats view of the agreen schema.
In this slight the employee when two changes is salary and she said salary amount
20000. After updating, she is confirming her salary to commit. And employee_id 120 salary is
When updating 'May' salary to 25000 and update. The user 'Thandar' is select his salary
is 20000 because the user may is not commit his salary.
Before, e enable server output 'on'. And, we declare (4) variables as NoOfEmp, AvgSal,
MaxSal and MinSal. In the begin, we write the select query for display information such as the
total number of employees, the average salary, the maximum salary and the minimum salary.
And then, we end the query.
This figure is the testing of get_annual _income. In this testing, the tested employee_id has
commission_pct, the output will display but it not the result will now display.
In our lessons, we learned that logical backup of a database consists of logical data
such as tables and stored processes. Logical backup transferred from a database with oracle
Logical backup are used for give a test or development copy of Rational RequisitePro
projects. The test or development copies are used for testing a new release of Rational
RequisitePro or to train new clients.
Logical backups are used for significantly altering the database construction such as
transferring the oracle schema for Rational RequisitePro from an oracle tablespace to
other or expending the different oracle schema names.
In the SQL Server, this can also be used for transfer the Rational RequisitePro data to
the different database.
Physical backups are the base ground of each backup and recovery idea. In the physical
backup, copying the files such as data files, control files and archived redo logs that constitute
to the database are included. Logical backups are so very useful adding to the physical backups
but not adequate protection against data destruction without physical backups. We also learned
that an effectiveness backup play must be foundation on physical backup.
https://blog.dbi-services.com/oracle-basics-1-oracle-database-vs-oracle-instance/
http://searchoracle.techtarget.com/answer/Oracle-instance-architecture
http://www.careerride.com/Oracle-what-is-Program-Global-Area.aspx
https://www.safaribooksonline.com/library/view/oracle-database
administration/1565925165/ch10s03s03.html
https://docs.oracle.com/cd/E21901_01/timesten.1122/e21642/privileges.htm#TTSQL341
https://en.wikipedia.org/wiki/Privilege_%28computing%29
https://www.ibm.com/support/knowledgecenter/en/SSSHCT_7.1.0/com.ibm.reqpro.help/administ
ering/projects/archiving/c_logical_backups.html