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).

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.

Help us Investigate

Please 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:

...

Calendar layout at bottom of email.

1. Cognos Sandbox = Now thru 5:00 PM, Friday, January 10:  ITS-BIA will review the upgrade in our sandbox prior to planning an upgrade of DEV.  The 12.0.4 upgrade has already been installed on our sandbox.

   1. BONUS: Monday, February January 6 thru 5:00 PM, Friday, February January 10: Cognos Developers will be allowed into the Cognos Sandbox for a preview

2. Cognos DEV = 5:00 PM on Friday, January 10: 

   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. Cognos DEV will be unavailable while this work occurs.

3. Cogno DEV = Post DEV upgrade Friday, January 10 thru 5:00 PM ThursdayFriday, January 24:

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

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

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

   4. NO MIGRATIONS OUT OF DEV can occur as the content from the upgraded environment will not work in environments on an earlier version.

4. Cognos DEV = Friday, August 18January 24

   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. Cognos QA = 5:00 PM on Friday, August 18January 24 (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.

   3. Cognos QA will not be available while this work occurs.

6. Cognos QA = Post QA upgrade Friday, August 18January 24 thru 5:00 PM ThursdayFriday, August 24January 31:

   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 the current version 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. Cognos QA = Friday, August 25January 31

   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. Cognos Prod = 5:00 PM on Friday, August 25January 31 (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.

   3. Cognos Prod will not be available while this work occurs.

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

Calendar

Sandbox Testing

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

...