Database Tuning is outside of the scope of the Jazz Administrator. Any information contained below is for reference only and should be passed on to your D.B.A. |
When discussing the tuning of DB2, it is important to be aware of the differences between the various types of DB2. There is DB2 Workgroup, DB2 Enterprise, and DB2 for z/OS. Jazz licensing currently provides an entitlement for the use of the DB2 Workgroup edition.
DB2 Express is also supported, but it should NEVER be used for anything other than a product demo, pilot project, or functionality review. It will not scale to support a typical user load.
Most DB2 customers will turn on the following monitoring and tracing for their Jazz supporting DB2 instance on zOS:
TNO | TYPE | CLASS | DEST | QUAL | IFCID |
01 | STAT | 01,03,04,05, | SMF | NO | |
01 | 06 | ||||
02 | ACCTG | 01,02,03,07, | SMF | NO | |
02 | 08 | ||||
04 | MON | 01,02,03,05, | OP1 | NO | |
04 | 07, 08 |
What does all of this mean?
When working with DB2 you should be doing a RUNSTATS [multi-table, multi-index] whenever you make any changes to the DB2 database. It should then be done by the database administrator on a regular basis, to make sure that DB2 performs efficiently.
If this doesn’t work, you might want to increase MAX_R_BLOCK in the zOS parameters.
Note: A good DB2 Administrator will want to create indexes based on the results from some of the monitoring and the RUNSTATS commands. They can do this, but make sure that you measure database performance both before and after doing this, so you can determine it's impact on your performance. |
Need real tuning examples here
Need real tuning examples here
Warning: Can't find topic Deployment.TuningDB2Comments
Status icon key: