Oracle database 12c intro

© Copyright 2013. Apps Associates LLC. 1
Oracle Database 12c – An Introduction
-- Satyendra P
@pasalapudi

Database-as-a-Service (DBaaS):
Gives users access to databases
running on a cloud computing
platform
Oracle Database 12c New Features

From now on, we can speak of two types of instances: CBD and PDB.
The CDB, or contanier Database, is the kind of body that can nurture others within your
setup.While the PDB, Pluggable Database (embedded database or embedded) are still the
classic database instances that we know in previous versions to 12c.
A container database (CDB), can absorb many (252) PDB instances, in order to consolidate
and streamline administration and save resources at the hardware level.
"The idea is that we can manage many database instances as if they were one."
PDB

Physically, MYCDB is an Oracle database. MYCDB
has a database instance (although possible number
in Oracle Real Application Clusters) and a set of
database files, as well as a non-CBD.
Logically MYCDB contains two PDB: hrpdb and
salespdb. The PDB serve their respective
applications as they did before the consolidation of
databases. For managing the CBD itself or any PDB
within it, an administrator can connect to the root,
which is a father for the PDB.

Pluggable Databases What?
• You can have many pluggable databases inside a single container
database. A PDB is fully backwards compatible with an ordinary pre-12.1
database
• Each instance in a RAC opens the CDB as a whole. A foreground session
sees only the single PDB it connects to and sees it just like a non-CDB
• The system administrator connects to the CDB as a whole and sees a
single system image
• Resource Manager is extended with new between-PDB capabilities
• Integrated with Enterprise Manager and tools like SQL Developer

Pluggable Databases Benefits?
• Very fast provisioning of a new database or of a copy of an existing database. Very fast redeployment, by
unplug and plug, of an existing database to a new platform
• Patch or upgrade the Oracle Database version for many databases quickly, and for the human cost of
doing it once. Patch or upgrade by unplugging a PDB and plugging it into a different CDB at a later version
• Secure separation of the duties of the application administrator from the duties of the administrator of
the Oracle-supplied system
• Consolidate many more PDBs onto a single platform than you can non-CDBs
• Centrally manage and administer multiple databases
• Disaster recovery
• Backups
• Scale-out and fault isolation using RAC

What changed in 12c
• Dictionary tables and user tables – the only ultimate
logical reality
Brand-new database: DBA_Objects,
DBA_Views, … DBMS_Sql, DBMS_Output, …

Earlier Releases before 12c
The “system” and the application are mixed together

In 12c
Architectural separation between the “system” and the application

Architecture to support multiple PDBs

User Management
• A PDB can be administered by a local user
• PDBs can be administered by a common user in the root
• A privileged common user can switch between PDBs
• A privilege is contained within the container where it is granted

Sessions and Services -How to connect
• Every PDB has a default service with its name.
• Service names across has to be unique across CDB
• Connection pool across PDB with a Common User

For the entire CDB
• The Oracle software version
• Active Data Guard
• Scheduled RMAN backups
• Some initialization parameters; some alter database operands (e.g. in 12c,
character set must be the same in all containers)
• Control files
• spfile
• Redo log files
• Flashback log files
• Undo

For just a particular PDB
• RMAN Point-in-time recovery (flashback PDB planned)
• Ad hoc backup
• In each instance: the PDB Open_Mode: MOUNTED, RESTRICTED, READ ONLY, READ WRITE
• Flush shared pool
• All parameters where IsSes_Modifiable = 'TRUE' and IsSys_Modifiable <> 'FALSE' and a few
others (like Open_Cursors, Resource_Manager_Plan)
• Some alter database operands (like default edition)

Dictionary views and performance views
• When queried from within a PDB, all dictionary views, and all performance views, will show
information only from that PDB
• New CDB_ dictionary views, when queried from the root, will provide information across PDBs
• The existing performance views, when queried from the root, will provide information across
PDBs
• The set of PDBs that the current user sees, from the root, depends on a new attribute of the
user

Pluggable Databases Conclusion
• No application validation required
• All Oracle database regression suites run in PDBs with no change
• Fast Provisioning
• Fast creation of empty PDB
• Fast clone of a PDB for testing
• Fast plug PDB for migrations & upgrades
• Strong Isolation
• Pluggable database per application
• High Level of Consolidation
• One database to manage
• Excellent Performance
• Fewest database instances

The new Oracle Database 12c, maintains system privileges SYSDBA, SYSOPER,
SYSASM, 11g of its predecessor but includes three new system privileges,
extremely important and contribute to building a more secure and robust, in the
issue of security .
These privileges are:
SYSBACKUP
SYSDG
SYSKM
New administrative privileges in Oracle Database 12c: SYSBACKUP, SYSDG and SYSKM

