Many thanks to Frank Fillmore for delivering the DB2 Advanced Enterprise Server Edition – aka AESE – presentation on Wednesday.  We had over 70 people join us for the presentation and appreciate the positive feedback.   The link to the presentation file is here; if you have any questions on AESE or the presentation content please feel free to contact me at kim.may@thefillmoregroup.com.

One final note:  Frank is tracking down answers to the questions posed in the Q&A at the end of the session.  Look for them here – soon!

Frank Fillmore will deliver a one hour presentation to explain the new DB2 for LUW Advanced Enterprise Server Edition (AESE) packaging – what’s included, how AESE differs from DB2 Enterprise Server Edition and most importantly, why anyone running DB2 for LUW should give AESE serious consideration.  

Date:  Thursday, November 18, 2010, Time:  12pm-1pm Eastern

With AESE, IBM is bundling Optim and InfoSphere tools that have been available as for-fee add-on features in the past.  Come learn how to upgrade DB2 and get: 

• DB2 Storage Optimization Feature
• DB2 Performance Optimization Feature
• Optim Performance Manager
• InfoSphere Federation Server
• InfoSphere Replication Server (Q Replication)
• Optim Development Studio
• DB2 Advanced Access Control Feature

To register, click here.  If you have a problem registering or have questions, email Blaire Crowley (blaire.crowley@thefillmoregroup.com).

The Fillmore Group received approval to add five new IBM courses to our schedule for 2010.  The new classes we will deliver in our Towson, Maryland classroom are listed below.  These classes will enable our team of expert DB2 consultants and instructors to continue to share their field experience with DBAs and to help increase DBA skills in the market.  Thanks IBM!

DX447,  Information Server Administration, starting January 11, 2010
CL461,  DB2 9 for LUW Advanced Database Administration for Experts, starting February 8, 2010
IM401,  IBM DB2 Content Manager V8 Implementation and Administration, starting April 12, 2010
CF242,  DB2 9 for LUW Multiple Partition DBA Workshop, starting April 19, 2010
CF413,  DB2 9 for Linux, UNIX, and Windows Performance Tuning and Monitoring Workshop, starting June 14, 2010

I can finally announce it – it’s finalized – Chris Eaton will be here September 9th for the Baltimore/Washington DB2 Users Group meeting.  For me, this is a big, big deal.  The turnout for the June meeting was disappointing and the board agrees that the LUW and z/OS track folks really need to be meeting together to encourage networking and all the social aspects of the users group.  So we are doing both tracks together September 9th in Columbia, with the hotel offering us an extra room and the attendees all getting a sit-down lunch – together, in one dining room. 

The LUW agenda is below.  Joining Chris presenting are *two* DB2 Gold Consultants – Frank Fillmore (on DB2 Connect) and Dave Beulke (on Java tuning and Data Studio).  Registration and the z/OS agenda are on the website at www.bwdb2ug.org.  If you are in town, please join us – this is like getting best of IOD in one day!

Read More…

The Data Studio team suggested a review of a new article on developerWorks, and it’s great!

Performance monitoring and tuning are critical tasks for a database administrator (DBA). DB2® Performance Expert helps DBAs tackle immediate performance problems, as well as avoid problems in the future. This article is the first of two in a series that describes the top 6 things you can do to get the most out of DB2 Performance Expert.

The top 6 tips for a successful DB2 Performance Expert deployment for DB2 for Linux, UNIX, and Windows, Part 1: Modifying settings, setting up alerts, and using System Health data views

http://www.ibm.com/developerworks/data/library/techarticle/dm-0904db2performanceexpert1/index.html

When the next article is published I will post the link. Please let me know if you find this helpful.

BETTER than an attachment on Cobra new features…here’s the link to the Early Access program site for Cobra.

The Early Access Program is designed to encourage DB2 users to check out DB2 new features in a sandbox environment. Sign up for the Early Access Program at:

http://www.ibm.com/software/data/db2/technology-sandbox/

Sorry I haven’t posted in a little while.  October was a 250 hour month with a critical customer project and the IBM Information OnDemand Conference (IOD – you know all about IOD from Kim).  My VP of Biz Dev is all about trying to make her “number”, so it’s been busy.

The Fillmore Group is an IBM Authorized Training Partner (ATP) so we use a product called Acronis to create a single image of our student lab machines and then deploy that image to multiple PCs.  Since these are Windows XP PCs running DB2 9 for Linux, Unix, Windows Fixpack (FP) 2, the computer name must be unique within the domain.  However, once you change the computer name, DB2 stops working.  The common error is SQL1042C.  Here’s how to fix that problem.

First, there is a file in each DB2 instance subdirectory (e.g. “c:\Program Files\IBM\SQLLIB\DB2”) called db2nodes.cfg; in this post we’re only going to address single-node (i.e. not Data Partitioning Feature or DPF) databases.  Open this file for each DB2 instance on the server – I use WordPad – and change the imbedded hostname to the current computer name for that PC.  The same hostname will be repeated twice on a single line in the db2nodes.cfg file.  Change both.  This used to be all you needed to do to fix the problem.  Now, there are a few more steps.

If you installed using the extended operating system security option, you likely will now receive an SQL1652N file I/O error.  In DB2 9.1 FP 2, support was added for domain userids and groups.  Use the db2extsec command to correct the authorities for the installation-defined groups DB2ADMNS and DB2USERS.  For example, let’s say the PC image was created using a computer name of TFGXP01.  We’ve deployed this image to another PC and changed the Windows computer name to TFGXP02.  Enter the command:

db2extsec -a TFGXP02\DB2ADMNS -u TFGXP02\DB2USERS

The last step involves correcting the DB2 registry variables.  Use the db2set -all command to examine the current registry variables.  In our example, you likely will have seen three variables with TFGXP01 as part of the value.  Issue the following commands:

db2set db2accountname=TFGXP02\db2admin

db2set db2instowner=TFGXP02

db2set db2system=TFGXP02

At this point, you should be able to start the DB2 instances.