Antes de migrar de 10g a 11g o 12c, tome en cuenta las siguientes consideraciones. No es tan sencillo como simplemente cambiar de motor de base de datos, se necesita hacer consideraciones a nivel del aplicativo.

1. Ronald Vargas Quesada, Oracle ACE
Expertise Database Management & Performance
Oracledbacr.blogspot.com
Technical Sales Consultant

2. Agenda
 Optimizador de consultas en Oracle Database, ( Optimización basada en
REGLA ó COSTO )
 El parseo de instrucciones SQL en el motor de base de datos
 Compartiendo eficazmente de planes de ejecución en la base de datos
 Interpretación adecuada de los “Explain Plan” generados por la base de
datos
 Consideraciones para el uso adecuado de Índices basado en optimización
por "Costo“
 Diseño y manejo de concurrencia a nivel de la base de datos.
 Concepto de AU ( Allocation Unit )
 Buenas prácticas generales de afinamiento.
 Weblogic Server 12c, Nuevo Servidor de Aplicaciones

3. Arquitectura Ambientes Ejecución
StandAlone
Host / Host
Nube
Cliente / Servidor
3 capas
Cliente delgado / AS
DB

4. Dispositivos de acceso

5. Defining the Problem
Monitor
Feedback
Users
DBA
Database
instance
Reports and files

6. Limit the Scope
• Where is the problem?
– Application (SQL)
– Instance
– Operating system

7. Setting the Priority
• Choose the problem that has the greatest impact:
– Analyze system performance in terms of work done (CPU or
service time) versus time spent waiting for work (wait time).
– Determine which component consumes the greatest amount of
time.
– Drill down to tune that component, if appropriate.

8. Oracle Architecture & Features
Concepto
Convencional:
Arquitectura Oracle
Instance y Database
Perspectiva física y
lógica

9. Oracle Database 12c Architecture & New Features

10. Oracle Database 12c Architecture & New Features

11. SQL Statement Processing Phases
Open
Parse
Close
Bind
Execute
Fetch

12. Considerations for SQL statements
Sensitive writing
Driving Table ( Pivote )
Clause: Where

13. Considerations for SQL statements
Table a = 20.000 rows
Table b = 25.000.000 rows
Order in clause FROM ?
1. FROM a, b
2. FROM b, a

14. Considerations for SQL statements
Table a = 20.000 rows
Table b = 25.000.000 rows
Table c = 10.000.000 rows
Order in clause FROM ?
1. FROM a, b, c
2. FROM b, c, a
3. FROM c, a, b
A ----- C
B ----- C

15. You Probably Do Not Need
to Use Bind Variables
Tom Kyte, Worst Practices
For Developers and DBAs Alike

