Kellyn Pot'Vin presented on performance diagnostics and tuning tools available in Oracle Enterprise Manager 12c. The presentation covered tools like Top Activity, SQL Monitor, ASH Analytics, Real-Time ADDM, and Compare Period ADDM. Top Activity provides a graphical view of current performance and resource usage. SQL Monitor allows monitoring of SQL statements and sessions. ASH Analytics is a more advanced replacement for Top Activity that provides historical performance data. Real-Time ADDM and Compare Period ADDM enable real-time and comparative Automatic Database Diagnostic Monitor reporting and findings within EM12c.
Merck Moving Beyond Passwords: FIDO Paris Seminar.pptx
EM12c Performance Diagnosis Tools
1. K E L L Y N P O T ’ V I N
S R . T E C H N I C A L C O N S U L T A N T
EM12c Performance Diagnosis
and Tuning Outside the Box
2. Kellyn Pot’Vin
Westminster, Colorado
Oracle ACE Director, Sr. Technical Specialist at
Enkitec
Specialize in performance and management of large
enterprise environments.
Board of directors for RMOUG, Director of Training
Days and Database Track Lead for KSCOPE 2013
Blog: DBAKevlar.com
Twitter: @DBAKevlar
3. Performance Diagnostics in EM12c
Simple access to performance, resource usage and
demands.
Data collection to investigate performance issues-
current, recent and historical.
Capacity planning.
Have the real answer, not assumptions.
4. Presentation Agenda
Performance Out of the Box with EM12c
Top Activity
SQL Monitor
ASH Analytics
Real-time ADDM
Compare ADDM
5. Tools at your Disposal
Requires the
Diagnostics
Pack
6. Top Activity, “The Grid”
Graphical display of performance usage.
15 second refresh, manual refresh or historical.
7. When to Worry
Out of the Ordinary Activity, (KNOW YOUR DB!)
Colors outside of green and [some] blue.
Large amounts of blue, (high IO)
Remember that pink, (unknown) red,
(concurrency/application) tan, (network) and
orange, (commit) in the grid should be investigated.
Brown or black? Run for the hills! (JK)
8. Here’s our spike, which waits?
Commonly, focus on pink,
orange, red and brown for
issues.
Network and queuing do
have opportunities for
tuning, as well.
Green and blue are expected,
but also part of problems
when over utilized.
9. We’re in the Red, (Orange, too!)
Inspect
High %
use.
Note that
the update
and
execution
may be
impacting
each other.
13. The Icing on the Cake
Duh, add some memory to the EM12c box!
14. SQL Monitor for Performance
• Elapsed Time
• SQL_ID, Beginning SQL Text.
• Parallel, Waits and Execution Time
15. Digging in
• Choose your session, SQL_ID or SQL_Text
• Shows active, completed sessions for amount of time chosen.
• Shows high level wait events, dbtime, IO usage and duration.
16. Digging Down
By SQL_ID, we can inspect:
• Duration
• DB Time
• PL/SQL Java time
• Wait Activity
• Buffer Gets
• IO Requests and IO Bytes
• If Exadata, Offload Efficiency
17. Monitoring Procedural Call
All SQL_ID’s called will show, along with
duration so it’s simple to pinpoint trouble
statements.
18. SQL Details
• Note that the SQL Statement, along with elapsed time is
shown.
• Data sources from Top Activity, not AWR data.
20. Added Data
Along with the main stats-
Activity information on the statement.
The execution plan
If there is a SQL Plan or outline in place.
If there have been any tuning advisors run against the
statement
And a direct link to SQL Monitoring
21. How to Use SQL Monitoring
Active Monitoring of database processing.
Investigation of performance.
Save off reports, which provide a graphical image of
performance differing from Top Activity or ASH
Analytics.
Distinct diagnosis at a session or statement level.
22. ASH Analytics
Future of Top Activity
Package installation to database.
Always on, non-impact of Top Activity performance
data gathering.
More defined, more accurate.
Historical data enhanced over Top Activity historical
views.
24. Custom Review Pane
• You can choose to change the overview pane to display data for any
amount of time.
• Just click on the pane and drag it to the area you are interested in or
extend it to cover the areas you are interested to investigate.
• Choose your filters or view all data and you are ready to go!
27. Pick Your Poison
View data very similar to the SQL and Session data
in Top Activity.
All data is sourced by AWR data and dependent on
samples and AWR retention/interval info in the
respository.
29. Activity Details
Activity shows wait detail over time.
Processes, including parallel sessions involved
during shaded time.
Option to run AWR or ASH report.
30. The Rest of the Story
For standard SQL- Plan, Plan Control and Tuning
History is shown under individual tabs.
SQL Monitor is minimized access to the SQL
Monitor view.
32. Data Break Down
Display offers incredible diversity in wait, resource
usage and other critical event choices.
33. ASH Analytics – When to Use It
Need the more defined ASH data for EM diagnostics.
Want a second way to present data to less “DBA”
centric groups, (load map)
Database level OR session/statement level
performance diagnosis.
Dig down deep, present data in numerous formats to
get the most complete picture of a complex issue.
Can be used for Real-time or historical analysis.
34. Real-Time ADDM
Yes, it requires a PL/SQL installation for the view
data.
Uses ADDM data for the source.
Always on, low to no impact.
Normal Mode or Emergency Mode when Emergency
Monitoring is required.
35. On Your Mark, Get Set…
This is a recorded ADDM session, beginning from
the time you click “Start”.
36. In Progress Data
Ability to stop
and restart.
Findings
gathered during
progress.
Check progress
notifies of any
issues.
37. Finished!
Once finished, verify no failures/errors occurred in
the collection.
Use the tabs to investigate findings, activity, hang
data and statistics.
The number of findings are shown.
38. The Findings
Example shows low priority SQL statements using
significant db time, but not other issues at this time.
If any issues are found that are high priority, will be
listed in red and details below the main pane, (low,
medium, high priority levels.)
39. Activity Tab
Activity Data, but sourced from ADDM.
Similar output to Top Activity and ASH Analytics.
40. Wait Details
• By highlighting a wait link on the right, you can detail down to the actual wait
information for that wait event.
41. Hanging out
If a database hang situation occurred and the real-
time ADDM was used to diagnose, then the HANG
DATA tab will show any diagnostic data it has
collected during the collection.
Statistics Data:
42. Last but not Least…
Initialization Parameter data for the database
instance.
Any undocumented of non-recommended parameter
settings will be identified and listed in the findings
section.
43. Compare Period ADDM
How is it different from Real-Time ADDM?
Ability to compare TWO snapshots in time, side by side of
ADDM data.
Compares ADDM snapshots against each other, (dependent on
snapshot intervals and retention.)
All comparisons can be saved off or mailed from the console,
(mailed through EM12c settings)
45. Comparison Activity
• Clear comparison from previous day, same time to see performance issue vs.
the right hand side snapshot.
• Commonality comparison of the SQL for snapshots being compared.
• Note the concurrency, commits and increased application waits.
46. It’s all in the Details
First tab shows any configuration differences
between the two snapshots and what the
configuration parameter is.
47. Findings Summary Detail
Shows comparison increases or decreases in waits.
Lists the percentage of change between each period
compared.
Upon highlighting, details data regarding the
increase or decrease.
48. SQL Changes
We can dig down into each of the SQL Statements
found to be the highest impacts to the system and
diagnose further.
49. Finding Detail Descriptions
As shown above, the wait on Checkpoints to Tablespace are
describe below once you highlight the section in the findings
tab.
And for RAC, some waits can be broken down by instance.
50. Resource Usage: CPU
CPU Usage is viewable
by instance and total
usage.
If no CPU bound wait
issues were seen, its
stated by comparison
snapshot.
51. Resource Usage: Memory
• If you note, Memory has a warning alert by the tab to point you to it after the
comparison is completed.
• The base and comparison is in red, meaning that Virtual paging was an issue
in both snapshots.
• Data is separated by instance in RAC, showing clear usage for better
diagnostics.
52. Resource Usage: IO
I/O is separated by Throughput and Single block
read latency.
Again, if there was an issue, a warning would be on
the IO tab and the Base and Comparison would show
in red instead of green.
53. Resource Usage: Interconnect
As this is RAC, note that we also have an
interconnect tab with data on the speed and
performance.
Total vs. rate on throughput is viewed through a
radio button choice.
55. How to Use the Comparison ADDM
Excellent to diagnose “what has changed”.
“Just the Facts” information on a comparison of
time.
Dependent upon retention time settings and
intervals for AWR.
Historical data, can be set by date, custom, by
previous snapshot.
Will move to next snapshot window if mid-snapshot
time span is chosen.
56. EM12c blogs-
Leighton Nelson- http://blogs.griddba.com/
Rob Zoeteweij-http://oemgc.files.wordpress.com/
Gokhan Atil- http://www.gokhanatil.com/
Martin Bach- http://martincarstenbach.wordpress.com
Niall Litchfield- http://orawin.info/blog/
Info for Me!
Company Website: www.enkitec.com
Twitter: @DBAKevlar
RMOUG: www.rmoug.org
Linkedin: Kellyn Potvin and/or Rocky Mountain Oracle User Group
Email: dbakevlar@gmail.com or kpotvin@enkitec.com or
TrainingdaysDir@rmoug.org
Blog: https://dbakevlar.com
Reference
57. Kscope13 features more than 300
educational sessions, full-day
symposiums, hands-on training courses,
informal networking sessions, and a
plethora of chances to increase your
technical know-how by learning from the
best.
• Application Express
• ADF and Fusion Dev.
• Developer's Toolkit
• The Database
• Building Better Software
• Business Intelligence
• Essbase
• Planning
• Financial close
• EPM Reporting
• EPM Foundations and Data
Management
• EPM Business Content http://kscope13.com/registration