Enkitec Oow 2013 JB Session
Transcript of Enkitec Oow 2013 JB Session
About UsI am…• Oracle ACE Director• Sr. Technical Consultant, EnkitecEnkitec is an Oracle Platinum Partner specializing in the following areas:Oracle ExadataOracle Database, including RACOracle Database Performance TuningOracle APEX and so much more!
Your Challenge, if you accept it..Upgraded to 11g in previous year.“Hybrid” environment, used for transactional,
ETL and reporting.Consistent degradation in last year.Had loaded on average 400 “business”
through ETL per hour, now down to 2-300.Code review and enhancement of ETL
process in works, but “what can you offer us outside of that?”
Goal: Load 700 business per hour!!
Tools of the Oracle TradeAWR data was first offered by onsite DBA,
but switched to ASH to provide more defined, smaller timeline data collections.
Gave more clear samples of what was occurring in the database at a given time.
Drilled down to code that was deprecated and unexpected.
EM12c available and used to enhance findings from ASH reports and to provide further research.
Why AWR Wasn’t the AnswerSmaller snapshots in time to allow more
definitive picture of performance challenges and when occurring.
Quantity of executions were not focus, but wait times.
Why ASH Was…More definitive breakdown of data.Session level information.Wasn’t interested in how many times, wanted
to know what was the impact.
Top SQLSTATS_ADMIN??SQL Analyze??
} What does this SQL Originate from?
SQL Profiles with DBMS_ADMINBy viewing Session SQL history from EM12c, was
able to see how reality was askew vs. what “analyze” of tables fed the CBO and SQL Tuning Analyzer. SQL Profiles were NOT offering better, more stable performance.
ASH Report Define CPUBreakdown by the minute, by interval.
Ash AnalyticsCPU + Wait for CPU can be misleading.Is the CPU simply used or is here a real
problem?
Parallel, Not Just for Reporting Anymore
When SQL Tuning Advisor Automated Jobs are NOT your Friend…
What Caused This?Due to high profile environment, change that
could be impacting was avoided, including stats collection enhancement in proprietary package implemented in 9i.
DBMS_ADMIN was deprecated and it’s “analyze” of objects did not offer proper data for Cost Based Optimizer.
Tuning Analyzer was implemented as part of 11g upgrade automatically and utilizing valuable ETL time resources.
Steps to CorrectMigrated to full DBMS_STATS collection,
disabling jobs using STATS_ADMIN pkg with DBMS_ADMIN.
Removed SQL Profiles that were impacted by incorrect information fed to CBO by DBMS_ADMIN.
Migrated select b-tree indexes to bitmap indexes, also much needed disk space.
Continued to review ASH, AWR and Session SQL performance for improvement.
Data Load Per Hour IncreasePerformance Increase Post Stats Change-
Where they Are Today…With further enhancements, both physical
and logical tuning:
750 !!