OEM NAMED CREDENTIAL : java.util.HashMap cannot be cast to oracle.sysman.emSDK.sec.targetauth.EMTargetConnectionPool

On OEM, when DBA trying to browse database performance or top activity page,
The following error occurs:

java.util.HashMap cannot be cast to oracle.sysman.emSDK.sec.targetauth.EMTargetConnectionPool

Checked named credential working fine against database target, and preferred credential has been setup against database target accordingly.

Subscribe to get access

Read more of this content when you subscribe today.

How to Share Named Credentials Using a Role in OEM

In your environment, there are hundreds or even thousands of targets managed by OEM, and a doze or even hundreds of OEM administrators and users. In this case, effectively and securely managing Named Credentials ( NC ) is a challenging job. Usually, every OEM administrator or user creates and manages their own Named Credentials ( NC ). So many duplicate copies of Named Credentials ( NC ) are kept, it brings difficulties for updating them if any targets credentials changed.

This post demonstrates how to share a Named Credentials ( NC ) with many administrators and users in any size of OEM environment by using a role. Same as an Oracle database role, which can be granted to a role or a user.

The following content is only available to subscribers only.

Please Subscribe to Access Premium Content