Re: Oracle and Sun fingered for Sidekick fiasco

  • From: Daniel Fink <daniel.fink@xxxxxxxxxxxxxx>
  • To: 'Oracle Discussion List' <oracle-l@xxxxxxxxxxxxx>
  • Date: Mon, 19 Oct 2009 10:44:02 -0600

Personal opinion of article - Mere speculation based on LinkedIn, job adverts and theorizing (next to last paragraph includes "appear to be", "failure of some sort", "seems apparent though"). So far, Hitachi, Oracle and Sun have been 'accused' of being the source of the problem...not Microsoft or Danger. A perfect combination of blamestorming and terrible "journalism".


Professional opinion of article/event - Way too much speculation, but there are two issues that we all need to keep in mind... 1) Always test upgrades/changes in a production-mirror environment. I recall a processor upgrade that had to be rolled back because of an incompatibility with the underlying operating system. 2) Always have a plan to return to a known good state without data loss. This includes having a known good backup (the only way to know this is to have performed a successful recovery) and capturing any data as it flows to the new system so it can be applied to the restored backup in case it has to be rolled back.


Regards,
Daniel Fink

--
Daniel Fink

OptimalDBA    http://www.optimaldba.com
Oracle Blog   http://optimaldba.blogspot.com

Lost Data?    http://www.ora600.be/



Taylor, Chris David wrote:
"On this reading the Oracle RAC was fed garbage by the Sun servers corrupted during an update process, and this fouled up access to the data." I wonder if they were using OCFS/OCFS2 on those linux servers. Doing an OCFS upgrade several years ago, we lost all our drive information. The data was still on the SAN mind you, but for whatever reason we could no longer get to it. The host servers didn't see the partitions any longer after the upgrade to OCFS and we had to remount the partitions and reload from backup. It was a very strange experience to say the least. */Chris Taylor/*
*Sr. Oracle DBA*
Ingram Barge Company
Nashville, TN 37205
Office: 615-517-3355
Cell: 615-354-4799
Email: chris.taylor@xxxxxxxxxxxxxxx <mailto:chris.taylor@xxxxxxxxxxxxxxx>
*CONFIDENTIALITY NOTICE**: This e-mail and any attachments are confidential and may also be privileged. If you are not the named recipient, please notify the sender immediately and delete the contents of this message without disclosing the contents to anyone, using them for any purpose, or storing or copying the information on any medium.*

------------------------------------------------------------------------
*From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] *On Behalf Of *Johnson, George
*Sent:* Monday, October 19, 2009 11:17 AM
*To:* Oracle Discussion List
*Subject:* Oracle and Sun fingered for Sidekick fiasco

Would anyone care to hazard a guess as to what happened? Purely as an academic exercise, you understand. http://www.theregister.co.uk/2009/10/19/sidekick_rac/ I am actually genuinely curious as to what people might think happened. We are about to head into ASM/RAC territory and it would good to hear some worse case theories, based on the flimsy outline given in the story. * *

Please consider the environment before printing

**********************************************************************************************

This message contains confidential information and is intended only for the individual or entity named. If you are not the named addressee you should not disseminate, distribute or copy this email.

Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as an invitation or offer to buy or sell any securities or related financial instruments. GAM operates in many jurisdictions and is regulated or licensed in those jurisdictions as required.

To the extent this email has been sent to you by any GAM company domiciled in the EU, being GAM (U.K.) Limited, GAM Sterling Management Limited, GAM International Management Limited, GAM London Limited, GAM Fund Management Limited, or GAM Fonds Marketing GmbH i.L., please note the following details in respect of each such company: - GAM (U.K.) Limited (a company limited by shares and registered in England and Wales with company number 01664573); - GAM Sterling Management Limited (a company limited by shares and registered in England and Wales with company number 01750352); - GAM International Management Limited (a company limited by shares and registered in England and Wales with company number 01802911); - GAM London Limited (a company limited by shares and registered in England and Wales with company number with Company Number 00874802) Each of Registered Office: 12 St. James's Place, London, SW1A 1NX

GAM Sterling Management Limited, GAM International Management Limited and GAM London Limited are each authorised and regulated by the Financial Services Authority. GAM Fund Management Limited (a company limited by shares and registered in Ireland with no. 156828) of Registered Office: George's Court 54-62 Townsend Street Dublin 2, Ireland

GAM Fonds Marketing GmbH, i.L. (a company limited by shares and registered in Germany under No. HRB 66857) of Friedrichstrasse 154, D-10117 Berlin, Germany. The competent Commercial Register is "Amtsgericht Charlottenburg" in Berlin. Liquidator: Daniel Durrer.



Other related posts: