Crack the complexity of oracle applications r12 workload v2
Download as PPTX, PDF1 like1,349 views
This document summarizes Ajith Narayanan's presentation on characterizing Oracle Applications R12 workload. The presentation covers instrumentation, collection, classification, measurement, and interpretation of workload data. The goal is to understand workload trends and impacts in order to optimize system resources and performance. Key aspects discussed include identifying workload classes like forms, batches, and self-service applications; measuring resource usage correlated to workload; and using interpretations to make scheduling and tuning decisions.
![2
GE Title or job number
12/14/2015
Ajith Narayanan
10+ years of Oracle [APPS] DBA/Technical Architect
experience.
Oracle ACE Associate
Blogger :- http://oracledbascriptsfromajith.blogspot.com
Member:-OAUG, AIOUG
AIOUG Real Application Clusters SIG Leader
Ex-Website Chair (2011-2013) – Oracle RACSIG
http://www.oracleracsig.org
Who Am I](https://image.slidesharecdn.com/crackthecomplexityoforacleapplicationsr12workloadv2-151214140227/85/Crack-the-complexity-of-oracle-applications-r12-workload-v2-2-320.jpg)
Crack the complexity of oracle applications r12 workload v2
- 1. Crack The Complexity Of Oracle Applications R12 Workload Ajith Narayanan Oracle ACE Associate 8th- Nov -2014, Bangalore, India.
- 2. 2 GE Title or job number 12/14/2015 Ajith Narayanan 10+ years of Oracle [APPS] DBA/Technical Architect experience. Oracle ACE Associate Blogger :- http://oracledbascriptsfromajith.blogspot.com Member:-OAUG, AIOUG AIOUG Real Application Clusters SIG Leader Ex-Website Chair (2011-2013) – Oracle RACSIG http://www.oracleracsig.org Who Am I
- 3. 3 GE Title or job number 12/14/2015 1. Introduction 2. Challenge 3. Workload Characterization 4. Instrumentation 5. Collection 6. Classifying Workload 7. Measure 8. Interpret 9. Conclusion 10. Q&A Agenda
- 4. 4 GE Title or job number 12/14/2015 Oracle Applications R12 is one of the flagship products from Oracle . Oracle Apps R12 implementations are quite large with more and more customizations done over a time. Being a huge product with 200+ products packaged most of the architects and DBA's find it difficult to understand the workload trend of the system. Customization's further contribute to the complexity. Take Away End of this session, we should be able get the functional perspective of our EBS system workload and its impact in 360º Introduction Functional User View Logical Developer View Physical Computer view
- 5. 5 GE Title or job number 12/14/2015 Oracle Application R12 has a very rich techstack. Understanding each components, analyzing the sizing requirements for each of these components is really tricky and tedious job. Forms, Reports, Self Service Applications, Concurrent Programs We will be trying to understand Workload characterization process by identifying classes of workload, measuring those classes and then identifying their impact to the business. Challenge
- 6. 6 GE Title or job number 12/14/2015 Workload Characterization Instrumentation Collection Classify Measure Interpret
- 7. 7 GE Title or job number 12/14/2015 We should be starting our analysis from the database (Matrices related to our workload) Understand the business process that is responsible for the peak workload. Know the workload in functional perspective to have a clear picture ( Batch, Forms, Self Service, Java, FMW, OA Framework Etc.) For the critical business process and related workloads, we should be ensuring that enough resources are available, since they are not available for compromises. Workload Characterization
- 8. 8 GE Title or job number 12/14/2015 Workload Characterization Instrumentation Collection Classify Measure Interpret
- 9. 9 GE Title or job number 12/14/2015 Forms Workload –Must be explained on the degree at which it impacts business. apps.fnd_login_resp_forms apps.fnd_logins apps.fnd_form_tl apps.fnd_login_resp_forms apps.fnd_application_tl Instrumentation
- 10. 10 GE Title or job number 12/14/2015 Batch workload Apps.fnd_concurrent_requests Self-Service Applications apps.icx_sessions DBMS_APPLICATION_INFO package set_client_info set_module set_action procedures Instrumentation
- 11. 11 GE Title or job number 12/14/2015 Additional attributes to extended SQL trace data as well. Instrumentation • Identify foreground sessions with “SYS$USERS” & background sessions with “SYS$BACKGROUND”.
- 12. 12 GE Title or job number 12/14/2015 Instrumentation • Client Identification:- Use, DBMS_SESSION.SET_IDENTIFIER Application Information
- 13. 13 GE Title or job number 12/14/2015 Instrumentation • Module Information (With action performed) • ASH – Active Session History Once a session disconnects the details are not available through the V$SESSION based views, ASH overcomes this problem with ability to catch sessions that might have otherwise been missed using the V$SESSION view. The data is sampled at 1 second interval, so the data is more granular than most attempts at sampling the V$SESSION based views.
- 14. 14 GE Title or job number 12/14/2015 Instrumentation • Tools Advantage (SQL*Plus commands ) SQL> set pages 9999 SQL> show appinfo appinfo is ON and set to "SQL*Plus" SQL> set appinfo on; SQL> show appinfo appinfo is ON and set to "SQL*Plus" SQL> set appinfo "AjithNarayanan" SQL> variable mod varchar2(30) SQL> variable act varchar2(30) SQL> execute dbms_application_info.read_module(:mod,:act); PL/SQL procedure successfully completed. SQL> print mod MOD -------------------------------- AjithNarayanan SQL> print act ACT -------------------------------- SQL> show appinfo appinfo is ON and set to "AjithNarayanan" SQL> set appinfo off SQL>
- 15. 15 GE Title or job number 12/14/2015 Instrumentation • OACore JVM usage can provide a 360 degree view of the Application workload using GCViewer.
- 16. 16 GE Title or job number 12/14/2015 Workload Characterization Instrumentation Collection Classify Measure Interpret
- 17. 17 GE Title or job number 12/14/2015 Collection • In an Oracle Applications system for example, concurrent manager jobs have a broad enough mix of runtimes that collection by interval is usually not very productive. • Forms users on the other hand tend to stay connected for a longer period of time and a logoff trigger misses the peaks and valleys of that type of workload. • OACore JVM usage by modules can provide a 360º view (GCViewer).
- 18. 18 GE Title or job number 12/14/2015 Workload Characterization Instrumentation Collection Classify Measure Interpret
- 19. 19 GE Title or job number 12/14/2015 Classifying Workload • Once we have instrumentation in place & data collection done, We need to classify the workload with a functional perspective. • Some important modules used by the E-Business R12 are: – Oracle Financials: Accounts Payable, Accounts Receivable, Fixed Assets, General Ledger – Human Resource Management System – Customer Support: Service – Supply Chain Management (SCM): Logistics, Order Management, Purchasing, Shipping – Self-Service Applications: Employee Self-Service, iExpenses, iProcurement, Oracle Time & Labor
- 20. 20 GE Title or job number 12/14/2015 Classifying Workload • Sample of collecting useful information for classifying the workload. • Once the classification of our system workload is complete, We now will have. the functional perspective of the total work.
- 21. 21 GE Title or job number 12/14/2015 Workload Characterization Instrumentation Collection Classify Measure Interpret
- 22. 22 GE Title or job number 12/14/2015 Measure • After workload classes are identified then measurements can be grouped by class and summarized.
- 23. 23 GE Title or job number 12/14/2015 Workload Characterization Instrumentation Collection Classify Measure Interpret
- 24. 24 GE Title or job number 12/14/2015 Interpret • Interpretation leads to • Understanding the overall impact of each workload class on the total workload. • Charts can be easily created by co-relating the workload class and the resource usage metrics • Decisions can then be made about work shift allocations or redistribution, and about possibly re-scheduling work to non-critical time periods.
- 25. 25 GE Title or job number 12/14/2015 Interpret Application SQLstmts Processes User Experience Oracle OperatingSystem Work CPUSubsystem Time (Time Based Analysis) IOSubsystem Memory Subsystem Network Subsystem Massive CPU Bottleneck 99% CPU 1% (Wait) Latching CPU Intensive SQL Get more CPU power (Short Term) or Look if high CPU consuming SQLs can be avoided from running at peak hours 1% wait time for acquiring cache buffer chain latches – Add CBC latches TOP SQLs by CPU – Tune the SQL or Reduce the number of executions
- 26. 26 GE Title or job number 12/14/2015 Interpret Application SQLstmts Processes User Experience Oracle OperatingSystem Work CPUSubsystem Time (Time Based Analysis) IOSubsystem Memory Subsystem Network Subsystem IO Read bottleneck 30% CPU 70% Wait (Single Block Sync Read) High Physical Read SQLs Add more devices – More IO read capacity Keep blocks in buffer cache Cache the key tables (Beneficial only if the blocks are repeatedly touched) TOP SQLs by Physical Reads or Executions (Tune it or Reduce its executions
- 27. 27 GE Title or job number 12/14/2015 Conclusion • This session brings awareness of few basic and already existing, small & powerful features in Oracle that can do a lot of help in understanding our system workload, • These features can provides us with all necessary leads to start tuning the system for optimal performance and sustainability.
- 28. 28 GE Title or job number 12/14/2015 Q&A
- 29. 29 GE Title or job number 12/14/2015 Thank You! Contact:- [email protected]