| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> Re: RMAN and control_file_record_keep_time
Peter,
I whole heartedly agree with the "Broke/don't fix" theory. This matter
came up in a meeting I attended last week and I was looking for a method
of bringing the database archlog info up to date with the backup info.
For example, I have over 500 archlogs listed when I view the info with
the OEM and I have performed numerious COLD backups of the database.
Should I not be able to remove the information if they are not needed
for a restore?. In the production database there are archivelogs listed
since May 2003 when I went live on the new server. The production
database is backed up using RMAN with a catalog. Maybe Oracle has not
thought about the need or the ability to keep the data in step and
cleaned up.
"Size doesn't really matter" is a true statement but cleaning up
after yourself would be nice.
Ron
>>> peter.gram_at_miracleas.dk 06/22/2004 5:27:26 PM >>>
Ron
Even if the control file is 27, 60 and 200 Mb I don't see a reason to
recreate the file. If you have some how can prove that the
performance of the database is affected by the size if the control
file
size it is fine to make a new control file. I have never
seen a prof that size does mater when it comes control files. A wise
DBA once sad to me "If it is not broken don't fix it".
/peter
-- 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 Wed Jun 23 2004 - 06:57:28 CDT
 |
 |