Re: My woes continue, Bad DBAs

kasperle_at_cs.tu-berlin.de wrote:
>
> Joost Ouwerkerk wrote:
> >
> > To all DBA's:
> > My DBA is making my job rather difficult, but I'm having trouble
> > exposing some of his incompetencies to my superiors... Should any of
> > the following statements be true for a well-tuned Oracle 7.3.2
> > database server running on an IBM AIX and serving an organization of
> > 50 users, about 15 of whom are data entry staff, and about 10 of whom
> > run regular queries and reports:

> > 1) A complex query can 'crash' the database and cause corruption of
> > data.

Once a developer of mine was able to crash an Oracle DB (inadvertently) via a simple PL/SQL loop. The fact that it crashed had to do with the fact it was an Oracle NLM on Novell. Basically, there was a loop followed by a if-statement that was never true, and the end-loop. In the NLM, no other processes would ever run because no resources were ever needed. Eventually, the Oracle processes died from no servicing, and if we let it go long enough (which we did), eventually the server would die. This is admittedly a very wierd situation, but there are real oddities out there sometimes

In addition, I have seen strange things happen because of network issues; Oracle and my PC see to get confused and EVERYTHING goes R-E-A-L slow, even though the DB is fine according to all the normal performance monitoring. I have been waging a similar battle with the network administrator.

The only time I can ever remember data corruption was due to hardware failure; I have never seen an instance where a user (and especially a QUERY) corrupted data.

> > My suspicion is that if any of these are true, there is a server
> > tuning problem. My DBA is suggesting no queries be run while data
> > entry is occuring (during business hours) and is threatening to remove
> > Personal Oracle and Dev/2000 from my computer because of the damage
> > I'm supposedly causing. Am I going crazy?
>

[Quoted] [Quoted] Perhaps you can look at enough things to tune the statement, and/or check [Quoted] the DB. If that is checks out, look elsewhere (ie, the network, your PCs [Quoted] network card). Do what you can to isolate it, and as Kathrin said

" So don't fight the DBA, try to fix it yourself.."

Good luck
Dan Hekimian-Williams Received on Wed Jul 16 1997 - 00:00:00 CEST