Enkitec Oow 2013 JB Session

14
About Us I am… Oracle ACE Director Sr. Technical Consultant, Enkitec Enkitec is an Oracle Platinum Partner specializing in the following areas: Oracle Exadata Oracle Database, including RAC Oracle Database Performance Tuning Oracle APEX and so much more!

Transcript of Enkitec Oow 2013 JB Session

Page 1: 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!

Page 2: Enkitec Oow 2013 JB Session

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!!

Page 3: Enkitec Oow 2013 JB Session

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.

Page 4: Enkitec Oow 2013 JB Session

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.

Page 5: Enkitec Oow 2013 JB Session

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.

Page 6: Enkitec Oow 2013 JB Session

Top SQLSTATS_ADMIN??SQL Analyze??

} What does this SQL Originate from?

Page 7: Enkitec Oow 2013 JB Session

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.

Page 8: Enkitec Oow 2013 JB Session

ASH Report Define CPUBreakdown by the minute, by interval.

Page 9: Enkitec Oow 2013 JB Session

Ash AnalyticsCPU + Wait for CPU can be misleading.Is the CPU simply used or is here a real

problem?

Page 10: Enkitec Oow 2013 JB Session

Parallel, Not Just for Reporting Anymore

When SQL Tuning Advisor Automated Jobs are NOT your Friend…

Page 11: Enkitec Oow 2013 JB Session

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.

Page 12: Enkitec Oow 2013 JB Session

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.

Page 13: Enkitec Oow 2013 JB Session

Data Load Per Hour IncreasePerformance Increase Post Stats Change-

Page 14: Enkitec Oow 2013 JB Session

Where they Are Today…With further enhancements, both physical

and logical tuning:

750 !!