Installed CpuApr2008 CRM Patch (db, apps) to Crmtst and Crm11id instance. Upgraded CRM’s Oracle Jinitiator from 13121 to 13129.
CRM was temporarily unavailable for for about 40 minutes.
Updated CRM database global parameter to allow for better performance monitoring.
Email sent to liaisons:
Thursday April 17, Information Services will be performing critical changes on our database systems to improve recent performance concerns.
Access to all database systems including Cascade, Cascade Web, Banner, Famis, Basis and Millennium will be unavailable from 5:30 AM until 6 AM Thursday.
If you have questions or concerns regarding this outage, please contact Jenifer Brauen by telephone at ext. 2725, 253.879.2725, or via email at firstname.lastname@example.org. Thank you for understanding our need to conduct critical systems work.
– Jenifer Brauen
4337683, 4741460, 4652461, 5097966
Camano failed due to process and memory overload caused by a failure to properly process bounceback messages from CRM.
Crital Patch cpuJan07
upgraded 220.127.116.11 db to 18.104.22.168 db
Applied Oracle CPUJuly2007 & 5671676 Patches to 22.214.171.124 Database and its Instances ( Ridge, Summit, Ban9id, Ban9it, Crm11id, Fam9id, Fam9it, Mildemo, Rcat, Tools9i) on Crystal server.
Applied Oracle CPUJuly2007 & 5671676 Patches to 126.96.36.199 Database and its Instances ( Cascade, Banner, Basis9i, Crm11ip, Famis9i, Mil9ip, Prcat) on Rainier and Whidbey servers.
Cascade Web came down 3/26 at 4:40pm following a restart of the Apache server to restore the use of Banner and Famis to the camano server which had been running on a backup server since Friday. Cascade Web was unable to start following this reboot and remained down until 10:30pm.
Other components of the Application Server including Discoverer and Portal remain down as of 8:15am on 3/27.
Cascade Web, Cascade, Banner, Famis and Millenium will be unavailable
Saturday, January 27th, from 9 a.m. through 5 p.m., for a planned upgrade.
CRM experienced periodic outages the morning of January 19 through 1:30 pm. Information Services was notified of the problem at approximately 11:00 am and began troubleshooting. The cause was identified at 12:15 pm and a resolution implemented by approximately 1:15 pm. The system was fully functional by 2:00 pm.
The cause of the failure was due to uncompiled objects in the database, but the root issue that caused the objects to become invalid is unknown.