Due to a security vulnerability in Progress DataDirect Autorest driver version 6.0.0.004291, Cognos Analytics 11.2.4 FP2 includes an upgraded Progress driver: version 6.0.1.005690. As such, UCSD will be applying Fix Pack 2 with an abbreviated upgrade process.

You can find information on what’s new in this upgrade here: https://www.ibm.com/docs/en/cognos-analytics/11.2.0?topic=features-release-1124-fp2-july-2023

Project Epic:

Cognos developer report testing at the beginning of the upgrade is critical to a timely and successful upgrade.

Applying a fix pack includes less risk than a release to a new version number.

Upgrade Process - Urgent Fix Pack Upgrade

Given that strategy, the plan for the upgrade from 11.2.4 (current) to 11.2.4 FP2 is as follows:

Calendar layout at bottom of email.

1. Now thru 4:00 PM, Wednesday, November 8:  ITS-BIA will review the upgrade in our sandbox prior to planning an upgrade of DEV.  The 11.2.4 upgrade has already been installed on our sandbox.

2. 4:00 PM on Wednesday, November 8: 

   1. A backup of the DEV content store will be conducted.  This will be insurance against any unforeseen issue during the upgrade process.

   2. The admin team will perform the upgrade of the DEV environment.

3. Post DEV upgrade Wednesday, November 8 thru 4:00 PM Thursday, November 16:

   1. All development teams to review content in Cognos DEV and test for issues related to the upgrade.

   2. Any issues are to be reported by sending an email to busintel@ucsd.edu

   3. If an issue is deemed critical, a rollback of DEV to 11.2.4 will be scheduled as soon as possible.

   4. NO MIGRATIONS TO QA/PROD can occur as the content from the upgraded environment will not work in environments on an earlier version.

4. Thursday, November 16

   1. GO/ROLLBACK determination for QA upgrade will be made.

   2. GO – the upgrade is applied to QA only over the weekend following the DEV upgrade. 

      1. This will be the determination if no new issue(s) are found in the upgraded version or if any new issue noted is deemed insignificant enough to move forward.

   3. ROLLBACK – the upgrade is rolled back from DEV

      1. This will be the determination only if new issues are found in the upgraded version and those issues are deemed significant.

5. 4:00 PM on Thursday, November 16 (based on GO determination in previous step):

   1. A backup of the QA content store will be conducted.  This will be insurance against any unforeseen issue during the upgrade process.

   2. The admin team will perform the upgrade of the QA environment.

6. Post QA upgrade Thursday, November 16 thru 4:00 PM Monday, November 20:

   1. All development teams to review content in Cognos QA and work with end users to test for issues related to the upgrade.

   2. Any issues are to be reported by sending an email to busintel@ucsd.edu

   3. If an issue is deemed critical, a rollback of QA and DEV to 11.1.7 will be scheduled as soon as possible.

   4. NO MIGRATIONS TO PROD can occur as the content from the upgraded environment will not work in environments on an earlier version.  Content may be migrated from DEV to QA.

7. Monday, November 20

   1. GO/ROLLBACK determination for PROD upgrade will be made.

   2. GO – the upgrade is applied to PROD over the weekend following the QA upgrade. 

      1. This will be the determination if no new issue(s) are found in the upgraded version or if any new issue noted is deemed insignificant enough to move forward.

   3. ROLLBACK – the upgrade is rolled back from DEV and QA. 

      1. This will be the determination only if new issues are found in the upgraded version and those issues are deemed significant.

8. 4:00 PM on Monday, November 20 (based on GO determination in previous step):

   1. A backup of the PROD content store will be conducted.  This will be insurance against any unforeseen issue during the upgrade process.

   2. The admin team will perform the upgrade of the PROD environment.

Please take note of the 12 day period from Wednesday, November 8 through Monday, November 20 where content may not be migrated to PROD.  Please be sure all required content is migrated from DEV to PROD prior to the DEV upgrade at 4:00 PM on Wednesday, November 8.  Please be sure all required content is migrated from QA to PROD prior to the QA upgrade at 4:00 PM on Thursday, November 16.

Calendar