I did that, knowing I was working with Production database. Exported the db,
dropped all prod schema objects to reorg. Forgot about the crontab jobs.
Which started, while I was editing scripts to re-build objects. The job
overwrote my export file. (I used the same cron job script to generate my
export file, so the name & path was the same).
Fortunately there was another full export from previous day that the client
had taken. Restored that one, but one full day of work as lost. Client had
to re-key all the data from original source and memory. There were no hot
backups and I was learning Oracle 6.0.13. Came pretty close to 'updating my
resume'.
Learned my lesson the very hard way. Since then no more oops...
Now I use a very detailed check list, even for small things! Test or
Production !!!
- Kirti
> -----Original Message-----
> From: Steve Boyd [SMTP:pimaco_oracle_at_hotmail.com]
> Sent: Thursday, May 25, 2000 10:39 AM
> To: Multiple recipients of list ORACLE-L
> Subject: Re: Re[2]: Big Whoops
>
> 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_at_vicr.com
> >Reply-To: ORACLE-L_at_fatcity.com
> >To: Multiple recipients of list ORACLE-L <ORACLE-L_at_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_at_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_at_gelco.com
> > >Reply-To: ORACLE-L_at_fatcity.com
> > >To: Multiple recipients of list ORACLE-L <ORACLE-L_at_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
Received on Thu May 25 2000 - 12:07:09 CDT
