Software Configuration Manager?
- From: LegeDoos <legedoos@xxxxxxxxx>
- To: "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 10 Jan 2008 15:49:15 +0100
Months ago I decided to give the Software Configuration Manager a try.
Today I had a look at the issues this manager found. I'm not pleased,
get the feeling this thing doesn't work as it should.
At the critical issues in Software Configuration Manager I get the following:
Archive log start is enabled: The database will eventualy hang if the
database is in archivelog mode, and no redo logs have been manualy
archived....
log_archive_start = FALSE, recommended TRUE.
First of all, our database instance is in NOARCHIVELOG mode for this
is a test database. Second, in metalink note 268581.1 I read that the
log_archive_start parameter is deprecated in release 10.1, we use
10.1.0.5. So, this "critical issue" is no issue I think.
I also get a patch advisory: "Database CPU for July 2007" is not
installed. I installed CPU October 2007 months ago...
What do you think about Software Configuration Manager? Am I the only
one with those weird messages?
Regards,
Rob
--
//www.freelists.org/webpage/oracle-l
Other related posts:
