Picture 1.6 Once you have configured your managed systems you will have the additional options available in the DBACOCKPIT (DB02). You can choose to either fill in a Begin Snapshot and an End Snapshot and analyze the data in between those two points in time or you can also provide a second Begin Snapshot and End Snapshot and analyze the different between the two ranges. 
In a recent blog (The specified item was not found.) by fresh SAP Mentor David Hull @sapdba the Database performance warehouse was featured. SAP announced they would also provide eight reports for Oracle but I haven’t seen it in action yet and I couldn’t find any SAP notes on it either. I mentioned in the comments of David’s blog that Oracle has a number of reports available that can be enabled to be used in SAP Solution Manager. For example generating an AWR report or viewing the Active Session History. Those reports are part of the diagnostics & tuning pack. Since there was a request to have some more information/instructions this blog was created. h4. Important SAP Notes *Check these SAP Notes after reading the blog. For some releases you need to implement source code corrections to ensure everything works properly.* {code:html}Note 740897 - Info about the Oracle license scope; Required Oracle options{code} {code:html}Note 853576 - Oracle 10g: Performance analysis w/ ASH and Oracle Advisors{code} {code:html}Note 1028068 - Required Oracle options for the DBA Cockpit{code} {code:html}Note 1250596 - Diagnostic package for Oracle systems in the DBA Cockpit{code} h4. What do you get? 
* *
* *Picture 1.0
*Enabling the Diagnostics package provides the following:*
- Workload Reporting (see picture 1.0)
- Active Session History
- System Metrics
- System Summary Metrics
- File Metrics
- Wait Class Metrics
+Source bullet list: extract from SAP +{code:html}+Note 1028068 - Required Oracle options for the DBA Cockpit+{code}+ +
*Enabling the Tuning package provides the following:* h4. Licensing 
Picture 1.1 - +reference SAP Note 740897+ Picture 1.1 is an extract from SAP Note 740897 and shows that if you have your Oracle license through your SAP license then you are allowed to use the Diagnostics Pack and the Tuning Pack. Most customers order their SAP software with an included Oracle license when they run their SAP system on Oracle. If you are unsure, check with your purchasing department. h4. Enabling the Diagnostics Package It is a good idea to have your managed SAP systems inserted into the DBACOCKPIT of your SAP Solution Manager. It is also what I’m basing this blog on as it’s considered to be best practice to do so. You can however derive the steps to perform the changes locally and have the features available locally. This blog is based on Solution Manager 7.0 EHP1. 
Picture 1.2 In your Solution Manager go to DB02 and click on System Configuration. 
Picture 1.3 You should now get a list of your managed SAP systems on the right pane. 
Picture 1.4 Double click on the System name of one of them to check the details. Under Collector Options you should see ORACLE Diagnostics Package is licensed enabled. If it’s not enabled you should be able to enable it by going into edit mode, checking the checkbox and saving afterwards. 
Picture 1.5 If for some reason the option stays grayed out in edit mode, the flag is set in table DB6NAVSYST. Field LICENSE EXT needs to have a X as value. +Remember you are only supposed to activate this if you have the proper license for it.+ h4. Enabling the tuning package To enable the tuning package you have to add a line to table ORA_FEAT_USED containing the following content for each managed SAP system to be configured: | | * *
* * | |
*FIELD* | VALUE |
* * |
|
*REMSYS* +*has to equal value of DB02 SID of the managed SAP system: for example AA1_SLD+*FEATURE* * * | TUNINGPACK |
*IS_USED* * * | X | More information on the tuning package can be found in SAP {code:html}Note 1028068 - Required Oracle options for the DBA Cockpit{code}. h4. An example of an AWR |
2 Comments
