Cross platform migrate repository and oms, gets "EM Key Verification Error"

Question

Hello,
I am trying to cross platform migrate repository and oms from Sun Solaris Sparc 64 bit to Linux x86-64bit.
Environment:
Original repository Oracle 10.2.0.3, OMS 10.2.0.5, Sun Solaris Sparc 64 bit
New repositoy Oracle 10.2.0.3, OMS 10.2.0.5, Linux x86-64bit
Following metalink note:
Subject: How To Move Grid Control Oms & Repository To Another Server
Doc ID: 853293.1
to step 4:
4. Point the new OMS to the new repository
can't get over emkey corrupt issue, gets error:
2009-10-13 14:07:24,570 [AJPRequestHandler-ApplicationServerThread-11] ERROR conn.ConnectionService verifyRepositoryEx.918 - EM Key Verification Error = Em key does not match with repos verifier
2009-10-13 14:07:27,910 [Shutdown] ERROR em.notification unregisterOMS.2573 - Error unregistering: EM Key is Missing java.sql.SQLException: EM Key is Missing
The newly installed additional OMS can only point to the original repository and can't point to the newly migrated repository.
Steps I did:
Install an addition OMS to point to original repository (make sure emkey is in repository)
create a new empty database on new host with a new name (is new name caused problem?)
migrate old repository to new (use export/import)
point new OMS to new repository by modifing emoms.properties
startup oms and gets emkey corrupt error
This metalink note does not help either:
Subject: The Em Key is not configured properly. Run "emctl status emkey" for more details.
Doc ID: 817035.1
I also have a SR open but still have no help from Oracle support. I did make sure the emkey is in the repository before migrate. There may be tricks that I don't know.
Can anyone shed some light on this?
Thank you for your help in advance.
Edited by: user1062137 on Oct 16, 2009 2:14 PM

Answer 1

Hi, I'm having the same issue.
Our original installation was on Windows 32bit with the repository and OMS on the same host. I want to move the repository to a linux 64bit host to make more resource available for everything. The new database is 11.1.0.7 though. As the Grid control release is 10.2.0.5 Oracle Support have confirmed that the 11g database is OK to use.
In the log I see a lot of this:
[AJPRequestHandler-ApplicationServerThread-5] ERROR conn.ConnectionService verifyRepositoryEx.911 - Invalid Connection Pool. ERROR = ORA-01031: insufficient privileges
ORA-06512: at "SYSMAN.MGMT_USER", line 10296
ORA-06512: at "SYSMAN.SETEMUSERCONTEXT", line 17
ORA-06512: at line 1
2009-11-05 18:54:57,254 [AJPRequestHandler-ApplicationServerThread-7] ERROR conn.FGAConnection _setConnContext.326 - java.sql.SQLException: ORA-01031: insufficient privileges
ORA-06512: at "SYSMAN.MGMT_USER", line 10296
ORA-06512: at "SYSMAN.SETEMUSERCONTEXT", line 17
ORA-06512: at line 1
java.sql.SQLException: ORA-01031: insufficient privileges
ORA-06512: at "SYSMAN.MGMT_USER", line 10296
ORA-06512: at "SYSMAN.SETEMUSERCONTEXT", line 17
ORA-06512: at line 1
2009-11-05 18:54:59,973 [Shutdown] ERROR em.notification unregisterOMS.2573 - Error unregistering: EM Key is Missing
java.sql.SQLException: EM Key is Missing
Unfortunately that package is wrapped so I can't see what privs are required.
The instructions say (simplified here) either datapump or exp/imp to the new database, run some admin scripts, then update the emoms.properties with the new connection information. Thats it - start OMS again and it should work.
Thankfully I can turn the old repository back on while I sift through these logs.