RE: Pre-Approved database changes

  • From: "Jacques Kilchoer" <Jacques.Kilchoer@xxxxxxxxx>
  • To: <oracle-l@xxxxxxxxxxxxx>
  • Date: Thu, 17 Jun 2004 14:48:35 -0700

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@xxxxxxxxxxx

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. 

Other related posts: