RE: Pre-Approved database changes
- From: "Jacques Kilchoer" <Jacques.Kilchoer@xxxxxxxxx>
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Fri, 18 Jun 2004 10:22:33 -0700
Drop unused columns - I was referring to the "alter table ... Drop
unused ... " command, to get rid of columns that are already marked as
unused.
Creating users and granting privileges - a DBA would probably not do
this, but whoever does it would not need to get approval from the CCB,
right?
Drop tablespace - that last one was thrown in as a joke of the "why
don't you try 'format c:'" variety.
-----Original Message-----
Thomas Day
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.)
- 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.
- 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).
- 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.
- 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.
----------------------------------------------------------------
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:
