We are advised to install the companion cd database-specific products
into the oracle home of the database. Which I did. I was advised to
reapply the patches, which I did. That seems to cause the em repository
to become corrupted. I had this happen before. I'm pretty sure
patching does it but
there are other things also.
BTW the repmanager still doesn't work as far as I can tell. I did
finally get it to run (it is very fussy about parameters and there are
a lot of them. What works is to give it ONLY -connect dbname -action
drop
[ and no more]. But it came back and said "repository creation failed.
Repos user already exists". Strangely repmanager not only asks for the
sys password, repos user name (sysman) and that password, but also asks
for your metalink id and password! but then flubbed fixing the
repository anyway. This is 10.1.0.4.0 so supposedly repmanager would
work but it does not (windows 2003 server).
But I note that what repmanager does eventually is call
a perl program emrepmgr.pl
I did test the way repmanager.bat
sets up the environment variables and
it does pick up the gnu perl 5.6.1 that oracle installed in preference
to the
activestate 5.8.4 I had already installed.
But I wonder if I should uninstall activestate perl anyway? Could there
be a place where they are getting ahold of the wrong libraries or some
such thing?
Btw these are the best instructions I have seen on the repository
problem:
http://www.idevelopment.info/data/Oracle/DBA_tips/Enterprise_Manager/OEM_3.shtml#On%20Windows%20Systems
Received on Tue Jul 12 2005 - 12:48:51 CDT
