IBM Optim Performance Manager Extended Edition What s New. Ute Baumbach September 6, IBM Corporation

Transcription

1 IBM Optim Performance Manager Extended Edition What s New Ute Baumbach (bmb@de.ibm.com) September 6, 2011

2 What s New in Enhancements Summary September 6, 2011

3 Optim Performance Manager Enhancements Simplified deployment with internal console process Up and Running improvements Installation, startup, configuration, runtime improvements Simplified product activation Extended Insight architecture simplification Extended Insight for zos improvements Improved documentation DB2 purescale feature support - stage 1 New SQL report containing static SQL statements Restriction: Not part of the product but can be requested on demand and delivered via APAR Fixes (APARs and defects) Bundling DB2 9.7 as a limited use license for OPM Provide WLM interactive monitoring features (part of WLM configuration tooling) within OPM Enterprise/Workgroup/Content Manager Edition Previously available in OPM Extended Edition only 3

4 OPM Extended Insight and Optim Tools Integration enhancements Optim Development Studio (ODS) integrates with OPM Extended Insight by displaying OPM Extended Insight performance data per SQL statement on the ODS SQL Outline view Minimum version of OPM Extended Insight required is Note: This integration is not part of OPM 4.1.1, but is mentioned in this presentation because ODS becomes available in the same timeframe as OPM V

5 What s New in Enhancements Details September 6, 2011

6 Simplified Deployment with Internal Console Process OPM 4.1 used WebSphere Application Server (WAS) to serve the OPM web console Either OPM installer installed WAS or a preinstalled WAS was used Now OPM uses an internal console process to serve the OPM web console New OPM installation The installer sets up the internal console process and asks for port numbers No possibility any more to use a preinstalled WAS Update installation from OPM 4.1 or The installer sets up the internal console process and asks for port numbers Previous installed WAS as part of OPM is uninstalled If preinstalled WAS was used then it is possible (but not recommended) to further use it Manual migration process necessary to further reuse it Web-container authentication method is not supported any more 6

7 Update Installation to OPM Migration Information If you use web container authentication before V4.1.1 do one of the following Before starting the install, change to repository database authentication and grant web console access to users, groups, or roles Let the installation change to repository database authentication. After install, log into the web console as the DB2 user of the OPM DB2 instance and grant web console access to other users, groups, or roles Note that the users, groups, or roles need CONNECT privilege to the repository database before you can grant web console access on the Console Security panel 7

8 Port Specification Panel for the Web Console This panel is shown for new and update installations of OPM

9 Continuing to Use WebSphere Application Server for an Optim Performance Manager Upgrade If you are using a fully licensed copy of WebSphere Application Server Can continue using this fully licensed copy as a web container for Optim Performance Manager by manually upgrading Optim Performance Manager. For information about how to manually upgrade Optim Performance Manager, contact IBM Software Support You may choose to do this, for example, to avoid disturbing a working OPM web environment or because you are using needed WebSphere functionality, such as specialized authentication and authorization mechanisms See also tatools.perfmgmt.installconfig.doc/app_server_support.html 9

10 OPM Extended Edition Architecture OPM system Repository Meta Snapshot E2E RS API Optim Performance Manager Console server Configuration, Dashboards Alerts, Health HTTP Browser (IE/Firefox) OPM Console DB2 LUW ESE Insert maintain Repository server TCP/IP All PE V3.2 level functionality PE Client Client Information Tx Metrics SQL Metrics OPM Extended Insight Java application JCC driver OPM EI TCP/IP DB2 Attachment Snapshots DRDA DRDA Monitored Monitored DB2 DB2 LUW Monitored DB2 LUW LUW TCP/IP DB2 Connection SQL Collection Event Monitors SQL Text SQL Metrics Tx Metrics DRDA Client Information Tx Metrics SQL Metrics CLI driver OPM EI CMX OPM Extended Insight.Net application.net driver C/C++ application WAS Cognos SQW DataStage SAP 10

11 Up and Running Unified Product Activation For OPM Extended Edition, one single activation kit activates OPM and Extended Insight Before: 2 activation kits for OPM and Extended Insight New install Activation combined in installation process if you specify the lic file Includes specification of Extended Insight controller and monitor ports Call activation separately if you installed a try and buy edition first OPM repository server restart during activation might be necessary Update install from OPM If update from OPM Extended Edition then the upgrade install asks for the Extended Insight ports No need to run the activation kit separately Run the Extended Edition activation kit if you installed OPM Enterprise/Worgroup/Content Manager Edition first, but want to upgrade to OPM Extended Edition The activation kit changes the license and asks for the Extended Insight ports OPM repository server restart during activation might be necessary 11

12 Up and Running - Starting and Stopping OPM New start and stop scripts are introduced to start OPM repository server and the console server in a single command On UNIX/Linux as a SYSADM user of the DB2 instance OPM uses Start/Stop/status of OPM (web console and repository server) OPMstart.sh, OPMstop.sh, OPMstatus.sh Start/Stop/status of OPM web console OPMstart.sh WebClient OPMstop.sh WebClient OPMstatus.sh WebClient Start/Stop of OPM repository server OPMstart.sh RepositoryServer OPMstop.sh RepositoryServer OPMstatus.sh RepositoryServer On Windows The program menu entries in the Windows start menu start and stop the web console and the repositoryserver If you want to start/stop the console server and repository server independently, then do that via the services window 12

13 Up and Running More Flexibility to Adjust Repository Database Configuration Parameters Changed behavior for updating configuration parameters of the repository database Default behavior OPM changes some configuration parameters during installation and configuration to the values it requires If you change them manually OPM resets them to the required values The configuration parameters AUTO_MAINT, AUTO_RUNSTATS, AUTO_REORG, AUTO_TBL_MAINT are only set during installation to ON If you change them manually to OFF, OPM does not reset them to ON Note: If you change them manually to OFF you are responsible doing manual maintenance tasks e.g. by running the perunstats.ddl and pereorg.ddl scripts that OPM provides If you do not want OPM to reset changed configuration parameters, then add the peconfig.db_cfg_updates = no parameter to the db2pesrv.prop file The db2pesrv.prop file is located in the repository server working directory Restart OPM afterwards See also 13

14 Up and Running Changing the Default Retention Period of SQL statements Collected by Extended Insight If you use Extended Insight, then OPM retrieves all statements from the package cache of the monitored database and saves them in a dimension table If the saved statements are not executed within a certain timeframe (dimension_retention_period) by Extended Insight Clients then OPM deletes them from the dimension table. In some environments, especially if you use Extended Insight for zos databases, the default dimension period might be too short. Statements are deleted before Extended Insight clients execute them. This leads to missing statement text on the Extended Insight dashboard You can extend the pruning interval by setting the one of the following properties in the db2pesrv.prop file clean.dimension_minimum_retention_period = <number of hours> clean.dimension_minimum_retention_period.<instance_id> = <number of hours> Restart the OPM server afterwards For LUW databases the default retention period is 1 hour For zos systems the default retention period is 1 week 14

15 Up and Running - Collecting Bufferpool Information in Different Intervals than Table and Table Space Information A new parameter is introduced to allow you to collect table and table space information (as part of the I/O and Disk space monitoring profile ) in higher sampling intervals than buffer pool information (as part of the Basic monitoring profile and I/O and disk space monitoring profile) Use this parameter when you monitor a partitioned system with a high number of tables and table spaces Name of parameter? ISAS_TBL_TBLSPACE_FREQUENCY Where to set it? DB2PM_<instanceId>.PARAMETER table in repository database What it means? Specifies the collection frequency of the table and table space snapshot For example setting it to 5 means, that 4 snapshots are to be taken without table+table space information and the 5th snapshot with table and table space snapshot information Usage For each monitored database, where the different collection is needed, insert a new row into table DB2PM_<instanceId>.PARAMETER. OPM server does not need to be restarted. Sample INSERT statement with frequency 5 insert into DB2PM_<instanceId>.PARAMETER values ('ISAS_TBL_TBLSPACE_FREQUENCY', 'I', 'N', 5, '0', '', NULL, NULL) 15

16 Up and Running - Keep Monitor Switches Unchanged When Disabling Monitoring Profiles or Unconfiguring Monitoring A new parameter is introduced that prevents OPM turning off monitor switches when you disable monitoring profiles or unconfigure monitoring of a database Use this parameter if your monitoring policy requires that the switches are turned on even if OPM is not monitoring the database Use this parameter to avoid the OPM collection user that you specify during monitoring configuration of a database requiring SYSADM rights for the monitored instance See privilege requirements in information center atools.perfmgmt.installconfig.doc/pm_configure_monitoring.html Name of parameter? KEEP_MONITORING_SWITCHES Where to set it? DB2PM.PARAMETER table in repository database (global setting) DB2PM_<instanceId>.PARAMETER table in repository database (per instance setting) What it means? The global setting ensures that the monitoring switches are not turned off on any DB2 instance that OPM monitors. The per instance setting allows to set it per monitored DB2 instance Usage Either set the global setting once or the per instance settings in multiple PARAMETER tables. The global setting has priority if global and per instance settings exist. The OPM server does not need to be restarted 16

17 Up and Running - Keep Monitor Switches Unchanged When Disabling Monitoring Profiles or Unconfiguring Monitoring (cont.) Sample INSERT statement for global setting insert into db2pm.parameter values ('KEEP_MONITORING_SWITCHES', 'F', 'Y', 0, NULL, 'Prevents disabling of the db2 monitoring switches globally', NULL, NULL) Sample INSERT statement for per instance setting insert into db2pm_<instance id>.parameter values ('KEEP_MONITORING_SWITCHES', 'F', 'Y', 0, NULL, 'Prevents disabling of the db2 monitoring switches for this monitored instance', NULL, NULL) 17

18 Up and Running Health Monitoring and Alerting Improvements New health alert for partition down Lock wait threshold set to higher values in some predefined system templates to reduce of exessive number of lock wait alerts that happened in some customer environments after applying a predefined system template OLTP production system with all details : (5sec) OLTP production system with low overhead : (5sec) BI production system with all detail : (2min) Thresholds of Failing Transactions % alert set to higher values for all predefined system templates to reduce the high number of alerts in some environments after applying a predefined system template New thresholds Warning: 7% Critical: 10% 18

19 Up and running - Event Monitor Improvements OPM creates the package cache event monitor now also as a tandem event monitor Used for Extended Insight for DB or higher Ensures that a high number of statements can be processed in time All DB2 9.7 event monitors (package cache, unit of work, lock) now use the TRUNCATE statement to delete the read records from the event monitor tables Event monitors used when monitoring DB or higher Before OPM used DROP/CREATE to prune the read data records which had the following disadvantage DB2 recovery history file got very large Workaround: Use tablespaces with DROPPED TABLE RECOVERY = OFF 19

20 Up and Running - Health Summary Performance Improvement Option The Health Summary dashboard now by default does not display the numeric metric columns any more as was done in earlier OPM releases This ensures a better display performance for a higher number of databases To get the the numeric metric columns displayed, open the Services panel from Task Manager and enable the Health Metrics. Afterwards, refresh the Health Summary dashboard to get the the metric columns displayed 20

21 Up and Running - Extended Insight Architecture Simplification New Single Monitor architecture Employs a single port for a single Monitor server, instead of employing separate dynamically allocated ports for each monitored database, each monitored by its own Monitor server. Simplifies administration effort in configuring ports that may pass through firewallls Eliminates lag times encountered by clients that must rediscover newly allocated ports after OPM restart During OPM installation or activation, the user is asked for the controller and monitor port The specified ports are saved in the repository database Auto-discovery of the Extended Insight controller via UDP multicasting is deprecated Controller will continue to broadcast its location via UDP multicast for the benefit of down-level clients An OPM server running on an IPv6 configured system now supports Extended Insight clients running on IPv4 configured systems Previously, all EI client machines and the OPM server machine all had to be at the same IP level, all IPv4 or all IPv6 An OPM server with multiple network cards is now supported for Extended Insight 21

22 OPM Extended Insight Architecture and Install Steps OPM system Repository DB2 LUW ESE Optim Performance Manager Console Server Repository Server Extended Insight Controller (Default port 60000) EI Metric Collectors EI Monitor Server (Default port 60001) Step 2: Install and configure EI client or continue to use down-level EI clients (V4.1.0, V ) Client system CMX OPM Extended Insight Client JCC driver.net driver CLI driver A P P L I C A T I O N Step 1: Install OPM Server Included in Step 1 or as separate step: Activate Extended Edition license for OPM Server (includes activating EI and specifying EI ports) Monitored DB2 LUW Monitored DB2 LUW Client system CMX OPM Extended Insight Client JCC driver.net driver CLI driver A P P L I C A T I O N 22

23 Extended Insight Port Specification in Activation Kit and Client Configuration Panel in installation and activation kit to specify ports Panel in EI client configuration to specify ports 23

24 Extended Insight Port Specification in Web UI The Extended Insight ports that were specified during installation or activation can be changed here 24

25 Changes on Extended Insight Monitoring Profile Panel Due to New Port Architecture OPM offered the specification of a fixed Extended Insight monitoring port per monitored database in the Extended Insight monitoring profile In OPM this has been removed now since Extended Insight works with 2 global ports only, one for the controller and one for a single monitor server As a new function you can now view all Extended Insight clients that are configured for this database by clicking the View button 25

26 Up and Running - Extended Insight for zos Improvements It is now possible to specify the minimum retention time of SQL statements collected by Extended Insight See slide 14 Fixed problems within predefined SAP workload cluster groups Web UI fixes Additionally apply DBSL patch level described in SAP Note for your SAP release Release Patch level 6.40 patch level patch level patch level patch level patch level patch level 84 Other enhancements of that apply to using Extended Insight for zos Simplified deployment with internal console process Simplified extended insight architecture 26

27 Up and Running- Improved Documentation The information center content has been restructured and enhanced Now included a deployment and capacity planning chapter that gives you the information you need in order set-up OPM optimally Planning and installation information in information center ols.perfmgmt.installconfig.doc/pm_installconfigure.html Improved instructions and explanations on installer panels, especially on activation and configuration panels of Extended Insight 27

28 DB2 purescale Feature Support - Stage 1 Provide monitoring metrics about the cluster caching facility (CF) on the Overview dashboard CF CPU and memory utilization Group Buffer Pool Hit Ratio CF lock timeouts, lock escalations, and transaction lock wait time Show enhanced system information on System dashboard Host status, instance status, CF requests and time, more CPU values,... Member information for locking problems on Locking dashboard Provide DB2 purescale system templates DB2 purescale production with all details DB2 purescale production with low overhead 28

29 Overview Dashboard for DB2 purescale System 29

30 System Dashboard for DB2 purescale System CF details 30

31 System Dashboard for DB2 purescale System (cont.) Member details 31

32 New SQL Report Containing Static SQL Statements Not part of OPM but can be requested on demand Request this report via contacting your IBM representative or by opening a PMR. The report will then be delivered via an APAR Prerequisite to run this report The monitored database must run on DB2 9.7 fix pack 1 or higher Extended Insight must be activated for the monitored database (on server only) Contents of the report Based on the existing Dynamic SQL report Lists top packages Selecting a package opens a new report page listing all used statements of the package Selecting a single statement opens a new report page displaying the execution details of the statement 32

33 APARs OPM contains a set of APARs that were provided to customers as special builds based on OPM The complete list of APARs can be explored here For OPM For OPM EI Some of the APARs require manual steps in order to exploit the function or fix that is introduced in the APAR For example PK99961 PK99962 (manual steps described on page 16, 17) PK99928 (manual steps described on page 15) 33

34 Optim Development Studio (ODS) and OPM Integration Details Optim Development Studio (ODS) integrates with OPM Extended Insight and higher by displaying OPM Extended Insight performance data per SQL statement on the ODS SQL Outline view Steps 1) Import data from the OPM repository for a specific timeframe for your database 2) Display the imported data on the SQL Outline view Displayed performance data per statement Number of Times Run Total Server Time Average Server Time Average Network Time Average Number of Rows Examined Average Number of Rows Returned Rows Returned Ratio CPU time Number of Sorts Average Number of RSCANs Average Number of ISCANs Number of physical IOs Number of logocial IOs 34

35 Improved services - Capacity planning and Health Checks The OPM support and development team offers the following free services around your OPM deployment Before OPM deployment: Capacity planning for your OPM deployment in order to determine the needed resource requirements for the OPM machine Sizing formulas improved for OPM Option to use a script to get more accurate estimates Get instructions and questionaire here rson/ p9/file/f7d3089b-aa5e-4496-b1b c2ef226 After OPM deployment: A health check of your OPM deployment after it has monitored the configured databases for a few days Collection of configuration details and log files to check for errors, collection bottlenecks, and resource shortages Contact OPM support, development (Ute Baumbach bmb@de.ibm.com) or your IBM representative to get these services 35