16. El rendimiento no es una preocupación !!!
SQL>
SQL>
2
3
4
5
6
7
8
9
10
set timing on
begin
for i in 1 .. 100000
loop
execute immediate
'insert into t (x,y)
values ( ' || i ||
', ''x'' )';
end loop;
end;
/
SQL>
SQL>
2
3
4
5
6
7
8
9
10
set timing on
begin
for i in 1 .. 100000
loop
execute immediate
'insert into t (x,y)
values ( :i, ''x'' )'
using i;
end loop;
end;
/

17. Processing a DML Statement
Database
2
Data files
Control files
Redo log files
1
Server
process
UPDATE
employees ...
4
User
process
3
SGA
Database
buffer cache
Redo log
buffer
Shared pool

18. EXPLAIN PLAN Command: Output
SELECT PLAN_TABLE_OUTPUT FROM TABLE(DBMS_XPLAN.DISPLAY());
Plan hash value: 1343509718
------------------------------------------------------------------------------| Id | Operation
| Name
| Rows | Bytes | Cost (%CPU|
-------------------------------------------------------------------------------|
0 | SELECT STATEMENT
|
|
106 | 2862 |
6 (17|
|
1 | MERGE JOIN
|
|
106 | 2862 |
6 (17|
|
2 |
TABLE ACCESS BY INDEX ROWID| DEPARTMENTS |
27 |
432 |
2
(0|
|
3 |
INDEX FULL SCAN
| DEPT_ID_PK |
27 |
|
1
(0|
|* 4 |
SORT JOIN
|
|
107 | 1177 |
4 (25|
|
5 |
TABLE ACCESS FULL
| EMPLOYEES
|
107 | 1177 |
3
(0|
--------------------------------------------------------------------------------
Predicate Information (identified by operation id):
--------------------------------------------------4 - access("E"."DEPARTMENT_ID"="D"."DEPARTMENT_ID")
filter("E"."DEPARTMENT_ID"="D"."DEPARTMENT_ID")
18 rows selected.

19. Reading an Execution Plan
0
1
TABLE ACCESS BY
INDEX ROWID
of DEPARTMENTS
2
INDEX FULL SCAN
DEPT_ID_PK
3
SELECT STATEMENT
MERGE JOIN
4
5
SORT JOIN
FULL TABLE SCAN
of EMPLOYEES

20. Selectivity
– Selectivity represents a fraction of rows from a row source.
• Selectivity affects the estimates of I/O cost.
• Selectivity affects the sort cost.
– Selectivity lies in a value range from 0.0 to 1.0.
– When statistics are available, the estimator uses them to
estimate selectivity.
– When statistics are not available the estimator uses default
values or dynamic sampling.
– With histograms on columns that contain skewed data, the
results are good selectivity estimates.

21. Cardinality and Cost
– Cardinality represents the number of rows in
a row source.
– Cost represents the units of work or
resource that are used.

22. Changing Optimizer Behavior
• The optimizer is influenced by:
–
–
–
–
–
–
–
SQL statement construction
Hints
Statistics
Data structure
System parameters
Session parameters
SQL Plan Management options

23. Using Hints
• Hints
– Are directives (suggestions) to the optimizer
– Require changing the code
SELECT /*+ INDEXto test specific access */ …
– Are useful (tablename indexname) paths
– Must be maintained through upgrades
– _optimizer_ignore_hints enables all
embedded SQL hints to be ignored

24. Optimizer Statistics
• The optimizer depends on various statistics to
determine an optimal execution plan for an SQL
statement.
– Some statistics are gathered at various times and are
controlled by statistic preferences.
• Object statistics
• Dictionary statistics
– Other statistics are only gathered manually.
• Statistics on fixed objects
• Operating system statistics

25. Extended Statistics
• Optimizer needs additional statistics in some cases.
– Multicolumn statistics for related columns (column groups)
• Collect statistics over a group of columns
• For complex predicates
• For equality predicates only
– Expression statistics for function-based indexes
• Collect statistics over an expression
• For expressions used in predicates
• Creates a virtual column

26. Controlling the Behavior of the Optimizer with
Parameters
• Optimizer behavior can be controlled using the
following initialization parameters:
–
–
–
–
–
CURSOR_SHARING = EXACT
DB_FILE_MULTIBLOCK_READ_COUNT = 8,16
OPTIMIZER_INDEX_CACHING = 0
OPTIMIZER_INDEX_COST_ADJ = 100
PGA_AGGREGATE_TARGET = nn MB/GB
– Optimizer underscore parameters:
• OPTIMIZER_FEATURES_ENABLE = Actual Version
• OPTIMIZER_MODE = ALL_ROWS

27. Optimizer with Parameters: Cursor_Sharing
Les facilito esta nota de Tom Kyte ( ASKTOM)
https://blogs.oracle.com/optimizer/entry/explain_adaptive_cursor_sharing_behavior_with
_cursor_sharing_similar_and_force
Aquí clarifica bastante el tema del uso de cursor_sharing para sus valores. La nota esta
en MOS es correcto, pero no esta obsoleto en 11g
También les paso esta otra nota de Morgan, ( otro viejo amigo ), que explica lo mismo y
que el valor esta aún disponible en 11.2.0.4
http://www.morganslibrary.org/reference/cursor_sharing.html

28. Enabling Query Optimizer Features
– The optimizer behavior can be set to prior
releases of the database.
– The OPTIMIZER_FEATURES_ENABLE
initialization parameter can be set to values of
different database releases (such as 8.1.7 or
12.1.0).
– Example:
OPTIMIZER_FEATURES_ENABLE=‘9.2.0';

29. Influencing the Optimizer Approach
•
The optimizer approach is to evaluate based on one of the following:
– Best throughput (default)
– Fastest response
•
The OPTIMIZER_MODE parameter can be set to change the approach:
– ALL_ROWS (default)
– FIRST_ROWS[_n]
•
The OPTIMIZER_MODE can be set at various levels
– System – ALTER SYSTEM SET…
– Session – ALTER SESSION SET…
– Statement – hint - /*+ FIRST_ROWS_10 */

30. Hash Joins
• A hash join is executed as follows:
– Both tables are split into as many partitions as
required, using a full table scan.
– For each partition pair, a hash table is built in
memory on the smallest partition.
– The other partition is used to probe the hash
table.

31. Sort-Merge Joins
• A sort-merge join is executed as follows:
1. The rows from each row source are sorted on
the join predicate columns.
2. The two sorted row sources are then merged
and returned as the resulting row source.

32. Join Performance
• Each join method works best in certain situations.
– Nested join
• Small tables
• Indexes on join columns
– Hash joins
• Large tables
• A large and small table
• A large portion of the table is selected for the join
– Merge-sort
• Non-equijoin
• Row sources are already sorted

33. How the Query Optimizer Chooses
Execution Plans for Joins
• The query optimizer determines:
–
–
–
–
–
Row sources
Type of join
Join method
Cost of execution plans
Other costs such as:
• I/O
• CPU time
• DB_FILE_MULTIBLOCK_READ_COUNT
– Hints specified

34. Optimezer Cost / Rule ?
• Rule / Cost
– Oracle Database 10gR1/R2 or <
• Cost
– Oracle Database 11gR1 or >

35. Optimizer Effects on indexes
• Rule
– Syntactic Evaluation
• Cost
– Mathematical

36. Optimizer Effects on indexes
Rule
Cost
aaaaabb
bbbb a
ccc
dd
e
a
b
c
d
e

37. Optimizer effects on indexes
• Query returned more than 5%
– FTS for rule
• Invalid entries aprox 20%
– FTS for rule
• Query without index
– FTS for rule
• Table or Index without statistics
– FTS for rule

38. Nueva Plataforma de Tecnología
• 5 Pilares de la nube
•
IaaS
Infraestructura-as-a-Service (IaaS),•
que da a los usuarios acceso a los
componentes de la infraestructura
en una plataforma de Cloud, tales
como los sistemas operativos y
software de otro sistema
•
Base
de
datos-as-a-Service
(DBaaS), que ofrece a los usuarios
el acceso a bases de datos que se
ejecutan en una plataforma de
computación en nube
•
Platform-as-a-Service (PaaS), que
ofrece a los usuarios el acceso a
entornos
de
desarrollo
y
despliegue que se ejecutan en una
plataforma de Cloud
•
Software-as-a-Service (SaaS), que
ofrece a los usuarios acceso a las
soluciones que se ejecutan en una
plataforma de computación en
nube
DBaaS
PaaS
SaaS
MWaaS
Middleware-as-a-Service (MWaaS)
Ofrece un entorno completo que
consta de todos los servicios
necesarios para implementar y
ejecutar una aplicación de clase
empresarial.

39. Oracle Weblogic Server 12c: Hacia un solo AS

40. Oracle Weblogic Server 12c
La más moderna versión de su servidor de aplicaciones Oracle
WebLogic Server 12c, es la pieza central de Cloud Application
Foundation y de Fusion Middleware, y esta especialmente diseñada
para desplegar sistemas de información convencionales, así como
de ingeniería y entornos en la nube.

41. Oracle Weblogic Server 12c
Está creada sobre tecnologías basadas en estándares
para cuestiones de portabilidad, eficiencia y facilidad de
integración.

42. Administración WebLogic Server
Cloud Management – Nuevo en Enterprise Manager Cloud Control 12c
WebLogic Server 12c
• Monitoreo de Rendimiento y
Diagnóstico
• Administración de Configuraciones
• Aprovisionamiento de Dominios y
Java EE App
• Integración con MOS & Support
Workbench
Administración en la Nube
• Self Service
• Medición y devoluciones de cargo
• Consolidation Planner

43. Oracle Weblogic Server 12c: Con OEM 12c
Oracle Forms 11gR2 ahora
puede ser monitorizado
desde RUEI ofreciéndonos
información de las páginas
visitadas por los usuarios,
cuánto tiempo permanecen
en ellas, etc.

44. Oracle Weblogic Server 12c: F&R Servicies
• Oracle Forms & Reports 12c, como parte de Fusion
Middleware. Integración con SOA, Coherence, Social.
Posiblemente liberado para finales del Y13, principios
de Y14
• A partir de la versión 13c de FMW, Reports ya no
formará parte del kit de desarrollo aplicativo. Oracle
Forms 13c y Oracle BI Publisher, es la combinación
para las futuras versiones.

45. Cuál es el Presente y Futuro de Forms & Reports ?
–
–
–
–
–
–
–
–
Oracle Forms 6i and Oracle Reports 6i will be de-supported effective 01/31/05.
Oracle Forms 9iAS R2, April 2002
Oracle Forms 10g 9.0.4, December 2003
Oracle Forms 10gR2, January 2005
Oracle Forms 11g , January 2011
Oracle announced that Oracle Forms & Reports does not go from 2017
March 2012, Oracle has no plan to discontinue support of Oracle Forms. Furthermore, a new
version of Forms, Oracle Forms 12c, is planned for delivery as a component of Oracle
Fusion Middleware 12c.
The last major changes to Oracle Reports were in the 10g release. Since then, there have
been limited new features added to the product in Oracle Reports 11gR1 and 11gR2.
Development efforts for Oracle Reports since 10g have been focused on stability and bug
fixes. We are planning to release Oracle Reports 12c as part of Oracle Fusion Middleware
12c.However, Oracle’s strategic reporting solution is now BI Publisher.

46. Recommendations for Oracle Customers Looking to
Migrate from Forms and Reports
– In some cases, there may exist a business driver to move existing
applications from Oracle Forms to a different technology choice. For
example, Oracle Forms may no longer be the ideal fit for the application
requirements, or you may be adopting a strategy to consolidate
disparate or heterogeneous development environments
– Oracle JDeveloper 11g with Oracle ADF is the tool of choice for
building applications on Fusion Middleware. However, given the
architectural difference between Java EE and Oracle Forms, Oracle
has no plans to offer a complete migration solution that attempts to
automatically migrate applications built with these tools to Java EE.

48. Oracle Weblogic Server 12c: Principales novedades de WLS 11g

49. Oracle Weblogic Server 12c: Innovación

50. Oracle Weblogic Server 12c: Principales novedades
– Java EE 6 y Java SE 7
– Mejor productividad del desarrollador ( Jrockit, FastSwap,
Coherence )
– Implementación y administración simplificados con la virtualización
– Integración de la Gestión de Tráfico
– Alta Disponibilidad y Recuperación de Desastres
– Rendimiento mejorado
– Actualización sin problemas

51. WebLogic Server en Exalogic
Más rápido en nuestros sistemas – Nuevo en WebLogic Server 12c
Web
Requests/Sec.
JMS
Messages/sec.
Enterprise Java
Operations/Sec.
49,460
836,520
1,979,940
10X
78,840
Conventional Hardware
Exalogic
5X
5X
401,070
Conventional Hardware
Exalogic
9,560
Conventional Hardware
Exalogic

52. Oracle Weblogic Server 12c: Menos trabajo para migrar

53. Oracle Weblogic Server 12c: Mejoras con Java EE 6
Java Classes*
Lines of Code*
Lines of XML*
25%
50%
80%
Less
Less
Less
• Less XML, Less Code
• Java Server Faces 2.0
• Java Servlets 3.0
• Java Persistence 2.0
• Enterprise Java Beans 3.1
& Interceptors 1.1
* Ejemplo
• Simplification, Productivity
• Managed Beans 1.0
• Bean Validation 1.0
• JAX-WS 2.2
basado en una aplicación construída para JavaOne
• Modernization
• Context & Dependency
Injection 1.0
• Bean Validation 1.0
• Java API for RESTful
Web Services

54. Weblogic Server 12c: Java SE 7: Más limpio, código
más fácil de mantener
• Oracle WebLogic Server 12c
soporta Java SE 7 ( y Java SE 6)
•
•
•
•
Optimización de lenguaje Java
Cliente/Servidor
Internacionalización
Capa de conexión segura SSL/TLS
(Transport Security Layer es el sucesor
para SSL )1.2 en JSSE (Java Secure
Socket Extension)
• Java VM concurrentes

55. rvargas@netsoftca.com
Twitter: @rovaque
Blog: oracledbacr.blogspot.com