Fix Packs are an important part of your maintenance strategy of your Analytics Platform solution and are available to all supported customers.
While we make best efforts to release Fix Packs according to the originally posted date, this schedule is subject to change.
|Product||Target Release Date|
|Cognos Business Intelligence 10.2.1.13 (10.2.1 FP13)||Released August 9, 2017|
|Cognos Mobile Client Update - iOS 18.104.22.168.0||Released August 30, 2017|
|Cognos Mobile Blackberry Dynamics Update - iOS 22.214.171.124.0||Released September 5, 2017|
|Cognos Business Intelligence 10.2.2.9 (10.2.2 FP9)||Released October 2, 2017|
|Cognos Mobile 126.96.36.199.1||October - December 2017|
|Cognos Mobile Blackberry Dynamics 188.8.131.52.3||October - December 2017|
|Cognos Mobile Client Update - iOS 184.108.40.206.0||October - December 2017|
|Cognos Mobile Blackberry Dynamics Update - iOS 220.127.116.11.0||October - December 2017|
|Cognos Mobile Client Update - Android 18.104.22.168.0||October - December 2017|
|Cognos Business Intelligence 10.2.2 FP10||January - March 2018|
What is a Fix Pack?
A Fix Pack is a product update that contains a cumulative collection of code fixes that have been made since the last release of the product. These code fixes may be a result of several interim fixes as well as other code fixes identified to be important to our customers. Unlike individual interim fixes, a Fix Pack will undergo a regression testing cycle to validate the quality and integrity of the combined set of fixes. It is important to note that interim fixes are not made available to all customers because they receive limited testing focused on the original problem that was reported. As a result, there are clear benefits for you to take advantage of a Fix Pack as a means to maintain your solution.
How reliable a guide is the Target Release Date?
While we make every effort to deliver Fix Packs according to the target schedule, this is subject to change.
In particular, regression testing of a Fix Pack may uncover undesirable side effects, such as a performance degradation or significant increase in memory and/or CPU resource usage. When such issues are discovered late in the release cycle we have no alternative but to reschedule the release, so that those issues can be addressed to ensure we deliver a quality Fix Pack expected by our customers.
We will update this page as soon as changes to the schedule become known.
What Do I Need To Know Before Installing a Fix Pack?
Administrators need to take into account several things when deciding to install a Fix Pack:
Review the Fix List for each Fix Pack (see link above).
Fix packs within a release are always cumulative; for example, 10.2.1 FP4 includes all the fixes from 10.2.1 FP3 and earlier 10.2.1 fix packs. Fix Packs are language independent.
Due to timing, you may have received an interim fix that was not included in the latest Fix Pack before it entered regression testing. Please verify that all of the interim fixes that you are dependent on are included in a Fix Pack before installing it.
How do I obtain a Fix Pack?
Fix packs are available through Fix Central at http://www.ibm.com/support/fixcentral.
We strongly recommend that you plan to upgrade to the latest available Fix Pack as preventative maintenance to help you safely avoid known problems. Above is the target release schedule for upcoming Fix Packs to help you prepare and plan for your upgrade. Please check this schedule on a regular basis as we will update it with new planned Fix Packs on an ongoing basis.
What is a "Hot Fix" or "Interim Fix" and how do I get it?
"Hot Fixes" are also know as "Interim Fixes" and are designed to be given to specific customers only. Each customer is individually entitled to the hot fix because the fix has not been integrated into a fix pack, (not regression tested), and, therefore, it is not generally available. A hot fix will be put into the next scheduled fix pack.
If there is a "security" hot fix that needs to be generally available, then it is published as "generally available" in Fix Central.