Cascade’s batch processing system went down unexpectedly at 11:15 am. We are working to restore this service.
Batch processing service was restored at 11:51 am.
Author Archives: kspiese
January 11, 2009: Cascade Web unavailable (back online at 12:15 pm)
Cascade Web is experiencing some unexpected complications related to yesterday’s Cascade database upgrade. Technology Services staff are working to resolve the issue as quickly as possible.
Cascade Web was brought back up around 12:15 pm.
Databases unavailable, 1/10/2009
Campus email text:
Saturday, January 10, Technology Services will be performing important updates on our database systems. There will be two groups of outages:
5 AM until 8 PM – Cascade and Cascade Web will be unavailable.
9 AM until Noon – Banner, Famis, Basis, and Millennium will be unavailable.
Email, network files and shares, and other network services will not be impacted.
Details:
Cascade database is switching to new hardware and upgrading to 10g. Administrative toolset is being upgraded to 10g and deployed on new hardware.
Banner, Famis, Basis, and Millennium will be patched to make them compatible with 10g.
November 24, 2008: CRM downtime, 6 am – 8 pm
CRM will be down from 6 am – 8 pm on Monday, November 24. The database instance will be patched then moved from Rainier to Grace.
Cascade Batch Processing outage 11/19
Cascade Batch Processing system was down for approximate 30 minutes, from 3:00 pm to 3:30 pm.
CRM application tier bounced at 10:20 am on 10/1/2008
CRM fulfillment experienced an error during the processing of an email (rollback segment problem). Restarting the email caused a runaway cpu-intensive session even though the email was subsequently cancelled.
Cause of runaway session: user created content using the wrong content type (admission content type instead of campus email), which relied on admission data being in the system.
Resolution: We bounced the application server and killed the runaway session. User recreated email with correct content type.
CRM unavailable – 4/25/2008
CRM was temporarily unavailable for for about 40 minutes.