RE: Software Configuration Manager?

Rob,
I was not very pleased with it either as I discovered the same issues as
you did during our POC. In the context of Oracle EBS, what further
annoyed me is that it needed one agent for each stack of the suite. For
example, it will run one agent for the DB, one agent for iAS on the
backend server and one for the iAS on the middle-tier server.
Additionally, it does not capture information for the developer 6i
stack. And this all is just for one environment. If you run multiple
environments on a server, like we do, you will need the same
configuration for each environment. Oracle rep said that we should open
an SR with the support on the issues that you also found which I am not
supportive of because Oracle should know all these things if they are
testing this tool correctly.

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?