RE: major blunders

From: Aragon, Gabriel (GE, Corporate, consultant) <"Aragon,>
Date: Wed, 7 Oct 2009 15:03:47 -0400
Message-ID: <>

Do not execute huge scripts at once, or without verifying content, most of all for scripts generated by tools like TOAD. A newbie DBA generated a script using TOAD and didn't uncheck "Drop table" option. Script was executed in production.  

From: [] On Behalf Of Toon Koppelaars Sent: Miércoles, 07 de Octubre de 2009 01:53 p.m. To:
Cc:;;; Subject: Re: major blunders

Absolutely right.

They should strike the term "backup strategy" all together from the documentation.

It's "recovery strategy" that's important. How to backup is a derivative from that.

On Wed, Oct 7, 2009 at 8:50 PM, <> wrote:

        Not testing recovery scenarios is also one of the major blunders.         

        Testing recovery is as important as taking regular backups.         


"Frits Hoogland" <>
Sent by:

Oct 07 2009 02:44 PM

Please respond to

"" <>
Re: major blunders

        in the line of not having a backup:         

        having the database backup done by another team than the DBA's, and doing it hot with putting tablespaces into backup mode, which is done by logging on to the database with the SYSTEM account. this on itself works, but fails if all database passwords needs to be changed, and the backup script isn't altered (of course there is a hardcoded password in it), because it isn't in control of the DBA team.         

        looks outdated, but still occuring:         

        outsourcing to india because of cost, and thinking it all "magically" goes well.         

        something all performance consultants will have encountered:         

        clients/programmers who believe: parallel improves performance, increasing parallelism improves performance even more, and increasing parallelism even more will improve performance once again. seen it been bumped up to 48 slaves for a single table with 4 CPU's and locally attached disks.                                                      

	On Wed, Oct 7, 2009 at 8:26 PM, ~Jeff~ < <> > wrote: 
	here's a couple of biggies that havent been mentioned yet: 
	- not having a backup   !!!! 
	- letting the newby DBA loose in production (see previous point!) 
	2009/10/8 April Sims < <> > 
	Compiling a list of major blunders to avoid:
	Don't use the number 8 for scripting or ORACLE_SID due to the wild card character * above it.
	Don't use rm *.*
	Anyone else have some to contribute?
	April Sims
	SELECT IOUG Contributing Editor <> 
	OCP 8i, 9i, 10g DBA
	Southern Utah University <> 
	-- <> 

Toon Koppelaars
RuleGen BV

(co)Author: "Applied Mathematics for Database Professionals"

Received on Wed Oct 07 2009 - 14:03:47 CDT

Original text of this message