Message-Id: <10508.106738@fatcity.com>
From: Kent Wayson <waysonkw@mail.milwaukee.k12.wi.us>
Date: Thu, 25 May 2000 12:29:51 -0500
Subject: Re: Re[2]: Big Whoops

You expect us to admit this in public?  <g>

O.K. - I deleted a datafile (Unix rm command), but the vendor software was
so un-stable at the time that I just let everyone assume it was a software
problem and not a human error problem.  Now that the software is (more)
stable, so am I.  I hope.


Kent



>I'd like to post a question for everyone on the list.
>
>How many of you have ever dropped a table, or done something like that in 
>the wrong database(thinking you were connected to say the test DB), and 
>hosed production?
>
>Steve Boyd
>
>>From: dgoulet@vicr.com
>>Reply-To: ORACLE-L@fatcity.com
>>To: Multiple recipients of list ORACLE-L <ORACLE-L@fatcity.com>
>>Subject: Re[2]: Big Whoops
>>Date: Thu, 25 May 2000 06:40:46 -0800
>>
>>A couple of years ago I was trying to create a new instance on one of our 
>>Unix
>>boxes to support an additional manufacturing line.  Since the first 
>>instance was
>>well tuned, I copied the init.ora file to a new name & did the little 
>>editing
>>that I believed necessary, like a new db_name.  What I forgot was the
>>control_file line.  You can guess what happen next, yes the control files 
>>got
>>trashed and the original instance terminated with errors.  We had to 
>>recover
>>that one from tape since I hadn't backed up the control files to trace for 
>>some
>>time, but I do now at every shutdown.  We live & learn from our mistakes,
>>hopefully NOT on a production server.
>>
>>
>>BTW: My advice to any new DBA out there is that when an emergency hits you, 
>>or
>>an AW SH%$.  First step in the process is to step back, take a deep breath 
>>&
>>calm down.  Adrenaline and instant reaction are your worst enemies.
>>
>>Dick Goulet
>>Senior Oracle DBA
>>Vicor Corporation
>>
>>____________________Reply Separator____________________
>>Author: "Rachel Carmichael" <carmichr@hotmail.com>
>>Date:       5/24/00 6:16 PM
>>
>>Lisa,
>>
>>You have backups? Restore from backup. Otherwise..... recreate and import 
>>is
>>the way to go.
>>
>>I gotta say, the fact that you did this, figured out how to fix it, and
>>didn't freak out about it, would impress me MUCH more on an interview than
>>the fact that you have your OCP :)
>>
>>Rachel
>>
>>
>> >From: Lisa_Koivu@gelco.com
>> >Reply-To: ORACLE-L@fatcity.com
>> >To: Multiple recipients of list ORACLE-L <ORACLE-L@fatcity.com>
>> >Subject: Big Whoops
>> >Date: Wed, 24 May 2000 14:44:29 -0800
>> >
>> >This is by far the funniest thing I have ever done.  I began running the
>> >create
>> >database scripts (ON A TEST MACHINE) when the $ORACLE_SID was set to a
>> >currently
>> >running database.  It's now completely and totally hosed.  I'm just
>> >wondering if
>> >there is any possible way of recovering from this.  I am just recreating
>> >the
>> >database and reimporting the data - it's not a big deal, but for future
>> >reference, I wonder if this really does mean THE END OF THE DATABASE AS 
>>WE
>> >KNOW
>> >IT.  My gut feel is YES.
>> >
>> >I just can't stop laughing.  I finish my OCP exams and completely TRASH a
>> >large
>> >database in the same day (and dump pink ice cream on my white sweater
>> >simultaneously)!  Like Kirti said, Who *WANTS* to be a DBA?  Are you out 