Why won’t you just die?! (Cleaning DB2 Process in Memory)

You may also like...

7 Responses

  1. Sandip says:

    Hi Ember,

    First of all let me thank you for your wonderful blogs which are so informative, resourceful and easily understandable. Humble recommendations for future blog topics –
    a) Can you write an article about db2top utility and the various practical ways in which it could be used to diagnose or investigate different types of issues? I don’t think there are many informative articles about db2top available on the internet.
    b) I know this may be a tough one. Decoding access plans is a challenge for any DBA. Query tuning was an art in my opinion, and it spans way beyond converting your table scans to index scans, which is where most DBA’s declare success. However I have seen a number of cases in my own project, where “ugly” access plans (with table scans) run much faster than ones with only index scans. Sometimes DB2 tries to ignore indexes even though you think you have created the best one for that particular query and in other cases, DB2 chooses a “dirty” index which you wouldn’t want it to. Apart from indexscans and index statistics, the type of “join” operators also hold a key to the efficiency of the operation being performed. As a result of all these, I have come to a state where the more queries I tune, the more number of uncertainties keep propping up which leave me less confident ultimately. And there aren’t many tutorials which teach you what to look for in an access plan (apart from the scans), how do you determine if a plan is an efficient one or not, what are the various parameters or data items in an access plan you should look at, and so on and so forth. So I thought it would be good if you could write an article on “How to decode access plans” which could help thousands of budding DBA’s like myself.

    Once again thanks a lot for your time and effort in writing these blogs. I cant tell you how useful they are to me.

    Regards,
    Sandip.

  2. Kermit Lowry says:

    Crisp and clean, and only a little caffeine. Good Article.

  1. March 7, 2014

    […] Why won’t you just die?! (Cleaning DB2 Process in Memory) […]

  2. March 17, 2014

    […] … DB2 and HACMP failover Technical Conference – It’s a skill builder, not a trip to Vegas. Why won’t you just die?! (Cleaning DB2 Process in Memory) Attack of the Blob: Blobs in a Transaction Processing Environment Automatic Storage Tablespaces […]

  3. March 24, 2014

    […] … DB2 and HACMP failover Technical Conference – It’s a skill builder, not a trip to Vegas. Why won’t you just die?! (Cleaning DB2 Process in Memory) Attack of the Blob: Blobs in a Transaction Processing Environment Automatic Storage Tablespaces […]

  4. May 7, 2014

    […] … DB2 and HACMP failover Technical Conference – It’s a skill builder, not a trip to Vegas. Why won’t you just die?! (Cleaning DB2 Process in Memory) Attack of the Blob: Blobs in a Transaction Processing Environment Automatic Storage Tablespaces […]

  5. May 13, 2014

    […] 2. Shut down the database and instance cleanly, possibly using IPCLEAN. […]

Leave a Reply

Your email address will not be published. Required fields are marked *