RE: Pre-Approved database changes
- From: Jared.Still@xxxxxxxxxxx
- To: oracle-l@xxxxxxxxxxxxx
- Date: Fri, 18 Jun 2004 10:35:13 -0700
comments inline
>
> For us the following items would be under change control (CC):
> - Drop unused columns of a table (how do you know they're unused? If CC
> lets the DBAs drop columns that they "think" are unused then evenually
they
> will drop a column that is used or will be used in a future release - we
> add columns now, when we can get them through the CC board, against a
known
> future need.)
good points
> - create user / change password for a user / drop user (for non-schema
> users, e.g. employees having an account to use the application) - Not a
> chance in the world that the DBA could/would do this. We have a whole,
> separate control function/group that does nothing but create and
administer
> users. You can't have the DBA just creating users because someone asked
> them to.
We have a process for this. Here, the DBA *must* do it.
> - granting privileges to a user - see point above. Just because a user
> thinks that they need a privilege doesn't mean that they're going to get
> it. They must justify the need to the control group and, if approved,
they
> will be granted an existing role. If no existing role meets their need
> then a new role must be approved, impleted, and granted (as if that's
going
> to happen).
Again, there's a process. Users cannot request access. Their mgr must
request it and present justification. Just a different organization.
> - changing system parameters - will any system parameter change require
> approval by the change control board? - You bet! It had to be done in
the
> testing database first. If the change is of a type that would only be
> applicable to the production database - because of size, number of
users,
> specific platform, etc. - then it has to be reversible. If it's an
> irreversible change, ie, something goes wrong and the database has to be
> recovered or rebuilt, then it's not likely to be approved.
With a total of 842 parameters in 9.2.0.5, I don't think we can catalog
which are pre-approved and which are not. The DBA must still be allowed
some discretion ( I hope )
> - drop tablespace including contents and datafiles - If you can prove
that
> the tablespace is unnecessary then you can prove it to the CC board. The
> DBA can't just drop it because the DBA "thinks" that it's unnecessary.
>
Well, that one was a joke.
Jared
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
Other related posts:
