Re: My woes continue, Bad DBAs

A slow-running and/or badly-tuned SQL is one thing, a corrupted database is another. There is only so much I can do without hacking into the SYS or SYSTEM accounts (and indeed I COULD do this -- I do know the passwords).

I want to thank everyone who replied to my cry for help -- I know I'm not going insane, but every once in a while, when everyone around me seems takes lunacy as normal, I start to question myself. Your votes of confidence helped me through a rough week.

I think my suggestion to management here that Oracle is SUPPOSED to be robust, and is SUPPOSED to handle many simultaneous queries and updates is starting to sink in. Our DBA isn't out the door yet, but people are finally starting to cop-on that maybe there is a better world out there -- a world where the database doesn't go down on a near-daily basis; a world where technical staff actually help the company find solutions.

Joost

>DanHW wrote:
>
>>
>> Perhaps you can look at enough things to tune the statement, and/or check
>> the DB. If that is checks out, look elsewhere (ie, the network, your PCs
>> 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
>
>--
>---------------------------------------------------------------
>John Caputo Lawrence Livermore
>Email: caputo1_at_llnl.gov National Laboratory
>Phone: (510) 422-5262 P.O.Box 808, L-650
>Mon-Thu 7:30 AM-5:30 PM - Off Fri Livermore, CA 94551
Received on Wed Jul 16 1997 - 00:00:00 CEST