Had I been working in Operations and on-call at an organisation using Java Cloud Service then it appeared I may well have been rudely woken up last night! At around 2am in the UK this email innocently dropped into my mail box:
This warning of an impending outage to Java Cloud Service was closely followed by one for Database Cloud Service. Judging by the email – “during the maintenance your services will be unavailable” – it seems an hour and a half later the instance failure notifications (from Enterprise Manager or Nagios etc) would have probably started coming in.
Then at 4:36am I had an email to say my JCS was now available again, and 5:11am to say my DBCS was too so, a total outage according to the emails of just under 2 hours. However when it happened all of my Java and Database test instances (test) were down already but as far as I can tell no changes were actually made to them (they were not started up for example) – be sure to read my conclusions at the end of this post!
So this evening I’ve been having a good look round. The most obvious first change is that you can provision new domains with WebLogic 220.127.116.11.4, and existing full JCS ones (i.e. the ones including ‘cloud tooling’ for patching) have the following patches available: Read the complete article here.
For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.