Fixpack

1. Russia Madden will submit standard change request for Prod update - see #3: CHG0040340

2. today Saparnell will notify report developers

3. apply to DEV (4hours) 4pm start Tuesday 11/7

4. apply to QA (3hours) 4pm start Monday 11/13

5. apply to Prod (4.5hours) 4pm start Wednesday 11/15 (change request from Russia w/ task for AP
   

Cognos Changes Affecting UCSD

Cognos alternates casting null date fields as integers and varchar. The report developer can tell Cognos to set this field null values to a null date by using cast (NULL, date).

Two Issues Resolved

Thank you to all who have provided us with feedback on unexpected behavior in Cognos DEV.  Please continue to let us know if you are experiencing anything unexpected.

DUO Push From Scheduled Reports

We have found an issue related to multiple DUO pushes occurring from Schedule Reports. When the scheduled report begins running a DUO push is initiated and the scheduled run will not continue until the DUO push is acknowledged.  This is a major concern and requires resolution prior to moving forward with the upgrade.  

DUO Push During Navigation

We have found an issue related to multiple DUO pushes occurring when users are navigating between the My Content are and Team Content area. 

We are currently researching the cause and resolution of these issues with the goal of continuing our Cognos upgrade on schedule.

Help us Investigate

Please continue to email busintel@ucsd.edu when you encounter something unexpected.  If you can provide the additional information seen below in your initial email that will help use investigate:

...

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

High Level Plan

We will follow our standard upgrade procedures listed below. 

...

1. ITS-BIA will review the upgrade in our sandbox prior to planning an upgrade of DEV

2. Perform upgrades of the DEV environment on the weekend before the 3rd week of a month as this is generally the quietest period of the month for most teams.

3. Allow two weeks for review of the upgrade in the DEV environment.

   1. At the end of the week a GO/ROLLBACK determination will be made.

   2. GO – the upgrade is applied to QA over the weekend following the DEV upgrade. (Upgrade is NOT applied to PROD.)

   3. ROLLBACK – the upgrade is rolled back from DEV

   4. During the two week period where DEV has been upgraded and QA / PROD have not, all teams will be in a “code freeze” in that no migrations from DEV can occur.

4. Allow one week for review of the upgrade in the QA environment.

   1. At the end of the week a GO/ROLLBACK determination will be made.

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

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

   4. During the one week period where DEV and QA have been upgraded and PROD has not, all teams will be in a “code freeze” in that no migrations to PROD can occur. Migrations from DEV to QA may be conducted.

5. Upgrade the PROD environment.

   1. Based on GO determination from both Cognos QA and Cognos DEV environments based directly on your feedback.

...

Upgrade Process

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

...

Please take note of the 3 week period from Friday, August 4 through Friday, August 25 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 5:00 PM on Friday, August 4.  Please be sure all required content is migrated from QA to PROD prior to the QA upgrade at 5:00 PM on Friday, August 25.

Calendar

Sandbox Testing

Currently, only the Cognos provided packages are available to test against.

...