I’ve written about this before, but I keep seeing big benefits from using it so I wanted to mention it again. Prior to DB2 9.7 FP3A there wasn’t an easy way to identify unused indexes. It could be done using a couple of different techniques but since FP3A a lastused column was added to syscat.indexes indicating the last time an index was used. I routinely use this to identify unused indexes and clean them up, resulting in less space used and faster table and index reorgs. So if you haven’t been checking this, it makes sense to start now. Stay tuned!
In a key finding, nearly half of respondents said a lack of partnership between operational units and the IT department was a top roadblock to getting new applications to market. Hmm…seems like I have heard this story before……..https://hbr.org/resources/pdfs/comm/oracle/19018_HBR_Oracle%20Report_rethinking_the_it_business_partnership_to_drive_digital_innovation.pdf
I’m doing a presentation on HADR and TSAMP at IDUG NA 2015 and have many clients running HADR. Over the various releases of DB2 HADR manageability, monitoring, and performance have been significantly improved. With new monitoring elements and log relay delay, along with log spooling, HADR runs like a smoothe running machine, with very few problems and near zero downtime. I recently came across the updated DB2 HADR Performance Wiki updated by lab guru Yuke Zhuge. Make sure you read this before you begin your HADR journey, you’ll be glad you did. Stay tuned!
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/DB2HADR/page/HADR%20perf
Waiting to try out BLU Acceleration on commodity hardware using non-RDMA capable NICs? You can do that in DB2 10.5 fixpak 5 in DB2 WSE….Get it here: http://www-01.ibm.com/support/docview.wss?uid=swg24038828 and read about it at the IBM BLU HUB, http://www.ibmbluhub.com/get-technical/blu-whatsnew-cancun/#Windows
I have received quite a few inquires lately from folks wanting to learn how to utilize the DB2 HADR multiple Standby and log delay feature introduced in DB2 LUW 10.1. Here is a link to a great whitepaper from my friends in the IBM DB2 Toronto Lab. http://public.dhe.ibm.com/software/dw/data/dm-1206hadrmultiplestandby/HADR_Multiple_Standbys_jn20.pdf
This was recently announced and I posted about this the other day. Kelly Schlamb from the Toronto has a good blog write-up about this. I’m very excited about what this offering can bring to my customers. Read about it here: http://ibmdatamanagement.co/tag/purescale/
and remember, stay tuned!
dashDB is a fully managed data warehousing and analytics as a service offering on the cloud. dashDB lets you set up a data warehouse in minutes. It takes the data warehouse infrastructure out of your way so you can focus on the business. Signup for this Jan 29, 215 deep dive here: http://bit.ly/tt2015jan
IBM announced yesterday a new batch of offerings for DB2 LUW at FP5. Get all the details here: http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=AN&subtype=CA&htmlfid=897/ENUS215-028&appname=USN. And remember, stay tuned!
I’ve mentioned this before so what are you waiting for? 🙂 Not kidding, a lot of folks running WSE aren’t aware of this. Also, range partitioned tables are included, yes I said included in WSE in DB2 10.5. This is a BIG feature that you can now use in WSE at DB2 10.5. Get moving and stay tuned!
Many times I get calls that something is sucking up the server and clients need to know what’s up. A very simple way nowadays is to use the MONREPORT reporting module first provided in DB2 9.7. It should be the first tool in your toolbag. Simply connect to the database where the reported problem is, and from a command line issue the following command:
“db2 call monreport.currentsql > csql.txt”
Examine the contents of the output file and if a query is actually executing it will be captured here. You can run subsequent calls to the module and don’t redirect the output to a file until you “catch” one executing. If you don’t catch one executing after repeatedly calling the monreport.currentsql stored procedure there is nothing running of interest or whatever is running is running sub-second. It is then doubtful SQL is your problem. Believe me, if it is, you will catch the SQL using this technique, guaranteed. There are other ways but this is easiest. Stay Tuned!
Gunning Technology Solutions, LLC. THE WORLD LEADER IN Db2 LUW CONSULTING! 