• SYSBACKUP, is a new privilege created to manage backup and recovery of database, made with the
RMAN utility.
• SYSDG, is the privilege assigned to manage disk groups and disk storage in a Automatic Storage
Management, better known as ASM.
• SYSKM is a privilege to manage the repository of keys and encryption keys from the same database.
The new feature in Oracle Advanced Security Transparent Database Encryption (TDE) in Oracle
Database 12c, adds a range of new functional to manage consistently, both Oracle Wallets and the
HSMs (Hardware Security Modules).
New administrative privilegies -Oracle Database 12c: SYSBACKUP, SYSDG y SYSKM

• Now, SQL, adding new commands, to manage these keys. From now on, it
keeps a track record (METADATA) to the main attributes associated with keys
created.
• Also, incorporate new views that let you query the privileges of the keys.
• Among the outstanding features is the ability to support export and import of
keys between repositories of Oracle databases, as well as support to store, the
Oracle Wallets, directly on Oracle ASM.
New administrative privileges in Oracle Database 12c: SYSBACKUP, SYSDG and SYSKM

In compliance with international standards and the lack of this requirement in the Standard
editions databases and Standard Edition One, it was easy to predict that this would happen.
From the Oracle Database 12c, encryption for data traveling on the network, based on native
encryption and SSL / TLS, and based strong authentication services such as Kerberos, PKI and
RADIUS, are no longer part of the Oracle advanced Security and now will be available for all
editions licensable database.
Native encryption and SSL / TLS

• Data types VARCHAR2, NVARCHAR2, and RAW have been increased to 32K
• A temporary UNDO tablespace has been added to the database, linked to
global temporary tables.
• Oracle Data Pump 12c, can turn the redo import processes for added load
performance. This feature is only on import.
• To turn off mode "Archive log" is not necessary to download the database.
• Move or rename a "datafile" is now online
• Check paged. Keywords SQL level will limit the number of records that must be
deployed. This replaces the old reference ROWNUM

SQL> select * from pruebas;
CAMPO1 CAMPO2 CAMPO3 CAMPO4
---------- ---------- -------- ----------
1 Hola 21/05/13 1
2 como 21/05/13 2
3 te 21/05/13 3
4 encuentras 21/05/13 4
5 en 21/05/13 5
6 este 21/05/13 6
7 momento 21/05/13 7
7 filas seleccionadas.
SQL> select * from pruebas fetch first 2 rows only;
---------- ---------- -------- ----------
1 Hola 21/05/13 1
2 como 21/05/13 2
select * from pruebas fetch first 30 percent rows only;
---------- ---------- -------- ----------
1 Hola 21/05/13 1
2 como 21/05/13 2
3 te 21/05/13 3
select * from pruebas fetch first 50 percent rows only;
---------- ---------- -------- ----------
1 Hola 21/05/13 1
2 como 21/05/13 2
3 te 21/05/13 3
select * from pruebas offset 2 rows fetch next 2 rows
only;
---------- ---------- -------- ----------
3 te 21/05/13 3

From 12c, a set of columns that are the same leading order in an existing index, are permitted. For
example, in a DW, where desired to have a column in an index such as "bitmap", previously defined in a
type B-tree index in the table.
SQL> create table pruebas(campo1 number, campo2 varchar2(10), campo3 date, campo4 number);
Tabla creada.
SQL> create index idx1_pruebas on pruebas( campo1, campo2);
Indice creado.
SQL> create bitmap index idx2_pruebas on pruebas(campo1, campo2);
create bitmap index idx2_pruebas on pruebas(campo1, campo2)
*
ERROR en linea 1:
ORA-01408: this column list already indexed
SQL> create bitmap index idx2_pruebas on pruebas(campo1, campo2, campo3);
Index created.
Duplicate Indexes

• RMAN Backup container level
• An instance PDB can be "disengaged" from a container and embedded in other CBD
• The PDB's can be cloned in the same container
• The basic administrative actions of a PDB (clone, create, embed, disengage, delete) are implemented
through SQL's.
• Each PDB has its own data dictionary
• The Data Guard configuration is at the level Container
• Recovering from a PDB to a specific spot RMAN does not alter the functionality of the other instances
within the container
• Flashback for a PDB is available from Oracle Database 12c Release 2
The level of PDB

Object-level recovery
RMAN at 12c version, recover or restore from a backup, one or more tables, based on a
versioning scheme (newest, oldest), with a single command, to solve a problem of accidental
deletion or updating of data, on a table. The process may be performed at the same schema
where the table belongs or another schema.
The ability to manage versions, allows RMAN, work in an area where the Flashback could not
come, either because the table had been purged from the recycle bin (recycle bin) or that the
retention period of time, had passed.
New features in RMAN

Platform migration simplification
The backup created with RMAN can back up tablespaces users and their respective
metadata. When you need to restore the tablespace on a different target platform to
source, RMAN will automatically convert, allowing easily attach the database to
"Container".
Support for database consolidation
RMAN can back up and restore the "Container" in full, or only one of the databases
attached. Restoring with RMAN, allow to fully or partially recover or restore a database,
based on a point in time or in a change control number.

Increased performance?
RMAN will allow us to easily clone our databases contained in the "Container". An important
point is that they need prior to backup the database to be duplicated or cloned, before
performing this task.
A new feature compression during backup, restore, or clone, will increase the speed in these
processes, including creating multiple tasks to meet the same process.
The restoration or recovery of a datafile through the network from the STANDBY database
may also be performed as part of the features added to improve performance.

An invisible column is a user-specified column whose values are accessible only
when the column is explicitly specified by name. You can add an invisible column
to a table without affecting existing applications, and make visible column if
necessary.
Tables with columns INVISIBLE

SQL> alter table pruebas add (INVISIBLE int);
Tabla modificada.
SQL> desc pruebas
Nombre +Nulo? Tipo
----------------------------------------- -------- ----------------
CAMPO1 NUMBER
CAMPO2 VARCHAR2(10)
CAMPO3 DATE
CAMPO4 NUMBER
INVISIBLE NUMBER(38)
SQL> update pruebas
2 set invisible=0
3 where campo1 in ( 1,3,5);
3 rows updated.

CAMPO1 CAMPO2 CAMPO3 CAMPO4 INVISIBLE
---------- ---------- -------- ---------- ----------
1 Hola 21/05/13 1 0
2 como 21/05/13 2
3 te 21/05/13 3 0
5 en 21/05/13 5 0
6 este 21/05/13 6
7 momento 21/05/13 7
SQL> alter table pruebas modify(INVISIBLE invisible);
Table Modified.

---------- ---------- -------- ----------
1 Hola 21/05/13 1
2 como 21/05/13 2
3 te 21/05/13 3
5 en 21/05/13 5
6 este 21/05/13 6
7 momento 21/05/13 7
SQL> select campo1, campo2, campo3, campo4, invisible
from pruebas
2 where campo1 in (1,3,5);
CAMPO1 CAMPO2 CAMPO3 CAMPO4 INVISIBLE
---------- ---------- -------- ---------- ----------
1 Hola 21/05/13 1 0
3 te 21/05/13 3 0
5 en 21/05/13 5 0

Oracle Object Tables is a user defined type with a name, attributes and methods.
This object type to model real-world entities such as customers and purchase
orders as objects in the database.
An object type defines a logical structure, but does not create storage.
Oracle Object Tables

SQL> create type registro_clientes as OBJECT
2 ( nombre varchar2(100),
3 identificacion varchar2(30),
4 edad number,
5 empresa varchar2(20),
6 profesion varchar2(30),
7 educacion varchar2(15));
8 /
Type created.
SQL> create table clientes of registro_clientes;
Tabla created

SQL> insert into clientes values('Ronald
Vargas','302970920',44,'NetsoftCA','Consultor','Universitaria');
1 fila creada.
SQL> select * from clientes;
NOMBRE IDENTIFICACION EDAD EMPRESA PROFESION EDUCACION
--------------- -------------- ----- ----------- -------------- --------------
Ronald Vargas 302970920 44 NetsoftCA Consultor Universitaria

SQL*Plus: Release 12.1.0.0.2 Beta on Mar May 21 16:38:09 2013
Copyright (c) 1982, 2012, Oracle. All rights reserved.
Enter the user name: system @ lab1
Enter the password:
Right Connection last time: Mon May June 2013 20:26:44 -06:00
Connected to:Oracle Database 12c Enterprise Edition Release 12.1.0.0.2 - 64bit Beta
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options
SQL> select to_char(sysdate,'dd-mon-yy hh24:mi') from dual;
TO_CHAR(SYSDATE
---------------
21-may-13 16:39
Last login Time Information in SQL*Plus

Thank You!
Satyendra.kumar@aioug.org
Satyendra.pasalapudi@appsassociates.com
@pasalapudi

Oracle database 12c intro

More Related Content

What's hot

Viewers also liked

Similar to Oracle database 12c intro

More from pasalapudi

Recently uploaded

Oracle database 12c intro