from Hacker News

Details on the Oracle failure at JPMorgan Chase

by babar on 9/17/10, 6:57 PM with 24 comments

• by babar on 9/17/10, 7:00 PM

  Short on details, and I thought the speculation on transferring the user info to a NoSQL solution sounds naive, but interesting to get a peek into the internal operations at a large enterprise. I think I want to go validate some of our database backup right now.

• by known on 9/18/10, 1:24 PM

  caused by corruption in an Oracle database.

  Could happen to any database. Not just Oracle.

• by lvecsey on 9/18/10, 12:07 AM

  So do those 8 machines and the code on it represent the system before or after the Wamu merger, or something in between? I've heard many of these banks such as Citigroup have something like 13 different databases or systems, many of which duplicate functionality.

• by unohoo on 9/17/10, 10:05 PM

  having worked at an enterprise software company and working with several big clients (including banks), I find it surprising (and shocking to some extent) that JPMC didnt have a more efficient disaster recovery process in place.

  I am not saying they didnt have one, just that disaster recovery scenarios should factor into such outages. Hypothetical fire drills etc. are needed at such critical businesses like banks.

  My guess is that a bunch of people @ jpmc will most likely be losing their jobs over this.