| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: how to crash a db ?
After taking the Oracle Backup & Recovery class (8.0), our ERP vendor's DBA
did some random "crashes" on a test DB. Not all of them brought the
instance down. After each trial, he would send me e-mail with some symptoms
as though a user had called with a real problem and I had to solve it.
I liked this method of backup/recovery test because it was much more true to life. It could have been a TRUNCATE on an application table or an accidentally deleted datafile or some other Stupid Human Trick (tm Worldwide Pants) like copying one datafile on top of another from the Unix shell. That was a tough one to determine what happened!
Don't worry about failing to recognize what the problem is right away! Going through this in a test environment a few times gets you used to a method of investigation (checking DBA/V$ views, checking log/trace files, etc.) as well as points out some possible areas to improve your setup. For example, if we hadn't audited all TRUNCATE statements, we would not have been able to accurately recover a production table because we wouldn't have known the exact time this table had been accidentally TRUNCATEd. Not that auditing all TRUNCATEs is applicable to every installation; it's just one example.
Pager just went off again <sigh>....Have fun testing! :)
Rich
Rich Jesse System/Database Administrator rich.jesse_at_qtiworld.com QTI, Sussex, WI USA
-----Original Message-----
Sent: Friday, February 21, 2003 5:54 PM
To: Multiple recipients of list ORACLE-L
Try this. Turn your server off, pull the drives, remove the outer plates from the individual drive enclosures, and scratch the platters with a nail.
That should do it.
Or, you could just shutdown your database, rename the system tablespace file and try to restart, and subsequently recover.
Using dbed to 'modify' the system tablespace comes to mind, but that's for the real byteheads.
How about 'delete from sys.fet$; commit;' . That should bring in down in a few minutes.
If you want a faster reaction, try 'delete from sys.tab$; commit;'.
That will have a more immediate effect.
Any of these should be sufficient to require recovery.
;)
Jared
<netmadcap_at_netzero.com>
Sent by: root_at_fatcity.com
02/21/2003 03:23 PM
Please respond to ORACLE-L
To: Multiple recipients of list ORACLE-L <ORACLE-L_at_fatcity.com>
cc:
Subject: how to crash a db ?
Hi Listers ...
sorry, no bad intentions or anything like that :) but i want to learn some recovery options. atleast, the basic point-in-time etc.
so how can i try to crash a db ? r there any other ways to learn this
w/out
crashing the db ?
wishing y'all a happy wknd !
thanks,
-sam
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: Jesse, Rich
INET: Rich.Jesse_at_qtiworld.com
Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting servicesto: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). Received on Sat Feb 22 2003 - 06:39:07 CST
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
 |
 |