RE: Pre-Approved database changes

From: <jo_holvoet_at_amis.com>
Date: Fri, 18 Jun 2004 09:43:49 +0200
Message-id: <OF971264E5.18715EE8-ONC1256EB7.002A5173@eu.amis.com>

Jacques,

around here any statement with the word 'drop' in it would not make it on to the list :) (except maybe drop user).

mvg/regards

Jacques Kilchoer <Jacques.Kilchoer_at_quest.com> Sent by: oracle-l-bounce_at_freelists.org
06/17/2004 23:48
Please respond to oracle-l

        To:     oracle-l_at_freelists.org
        cc:     Jared.Still_at_radisys.com
        Subject:        RE: Pre-Approved database changes

How exhaustive does this list need to be?
- Drop unused columns of a table

Recompile stored PL/SQL
create user / change password for a user / drop user (for non-schema users, e.g. employees having an account to use the application)
granting privileges to a user
exchange partition (this could fall under "change storage parameters")
alter table move (this could fall under "change storage parameters")
resize datafile (increasing its size)
moving datafile to a new location
adding more redo logs
changing system parameters - will any system parameter change require approval by the change control board?
turning on session tracing
drop tablespace including contents and datafiles

How about system shutdown / startup? Obviously you don't want to ask your control board everytime you do that.

Are you also considering any changes to configuration files, e.g. listener.ora, tnsnames.ora, password files?

Jared.Still_at_radisys.com

Those of you with stringent change control standards, or are currently going
through Sarbanes Oxley, may be familiar with pre-approved changes.

Essentially, all changes will be logged to the change control repository.

Yes, all.

There will be a list of pre-approved changes. These are changes that may be performed without review by the change control board.

These are things that are naturally done throughout the course of the day as part
of normal DBA duties. These changes are of a nature that the outcome is always
predictable, and does not result in accidental downtime or outages, or have other
profoundly negative results.

Keep in mind that there is an assumed level of competence and some discretion involved on the part of the DBA. You could probably perform just about any database operation and cause problems if you don't know what you are doing or act as if you are the only user on the system.

Examples:

adding datafiles to a tablespace
changing storage parameters on an index or table modifying database statistics through collection or deletion create exports
create backups
online index rebuilds ( in the rare case that it is useful ) Vertex Tax Table loads( yes, I'm stuck with those )

These changes are assumed to occur on active database systems, and are not part of some other normally scheduled procedure, such as a data load.

I would like to add to this list, and will welcome all suggestions and/or corrections.

If it is substantial, I will post it somewhere that all can access it.

Please see the official ORACLE-L FAQ: http://www.orafaq.com

To unsubscribe send email to: oracle-l-request_at_freelists.org put 'unsubscribe' in the subject line.

--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------

Received on Fri Jun 18 2004 - 02:40:38 CDT