Gee... David

This week I was asked to implement a new installation of WebSphere Portal V6. Specifically, I was asked to implement the current recommended soluition. Upon review I determined that this is V6.0.1.1. I was further directed to employ a remote DB2 database. For implementation of the recommended, tested, and supported configuration I learned that we would need to use DB2 V8.1 FixPak 14 with Interim Fix (APAR) IY93359 (for support of Type 4 JDBC drivers. (DB2 V9.1 FixPak 1 is an alternative but not available for the client in question.)

As luck would have it, the required Interim Fix is no longer available as a discrete download. Of course it is included in cumulative FixPak 15. This, however, is not a 'tested' implementation.

Woe upon woe to discover that there is an answer but I can't have the solution because "someone" decided that I didn't need it.

In case you are wondering, I went forward with FixPak 15 with the client's consent only because they are in extermis with a customer mandated deadline. Here's my tip: consultants need to maintain their own inventory of Interim Fixes and FixPaks as they apply to their repertoire of solutions since IBM has, in my case, on two occasions displayed a proclivity to pull the rug out from under me without warning.