EM13c : Kerberos Authentication Is Sporadically Throwing TGT Errors
(Doc ID 2637516.1)
Last updated on FEBRUARY 13, 2022
Applies to:
Enterprise Manager Base Platform - Version 13.2.2.0.0 and laterInformation in this document applies to any platform.
Symptoms
In Enterprise Manager (EM) Cloud Control, trying to login to target databases with Kerberos Authentication fails with TGT error.
"Unable to create connection from TGT, Verify the network configuration for database. See the log for more information."
Error stack from <EM_INSTANCE_HOME>/em/EMGC_OMS*/sysman/log/emoms.trc file:
2019-07-30 10:41:43,188 [[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] WARN toaster.MessageBroker logp.251
- WARNING! No Subscriber MQ with session Id: <Session ID>
2019-07-30 10:56:29,663 [[ACTIVE] ExecuteThread: '17' for queue: 'weblogic.kernel.Default (self-tuning)'] ERROR jdbc.ConnectionFactory getConnectionFromSubject.215 - EXCEPTION_WHILE_CREATING_CONN_FROMSUB java.security.PrivilegedActionException: java.sql.SQLRecoverableException: IO Error: The service in process is not supported.
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at oracle.sysman.emSDK.core.util.jdbc.KerberosConnectionUtility.getConnectionFrom Subject(KerberosConnectionUtility.java:170)
at oracle.sysman.db.conn.DBConnectionCache.getConnectionFromSubject(DBConnectionCache.java:285)
at oracle.sysman.db.conn.DBConnectionCache.getConnection(DBConnectionCache.java:228)
at oracle.sysman.db.conn.DBMetaConnectionPool.initializeConnectionCache(DBMetaConnectionPool.java:523)
at oracle.sysman.db.conn.DBMetaConnectionPool.<init>(DBMetaConnectionPool.java:181)
at oracle.sysman.targetauth.EMDBConnectionHandler.login(EMDBConnectionHandler.java:96)
at oracle.sysman.emSDK.sec.targetauth.EMTargetLoginService.doTargetLogin(EMTargetLoginService.java:491)
at oracle.sysman.emSDK.sec.targetauth.EMTargetLoginService.doTargetLogin(EMTargetLoginService.java:321)
at oracle.sysman.db.homepage.ui.DBLoginPageModelBean.doLogin(DBLoginPageModelBean.java:317)
at oracle.sysman.db.homepage.ui.DBLoginPageModelBean.doApplyAction(DBLoginPageModelBean.java:88)
- WARNING! No Subscriber MQ with session Id: <Session ID>
2019-07-30 10:56:29,663 [[ACTIVE] ExecuteThread: '17' for queue: 'weblogic.kernel.Default (self-tuning)'] ERROR jdbc.ConnectionFactory getConnectionFromSubject.215 - EXCEPTION_WHILE_CREATING_CONN_FROMSUB java.security.PrivilegedActionException: java.sql.SQLRecoverableException: IO Error: The service in process is not supported.
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at oracle.sysman.emSDK.core.util.jdbc.KerberosConnectionUtility.getConnectionFrom Subject(KerberosConnectionUtility.java:170)
at oracle.sysman.db.conn.DBConnectionCache.getConnectionFromSubject(DBConnectionCache.java:285)
at oracle.sysman.db.conn.DBConnectionCache.getConnection(DBConnectionCache.java:228)
at oracle.sysman.db.conn.DBMetaConnectionPool.initializeConnectionCache(DBMetaConnectionPool.java:523)
at oracle.sysman.db.conn.DBMetaConnectionPool.<init>(DBMetaConnectionPool.java:181)
at oracle.sysman.targetauth.EMDBConnectionHandler.login(EMDBConnectionHandler.java:96)
at oracle.sysman.emSDK.sec.targetauth.EMTargetLoginService.doTargetLogin(EMTargetLoginService.java:491)
at oracle.sysman.emSDK.sec.targetauth.EMTargetLoginService.doTargetLogin(EMTargetLoginService.java:321)
at oracle.sysman.db.homepage.ui.DBLoginPageModelBean.doLogin(DBLoginPageModelBean.java:317)
at oracle.sysman.db.homepage.ui.DBLoginPageModelBean.doApplyAction(DBLoginPageModelBean.java:88)
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 |
| References |