This content has been marked as final. Show 4 replies
You should (re-)create the repository and configure it, after creating the database
1- First check if sysman user has been created, in that case, run the following to drop it :
emca -deconfig dbcontrol db -repos drop
2- Then create the repository :
emca -repos create
3- ... And configure it :
emca -config dbcontrol db
Hope this helps
Because I created this new DB from a cold backup, and the fact that the SYSMAN user not only existed in the source DB, but scheduled jobs also existed, would not the repository already exist?
If I (re-)create the repository as you suggest, I would loose all of the jobs and many other settings from the source DB? It is my understanding that the OEM repository resides in the SYSMAN schema, is that true?
Is there a way to get the OEM on the new server/box to reference the already existing repository form the backup?
I perfectly agree, you should reconfigure the dbconsole without recreating the repository.
I think the main problem is the hostname change
you may try this :
1- remove the existing Database Control configuration : (does not drop the repository as far as I know)
$ORACLE_HOME/bin/emca -deconfig dbcontrol db
2- export the hostname of the current machine
3- recreate the Database Control configuration :
$ORACLE_HOME/bin/emca -config dbcontrol db
hope this helps
After starting over with a restore on a test server from cold backup.
I tried to start the OEM GUI again and got an error message saying to run “emctl status emkey”.
This generated a message saying to copy the emkey.ora file from the source or backup and then run:
emctl config emkey -emkeyfile <Loacation of the file>\emkey.ora –force
The OEM now works fine.
Thanks again for your time,