| 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: Griping about auditing (not the Oracle Kind)
I
suggest CYA as much as possible and escalate the issue and begin search
for another job. Also if you are an FTE - now is a good time to go on
vacation or become sick. Because if something breaks damagement knows much
better how to avoid responsibility than we (at least most of us) are. For
example it can be said that you did not explained an issue well enough etc. And
you will show your e-mail to the damager of the damager who knows even less
about Oracle.
<FONT face=Arial color=#0000ff
size=2>
Alex
Hillman (incredibly rude and cinical)
<FONT face=Arial color=#0000ff
size=2>
<FONT face=Tahoma
size=2>-----Original Message-----From: Bowes, Chris
[mailto:Chris.Bowes_at_kosa.com]Sent: Monday, June 25, 2001 5:06
PMTo: Multiple recipients of list ORACLE-LSubject: RE:
Griping about auditing (not the Oracle Kind)
In a perfect world or even a sucky world, yes. But the
nightmare scenerio that was laid out wouldn't allow proactivity on their part.
The inconvenient time thing was due to the fact that the proactive items they
wanted to to do were rejected. They had a table that was diagnosed with
too small extents and they wanted a bigger extent size. They submitted
paperwork and a non-tech management type said 'no'. Does he disobey the
rules and risk getting fired? They made other requests for day-to-day
events and possible problems. They were rejected because "you cannot do
that many changes". Do they risk their jobs and do what is needed,
knowing eventually someone *WILL* find out and at that point they can/will be
terminated for insubordination and failure to follow process or at least
slapped down big for it?
In all situations I had seen until here, I would say, yes,
proactivity is a must and I know that we can look at any one item and get
around rules that get our way. When it becomes a corporate culture, you
really need to get the policy eliminated. The way to do that is to allow
the people who can make these stupid decisions suffer. He simply said
"OK, if that's the way you want to play it, then I'll do what you say. I
will follow your rules and not fix things I see wrong because *you say I
can't*. Of course, you wouldn't know a database problem if it jumped up
and bit you and said, 'Hi I am a database problem', but that's
irrelevant. I will do it your way and fix it when it breaks and
you're franticly signing off on the same paperwork you rejected x days/months
ago. Just don't expect a friendly call at 2 am when it
happens..."
I agree, we need to be proactive,
however, the way I read this issue, they were proactive and lots of times when
they made suggestions, they were rejected and their proactivity was rendered
moot by people who have no clue. When that happens, it is wise to make
them feel some pain for the decisions they make.
--Chris Chris.Bowes_at_Kosa.com
-----Original Message----- From:
Jared.Still_at_radisys.com [<A
href="mailto:Jared.Still_at_radisys.com">mailto:Jared.Still_at_radisys.com]
Sent: Monday, June 25, 2001 4:01 PM <FONT
size=2>To: Multiple recipients of list ORACLE-L <FONT
size=2>Subject: RE: Griping about auditing (not the Oracle Kind)
Kimberly,
We're on the same wavelength, as I was thinking the same
thing.
Procrastinating on something that you know needs to be
done is not an ethical way of dealing with this,
IMO.
Jared
<FONT
size=2>
size=2>
Smith
size=2>
size=2> jitsu.com> cc:
size=2>
by: Subject: RE: Griping about auditing (not the OracleKind) <FONT
size=2> root_at_fatcity.com
size=2>
size=2>
size=2>
AM
size=2>
to
size=2> ORACLE-L
size=2>
size=2>
I say that if you wait until you database has an error you
really aren't proving much except that you are not
proactive in your job. Which, in my book, makes you
not a very good DBA. Dealing with a dumb process
is one thing (we have our fair share on this account) <FONT
size=2>but I take to much pride in my work to let things fail because I
need to fill in a piece of paper.
-----Original Message----- Sent:
Monday, June 25, 2001 9:43 AM To: Multiple recipients
of list ORACLE-L
Wahey !!! The answer I was going to provide. We started
calling the manager up quite frequently at home to
authorise changes - he eventually saw sense. Not quite
as bad as 2am in the morning but inconvenient enough for him to
put a stop to it.
Best of Luck.
-----Original Message----- Sent: 25
June 2001 17:07 To: Multiple recipients of list
ORACLE-L
Jay; I have had to go thru the
same thing a couple times on a previous job <FONT
size=2>with Auditors. Every time those kind of
restrictions were placed on us it brought things to a
snails pace or, in some conditions, a complete halt. <FONT
size=2>Sooner or later they realized that it was unreasonable and lifted
them. But it was a pain until
they did it.
It took them a while to realize that we HAD to work the way we
did in order to keep things running smoothly.
I personally think that you should wait with resizing any of
your production data files
until you get oracle errors saying that things can not extend.
At that time, call up the Sr. VP at 2 am in the morning and
tell him that you have a crisis but you can not
proceed until you get his permission because of the
restrictions placed on you by the Auditors. Repeat this
process as many times as neccessary for them to lift the
restrictions.
Kevin
-----Original Message----- Sent:
Monday, June 25, 2001 9:32 AM To: Multiple recipients
of list ORACLE-L
We've been through an internal audit and I was just wondering
if anyone else has to deal
with the rather ludicrous requirements I now have. In order to
add or resize a datafile I now need to fill out a form and
get Senior VP approval and the alert logs must be
reviewed every day by a non-DBA in order
to be certain that I didn't make any database changes without
such approval. The auditors
were horrified to discover that not only did I do such things <FONT
size=2>whenever I thought them necessary but that we didn't have a non-DBA
review everything I did after an Oracle upgrade to
ensure I didn't install any other software.
Fortunately I managed to convince them that yes, I really did
need a Unix login (they were skeptical).
So, any similar horror stories?
Jay Miller Sr. Oracle DBA
The information contained in this communication is
confidential, is intended only for the use of the
recipient named above, and may be legally privileged.
If the reader of this message is not the intended
recipient, you are hereby notified that any
dissemination, distribution or copying of this
communication is strictly prohibited. If you have
received this communication in error, please re-send
this communication to the sender and delete the <FONT
size=2>original message or any copy of it from your computer <FONT
size=2>system. -- Please see
the official ORACLE-L FAQ: <A target=_blank
href="http://www.orafaq.com">http://www.orafaq.com <FONT
size=2>-- Author: Robertson Lee - lerobe
INET: lerobe_at_acxiom.co.uk
Fat City Network Services -- (858)
538-5051 FAX: (858) 538-5051 San Diego,
California -- Public Internet access
/ Mailing Lists <FONT
size=2>--------------------------------------------------------------------To REMOVE yourself from this mailing list, send an E-Mail message to: 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).
 |
 |