This content has been marked as final. Show 5 replies
It sounds like your plan is to migrate both the Repository and the OMS to the new server.
For repository migration follow these steps:
For migration of the OMS follow these steps:
Your 11g agents will not work with 12c since the entire OEM architecture is new from the ground up. That's the bad news. the good news is that deploying new agents is a breeze with 12c (once the 11g agents are removed)
Actually we haven't got any 10g and 11g agents running on our environment. The entire environment is compose of 12c components. I've been studying the articles sent up there cos basically is what we look for. We need to migrate our OMS and Repository (+ASM, OEM12REP db, OMS_HOME, AGENT_HOME) from a machine to another hardware we'll buy, and after that point the agents 12c to that new server.
I tried the following the steps in below documentation:
Till step 8 everything worked fine and seems to be working but Step 9 did not work for me. Initially I "OK" button in the Weblogic domain change window was disabled then I started up the management agent in old OMS and could the "OK" button but then it could not change the Weblogic Hostname in the Weblogic Domain window. Later I found that I can delete the old target and add Weblogic Target with New OMS host but I was not sure about that and till that time had played around the config files so did not waste time and did fresh installation.
I would say if you are doing the migration using these steps just carefully gather info and work-arounds on Step 9, otherwise all it should work for you. Also let me know if you could this step elaborated. The documentation is not much clear about this.
Thanks for the response. I'll open a SR to get Oracle in this migration too, as we have support for that. We'll need to have a look carefully at these docs cos they are the line to be followed. The greatest thing is the entire environment composed by 12c components, it means we won't migrate OMS and OMA versions, but it's necessary to migrate from one machine to another.
As soon as we get the environment migrated, I'll update the information here with issues and workarounds we encountered.