Re: Pre-Approved database changes
- From: "Stephen Andert" <StephenAndert@xxxxxxxxxxxxxxx>
- To: oracle-l@xxxxxxxxxxxxx, Jared.Still@xxxxxxxxxxx
- Date: Thu, 17 Jun 2004 18:05:18 -0500
- adding partitions. I make new partitions every month. Currently our
Change Control procedures say I need to log it, but this is considered a
"no approval needed".
- deleting empty partitions/tablespaces
- gathering statistics. This list has made it pretty clear that
analyzing can cause "profoundly negative results". We have currently
escaped tracking this since all of our analyze jobs are automated, but
that will probably change the first time a major system has a slowdown
and the only thing that has changed is a recent analyze and that was not
tracked.
Stephen Andert
>>> Jared.Still@xxxxxxxxxxx 06/17/04 02:00PM >>>
Dear List,
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.
Thanks,
Jared
PS. It's due tomorrow. ;)
----------------------------------------------------------------
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:
