Skip to Content

Task 4.6: Configure the Strobe for Db2 Options


31704_FastForward_50x50_icon_4.png

This task guides you through configuring the support for Db2 in Strobe. Proceed to Task 4.7: Verify Product Installation if you are not licensed for Db2.

31704_Roles_50x50_icon_10.png

The Db2 database administrator is required for this task.

Task 4.6.1: Bind StrobeDb2 Packages and Plan and Grant Required Privileges

31704_Important_50x50_icon_17.png

Review the following restrictions:

  • A Db2 database administrator with SYSADM authorization should execute the following steps for each Db2 subsystem where Strobemeasurements will occur.
  • Do not change StrobePackage, Collection, Plan Names, or Bind parameters.
  • Enabling New Function subsystems is not supported.
  • If your site uses your Security Package to provide Db2 authorization, the equivalent GRANT authorization found in SBDB2INS needs to be made.
  • If the Security Administrator changed the name of STRTSSA in StrobeStarted Tasks, update the name in the SBDB2INS JCL before submitting the job.
  • STRSSA should be assigned the same, or higher, dispatching priority as the Db2 MSTR address space. Running it at a lower priority could result in measurements with missed Db2 data.
  • Compuware recommends granting PUBLIC execution authorization to its PLAN, STRANANA. If restrictions prohibit granting it to PUBLIC, a list of authorization IDs that will be executing StrobeSQL Analysis is required. This list must include all StrobeSQL Agent authorization IDs because they also access the plan.
  • StrobeSQL Agent authorization IDs, typically STRTSSA, must be granted TRACE and MONITOR2 authorization.
  • If you are running Db2 Version 12, Function Level 500 or more current, add option ‘APPLCOMPAT(V12R1M500)’ to each ‘BIND PACKAGE’ command in the SBDB2INS JCL member.

Bind the StrobeDb2 Packages and Plan and Grant Authorization by completing the following steps:

  1. Edit the SBDB2INS JCL member found in the hlq.SSTRSAMP library and make the changes as directed in the JCL.
  2. Change STRSSA to STRTSSA.
  3. Submit the JCL.
  4. Repeat the steps for each Db2 subsystem where Strobemeasurements will occur.

Task 4.6.2: Create Db2 Explain Tables

31704_FastForward_50x50_icon_5.png

If Explain tables from your production Strobeinstallation are available to be used with your test installation, skip this task and proceed to Task 4.7: Verify Product Installation.

Before you can create a Performance Profile for iStrobethat contains StrobeSQL Analysis reports, a PLAN_TABLE, DSN_FUNCTION_TABLE, DSN_PREDICAT_TABLE, and DSN_STAT_FEEDBACK (optional DSN_QUERYINFO_TABLE if used at your site) must exist for the resolved or secondary authorization ID of the user/job running the reports. The table qualifier must match the authorization ID of the user executing reports.

31704_Tips_50x50_icon_15.png

If user DB2USER1 wants to generate a Strobeprofile that contains SQL Analysis, DB2USER1 needs one of the following:


    • A set of explain tables created with the qualifier DB2USER1.
    • A secondary user ID set up for DB2USER1— for example, STROBE and a set of explain tables created with the qualifier STROBE.
    • A set of explain tables created with a generic qualifier — for example, STROBE and aliases created against them for DB2USER1.
      CREATE ALIAS DB2USER1.PLAN_TABLE FOR STROBE.PLAN_TABLE;

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Compuware Strobe 18.02