EM13C : emkey copy failed with error "Failed to get the EMKey from Management Repository"
(Doc ID 2543058.1)
Last updated on AUGUST 19, 2022
Applies to:
Enterprise Manager Base Platform - Version 13.1.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
In Enterprise Manager (EM) Cloud Control, Trying to copy emkey to the repository failed with the below error:
$emctl config emkey -copy_to_repos
Oracle Enterprise Manager Cloud Control 13c Release 2
Copyright (c) 1996, 2016 Oracle Corporation. All rights reserved.
Enter Enterprise Manager Root (SYSMAN) Password :
Error occurred. Check the log <EM_INSTANCE_HOME>/em/EMGC_OMS*/sysman/log/secure.log
But verifying the status of the emkey confirms the emkey is configured properly:
$emctl status emkey
Oracle Enterprise Manager Cloud Control 13c Release 2
Copyright (c) 1996, 2016 Oracle Corporation. All rights reserved.
Enter Enterprise Manager Root (SYSMAN) Password :
The EMKey is configured properly.
Copying emkey to the cred store failed with below error:
$emctl config emkey -copy_to_credstore
Oracle Enterprise Manager Cloud Control 13c Release 2
Copyright (c) 1996, 2016 Oracle Corporation. All rights reserved.
Enter Enterprise Manager Root (SYSMAN) Password :
Failed to get the EMKey from Management Repository. Check the log <EM_INSTANCE_HOME>/em/EMGC_OMS*/sysman/log/secure.log
Error stack confirmed from the <EM_INSTANCE_HOME>/em/EMGC_OMS*/sysman/log/secure.log file:
2018-05-15 11:04:48,840 [main] INFO mas.CredStoreUtil logp.251 - getCredential : Got creds for mapName -EM keyName - ENCR_DETAILS
2018-05-15 11:04:48,864 [main] ERROR util.EmctlUtil logp.251 - Failed to get EMKey from CredStore. Trying to get from repository.
java.io.IOException: Failed to get the EMKey from Credential Store.
at oracle.sysman.emctl.config.oms.EMKeyCmds.getEmKeyFromCredStore(EMKeyCmds.java:504)
at oracle.sysman.emctl.util.EmctlUtil.getReposConnUsingAdminServer(EmctlUtil.java:891)
at oracle.sysman.emctl.util.EmctlUtil.getReposConn(EmctlUtil.java:849)
at oracle.sysman.emctl.config.oms.StoreReposDetails.processCmd(StoreReposDetails.java:539)
at oracle.sysman.omsca.adapter.wls.OMSWLSAdapter.adapterPostDeployAndReposSetup(OMSWLSAdapter.java:3219)
at oracle.sysman.omsca.framework.OMSGenericAdapter.postDeployAndReposSetup(OMSGenericAdapter.java:333)
at oracle.sysman.omsca.framework.OMSCAFreshInstall.execute(OMSCAFreshInstall.java:203)
at oracle.sysman.omsca.framework.OMSConfigAssistantDriver.main(OMSConfigAssistantDriver.java:287)
2018-05-15 11:04:49,013 [main] INFO oms.StoreReposDetails logp.251 - Commiting the getLockConn to release lock on EM_UPDATE_DATASOURCES_LOCK
2018-05-15 11:04:49,014 [main] INFO oms.StoreReposDetails logp.251 - Done commiting the getLockConn
.
2018-05-15 11:04:49,080 [main] ERROR oms.EMKeyCmds logp.251 - Exception occurred while checking status of emkey in credential store : Failed to get the EMKey from Credential Store.
2018-05-15 11:04:49,080 [main] INFO oms.EMKeyCmds logp.251 - The EMKey exists in the Management Repository, but is not configured properly or is corrupted in the credential store.
Configure the EMKey by running "emctl config emkey -copy_to_credstore".
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |